Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Problems with PEEK

Created by: Ben Rowland at: 6/6/2012 6:53 PM (6 Replies)

Rating (0)

Thanks 2

7 Entries

6/6/2012 6:53 PM	Rate (0)
Ben Rowland Posts: 4 Rating: (0)	I am using an SCL command like #result := PEEK(area:=16#84, dbNumber:=5, byteOffset:=1); to try to read the second byte in the data block DB5. I have created a DB and given it the number 5, so that when I type %DB5 it autocorrects to the name of the data block, but when I try and run the code I get the following error message: Temporary CPU error: DB 5 not loaded, access in FC 1 affecting OB 1 execution Processing will continue (no OB processing) I am able to access the values in the DB using direct addressing, so I don't know why it it "not loaded" within the same FC when I use PEEK instead. Any help anyone can give would be greatly appreciated. Ben
Ben Rowland Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

6/6/2012 8:18 PM	Rate (0)
0_Einstein Diamond Expert Joined: 7/7/2010 Last visit: 12/11/2023 Posts: 13998 Rating: (2284)	Ben Rowland I am using an SCL command like #result := PEEK(area:=16#84, dbNumber:=5, byteOffset:=1); to try to read the second byte in the data block DB5. I have created a DB and given it the number 5, so that when I type %DB5 it autocorrects to the name of the data block, but when I try and run the code I get the following error message: Temporary CPU error: DB 5 not loaded, access in FC 1 affecting OB 1 execution Processing will continue (no OB processing) I am able to access the values in the DB using direct addressing, so I don't know why it it "not loaded" within the same FC when I use PEEK instead. Any help anyone can give would be greatly appreciated. Ben My Test FC syntax (see attachment) seems to work correctly. Maybe my example will help. Attachment peek_testing.jpg (791 Downloads)
	science guy
Suggestion To thank Quote Answer

6/7/2012 10:01 AM	Rate (0)
Ben Rowland Posts: 4 Rating: (0)	Hi Huggy, Thanks for the quick response. Your code seems very similar to what I am trying to do, and my code compiles and runs fine, it just seems to be having a problem with accessing the DB at runtime. In your example you give the DB number as 906, did you just create a new DB and set its number to 906 in properties? Thanks again, Ben
Ben Rowland Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

6/7/2012 1:25 PM	Rate (0)
Ben Rowland Posts: 4 Rating: (0)	With the help of Siemens support, I have now solved my problem. For anyone else who may be seeing the same thing in the future, the solution is to create a DB using the "Standard - compatible with S7-300/400" block access rather than the default "Optimized" option.
Ben Rowland Posts: 4 Rating: (0)
Suggestion To thank Quote Answer
This contribution was helpful to 2 thankful Users O_Moderator 0_Einstein

6/15/2012 10:41 AM	Rate (0)
Remark Bronze Member Joined: 9/1/2006 Last visit: 8/28/2023 Posts: 192 Rating: (13)	Where can you change this default setting ?

Suggestion To thank Quote Answer

6/15/2012 12:32 PM	Rate (0)
Ben Rowland Posts: 4 Rating: (0)	This is one of the main options when adding a new block to a project. When you click on "Add new block" in the left hand tree menu, the Add new block window will pop up. Select "Data block" and one of the settings you will be able to configure is "Block access:" which has two options, "Optimized" and "Standard - compatible with S7-300/400". You need to select the latter. Then when you create variables in the DB, they will have an offset value, which you can use to refer to them using PEEK and POKE. I hope this helps. See the attached image for more information. Attachment create_datablock_standard.jpg (329 Downloads)
Ben Rowland Posts: 4 Rating: (0)
Suggestion To thank Quote Answer

4/14/2013 7:26 AM	Rate (0)
Elektron. Posts: 2 Rating: (0)	If you use the 'optimized block access' setting the peeks wil return only zero's / 16#0. (on a 1212C)
Elektron. Posts: 2 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on