Host Engineering Forum
General Category => Do-more CPUs and Do-more Designer Software => Topic started by: davidbgtx on September 14, 2015, 12:17:24 PM
-
Just to be certain before I design another system - I can program the Do-More through an ECOM100 located in the same rack as the Do-More, yes/no?
I believe using the Do-More ethernet port for my remote bases, and then using an ECOM100 for programming from my office and modbus communincations to a sql server database and/or other PLC's , would be best for keeping network traffic low on I/O, is the also the best way to go??
Would you then suggest my C-More, which needs to talk to the Do-More, but also be programmed from my office, be on the remote base network or the programming/modbus network?
-
I use an ECOPM100 for my Cmore comms, you can program through it as well. The ECOM cannot be used for custom TCP protocols though.
-
Just to be certain before I design another system - I can program the Do-More through an ECOM100 located in the same rack as the Do-More, yes/no?
I believe using the Do-More ethernet port for my remote bases, and then using an ECOM100 for programming from my office and modbus communincations to a sql server database and/or other PLC's , would be best for keeping network traffic low on I/O, is the also the best way to go??
Would you then suggest my C-More, which needs to talk to the Do-More, but also be programmed from my office, be on the remote base network or the programming/modbus network?
You can. Older ECOM100s required a firmware update, so if it doesn't seem to be working, make sure it is up to date.
Running I/O with the on-board port and programming/HMI through the ECOM100 is an excellent approach. The on-board port can generally handle both at once, but you tend to get a higher retry frequency on the I/O, which is obviously undesirable, and may even be unacceptable depending on the app. Depending on your overall network use and saturation, the possibility exists of an extreme data storm causing a complete I/O failure...which depending on your I/O setup, could drop the controller into program mode. In a properly managed network the probability is very low, but we always recommend splitting if there is concern or doubt.
-
Thanks to all