DenisOz (Customer) asked a question.
In creating the project at the office, I selected the Micrologix protocol because I felt that they were technically equivalent. Yes, I can connect via DF1 serial, but I have multiple PLC's to communicate with. How could this situation be possible ?? - the SLC may be long in the tooth, but it is the most installed PLC on the planet. The PLC's keep going, but it is the HMI s that need replacing. This job is replacing a locked up Panel View 1000, and I had to sweeten the proposal by providing remote access to the HMI, which is hard to do on a PV. Of course I found this out when on site hundreds of kilometres from the office. Local ADC in Australia offered me an EA9-- but the project has been developed in CM5 and no backwards migration. This has just cost me a lot of $$ and a slap in the face from my advocating for Cmore and ADC. I have used every ADC panel starting with the terrible DV1000, EZ automation and all the Cmores. This is a relationship that started in 1998. Cmon ADC, you have my email, get a revision going before the bad press starts.
The ethernet protocol for AB SLC in the CM5 is EtherNet/IP Client (SLC5/05/ENI Adapter), as it was before.
This driver works with SCL5/05 natively and with other processors with the addition of a NET-ENI adapter, as shown in the manual.
https://cdn.automationdirect.com/static/manuals/cm5userm/ch6.pdf#page=21
If you are referring to DH485 (serial), that protocol is not available in the CM5.
If you have to use DH485 in a C-more, you would need to go with an EA9.
I apologise for my intemperance yesterday - the frustration, and the distance...... In communication with the local ADC consultant, we agreed that the protocol was not supported unless used with an ENI adaptor as suggested in the configuration pull down. I went back to the old Cmore app & indeed it is the same option. So haste makes waste, and a return trip to the client. On closer inspection of the comms error message, I am suffering the PLC-498 error. I will connect up a SLC rack in the shop and mess with the memory boundaries on a test project, but this is puzzling, as I have not encountered this before. I have replaced many SLC HMI installations previously without this issue. Thank you ADC for the prompt reply, and rest assured that I am still a strong advocate for ADC down under. I will report back the solution when I get it sorted.