
bgirouard (Customer) asked a question.
I am Running C-More V9.02 and Do-More Designer 2.11.2. I consistently get a PLC-001 Comm. Timeout on the CM5 via ethernet connection DX-DM1E-10ED13-D. I have the PLC's IP address set to 192.168.0.20, CM5 address 192.168.0.22, both subnet masks set to 255.255.255.0, no gateway and no DNS entries (Only these two products and my PC with 192.168.0.10 address are connected to each other).
I ran the PLC inquiry on CM5 which is able to ping the PLC, but it fails all four protocol tests. On the CM5, I've tried both Do-More Ethernet Symbolic Addressing (Full Memory) protocol as well as Do-More Ethernet (built-in memory only) protocol, with the same results.
I'm able to connect to both BRX and CM5 for software downloads and reading status updates using the same ethernet connection. I've done a similar installation in recent months using the Built-in Memory protocol with no issues. The only difference between this instance and that previous instance was C-More software version 8.26.
Side note: Am I able to upload older firmware (e.g., open C-More Ver. 8.26 and update firmware to that version)?
Thanks in advance for any help/insight!
A couple of thoughts, at least until tech support can resolve the problem. Are there any tags in the HMI that point to PLC addresses that are not valid? Does the HMI memory usage or resource monitor show anything out of the ordinary? Does the timeout also occur if you have the HMI connected to the PLC using a serial port (if able to program and connect using serial)? Does timeout occur with just HMI connected to PLC (not using Ethernet switch and PC connected)? Does lengthening Ethernet timeout times, or changing poll time, effect the timeout errors?
Thanks for your response!
I just got my configuration to work.
I somehow had Disable Unencrypted Programming checked in the Internal Ethernet Port Security section selected. When I unchecked this, it all started working!
Now off to tweaking the HMI code!
Good Find! I did not think of this one. Thank you for sharing the solution. Good to know for next time.
"Now off to tweaking the HMI code!" Have fun!