04-12-2010 08:35 AM
I'm experiencing a big problem since installing Veristand on a customer machine running Windows 7.
Often (like every 15minutes) the connection between the host and the PXI is lost and there is no way to reestablish it other than rebooting the RT target.
When this event occurs the RT system keeps running, the model, the DAQ, everything seems ok, but the workspace doesn't reconnect. Exiting the WS and reopening it does not solve the issue. Only rebooting the PXI solves the issue.
This problem makes the HIL system rather useless, since it is impossible to run automated tests unattended.
Are there any workarounds, tests or further investigation I can make?
04-12-2010 10:07 AM
Do you have a second host machine with VeriStand installed? I'd be interested to see if it can connect to the target after the connection is dropped on the first host. Another good thing to check would be to see if exiting VeriStand and possibly rebooting the original host machine allows that host to connect to the RT Target.
This could help us determine if the issue is on the host or target side.
04-12-2010 10:13 AM
The host machine seems to have no effect on the problem. I've tried rebooting the host with no success, the target remains unaccessible.
I'll try using a different host machine, but it seems the target gets in a state from where it cannot recover.
04-13-2010 10:56 AM
A couple questions:
Here are a couple more things we can do to try to isolate the cause of this issue:
04-13-2010 11:12 AM
Here are some of the answers:
1) PXI8110 with standard ethernet
3) The problem is not related to any particular action, it may happen without actually doing anything on the host
4) Yes, I can access the RT via FTP
5) No, cores n.1,n.2,n.3 are running at 20%, the n.4 is at 50%
I can add another weirdness:
- when the system is running if I disconnect the ethernet cable the connection led on the workspace stays on. After reconnecting the cable sometimes it gets back online, sometimes no and sometimes stays in between, meaning that I can change control values (and the system reacts accordingly) but cannot read back indicators (everything is frozen).
I'll do the proposed tests tomorrow.
05-07-2010 02:44 PM - edited 05-07-2010 02:46 PM
Hello, I am having a similar issue but am running Windows XP and talking to an industrial PC running LabVIEW RT connected to a PXI-1033 chassis over MXI.
Here are my answers to the same set of questions:
1. What type RT target are you using? Are you using the standardethernet port or another ethernet card?- I am using an industrial PC running LabVIEW RT connecting to the PXI-1033 over MXI.
2. Are the RT target and host on the same subnet?- Yes.
3. Were you doing anything specific on the host when this happens? Areyou running stimulus profiles or anything, or does it occur regardless ofwhat the host PC is doing?- Nothing specific. Once I disconnect the Ethernet, I lose communication with the RT system. But when I physically reconnect, Windows actually tells I am connected.
4. Can you ping the target or connect with an FTP session after thedisconnect occurs?
- Yes, I can ping and FTP via an FTP client. However, when I try to deploy new code via VeriStand FTP, it tells me that the FTP connection fails. The RT's monitor also continues to show that my host is connected (doesn't recognize the disconnection). Windows tells me I'm connected too.
5. Is the target experiencing a very high CPU load that might preemptthe TCP threads?- No, both CPU's are under 30% in usual operation.
1. Deploy an empty configuration the target from the same Windows 7machine and see if the same behavior occurs.- I am using Windows XP but I cannot deploy as I cannot connect via VeriStand's FTP.
2. Deploy a configuration from another host machine on the same networkand see if the disconnect ever occurs. (Windows XP would be ideal, becauseit has a different network stack than Vista and Win7.)- I don't have easy access to another machine that I can run VeriStand from.
3. To test if the network is causing this issue, you might also tryconnecting the Windows 7 host machine to the target using a cross-overethernet cable and see if the behavior still exists.- I don't have a crossover cable handy here. Are you suggesting that a standard cable can work most of the time but after disconnecting and reconnecting it may not recognize the new connection? For what it's worth, Windows tells me it's reconnected but the workspace has no real response.
06-07-2012 10:01 AM
I had the same probleme
The workspace stops responding when there are many control.
After this i must kill veristand.exe next re start veristand projet and re connect to the target.