The issue is unresolved. I updated the software to 16.0. Initially that allowed me to move cycle the actuator from 0% final value AO(closed) to 100% final value AO (open), before the interface disconnected.
What we are doing is testing automated valve assemblies/packages that we have built to verify proper function before we ship. That involves moving the valve to set positions: 25% final value, 50%, 75% etc..
The first time this occured we had the actuator manufacturers field techs in house and they were unsuccessfull in finding a solution, finally resorting to the use of a fischer field unit(486?) and the actuator performed with no issues.
So, we can find the device on the network, set tags, export parameters but when it comes to cycling, the interface disconnects during movement requiring a reboot of the program to restablish the connection. Following is the process we are following:
- establish the connection to the device
- opening the resource block and selecting "auto" rather than "OOS"
- opening the transducer block
- changing the control mode to "AO only"
- selecting "manual" rather than OOS
- under Final Value AO, selecting quality: good non cascading, sub-status "non- specific"
- changing the value with in the range of 0-100, then writing changes
This is the extent of our experience with the NI software. We just need to verify functionality, the rest is up to the end user. We are not involved with plant engineering or configuring the blocks.
