S7 area length error when writing

  1. 26.11.2010, 09:19#1
    Join date
    09.11.2010
    Posts
    6
    thanks
    1
    Got 0 Thanks for 0 posts

    Hello,
    We have written a program to monitor the temperature and mileage of slip rings. We have coupled an S7-317 2DP as a slave and an S7-313 C 2DP as a master in a multiproject.
    Our slave is an intelligent slave in which we save the temperature values ​​in DBs.
    Since the last program change (we added 1FC and 2 DBs)
    there is always an area length error in the diagnostic buffer of the S7-317 when writing, but there is no indication in the details that we can see where the problem is.
    Can someone help us?
    Area length error while writing

  2. 26.11.2010, 09:23#2
    Join date
    29.08.2009
    Posts
    7
    thanks
    0
    Got 0 Thanks for 0 posts

    Are the called DBs also available in the controller and long enough?
     

  3. 26.11.2010, 09:24#3
    Join date
    11.04.2008
    Location
    Bavaria
    Posts
    531
    thanks
    28
    Received 68 thanks for 68 posts

    On offline comparison
    If necessary, comment out all calls one after the other in OB1 where the system error goes away. Something is wrong in the block.
     

  4. 26.11.2010, 09:33#4
    Join date
    07.10.2008
    Posts
    78
    thanks
    1
    Received 15 thanks for 15 posts

    If you go further down in the diagnostic buffer, an address should appear.
    Or if you can stop the system, then remove the OB121 online so that the CPU goes to Stop and in the stacks you can see in which block and at which point.

    If necessary, mark the diagnostic buffer and copy it in here as a quote or code tag.
     

  5. 26.11.2010, 10:02#5
    Join date
    09.11.2010
    Posts
    6
    thanks
    1
    Got 0 Thanks for 0 posts

    DB's all there and long enough.
    Regardless of how far I look back in my diagnostic buffer, I cannot find a block address in which the error occurs, everything is the same as in the picture in my first post.
    I cannot stop the system at the moment, but will delete OB 121 online at the next opportunity and then take a look.
     

  6. 26.11.2010, 10:15#6
    Join date
    16.05.2007
    Location
    in the steel mill ...
    Posts
    1,182
    thanks
    120
    Received 429 thanks for 236 posts

    You can also proggen fine things in OB121 to find out why it was called. Simply mark the OB121 in the block container and press the mysterious "F1" key.
    Approx
    „Nihil est in cpu, quod non fuerit in intellectu "-Nothing is in the CPU that was not (before) in mind.
     

  7. 26.11.2010, 10:15#7
    Join date
    27.10.2005
    Location
    Schwäbisch Gmünd
    Posts
    5,654
    thanks
    717
    Received 1,007 thanks for 818 posts

    What parameters does the OB121 have? Maybe it brings something to look at the status.
    But after the message it really looks as if the DBs are not on the CPU or not linked, i.e. are only in the load memory. What is the online accountant showing? What does he say about building block properties?
    Rainer Hönle
    DELTA LOGIC GmbH

    The criticism of others has not spared anyone from their own performance (Noël Coward)
     

  8. 26.11.2010, 10:28#8
    Join date
    08.04.2008
    Location
    Cologne
    Posts
    846
    thanks
    39
    Received 245 thanks for 200 posts

    Hello Stemmann!

    If "Access address: 0" is in the diagnostic buffer, it indicates that the DB online is not available.
    Possible causes are:
    1. the DB is really not there
    2. No DB is open in the block with "T DBD 0"

    Look for DBD 0 and check the corresponding blocks.

    greetings
    Give
     

  9. The following user says thank you to Gebs for this useful contribution:

    bernd81 (January 12, 2012)

  10. 26.11.2010, 11:21#9
    Join date
    29.07.2008
    Location
    Stuttgart
    Posts
    232
    thanks
    64
    Received 25 thanks for 25 posts

    Hi,

    Deleting online with the OB121 also worked for me. Then you will also see the position in the DiagPuffer.

    My mistake at the time was that I had parameterized a data word in the DB (and ONLY the one word!), But queried a double word in the FC ...
     

  11. 26.11.2010, 12:05#10
    Join date
    08.02.2007
    Location
    A-2320
    Posts
    2,270
    thanks
    251
    Received 333 thanks for 304 posts

    I'm guessing that the wrong DB will be opened ......