Echelon LonBridg Server - Manual (Page 20)

14 Configuring the LonBridge Server
the program ID from the new device and then searches the device class files for a
matching program ID. If the LonBridge Server finds a matching program ID, the
LonBridge Server stores information about the discovered device in the
devices.xml file in the Instances directory (see Instances Directory on page 16).
Each class file describes the device interface for a specific program ID, similar to
a L
ON W ORKS device external interface (XIF) file. However, unlike XIF files, the
class files are XML files that identify only those network variables that the
LonBridge Server monitors or controls. That is, the class files do not necessarily
include all of the network variables that are available on the device. In addition,
the class files specify whether a network variable should be polled by or bound to
the LonBridge Server.
A standard installation includes the class files listed in Table 2.
Table 2. Class Files
Class File Application Program ID
AM1_LNS_S04.xml Appliance Module 9F:FE:57:1E:28:06:10:00
AM2L_LNS_S04.xml Appliance Module 9F:FE:57:1E:28:06:10:60
AMDR_LNS_S04.xml Lamp Module 9F:FE:57:1E:00:0A:10:40
blinds.xml Sun Blind Actuator 9F:FF:FF:05:01:06:11:08
isiappliance.xml Echelon 3120 ® Appliance
Module
90:00:01:1E:29:4A:11:01
isiappliance2.xml Example Appliance
Module
9F:FF:51:1E:00:4A:11:08
isiappliance3.xml Echelon 3170™
Appliance Module
90:00:01:1E:29:46:11:03
isiblinds.xml Example Blinds 9F:FF:FF:3D:0C:40:11:00
isiblinds2.xml Sienna AM2 3170
Sunblinds
9F:FF:FF:3D:0C:44:11:03
isiblinds3.xml Echelon Mini PL 3150 ®
Sunblinds
9F:FF:FF:3D:0C:46:11:03
isikeypad.xml Nico Keypad 90:00:B5:20:35:41:11:01
isikeypad2.xml Nico Keypad 90:00:B5:20:35:41:11:00
isilampmodule.xml Echelon 3120 Lamp
Module
90:00:01:1E:29:49:11:02
isilampmodule2.xml Example Lamp Module 9F:FF:51:1E:00:4A:11:00