2 replies to this topic

[g_l_u_p]

Hello everyone,

My project:
We have 2 PXI-RT communicated by 2 connections: a fiber optics connection (not Ethernet), and an Ethernet connection. The FO connection is the main connection used to wsend a receive data. The Ethernet connection is only use when the FO connection is lost, in order to check if the "mute PXI" has lost the FO connection but is still on, or if the PXI has been switched off.

The problem:
Originally we used the "RT Ping controllers.vi" on the "Real-Time Utilities", but unluckily we changed the PXI controller and the new one is not supported by the library.
The main issue is the application was developed using LV7.1 and cannot be upgraded.

Options already disscarted:
We tried opening a TCP connection, but the operation takes too long.

I found this great VI, but its for LV2010. I tried it and it works perfectly. (http://forums.ni.com...er/td-p/1535420)
I tried translating it to LV7.1, but something is wrong, because LV closes as soon as I play Run

Have any of you worked using wsock32.dll on a PXI?

Best regards,
g_l_u_p

Attached Files

•  ping_PharLap_LV711.vi   217.98K   59 downloads

[g_l_u_p]

Just found out why my VI was closing LabVIEW. The first "Call Library Function" was using "Calling Conventions = C" instead of "stdcall (WINAPI)".

Now, the VI doesn't close LV, but timesout on the call to function "select" (befor the "recvfrom"). It actually behaves the same running on my PC or on PXI-RT.

Could anyone have an idea ?

Thanks again
g_l_u_p

Attached Files

•  ping_PharLap_LV711.vi   295.31K   64 downloads

Edited by g_l_u_p, 18 November 2011 - 01:21 PM.

[JamesMc86]

Could you implement a UDP heartbeat instead? Have the mute controller send hb to a port on the other controller. If it times out waiting for it then the other controller is off/down. This would be a typical alternative to ping and confirms not only that the controller is on but that it is running.

(null)