Issues connecting to an already deployed and running system definition

[raphael.wittwer]

Dear Forum

I set my real time target to automatically start the system definition on boot. Most of the times it starts well and I can connect from Veristand to the running project. Sometimes however when I try to connect to the target I get the output in the logfile below and it doesn't connect. I can see the target is running on the screen attached to the target.

If I try to deploy the system definition subsequently I get error -307661 "NI VeriStand failed to deploy the system definition file." This can only be solved by a restart of the target where it throws the error code 1556 and halts execution. Then I can redeploy and it works again for a few restarts.

Any idea why this happens and how I can avoid this?

Thanks, Raphael

The log output:

• Start Date: 15.05.2018 11:11
• Loading System Definition file: C:\Users\Public\Documents\National Instruments\NI VeriStand 2017\Projects\EFFPP\EFFPP.nivssdf
• Initializing TCP subsystem...
• Starting TCP Loops...
• Connection established with target PXI RT.
• Preparing to synchronize with targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Connection established with target PXI RT.
• Querying the active System Definition file from the targets...
• Connection established with target PXI RT.
• Querying the active System Definition file from the targets...
• Connection with target PXI RT has been lost.
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Querying the active System Definition file from the targets...
• Stopping TCP loops.
Waiting for TCP loops to shut down...
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:
Error -307672 occurred at Project Window.lvlib:Project Window.vi >> Project Window.lvlib:Command Loop.vi >> Project Window.lvlib:Connect to System.vi

Possible reason(s):

NI VeriStand: Mindestens eines der Zielsysteme konnte nicht vor Ablauf des festgelegten Timeouts gestartet werden. Prüfen Sie die Konfiguration der Start-Trigger und Taktsignale.
=========================
NI VeriStand: NI VeriStand Gateway.lvlib:VeriStand Server Wrapper.vi >> NI VeriStand Server.lvlib:NI VeriStand Server.vi

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
• TCP loops shut down successfully.
• Unloading System Definition file...
• Connection with target PXI RT has been lost.
• Connection with target PXI RT has been lost.

[timtamslam]

Hey raphael.wittwer, 

Can you elaborate on how you are connecting between the PC and RT target? (directly, via switch, etc). If you can simplify the network connection and try to rule out any network switches between the PC and RT target that will help troubleshooting.

Have you checked the processor utilization on the RT Target when this happens? Assuming you're using a PXI or RT PC you can connect to the video output and see the CPU usage of each core. If your RT target is using Core 0 a substantial amount, this could be starving the RT targets ability to communicate over the network.

[raphael.wittwer]

Hi Tim

I am connecting via a network switch. The windows machine and the target share one VLan, I also suspect that something about this might be part of the problem. I will try to rule this out today.

The processor utilisation is fine while this happens, having the screen attached to the target I can even see that the target runs fine.

Thanks,

Raphael

[Wangen_Patel]

Hello Raphael,

I know its old thread to start the discussion but Still Curious to know that "Did you found a solution for this error -307661 ?". I have a similar issue but once in a while randomly. I am kind of blind to find the solution. Thank you in advance.

[raphael.wittwer]

Hello

there have been so many changes to the way I start my system that I couldn't say which one was the solution. I start the system with a script now which tries to connect to the already running real time system which seemed to improve things.

It was definitely unrelated to the switch/Vlan setup since this is unchanged.

Raphael