Deeps

Hi

By looking the at Flashing Status of all 4LED's it seems that the Module is Faulty.

Before concluding I would like to suggest you can try to Update the Firmware & reconfigure the module .

You can download the latest Firmware updates from following link ,

https://support.automation.siemens.com/WW/livelink.exe/24463869?func=ll&objId=24463869&objAction=csView&nodeid0=10805045&lang=en&siteid=cseus&aktprim=0&extranet=standard&viewreg=WW&load=content&csQuery0=CP343-1%20Lean%20%20Firmware%20&subtype=130000

Darius

Deeps wrote:

Hi

By looking the at Flashing Status of all 4LED's it seems that the Module is Faulty.

Before concluding I would like to suggest you can try to Update the Firmware & reconfigure the module .

You can download the latest Firmware updates from following link ,

https://support.automation.siemens.com/WW/livelink.exe/24463869?func=ll&objId=24463869&objAction=csView&nodeid0=10805045&lang=en&siteid=cseus&aktprim=0&extranet=standard&viewreg=WW&load=content&csQuery0=CP343-1%20Lean%20%20Firmware%20&subtype=130000

Hi,

I'm just curious, but why everyone suggest to update firmware IF SOMETHING GOES WRONG WITH THE MODULE ? New firmware can bring you new features and some bugfixes, but even with the oldest firmware device should work. Everyone knows that. So I think it is better idea to look at diagnostic buffer. And if you find that module is defected then no firmware upgrade will help you.

I had a different but similar experience last year.System would run for a few hours, but then it would fault. It was my CPU317PN/DP that had all LEDS flashing. I had a WinCC station, (not Flex). I tried all the firmware updates, as suggested by the tech support people, etc. No change. The Diagnostic buffer said the CPU went into Stop with Defective:Internal System Error and a no relevance for user (Z1):xxxx code.I even got a new CPU under warranty becauseof the "Defect". No change.Get the diag buffer (save as text file)from your CPU and CP card and see what they say.

In the end I found out just by accident that I had a bad WinCC tag address.A typopointed the tag to an address in a DB beyond the DB size. My graphics designer had logged in remotely to the WinCC station and made an edit, making the typo. When that screen or whatever element it was got activated, bang, the system would STOP with a Defect code. I had teams of people looking at firmware and all kinds of things, swearing that there was no way that something as dumb as an out of bounds address pointer couldpossibly be the case, but after I fixed the rogue address, no more problems. So check your tag database very carefully.