LabVIEW Real-Time Application Deployment

[ePower-ahp]

I am using v3.0.2 (October 2012)

Now I have tried a little more, and it is correct RAD is setting up the FTP password at the sbRIO. But it will still not detup the paqssword and user rights for "NI Web-based Configuration monitoring".

It should be said that I get the error when I install the SW (but it seems as all the other parts is installed):

Error -2147220621 at nisyscfg.lvlib:Initialize

<b>Complete call chain:</b>
nisyscfg.lvlib:Initialize (Helper).vi
nisyscfg.lvlib:Initialize Session.vi:1
rad_Open System Config Session.vi
rad_Reboot (IP) Wrapper.vi
rad_Deploy Images with Progress.vi
rad_Deploy Application Image.vi
Replication and Deployment Utility.vi

Am I doing anything wrong?

[JimMacD]

I am using RAD v3.0.2. Is there a newer version?

[JoshuaP]

What version of LabVIEW RT are you using and what version of NI System Configuration on the host?

[ePower-ahp]

I am using LabVIEW RT 2012 (Real time module version 12.0.344.0) and System Configuration 5.3 on the target. It should be the newest on both...

[Burt_S]

After further investigation, it seems that the NI-Auth settings may not get copied properly if the target is not reboot immediately after the image is applied.  The next release of the RAD should have this issue resolved.  In the meantime, there are a couple of ways it can be fixed using the source code download.  Perhaps the easiest is to open the 'rad_Deploy Images with Progress.vi' and go to the Deploy Image case.  There you will find a 'restart after imaging?' boolean which can simply be changed to True.

An alternative approach could be to call 'Set System Image' from the System Configuration API a second time with a blacklist of '/'.  This should blacklist everything on the controller and only apply the NI-Auth settings.  Let me know if you have any questions about this and I will update the forum as soon as a new version of the RAD is released with a fix.

[S1ack]

Have used RAD succesfully previously.

Today I am needing to image a cRIO-9074. Getting this error.

I rebooted my dev machine, but made no difference.

LV 2011

XP 32 Bit

RAD V3.0.2

Now, during the course of writting this I had to enable my wifi to see corporate proxy.

I let RAD discover targets, and it discovers some on local subnet, and on corporate WAN. 

And pulled the image succesfully.

Anyone care to clutch at some straws?

[QFang]

BUG report:

Level: minor

Version: RAD 3.0.2

Short description:

IP reported in deployment log may not match actual IP setting. (When "Apply the Network Configuratino Found in the Image" is selected via deployment)

Suspect log IP field is populated prior to final reboot.

Steps to reproduce:

(note most of the steps are probably not required, but this is how I happened to do it when it happened)

Have a working image (created with RAD 3.0.2) on hand.

Start with a blank cRIO without an IP.

Set cRIO to "safe mode"

Connect network and then power cable

Refresh the list and note the IP. Mine was assigned 192.168.1.25 by our DHCP server.

Deploy image to cRIO and choose "Apply the Network Configuratino Found in the Image" (the image IP in my case is 192.168.1.249)

Complete deployment and save a "Log" to disk using the completed dialogue.

Open the log file. All the information appears to be correct, except the IP address which in my case lists 192.168.1.25. It seems the IP is pulled either at start of the deployment, or prior to the post deployment reboot. The log thus contains the wrong IP. I confirmed by FTP connection that the cRIO has the desired IP of 192.168.1.249 from the image.

[QFang]

Anyone know why I would get these two "Bad VI" messages during mass compile in LabVIEW 2012?

I have the following packages installed using VI Package Manager:

ni_tool_string 

ni_tool_keyedarray

ni_lib_amc

#### Starting Mass Compile: Fri, Feb 22, 2013 8:40:25
Directory: "C:\Users\Kjell Ims.QOREX\Documents\GIANT9v\RH\Software Projects\RAD\trunk\source"
### Bad VI: "rad_Deploy Image State Machine.vi" Path="C:\Users\Kjell Ims.QOREX\Documents\GIANT9v\RH\Software Projects\RAD\trunk\source\subVIs\App Images\Deploy App Images\rad_Deploy Image State Machine.vi"
### Bad VI: "rad_Set Application Image To Target.vi" Path="C:\Users\Kjell Ims.QOREX\Documents\GIANT9v\RH\Software Projects\RAD\trunk\source\subVIs\App Images\Deploy App Images\rad_Set Application Image To Target.vi"
#### Finished Mass Compile: Fri, Feb 22, 2013 8:41:56

[JoshuaP]

If you are using DHCP then there is no guarantee the IP address will be the same on the source and destination targets. Only the hostname will be the same. This is because DHCP relies on a DHCP server to automatically assign ip addresses. You would have to change to using static ip addresses if you wanted them to be the same, but be careful if you to reserve the address if on a DHCP network to avoid conflicts.

[QFang]

Joshua,

I thought I replied via my cell but I see it never posted.

Please note that the IP log issue I described is not due to DHCP. If you re-read and look between the lines, you will see that while the initial IP is assigned via DHCP, I stated that I use the option of applying the network settings from the image when I do the image deployment. The image has a static IP setting. After the image has been deployed, the cRIO indeed has the expected static IP and network settings, but the LOG of the deployment incorrectly lists the initial DHCP assigned IP..   I suppose you could argue that the log file shows the IP that you deployed the image to, and there may be some value in that, however, you definitley want to know what IP the device will take on after the deployment as well.. So maybe a better way would be to update the log to have "pre" and "post" -IP entries in the log file.