connecting to labview over TCP/IP port

[Dennis_Knutson]

Bob is asking for the same thing I am. YOU have to provide the information on the LabVIEW application.

[Dennis_Knutson]

To clarify, why do you think your java app is communicating to a LabVIEW app? There isn't any reference to LabVIEW in the java code. It could very well be an app written in any language.

[Bob_Schor]

---

@vikrantl wrote:

Please find copy pasted Java code in the attached file.

I did not find anything like USB-6009, but I know that the end intrumentation device is connected over USB port to the PC, there is an installable file CONF-6009OEM2.NCE

The user is expected to install NIDAQ980f0.exe before installing the Java application.

Thanks BS & all.

-Vikrant

---

NIDAQ is NI's Data Acquisition package, usually installed as part of a full LabVIEW installation to handle communication with data acquisition devices.  It works with NI's Measurement and Automation Explorer (MAX), which "knows" how to talk to specific hardware.  Indeed, the .nce file format is one that MAX uses to configure itself for specific devices.

I'd suggest you go on NI's site and look for and download their Device Driver DVD, and run it to get at least MAX running.  I'm assuming (but have never tested this) that you can install NI drivers without having LabVIEW itself installed.  If so, see if MAX can import your CONF-6009OEM2 file (hey, that looks like it might be related to the USB 6009, which definitely does not use TCP/IP ...).

Bob Schor

[Bob_Schor]

---

@vikrantl wrote:

The user is expected to install NIDAQ980f0.exe before installing the Java application.

-Vikrant

---

I should have mentioned that I believe the version of NI-DAQmx installed with LabVIEW 2013 is 9.8.0f0.  As far as I know, it is not an executable (at least I find no .exe file starting with NIDAQ on my LabVIEW machine).

BS

[Dennis_Knutson]

The exe is the installer for the DAQmx driver and since the driver installation is completely separate from any LabVIEW installation, it's actually irrelevant to the poster's question. The other program could be another java app as far as we know.