Skip to Content

Register Login

Default Header

(header konnte nicht geladen werden)

Navigation

area length error when reading

Created by: jejelafrite at: 5/12/2014 4:17 PM (12 Replies)

Rating (1)

Thanks 3

Result pages:: |; 1 | 2; |

13 Entries

Entries per page: 10 | all

5/12/2014 4:17 PM	Rate (0)
jejelafrite Posts: 1 Rating: (0)	Hie, I work on a siemens cpu S7-300 witch is in network with an other cpu S7-300 by profinet, who communicate with differents computer also by profinet, and a spécial équipement made by CEA who work on simatic manager with a file.GSD and who communicate by profibus. After différents network and hw-config modification an error occur. i have put the OB 121 block and in the diagnostic buffer i can see: area length error when reading Global DB, double-word acces, Acces adress:340 request OB:programming error ob(ob121) priority class: 12 internal error, incomming event. i have search and i dont use that number of adresse I/O in the simatic programme, Somebody can help me? thank you
jejelafrite Posts: 1 Rating: (0)
Suggestion To thank Quote Answer

5/12/2014 5:41 PM	Rate (0)
hdhosseini Diamond Expert Joined: 1/28/2009 Last visit: 1/3/2026 Posts: 6891 Rating: (1368)	jejelafrite Hie, I work on a siemens cpu S7-300 witch is in network with an other cpu S7-300 by profinet, who communicate with differents computer also by profinet, and a spécial équipement made by CEA who work on simatic manager with a file.GSD and who communicate by profibus. After différents network and hw-config modification an error occur. i have put the OB 121 block and in the diagnostic buffer i can see: area length error when reading Global DB, double-word acces, Acces adress:340 request OB:programming error ob(ob121) priority class: 12 internal error, incomming event. i have search and i dont use that number of adresse I/O in the simatic programme, Somebody can help me? thank you Hello, Perhaps Open Block option in diagnostic buffer of CPU guide you to the point of error.Possibly you can find clue regarding base address or start address of a module or a communication partner.In case of address calculation in runtime,you may need a bit of indirect addressing knowledge to find the cause of error. I hope these comments help you, Hamid Hosseini
	Last edited by: hdhosseini at: 5/12/2014 5:56 PM Demo Channel on Youtube
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users metwally mustafa Mo.Sa

5/12/2014 9:08 PM	Rate (0)
IBN-Service Posts: 8946 Rating: (1000)	jejelafrite ... Global DB, double-word acces, Acces adress:340 ... i have search and i dont use that number of adresse I/O in the simatic programme, That adress is not an I/O adress, it is the DBD -adress of DB. The DB is to short!
IBN-Service Posts: 8946 Rating: (1000)
Suggestion To thank Quote Answer

5/13/2014 5:49 AM	Rate (0)
S7 AUTOMAN Posts: 515 Rating: (56)	jejelafrite Hie, I work on a siemens cpu S7-300 witch is in network with an other cpu S7-300 by profinet, who communicate with differents computer also by profinet, and a spécial équipement made by CEA who work on simatic manager with a file.GSD and who communicate by profibus. After différents network and hw-config modification an error occur. i have put the OB 121 block and in the diagnostic buffer i can see: area length error when reading Global DB, double-word acces, Acces adress:340 request OB:programming error ob(ob121) priority class: 12 internal error, incomming event. i have search and i dont use that number of adresse I/O in the simatic programme, Somebody can help me? thank you hello, as IBN-Service mentioned, area length error occurs when the processor try to access an address which is not defined. Check the particular DB and and see whetehr its undefined addresss is being used somewhere.
S7 AUTOMAN Posts: 515 Rating: (56)
Suggestion To thank Quote Answer
This contribution was helpful to 1 thankful Users IBN-Service

5/13/2014 7:24 AM	Rate (0)
R J Posts: 215 Rating: (12)	Hi jejelafrite, Please go through below link: http://www.plctalk.net/qanda/showthread.php?t=55152 To see the jpg image you have to register yourself over there. Also go through below forum link as well: /tf/WW/en/Posts/42387
R J Posts: 215 Rating: (12)	Last edited by: R J at: 5/13/2014 7:25 AM
Suggestion To thank Quote Answer

5/13/2014 1:57 PM	Rate (0)
Madhava Silver Member Joined: 11/26/2011 Last visit: 4/11/2025 Posts: 508 Rating: (23)	It means CPU is trying to access to a address which is not defined/found. Try to open the fault location from diagnostics itself.

Suggestion To thank Quote Answer

9/10/2015 3:26 PM	Rate (0)
Andre4x4 Posts: 2 Rating: (0)	HI Please explain the " Acces adress:340" Where is this 340 pointing to? Thanks andre
Andre4x4 Posts: 2 Rating: (0)
Suggestion To thank Quote Answer

9/10/2015 3:43 PM	Rate (0)
hdhosseini Diamond Expert Joined: 1/28/2009 Last visit: 1/3/2026 Posts: 6891 Rating: (1368)	Please explain the " Acces adress:340" Where is this 340 pointing to? It means, there is an error for word access starting from byte number 340 .For example"L DB1.DBW340" wants to access word number 340 and that cell doesn't exist.
	Demo Channel on Youtube
Suggestion To thank Quote Answer

5/3/2019 8:30 AM	Rate (1)
Seyyed Mahdi Esma... Posts: 25 Rating: (2)	Hello to everyone I had this problem when I've deleted some CFC charts and downloaded to PLC (in PCS7). So, I had to delete all DBs on CPU and download entire program to CPU. I hope my experience help you
Seyyed Mahdi Esma... Posts: 25 Rating: (2)
Suggestion To thank Quote Answer

7/10/2019 6:20 AM	Rate (0)
NullVelocity Posts: 1 Rating: (0)	Rather shocked that no one has been able to properly assist with this. Clearly, he is not receiving the complete diagnostic information due to the OB121 interrupt. A quick workaround for this is to go "on-line" and delete OB121. This will cause the CPU to stop, however, you will now have the complete diagnostic information everyone on this thread seems to believe you already have
NullVelocity Posts: 1 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on