cRIO "Serial Number"

[Christian_L]

---

asper wrote:

Is this "preliminary" version suitable for a stable solution?

---

Yes, the code is very stable. We are considering exactly how to package the VIs and how much of the source code to make open.

[dwisti]

Christian,
Thanks for taking the time to respond to my comments.  I guess I should have been a bit more specific on my requests.  I agree the comment is in the NI-RT.INI file and can can be read or written with config file VIs with a little work.  I also agree the netconf.ini can be manipulated with config file VIs but there is little documentation and it takes a bit of hacking to figure this stuff out.  I suggest NI write the VIs or create some documentation for the end user.  The time and date is not something the host (Non-RT) can read or set.  Replication tools are run on a host not on the RT target.  I would like to be able to read or set the time from the host system, when I'm applying an image to a new RT system.  I know MAX can't even do this but it would be a nice feature.

Well at least one of my suggestion made it to the list.  I'm a fond user of the replication tools so keep up the good work!

Thanks,

David

[Christian_L]

David,

Thanks for the clarification on the Set Date/Time function and the rest. I was interpreting that you wanted these functions to run in RT. I will add all of them to my list.

[Texas_Diaz]

I won't disagree with the need for VI's to do what you've described, but I do want to point out a VI you might not be aware of:

Functions->Real-Time->Real-Time Utilities->RT Set Date and Time.vi

In LabVIEW RT 8.5 we actually did add a VI so that you could set the date and time of the target, assuming the timezone has already been set correctly by MAX.  Realize you only get seconds level resolution on the time, but that should be adequate for most applications.

-Danny

[Christian_L]

I have published a new LabVIEW component (user VI library) called cRIO Information (CRI) which packages up all of the VIs to read back information about a local or remote (networked) cRIO system including the controller, backplane and modules.

http://zone.ni.com/devzone/cda/epd/p/id/1717