|
- Controller based on a Neuron 3150 micro-controller
- Non volatile storage capacity of up to 1MB.
|
- Controller based on a Neuron 3150 micro-controller.
- Integrated real-time clock.
- LCD interface for information display.
- Three buttons allowing various settings.
- Controller based on a Neuron 3150 micro-controller.
- On the first card, the first 3 inputs are used to monitor the current.
- The other inputs can be configured in thermistor mode.
- Current monitoring only (0-10 Vdc or 2-20 Ma).
- Eight outputs that can be configured in dry contact or pulse mode for use with CCT (triac)
- Output capacities: dry contact: 1 Amp/120Vac ; 0-20 Ma : 800W ; 0-10V : 45 Ma, total 200 Ma
-
Bypass switch on every output.
- Controller based on a Neuron 3150 micro-controller.
- Input compatible with “load pulse output” system.
LNS® (“Lonworks Network Services”) is an application layer product used as an interface between an Echelon network and an application such as LoadShedder2000®. It manages all access to the LonWorks® network. For every Echelon network created by the user, Echelon’s LNS generates a data base reflecting the network configuration, including the cards installed, the links between them, the logical addresses assigned to each card, etc.
LoadShedder2000® is an application executed on a Windows 95,98 /ME operating system. Allowing for the installation, configuration and visualization of the LoadShedder2000® power management system. It has a intuitive interface which is very easy to operate. All of the system’s inputs/outputs can be custom- named for easy identification. Addiutionally the loaddShedder package allows easy modifications to the project including adding inputs/outputs to an existing project. The project parameters are saved in a file with the “lsh” extension. The software automatically links a given project with the LNS data base containing the information concerning the system’s LonWorks® network.
The network interface is the link connecting the computer to the Echelonrnetwork. When working with LoadShedder2000® it is important to specify the particular interface to be used. It is also possible to work in an off-line mode at all times. By default the software selects the latest network interface used. To avoid the automatic selection of the latest network interface it is important to specify it before opening or creating a project. The “File/Network interface” command invokes a dialog box that displays the various network interfaces detected on the computer, which allows for the selection of the desired interface. Possible choices include: SLTA-10 for network or modem, PCC-10 pcmcia for portable, PCLTA-10 ISA card for PC, PCLTA-20 PCI card for PC, I-Lon Ethernet interface
|
|
|
|
Using the “File/New” command or the blank sheet icon, choose a location and assign a name to the project. If there is no LNS database bearing the name of the project, a new data base will be created. The name of the project must be chosen with care since the LNS data base cannot be renamed. The name cannot have more than eight characters.
Schedule construction with the LoadShedder2000® system is based on the creation of a standard week and the creation of an annual event. A standard week is a representation of a seven-day week from Sunday to Saturday, in which the appropriate events are positioned at the desired times. Annual events are the dates that override the events of standard weeks. The system automatically tracks the day of the week and the date corresponds then takes appropriate action.
Two types of schedules are possible with LoadShedder2000®: (1) the “Occupation” schedules and the “Pulsed” schedules. The Pulsed schedules are in fact momentary events applied to an output at a specific time. The event time ranges from 1 second to 32,767 seconds (more than 9 hours). The “Pulse” is managed by the slave card and up to 200 events per week can be supported by the eight outputs of a single card.
Up to 64 occupation schedules can be created for a single system. These are managed by the master card. Up to 100 annual events can be created per schedule, and a maximum of 400 events per standard week are possible. A total of 1,500 annual events/weeks are possible for the system as a whole.
In order to use optimized starts we insert an “OptON” event instead of an “On” event in the selected standard week. This activates the occupation mode based on outside temperature. In the case of optimized starts, three parameters can be configured: the maximum advancement of the start, the maximum temperature at which the optimized start is no longer necessary, and the minimum temperature when the advancement time must be maximal.
The number of inputs/outputs of a system is determined by the number of slave cards used. When a project is being designed, the number of cards used must be specified in the software. It is then possible to individually access each of the system’s input/output. In order to facilitate project design and control it is possible to rename the input and output (maximum of 255 characters). Input/output names are saved in the “lsh” configuration file.
When the system is connected to the network and the controller cards are installed, the temperature can be read and the temperature sensors can be calibrated if necessary. The temperature range covered by the cards varies from –50 to 100 C. It should be noted that the short-circuit card input will be interpreted as a temperature of 100 C and that the off-net card input will be interpreted as a temperature of –50 C. The input status transmission parameters may be modified in the case of specific requirements.
Every output may be configured in schedule control: activated in day mode, deactivated in night mode; in comfort control: activated as needed by using the day or night set point as the case may be; in peak control: forced inactive in case of brown-out. If no schedule is linked to an output, the day mode is adopted by default. Although any input may be assigned to an output, it is recommended while a project is being developed, to use the inputs on the card with outputs on the same card in order to minimize network traffic on the LonWorks network
Every output can be configured to be “Pulsed”. In a “Pulsed” mode the dry contact within the card switches immediately as soon as the output becomes active, whereas the analog output pulses according to outside temperature. A chart allows one to configure the desired modulation according to outside temperature. There is a modulation chart for every card. It is therefore possible for two outputs to have two distinct modulation charts provided these 2 outputs are on two separate cards.
When the system is connected to the network and the controller cards have been installed it is possible to visualize the state of the relays and to force this state if desired (“Bypass On/Off”).
A configurable priority number indicates the importance of the output during brown-out periods. The output with the lowest priority value will be among the first to be browned-out. A load value is assigned to every output. It is possible to specify a high/low temperature limit when a sensor is linked to the output, and it is also possible to specify minimum “On” and maximum “Off” operation times (up to 6,553 seconds/109 minutes). Moreover, an output may be forced “On” regardless of the system’s status (brownout or normal)
Output
1 Output
5 Output
6 Output
7 Output
8
Three types of controllers can be used as a power control interface. The “WattNode” (from Continental Control Systems) is a controller dedicated to power control supported by LoadShedder2000®. The PI2000 card is a card which is compatible with the systems offering a “Load Pulse Output”. The slave card (Multi-IO) can also be used as a reader card if it is connected to an interface offering a 4-20ma, 0-10V or 0-5V signal.
Twelve (12) monthly power sets are pre-adjustable. When the dates of the meter readings are indicated, the system will select during the transition period the lowest power set for the two-month period. The user can maintain the power set of the current month according to the configuration of the display unit.
The system may be configured so as to brown-out all project outputs, or only those selected. The maximum number of outputs to be browned-out is adjustable. It is also possible to request a minimum brown-out level applicable at all times.
System brown-out occurs when consumption exceeds the set point. A first output is then browned-out. Following a configurable brown-out period, if consumption still exceeds the set point, a new output is browned-out until the required electrical consumption level is restored. For re-energizing of an output, consumption must fall below the set point – hysteresis. A first output is then re-energized; thenafter a configurable delay period, a new output is re-energized until the minimum brown-out threshold is again achieved.
When the system is started, brown-out is set at 100%. A third delay is provided for this particular purpose. When the system is launched the startup delay followed is “Start up delay ON”. This delay will be followed until 80% of the actual or theoretical consumption of the current power set is reached (theoretical consumption is the total of the values of the actual loads). Subsequently, the normal re-energization delay is used.
The configuration of the stages helps determine the order in which the brown-outs of the outputs are called. Every time a brown-out is necessary or the re-energization becomes possible, the brown-out level is incremented or decremented. The brown-out level indicates what stage the brown-out must refer to. The stage points to a group of outputs. When the brown-out level changes, one of the outputs of the group is re-energized or browned-out, as the case may be. The hysteresis for a given stage is actually the greatest charge value contained in the group to which it belongs.
It is at group level that the final decision concerning the output to be browned-out or re-energized is made. Up to 64 groups can be configured within a system, and each group can contain up to 64 members. In case of energization, the output with the highest priority in the group is readmitted; in case of brown-out, the output with the lowest priority is browned-out. Output priority is determined in order according to the following parameters: configuration priority, temperature differential (when a temperature sensor is linked with the output), working time (the smallest has the highest priority), out of function cumulative time (the greatest has the highest priority).
When a group output is forced “ON” the system tries to compensate by browning out another output from the same group. If all outputs have already been browned-out or forced “ON”, the system will wait until one of the other outputs can be browned-out again to restore the brown-out balance within the group.
The brown-out time can be distributed over several outputs by performing the cycling of the browned-out outputs in a given group. A configurable cycling time indicates the minimum time to adhere to before interchanging the brown-out state between the group outputs. One can choose between priority cycling in which the system attempts to readmit the output with the highest priority for the benefit of the output with the lowest priority, and the time cycling in which the system attempts to readmit the output that has been browned-out the longest for the benefit of the output that has been active the longest. The cycling parameters are specific to each group. If cycling is not desired it can be forbidden.
Since hysteresis is determined by the greatest charge value found within a group, the outputs included in a group should have approximately the same charge value. This ensures an optimum readmission of outputs following brown-out. Moreover, when cycling is allowed within a group, permutation of browned-out and active outputs can result in an unbalanced consumption.
For the system to be launched the controllers must be installed. The installation is the network configuration assigned to each controller. Each controller must first be installed into the network. The card installation needs to be performed only once. It can be done at the beginning or at the end of the project’s construction. When the cards are installed it is then desirable to download the application to the card using the “Load App” command to confirm the program executed by the card is the right one.
When all the parameters have been configured and all the controllers have been installed, the “Download all configuration” command transmits the project’s configuration to the controllers. The links between the controllers (the “bindings”) are generated. If a controller cannot be accessed during the transmission of the parameters, an error message will indicate that the downloading of the configuration on a specific controller could not be carried out properly. These errors are often caused by one or more controllers that are either not linked to the LonWorks network or have not been physically supplied.
The location of the project can be indicated using the “File/Open” command or the yellow file icon. If there is no existing LNS data base bearing the project’s name a new data base is created. If changes are made in the project, the configuration of the cards will only be affected following the “Download All” command. The project must be saved in order for the changes to be preserved.
To install an existing project on a new computer it is important to import the project so that the information contained in the LNS data base can be included. The “File/Lns Db/Restore & Open” command allows you to indicate where the “ldb” file is located. The LNS data base is then imported and the project is opened. The “lsh” file will be restored in the same location as in the computer it was exported to. If the catalog containing the “lsh” file does not exist on the new computer it will be created automatically.
Deleting a LNS data base:
It sometimes happens that a LNS data base is no longer useful, either because a later version is being imported, because the project was exported to a new computer, or simply because the project is being destroyed. The “File/Lns Db/Delete” command invokes a dialog box which contains all of the computer’s LNS data bases, and the data base to be deleted can be selected. This operation is irreversible, so we must be sure this data base information will never again be of any use. It should be noted that this command does not delete the “lsh” file of the LoadShedder2000®.project.
- Terminations required when several panels (CCFTT) are in use.
- The network cable “shields” must be linked when several panels in a project.
- Contact factory for the wire selection.
- The green “led” indicates that the application is working properly.
- The button near the green “led” is the card “reset”.
- The yellow “led” is the “led” neuron status.
- The button near the yellow “led” is the “service pin”.
- Please refer to the card silk screen for the input/output connector polarity.
2 YEAR LIMITED WARRANTY
The manufacturer warrants to the original user that its products will be free from defects in materials and workmanship for a period of two years after the date of shipment.
If any of the manufacturer’s product is found to be defective in material or workmanship during the applicable warranty period, the components shall be the repaired or replaced or the refund of the purchase price, at the manufacturer’s direction. The manufacturer shall not be held liable for any costs or expenses, whether direct or indirect, associated with the installation, removal or re-installation of any defective product.
This limited warranty shall not be effective unless there is compliance with all installation and operating instructions furnished by the manufacturer, or if the products have been modified or altered without the written consent of the manufacturer, or if such products have been subject to accident, misuse, mishandling, tampering, negligence or improper maintenance. Any warranty claim must be submitted in writing within the stated warranty period.
This limited warranty is made in lieu of, and the manufacturer disclaims all other warranties, whether expressed or implied, including but not limited to any implied warranty of the products.
The manufacturer shall not, under any circumstances be liable for any direct, indirect, accidental, special or consequential damage (including but not limited to, loss of profits revenues or business) or damage or injury to persons or property in any way related to the manufacture or the use of its products. The exclusion applies regardless of whether such damages are sought based on breach of warranty, breach of contract, negligence, strict liability in tort, or any other legal theory, even if the manufacturer was noticed of the possibility of such damages.
By purchasing our products, the purchaser agrees to the terms and conditions of this limited warranty.
How to contact us
For more information on Surf Networks® products concerning energy automation or management, please call: 561.447.8929 or email us at info@surfnetworks.com
Any representation or reproduction, in whole or in part, made without the permission of Surf Networks, Inc., is unlawful. Such unlawful representation or reproduction, made by any means, would be an infringement of copyright punished under the provisions of the copyright law. Microsoft Windows 95 and 98 are registered trade marks of Microsoft Corporation. All other products are registered trade marks of their respective companies.