Subject: Urgent Communication Issue Between Cimplicity 6.0 and Schneider M340 PLC Hello everyone, I am currently experiencing a communication challenge between Cimplicity 6.0 and the Schneider M340 PLC. To provide clarity on the issue, I will detail the steps and problems encountered. Initially, we had a running machine controlled by the Schneider Premium PLC with Cimplicity SCADA 6. The communication between the Premium PLC and Cimplicity 6 was established through the Schneider OPC Factory Server (OFS) 2.2 and the XIP driver. Now, the client has opted to upgrade the PLC from the Premium model to the Schneider M340 while keeping the Cimplicity SCADA unchanged. On site, we have successfully replaced the Premium PLC with the M340 and have adjusted the wiring accordingly. I can successfully ping the M340 PLC from the SCADA PC, and the Cimplicity TCP/IP diagnostic tool allows me to read and write registers to the M340 PLC. In the OFS, I have defined an alias for the M340 along with its corresponding IP address. However, I am facing an issue as I am unable to view the PLC values in the point control panel. Additionally, the OFS status window displays an error: "Error creating item M340!%MWXX". Moreover, the Cimplicity log file indicates that while the Cimplicity client connects to the OFS server, it encounters an error: COR_DCRP_ERR (20016) AddItemListToServer. I would also like to highlight that importing Unity variables into OFS is not possible since there is no dedicated option for Unity. I have attempted direct TCP/IP communication, but that has also been unsuccessful. When defining the port in Cimplicity, I only see options for the Modicon 184 to Quantum series and not the M340 PLC. We are currently facing machine downtime, and I need to resolve this issue as soon as possible. If anyone has insights or solutions that could help me overcome this challenge, I would greatly appreciate your assistance. Thank you!
Your concern might be related to the way you are using addressing. I recommend trying 401234 in place of the complex format such as %MW1234%I1234 - 101234%M1234 - 1234%IW1234 - 301234. Additionally, it’s important to note that the M340 controller utilizes tag-based addressing, in contrast to the older processors that relied on traditional Modbus addresses. To ensure your I/O functions properly, you will need to map your existing Modbus addresses to the new tag names. This adjustment will enhance compatibility and improve performance.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.