Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Event ID 16# 494D STOP caused by I/O error

Created by: Lalit upadhyay at: 12/7/2015 9:22 PM (4 Replies)

Rating (1)

Thanks 1

5 Entries

12/7/2015 9:22 PM	Rate (0)
Lalit upadhyay Posts: 21 Rating: (0)	Hello Expert's , I am Facing a Problem as below diagnostic buffer log's .I have change the rack, clearing for my doubt but problem not solved .Please help me out. Attachment Diagnostic buffer.txt (862 Downloads)
Lalit upadhyay Posts: 21 Rating: (0)	Last edited by: Lalit upadhyay at: 12/7/2015 9:23:53 PM Last edited by: Min_Moderator at: 12/8/2015 11:50:38 AM Upload Diagnistic buffer
Suggestion To thank Quote Answer

12/8/2015 7:25 AM	Rate (0)
UMENCHO Diamond Member Joined: 3/21/2006 Last visit: 11/1/2024 Posts: 10229 Rating: (1181)	Hello, Almost the same issue has been discussed a few times here in forum. Did you check all the suggestions? Please use search for ' Event ID 16# 494D'. Best regards, Hristo Mihalev

Suggestion To thank Quote Answer

12/8/2015 10:43 AM	Rate (0)
mopS04 Platinum Expert Joined: 3/5/2014 Last visit: 8/5/2022 Posts: 5521 Rating: (1054)	hi, like UMENCHO said, see allt the other threads about this Error. But the best would be, contact Siemens by starting a Support Request. They could give you more information on this error: Event 23 of 28: Event ID 16# 494D STOP caused by I/O error No relevance for user (Z1): 9182 No relevance for user (Z2): 0060 (Z3): 0367 Previous operating mode: STOP (internal) Requested operating mode: STOP (internal) External error, Incoming event 12:00:03.411 AM 01/01/1994 The can read more information out of Z1/Z2/Z3. hope this helps, regards,
	FCK WAR! Be nice!
Suggestion To thank Quote Answer

12/8/2015 3:04 PM	Rate (1)
Towome Platinum Expert Joined: 7/9/2015 Last visit: 11/15/2024 Posts: 4027 Rating: (603)	Hi, such problem could caused by a firmware problem. I saw you have and older FW. I would update to Version 5.3.5 and check again. Please look here: https://support.industry.siemens.com/cs/de/en/view/109474827 Regards, Towome
	If my post was useful, please rate me - if not, please tell me - thank you!
Suggestion To thank Quote Answer

1/5/2021 4:31 PM	Rate (0)
S.Veselinov Advanced Member Joined: 2/17/2012 Last visit: 10/22/2024 Posts: 21 Rating: (0)	Hello, We had exactly the same problem - there was a defective module and for some reason it made the PLC go in stop mode. The solution was to disconnect all the modules and then start just the PLC (if it is ok and you have downloaded all the necessary diagnostic OBs it should go in run mode). Then start putting the modules one by one. This procedure should tell you which is the defective module. I am not sure why the PLC cannot diagnose the problem, maybe it has something to do with the backplane bus. Regards

Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users Towome

|

Share this page:

Share this page on...

Follow us on