tcp problem

[mf_hussin]

Dear guys,

I'm having a problem with my program.

Can someone guide me in solving the problem, which is I try to send a data via wifi.

My server is using a serial Vi's and my client using a TCP/IP Vi's.

Here, I attach the program and can you guys advixe me on this.

Really urgent need someone helps.

Please guys.

Help me out.

Cheers!

[Tom.]

Hello,

Can you describe what the problem is with your code and in addition what it is trying to achieve exactly.

Cheers

Tom
NIUK

[mf_hussin]

Dear Tom,

The problems that I'm having right now is to interface both programs.

The error that I got is error 63.

The other problem is I couldn't establish the pysical serial interface between this two devices.

Let me briefly explain about my project.

The serial program that we develop will connect with wifi devices called Airbone.

And the TCP program will connected at the another end with Access point or router using RG45 cable.

Then we will interface both of the components.

But by now we unable to do it.

Hope this information enough for you.

Cheers!

Regards,

Hussin

[Ben]

Error 63 is "...refused by ..."

This will occur for any reason that would prevent the server from accepting the coonection.

If the device is busy,

If the port is already open,

etc.

Power cylce your device and try again. Once you get a connection make sure you close it.

That's all I can offer for now.

Ben

[Tom.]

Hello,

I have attached a simple TCP server that generates 2 Waveforms clustered together to port 1409. On your tcp-alex.vi you will need to set the address to 'localhost' and the post to 1409. Make sure you have the TCP/IP VI Server enabled by navigating to Tools > Options > VI Server: Configuration and ensure the TCP/IP checkbox is ticked. Also in VI Server: Machine Access ensure the client IP (in this case the IP of the machine) is allowed.

Post back if you have further trouble. I can't run your server code as I do not have the instruments to interact with the serial VIs.

Good Luck!

Tom
NIUK

[mf_hussin]

Dear Tom,

I couldn't open the VI's because I'm using Labview 8.0.

Can yo repost the program by using 8.0 version.

Hope to get a that VI from you again.

Thanks

[altenbach]

Maybe I am completely misunderstanding what you are doing, but you cannot establish any communication with TCP/IP on one end and serial on the other end. That's like trying to connect a regular phone to a cable TV outlet and expect it to work.

You need a VI that does both and translates between the two protocols if you really need both. Else stick to TCP/IP exclusively for server and client.

[mf_hussin]

Dear Altenbach,

That the major problem of our project. I have thought about that but we already implement our project in such way.

As I already post a few question which explain our project description.

Its ok, let me make a summary why we did that way.

Firstly, we required to measure a voltage then convert that analog signal to digital trough the ADC (analog to digital converter). After that, we send the signal to ERAM (external memory) before transmit through airborne. This airborne is a wifi device and to send a data or signal to the wifi device we using a serial port to connect between that ADC and airborne. This component is installed at the server computer.

At the receiving or client, we using an access point or router (netgear) which using RG 45.

Hope you can guide me in solve this problem.

We could not make both sides TCP as we already purchase these items.

Here I attached the pdf of our devices as your reference.

Cheers!!

 Hussin

[altenbach]

The way I understand this device (maybe I am wrong) is that you need to install the virtual COM driver on the PC, then use serial commands. You should not use TCP/IP. The virtual COM driver will create a vrtual serial port that transparently handles the TCP/IP part. From the viewpoint of the LabVIEW program, it just sees a serial port with a device attached on the other end. The driver will transparently create the communication tunnel th the serial device server.

See http://www.quatech.com/ManualsDriversFirmware/manuals/VCOM_ABSE.pdf

.

[mf_hussin]

Dear Altenbach,

How about the program at the client?

It is ok?

Should I stick with this program and that program works?

Thanks