Connecting a host APP to a remote RT App

[jotemak]

Problem Description :
We have a real time code that was running on a PCI 7041 RT card. We are in the process of buying a PXI chassis (PXI-1031) with the newer PXI 8184 RT card and porting the code over. It looks like our real time code is running on the newer Chassis and controller when looking thru the debugger but when we issue a "10.0.0.10:3580/dumpinfo?" from a web browser of an ethernet connected PC (host PC) we error out and don't get any mapped port info as we expect. We can see the RT controller in the PXI from MAX as a remote system with the IP address mentioned and can also FTP into it and out of it without a problem. Do we need to do additional configuration in 8184 OS to get "dumpinfo" to work??

When we just type the ip address in the host PC browser as http://10.0.0.10/ we see the running VI of the RT controller and it appears to be running correctly as expected.

We just can't get any information to connect the host App to the RT App by discovering the port by doing a "dumpinfo" as the old one works.

The contents of my NI-RT.ini is attached and it shows that webserver is enabled in the remote RT controller.

Please help...

Thanks

JM

[nathand]

Guessing a bit here since I don't have that hardware to test or duplicate your setup. There might be a software component that you need to install on the RT system. In MAX, find the remote system, right-click the software item to install software. This will give you a list of components that you can install on the RT system. I'm not sure whether the NI Service Locator stands on its own or is part of another package, but I believe that's what you need to install.

[Texas_Diaz]

Port 3580 is a Web Monitoring and Configuration server port, and you need to make sure the Web Monitoring and Configuration software component is installed onto the controller - you can see this from the installed software view in MAX.

-Danny

[jotemak]

Thanks for the reply Danny...

Here is what we did to get ot to work.

The previous LV code was doing the "3580/dumpinfo" from the Windows host app in order to detrmine the port mapping for the purpose of connecting to the RT code running on the 7041 card installed in the same PC running the host app.

Our new configuration is for replacing the 7041with a PXI chassis that is equipped with the 8184 RT controller running the same RT code that was in the 7041, and the link is the same as before which is TCP (physical Ethernet).

The RT code is listening on port 23 and we made a change in the host app code to directly map also port 23 rather than doing a "3580/dumpinfo" to detrmine the mapping. This made it work right away and we are running with that for now.

What is the name of the the "Web Monitoring and Configuration software component is installed onto the controller"?? This is a controller running LV RT 7.1.

Thanks

Jote M

[Texas_Diaz]

---

@jotemak wrote:

The RT code is listening on port 23 and we made a change in the host app code to directly map also port 23 rather than doing a "3580/dumpinfo" to detrmine the mapping. This made it work right away and we are running with that for now.

What is the name of the the "Web Monitoring and Configuration software component is installed onto the controller"?? This is a controller running LV RT 7.1.

---

Watch out about listening on port 23 (Telnet port), if any app ever tries to connect to the RT system via Telnet you're going to receive its traffic (a hazard of choosing an established port). 

Just another fair warning, LabVIEW RT 7.1 is no longer supported by National Instruments.  The "Web Monitoring and Configuration" module - which is what TCP port 3580 is talking to - was not supported until LabVIEW 2010 (also known as LabVIEW / LabVIEW Real-Time 10.0).  And no, unfortunately it's not backward compatible (cannot run under LabVIEW RT 7.1).  With LabVIEW Real-Time 7.1, you're stuck with doing things old-school.

-Danny