Lonworks modules
To use this driver, you must have a target host (remote controller) that is licensed for the feature lonworks. Your Supervisor station must also be licensed for lonworks).
The Lonworks driver provides these driver modules and many modules that support specific devices.
| Palette name | Network component name in the Nav tree | .jar file names in the modules folder | Function |
|---|---|---|---|
| lonworks | LonNetwork | lonworks.jar | Provides Lon (Local Operating Network) networking functions; manages devices and proxy points. |
| lontunnel | TunnelService | lontunnel.jar | Supports remote PCs with a
|
| kitLon | LonTime, LonTodEvent, LonEnumTodEvent, LonPoint, LonReplace, and BufferParams | kitLon.jar | Provides additional components that manage inputs and outputs and configure advanced messaging. |
| lonIP | LonIpNetwork | lonIp.jar | Communicates on an IP Lonworks channel as defined in CEA-852. The station presents itself as an IP channel node. |
| lonVendor | depends on the vendor | lonVendor.jar | vendor is replaced by the name or acronym for a building automation manufacturer, such as Aaon, FloridaHeatPumps, Hillrom, Mitsubishi, Trane, etc. |
Each Lon vendor module includes its own palette, which you open in the palette side bar, JACE-9000 and manually drag or copy devices to a Lon network.
Figure 1. Opening a specific Lon vendor palette
