Components

cancel
Showing results for 
Search instead for 
Did you mean: 

Replication and Deployment Utility (RAD)

Hi,

 

It typically involves a significant IP change like:

cRIO IP settings from where we want to create image:

192.168.1.125 (255.255.0.0), Windows NIC IP settings: 192.168.1.55 (255.255.255.0)

 

cRIO IP settings where we want to deploy image:

192.168.2.128 (255.255.0.0), Windows NIC IP settings: 192.168.2.54 (255.255.255.0)

 

Of course, before we launch the deploy process, the cRIO (at address 192.168.2.128) appears in the target list in RAD tool.

I have to add something that may be relevant: on-site, at least one time, I faced the case (described in my previous post) where the physical unit cRIO from which I retrieved and where I wanted to deploy image was the same unit (for testing purpose). The other thing is that there is a second NIC on Windows machine which settings are set to DHCP.

 

Regards

 

Vincent

 

 

0 Kudos
Message 211 of 324
(1,283 Views)

out of my depth here, but wouldn't the fact that the Windows NIC IP subnet is set to 255.255.255.0 prevent the RAD tool from getting any messages back from the cRIO on ..2.128?  So the cRIO may get the packets from the windows NIC but not vice versa since the windows NIC subnet is set too narrowly?

 

[edit] the mechanism for discovering cRIO's are not the same as the mechanisms for communication with the cRIO.. for example TCP (FTP etc.) for moving files, but UDP for discovery.. so discovery != with visible for deployment tool file operatoins. [\edit]

QFang
-------------
CLD LabVIEW 7.1 to 2016
0 Kudos
Message 212 of 324
(1,280 Views)

Hi,

 

I don't have a cRIO-9075, only a cRIO-9074 on my end. I've a testing code I could use as image and reproduce that setup from NI Office.

Do you want me to do that? Or it's not worth and I should simply ask customer to redo the test and ensure that cRIO and Windows NIC are on the same subnet by putting 255.255.0.0 for Windows machine also.

 

Where I don't understand is why forcing the cRIO to Safe Mode by pressing Reset button would change? Is-it because in that case we don't try/need to reboot the cRIO before starting to deploy the image or something like that?

 

Regards

 

Vincent

0 Kudos
Message 213 of 324
(1,266 Views)

Looks like your subnet is improperly set.  Both RT and Windows should be 255.255.0.0.

0 Kudos
Message 214 of 324
(1,262 Views)

The subnet could be a red herring from me, or it could be that like you suggested rebooting the controller in safe-mode first allows the operation to complete even across subnets, or, perhaps the safe-mode uses a different IP on your RIO? (On our devices, rebooting to safe mode keeps the network settings of the RIO).

 

It's a delicate situation when you have to ask your customer to troubleshoot for you, but if your customer relationship allows you to do so, then it would be interesting to ask them to change the sub-net and try again and see if that works without them manually rebooting the cRIO into safe mode first.. I would be interested in hearing back if that worked or not if you are able to ask them for that.

 

( as an aside, you could extend/tweak RAD and have it change the local subnet automatically as and if required. Check out this thread on the subject of changing windows IP from LabVIEW. There may also be .net system calls you can make instead of doing command line like that thread suggests.. http://forums.ni.com/t5/LabVIEW/Change-IP-number-and-Subnet-mask-with-LabView/m-p/407555#M202099

QFang
-------------
CLD LabVIEW 7.1 to 2016
0 Kudos
Message 215 of 324
(1,260 Views)

Hi Joshua,

 

Thanks.

Where they're not defined at exact same subnet because of different subnet mask, shouldn't they be "compatible" (with what customer entered)?

If I take a PXI-RT and put it with address: 192.168.2.24 and subnet mask 255.255.0.0 and I have my windows NIC set to 192.168.2.29 and subnet mask set to 255.255.255.0, I can do typical operations like changing software on it but also detect it if not present in MAX, no?

 

[EDIT 03:40 PM EST]

I just did the test with a PXI-RT (192.168.2.24) being set with 255.255.0.0 subnet mask and Windows machine (192.168.2.29) set with 255.255.255.0 subnet. I can access the PXI-RT, retrieve image. I can format it from MAX. Then, I can re-deploy created image with RAD. I then changed IP of PXI-RT to 192.168.2.25 (with same 255.255.0.0 subnet). I can deploy created image as well, I don't have to force it to reboot in Safe-Mode (the deploy process includes the reboot and it seems to work well).

[/EDIT]

 

Regards

 

Vincent

0 Kudos
Message 216 of 324
(1,249 Views)

Can anyone provide a link to version 3.0.02 of the RAD utilities?  I am looking for a LV 2011 version to replicate some sbRIO devices and I think that might be it.  I have found older and newer, just not that one.  Thanks.

 

Matt

0 Kudos
Message 217 of 324
(1,202 Views)

Hi,

 

we have a trouble with RAD 5.5.2.

We are trying to use a cRIO image on wich we use the password on clean cRIO.

We are running the RAD as admin, but we receive the error #-2147220621.

 

Is it a known issue? How can we solve?

 

Thank you so much,

have a nice day!

0 Kudos
Message 218 of 324
(1,015 Views)

Hi,

 

What version of System Configuration do you have installed on your computer?

Do you know if you can successfully image a non-password protected cRIO?

What do you mean by a "clean cRIO"? (newly formatted?)

 

Warm regards,

 

Alisha Pulsipher | Product Support Engineer | NI R&D

0 Kudos
Message 219 of 324
(991 Views)

Hi Alisha,

 

first of all, thank you so much for the help!

 

We're using NI System Configuration 5.6 and we can image a non-password protected cRIO.

By cRIO I mean that we're trying to take an image of a pw protected cRIO and to write it on a cRIO whitout pw.

 

Have a nice day!

 

Massi

0 Kudos
Message 220 of 324
(938 Views)