Dear CD,
I have tried loading Labview using WPI website instructions for 2022. I have used Labview in the 2016 season so I a familiar with the setup instructions. I have received the same error on both my desktop and laptop. I have removed the installation on my desktop, reinstalled (takes a while), and received the same error message. I do not have a cRio connected. Is there a solution to this problem? Are other Labview users having the same issue?
What is the error?
What is the operating system?
Mark,
Wow, that was a quick response.
Same as shown in the title bar.
Windows 10
LabVIEW: (Hex 0x41F) Object reference is invalid.
Did you uninstall all old National Instruments Software (that includes old FRC Game Tools too) before installing the latest LV?
Do you get the 2022 FRC starting Window when LabVIEW starts?
I’ve seen the error before, but it was always associated with a mixture of LV software versions.
Yes, I did a thorough uninstall. I have not been in FRC since 2016, dipping my toes back into FRC, so I did not have old stuff on desktop… laptop used in FRC 2016 may be different story but focusing on desktop right now.
Yes, I received the error while creating a new Robot Project for 2022.
Marc
@oscarfonloz & @JeffB & @Jonathan_L have you seen this error recently?
Then it seems to be behaving as if a package wasn’t installed properly or was corrupted, or a package that shouldn’t have been installed was, but since you tried multiple machines and uninstall/reinstall I don’t know why that would be the case.
I’m doing a search of the NI forums but haven’t found anything applicable yet.
Mark,
Thanks.
I have ordered a new, laptop that I will be receiving Sunday night. This will allow a “clean” install and may solve the problem. But, I have to believe that other folks should be having similar issues.
Thanks for your help, off to school to work with some students.
Only other thing that comes to mind is if you accidentally installed any non-FRC specific LV updates, like general “recommended” updates (which are not recommended by FRC).
I might try a few installs to see if I can come up with a way to repeat the error you are seeing.
Have fun building/prototyping today!
Mark,
There were two groups of NI software installs that I used. The first was a smaller group, the second a much larger group. I tried to not accept the second group, but was unable with initial attempts. Is the first group the only group I should be accepting for FRC 2022 Labview?
Mark,
Is the “official list of FRC2022 Labview programs” posted somewhere?
No list, so I’ll go through and take some screen shots during the install of what gets selected.
I have to uninstall first to get the right feedback.
Just the
P.S.
NI gives a walkthrough that you probably followed: Installing LabVIEW for FRC (LabVIEW only) — FIRST Robotics Competition documentation
That shows some of the checked products. Those checks should be left alone.
Say “NO” when it asks about the NI Update Service. That can be a problem.
Can you explain this for me? I’d expect you to install LabVIEW Software for FRC 2022 first. That will have a LOT of software checked. After you hit ok, you’ll have a bunch of recommended things as well. Ideally, you wouldn’t change the checkmark on any of these. You’d get a couple of license agreements to agree to and then a series of installs that all need to occur.
After that, you’d install FRC Game Tools 2022. You’d have a couple of checkmarks you can choose (I’d check the WebSockets option and am making sure it’s selected by default in the future). You’ll see some installs and then have everything.
What extra installs are you seeing and what are you trying to stop? There shouldn’t be anything else you’re seeing. And, you shouldn’t be trying to avoid any of the things mentioned prior installing.
Which project are you trying to create? Do you see this error with all of them or just one type? That helps me narrow down and try to reproduce here as well.
Also, I like this advice too. It SHOULDN’T impact this year. It’s still generally great advice for FRC. The more updates you install, the further you get away from the software stack that’s been used to test the FRC projects both at NI and within the beta. It’s caused some frustrating bugs to hunt down in the past.
I went through the install and took a few more screenshots to aid the discussion.
The first choice that Marc is probably talking about is only a few packages and all should be checked by default:
The second group is the much larger one and again the default should be taken. Do NOT Select All or anything like that, because there are several listed at the very bottom that are not, and should not, be selected:
At the end the license activation only activates 8 licenses:
But does not activate 6 licenses (and those do not need to be activated for FRC use):
Finally, reboot to complete the installation, and run the Games Tools installation.
Mark and JeffB,
Thanks guys. I think it is working on my desktop. I will connect up to cRIO at school for final confirmation.
I went through the whole uninstall and reinstall process that Mark has shown and was careful to NOT select the NI update service option. That is most likely the key to the issue.
The instructions at WPILIB say “You will be prompted whether to enable the NI update service. You can choose to not enable the update service” should probably be changed to be more specific and say “DON’T SELECT”, lol.
I did receive an initial error message, different from the Error 1055, but it did not show up again after I saved and reopened the same FRC2022 Robot Project.
Thanks again, will keep the thread open when I load my new laptop using the same sequence early next week.
Marc Center, former FRC3548 coach, Royal Oak, MI
I guess I should have read the next line more carefully,
Warning
It is not recommended to install these updates unless directed by FRC through our usual communication channels (FRC Blog, Team Updates or E-mail Blasts).
Mark,
It is not mentioned above but should I have turned off my Antivirus utilities, McAfee?, when performing the installation? In the distant past, I believe that was sometimes important.
I don’t have 3rd party anti-virus running during installations if I trust the source like this.
There might be a log message from McAfee that you can check for, just to see if it was actively interfering.
