Please help me interface a Cmore micro to the do more

[AustinT]

Hello,

   I have tried for a few hours to connect a c more micro to a do more and am not having success.   I have used the C more with other plc's with success .   This is my first time to try the do More PLC.   
I am using the H2-DM1E with a serial cable between the CPU and PORT 2 on the C more.  The config in the do more is set to MODBUS RTU Slave, 9600,8,n,1,unconditional, follows transmitter.

The c more is a EA3-T6CL  9600,8,n,1 station 1, RS 485 -no, timeout --40 , port time 0, memory version 1. 

I am getting receives on the do more but its not talking back

Thanks

[Mike Nash]

This works for me.

[BobO]

The H2-DM1E's port is RS232...not RS485.

[AustinT]

The H2-DM1E's port is RS232...not RS485.

Thank you both for the quick reply.  I probably was not very clear when I wrote " RS 485 -no"
I am using 232.   Can you think of anything else I could be missing ?


Thanks

[AustinT]

Thank You Mike Nash,

It was the Do-More programming selection that I was missing.   In one of the automation direct videos they used the RTU slave so I always just left it on that setting.   It is working great now.

Its nice to have a forum that has good quick responses.  Thank you all

[BobO]

Thank You Mike Nash,

It was the Do-More programming selection that I was missing.   In one of the automation direct videos they used the RTU slave so I always just left it on that setting.   It is working great now.

Its nice to have a forum that has good quick responses.  Thank you all

Sorry, I know next to nothing about C-more. Glad it's working though! Ask something about Do-more and I have a decent chance of knowing the answer.

[AustinT]

Thanks BobO
I will take you up on that

[Controls Guy]

Wait, if the C-More was set to talk to a Modbus/RTU slave, why would the Do-More port config want to be set as a programming port and not a Modbus slave?

Or was the C-More set for Do-More protocol and the Do-More was on Modbus/RTU?

[franji1]

Wait, if the C-More was set to talk to a Modbus/RTU slave, why would the Do-More port config want to be set as a programming port and not a Modbus slave?

Or was the C-More set for Do-More protocol and the Do-More was on Modbus/RTU?

It shouldn't.  However, at the initial release of Do-more back a few years (Do-more shipped in 2012), C-more did not yet have a Do-more driver, so you had to use either a Modbus driver or a DL driver.  Hence, there are probably some old videos/web pages out there that show "here's how to connect a C-more to the new Do-more PLC", with it showing Modbus/RTU as the "driver".  C-more has had a Do-more driver for a number of years now, so the legacy DL and Modbus mechanisms are no longer required (although you COULD still use the Modbus or DL serial driver if your C-more masters on a 485 with multi-drops to legacy DL PLCs XOR Modbus/RTU slaves along with a Do-more PLC).

[Controls Guy]

However, at the initial release of Do-more back a few years (Do-more shipped in 2012), C-more did not yet have a Do-more driver, so you had to use either a Modbus driver or a DL driver.  Hence, there are probably some old videos/web pages out there that show "here's how to connect a C-more to the new Do-more PLC", with it showing Modbus/RTU as the "driver".  C-more has had a Do-more driver for a number of years now, so the legacy DL and Modbus mechanisms are no longer required (although you COULD still use the Modbus or DL serial driver if your C-more masters on a 485 with multi-drops to legacy DL PLCs XOR Modbus/RTU slaves along with a Do-more PLC).

Ah, got it.   I tend to like to use Modbus as my comms protocol regardless of whose PLC and HMI I'm using, even if they're the same brand, because it modularizes the app.  EVERYBODY talks Modbus -- Even AB, the last holdout, finally caved and supports it on many of their PLC's and HMI's.  If I do the app again and one of the components isn't available or I no longer want to use it, I can easily swap it out with minimal impact on the other black box.  I assumed that was what he was doing.