LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

RT Reboot Controller and RT Ping Controllers with PXI-8184 and LabVIEW 7.1

Hi,

 

I’m having problems using RT Reboot Controller and RT Ping Controllers from the Real-Time Utilities palette with LabVIEW 7.1, but only with PXI-8184 controllers.  This work fine with PXI-8175.

 

The attached VI will list all the 8175 on the subnet, but none of my 8184.  However, I can ping and FTP all my 8184.   If Local Subnet? is TRUE, I don’t get any error, but the RT controller doesn’t reboot.  If it is FALSE, I get: Error 63 occurred at TCP Open Connection in FPC open connection.vi->RT Ping Controllers.vi->MssUT-RebootController.vi.  All 8175 and 8184 are on the same subnet and ahve the same IP settings (mask, gateway, DNS server).  None of them is locked with a password.

 

What’s wrong with this VI and 8184 controllers?  Please don't tell me to upgrade to LabVIEW 8.2, I can't, these systems are under production in 3 sites in 2 countries.  We already have 16 PXI-8175 deployed that control cars from trains in hump yards.

 

Thanks,

 

Patrick.

0 Kudos
Message 1 of 6
(3,666 Views)
The issue is that the PXI-8184RT was released after LabVIEW RT 7.1. The RT Ping Controllers uses an internal protocol to find ethernet base devices. It is actually used on more than just RT targets as other products like GPIB and Serial Enet devices. The RT Ping Controller VI in LVRT 7.1 uses a white list of known RT targets to provide you with only the RT targets. KB 3MEGCEUW contains and updated version of the library with that VI.
 
FYI, rather than update that every time a new RT target comes out, we've changed that to being a black list of non-RT targets. This means if a new non-RT ethernet based device came out it might mistakenly be returned as an RT target but we thought that was better then your RT target not showing up.
 
-JRA 
Message 2 of 6
(3,659 Views)

Hi Partha,

    I am also getting the similar problem when i try to restart the PXI 8196 controller programatically. Did you already found any solution for this problem?

 

 

Balaji PK (CLA)
Ever tried. Ever failed. No matter. Try again. Fail again. Fail better

Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
0 Kudos
Message 3 of 6
(2,908 Views)

Balaji,

 

As stated above, the device was released after LabVIEW 7.1 so it was not showing up in the list of devices.  There is a link above to a Knowledgebase article that discusses that and provides a library that will fix the problem.

 

Regards,

0 Kudos
Message 4 of 6
(2,892 Views)

Thanks Nunnya, It worked 🙂

Balaji PK (CLA)
Ever tried. Ever failed. No matter. Try again. Fail again. Fail better

Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
0 Kudos
Message 5 of 6
(2,886 Views)

I would not use PXI with LabView 7 !!!

I would suggest: Use LV2012!

Buy / renew SSP and use the latest version (also of DAQmx). I have seen that a lot of changes / bug fixes were with PXI.

 

BR

-------------------------------------------------------------------
Eugen Wiebe
Bernstein AG
CLAD - Certified LabView Associate Developer
0 Kudos
Message 6 of 6
(2,881 Views)