...
- State/Transition must be entered in one of the following forms: UP, DN, UP to DN, DN to UP. This field can be left blank to indicate an info event.
- UP and DN represents an initialisation state for the channel
- UP to DN and DN to UP represent state transitions for the channel
All fields must be separated by single comma. Spaces are not required. A trailing comma is not required but will be removed automatically when read by Centrix.
...
If an event already exists for a relay at the time listed in the file, that event will be marked as duplicate and not uploaded.
Warnings
| Note | ||
|---|---|---|
| ||
| Centrix generally expects event data to be imported in chronological order. Events that are imported out of sequence can cause unexpected results, especially with regard to Virtual Channels and Alerts. You may also find that the map initialises some objects to the wrong state if events are imported out of order for the site you are viewing. |
| Note | ||
|---|---|---|
| ||
| Centrix expects to receive initialisation events for channels if there is a 'dark' period. For example, if you import some event data covering 8AM to 9AM and then subsequently import data from 11AM to 12PM, you should ensure that the beginning of the 11AM-12PM file contains the starting state for every channel. This is because there is an unknown period between 9AM and 11AM where the state transitions are missing. If you do not initialise the state at the beginning of the data set then you can experience some unexpected behaviour similar to those highlighted in the 'out of order' event warning above. |