theDave2
Member
We've got a CLX L35E (v16.3)sending/receiving data to a MicroLogix 1400, via MSG instruction over ethernet. We read then write data every second.
We are using CIP communication method with SLC Typed Reads and Writes, to N100 in the ML1400.
What we see is that when we turn power off the ML1400 and then back on, the MSG block takes 7 minutes to recover and communicate again.
The MSG block does give the ER bit and error code for comm time out. We allow 10 seconds after the ER bit before we try again. We don't keep the MSG block energized all the time when reading/writing as we just look for the DN or ER bit to be set as it's sequential stepping logic for the code.
Any thoughts ? Should we be using CIP w/source id ? If so, where is that explained ? How about keeping power flow into the MSG block until we see the DN or ER bit ?
Thanks,
Dave
We are using CIP communication method with SLC Typed Reads and Writes, to N100 in the ML1400.
What we see is that when we turn power off the ML1400 and then back on, the MSG block takes 7 minutes to recover and communicate again.
The MSG block does give the ER bit and error code for comm time out. We allow 10 seconds after the ER bit before we try again. We don't keep the MSG block energized all the time when reading/writing as we just look for the DN or ER bit to be set as it's sequential stepping logic for the code.
Any thoughts ? Should we be using CIP w/source id ? If so, where is that explained ? How about keeping power flow into the MSG block until we see the DN or ER bit ?
Thanks,
Dave