I have a serial communication custom device, with one channel to control the serial port connection and it's mapped to WorkSpace.
The RT driver has VISA open and configuration before the Timed Loop, and VISA read/write inside the TimedLoop
The plan is to run the NIVS project, power up UUT, click on "connect" on WorkSpace to set up the serial port communication.
Our protocol defines - if UUT doesn't get "connect" command within 5 seconds, it fails the connection.
Here the problem comes - The "connect" command won't be available until WorkSpace becomes available. While WorkSpace comes up at least 10 seconds later after the NIVS starts to deploy. But VISA open/configuration happens immediately after NIVS is deployed. So if UUT is powered on after WorkSpace is available, VISA open will fail with "resource not available" error; if UUT is powered on when NIVS starts to deploy, "connect" command will timeout due to our protocol.
Any kind of suggestions will be very much appreciated.
