I own a Schneider M580 Safety PLC (BME P58 4040S) that connects to a remote rack with safe IO using Ethernet IP. Occasionally, upon startup, the PLC seems to freeze. The front Ethernet Ports LEDs on the CPU are solid green instead of flashing as usual, red fault indicators are lit on some IO units, and my laptop cannot establish a connection. Restarting the PLC typically resolves this issue, but it starts up in STOP mode and requires laptop connection to switch to RUN. There are times when it powers up without any problems, indicating it is not a consistent issue. I have already checked the checkboxes for Automatic start in Run and Initialize %MWi on cold start. Has anyone encountered a similar situation or can provide advice on further troubleshooting steps?
User rwatson shared their experience with a Schneider M580 Safety PLC (BME P58 4040S) connected to a remote rack with safe IO via Ethernet IP. At times, upon powering up, the PLC seems to freeze with solid green LEDs on the front Ethernet Ports instead of the usual flashing for link activity, red fault indicators on several IO units, and inability to connect a laptop. This issue can typically be resolved by power cycling, although the PLC starts in STOP mode necessitating a laptop connection to switch to RUN. While the problem doesn't occur consistently, enabling Automatic start in Run and Initialize %MWi on cold start checkboxes hasn't fully addressed it. Seeking advice or similar experiences from other users. It may be helpful to update firmware, as there have been significant updates in the standard range in the past year despite not using the safety range.
Great! I’ll give it a try and see if it makes a difference.
Rwatson enthusiastically agreed, stating "Cheers! I will definitely give that a try and see if it makes a difference." You can find the necessary information at the following link: https://www.se.com/uk/en/product/BMEP584040/processor-module-m580---level-4---remote/. Feel free to reach out if you need any assistance.
To access crucial information, make sure to refer to page 200 in the manual available for download on Schneider Electric's website. Visit the following link: https://download.schneider-electric..._File_Name=QGH46982.05.pdf&p_Doc_Ref=QGH46982.
Comment by rwatson: I own a Schneider M580 Safety PLC (BME P58 4040S) connected to a remote rack via Ethernet IP for safe IO. Occasionally, upon power up, the PLC appears to freeze. The front Ethernet Ports LEDs stay solid green instead of the usual flashing, there are red fault indicators on some IO units, and I cannot connect my laptop. Rebooting typically resolves the issue, but the PLC starts in STOP mode and requires laptop connection to switch to RUN. Sometimes it powers up smoothly, so the problem is intermittent. I have ensured Automatic start in Run and Initialize %MWi on cold start are selected. Has anyone encountered this issue before or have suggestions for troubleshooting? Hello, we are planning to expand IOs in our BME P58 4040S system by adding safety IO racks on Ethernet. Can you provide information on the maximum number of safety IO racks supported on a Node and by this specific safety controller?
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - The PLC freezing upon startup could be due to various reasons such as connection issues, faulty IO units, or configuration settings.
Answer: - The solid green LEDs on the Ethernet Ports of the CPU could indicate a connectivity issue or a communication problem with the remote rack and safe IO units.
Answer: - Red fault indicators on IO units could signify hardware issues or communication errors. Troubleshooting steps may include checking connections, power supply, and configuration settings.
Answer: - The PLC starting up in STOP mode may be a safety feature to prevent unexpected operations after a freeze. Switching to RUN mode via a laptop connection ensures controlled operation.
Answer: - Additional troubleshooting steps may involve checking network connections, firmware updates, verifying configuration settings, and conducting diagnostics to identify the root cause of the inconsistent startup problems.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.