Skip navigation

community

Up to Discussions in Development Tools and Solutions
493 Views 1 Reply Latest reply: Sep 23, 2011 6:15 PM by DAB RSS
dhautekeete PremierFarnell
dhautekeete
1
Currently Being Moderated

Sep 23, 2011 8:10 AM

Communication issues S2E-module

Hello,

 

Could someone please help me forward with the problem below?  It concerns the

TEXAS INSTRUMENTS - MDL-S2E - MODULE, SERIAL TO ETHERNET

 

http://be.farnell.com/texas-instruments/mdl-s2e/module-serial-to-ethernet/dp/1712294?Ntt=1712294

 

 

A customer uses this device in the following installation:

The installation is built around a PC-application, running on Windows 7 and is connected to the network with 2 units each carrying a S2E-module.  After building the units, they are tested functionally, using a Windows-XP machine with HyperTerminal and appointing the IP-addresses automatically (port 26 on the network).

The company installing the devices in the field, re-appoints the IP-addresses using the 'fixed address' protocol (instead of the auto-selection of an IP-address), appointing one device to 192.168.30.10 port 26 (serial port 1) and the other to 192.168.30.11 port 27 (serial port 1). After that all communication is lost and the MDL-S2E devices cannot be used anymore.

 

The settings sheet gives the choice to either select the IP-addres automatically or by fixed appointment, entering the address and port of choice manually.  This last method stops all communication with the device.


Remark: in the past a batch of these modules were used under the Luminary Micro brand and the same method was used.  No problems were reported then.  The last batch was Texas Instruments brand and almost the whole 50pcs batch failed when installing in the field.

 

Kind regards,

 

Dimitri

Attributes
Tags: s2e-module, communication_module
  • DAB Level 8
    DAB
    Currently Being Moderated
    1. Sep 23, 2011 6:15 PM (in response to dhautekeete)
    Re: Communication issues S2E-module

    Hi Dimitri,

     

    It looks like you might have a couple of problems.

    First, you need to verify that the TI parts have the same capability as the earlier units.

    Second, you need to verify that the protocol is the same as the earlier units.

     

    I have seen components from different vendors react quite differently once installed.  Spec sheets may claim they are the same, but there are always subtle differences that you need to check and verify.  You might want to set up a test stand and look at how the older units work with the software driver and then plug in a new unit to see what is different.  Then you might have some idea as to why they do not work as advertised.

     

    First though, I would call the vendor and make them do the tests.  If they were supposed to be the same, it is their problem to make them work.

     

    Just an thought,

    DAB

Related Content


Related Products
Discussions
  • Retrieving data ...

Bookmarked By (0)

Legend

  • Correct Answers - 50 points
  • Helpful Answers - 25 points