Filter
Top Products
FS-8700-48 Fike Cheetah Manual Page 22 of 36
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Tel: (408) 262-2299 Fax: (408) 262-9042 Toll Free: 888-509-1970 email: support@fieldserver.com
4.5.9. Map Descriptor Example 9 – Full History Event Record – Specific Device
Full History Event records contain composite data which require at least 65 consecutive Data Array locations for storage. If the
Data_Array_offset is not carefully specified the storage areas will overlap.
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Cheet_Zone, Cheet_DT, Cheet_Device, Cheet_Loop, DA_Byte_Name
Device1_L1_Hist, DA_HIST, 20, Passive, Node_A, None, History, 20, 1, DA_HIST_EVENT
4.5.10. Map Descriptor Example 10 – Full History Event Record – Any Device
Only the most recent history event is stored using this Map Descriptor. The full record is stored but is overwritten when a new event
is received irrespective of the event’s device address.
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Cheet_Zone, Cheet_DT, Cheet_Device, Cheet_Loop, DA_Byte_Name
Device1_L1_Hist, DA_HIST, 0, Passive, Node_A, None, History, ALL, 1, DA_HIST_EVENT
Event codes are stored in
this Data Array.
Event history records are stored in
this Data Array. The contents of the
Data Array locations are described in
section 6.6
Each event record uses at least 65
consecutive elements of the array so
the choice of an offset must be made
carefully.
One device is processed using this
Map Descriptor. Thus only events
relating to device 20 of loop 1 will be
stored using this Map Descriptor.
Events relating to other devices will
be discarded unless additional Map
Descriptors are defined.
Differs from Example 9 in that
the device is specified as ALL -
now the driver stores the event
for any device at the same
location.