82
ICC
Max Master
This field is the highest allowable address for MS/TP master nodes on the
network. Any address higher than this will not receive the token from the
gateway. Enter a value between 0 and 127. Note that this value must be greater
than or equal to the configured Address for the gateway. If the highest address
on the network is unknown, set this field to 127.
Configuration tip:
The Address and Max Master fields greatly affect network
performance. For best results, set all device addresses consecutively, starting
with address 0, ending with a device with a configurable Max Master field at the
highest address. Then set that device’s Max Master field to its network address.
This will prevent any unnecessary poll for master packets on the network and
thereby maximize efficiency.
8.8.3.3
BACnet Service Object Configuration
The following describes the configurable fields for a BACnet service object. For
more information on BACnet service object editing options, refer to section 8.6.
Type
The radio buttons in this group select the BACnet object type. Choose from
Analog Input, Analog Output, Analog Value, Binary Input, Binary Output, or
Binary Value.
Description
This field is a description of the service object. It is not used on the gateway, but
serves as a reference for the user. Enter a string of between 1 and 16 characters
in length.
Dest Dev Inst (“Destination Device Instance”)
This field is the destination device instance of the BACnet device the gateway
should send requests to for this service object. Enter a value between 0 and
4194302 (0x0 – 0x3FFFFE).
Note that the gateway uses this value for dynamic device binding to determine
the address of the destination device. If the destination device does not support
dynamic device binding, then static device binding must be used. For more
information on device binding, refer to section 11.3.2.3.
Use Static Device Binding
This checkbox is used to manually define the destination device network address.
This feature must be used for all MS/TP slave devices, and for any MS/TP
master devices that do not support dynamic device binding. For more
information on device binding, refer to section 11.3.2.3.
