Echelon i.LON SmartServer 2.0 - Manual (Page 234)

i.LON SmartServer 2.0 Programmer’s Reference 14-34
bridges. You can use permanent bridges to preserve subnet
IDs.
• LCA_NUL. The SmartServer automatically select the
appropriate router type.
The port on the SmartServer used for receiving messages from
the IP-852 Configuration Server. The default port is 1628.
14.5 Remote Network Interface
You can use the List, Get, Set, and Delete functions on a remote network interface (RNI) as described
in the previous section, L
ON W ORKS Devices. An RNI has the same properties as devices except for the
following differences:
• An RNI has an xsi type of LON_Device_RNI_Cfg.
• The property is RNI.
• The property is LON_Device_RNI_Cfg.htm.
Note that LON_Device_RNI_Cfg has three additional properties:
The port on the SmartServer used to listen for LonTalk packets
when it is being used as an RNI. The default port is 1628.
The maximum number of receive transactions that the RNI
application can receive at one time. This value may range from
1 to 32,768. The default value is 16. You can increase this
value if you observe buffer overflows. You can decrease this
value if you observe that the SmartServer's memory is low.
A receive transaction entry is required for any incoming
message which uses either repeating or acknowledged
messaging service (a receive transaction is not required for
messages using unacknowledged service). A receive transaction
entry is also required for each unique source address/destination
address/priority attribute.
Each receive transaction entry contains a current transaction
number. A message is considered to be a duplicate if its source
address, destination address, and priority attribute vector into an
existing receive transaction and the message's transaction
number matches the entry's transaction number.
Receive transaction entries are freed after the receive timer
expires. The receive timer duration is determined by the
destination device and varies as a function of the message
addressing mode. For group addressed messages, the receive
timer is determined by the address table. For Neuron ID
addressed messages, the receive timer is fixed at eight seconds.
For other addressing modes, the non-group receive timer in the
configuration data structure is used.
14.6 L
ON
W
ORKS
Functional Blocks
The following section describes how to use the List, Get, Set, and Delete functions on L ON W ORKS
functional blocks.