Daily Error: IO station failure- /> HW_ID= 272 ........ Event ID 16#02:39CB

0_Einstein

PetePinetown

Hi Siemens Clever Guys

This is my first post, go easy on me.

Ive got a S7-1200 PLC that goes into stop every few weeks. The Description in the Diagnostic buffer is:

Error: IO station failure- /> HW_ID= 272 ........ Event ID 16#02:39CB

I can't find documentation that shows me what actions to take for this event ID.

Any Ideas???

Have you looked in your system constants in the tag table to find the constant associated with that HW_ID? Convert the 272 to hex if your HW_IDs are not displayed in decimal. That will tell you what hardware has faulted.

Depending on what it is, you can correct the problem, or in your logic insert a fault handler that detects this problem and handles it gracefully.

If this is mission critical or safety, you may choose to let it fault and stop the plc. If however you can handle the error, look at the Hardware Interrupt OB and how to detect and handle hardware faults like this.

It might be as simple as forcing a cycle stop, displaying the hardware fault on the HMI, and maybe make some alarm noise or blinker.

 Dear 0_Einstein,

I have same problem every day. Part of the system where this error occurs contains two IM151-6 modules, 3 Sick encoders and 1 AMS laser distance sensor. In some moment one of 3 Sick encoders goes in error state and in next 20 seconds all of them have same error: IO device failure - RPC application timeout.

The problem is that we cannot work with the machine until we solve the communication with the encoders. That's why we have to turn off/on the PLC every time so that the network and communication with the encoders is stable.

Hope you can give me some hint!

Thank you in advance!

------------------------------------------------------------------------------------------
Split from S7 1200 Error: IO station failure- /> HW_ID= 272 ........ Event ID 16#02:39CB.

Hello,

not easy to say exactly. generally is expecetd for first check your Encoder specification if you don't work with some not allowed settings or proccess performance. There is also clear requirements what exactly PN cable is required and other things. Without to say that all is ok and set as technical-interface specifications shows, is simply only guess. Look at your situation, only that 3 encoders have problems looks like what other procedures you do inside program? Any special steps, blocks? Provide more clear informations.

Thank you for your answer.

Duris_I

Hello,

not easy to say exactly. generally is expecetd for first check your Encoder specification if you don't work with some not allowed settings or proccess performance. There is also clear requirements what exactly PN cable is required and other things. Without to say that all is ok and set as technical-interface specifications shows, is simply only guess. Look at your situation, only that 3 encoders have problems looks like what other procedures you do inside program? Any special steps, blocks? Provide more clear informations.

Hello,

no, not helpful exactly because specific block is used here and you also have not shared Online values to see, maybe some where is the problem. I expect you need pay attention to CPU's Diagnostic buffer in Online mode to check history and you can maybe find there reasons with events listed. basically, that Company what did this project is expecetd to call and check but it's up to you if you don't have responsible person for that. To me, it looks like some program error with access to that encoders in specific situation that isn't handled by PLC code.

 Dear Duris_I,

I changed watchdog time from 6ms to 20ms for each encoder and it looks like problem is gone. Already working for few days while before we worked without this error for maximum 1 hour.

I hope this will be solution.

Thank you for your help!

Duris_I

Hello,

no, not helpful exactly because specific block is used here and you also have not shared Online values to see, maybe some where is the problem. I expect you need pay attention to CPU's Diagnostic buffer in Online mode to check history and you can maybe find there reasons with events listed. basically, that Company what did this project is expecetd to call and check but it's up to you if you don't have responsible person for that. To me, it looks like some program error with access to that encoders in specific situation that isn't handled by PLC code.

Hello,

yes, this can be easy general solution but to me is strange that you've all things ok before and after some time it started do some problems. I expect only that something was changed inside PLC or code. Something simply prolongs some system monitoring, only my opinion to your situation.