10-04-2011 05:03 PM
Hello Gharb,
What version of LabVIEW real-time are you using? For LabVIEW 2009, the RIO System Replication VIs do not work when the modules are in scan mode. One way to solve this problem is to reinstall NI Scan Engine support on the CompactRIO. Does it work without error when reinstalling the NI Scan Engine through Measurement & Automation Explorer?
Thank you,
Deborah Y.
02-03-2012 04:34 AM
Ben S -
This CAR ID 19078, what is the status of it (can I find that somewhere myself?)?
I just spent 1,5 weeks of bug hunting trying to figure out why one of two CFP-2220s refused to respond if it happened to have both Ethernet ports connected (it would boot properly if either only port 1 was connected at startup, or if one of the ports were connected to a network with a DHCP server, OR one single reboot if I removed the TCP_Stack section in the ni-rt.ini file...). The application ofn the controllers does some IP switching using the System Configuration API so I spent a lot of time thinking that had something to do with it, but could finally isolate it to the ni-rt\system folder..and when I did a file diff on all the files between a working system and a non-working one the netconf.ini file put me on the right track:
Here's a copy of the netconf.ini comparison, with the working one on the left and the non-working one on the right. I'v been using the RTAD utility from NI to apply the same image to 8 controllers - so I had one controller that worked fine, probably because that is the one that the image was based on...
02-06-2012 04:05 PM
Hi Mads,
The CAR ID number is actually 190786. This CAR has not been published online, we typically only mention fixed CARs in the readme files for our software installations.
This car has been closed out because we are planning to deprecate the RT system replication VIs and move to the System Configuration system replication VIs owned by MAX. This CAR has already been handled in Measurement & Automation Explorer version 4.8.
The Measurement & Automation Explorer VIs are located the Functions Pallet under Measurement I/O»System Configuration»RT Software. These VIs should be able to perform for functions you are looking for.
02-07-2012 03:06 AM
Hi Mike
Does this mean that the RTAD Reference is going to be updated to use the system configuration vis or is there going to be a totally new NI reference that does the same thing as the RTAD?
If the RT system replication vis are going to be deprecated does this mean that they will cease to exist in some future version of LabVIEW?
If there is going to be a new reference design based upon the new vis is it going to be backwardly compatible with the image files generated by the RTAD? The RTAD is a very useful tool for deploying the same software to multiple RT systems and to assist in software configuration and management for Quality Assurance purposes.
I am deploying systems that will need to be supported for several years and do not want to continually change my software configuration and management systems. Whilst I appreciate the improvements that NI have made regarding RT deployment over recent versions of LabVIEW I hope that some thought has gone into support of RT systems over the long term. Many RT systems will be operating for several years and deployed after the software has completed development.
Cheers
Stephen
02-07-2012 09:51 AM
Hi Stephen,
The RTAD Reference will remain a part of LabVIEW for future years. Currently both approaches are viable solutions. The use of the System Configuration VIs are just a suggested route if you are running into problem relating to CAR 190786. With long term systems in mind the RTAD Reference will continue support in future version of LabVIEW. There are no distinct timeliness on this but, I imagine the developers will take in consideration long term applications.