LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

UUTs with identical IP addresses

I would like to be able to communicate with 2 units under test at the same time. The communication is via telnet, and the UUTs are constrained to have the same IP address, say 192.168.1.10.

 

 I normally use the internet toolkit telnet VIs. Is there a way, with separate NICs or anything else, to keep the telnet sessions separate? Thanks.

0 Kudos
Message 1 of 9
(3,448 Views)

Not that  I know of.  Having two devices with the same IP address is a violation of the network.  You are going to have collisions.

 

Why do they have the same IP address?  What are you REALLY trying to do?

Message 2 of 9
(3,416 Views)

There is no way this can work.

0 Kudos
Message 3 of 9
(3,377 Views)

The reason for the duplicate IPs is that the devices have this as their default state used for testing. Perhaps a device in the middle that does some kind of NAT might work? Not a LabVIEW solution per se.

0 Kudos
Message 4 of 9
(3,358 Views)
You don't have access to the UUT setup so that you can assign different addresses?
0 Kudos
Message 5 of 9
(3,291 Views)

@Dennis_Knutson wrote:
You don't have access to the UUT setup so that you can assign different addresses?

This could be product that is at a final functional test, and should be tested using the same settings as it is shipped out with.

 

Still I suggest changing to unique IPs if you can.  If you can't then you'll need some kind of device in the middle which can intercept the data and effectivly change the IP address.

 

Or is it possible to test the UUTs one at a time, where you power on one test, power it down then power on the next?  I think some high end switches can have ports turned on and off and this could be another solution.

0 Kudos
Message 6 of 9
(3,277 Views)
I've done a lot of production testing of units in parallel and never had a problem with changing back to the default when the test was complete. That was, of course, after validating the devices firmware worked.
0 Kudos
Message 7 of 9
(3,269 Views)

We use a "Managed Switch" to control which port we are communicating to.

We have ESS chambers with up to 24 UUT all with the same factory default IP address.

You can find 4 port managed switches for under $100. 

Omar
0 Kudos
Message 8 of 9
(3,264 Views)

@Omar_II wrote:

We use a "Managed Switch" to control which port we are communicating to.

We have ESS chambers with up to 24 UUT all with the same factory default IP address.

You can find 4 port managed switches for under $100. 


But that does not really work with the "parallel" requirement. You can only communicate with one at any given time.

 

NAT should work with a little bit of effort and some hardware (Plain NAT routers can be had very cheap today). Basically you would have NAT routers with different WAN IPs (all on your factory subnet), but the same LAN subnet. You would define the fixed UUT IP on each LAN subnet as the default server in the router and contact each viat the WAN IP of each router. Turn off the router firewall (if present) and LAN DHCP, etc.

This assumes that the devices are relatively well behaved and are NAT compatible. Telnet should work. If the router runs a telnet server for configuration, you would need to make sure it does not interfere.

0 Kudos
Message 9 of 9
(3,229 Views)