MAJOR issue with labview(NI Update Service) update

[sanelss]

https://www.reddit.com/r/FRC/comment...ervice_update/

Doing an update from "NI update service" completely breaks code deployment to the robot. Anytime I deploy code I get this error:

Deploying WPI_CameraSetModeAttr.viWPI_CameraSetModeAttr.vi loaded with errors on the target and was closed. LabVIEW: (Hex 0x627) The function name for the niimaqdx.dll:LV_IMAQdxAttributeBatch:C node cannot be found in the library. To correct this error, right-click the Call Library Function Node and select Configure from the shortcut menu. Then choose the correct function name. Deployment completed with errors

Everything was working fine earlier today until I ran the update(11GB!). When I noticed this broke code deployment i tried to undo it to no avail. I then did a completely fresh install on another machine thinking something got corrupted. This time I did fresh labview install>ni service update>FRC update package. EXACT same issue then as well. So there is something with an NI update that completely borks FRC code deployment.

[Kevin Phan]

I had the same issue when I did the NI update, and I ended up getting something I wasn't suppose to have, which was a vision program that required an activation. I tried to work around it, but it continued to keep referring vis in the wpi camera vis. I ended up uninstalling and reinstalling in order to get the product out. I know that when you try to uninstall, a menu comes up with what do you want to uninstall, but at that time I had no idea what I downloaded from NI update. Long story short, do no update from NI update until specified by NI or FIRST.

[NI_Brian]

Hi Sanelss,

I am an Applications Engineer at National Instruments and I support the roboRIO and NI FRC Software.

It sounds like the problem lies somewhere within the Vision software on your machine. When you did a fresh LabVIEW install did you uninstall all NI software first?

I am currently working on reproducing this error and I will let you know when I have more information.

[sanelss]

Originally Posted by NI_Brian

Hi Sanelss,

I am an Applications Engineer at National Instruments and I support the roboRIO and NI FRC Software.

It sounds like the problem lies somewhere within the Vision software on your machine. When you did a fresh LabVIEW install did you uninstall all NI software first?

I am currently working on reproducing this error and I will let you know when I have more information.

Yes, but i also did it on a fresh machine. this is what i have found out so far:

Working:
-use new machine or if installed, remove all NI software from uninstaller
-install labview from CD
-install frc update package
-everything works

NOT working:
-install labview from cd
-run ni update service
-install frc update package
-CODE DEPLOYMENT ERROR

NOT working 2:
-install labview from cd
-install frc update package
-run ni update service
-CODE DEPLOYMENT ERROR

so regardless of if you do it before or after the frc update package, doing the ni service update will break some vis that wpi vision lib uses.

We don't use any other vision software other than just labview.

[NI_Brian]

Hi sanelss,

I was able to figure out the cause of this problem. In NI Update Suite there are two main sections: Critical Updates and Optional Upgrades.

Critical Updates:
Include bug fixes and improvement to the existing drivers and software on your computer.

Optional Upgrades:
Include complete upgrades in software which include much more than just bug fixes.

My guess is that everything in both critical updates and optional upgrades were selected on your computer. In this case it is not the critical updates but rather the optional upgrades that breaks deployment.

Specifically: NI Vision Acquisition Software February 2015 is what is breaking deployment. This is because the vision acquisition 2015 software (and everything else currently in the optional upgrades section) is built for LabVIEW 2014 SP1 and NI Software for FRC 2015 includes LabVIEW 2014 NOT 2014 SP1. Installing the 2015 vision software replaces all of the driver information with that built for LabVIEW 2014 SP1 so when LabVIEW 2014 is looking for the Vision VIs it cannot find it because it has been removed from the LabVIEW 2014 directory.

You can fix this problem two different ways: you can uninstall all NI software and reinstall the software from www.ni.com/frc (making sure to only apply the critical updates) OR you can uninstall everything that says vision 2014 SP1 or IMAQ 14.5 and then install Vision Acquisition August 2014 f1 (14.0) from this link, either of which will solve this issue.

[sanelss]

Originally Posted by NI_Brian

Hi sanelss,

I was able to figure out the cause of this problem. In NI Update Suite there are two main sections: Critical Updates and Optional Upgrades.

Critical Updates:
Include bug fixes and improvement to the existing drivers and software on your computer.

Optional Upgrades:
Include complete upgrades in software which include much more than just bug fixes.

My guess is that everything in both critical updates and optional upgrades were selected on your computer. In this case it is not the critical updates but rather the optional upgrades that breaks deployment.

