Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

i/o access error

Created by: newman at: 2/18/2012 6:09 PM (2 Replies)

Rating (0)

Thanks 2

3 Entries

2/18/2012 6:09 PM	Rate (0)
newman Posts: 22 Rating: (0)	hi for plc s7 400 cpu 414-dp via cp417 which communicated with i/o via profibus protocol this error occured I/O access error during update of the process image , and called ob85 diagnostic buffer dp station number error changing for each error i will check the cable and socket , but how to configure ob85 to cancel this error for few second, especially this error occured just for part of second causing production line stop best regards
newman Posts: 22 Rating: (0)
Suggestion To thank Quote Answer

2/19/2012 5:45 AM	Rate (0)
Magica Posts: 35 Rating: (0)	Hello newman, In order to avoid the production line stop,you could insert one newOB named OB85 in your project in the Simatic manger,and download it into the 400 PLC,you don't need to configure any procedures in the OB 85. But as for the I/O access error,you need the OB122 not the OB85,just create a new OB named OB122,and downed it into the CPU,then the CPU won't stop as a result of the I/O access error. Best regards, Magica.
Magica Posts: 35 Rating: (0)
Suggestion To thank Quote Answer

2/20/2012 2:08 AM	Rate (0)
fritz Diamond Expert Joined: 10/7/2005 Last visit: 11/13/2024 Posts: 3027 Rating: (1057)	newman ... but how to configure ob85 to cancel this error for few second, especially this error occured just for part of second causing production line stop Hello newman Even though the error OB's willprohibit the CPU from going to stop mode, they are a reaction to a problemandwill not (can not) be used to "mask" the underlying problem. If and when you loose a DPSlave, the CPU will notice this and substituteall input values with zero (as well as calling the appropiate error OB's), which is most likely the reason that your program will stop production. You may not realise it, but you actuallywantthis production stop to happen, as you do NOT havehave the correct input status anymore which- if masking were possible -can lead to dangerous and/or uncontrollable program behaviour. The only advise I can as such give you is tofind out why your DP Slaves drop out and fix that root problem. Reasons could be manifold (e.g. power supply problems, poor Profibus cable termination, interference etc. etc.)and a tool like Procentec's Profitrace2 and/or COMbricks willhelp you with the analysis of theProfibus. I hope this helps
	Cheers fritz The advice and opinion given in this thread is that of the author and does not necessarily reflect the views of I S Systems Pty Limited. To find out how I S Systems can help you with your automation needs please visit www.issystems.com.au.
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users H-H AurinoP

|

Share this page:

Share this page on...

Follow us on