Ask our Experts
Didn't find what you are looking for? Ask our experts!
Launch of Consumer/Home Owner registration process! We are pleased to announce the commencement of the Consumer/Home Owner Registration Process on Community. Consumers/Home Owners may now proceed to register by clicking on Login/Register. The process is straightforward and designed to be completed in just a few steps.
A forum for topics related to the scope of Modicon PAC offers and ecosystem along the whole lifecycle: Modicon M580 and 340, EcoStruxure Control Expert, EcoStruxure Process Expert (Unity Pro) and more.
Search in
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-12-13 09:01 AM
Hello everyone, The processor M340 ( P341000) Is showing a steady (not blinking) error light. And the display on the HMi Is UNABLE TO OPEN CONNECTION TO THE PLC (M340) please what could be the cause and solution to the problem.. Kindly help me out. Thanks
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2023-12-17 10:13 AM . Last Modified: 2023-12-19 08:06 PM
It will need a power cycle to wake it up again. It should boot from the SD card. Then go online to the CPU with Unity/ECE and go into Help->About->Technical Support and use this to generate tech support files to send to SE. This will grab online crash diagnostics to send to SE to help them identify what went wrong.
My experience of this state in the past has been an internal system error. I have seen it several times, most of which came back to FW errors in the early days of the M340. Here are a couple of the specific ones I remember (7 or more years ago):
1. Firmware issue on the ethernet driver of the CPU. After 480days of uptime, a counter in the Ethernet driver over-ran and crashed. This was subsequently identified across multiple products and FW updates released to resolve. This was back in 2015. Long since fixed in subsequent FW.
2. A procedural issue with use of %S94 and %S66 for snap shotting the state RAM and backup program to SD card, which could coincide with internal program integrity check. There was no FW fix released for this, but SE specified a revised procedure. No issues since.
There have been one or maybe two others since then that SE were never able to identify, but pretty uncommon.
Link copied. Please paste this link to share this article on your social media post.
You’ve reached the end of your document
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.