Code: |
AS + 516 |
Symbolic |
bccAlarmHList |
This command will get complete (or partial) alarm history from the remote device.: this is a standard download transfer sequence.
REQDATA structure is the following:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U32 |
FROMID |
First alarm history ID required |
4 |
U32 |
TOID |
Last alarm history ID required |
ITEMDATA structure is the following:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U32 |
ID |
Alarm history ID |
4 |
U8 |
HH |
Time (hour) of the item |
5 |
U8 |
MM |
Time (minute) of the item |
6 |
U8 |
SS |
Time (second) of the item |
7 |
U8 |
DD |
Date (day) of the item |
8 |
U8 |
MO |
Data (month) of the item |
9 |
U8 |
YY |
Data (year - 2000) of the item |
10 |
U32 |
CODE |
Alarm code |
14 |
U32 |
- |
Reserved |
18 |
U32 |
- |
Reserved |
22 |
U32 |
- |
Reserved |
26 |
STRZ |
TEXT |
Alarm text desctiption (optional) |
In case of RTE firmware (see bccSysInfo, FIRMWTYPE=8), the CODE field contains the following data:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U16 |
ALCODE |
RTE alarm code (0=none) |
2 |
U16 |
ALAXIS |
RTE alarm axis ID (0=none) |
As general, you can get items with the following order:
•from OLDID to NEWID for native order.
•from NEWID to OLDID for reversed order.
When using RTE version 33.16.x (or lower), you should consider two different cases:
1.NEWID is greater/equal than OLDID.
2.NEWID is less than OLDID.
In case 1, you can get items with a single request, as:
•from OLDID to NEWID for native order.
•from NEWID to OLDID for reversed order.
In case 2, you must get items with two different request, as:
•from OLDID to 0xFFFFFFFF and from 0 to NEWID for native order.
•form NEWID to 0 and from 0xFFFFFFFF to OLDID for reversed order.
