® @echelon CRD 3000 Integrator’s Guide 078-0439-01F
Echelon, LONWORKS, i.Lon, LonTalk, Neuron, 3120, 3150, 3170, and the Echelon logo are trademarks of Echelon Corporation that may be registered in the United States and other countries. Other brand and product names are trademarks or registered trademarks of their respective holders.
Welcome Intelligent street lighting uses electronic ballasts, power line communications hardware, and local network controllers that are interconnected with specialized control and reporting software. A street lighting network establishes two-way communications with each lighting fixture so that you can control the lighting level of each fixture, turn it on and off, and monitor its condition.
FCC Compliance Notice Federal Communications Commission Radio Frequency Interference Statement This equipment has been tested and found to comply with the limits for a Class B digital device pursuant to Part 15 of the FCC Rules, per sections 15.107 and 15.109. These limits are designed to provide reasonable protection against harmful interference in a residential installation.
CRD 3000 Planning Checklist This checklist is intended for installers who will use the CRD 3000 power line to RF bridge to extend outdoor range in outdoor lighting systems. To better differentiate the CRD 3000 from the CPD 3000 and CPL 4000 devices, the checklist below calls the CRD 3000 an SLB (Street Light Bridge). The CPD 3000 and CPL 3000 devices are referred to as OLCs (Outdoor Lighting Controllers). Any power line device using the ISO/IEC 14903-3 standard may be used with the SLB. 1.
. If the lighting circuit will contain only lighting loads that are controlled using power line based controllers like the CPD 3000 or CLP 4000 you should expect solid communication across dedicated lighting segment. If there are other devices attached to the same electrical service, such as traffic controllers, you may need to use a filter to isolate these devices from the outdoor lighting circuits. 7.
Table of Contents Welcome .................................................................................................................. iii Audience.................................................................................................................. iii Related Documentation ....................................................................................... iii FCC Compliance Notice ........................................................................................
Defining the Media Access Protocol ........................................................... 35 Preparing the Segment Controller ............................................................. 36 Preparing the CRD 3000 Street Light Bridge Modules......................... 36 Preparing the Luminaires ........................................................................... 37 Device Discovery ............................................................................................ 37 Defining Repeating .
The Example Schedule ................................................................................. 98 Copying Event Schedulers to Other Segment Controllers ........................... 99 Interoperable Interface for the Street Light Bridge .......................... 101 Interface ................................................................................................................102 Output Data Points .....................................................................................
1 Introduction This chapter introduces the Echelon Street Lighting solution.
The Echelon Street Lighting Solution Energy and maintenance costs are increasing for municipal street lighting. Studies show that the electricity used for street lighting can account for up to 40% of municipal electric bills. With an estimated 90 million street lights in Europe and 63 million in North America, efficient use of energy for street lighting is important, both for economic reasons and for environmental reasons.
Figure 1. A Basic Street Lighting Network Because the CRD 3000 Street Light Bridge module provides both ISO/IEC 149083 Control Network Protocol power line communications and IEEE 802.15.4 (2.4 GHz) radio frequency (RF) wireless communications, the street lighting network can leverage the existing power line circuits to communicate with the luminaires, and create small RF bridges to bypass power line gaps created service distribution transformers.
information about the Segment Controller. See the SmartServer User's Guide for more information about the SmartServer. Luminaires and Street Light Controllers Each street light in an intelligent street light network must be able to communicate over a LONWORKS power line communications channel. Thus, each luminaire must include a LONWORKS power line communications chip (such as an Echelon Power Line Smart Transceiver).
RF Repeating Channel 1 Lamp 1 Lamp 2 2 Lamp 3 Lamp 4 Lamp 5 (Repeater) Lamp 6 PLC PL Channel PL Repeating Channel Figure 2. An Example Repeating Network Each time that a message is repeated, on either channel type, is a repeater hop. A message within a street lighting network must be able to reach its destination in eight or fewer hops.
Lamp failures can be identified quickly, reducing average lamp downtime by as much as 90%. Alarms can be triggered when lamp voltage exceeds recommended levels, preventing future lamp failures. Reduction in replacement costs for aging lamps – for one installation that uses electronic ballasts that regulate high-pressure sodium lamps, lamp replacement costs were reduced by 20% by replacing the lamp before its power consumption became uneconomical.
offering far longer operating life, have helped the city improve its closed-circuit television (CCTV) image capturing system for increased public safety.3 As stated by the city of Oslo, Norway, in November 2004, cities that take advantage of today’s new technologies and solutions can reduce the overall costs associated with streetlight networks by almost 50%, while increasing the quality of service and safety.
2 Installation for the Street Lighting Solution This chapter describes installation for a street lighting network. See the CRD 3000 Planning Checklist before you install a street light bridge.
Overview The process for installing a street lighting network includes the following basic tasks: Install a Segment Controller Install luminaires Install CRD 3000 Street Light Bridge modules, as needed For a typical new installation, you install the Segment Controller first. However, you could install luminaires (or have already existing luminaires), and then install the Segment Controller.
High-Voltage Warning ! High-voltage installation must be performed only by a qualified service person. ! Hochspannungs-Installation darf nur von einem qualifizierten Servicetechniker durchgeführt werden. ESD Warning ! This product contains components which are sensitive to static electricity. ! Dieses Produkt beinhaltet Komponenten, die empfindlich für eine statische Aufladung sind.
Safety Warning ! Fuse F1 in the Street Light Bridge uses a Littleman rated, 300 VAC, 10 A, SLOBLO. This device has no user-serviceable parts. Only qualified personnel should perform the procedures in this guide. ! Sicherung F1 im Street Light Bridge ist ein Littleman Sicherung bewertet 300 VAC, 10 A, SLO-BLO. Dieses Gerät hat keine vom Anwender zu wartenden Teile. Nur qualifiziertes Personal sollte die in diesem Handbuch beschriebenen Verfahren durchführen.
START OR Install Luminaires Install SmartServer Install luminaires Place Segment Controller in Acquisition Mode to discover luminaires and SLB modules 1 2 Each lamp turns on Install Luminaires Install SmartServer Install luminaires Segment Controller discovers as many lamps as it can, and turns each one off to indicate that communications are established Segment Controller discovers lamps and turns each off YES All Lamps Off? NO Install SLB Install a Street Light Bridge module on a previousl
Step 1: Install the Segment Controller Configure the Segment Controller (see Chapter 3, Setting Up the Segment Controller) and install it at any convenient location for the street lighting solution. For example, you can install it on one of the street light poles or utility poles (typically below the neutral space) within the area for the street lighting solution. Ensure that the Segment Controller has power. Place the Segment Controller into Acquisition Mode; see Automatically Discovering Devices.
assume that the Segment Controller cannot communicate with the luminaire, and you should proceed to step 3. If you install the luminaires before the Segment Controller, the Segment Controller will discover and commission all of the luminaires; however, this process could take some time. After an installed luminaire is discovered and commissioned by the Segment Controller, the lamp should turn off.
communication with a previously installed module; see Verifying Successful Installation. If the newly installed CRD 3000 Street Light Bridge module does not have a sufficient RF signal with a nearby CRD 3000 Street Light Bridge module, reinstall the CRD 3000 Street Light Bridge module in a different location (perhaps closer to or within a different line-of-sight of a previously installed CRD 3000 Street Light Bridge module).
If a luminaire or CRD 3000 Street Light Bridge module fails, you can use the Segment Controller Web pages to determine which device is bad. You can decommission the failing device, physically replace the failing device, assign the new device’s Neuron ID to the decommissioned device, then recommission it. See Chapter 5, Managing a Street Lighting Network, for more information about these tasks.
Figure 4. RF Signal Quality as Represented by the RF Signal LED The flashing pattern of the RF signal LED allows the installer to confirm good RF communications with nearby CRD 3000 Street Light Bridge modules without having to return to the Segment Controller. Echelon does not recommend using a link that indicates poor or no margin; such a link is likely to have poor reliability.
Note that the Segment Controller does not share a power line connection with the luminaires on the other side of the RF bridge; the CRD 3000 Street Light Bridge modules forward all communications between the two network segments. Figure 5. Basic Street Light Bridge Installation (Typical US Installation) Figure 6.
Figure 7. Extending the Street Light Bridge Installation Adding Multiple RF Hops Because CRD 3000 Street Light Bridge modules provide communications across power line boundaries, you can connect them in a series to provide maximum range extension. Figure 8 shows such an extension from the configuration shown in Figure 7.
Figure 8.
3 Setting Up the Segment Controller This chapter describes the tasks required to set up the Segment Controller.
Placing the Segment Controller in Standalone Mode A street lighting network is a power line repeating network, which requires that the Segment Controller operate in standalone mode with power line repeating enabled. Standalone mode allows the Segment Controller to operate as the exclusive network manager of the system, and to establish and maintain the appropriate repeating chains.
Network is limited to a single channel. Network cannot have a router attached to the channel. Network does not use LNS® management. Devices cannot be configured with LNS Plug-ins Network cannot be connected to any other network management tool through the network interface or remote network interface. LONWORKS network variable connections are not supported. A network in standalone mode functions strictly as a master-slave system.
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. Thus, network performance is not impacted by an offline device. You can also set the minimum period of time (in seconds) that the Segment Controller waits before transmitting network messages to offline data points. During this period, an offline device transmits an OFFLINE status in response to data point requests.
Deploying a “Golden Master” Segment Controller After you set up a Segment Controller with a configuration that is appropriate for your installation, you can make a template of that configuration, and then deploy that template on multiple Segment Controllers. See chapter 2 of the Echelon Enterprise Services 2.0 User’s Guide for information about how to use the Echelon Enterprise Services to create and deploy an i.LON template.
5. Select the Predictive Scanning checkbox. You can also specify the maximum hop count for repeating chains; the default is 8. Click OK to close the dialog and return to the Lon Devices page. 8. From the Street Light Bridge Installation page, select the Continuously checkbox to initiate continuous scanning. Alternatively, click Scan to initiate a one-time scan. The Segment Controller discovers any unconfigured devices (street light devices or CRD 3000 Street Light Bridge modules) and commissions them.
4 Planning for the Street Lighting Solution This chapter includes information needed for planning a street lighting network.
Security Planning Security planning for a street lighting network must address both of the following concerns: Physical security of the luminaires, CRD 3000 Street Light Bridge modules, and the Segment Controller Network communications security This document does not describe planning for physical security. The luminaires do not require extra security to participate in a street lighting network.
In addition, CRD 3000 Street Light Bridge modules provide the following security measures for the RF channel: Each message includes the sender’s RF address. Each message contains a 32-bit sequence number that allows for duplicate detection and protection against replay attacks.
a LONWORKS configured device and must use authentication. If security is less important, the devices can be in the unconfigured state before installation and be configured during commissioning. In both cases, authentication is recommended using 12-byte authentication keys. Using a NodeUtil Script to Define Security You can use the NodeUtil Node Utility, version 2.21 or later, to create and run script files to automate command entry for the NodeUtil Node Utility.
y Step 3. Set the channel ID to 0 so that the i.LON SmartServer can discover this device. q q y 6e 02000002040000 Step 4. Set the device to the configured state and online m s c m n Step 5. Turn on NM authentication. q q y 6e 0200180104E8 Step 6. Exit to force user to issue another "g" command (to enter the key to talk to the device) e Note that this script uses the string “112233445566” as the first half of the 96-bit key and the string “665544332211” as second half of the 96-bit key.
The Street Light Bridge firmware transfers the application image from off-chip to on-chip flash. The Street Light Bridge resets and begins running the new application image. Note that although you can upgrade the Street Light Bridge application over the network, you cannot upgrade the Street Light Bridge firmware over the network.
and the repeat count plus one should not exceed 12. The default is 6 (three channels with one repeat). Thus, for three configured channels, you should define no more than three repeats. Signal Strength The Segment Controller Power Line Repeating Analysis Web page shows cumulative device signal strength and margin information. When a CRD 3000 Street Light Bridge module is used for power line repeating, the Web page shows power line signal strength and margin information, which defines overall link quality.
EN50065-1 media access protocol is disabled. The device program ID reports a PL-20N channel. The XIF file for this mode is slb-normal.xif. 2 (cenelec): The CRD 3000 Street Light Bridge module uses the communication parameters of a PL-20C device. That is, the CENELEC EN50065-1 media access protocol is enabled. The device program ID reports a PL-20C channel. The XIF file for this mode is slb-cenelec.xif. Changing the value of this data point overrides the setting maintained in the device firmware.
the installed location of the CRD 3000 Street Light Bridge module with its Neuron ID in the Segment Controller. 3. Define which domains the device should use for normal communications. You can use any 1-, 3-, or 6-byte domain, but a 6-byte domain is recommended; for example, you could use the 6-byte Neuron ID of the Segment Controller as the network segment domain. If security is not required for your network, each device can use a single domain for both discovery and normal communications.
module in the entire street lighting network. The Segment Controller discovers and commissions nearby devices first, then discovers additional devices through the Street Light Bridge or luminaire repeaters, and then commissions them. Thus, the discovery and commissioning process is iterative, and could take some time to complete. The process also depends on your having installed Street Light Bridge or luminaire repeaters in appropriate positions within the network.
When directed to repeat onto the RF channel, the receiver waits until all the retries from the originator have completed before repeating onto the same channel. Thus, a CRD 3000 Street Light Bridge module attempts to keep the RF channel clear while another module is using it, and does not send responses while the originator is busy sending repeats of the request.
Figure 9. RF/RF Repeating Scheduling The Segment Controller includes an Event Scheduler application that you can use to schedule events. Thus, 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. In general, you would not define an event schedule for CRD 3000 Street Light Bridge modules (they should run continuously).
the Segment Controller should report the outage so that network management personnel can investigate and repair the outage. Figure 10. An Example Street Lighting Network These scenarios assume that both SLB A and SLB B have the same RF channel lists (primary 25, 20, 15 and secondary 11, 17, 26) – an assumption that should apply to nearly all street lighting networks. Also, these scenarios assume that the network has good communications prior to device failure.
Scenario 3: Prolonged Loss of SLB B If SLB B experiences an extended outage (longer than 15 minutes), communications between the Segment Controller and SLB B or the street light fail. SLB A detects an idle channel, and begins cycling through the channel list. If the Segment Controller continues to attempt to communicate with SLB B, SLB A delays cycling through the channels until the number of failed messages equals the retry count. When SLB B becomes operational, it uses its last-known-good channel.
Street Light Bridge module is powered on; any time spent powered off is not included in this timeout value. Because the Street Light Bridge application writes the remaining error simulation time to onboard flash memory once every 30 minutes, completion of error simulation might be delayed by up to 30 minutes if the CRD 3000 Street Light Bridge module is powered off or reset during the simulation.
Table 1. Street Light Bridge Firmware Error Codes 44 Error Description 0x40 Logged when a download fails because the image has a bad CRC, fails to decompress, or is improperly formed in some way. 0x41 Logged when a download fails because an image is incompatible with the target. This error includes image incompatibility (for example, not a Street Light Bridge image), hardware incompatibility, bootrom incompatibility, or feature incompatibility.
5 Managing a Street Lighting Network This chapter describes how to manage a street lighting network that uses power line repeating.
Manually Installing a Street Lighting Network You can manually install a street lighting network using the Segment Controller Web pages (see Automatically Discovering Devices for information about installing devices automatically). The installer should create a device list that accurately records the device location (such as light pole number) and the Neuron ID of the device installed at that location.
The location of the device (select External) The XIF file for the device (for example, “slb-normal”) 3. Click OK to add the device. It is added to the tree of its parent channel. 4. Click Submit on the main Segment Controller page to accept the change to the network. 5. Repeat steps 1–4 for each device on the network to be installed. Entering Device Locations and Neuron IDs Use the Segment Controller Web pages to enter the locations and Neuron IDs of the devices being installed: 1.
2. To select one device, click that device. To select multiple devices, click one device and then either hold down CTRL and click all other devices to be installed or hold down SHIFT and select another device to install the entire range of devices. The device page opens. Proceed to the next section, Installing Devices with Smart Network Management, to install the devices.
Installing Devices After enabling smart network management for all the applicable device properties, click Submit. The Segment Controller performs the following tasks for each device that you are installing: 1. Fetches the program ID of the device (if the Smart Network Management checkbox is selected for the Program ID property). 2. Downloads the application image file to the device (if the Smart Network Management checkbox is selected for the Application Image property).
2. The LON Command Queue page opens. 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.
Clear Table Clears all entries in the LON Command Queue table. The table automatically re-lists pending commands (STATUS_REQUEST) and updates their statuses after the commands successfully complete or fail. Configure Device Opens the Driver or General properties page for the selected device. Cancel Command Cancels the selected command and deletes it from the table. You can select multiple commands by clicking one, holding down CTRL, and clicking the other commands to cancel.
Delete devices Analyzing a Power Line Repeating Network When running on a power line repeating network, the Segment Controller transmits network messages to the repeating devices with which it can directly communicate, and those repeating devices in turn relay the messages to repeating devices located further down the power line, and so on until the message reaches the target device.
farthest 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. The repeating chains lead back to the Segment Controller, which is listed farthest to the left, in the column titled Center. The Segment Controller is always listed in the column titled Center because all network messages originate from its local LonTalk (ISO/IEC 14908-3) device (Net/LON/LtaLdv).
The direct communication devices (proxies that can directly receive messages from the Segment Controller without any repeating) are listed in the Direct Communication column (in the example above, the Segment Controller can reach both Lamp 1 and SLB 1 directly). The direct communication devices can relay messages to proxies and target devices further down the power line (in the example above, SLB 2 and Lamp 2).
Last Time Reached The time at which the device last responded to a network message. Frequency in use 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). For RF hops, Primary or Secondary refer to the CRD 3000 Street Light Bridge module’s primary or secondary channel lists.
Available Proxies The approximate number of repeating devices that can directly communicate with the device, including the current proxy. The signal strength at the repeating device and the number of hops required to reach it determine whether a repeating device can serve as a proxy for a given device. Failure History (24h). Lists the 45-minutes intervals within the current 24-hour period in which a device failure (if any) was reported.
Black (Installed) Commissioned. The device has successfully been installed. Orange (Installation in Progress) Pending Commission. The Segment Controller has identified that it needs to commission the device. Pending Download. The Segment Controller has been instructed to download an application image to the device. Never Reached. During the initial installation attempt, the device has not received messages from the Segment Controller.
Online Status Indicates the current device state. The values that can 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 Segment Controller, and it does not have any hard message failures. Orange (Installation in Progress) Nul.
Communication Agent Switch The number of times that the proxy agent used by a target device to receive a message from the Segment Controller has been switched because of a communication failure with a previous proxy agent. Communication Skipped The number of times that a proxy agent has not attempted to send a message to the target device because the Online Status of the target device was not “Up”. 6.
Frequency in Use 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 PLT-22 Power Line Transceiver User’s Guide (110kHz - 140kHz Operation). For RF hops, Primary or Secondary refer to the CRD 3000 Street Light Bridge module’s primary or secondary channel lists.
c. All the proxies (repeating devices) that can directly communicate with the selected device, including the current proxy, are listed in columns. For each proxy, the following statistics are listed: Primary Frequency The cached signal strength and signal margin measurements at the hop between the selected device and the proxy on the primary frequency. Signal Strength Direct Communication Devices: Displays the reduction in signal strength at the device in decibels (dB).
Signal Strength Direct Communication Devices: Displays the reduction in signal strength at the device in decibels (dB). Proxies: The reduction in signal strength at the hop in decibels (dB). This value is the minimum of the signal strengths measured at the selected device and the proxy. Signal Margin Direct Communication Devices: The amount in decibels (dB) that the signal margin exceeds the recommended amount calculated by the SmartServer for reliable communications at the device.
When you add the device to the network, the Segment Controller attempts to commission the new device. The commissioning succeeds if the Segment Controller can communicate with the device either directly or through a repeating chain. Upgrading Devices You can use the Segment Controller to upgrade devices that support application upgrade, such as CRD 3000 Street Light Bridge modules or most Neuron hosted devices.
b. The Choose File dialog opens. c. Expand the LONMARK Image (APB) icon to show the appropriate /lonworks/import folder. Expand the folder to show the application image files. d. Select the application image to be downloaded to the devices.
e. Click OK to return to the device Web page. 4. If the external device interface has changed, you need to load a new XIF file for the device onto the Segment Controller: 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.
8. To check the status of the device upgrade, open the LON Command Queue Web page: Right-click the Segment Controller icon, select Setup, and select LON Command Queue from the shortcut menu. Alternatively, you can open the Tools menu and click LON Command Queue. See Checking Device Installation Status for more information about using this Web page. Replacing Devices You can use the Segment Controller to replace a device if the device fails or a newer version of the device becomes available.
3. The Replace LON Device dialog opens. 4. You can acquire the Neuron ID of the replacement device using a service pin or you can enter it manually: 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.
decommissions the replacement device, begins repeater discovery, and then commissions the replacement device. 7. To check the status of the device replacement, open the LON Command Queue Web page: Right-click the Segment Controller icon, select Setup, and click LON Command Queue on the shortcut menu. Alternatively, you can open the Tools menu and then click LON Command Queue. See Checking Device Installation Status for more information about using the LON Command Queue Web page.
Alternatively, you can change the Commission Status property to Uncommissioned from the Setup tab of the device Web page, which appears when you select devices in step 1. 3. The Segment Controller places the devices in the soft-offline state (the device has an application loaded and is configured, but it is offline) and then unconfigures the devices. The offline devices are highlighted red in the Segment Controller tree and in the Power Line Repeating Analysis Web page. 4.
data point updates; however, it does not process them. Instead, the offline device transmits default values for its data points. In addition, an offline device can still process commission, decommission, set online, query status, clear status, wink, and reset commands. Note: Setting a device offline can affect the performance of the power line repeating network, particularly if the device is being used as a repeating agent in a repeating chain.
4. To place a device back online, select one or more devices to set online, right-click a selected device, select Manage, and select Set Online. Alternatively, you can select the Smart Network Management checkbox for the Application Status property from the Setup tab of the device Web page and then click Submit, or you can change the Application Status property to Application Running (Online) and click Submit.
3. 72 This dialog lists the following network statistics. Non-zero values indicate that the device was unable to receive or respond to a message. Small values are expected; rapidly increasing values could indicate a problem. If the device is consistently reporting failures and new errors are being logged, the device could have a configuration problem or the network could be overloaded. Name The name of the device in the following format: //.
Lost Messages Lost messages occur when a device’s application buffer overflows. This error could indicate excessive network traffic or a busy device application. If the incoming message is too large for the application buffer, an error is logged but the lost message count is not incremented. Missed Messages Missed messages occur when a device’s network buffer overflows or network buffers are not large enough to accept all packets on the channel, whether or not addressed to this device.
2. From the Setup tab of the device, right-click one of the selected devices, select Manage, and select Wink. Deleting Devices You can delete a device to logically remove it from the network: Right-click the device, and select Delete. The device is removed from the Segment Controller.
6 Controlling a Street Lighting Network This chapter describes how to use the Scheduler application on the Segment Controller to control the devices on a street lighting network.
Scheduling Overview The Segment Controller contains an Event Scheduler application that you can use to schedule data point updates (called events) to occur at specified times, such as sunrise and sundown, or at a configured amount of time before or after. For example, you can schedule luminaires to turn on at sundown, dim at the end of the evening rush hour, brighten again at the start of the morning rush hour, and then turn off at sunrise.
4. Select the data points to be updated by the Event Scheduler. See Selecting Data Points. 5. Create the daily schedules: set the days for which the daily schedules are used and creating events. See Creating Scheduled Events. 6. Create the exception schedules: set the range of dates and recursions for which the exception schedules are used and creating events. See Creating Exception Schedules.
3. Enter the IP address or hostname8 of the SNTP server and click Submit. The server icon in the tree is updated with the IP address or hostname that you entered. Note that you must configure the Segment Controller’s DNS servers correctly within its TCP/IP setup to be able to specify an SNTP server by hostname. 4. To specify that the SNTP server that you added supplies time service for your network, right-click the server icon, select Add Service, and select Time (SNTP) from the shortcut menu. 5.
6. Configure the following time (SNTP) server properties: Time Server Port The port used by the Segment Controller to receive time data. The default value is 123, and it cannot be changed. Contact your IT department to make sure that your firewall is configured to allow you to access the time server on this port. Time Synchronization Mode Select the frequency in which the Segment Controller is synchronized to the SNTP server: Automatic.
7. Click Submit to save the changes. Manually Configuring the Time You can manually configure the Segment Controller’s real-time clock: 1. Right-click the Segment Controller icon, select Setup, and select Time from the shortcut menu. Alternatively, you can click Tools and then select Time to configure the time settings on the local Segment Controller. 2. The Setup Time Web page opens. 3. In the Timezone property, select the time zone in which the Segment Controller is located. 4.
1. Open the Real-Time Clock application on the Segment Controller: Expand the Net network icon, expand the LON channel, expand the iLON App (Internal) device, and then click the Real-Time Clock functional block. If the Real-Time Clock functional block does not appear in the tree view, right-click iLON App (Internal) and select Add Functional Block to open the Add Functional Block dialog. From the dialog, expand the Static tree and select Real-Time Clock from the tree.
4. Click Submit. You can now view the calculated sunrise and sunset times. 1. Expand the Real Time Clock functional block, right-click the data point (nvoSunrise or nvoSunset), and select Show Value from the shortcut menu. 2. The data point value dialog opens. The value shown is the currently stored sunrise or sunset time, the 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.
Controller tree below the iLON App (Internal) device. You can then click the functional block and begin configuring the Event Scheduler application. To create a Scheduler functional block and open the application, perform the following steps: 1. Expand the Net network icon in the Segment Controller tree, and expand the LON channel to show the iLON App (Internal) device. 2. Right-click the iLON App (Internal) device, and select Add Functional Block from the shortcut menu. 3.
5. 84 If the Segment Controller 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.
6. Optionally, you can select the Restrict Effective Period checkbox to configure the period of time for which the Event Calendar and Event Scheduler are active, respectively. By default, both are active for a 37year period starting on January 1, 2000 and ending December 31, 2037. To configure a different effective period, specify the Start Date and Stop Date. If you clear the checkbox, the default 37-year effective period is used. 7. By default, the Suppress Event Recovery checkbox is cleared.
Adding Data Point Preset Values You can select and configure the input points to be updated by the Event Scheduler application. To select a data point, perform the following steps: 1. Expand the Net network icon, expand the LON channel, expand the tree view for the lamp or other device (for example, Lamp 1), expand the device’s primary functional block and click the data point for which you want to set a preset.
3. Expand the tree view for the device for which you want to add a data point, and expand its primary functional block. 4. Select the data point to add it to the scheduler. 5. Repeat steps 3 and 4 for each data point that you want to add. 6. Optionally, you can click the Stagger Delay column to specify the period of time (in seconds) that the Event Scheduler waits before updating the specified data point at each schedule interval. This setting enables you to ramp up or wind down a system.
b. c. 8. 9. 88 The Add/Delete Preset dialog opens. To create a new preset, select the Add radio button, enter the name of the new preset in the field, and click Add. The new preset appears without a value in the Scheduler: Data Points Web page. To delete an existing preset, select the Delete radio button, select the preset to be deleted from the dropdown list box, and click Delete. The preset is removed from the Scheduler: Data Points Web page. Click Close.
Creating Scheduled Events You can create scheduled events for the Event Scheduler. 1. Open the scheduler so that the calendar view for the current date opens. See Creating Event Schedulers to create an event scheduler. 2. Left-click in the calendar (or right-click anywhere in the calendar view page and select Add → New Event) to open the Edit Event dialog. 3. By default, the Recurrence is set to None.
Daily: The event occurs once per day. In this case, the dialog includes two checkboxes (neither selected by default): Range of Recurrence and Pattern. Select Range of Recurrence to specify a specific range of dates during which the event applies. For example, you can select a threeweek range from 4 October to 25 October. Select Pattern to specify how the daily schedule should recur. You can select a Day Based or a Month Based pattern.
If you added the event from a specific day in the calendar view, that day within the Pattern is selected by default. You can select any or all days of the week. In addition, you can select Range of Recurrence to specify a specific range of dates during which the event applies. Monthly: The event recurs on a monthly basis. In this case, the dialog includes checkboxes for Range of Recurrence, Date, and Pattern.
Select a Day Based pattern to specify that the event should occur every first (to 31st) day (or Sunday, Monday, and so on) of the month, or every weekday (or weekend day, Sunday, Monday, and so on) of the month, or every second (or third to sixth) day of the month. Select a Month Based pattern to specify that the event should occur every other month, quarterly (every third month), every fourth month, and so on to every eleventh month, or every January, every February, and so on to every December.
You can select a Day Based or a Month Based pattern. Select a Day Based pattern to specify that the event should occur every first (to 31st) day (or Sunday, Monday, and so on) of the month, or every weekday (or weekend day, Sunday, Monday, and so on) of the month, or every second (or third to sixth) day of the month.
7. Click Add Row to add additional rows for the event. For example, you can specify several on and off times for the device within a single day. 8. To remove a row from the event, click the X icon to the right of the row. 9. Click OK to add the event to the Event Scheduler and close the dialog. 10. Click Submit.
The exception schedule appears in the calendar view along with other scheduled events and exception events.
Weekdays. A daily schedule turns on the lights at the start of the morning commute hour, turns them off for the daylight hours, turns them on again for the evening commute hour, and dims them at the end of the evening commute hour. Weekends. A weekly schedule that turns on the lights at sundown and turns them off at sunrise. You would create exception schedules for holidays. The holiday exception schedules would have the same behavior as the weekend schedule.
Creating the Weekend Schedule You can create a schedule (or exception schedule) that controls the street lighting network on weekends, as shown Figure 12. The schedule includes the following events: An OFF event at sunrise that turns the lights off. An ON_60 event at sundown that turns the lights on to 60%. Figure 12. Weekend Schedule The weekend exception schedule turns the lights on (at 60% brightness) at sundown and turns them off at sunrise.
The Example Schedule The calendar view shown below displays the schedule defined in the previous sections.
Copying Event Schedulers to Other Segment Controllers After you create Event Schedulers with the appropriate exceptions, you can copy the Event Schedulers to other Segment Controllers: Back up the Segment Controller App device’s XML configuration on the source Segment Controller, copy the backup to one or more target Segment Controllers that have been reset to their factory default settings, and then reboot the target Segment Controllers.
shortcut menu. The Cleanup dialog opens. Click Cleanup to reset the Segment Controller. 100 To restore your Segment Controller to its factory default settings using the console application, enter the factorydefaults command, or enter the factorydefaults keepipaddrs command to reset the Segment Controller but keep its basic IPv4 and IPv6 IP addresses. For more information about using the Segment Controller console application, see Appendix B of the i.LON SmartServer User’s Guide. 3.
A Interoperable Interface for the Street Light Bridge This appendix describes the data points (input network variables and configuration network variables, and output network variables) that define the Street Light Bridge’s interoperable interface.
Interface You can use the Segment Controller to view the interoperable interface for a CRD 3000 Street Light Bridge module from the module’s Properties Web page. The interface includes output data points (network variables) that contain status information for the CRD 3000 Street Light Bridge module. The interface also includes input data points (network variables and configuration network variables) that define the operational characteristics of the CRD 3000 Street Light Bridge module.
Table 3. Input Data Points Variable Description Ok to Modify? nviL5Timeout Defines a timeout for updating the system firmware. Such updates should only be performed with guidance from Echelon Support. No Changing this value can prevent communications with the device. nciLtRate nciHbRate nciUpDwell nciDownDwell nciRcvStable nciCqaLimit nciSlotCount nciSlotWidth nciTransmitHb Define characteristics for the algorithms that control channel and signal quality.
Variable Description Ok to Modify? nciPriRpt Defines the repeat count for the primary path. Yes Defines channels for RF data transmission on the secondary (alternate) LonTalk (ISO/IEC 14908-3) path. Yes nciSecChs Valid values are 11 to 26. Values outside this range are ignored. nciSecRpt nciRepeatMode See Defining the Networking Channels for information about defining channels. See Defining the Networking Channels for information about defining channels.
Variable Description Ok to Modify? nciLedTimeout Defines the timeout for the LEDs on the CRD 3000 Street Light Bridge module. The timeout starts at each reset or power up of the device. Yes Controls error simulation mode. Yes nviErrMode Default value is 60 minutes. Set to 0 (zero) to leave LEDs on indefinitely, for example during installation debugging. See Verifying Successful Installation for more information about the device LEDs.
B Cryptography License This appendix provides the redistribution license for the cryptographic implementation used by the Street Light Bridge firmware.
License For authentication, the Street Light Bridge firmware uses a cryptographic hash function, the Secure Hash Algorithm (SHA), described by the National Institute of Standards and Technology (NIST) Federal Information Processing Standards Publication 180-2 (FIPS PUB 180-2).
C Glossary This appendix lists terms used in this manual and in the Street Light Bridge interface.
A Alternate path The path specified by LTEP when the “alternate path” bit is set. C Channel An RF or PLC frequency. CQA Channel Quality Assessment – algorithm that maintains statistics for all RF channels to support FAA. D Downstream [RF] channel The channel which a device normal listens to on RF waiting for a downstream message. Downstream message A message (for example, request) going from the Segment Controller to a target device.
PLC Power line carrier or power line communications. Primary channels A set of channels used to transmit on when the normal path is specified by LTEP. Primary receive channel The channel a device listens to when awaiting an upstream message (for example, response) on the normal path. S Secondary channels A set of channels used to transmit on when the alternate path is specified by LTEP.
