• Setting the initial state of the device or router
• Installing the device or router using the service pin or manual (Neuron ID) method
The processes vary depending on your device or router requirements and whether you are attached to the network and OnNet. The Commission Wizard guides you through the process.
To commission devices and routers, follow these steps:
1. Select the devices and routers to be commissioned. You can select one or more device shapes, one or more subsystem shapes, one or more supernode shapes, or a combination. You can also select a subsystem by right-clicking the page background.
If devices to be commissioned are on the far side of a router from the network service device, you must commission the router before any such devices.
When you select a subsystem shape or page, the operation applies to all devices and routers in that subsystem and its dependent subsystems unless excluded by setting Exclude Nested Subsystems from Subsystem Operations. Before commissioning a subsystem, you may identify the devices that will be affected by the commission—right-click the subsystem shape or a blank portion of the subsystem page, click Subsystem Propertieson the shortcut menu, and view the devices listed on the Devices tab.
2. Right-click one of the selected shapes. 3. Select Commission from the shortcut menu.
The Commission Device Wizard starts. Select from the following for your next step:
If you are attached to the physical network and working OnNet, the Application Image Name window appears. Go to Loading an Application Image for directions. Routers do not support application loading. During the load application process, any selected routers are excluded. If you are unattached or attached and working OffNet, the Device Identification window appears. Go to Installing Devices and Routers.
Loading an Application Image
This section provides information on specifying the device application image name and selecting the Load Application Image command for commissioning, loading, and replacing devices. The title on the window reflects the process in progress.
If you are connected to the physical network and working OnNet, the Specify Device Application Image Name window (shown below) begins the commission process and is the second step in loading a new application or replacing a device.
As discussed in LONWORKS Basics, every device contains an application that determines the behavior of the device. The device may contain the desired application when purchased or it may come with an application file that you may load into the device upon commissioning. You may be prompted to load an application image into a device while you are commissioning, replacing, or loading a new application into the device.
All the selected devices associated with the listed Device Template are shown in this window. Additional windows are shown after you complete selections for this window if the devices you selected have other device templates.
1. Make appropriate selections in the window based on the information provided below. Load Application
Image
Set Load Application Image if the device you are commissioning is a Neuron Chip or Smart Transceiver hosted device with writeable application memory and the device comes with an application file (.nxe or .apb extension).
Image Name Specify the pathname. If you specified a device interface (XIF) file in the Device Template dialog (see Creating a Device in Chapter 4) and you are simultaneously creating and commissioning the device, you cannot specify a different device interface file here. If an application image file is found in the same directory as the XIF file of the device template, that directory is the default.
XIF Name If you are loading an application file with an .nxe extension, select the pathname of a device interface file (.xif extension).
.xfb); however, it automatically creates binary files from existing text files (.nxe and .xif) and saves them in the application file folder containing the corresponding .nxe file.
Note: If you are operating as a remote client (full or lightweight), the LonMaker tool looks for the application files on the LNS Server computer. Be sure to specify the full pathname (including drive) of the application files on the LNS Server. You cannot load an application file directly from a remote client computer to a device.
Caution When you load an application image, be sure to verify that the Device Name field
contains the name of the device to be loaded to make sure that you are loading the application into the correct hardware device. If the device already has an application, the LonMaker tool will compare the program ID of the new application with the program ID of the application in the device. If both applications use a type 8 or 9 program ID, a warning message is displayed if the device Class or Subclass are different. A warning message is also displayed if a program ID that is not a type 8 or 9 program ID will be overwritten with a type 8 or 9 program ID, or vice versa. If you see this warning, verify that you have the correct device and application. If you do, you can safely ignore the warning message.
2. Click Next to continue. Repeat this process for each device template in the selection. The Setting the Device Initial State window appears.
Go to Setting the Initial State for further instructions.