A project on customer site reports a few problem after customer turned the power off/on for the panel. Firmware is 2020.3.1, project is AXC F 2152 version 00/2020.0.0, and the PLCNext Engineer is 2020.3.1. Project files for PLC_A and PLC_B are stored in different folders and haven’t been done any changes.
Issue 1,
After PLC_A is loaded with its project, PLC_A can turn debug on and PLC_B becomes Master. However, PLC_B cannot turn debug on after its project is loaded by PLCNext Engineer.
Now load PLC_B with its project, PLC_B can turn debug on and PLC_A becomes Master. However, PLC_A cannot turn debug on after its project is loaded by PLCNext Engineer.
Thus, the values in Master PLC cannot be monitored by PLCNext Engineer.
We also noted that the PLC_B gets disconnected after some minutes automatically and can’t turn debug on after reconnection.
We have never encountered this behaviour before. What will be the reason?
Issue 2,
We have Tridium Niagara Jace acts as the OPC client. For PLC_A OPC connection, it reports “Invalid sever certificate” and connection is down. For PLC_B OPC connection, the connection is “OK”. We used “UA Expert” as the OPC client and ignored the error, finding out that the current time of sever status of PLC_A matches the computer platform time, while the current time for PLC_B is 11am and the computer platform time is 21pm.
While PLC_B is loaded, its RTC variable shows the computer platform time. It seems that the RTC changes to a time 10 hours difference after PLC_B gets disconnected. Thus the current time of OPC sever changes.
How to solve the OPC connection issue for PLC_A?
What else can change the RTC values?
Thanks
Jason
I assume that you’re using the ASR app from the PLCnext Store - is that correct? If so, which version of the ASR app is installed?
Here are some comments from the developers of the ASR app:
_The function blocks of the ASR library have no influence on online debugging or OPCUA communication. Therefore, in this case, there must be another problem that causes these difficulties. Maybe there is a problem in the Ethernet network that causes these problems.__It is mentioned that two different projects are used for PLC A and PLC B. With the PLCnext ASR library, however, only one project may be used, and it is selected via the communication path in PLCnext Engineer whether you want to communicate with PLC A or PLC B._Please keep in mind that if you switch the communication path between the PLC A and PLC B, a rebuild of the project’s program code is essential. For application-specific issues like this I can recommend getting in touch with either the ASR app developers (using the “Contact Developer” button on the product page in the PLCnext Store), or else the specialists in your local Phoenix Contact office, who may be able to help troubleshoot issues like this.