Unable to program E10-npn+ via RS485

[BC SYSTEMS]

HI,

I have a T100MD-24 and an E10-npn+.  I'm using the Auto485 to connect and program the T100 with no problems.

I would like to be able to connect both PLC's to the RS485 network and program each one via their associated software (Tri logi for the T100 and wintrilogi for the E10) I'm having trouble connecting to the E10-npn+ via the RS485 connection.

Can the E10 be programmed via the RS485 connection?  I have connected the RS485 + on the auto485 to pin 5 on the E10 and the Rs485 - to pin 2 on the E10.

I have tried swapping the connections and installing a 120ohm resistor in the circuit with no avail.  

I have installed the jumper on the E10 to 485 and left the auto485 in "auto" mode.

Any help greatly appreciated

Marcus

[support]

You should be able to use Auto485 to program the E10 if its jumper is set at the "485" side.

Ensure that the WinTRiLOGI - E10 mode is selected, then check the COM port setting in WinTRiLOGI to make sure that the correct com port and the correct baud rate has been selected.

Have you already connected the Auto485 to both E10 and T100MD+ PLC? How about trying it one at a time to make sure that it can talk one to one first.

[BC SYSTEMS]

Hi,

I have connected the t100 on its own no problems.

when i try to connect the E10 (on its own) i'm unable to communicate i.e change PLC ID.

What serial settings are needed? i'm using the below configuration.

Comm 1

8 data
1 stop
none parity
9600 baud
500ms timeout

Any ideas?

[support]

I just tried using WinTRiLOGI E10 mode to connect to the E10-npn+. I found out that the "Detect ID" don't work in RS485 mode, possibly due to the turnaround delay of Auto485 to catch the Ctrl-E properly.

But when I manually enter the known ID and then I was able to connect to the PLC to perform online monitoring or program transfer using 9600,8,n,1. You may like to give that a try.

[BC SYSTEMS]

Hi,

That works a treat!

 I assume the E10 will work on a multidrop network providing the PLC ID is "known"?

Is this something you guys will rectify or will this be added to the "Known bugs list" for this model?

Thanks for your help

Marcus.

PS

My company also purchased (in the last week or so) the tri excel link software, but unfortunately the CD data format is corrupt / un-readable, so I will be sending it back for replacment.  

I have tried the CD on a couple of PC's so I?m sure it's the CD thats at fault.  Have you had any issues with the software / CD?

[support]

Yes, they are designed to work on a multi-drop network as long as each PLC has a unique ID.

The problem of "IR*" not getting a response on RS485 from E10 may have something to do with the auto-turnaround time delay. I found out that you can still get the ID by entering "IR" (without the '*') and press Enter.  In any case, on a multi-drop network one should avoid using the point-to-point protocol as it will guarantee to disrupt communications between the host and the slave PLCs.