Programming using a Device Server

[Ben_Whitworth]

Hello

We would like to programme our T100MD 888+ via the RS485 port using a device server (Lantronix UDS-10 IAP).  This allows the PC to connect to the PLC via a LAN.  We can monitor the PLC and receive data from the Excellink Softweare- albeit limitedly - but we cannot programme the PLC at all - TriLogi just locks out.  

Has anyone else had similar problems?? Is the programming protocol identical to the Native link protocol or does it change Baud rate, parity, format etc...

Any help much appreciated

Ben

[support]

I assume Lantronix UDS-10 IAP is an Ethernet to RS485 converter?

You can't use the TRiLOGI client to directly address the the Ethernet port on a converter since TRiLOGI assume the availability of a TLServer with its own proprietary login procedure.

Does the Lantronix UDS-10 IAP support a virtual com port? If ?it does, you can run TLServer and use the virtual com port for communication with the UDS-10 IAP. You will still need to run the TLServer and the TRiLOGI still have to login to the TLServer. The TLServer in turn communicates with the Ethernet converter via the virtual comm port. We have customers who have successfully used the DE-311 Ethernet to RS232 converter (mfg by MOXA) in this manner.

[Ben_Whitworth]

The UDS-10 is a RD485 converter. The Lantronix does use a virtual com port and the monitoring of the PLC is fine and dandy, but the programming has not been possible yet. The Rep from Lantronix said that occasionally PLC's programming language is different to thjat of the normal communication language.  Is this the case??  Could your client who used the MOXA device server programme too??

Cheers for the help.
Ben

[support]

Yes, the customer who used the MOXA had no problem transferring program to the PLC.

If you are able to monitor the PLC, then we don't see why you can't program the PLC since program transfer is also done by the similar communication protocol as the monitoring. Could you describe the error message you get when trying to transfer program? Which stage did the transfer break down?

[Ben_Whitworth]

Tri Logi breaks down when the PC connects with the PLC.  The splashbox that says "Success!" apperars, but then nothing more happens, and that box stays on screen. Am I right in saying that it has prepared the programme for sending it but not sent it yet.  No error message occurs.  The only thing that I did notice is that the device name in that success box normally is along the lines of "Tri logi MD+", but through the device server it comes up with a long list of numbers instead.

Does it matter that it is via 485? If the program is similar - does it still use the same baud rate and parity etc? Is it worth playing with the packing algorithm to force the packets through the converter every time it comes to a termination charecter?

I appreciate all the help
Ben

[support]

When the "Success" message appears, the program has been compiled successfully. But when the TRiLOGI software try to communicate with the PLC (via your virtual com port and UDS-10 IAP) something it receive is not normal and that's why it could not proceed. It doesn't matter if it is RS485 or RS232 since both serial ports can be used for programming.

It is difficult for us to understand what went wrong during the conversion of the ASCII string via virtual com port -> ethernet -> UDS-10 IAP -> RS485 to the PLC.  If you are located in the US and you are willing to send a unit of UDS-10 IAP to us for testing, then we can try to track the communication and see where it fails in order to find a fix around it. You can email to us at support@tri-plc.com to make arrangement. We may need to hold on to the unit for a week or so to test it.