Showing results 1 to 6 of 6

Thread: Archive scanning cycle ignored

  1. #1
    nsko Gast

    Frage Archive scanning cycle ignored

    When an archive is started using a function the Archive Scanning Cycle is ignored. Is this intended behaviour?

  2. #2

    Default Re: Archive scanning cycle ignored

    If the archive is not started automatically with the runtime, but user defined e.g. through the function "start archive", for example to achieve batch archives, this does not affect the scanning rate of the cyclic scanning (the rate in which a value is recorded in the archive).

    User-defined start and stop of the archive however does affect the archive saving rate. (the rate in which the archive (file) is closed, and a new archive (file) is started. The settings configured here (e.g. save archive every 1 minute) are ignored in this case.

    From the moment the archive is started until it is stopped manually through the function, the archive entries are in the "open" archive file "xx.arx". Even after the runtime has been restarted, it continues to write in this file until the archive is stopped (e.g. until the batch is finished). At this moment, the "xx.arx" file (xx is the short name of the archive) is renamed in xx080815085337, where again xx is the short name, 08 the year, 08 the month, 15 the day and 085337 the time in UTC the archive is closed.

    Of course this does not mean, that the archive is not saved on the harddrive, but only that the archive is not closed, until it is stopped through the function "stop archive".

  3. #3
    nsko Gast

    Cool Re: Archive scanning cycle ignored

    Hi Mark
    That's fine. But when evacuating data to SQL Server the consequence is, that no data are evacuated until the batch is ended. It would be nice to make this configurable, so that data evacuation still could run every 5 min even with batch archiving.
    best regards, Niels

  4. #4

    Default Re: Archive scanning cycle ignored

    I can register your request to be considered for when the next zenon version is planned.

    May I ask why exactly you want to save partial batch data in the SQL database? For data safety reasons? Or because you already want to start working with the data?

    You could create a second archive, which is not a batch archive and starts automatically with the runtime, which has the same variables and scan rate as the batch archive, and set to "keep 0 hours" and evacuate to SQL. This way you would have double data, but could work with the data in your SQL server from an external application or reporting tool.

    Looking in detail at the batches, you will find they consist "just" of a batch-name and the corresponding start-time and stop time.

    In fact if you could work with the data recorded by the non-batch archive, and read the information about the batches (if already available / closed) from the table containing the batch information, e.g. when working with an external reporting utility like crystal reports.

  5. #5
    nsko Gast

    Rotes Gesicht Re: Archive scanning cycle ignored

    The reason is that we want to start using the data before the batch is ended.
    We will follow your suggestion, even though it's not the optimal solution. The result is not only double data as you mention, but also data aquisition when there's no active batch - part of what we want to avoid by using batch archiving.
    Please register the request.

  6. #6

    Default Re: Archive scanning cycle ignored


    your request has been added with the reference number RQ#3508.

    best whishes from Austria

Similar Threads

  1. RDA archive functionality for the STRATON driver
    By bernhards in forum Drivers
    Replies: 1
    Last Post: 20th February 2008, 13:48
  2. How does the batch archive gets its name?
    By bernhards in forum zenon Pharma Edition
    Replies: 0
    Last Post: 21st August 2007, 08:59
  3. On opening the archive MDI window an error appears!
    By wolfgangm in forum zenon Supervisor
    Replies: 0
    Last Post: 17th August 2007, 13:11

Posting Rules

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts