Driver Manual |
4.4.4Map Descriptor Example.
Name of the data array that will be updated when this map descriptor is used.
The position in the data array that corresponds to device whose number is equal to the Address Parameter.
In this example device 500's state will be strored in the 0th element of the data array called
DEVICE_STATES_LOOP1
| The range of | |
| device address is | |
| determined by this | |
All map | parameter. | |
Because address is | ||
descriptors for the | ||
500 and length is | ||
AM6000 Notifier | ||
100 in this | ||
driver must be | ||
example all | ||
passive. | ||
devices 500 to 599 | ||
| ||
| will be |
Map_block_Name, scan_interval, Data_Array_Name, | Data_Array_Offset, Function, node_name, AM6000_TypeID, Address , Length , am6000_Ackable | ||||
DEVICES_100_199, 1.0s, | DEVICE_STATES_LOOP1, 0, | passive, node_a, | 500 , 100 , Yes | ||
Connects this map descriptor to a node whose name is 'node_a' and thus connects the map descriptor to a port.
This keyword indicates that this map descriptor will only be used to process device state messages. This makes the address and length parameters very important.
The device address of the first device to be processed by this map descriptor. Devices are allocated to loops. The device address consists of a mmnn format where mm is the loop number and nn is the device number.
In this example the address is set to 500 this indicated that the first device to be processed by this map desc. Is on loop 5 and is device zero.
When a Block Acknowledge or System Reset message is received the driver will set the portion of the data array
DEVICE_STATES_LOO P1 starting at Data_Array_Offset for Length number of elements to zero.
FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408)
Visit our website: www.fieldserver.com
Page 8