sachsm
2008-08-11 20:10:07 UTC
Greetings,
First off, let's take our hats off to the team at NI for creating this technology, it is a powerful new set of features for cRIO and has tremendous potential.
I have a application that will require 9 cRIO chassis. There will be 3 identical 'sections', each with 3 cRIO's. It would be ideal if
each cRIO could read a disk config file that would contain scaling constants for each I/O Variable. This would require programmatic access
to the I/O Variable Properties which is not currently available. It does appear that the hooks are in the place under the hood but have not
been wrapped in LV yet. For the next 6 months I will only be building one section of my system, but by next Q2, 2009 I will need to complete all 3 sections
and would like to have some idea if these types of features will be forthcoming. My wish list would also include the ability to
programmatically create or rename I/O variables and perhaps even add inline filtering to the scan engine. Thanks,
Mike Sachs
Intelligent Systems
www.viScience.com
Onsite at the NASA Marshall Space Flight Center
First off, let's take our hats off to the team at NI for creating this technology, it is a powerful new set of features for cRIO and has tremendous potential.
I have a application that will require 9 cRIO chassis. There will be 3 identical 'sections', each with 3 cRIO's. It would be ideal if
each cRIO could read a disk config file that would contain scaling constants for each I/O Variable. This would require programmatic access
to the I/O Variable Properties which is not currently available. It does appear that the hooks are in the place under the hood but have not
been wrapped in LV yet. For the next 6 months I will only be building one section of my system, but by next Q2, 2009 I will need to complete all 3 sections
and would like to have some idea if these types of features will be forthcoming. My wish list would also include the ability to
programmatically create or rename I/O variables and perhaps even add inline filtering to the scan engine. Thanks,
Mike Sachs
Intelligent Systems
www.viScience.com
Onsite at the NASA Marshall Space Flight Center