i.
Echelon, i.LON, LON, LONORKS, LonTalk, Neuron, LONMARK, 3120, 3150, LNS, LonMaker, and the Echelon logo are trademarks of Echelon Corporation registered in the United States and other countries. LonPoint and LonSupport are trademarks of Echelon Corporation. Other brand and product names are trademarks or registered trademarks of their respective holders.
Preface The i.LON® SmartServer can automatically install and manage a LONWORKS network running over a PL-20 power line channel. The SmartServer features a standalone network management mode in which it can install and maintain a LONWORKS network without LNS network management services.
Welcome When running on a noisy PL-20 power line channel, the SmartServer can use a repeating function to transmit network messages to the devices closest to it, which in turn relay the messages to the devices located further down the power line, and so on until the message reaches the target device.
system such as street lighting, where access to an Ethernet, GPRS, or dial-out connection may not be readily available or is cost-prohibitive. Device Requirements The Neuron-hosted devices and host-based ShortStack devices to be installed on a power line repeating network must be enabled for repeating. This is because the devices may need to be used to relay network messages from the SmartServer to devices located further down the power line.
Network Installation Process The following section lists the basic steps required to install a power line repeating network that are detailed in this guide. These steps assume that a Pocket PC is being used as an installation tool. 1. Install the applications on the Pocket PC to be used for collecting device coordinates and Neuron IDs and transmitting them to the SmartServer that is attached to the power line repeating network. 2. Copy the application image files (.
See Chapter 1, Preparing a Power Line Repeating Network for Installation, and Chapter 2, Installing a Power Line Repeating Network, for more information on these steps. Related Reading The documentation for the SmartServer is provided as Adobe Acrobat PDF files and online help files. The PDF files for all the SmartServer documents except for i.LON SmartServer Freely Programmable Module Developer’s Guide are installed in the Echelon i.LON SmartServer program folder when you install the i.
Describes how to duplicate a Scheduler application so that you can create additional pre-configured Event Schedulers to the SmartServer. • Connecting Devices on a Power Line Repeating Network. Describes how to use type translators and Web connections to connect devices on a power line repeating network together and to devices on other networks. • Appendix A – Glossary. Provides definitions for key terms associated with a power line repeating network.
Viewing the i.LON SmartServer ReadMe The i.LON SmartServer ReadMe provides descriptions of known problems and their workarounds. To view the i.LON SmartServer ReadMe, click Start, point to Programs, point to Echelon i.LON SmartServer, and then select i.LON SmartServer ReadMe First. You can also find additional information about the i.LON SmartServer online at www.echelon.com/products/cis/. Using Technical Support If you have technical questions that are not answered by the online help, i.
Region Languages Supported Italian Contact Information Watford Herts. WD18 8YH United Kingdom Phone: 44 0 1923 430200 Fax: 44 0 1923 430300 lonsupport@echelon.co.uk Japan Japanese Echelon Japan Holland Hills Mori Tower, 18F 5-11-2 Toranomon, Minato-ku Tokyo 105-0001 Japan Phone: 81 3 5733 3320 Fax: 81 3 5733 3321 lonsupport@echelon.co.jp China Chinese English Echelon Greater China Rm.
Table of Contents Preface .................................................................................................... iii Welcome......................................................................................................... iv Purpose .......................................................................................................... iv Audience......................................................................................................... iv Models .......................
Entering Device Locations and Neuron IDs............................................ 26 Selecting Devices.................................................................................... 26 Installing Devices with Smart Network Management.............................. 27 Enabling Smart Network Management............................................. 27 Installing Devices.............................................................................. 28 Checking Device Installation Status ...................
Using Type Translators to Connect Devices within a Network ............... 98 Creating a Type Translator............................................................... 98 Selecting Input and Output Points.................................................. 101 Selecting or Creating a Type Translation ....................................... 102 Creating a Custom Scalar-Based Translation ......................... 103 Creating a Custom Rule-Based Translation ............................
xiv Preface
1 Preparing a Power Line Repeating Network for Installation This chapter describes the tasks required for preparing a PL-20 power line repeating network for installation. It describes how to download the Street Lighting Helper sample application used to store and transmit device locations and Neuron IDs to a Pocket PC that is being used as an installation tool. It describes how to upload application image files, external interface files (XIFs), and resource files to the SmartServer.
Preparation Overview Before a PL-20 power line repeating network can be installed, you need to perform a few tasks to prepare your Pocket PC (if you are using one to install the power line repeating network) and the SmartServer to be attached to the network for the installation. If you are using a Pocket PC as an installation tool, you need to install the Street Lighting Helper application (or your own custom Street Lighting Helper application) and the iLONPocketProxy application to your Pocket PC.
5. Connect the Pocket PC to your computer via a USB or serial connection. 6. Set up a sync partnership between your computer to the Pocket PC. Your computer is now connected to the Pocket PC and you can begin copying files. 7. Download or copy the Street Lighting Helper file to your Pocket PC. To copy the file, skip to step 8. To download the file, follow these steps: a. On your computer, browse to the C:\LonWorks\iLon100\unsupported\iLonProxy\Install folder and then double-click the setup.exe file.
4 d. Click Next to start the Street Lighting Helper installation. e. After Street Lighting Helper has been installed, a window appears stating that the installation has been completed successfully. Click Close. If the Application Already Installed dialog opens, click Yes. The Street Lighting Helper application is downloaded to the Pocket PC. f. When the Street Lighting Helper download is complete, the Application Downloading Complete dialog opens. g. Click OK.
h. 8. On the Pocket PC, tap OK. To copy the Street Lighting Helper files from your computer to the Pocket PC, follow these steps: a. On your computer, browse to the LonWorks\iLon100\unsupported\iLonProxy\bin folder on your computer and then copy the StreetLightingHelper.exe, iLonProxyPocket.exe, and iLonProxy.exe files. b. In Microsoft ActiveSync, click Explore, browse to the Mobile Device\Program Files folder on your Pocket PC, and then paste the files. c.
• Application image files (.apb extension). The application that determines how a device functions. • External interface files. The logical interface to a device. It can either be a device interface file (.xif extension) or a device template (.xml extension). • Resource files. Defines the components of the device interface, including network variable types, configuration property types, format types, and functional profiles implemented by the device application.
device. Note that standard, echelon, bas_controller, and mbus_integrator catalogs are pre-loaded in the root/lonWorks/types/folder of the SmartServer flash disk. To copy a resource file to the SmartServer, follow these steps: 1. Follow steps 1–3 in Copying Application Image Files. 2. Access the root/lonworks/types folder on the SmartServer flash disk . 3. Copy the resource file from the location where it saved to the root/lonWorks/types folder on the SmartServer flash disk.
It may take up to a few minutes for the SmartServer to switch to standalone mode. When the SmartServer has switched to standalone mode, the dialog closes and you can continue preparing your SmartServer for the network installation. Network Limitations in Standalone Mode Managing a power line repeating network in standalone mode has the following restrictions: • Network is limited to a maximum of approximately 200 devices. • Network is limited to a single channel.
5. If a network message fails, a data point and its device are marked offline. You can select the Use Minimal Offline Time check box so that all the data points on the offline device with pending network messages (read/write requests, polls, or heartbeats) are marked offline and network messages are not sent to them. This ensures that network performance is not impacted by an offline device.
network topology for all hops in the repeating chain. Use Retry Count You can change the number of times a network message is re-sent when no confirmation is received. The default value is 3 attempts. This means that the proxy agent will attempt to re-send a network message to the target device three times.
2 Installing a Power Line Repeating Network This chapter describes how to acquire the coordinates and Neuron IDs of the devices to be attached to a power line repeating network, including how to use a bar code scanner and Pocket PC to acquire the device data. It describes how to transmit the device data to the SmartServer and install the devices, including how to link a Pocket PC to the SmartServer and use the Pocket PC to upload the device data to the SmartServer and install the devices.
Installation Overview You can use the SmartServer to install a power line repeating network. The installation process entails acquiring the coordinates of the devices to be installed (or descriptive strings uniquely identifying their locations) and the Neuron IDs of the devices. After collecting the device data, you transfer it to the SmartServer, which installs the network upon receiving the device data. If you are using a Pocket PC, which is recommended, the installation process is simple and accurate.
Commissioning a Power Line Repeating Network in the Correct Order You must either commission the power line repeating network all at one time, or commission it incrementally starting from the devices closest to the SmartServer. This is because the SmartServer must commission the repeating devices closest to it so that they can be used to reach and commission the devices located further down the power line.
Installing a Three-Phase Power Line Repeating Network You can install the SmartServer (PL model with external coupling option) on a three-phase system using a passive three-phase coupler. For a three-phase power line repeating network, the cabinet in which the SmartServer is mounted must be placed in a location where the SmartServer is within 100m of a repeating device on each of the three phases.
Acquiring Device Locations and Neuron IDs You can use the Street Lighting Helper application on the Pocket PC to acquire or enter the locations and Neuron IDs of the devices being installed. You can use an internal GPS receiver on the Pocket PC or connect an external Bluetooth GPS receiver to the Pocket PC and acquire the geographic locations (coordinates) of the devices. The coordinates of a device enable it to be associated with a specific location.
6. If you are entering the Neuron ID, click Add. The device specified in the Neuron ID box is added to the device list. a. If the device being added has the same location or Neuron ID as an existing device, the Conflict dialog appears. This dialog prompts you to select whether to replace the existing device, add the new device, or cancel the add operation. b.
2. Select the COM ports on the Pocket PC that are used by GPS receiver and the barcode scanner. Tap More to open the Serial Settings dialog in which you can configure the communication properties for the selected port. The default communication properties are 9600-None-8-1-None. Tap OK. Tip: If you are having trouble connecting the GPS receiver to the Pocket PC, you can set the communication properties on the specified COM port to 4800-None-8-1-None. 3.
2. Configure the following settings: Auto Confirm Enables the current device to be stored automatically in the device list when you scan or enter a valid Neuron ID. This check box is selected by default. If this check box is cleared, you need to tap Add/Save to add a device to the list. Auto Location Enables the GPS coordinates of the current geographical location to be entered into the Location property automatically (provided that a GPS signal is available). This check box is selected by default.
4. Select the Auto Resolve ID Conflict check box to set how duplicate Neuron IDs are resolved. You have the following three choices: • Replace Existing. The device specified in the Neuron ID box is added to the list, replacing the currently listed device that has the same Neuron ID. This is the default. • Duplicate Entry. The device specified in the Neuron ID box is added to the list, and the device in the list with that same Neuron ID remains on the list. • Don’t Store.
3. Create a GPRS connection on the external GSM modem. See the i.LON SmartServer User’s Guide for information on how to do this. Using iLonProxyPocket The iLonProxyPocket application is used to transmit the device file created with the Street Lighting Helper program to the SmartServer. The iLonProxyPocket application serves as proxy for HTTP requests (Web server/SOAP) between the Pocket PC and the SmartServer. You can transmit SOAP requests using either a serial connection to the console port on the .
3. Verify that the Listen on Port property is set to 80. This is the Web services port used by the Street Lighting Helper application on the Pocket PC to send SOAP requests. 4. Select the serial port used to connect the Pocket PC to the SmartServer. 5. • If you are using a RS-232 serial connection, accept the default port, which is COM1. • If you are using a Bluetooth connection, select any available port.
4. Verify that the Listen on Port property is set to 80. This is the Web services port on the local Pocket PC device. 5. In the Host property under Resend to LAN, enter the IP address or TCP/IP host name of the SmartServer. 6. In the Port property under Resend to LAN, enter the port that the SmartServer uses to transmit and receive HTTP and SOAP messages. The default value is 8080, but you may change it to any valid port number.
3. Verify that you have exited the SmartServer console application if you were accessing it via Telnet. Otherwise, the SmartServer cannot receive the device data from the Pocket PC because the console port is blocked. 4. Tap Send. A dialog appears informing you that the transmission of the device data has started. The device data is sent to the SmartServer via the iLonProxyPocket application. 5.
6. Once the SmartServer receives the device data, it discovers the repeating chain for each device and then commissions the devices. It then downloads the application image files to the devices and loads the device interface (XIF) files (if they have been uploaded on the SmartServer flash disk) to the devices, re-commissions the devices, sets the devices’ applications online, writes the configuration properties to the devices, and resets the devices, which starts their applications.
3. Enter the following device properties: Name Enter a name for the device that is unique to the network. File Name: Displays the full path of the LonMark external interface (.XIF file) or template (.XML file) selected for the device. If you select a LONWORKS template, the program ID of the device is also displayed. Location Select External because you are adding an application device that can be physically installed on a network.
file contains all the functional blocks, network variables, and configuration properties shown on the tree view at the time the device template was created. The .XML file can contain dynamic functional blocks and dynamic network variables. See the i.LON SmartServer User’s Guide for more information on creating device templates. 4. Click OK. The device is added to the bottom of the tree of its parent channel. 5. Repeat steps 1–4 for each device on the network to be installed.
Installing Devices with Smart Network Management Once you have selected the devices to be installed, you use the Smart Network Management feature on the Setup - LON Device Driver Web page to install them. With this option, the SmartServer asynchronously sets the following device properties to the states it determines to be desired: • • • • • • program ID. commission status (commissioned or decommissioned). application state (online or offline). application image. device template (external interface).
Installing Devices After enabling smart network management for all the applicable device properties, click Submit. The SmartServer then does the following for each device you are installing: 1. Fetches the program ID of the device (if the Smart Network Management check box is selected for the Program ID property). 2. Downloads the application image file to the device (if the Smart Network Management check box is selected for the Application Image property).
3. The management commands submitted for all devices and their statuses appear in a table. By default, the names of the first 20 devices listed in the tree in the left frame are listed in descending alphabetical order and the commands executed on them are listed in descending chronological order (most recent to earliest). You can sort the management commands by clicking the column headers.
30 Installing a Power Line Repeating Network
3 Maintaining a Power Line Repeating Network This chapter describes how to analyze and debug a power line repeating channel using the Power Line Repeating Analysis Web page on the SmartServer. It explains how to add, upgrade, replace, decommission, place offline, test, and delete devices with the SmartServer. It describes how to switch the network to LNS management mode and synchronize the network to an LNS database so that it can be managed with an LNS application such as the LonMaker tool. i.
Maintenance Overview You can perform routine maintenance to update, repair, and optimize an installed power line repeating network. You can use the SmartServer to maintain the network and its devices. For example, if a device fails, you can replace it on the physical network and then logically replace it on the SmartServer, preserving the device’s configuration.
Alternatively, you can click Setup and then click Power Line Repeating Analysis. 2. The Power Line Repeating Analysis Web page opens. The rows in this Web page represent established repeating paths between the listed devices. The target device in a repeating chain is listed furthest to the right. The current chain of repeating devices used to relay messages to the target device are listed to the left of the target device.
and click all other devices to be viewed, or hold down SHIFT and select another device to view the entire range of devices. 3. You can identify repeating devices (devices that relay messages to devices located further down the channel) and target devices (the destination device in a repeating chain) by observing whether there is a device listed in the column to the right. If there is no device listed in the column to the right, that device is a target device.
Last Time Reached Frequency in use Signal Strength Signal Margin Available Proxies Failure History (24h). The time at which the device last responded to a network message. The frequency carrier of the signal at the hop (Primary or Secondary). For more information on the use of these frequency carriers on a LONWORKS power line channel, see the LONWORKS PLT-22 Power Line Transceiver User’s Guide (110kHz - 140kHz Operation).
Commission Status Indicates whether the device has been commissioned. The values that may appear in this field and their colors depend on whether the device has successfully been installed (black), is being installed (orange), or has an error (red). Black (Installed) • Commissioned. The device has successfully been installed. Orange (Installation in Progress) • Pending Commission. The SmartServer has identified that it needs to commission the device. • Pending Download.
Online Status Indicates the current device state. The values that may appear in this field and their colors depend on whether the device has successfully been installed (black), the device is being installed (orange), or the device is not running because of an error (red). Black (Installed) • Up. The device has been commissioned, it is communicating with the SmartServer, and it does not have any hard message failures. Orange (Installation in Progress) • Nul.
b. The Online Measurement dialog opens. c. This dialog displays the following statistics: Time Stamp Frequency in Use Signal Strength Signal Margin 38 Displays the time at which the device last responded to a network message. Displays the frequency carrier of the signal at the hop (Primary or Secondary). For more information on the use of these frequency carriers on a LONWORKS power line channel, see the LONWORKS PLT22 Power Line Transceiver User’s Guide (110kHz - 140kHz Operation).
7. Optionally, you can view statistics related to signal at the hop between the selected device and all the proxies (repeating devices) that can be used to relay messages to that device, including the current proxy. To view the available proxies for a given device, follow these steps: a. Right-click the device and select Show Available Proxies in the shortcut menu. b. The Show Available Proxies dialog opens. c.
Signal Margin Failure History Last Time Reached The amount that the signal is greater than the noise level at the hop in decibels (dB). Provides a historical list of the 45-minutes intervals since the SmartServer was rebooted in which a device failure (if any) was reported.
1. Copy the .apb file of the new application and the .xif file of the new external interface (if required) to the root\LonWorks\import folder on the SmartServer flash disk. 2. Click Driver. 3. Select one or more devices from the tree to be upgraded. 4. • To select one device, click that device.
5. 42 d. Select the application image to be downloaded to the devices. e. Click OK to return to the Setup - LON Device Driver Web page. If the external device interface has changed, you need to load a new XIF file for the device onto the SmartServer. To do this follow, these steps: a. In the Template property, click the button to the right. b. The Choose File dialog opens.
c. Expand either the LonMark (XIF) or Template folder depending on whether you are using a .xif or .xml file for the external device interface. If the device being upgraded is located in the LNS tree, the Template folder is not available. d. Expand the subfolders containing the XIF file to be loaded onto the SmartServer and then click the XIF file. e. Click OK to return to the Setup - LON Device Driver Web page. 6. Click Submit. 7. Download the application image to the selected devices.
8. Activate the XIF files for the devices (if necessary). To do this, right-click one of the selected devices in the SmartServer tree, point to Manage, and then click Activate Template in the shortcut menu. Alternatively, you can clear and then select the Smart Network Management check box to the left of the Template property in the Setup -LON Device Driver Web page and then click Submit. 9. To check the status of the device upgrade, open the LON Command Queue Web page.
1. Attach the replacement device to the network by applying power to the device and attaching its network connection as documented by the device manufacturer. 2. Start the Street Lighting Helper application. To do this, tap Start, tap Programs, tap Street Lighting Helper. The Street Lighting Helper application opens. 3. Acquire or enter the location and Neuron ID of the replacement device. 4. Connect the Pocket PC to the SmartServer as described in Chapter 2. 5.
4. You can acquire the Neuron ID of the replacement device using a service pin or you can manually enter it. • If you are using the service pin method, press the service pin of the device. The Neuron ID and program ID of the device are both entered into the Incoming Service Pin Messages box and they are input into the Neuron ID or LUID and Program ID boxes, respectively. • If you are using the manual entry method, enter the 12-digit hex string of the device in the Neuron ID or LUID box. 5. Click OK.
2. 3. Select one or more devices from the tree to be decommissioned. • To select one device, click that device. • To select multiple devices and perform a batch upgrade, click one device and then either hold down CTRL and click all other devices to be decommissioned or hold down SHIFT and select another device to decommission the entire range of devices. The Setup - LON Device Driver Web page opens. Right-click a selected device, point to Manage, and click Decommission.
placed offline, it may cause communication failures for multiple devices. In addition, setting a device offline may affect network performance if the device was polling prior to being set offline. To set a device offline, follow these steps: 1. Click Driver mode. 2. Select one or more devices to place offline. To select one device, click that device.
2. The Query Status dialog opens. 3. This dialog lists the following network statistics. Non-zero values indicate that the device was unable to receive and/or respond to a message. Small values are expected; rapidly increasing values may indicate a problem. If the device is consistently reporting failures and new errors are being logged, the device may have a configuration problem or the network may be overloaded. i.
Name The name of the device in the following format: // Unique ID Displays the Neuron ID of the device as a 12-digit hex string. The Neuron ID is a unique 48-bit number burnt into the device’s Neuron chip. Transmission errors typically indicate cyclical redundancy check (CRC) errors. CRC errors are commonly caused by electromagnetic interference (EMI) on the channel.
3. Click Submit. Deleting Devices You can delete a device to logically remove it from the network. To do this, right-click the device, and then click Delete. The device is removed from the SmartServer. If you delete a device that was serving as a repeating agent, the SmartServer automatically identifies alternate repeating devices to relay network messages to those target devices that were using the deleted device in their repeating chains.
• If the LNS database is not empty, all the LONWORKS channels and devices on the SmartServer tree are merged into the database. The domain length and domain ID properties in the database are not changed. After the LNS database has been updated, you can synchronize an LNS application such as the LonMaker tool to the LNS database and then use it to manage the network.
database. Enter your login information for accessing the LNS Server via the LNS Proxy Web service and then click OK. The default user name and password is ilon, but you may have entered a different user name/password in the Echelon i.LON Enterprise Services installer. 7. If IP-852 routing is licensed on your SmartServer, a dialog appears informing you that you need to reboot your SmartServer in order to use it as an IP-852 router. Click Close. 8.
network database name that is unique to the selected LNS Server (the box in the LNS Network property will be highlighted red), and then click Submit. 9. The name of the network changes to the name you entered in the LNS Network box in step 8. If you selected an existing LNS network database on your computer, the network icon also changes to an LNS server icon. 10.
4 Controlling a Street Lighting Network with the Scheduler Application This chapter describes how to use the Scheduler application on the SmartServer to control the devices on a street lighting network. It explains how to create exception schedules and how to add events to the schedules so that devices such as luminaries can be turned on and off based on calculated sunrise and sundown times.
Scheduling Overview The SmartServer contains an Event Scheduler application that you can use to schedule data point updates (called events) to occur at sunrise and sundown, or a configured amount of time before or after. This means that, for example, you can schedule luminaires to turn on at sundown, dim at the end of the evening rush hour, brighten at the start of the morning rush hour, and then turn off at sunrise. Each Event Scheduler includes day-based daily schedules and date-based exception schedules.
resides or manually specify the time. After you have stored the time of day on the SmartServer, you enter the geographic coordinates of the SmartServer. Based on this information, the astronomical position sensor application on the SmartServer calculates the position of the sun relative to the SmartServer and stores this information in nvoElevation_005 and nvoAzimuth_005 SNVT_angle_deg data points.
5. The Setup – TimeService Web page opens. 6. In the Time Synchronization Mode property, select the frequency in which the SmartServer is synchronized to the SNTP server. You have four choices: • Automatic. The SmartServer is synchronized every 1 to 15 minutes and remains within 100ms of the SNTP server. This is the default, and it can be used for both LAN and dial-out (modem and GPRS) connections. • Sync when dial-up is active.
Alternatively, you can click Setup and then click Time to configure the time settings on the local SmartServer. 2. The Setup – Time Web page opens. 3. In the Timezone property, select the time zone in which the SmartServer is located. 4. In the Date and Local Time property, enter the time and date to be stored in the SmartServer's real time clock. You may need to refresh the Web page to view the current time. 5. Click Submit to save the changes.
• 60 Create or open an Event Scheduler application following the steps described in Creating Event Schedulers later in this chapter, and then click the Real-Time Clock / Astronomic Position Sensor icon in the Scheduler: Configure Web page. 2. The Real Time Clock: Configure Web page opens. 3. Configure the following properties for the real-time clock and astronomical position sensor on the SmartServer: 4.
8. A dialog opens and displays the current sunrise or sundown time stored in the data point in the following format: YYYY-MM-DD hh:mm:ss. Creating Event Schedulers You can create a single Event Scheduler with multiple exception schedules to control a street lighting network.
4. The Add Functional Block dialog opens. 5. Select the Scheduler functional block from the Static or Dynamic LonMark folder. The folder available in the dialog depends on whether the SmartServer is using the static v12 external interface (XIF) file or the dynamic v40 XIF file.
• If the SmartServer is using the dynamic v40 XIF file, you can select the Scheduler functional block from either the Static or the Dynamic folder. To select the Scheduler functional block from the Dynamic folder, expand the Dynamic icon, expand the root/lonworks/types folder, expand the bas_controller folder, select the user-defined functional profile template (UFPT) for the Scheduler, enter a name for the functional block such as “Scheduler 1”, and then click OK. i.
6. A functional block representing the Scheduler application and all of its static data points are added to the bottom of the i.LON App (Internal) device tree, and the Scheduler: Configure Web page opens application opens in the application frame to the right. Note that construction symbol overlaid onto the Scheduler application icon in the upper-left hand corner of the Web page indicates that the application has not been configured yet. 7.
2. The Scheduler: Data Points Web page opens. Click the data points to be updated by the Event Scheduler from the SmartServer network tree. The selected data points are added to the Web page; any presets defined for the selected data points are displayed to the right. 3. Optionally, you can click the Stagger Delay box to specify the period of time (in seconds) that the Event Scheduler will wait before updating the specified data point at each schedule interval.
• c. 5. 66 To delete an existing preset, click Delete at the top, select the preset to be deleted from the list of presets, and then click Delete next to the list of presets. The preset is removed from the Scheduler: Data Points Web page. Click Close. Optionally, you can edit the values of existing presets. To do this, follow these steps: a. Click the preset to be edited. The Edit Presets dialog opens. b.
Creating Daily Schedules You can set the daily schedules for the Event Scheduler. This entails defining for which days a schedule is applicable and creating events. Defining Schedules By default, the Event Scheduler has two schedules: weekday (Monday–Friday) and weekend (Saturday–Sunday). You can create separate schedules for individual days and modify for which days the schedules are applicable. To define the scope of the schedules, follow these steps: 1.
This dialog functions similarly to the Scheduler: Daily Schedules Web page, except that it also lets you view the current daily schedules as you group days into different schedules. It lists two schedules: Weekday and Weekend. The Monday–Friday check boxes are selected in the daily schedule, and the Saturday–Sunday check boxes are selected in the weekend schedule. This means that the five weekdays use the same daily schedule, and the weekend days use a separate weekend schedule.
You can also re-name any of the daily schedules. When you are done editing and re-naming the daily schedules, click Close. 4. Click Submit. Creating Events You can add and edit events to the daily schedules. To do this, follow these steps: 1. From the Scheduler: Daily Schedules Web page, click the box corresponding to the day and time for which an event is to be created.
70 3. In the Time box, enter the exact time the event is to occur if it is different than the default time, which is on the hour of the selected time. For example, to create an event that occurs at 7:15 A.M. instead of the default 7:00 A.M, enter 07:15. 4. In the Value box, select the preset to be used to update, at the specified time, the values of all the data points added to the Event Scheduler that have that preset defined for them.
7. Repeat steps 2–6 to schedule all the events to be executed by the Event Scheduler. Note that to create additional events within a given hour, you can only right-click the Time column and click Add Event to open the Add Event dialog. You can create up to one event per minute. 8. Click Close. The events you created are listed under each day of the daily schedule you edited.
1. In the Scheduler: Configure Web page, click the Exception Schedules icon. 2. The Scheduler: Exception Schedules Web page opens. 3. Right-click the date that will be the start date for the exception schedule, point to Add Exception, and then click New Exception on the shortcut menu. 4. The New Exception dialog opens. 5. Enter a descriptive name for the exception. The default name is the selected start date in the following format: --. 6.
specific days such as every Monday, every Tuesday, and so on; every weekday or every weekend day; and every other day, every third day, and so on up to every sixth day. • Clicking Specific lets you apply the exception to specific months such as January, February, and so on up to December in addition to the monthly options offered by clicking Standard.
7. Specify the range of dates for which the exception schedule is used. Specify the start and end dates in the From and To properties, respectively. Tip: You can create an exception that occurs every day from the specified start time to the specified stop time instead of specifying actual start and end years, months, and dates. In the To and From properties, select Every Year, Every Month, or Every Day in the year, month, or day boxes based on when this recurring exception is to begin and end.
8. Under Recurrence, select the monthly and daily recursions from the Monthly and Daily lists. The default monthly recursion is every month. This means that if you do not specify a monthly recursion, the events will occur every month within the specified range. The default daily recursion is every day. This means that if you do not specify a daily recursion, the events will occur every day within the specified range. 9. Click Close.
Creating Events This section generally describes how to create events in an exception schedule. The subsequent section, Demonstrating a Street Lighting Schedule, includes the specific events you can create for scheduling a street lighting network. To create events in an exception schedule, follow these steps: 76 1.
3. Click anywhere in the row under the Schedule, Event Time, Value, or Priority columns at the time the event is to occur. The Add Event dialog opens. Alternatively, you can right-click a time under the Time column or right-click the column to the right and click Add Event on the shortcut menu to open the Add Event dialog. 4. Select the Show Advanced check box. A Function field appears in the dialog. 5. In the Function box, select the Sunrise ( ) or Sundown ( ) icon.
6. If the event is to occur sometime before or after sunrise or sundown, enter that period of time in the Offset box. To schedule an event to occur before sunrise or sundown, enter a negative value; to schedule an event to occur after these times, enter a positive value. For example, if you want a ON event to occur 30 minutes after sundown, enter 00:30. If you want a DIMMING event to occur 15 minutes before sunrise, enter -00:15. 7.
11. Create an #UNLOCK event at the time you want lower priority events to be able to update the data points. To do this, you add an event, select the function, specify the time, select #UNLOCK in the Value box, and then click Close. The events in the exception schedule are highlighted teal and the exception schedule is updated to reflect the lower priority events that are now scheduled to occur after the #UNLOCK event. 12. Click Close.
Demonstrating a Street Lighting Schedule This section demonstrates how you can control a street lighting network using a single Event Scheduler that includes one daily schedule and one exception schedule for weekdays, and one exception group that includes exception schedules for weekends and holidays. The following briefly describes how the street lighting network is controlled on weekdays and weekends/holidays. • Weekdays.
Light Level ON_100 Priority 255 ON_100 Priority 255 100 ON_60 Priority 255 ON_60 Priority 255 60 #UNLOCK #UNLOCK OFF Priority 220 0 Time SunRise AM Rush Hour Starts SunDown AM Rush Hour Ends PM Rush Hour Starts PM Rush Hour Ends Weekday Daily Schedule Weekday Exception Schedule Creating the Weekday Daily Schedule The weekday daily schedule turns on the lights at the start of the evening rush hour, dims them at the end of the evening rush hour, brightens them at the beginning of the morning ru
o • If the end of the evening rush hour occurs before sundown, the ON_100 event is never executed. This is because the weekday daily schedule executes an ON_60 event with a priority of 255 at the end of the evening rush hour. The ON_60 takes precedence by virtue of it being the most recent event between two events with the same priority. At the end of the evening rush hour (for example, 19:00), an ON_60 event.
3. Enter a descriptive name for the exception such as “Weekday Exception”. The default name is the selected start date in the following format: --. 4. Click Standard to expand the dialog to show the Recurrence property. This lets you apply the exception to every month and every weekday in step 6. 5. In the From and To properties, specify the start and end dates of the exception. 6. Under Recurrence, select Every Month from the Monthly list.
Creating the Weekday Exception Schedule To create the schedule for the weekday exception you created in the previous section, follow these steps: 84 1. Click one of the yellow-highlighted weekday dates in the calendar to schedule the events to occur on the range of dates specified in step 5 in the previous section. The Edit: dialog opens. 2. Create an #UNLOCK event at the start of the morning rush hour (05:00 in this example). To do this, follow these steps: a.
3. Create an OFF event that occurs at sunrise. To do this, follow these steps: a. Click anywhere in the row under the Schedule, Event Time, Value, or Priority columns at the time the event is to occur. The Add Event dialog opens. Alternatively, you can rightclick a time under the Time column or right-click the column to the right and click Add Event on the shortcut menu to open the Add Event dialog. b.
4. 86 g. Click Close to return to the Edit: dialog. h. You will observe that the exception schedule has been updated to show the sunrise event (priority 220) and to hide the lower priority rush hour events in the daily schedule (priority 255) that are scheduled after sunrise. These lower priority events in the daily schedule are locked out until the exception schedule executes an #UNLOCK event. Create an #UNLOCK event that occurs at sundown. To do this, follow these steps: a.
d. In the Function box, select the Sundown ( ) icon. The calculated sundown time appears in the Time box, which becomes read-only, and an Offset field is added to the dialog. Verify that the Offset field is set to 00:00. e. In the Value box, select #UNLOCK. f. In the Priority box, enter a priority that is lower than the 255 priority used for the weekday daily schedule (this example use a priority of 220).
5. Click Close. The range of weekday dates on which the exception occurs is highlighted teal in the calendar on the Scheduler: Exception Schedules Web page. 6. Click Submit. Creating the Weekend and Holiday Exception Schedules You can create a schedule that controls the street lighting network on weekends and holidays. This entails creating an exception group that includes an exception that recurs every weekend and exceptions for each holiday that occurs on a weekday in which there is no rush hour.
3. In the Advanced property located directly below the Private property, click the blue arrow ( to expand the dialog to show options for adding, deleting, and editing additional exceptions included under the current exception. Add a new exception following these steps: ) a. Click Add to create an exception group and add new exceptions for weekday holidays to the group.
d. Repeat steps a–c for additional weekday holiday exceptions to be added to the exception group. Notes: 4. 90 • You can click the arrows to scroll through the various exception instances. You can edit the scope (private or public), dates, and recursions for the selected instance. • You can click Delete to remove the selected exception instance from the Event Scheduler. Click Close.
Creating the Weekend/Holiday Exception Schedule To create the schedule for the weekend/holiday exception you created in the previous section, follow these steps: 1. Click one of the red-outlined weekend dates or weekday holidays in the calendar to schedule the events to occur on the specified range of dates. The Edit: dialog opens. 2. Create an OFF event that occurs at sunrise. To do this, follow these steps: 3. a.
92 e. The Priority box will have the priority of 210 that you entered in step 2. f. Click Close to return to the Edit: dialog. The exception schedule shows the events scheduled in it. 4. Click Close. The range of weekend dates remain outlined red and the weekday holiday dates remain highlighted teal in the calendar. 5. Click Submit.
Copying Event Schedulers to other SmartServers Once you create an Event Scheduler with the appropriate exceptions, you can save the i.LON App (Internal) device as a template. The template will include the current configuration of the Event Scheduler, including the events, data points, and presets. Using device templates, you can add pre-configured Event Schedulers to other SmartServers.
4. Click OK. An .XML file documenting the driver properties of the device and the driver properties of its functional blocks and data points is created, and it saved to the SmartServer flash disk at the path specified in step 3. Note that it takes a few minutes for the SmartServer to create the device template. 5. When the template has been created, a message appears above the application frame informing you that the template is ready. 6. Click Submit.
7. Copy the template from the location where it was saved in step 5 to the root/config/template/lonworks directory on the SmartServer flash disk. Creating an SmartServer Device from a Template After you create a SmartServer device template, you can use it to configure another SmartServer. The new SmartServer device is created with the same general and/or driver properties as the template.
96 5. Click OK. 6. Click Submit. The new SmartServer device and all of its functional blocks and data points are added below the LON channel. The default general/or driver properties of the devices match those of the selected template. You can use these default settings or modify them as necessary.
5 Connecting Devices on a Power Line Repeating Network This chapter describes how to use type translators and Web connections to connect devices on a power line repeating network together and to devices on other networks. i.
Connecting Devices Overview You can connect the devices on a power line repeating network though the SmartServer gateway using type translators, Web connections, and freely programmable modules (FPMs). These types of connections provide an alternative to LONWORKS connections, which are not supported on a power line repeating network (devices on a power line repeating network cannot initiate network messages and communicate in a peer-to-peer manner).
1. Click General above the tree view in the left frame of the SmartServer Web interface. 2. Expand the network icon in the SmartServer tree, and then expand the LON channel to show the i.LON App (Internal) device. 3. Right-click the i.LON App (Internal) device and then select Add Functional Block in the shortcut menu. 4. The Add Functional Block dialog opens. 5. Select the Type Translator functional block from the Static or Dynamic LonMark folder.
• 100 If the SmartServer is using the dynamic v40 XIF file, you can select the Type Translator functional block from either the Static or the Dynamic folder.
6. A functional block representing the Type Translator functional block application and all of its static data points are added to the bottom of the i.LON App (Internal) device tree, and the Type Translator: Configure Web page opens in the application frame to the right. Note that construction symbol overlaid onto the Type Translator functional block application icon in the upper-left hand corner of the Web page indicates that the application has not been configured yet. 7. Click Submit.
list of output points. To show the output data points, select the Show Outputs check box. You ) on the can access the list of output by clicking the Output data point icon ( right side of the Type Translator: Configure Web page. 4. Click Submit. Selecting or Creating a Type Translation Type translations specify the conditions in which the values of input points are translated to output points.
rule specifies the value to be copied to the output points. Once you create a custom type translator rule, you can select it from the list of defined rules and use it for other translations. Creating a Custom Scalar-Based Translation You can create a custom scalar-based translation with the Type Translator. This is useful if you need to perform some scaling on the value of the input point before it is translated to the output point.
104 a. Click anywhere in the Copy rule to change the default input or output points, scale the input point, or add an offset. b. If you added more than one input point, you can change the default input point (the first input point added to the type translator) by clicking it and then selecting a different input point from the list. c. If the input point is a structured data point, a list box is added to the right of the input data point.
g. If the output point is a structured data point, a list box is added to the right of the output data point. Select whether to evaluate a field within the structure or the entire structure. By default, the entire structure is evaluated. 7. Click Submit. 8. To add another case to the type translation, right-click the top-level ALWAYS case, click Copy on the shortcut menu, right-click the top-level ALWAYS case again, and then click Paste on the shortcut menu.
c. Select one of the following comparison functions: equal to (default), not equal to, greater than, less than, greater than or equal to, or less than or equal to. Note: If you are evaluating a structured data point as a whole, you can only select the equal (=) or not equal to (!=) comparison functions. d. Enter a comparison value. The default comparison value is 0.
7. Click Submit. 8. You can add another case/rule to the current translation by adding a new one or copying an existing one. The copying method is recommended for creating more complex rule-based translations. The method you choose depends on whether you want to re-use the previous case/rule.
You can use the View – Data Points Web page to enable the type translator and control the switch device. In this Web page, you can add the SNVT_switch data points of the type translator, the switch, and the luminaires. You first set the state of the “Enable” data point on the type translator to ON. You can then change the state and/or value of the “switch ON_OFF” data point on the switch device, and the luminaires will be updated accordingly.
Connecting Repeating Devices on the Same Network To create an internal binding between two repeating devices on the same power line repeating network, follows these steps: 1. From the local SmartServer tree on the left frame, right-click a source data point on the SmartServer attached to the power line repeating network and then click Add Binding in the shortcut menu. 2. The Configure – Web Binder Web page opens and the hostname of the local SmartServer appears in the application frame to the right. i.
3. From the Webbinder Destinations tree on the right frame, expand the SmartServer Webbinder destination node, expand the network icon, expand the LON channel, expand the device and functional block containing the desired target data point, and then click one or more compatible target data points. 4. Click Submit. References to the target data points are added underneath the source data point in the local SmartServer tree on the left frame.
2. a. Right-click the LAN node, point to Add Host, and then click i.LON SmartServer on the shortcut menu. b. The Setup – Remote i.LON SmartServer Web page opens, and a SmartServer node is added to the tree view below the LAN node. c. Enter the SOAP/HTTP properties of the SmartServer attached to the power line repeating network. See Chapter 3 of the i.LON SmartServer User’s Guide for more information on configuring these properties. d. Click Submit.
112 3. The Configure – Web Binder Web page opens and the hostnames of the local SmartServer (the SmartServer attached to the FT-10 or PL-20 non-repeating network) and the SmartServer attached to the power line repeating network, which are collectively referred to as Webbinder Destinations, appear in the application frame to the right.
5. Click Submit. References to the target data points are added underneath the source data point in the local SmartServer tree on the left frame. Testing Web Connections To test that your Web connections are updating the target data points when the value of the source data changes, follow these steps: 1. Click View and then click Data Points. The View – Data Points Web page opens. 2. Close the graph by clicking the ‘X’ in the upper right-hand corner of the application frame. 3.
5. Change the value of the source data point. Observe that the target data point has the same value as the source data point. The Web connection keeps these data points synchronized. For more information on using the Web Binding application, including how to validate, delete, and add attachments to bindings, see Chapter 4 of the i.LON SmartServer User’s Guide.
Appendix A Glossary This appendix provides definitions for key terms associated with a power line repeating network. i.
Glossary Alternative Proxy A repeating device that can directly communicate with a given target device if the current proxy agent fails. Direct Communication State when a repeating device can directly communicate with the SmartServer. A device that has direct communication does not use a repeating chain to receive a network message from the SmartServer.
target device or the next repeating device in the repeating chain. A repeating device may also be referred to as a repeating agent. For a LONWORKS device to function as repeating device, application device repeating must be installed on the device. For more information on installing application device repeating on your LONWORKS devices, contact your Echelon sales representative. Signal Strength The attenuation (reduction in amplitude and intensity) of a signal.
