Appendix
9836 3521 01 655
10.3.1.1 Storing and retrieving cycle data
Since the cycle data for each bolt is stored locally on the TC it was run on the amount of cycle data that
could be stored depends only on the size of the cycle data storage and on how many variables that is
included in the configured reporters.
To minimize the need for fetching bolt cycle data from each TC when a device is requesting it a complete
cycle data is stored in a volatile memory cache on TC1. This cache is filled with cycle data when a cycle is
run or when a requested cycle data has been retrieved from each TC. After a power up the cache is empty
an all requested cycle data has to be retrieved from each bolt.
It is possible to change TCs within a system and still be able to retrieve cycle data from them.
If however any TC should be missing or disconnected when a cycle data is fetched the data for the bolt
that belong to that TC is reconstructed using status information that is saved in the cycle data header for
each bolt in the cycle data. Since this data is saved together with station data and data for bolt 1 on TC1 it
is kept to a minimum, the data saved for each bolt is:
Ordinal bolt number
Status (OK,NOK etc.)
Failing step number (if status NOK)
A new bolt variable “Data missing” has been added to make it possible to detect if data was missing for a
particular bolt. This variable is 1 if data is missing and 0 if not.
To Next Page
Loading...
Need help?
General
