® @echelon Street Light Bridge Integrator’s Guide SECOND REVIEW DRAFT 078-0439-01A
Echelon, LONWORKS, LONMARK, LonTalk, Neuron, 3120, 3150, LonMaker, and the Echelon logo are trademarks of Echelon Corporation registered in the United States and other countries. 3170 is a trademark of the Echelon Corporation. 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.
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. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the manufacturer’s instruction manual, may cause interference with radio communications.
Table of Contents Welcome .........................................................................................................iii Audience ........................................................................................................iii Related Documentation ................................................................................iii FCC Compliance............................................................................................iii RF Statements...............................
PL/RF Repeater............................................................................... 41 Scheduling.............................................................................................. 42 Device and Network Recovery Planning .................................................... 42 Scenario 1: Loss of SLB A ..................................................................... 43 Scenario 2: Brief Loss of SLB B............................................................
Cryptography License .....................................................................................129 License ........................................................................................................ 130 Glossary...........................................................................................................
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. Recent 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.
Power Line Communications Radio Frequency Communications Street Light Bridge Street Light Bridge Segment Controller Service Distribution Transformer Figure 1. A Basic Street Lighting Network Because the Street Light Bridge module provides both ISO/IEC 14908-1 Control Network Protocol power line communications and IEEE 802.15.4 (2.
Controller. See the i.LON SmartServer 2.0 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).
PL-20 Channel Repeating Device 1 Device Repeating Device 2 Hop Device Repeating Device 3 Hop Target Device Hop Repeating Chain 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.
• Reduction in carbon dioxide (CO2) emissions – in one installation, by 70 tons per year (corresponding to the 45% reduction in electricity use). • Lamp failures can be identified within hours, reducing average lamp downtime by as much as 90%. • Alarms can be triggered when lamp voltage exceeds recommended levels, preventing future lamp failures.
offering far longer operating life, have helped the city improve its closed-circuit television (CCTV) image capturing system for increased public safety. 2 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.
Overview The process for installing a street lighting network includes the following basic tasks: • Install a Segment Controller • Install luminaires • Install 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. In either case, you install Street Light Bridge modules, as needed, to enable and extend the network.
Alternatively, you can install the luminaires, and then install the Segment Controller. However, this document does not describe details for this alternate installation scenario. START OR Install i.LON 1 Install Luminaires i.LON Segment Controller is in Acquisition Mode to discover luminaires and SLB modules Install luminaires Each lamp turns on Install Luminaires 2 Install i.LON i.
After your initial network of the Segment Controller and luminaires is defined, you can add Street Light Bridge modules to extend the communications range of the network. Step 1: Install the Segment Controller Configure the Segment Controller (see Chapter 3, Setting Up the Segment Controller, on page 27) and install it at any convenient location for the street lighting solution.
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. For any that do not turn off, proceed to Step 3 to install Street Light Bridge modules; the Segment Controller will discover the installed luminaires through the Street Light Bridge modules.
the Segment Controller discovers and commissions the luminaires. If all of the lamps are off, the installation is complete. For those lamps that do not turn off, install additional Street Light Bridge modules to further extend the communications range of the Segment Controller.
• Query the status of the Street Light Bridge module from the Segment Controller See Testing Devices on page 72 for more information about using the Segment Controller to verify Street Light Bridge installation. Both Street Light Bridge LEDs are off initially, but the green power LED turns on as soon as possible after you supply power to the device.
Example Installations You can install Street Light Bridge modules in almost any configuration to provide power line and radio frequency communications for street lights within a street lighting solution. In the figures, the arrows represent RF communications between the Street Light Bridge modules. Although the street lights in the figures are shown in straight lines, they could be in any physical configuration.
Figure 6. Extending the Street Light Bridge Installation Adding Multiple RF Hops Because Street Light Bridge modules provide communications across power line boundaries, you can connect them in a series to provide maximum range extension. Figure 7 shows such an extension from the configuration shown in Figure 6.
Installation for the Street Lighting Solution
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. This 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 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.
status in response to data point requests. After the Minimal Offline Time elapses, the SmartServer sends a read/write request to one offline data point. If the read/write request succeeds, the data point and its device are marked online, and all cached read/write requests for the offline data points on the device are executed. If you do not configure this property on a power line repeating channel, it is set to 60 seconds. 5.
2. Click the Tools icon to open the Tools dialog. 3. From the Tools dialog, click Street Light Bridge Installation to open the Lon Devices page. 4. From the Lon Devices page, click the … button at the top of the page to open the LON Scan Settings dialog. 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. 6.
Setting Up the Segment Controller
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, 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.
• Each message includes the sender’s RF address to detect simple intrusion. • Each message contains a 32-bit sequence number that allows for duplicate detection and protection against replay attacks.
important, the devices can be in the unconfigured state before installation and be configured during commissioning. In both cases, authentication is recommended. Device Upgrade Planning To allow your street lighting network to be upgraded over time, you can download an updated Street Light Bridge application (as Echelon releases application updates) over the power line network. The application download uses the standard ISO/IEC 14908-1 download protocol.
channel, all the Street Light Bridge modules within a street lighting network coordinate which frequencies they use. Multiple Street Light Bridge modules can use a single RF channel. In addition, multiple RF channels can exist within a single street lighting network. A Street Light Bridge module identifies these channels through a pair of configuration network variables (nciPriChs and nciSecChs), which define three channels in the range 11..
the value of the nciMediaAccess configuration network variable to specify the power line media access protocol: • 0 (default): The Street Light Bridge module uses the media access protocol setting defined in the firmware. That is, European models use the CENELEC protocol, and other models do not. • 1 (normal): The Street Light Bridge module uses the communication parameters of a PL-20N device. That is, the CENELEC EN50065-1 media access protocol is disabled. The device program ID reports a PL20N channel.
1. If the network configuration is known, or if device security is configured before the devices are installed (that is, in a pre-deployment facility), define the authentication key for the device. You can use any 12-byte (96-bit) key. 2.
commission all luminaires and Street Light Bridge 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.
Figure 8. PL/PL Repeating RF/RF Repeater You can define the Street Light Bridge module as an RF repeater to extend the range of RF communications. If you set nciRepeatMode to 2, you block power line communications, which can be useful if the Street Light Bridge module should act as a repeater for a different Segment Controller than the one with which it has power line communications. Figure 9 shows an example for RF/RF repeating mode.
• When receiving a message, the Street Light Bridge module replies only on the channel on which the message was received (PL or RF). In this case, “reply” means response, acknowledgement, challenge, or reply. • When receiving a proxy request, the Street Light Bridge module forwards the request to both the RF and PL channels. A Street Light Bridge module does not repeat a packet onto the RF channel unless it receives a request from the Segment Controller to repeat.
Scenario 1: Loss of SLB A When SLB A fails (for example, it experiences a power outage), any communications initiated by the Segment Controller cannot reach SLB B or the street light (SL). At this point, SLB B determines that the RF channel is idle. After the channel has been idle for 15 minutes, SLB B tunes to another channel from its configured channel list. If that channel is also idle, SLB B cycles through all of its configured channels to attempt to reestablish communications.
Simulating Communications Errors A Street Light Bridge module autonomously determines which frequency to monitor, and then continues using this frequency until some failure condition occurs that makes the frequency unusable. When determining which channel to use, the Street Light Bridge firmware monitors the channel quality and the signal quality for the channel, and chooses the best transmit and receive channel.
• If error simulation mode is active, error simulation mode is restarted with the new timeout value, regardless of how much time has already passed or how much time would be left in the previous simulation. • If error simulation mode is not active, the value is stored but has no other immediate effect.
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 SmartServer Web pages (see Automatically Discovering Devices on page 30 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.
2. Enter the following device properties: the name of the device (for example, “Oak Creek Road Lamp 46N”), the location of the device (select External), and 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 SmartServer page to accept the change to the network. 5. Repeat steps 1–4 for each device on the network to be installed.
1. 2. Select one or more devices from the tree to be installed. • 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 SmartServer 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.
4. You can right-click the header, a table entry, or an empty space in the application frame and select one of the following options from the shortcut menu: 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.
• Set devices offline • Test (query and wink) devices • Delete devices Analyzing a Power Line Repeating Network When running on a PL-20 repeating network, the SmartServer 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.
1. Right-click the SmartServer icon, select Setup, and select Power Line Repeating Analysis from the shortcut menu. Alternatively, you can click the Tools icon and select 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.
To view the repeating chain of a specific device, click one of the 20 bluehighlighted devices in the tree to clear the pre-selected devices and then click the device to be viewed.
a. The proxy in the repeating chain that directly communicates with the SmartServer is listed in the Direct Communication column. b. The next proxy in the repeating chain, which does not have direct communication with the SmartServer, is listed in the Proxy Zone 1 column. c. The proxy that can directly communicate with the target device (the proxy agent) is listed in the Proxy Zone 2 column. d. The target device is listed in the Proxy Zone 3 column.
Signal Strength Direct Communication Devices: The reduction in signal strength measured at the device in decibels (dB). Proxies and Target Devices: The reduction in signal strength at the hop in decibels (dB). This value is the minimum of the signal strengths measured at the device and its proxy. Signal Margin Direct Communication Devices: The amount that the signal is greater than the noise level at the device in decibels (dB).
Commission Status Indicates whether the device has been commissioned. The values that can 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.
model number, or the device and the application image file (.apb extension) on the SmartServer (to be downloaded to the device) having mismatching program IDs. • Online Status Message Error. The SmartServer cannot communicate with the device after the calculated number of retries (this state is classified as a hard message error). The SmartServer regularly attempts to communicate with the device over an approximate 5-minute period.
Communication Failures The number of times that a device (either the SmartServer or a proxy agent) has failed to communicate with the target device. For direct communication target devices, this field lists the number of communication failures that have occurred with the SmartServer. For all other target devices, this field lists the number of communication failures that have occurred with a proxy agent.
Time Stamp Displays the time at which the device last responded to a network message. 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). Signal Strength Direct Communication Devices: Displays the real-time measurement in dB of the signal strength at the device.
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 Margin Direct Communication Devices: The amount that the signal is greater than the noise level at the device in decibels (dB). Proxies: The amount that the signal is greater than the noise level at the hop in decibels (dB). Failure History Provides a historical list of the 45-minutes intervals since the SmartServer was rebooted in which a device failure (if any) was reported.
To perform an upgrade, you need to obtain from the device manufacturer the binary application image file (.apb extension) and related files for the new application to be used to upgrade the device. The system image in the application image file must have the same firmware version as the Neuron Chip on the device. If the device interface has changed, you also need to obtain a new device interface (XIF) file for the device, upload it to the SmartServer, and activate it on the SmartServer.
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 SmartServer: a. In the Template property, click the … button to the right. b. The Choose File dialog opens. c.
then select the Smart Network Management checkbox to the left of the Application Image property in the device Web page and click Submit. 7. Activate the XIF files for the devices (if necessary): Right-click one of the selected devices in the SmartServer tree, select Manage, and click Activate Template in the shortcut menu. Alternatively, you can clear and then select the Smart Network Management checkbox to the left of the Template property in the device Web page and click Submit. 8.
If you replace 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 old device in their repeating chains. When you add the replacement device to the network, the SmartServer attempts to commission the replacement device. The commissioning succeeds if the SmartServer can communicate with the device either directly or though a repeating chain.
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. • 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.
a repeating chain. If a repeating agent is decommissioned, it could cause communication failures for multiple devices. To decommission a device, perform the following steps: 1. 2. Select one or more devices from the tree to be decommissioned: • To select one device, click that device.
the devices again, right-click a selected device, select Manage, and select Set Online from the shortcut menu. Alternatively, you can select the Smart Network Management check boxes for the Commission Status and Application Status properties from the Setup tab of the device Web page, and click Submit. You can also change the Commission Status property to Commissioned and change the Application Status property to Application Running (Online), and then click Submit.
Alternatively, you can change the Application Status property to Application Stopped (Offline) in the from the Setup tab of the device Web page, which appears when you select devices in step 1. 3. The SmartServer places the devices in the soft offline state (the device has an application loaded and is configured, but it is offline). The offline devices are highlighted red in the SmartServer tree and in the Power Line Repeating Analysis Web page. 4.
Querying Devices You can query a device to evaluate its performance and diagnose problems. It is recommended that you query devices under both normal and peak conditions. To query a device, perform the following steps: 1. Right-click the device, select Manage, and select Query Status. 2. The Query Status dialog opens.
3. 74 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.
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 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.
6 Controlling a Street Lighting Network This chapter describes how to use the Scheduler application on the SmartServer to control the devices on a street lighting network.
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 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 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.
3. Select the data points to be updated by the Event Scheduler. See Selecting Data Points on page 88. 4. Create the daily schedules: set the days for which the daily schedules are used and creating events. See Creating Scheduled Events on page 90. 5. 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 on page 92.
3. Enter the IP address or hostname 6 of the SNTP server and click Submit. The server icon in the tree is updated with the IP address or hostname that you entered. 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. The Set Up Time Service Web page opens. 6 Your corporate or municipal network might already include one or more SNTP servers.
6. Configure the following time (SNTP) server properties: Time Server Port The port used by the SmartServer 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 SmartServer is synchronized to the SNTP server: • Automatic.
Manually Configuring the Time You can manually configure the SmartServer’s real-time clock: 1. Right-click the SmartServer 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 SmartServer. 2. The Setup Time Web page opens. 3. In the Timezone property, select the time zone in which the SmartServer is located. 4.
1. Open the Real-Time Clock application on the SmartServer: Expand the Net network icon, expand the LON channel, expand the i.LON App (Internal) device, and then click the Real-Time Clock functional block. 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. • In the Latitude property, enter the north-south location of the SmartServer relative to the equator.
illuminates them at the beginning of the morning and evening rush hours, and a third exception that dims the lights at sunrise and sundown. To open an Event Scheduler application, you must first create a Scheduler functional block, if the available functional blocks are not already displayed in the tree view for the i.LON App (Internal) device. After you create the Scheduler functional block, the functional block appears on the SmartServer tree below the i.LON App (Internal) device.
4. 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 static v12 XIF file (the default), expand the Static icon, select the Scheduler functiona1 block, optionally enter a different name than the default programmatic functional block name, and then click OK.
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. 5. A calendar view for the current date opens. 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.
To open the Scheduler application from an existing Scheduler functional block, perform the following steps: 1. Click the Scheduler functional block representing the Scheduler to be opened. The Scheduler Web page opens in the application frame to the right. 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.
Selecting Data Points 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: 88 1. Expand the Net network icon, expand the LON channel, expand i.LON App (Internal), and select the scheduler for which you want to select data points. See Creating Event Schedulers on page 83 to create an event scheduler. 2. The calendar view for the current date opens.
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. Click Submit. 7. Optionally, you can add new presets to a data point or delete existing presets: a. Right-click the data point and select Add/Delete Preset from the shortcut menu. b.
• c. 8. 9. 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. Optionally, you can edit the values of existing presets: a. Click the preset to be edited. The Edit Presets dialog opens. b. Enter the value (or values, if you are editing the preset of a structured data point) for the preset. c. Click OK. Click Submit.
Edit Daily Schedules dialog and configure the scope of the daily schedules. See Error! Reference source not found. on page Error! Bookmark not defined. for more information about configuring the daily schedules. 4. In the Time box, enter the exact time that 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.
Note: To edit an event, click the event in the Scheduler: Daily Schedules Web page, change the time or value, and click OK. To delete an event, click the event in the Scheduler: Daily Schedules Web page, right-click the event, select Delete from the shortcut menu, and click OK. 9. Repeat steps 1–6 to create events for other Daily Schedules in the Scheduler. 10. Click Submit. 11. Click Back to return to the Scheduler: Configure Web page.
The Scheduler: Exception Schedules Web page opens. 2. Right-click the date on which the one-time exception schedule is to be used, point to Add Exception, and select New One-Time Exception from the shortcut menu. 3. The New One-Time Exception dialog opens. 4. By default, the name of the one-time exception is the date for which it is being created. You can enter a different (perhaps more descriptive) name in the box at the top of the dialog.
5. Select the Show Sunrise/Sunset Functions checkbox to create events based on sundown and sunrise times. In the Function box, select the Sunrise ( ) or Sundown ( ) icon. The calculated sunrise or sundown time appears in the Time box, which becomes read-only, and an Offset box is added to the right of the Time box. In the Offset box, you can enter the time before or after sunrise or sundown that the event is to occur. 6.
schedule have a priority of 250. This priority essentially locks out events with lower priorities so that they cannot update the data points written to by this event. When the event ends, lowerpriority events can update the data points. e. To create additional events in the one-time exception, right-click anywhere in the Time or Value boxes, and select Add from the shortcut menu. A new row for the event is added to the dialog.
Note: This section generally describes how to define the exception schedules. See Demonstrating a Street Lighting Schedule on page 105 for specific exception schedules that you can create for scheduling a street lighting network. Defining Exception Dates and Recursions To define the dates and recursions of an exception in the Event Scheduler, perform the following steps: 96 1. In the Scheduler: Configure Web page, click the Exception Schedules icon. 2.
5. Enter a descriptive name for the exception. The default name is the selected start date in the following format: --. 6. Click the Standard or Specific radio buttons to expand the dialog to show the Recurrence property. • Clicking Standard lets you apply the exception to every month, every other month, every third month, and so on, up to every eleventh month.
• 98 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 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 occur every day within the specified range. 9.
schedule) that includes this exception and one or more other existing exceptions. 10. Click OK to add the exception and return to the Scheduler: Exception Schedules Web page (click Cancel to discard all changes and return to the Scheduler: Exception Schedules Web page). The range of dates on which the exception is to occur is highlighted light blue in the calendar and outlined with a color differentiating it from the other exceptions in the calendar. 11. Click Submit.
2. Click anywhere in the row under the Schedule, Event Time, Value, or Priority columns at the time the event is to occur. The Edit Events of dialog opens. Alternatively, you can right-click a time under the Time column or right-click the column to the right and select Add Event from the shortcut menu to open the Edit Events of dialog. 3. Select the Show Sunrise/Sunset Functions checkbox to create events based on sundown and sunrise times. A Function field appears in the dialog. 4.
5. The calculated sunrise or sundown time appears in the Time box, which becomes read-only, and an Offset field is added to the dialog. 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 an ON event to occur 30 minutes after sundown, enter 00:30.
7. 104 In the Value box, perform one of the following tasks: • Select the preset to be used to update the values of all the data points added to the Scheduler that have that preset defined for them. Alternatively, you can enter a new preset and then go back to the Scheduler: Data Points Web page and define the value (or values) for the preset. • Enter a valid value to be written to all the data points.
10. Click OK to save your events and return to the Edit: dialog. Click Cancel to delete all changes and return to the Edit: dialog. 11. The Edit: dialog is updated to reflect the events that you added to the exception schedule. The events are highlighted light blue. 12. Click OK to save your changes to the Edit: dialog and return to the Scheduler: Exception Schedules Web page.
• Weekends/Holidays. One exception group (a group of exceptions that use the same schedule) is used to control the street lighting network on weekends and holidays. The exception schedule simply turns on the lights at sundown and turns them off at sundown. Note: In this example, additional user-defined presets have been created for the SNVT_switch data point on the luminaire. These presets include ON_60 and ON_100, which set the SNVT_switch data point to 60.0 1 (60% brightness and on) and 100.
Figure 12. Weekday 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 rush hour, and dims them at the end of the morning rush hour. To create the weekday daily schedule, perform the following steps: 1. In the Scheduler: Configure Web page, click the Daily Schedules icon. The Scheduler: Daily Schedules Web page opens. 2.
ON_100 event in the weekday daily schedule has a lower priority (255) than that of the OFF event in the weekday exception schedule (220), which does not end until sundown. After the OFF event in the weekday exception schedule is executed at sundown, the ON_100 event is executed and the lights are turned on and fully illuminated to 100%.
6. Click Back to return to the Scheduler: Configure Web page. Creating the Weekday Exception Schedule The weekday exception schedule turns on the lights at sundown and turns them off at sundown. To create the weekday exception schedule, you create a new onetime exception; change the name, range of dates, and recursions for the exception; and then create the sunrise and sundown events. To create a new exception for the weekday schedule, perform the following steps: 1.
selected start date in the following format: -. 110 b. Click Standard to expand the dialog to show the Recurrence property. This option lets you apply the exception to every month and every weekday. c. In the From and To properties, specify the start and end dates of the exception. d. Under Recurrence, select Every Month from the Monthly list. This option means that the exception recurs every month in the specified range of dates. Select Every Weekday from the Daily list.
which becomes read-only, and an Offset box is added to the right of the Time box. If the event is to occur sometime before or after sundown, enter that period of time in the Offset box. For example, if you want an ON_100 event to occur 30 minutes after sundown, enter 00:30. d. In the Value box, select OFF. If OFF does not appear as an option in the list, you can enter OFF and then create an OFF preset as described in Selecting Data Points on page 88. e.
10. You can verify how the weekday exception schedule has been updated with the morning and evening weekday rush hour events in the daily schedule that are now scheduled before and after the OFF event: 112 a. Click one of the teal-highlighted dates in the calendar. The Edit: dialog opens. b.
scheduled to occur once the OFF event ends at sundown and resets the data point priority to 255. Creating the Weekend and Holiday Exception Schedules You can create a schedule that controls the street lighting network on weekends and holidays. This schedule creates 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.
2. 114 The Edit Exceptions dialog opens. Set the name, range of dates, and recursions for the exception following these steps: a. In the Exception Name property, enter a descriptive name for the exception such as “Weekend/Holiday”. The default name is the selected start date in the following format: -. b. Click Standard to expand the dialog to show the Recurrence property. This option lets you apply the exception to every month and every weekend day. c.
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 by performing the following 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: 116 • 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. 4. Click OK to save exception and return to the Scheduler: Exception Schedules Web page. 5.
6. Click Submit. 7. Create the sunrise and sundown events for the weekend/holiday exception following these steps: a. Click one of the light blue-highlighted dates in the calendar. The Edit: dialog opens. b. Click anywhere in the row under the Schedule, Event Time, Value, or Priority columns at the time that the event is to occur. The Edit Events Of dialog opens.
c. Select the Show Sunrise/Sunset Functions check box. A Function box appears to the right of the Time box. d. In the Function box, select the Sunrise icon ( ). The calculated sunrise time appears in the Time box, which becomes read-only, and an Offset box is added to the right of the Time box. If the event is to occur sometime before or after sunrise, enter that period of time in the Offset box. For example, if you want a DIMMING event to occur 15 minutes before sunrise, enter -00:15 e.
h. In the Function box, select the Sundown icon ( ). The calculated sundown time appears in the Time box, which becomes read-only, and an Offset box is added to the right of the Time box. If the event is to occur sometime before or after sundown, enter that period of time in the Offset box. For example, if you want an ON_60 event to occur 30 minutes after sundown, enter 00:30. i. In the Value box, select ON_60.
9. Click OK to save your changes to the Edit: dialog and return to the Scheduler: Exception Schedules Web page. 10. Click Submit.
the local drive of your computer, a USB drive, another removable media, or a shared network drive with read/write permissions. 2. Restore the target SmartServer to its factory default settings with the Setup – Cleanup Web page or the console application: • To restore your SmartServer to its factory default settings using the SmartServer Web pages, right-click the local SmartServer, point to Setup, and select Clean Up from the shortcut menu. The Setup – Cleanup dialog opens.
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 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 Street Light Bridge module. The interface also includes input data points (network variables and configuration network variables) that define the operational characteristics of the Street Light Bridge module.
Table 3. Input Data Points Variable Description Modifiable? 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 Modifiable? nciPriRpt Defines the repeat count for the primary path. Yes See Defining the Networking Channels on page 36 for information about defining channels. nciSecChs Defines channels for RF data transmission on the secondary (alternate) LonTalk (ISO/IEC 14908-1) path. Valid values are 11 to 26. Values outside this range are ignored. nciSecRpt Contains the repeat count used for the secondary path.
Variable Description Modifiable? nciLedTimeout Defines the timeout for the LEDs on the Street Light Bridge module. The timeout starts at each reset or power up of the device. Yes Default value is 60 minutes. Set to 0 (zero) to leave LEDs on indefinitely, for example during installation debugging. See Verifying Successful Installation on page 22 for more information about the device LEDs. nviErrMode Controls error simulation mode.
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 SmartServer to a target device.
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. Secondary receive channel The channel a device listens to when awaiting an upstream message (for example, response) on the alternate path. SLB Street Light Bridge module.