Specifically: NI Vision Acquisition Software February 2015 is what is breaking deployment. This is because the vision acquisition 2015 software (and everything else currently in the optional upgrades section) is built for LabVIEW 2014 SP1 and NI Software for FRC 2015 includes LabVIEW 2014 NOT 2014 SP1. Installing the 2015 vision software replaces all of the driver information with that built for LabVIEW 2014 SP1 so when LabVIEW 2014 is looking for the Vision VIs it cannot find it because it has been removed from the LabVIEW 2014 directory.

You can fix this problem two different ways: you can uninstall all NI software and reinstall the software from www.ni.com/frc (making sure to only apply the critical updates) OR you can uninstall everything that says vision 2014 SP1 or IMAQ 14.5 and then install Vision Acquisition August 2014 f1 (14.0) from this link, either of which will solve this issue.

sounds good. do you advise doing any of the non-critical updates then or just leave them uninstalled? If they are not FRC related then they seem to just be a waste of space?

[NI_Brian]

NI Update Service is not FRC specific but will actually check for and recommend updates for all NI software including the FRC software. The optional upgrades are normally for new software so if you do not have that new software it is not always recommended (the update suite should warn you when it is not recommended).

In this case I do not recommend installing any of the optional software.

[zachmx]

To be more specific, Update Service will check for LabVIEW (which is part of LabVIEW for FRC) updates, not FRC updates. The FRC Update Suite and any related updates during the season will not be available through Update Service.

LabVIEW for FRC users do not need to download anything through NI Update Service.

[mgurgol]

I installed the SP1 updates when they came out, and received the message that there was a problem in vision.

I uninstalled all National Instrument software and started again.
Installed Labview from the DVD.
When applying the FRC Update, I am receiving the following message:
Procedure Entry Point Gen_MarkExternalBufferNoThreadCore could not be locating in the dynamic link library nivissvc.dll.

It will also pop up when I am loading RobotMain.vi. I do not have a robot to test with at the moment, as we have the St Louis Regional tomorrow. I can build the project, but I do not know if it will deploy or not. Has anyone seen this error before, any help would be appreciated.

[pleaseignore]

Originally Posted by mgurgol

I installed the SP1 updates when they came out, and received the message that there was a problem in vision.

I uninstalled all National Instrument software and started again.
Installed Labview from the DVD.
When applying the FRC Update, I am receiving the following message:
Procedure Entry Point Gen_MarkExternalBufferNoThreadCore could not be locating in the dynamic link library nivissvc.dll.

It will also pop up when I am loading RobotMain.vi. I do not have a robot to test with at the moment, as we have the St Louis Regional tomorrow. I can build the project, but I do not know if it will deploy or not. Has anyone seen this error before, any help would be appreciated.

I had the issue with the SP1 update at St. Louis, the CSA uninstalled everything and reinstalled Labview, but now I am getting that "Procedure Entry Point..." error as well whenever I try to deploy code. It seems to deploy fine, but it is very worrying that it throws that error every time I deploy. Can NI give us some advice on this?

[Greg McKaskle]

I did this to my laptop as well, just to see what the effect was and how to correct it.

As far as I can tell, you only need to downgrade the IMAQdx installation. It was bumped to 14.5 by the service and I uninstalled and installed from the kickoff upgrade installer and everything seems fine now.

My advice would be to open up the Add/Remove Programs control panel, open the NI SW section, and verify that the IMAQdx files are not 14.5. I have six IMAQ and IMAQdx products installed and they are all version 14.0. What does yours show?

Greg McKaskle

[rwood359]

Hi Greg,
I'd like to make sure that we only upgrade LV when NI issues a FIRST upgrade.
Will unistalling NI Upgrade Service from Add/Remove eliminate the auto checks?
Is it OK for us to do that?

[plnyyanks]

Originally Posted by Greg McKaskle

As far as I can tell, you only need to downgrade the IMAQdx installation. It was bumped to 14.5 by the service and I uninstalled and installed from the kickoff upgrade installer and everything seems fine now.

I can confirm this. When I was CSAing at an event I had a team with the same issues. I talked to Kevin, and we uninstalled anything that said Vision/IMAQ and reinstalled from the KOP disc. The team had no further issues.

[Greg McKaskle]

I have not tried uninstalling the NI Upgrade Service. For an FRC-only laptop, especially one that is a DS as well, it may be the right move. It is your SW and you can certainly give it a try and I'd like to hear feedback.

I'm sure we will discuss this for next year and make some changes. At the very least, we need to have the groups who broke compatibility add tests to avoid that. I also see little value in telling FRC teams about the updates that will not affect the robot, but will take lots of time and bandwidth. But we need to discuss this with various other teams before we make a recommendation.

Greg McKaskle