serial COM Port to TCPIP

Omar_II · ‎07-21-2015

@rsmrostov wrote:

Also, Omar, the overhead seems to be quite big in such a set-up, unfortunetly.

We have to test the auto sync of the ports. We can command the NetGear to change it's port speeds to see if the UUT auto sync.

Omar

Dennis_Knutson · ‎07-21-2015

I don't see where this is a LabVIEW problem. If this proprietary driver converts the USB port to a serial connection, then it is this driver that needs to convert it to TCP/IP connection with a specific IP. There is nothing in LabVIEW that can make it an Ethernet port. Contact the vendor of the driver. Perhaps you need additional hardware in the loop to convert a serial connection to Ethernet TCP/IP

rsmrostov · ‎07-21-2015

It is NOT a labview problem, however, I am using labview to make this work as one of the pieces. What I am looking for is a reliable way of getting this to work: like hey, use this virtual driver it doesn't have much of a problem (as I had used some and they do), or hey we accomplish this with a managed Switch, or hey, we use a usb-to-Ethernet nick card with a fixed IP. Labview (G) was put into place to help us test stuff, no?

nathand · ‎07-21-2015

@rsmrostov wrote:

there's a proprietary driver that picks this up as the COM port, this part works like a charm. It's converting this serial COM-port to a TCP/IP and locking a COM port to an IP that is troubling me.

Are you sure that this adapter is going to TCP/IP? As Dennis mentioned, your adapter has an RJ-45 connector, but it's not using that cable to carry ethernet traffic. It's just putting the serial port lines on the pins of the RJ-45. If your UUT expects to be plugged into an ethernet network, and you're instead plugging it into a serial port that happens to use the same physical connector, then of course this won't work.

rsmrostov · ‎07-21-2015

Clearly, I understand this. What I am looking for is another layer, that would turn the RJ45 Serial Connection into RJ45 TCPIP connection. Something like TCP-COM software, but it seems to be hogging the COM port, while creating a TCP/IP layer and I can't communicate via lv.

nathand · ‎07-21-2015

I don't think you understand this, because the setup you have described does not match the equipment you have mentioned. You will NEVER run TCP-IP, nor ethernet, over that TRIPP-LITE extender - it is purely for USB. You wrote that you have a USB-to-ethernet adapter. Did you mean the TRIPP-LITE extender? That is simply a USB extender, no conversion to ethernet.

Does your device speak TCP-IP or serial? Where is the USB-to-serial adapter, and what model is it? Is it integrated into the DUT? What can you tell us about the DUT?

You wrote that one component of your chain is "usb->ethernet adapter (this creates a com-port)". This isn't correct. Either you have a USB->serial adapter that creates a COM port, or you have a USB ethernet adapter, but it is definitely not both. What device is this? Again, the TRIPP-LITE extender is neither of these options.

rsmrostov · ‎07-21-2015

Re: serial COM Port to TCPIP

‎07-21-2015 12:57 PM

I don't think you understand this, because the setup you have described does not match the equipment you have mentioned. You will NEVER run TCP-IP, nor Ethernet, over that TRIPP-LITE extender - it is purely for USB. You wrote that you have a USB-to-Ethernet adapter. Did you mean the TRIPP-LITE extender?

yes

That is simply a USB extender, no conversion to Ethernet. - obviously

Does your device speak TCP-IP or serial? -TCP-IP

Where is the USB-to-serial adapter, and what model is it? non, there's a driver that comes with the device, that must let you talk to TCP/IP

Is it integrated into the DUT? - most likely, not sure to be honest, as I am helping out one of the guys who plain just doesn't know.

What can you tell us about the DUT? - Linux based device, has a fixed IP

nathand · ‎07-21-2015

@rsmrostov wrote:

‎You wrote that you have a USB-to-Ethernet adapter. Did you mean the TRIPP-LITE extender?

yes

That is simply a USB extender, no conversion to Ethernet. - obviously

Then why did you describe it as a USB-to-ethernet adapter?

rsmrostov wrote:

Does your device speak TCP-IP or serial? -TCP-IP

Where is the USB-to-serial adapter, and what model is it? non, there's a driver that comes with the device, that must let you talk to TCP/IP

Is it integrated into the DUT? - most likely, not sure to be honest, as I am helping out one of the guys who plain just doesn't know.

What can you tell us about the DUT? - Linux based device, has a fixed IP

You showed us a screenshot of MAX, listing several COM ports. So, those COM ports somehow exist on your system. You also said that only one of them is connected to the DUT. If this is true, then the COM port must be created outside of the device (for example, a USB-to-serial adapter). However, if the device doesn't use serial communications, then it doesn't make any sense to have a USB-to-serial adapter at all, because there's no easy way to run TCP over serial.

It sounds like you need to do some research on exactly how your DUT works, what types of connections it offers, and what protocol it uses. If you absolutely need to connect to multiple devices, each of which have the same IP address, I would recommend that you get a bunch of cheap home NAT (network address translation) devices, often seen as a home/office router (allows you to connect multiple computers to a single internet connection). Assign each one a unique IP address within the same subnet, plug them all into an ethernet hub or switch, and plug one DUT into each router. Configure the router's internet address to match the subnet of the DUT, and set each router to route all incoming connections to the IP of the DUT.