Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Area error when writing

Created by: andrego at: 12/16/2011 1:43 PM (5 Replies)

Rating (1)

Thanks 0

6 Entries

12/16/2011 1:43 PM	Rate (0)
andrego Posts: 3 Rating: (0)	Hi Guys. Can someone please help me with this problem " Area error when writing ". How do i solve this problem? I have Attachment Diagnostic buffer.zip (65 Downloads)
andrego Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

12/16/2011 2:10 PM	Rate (0)
hdhosseini Diamond Expert Joined: 1/28/2009 Last visit: 6/8/2023 Posts: 6805 Rating: (1346)	andrego Hi Guys. Can someone please help me with this problem " Area error when writing ". How do i solve this problem? I have Dear andrego, Check the attachment to see how you can find more information about the event occured.You can find help on event occured and also go to the problematic block .You can upload the whole project or section you have problem in it for further inspection here. Help on Event 2x25 Cause: You have used an illegal address range for area-crossing indirect addressing. The area ID of the access address (bits 24 to 31) is not permitted. To correct or avoid errors: Use a pointer with a correct area ID. Best regards, Hamid Hosseini Attachment error.JPG (164 Downloads)
	Last edited by: hdhosseini at: 12/16/2011 2:18 PM //typo Demo Channel on Youtube
Suggestion To thank Quote Answer

12/19/2011 8:15 AM	Rate (0)
andrego Posts: 3 Rating: (0)	I have attached a screenshot of the diagnostic buffer, but i cant click on the button "open block"? I read somewhere that ob121 could interfere, so you cant open the block. Regards, Andreas Pehrson Attachment Diagnostic buffer.JPG (70 Downloads)
andrego Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

12/19/2011 8:46 AM	Rate (0)
fritz Diamond Expert Joined: 10/7/2005 Last visit: 6/9/2023 Posts: 2969 Rating: (1025)	Hello andrego can you afford to put your CPU into Stop? If so, delete OB121 from the PLC, it will then go into Stop due to the access error, "Open Block" will be available and take you straight to the isntrcution that causes the problem. 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

12/19/2011 10:48 AM	Rate (0)
andrego Posts: 3 Rating: (0)	Hello Fritz Thanks for your reply. I tried to put the cpu in stop mode and deleted ob121, but without any luck. Are there other solutions to the problem? Regards, Andreas Pehrson
andrego Posts: 3 Rating: (0)
Suggestion To thank Quote Answer

12/19/2011 12:06 PM	Rate (1)
fritz Diamond Expert Joined: 10/7/2005 Last visit: 6/9/2023 Posts: 2969 Rating: (1025)	Hello andrego it must work and as I'm not too sure what you have done, please try the following: 1.) Make sure OB121 has been deleted online from the CPU while the CPU is still in run (if you manually stopped the CPU to delete OB121, restart it to let it "crash" again). 2.)Your CPU must now "crash" due to the access error and the missing OB121 3.) Open the CPU diagnostic buffer. The last entry will simply tell you that the CPU is in Stop mode,the entry before that should contain the FC or FB that caused the access problem. 4.) Highlight it and you should have the "open Block" available. Please check this again and - should it still not work - let us know which of the above Steps did not work and post your CPU diag buffer here. 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

|

Share this page:

Share this page on...

Follow us on