Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

S7-300 CPU317F-2DP

Created by: Survive at: 12/11/2008 9:18 AM (2 Replies)

Rating (0)

Thanks 0

3 Entries

12/11/2008 9:18 AM	Rate (0)
Survive Posts: 26 Rating: (0)	Hi, I have a PLC configuration with CPU 317F-2DP and ET200S Safety IM151-HF(four 4/8F-DI and three 4F-DO) in Profibus, but I am having trouble with them. Some times the SF led of allsafety modules flashes (red light), only with a restart of the CPU (Stop to Run) the problem desappear temporally.The SF led of CPU remains on permanently(red light)and a restart od CPU does not take effect, see the diagnostic of CPU is showed below. Itried to find the addresses 503, 504, 505and 514 but I did not have success. If you need more details to help, please tell me. Please, I need help to find the cause of this problem ! regards, Merry Christmas for all ! ---------------------- Diagnostic buffer of module CPU 317F-2 DP Order No./ Description Component Version 6ES7 317-6FF03-0AB0 Hardware 2 - - - Firmware V 2.6.0 Boot Loader Firmware expansion A 10.13.9 Rack: 0 Slot: 2 Event 1 of 10: Event ID 16# 2522 Area length error when reading Global DB, bit access, Access address: 514 Requested OB: Programming error OB (OB121) Priority class: 1 Internal error, Incoming event 07:14:54.382 PM 04/13/1994 Event 2 of 10: Event ID 16# 2522 Area length error when reading Global DB, bit access, Access address: 514 Requested OB: Programming error OB (OB121) Priority class: 1 Internal error, Incoming event 07:14:54.382 PM 04/13/1994 Event 3 of 10: Event ID 16# 2523 Area length error when writing Global DB, bit access, Access address: 514 Requested OB: Programming error OB (OB121) Priority class: 1 Internal error, Incoming event 07:14:54.382 PM 04/13/1994 Event 4 of 10: Event ID 16# 2522 Area length error when reading Global DB, bit access, Access address: 514 Requested OB: Programming error OB (OB121) Priority class: 1 Internal error, Incoming event 07:14:54.382 PM 04/13/1994 Event 5 of 10: Event ID 16# 2523 Area length error when writing Global DB, byte access, Access address: 505 Requested OB: Programming error OB (OB121) Priority class: 1 Internal error, Incoming event 07:14:54.382 PM 04/13/1994 Event 6 of 10: Event ID 16# 2523 Area length error when writing Global DB, byte access, Access address: 504 Requested OB: Programming error OB (OB121) Priority class: 1 Internal error, Incoming event 07:14:54.382 PM 04/13/1994 Event 7 of 10: Event ID 16# 2523 Area length error when writing Global DB, byte access, Access address: 503 Requested OB: Programming error OB (OB121) Priority class: 1
Survive Posts: 26 Rating: (0)
Suggestion To thank Quote Answer

12/12/2008 8:15 PM	Rate (0)
jklm Platinum Member Joined: 12/22/2006 Last visit: 1/25/2022 Posts: 1742 Rating: (308)	Hello, I would check the points below in the following order: - be sure you have the latest F-configuration Pack (can be downloaded for free at http://support.automation.siemens.com/WW/view/en/15208817) - be sure the Profisafe Addresses set by Dip switches on the modules match with the adresses in the tab with failsafe parmeters of each of the modules - be sure the monitoring time in the same tab is not set too low. You can compute this time using the excell sheet named cotia.xls (can be downloaded on the support site at http://support.automation.siemens.com/WW/view/en/25412441). The value depends among other things on the frequency of the safety prgram(OB35if tyou call your F-Call there)and the typical rotation time. Just for testing, you could try with 1000 msec. Afterwards you will have to set it to the correct values. - be sure to deactivate in HWconfig the channels that arenot used on themodules. - be sure that you have compiled the hardware, and download it. Than compile the safety program and download it. You must do this for each setting in HWconfig that affects the safety parameters. I hope this helps.
	Best regards jklm Suggestion was helpful? Feel free to rate it.
Suggestion To thank Quote Answer

12/15/2008 7:47 AM	Rate (0)
Arunakat1 Posts: 217 Rating: (52)	Hi, To my knowledge I think you are having problem with profibus connection. First check the profibus cables connectors and switches. And check weather all the Access addresses are in ET station. If so may be you having your problem in ET module or in network connection. OB121 means theirs a programming error in your program. But it can happen when you lose access to other modules.Check the program also. I think this will help you, Thanks.
Arunakat1 Posts: 217 Rating: (52)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on