Schneider Electric SW ABILIT.CBS/SPACELYNK/BMS enables system integrators to develop customized applications that can access system data, control devices, and create new visualizations. It provides a secure and reliable way to connect to Schneider Electric devices and systems, and to create custom applications that can be tailored to the specific needs of a building or facility.
Some of the possible use cases for Schneider Electric SW ABILIT.CBS/SPACELYNK/BMS include:
- Monitor and control HVAC systems
- Monitor and control lighting systems
- Monitor and control security systems
- Monitor and control energy consumption
advertisement
Basic / Advanced / Expert
Application note
EXIWAY POWER CONTROL connected to
StruxureWare Building Operation via spaceLYnk
A smart configuration to share data between EXIWAY
POWER CONTROL and StruxureWare Building Operation solution.
AN019_v1-1_EXW-P-C_Connected_to_SBO_via_spaceLYnk
Safety Information
Important Information
Read these instructions carefully before trying to install, configure, or operate this software. The following special messages may appear throughout this bulletin or on the equipment to warn of potential hazards or to call attention to information that clarifies or simplifies a procedure.
The addition of either symbol to a “Danger” or “Warning” safety label indicates that an electrical hazard exists which will result in personal injury if the instructions are not followed.
This is the safety alert symbol. It is used to alert you to potential personal injury hazards. Obey all safety messages that follow this symbol to avoid possible injury or death.
DANGER
DANGER indicates an imminently hazardous situation which, if not avoided, will result in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided, can result in death or serious injury.
CAUTION
CAUTION indicates a potentially hazardous situation which, if not avoided, can result in minor or moderate injury.
NOTICE
NOTICE is used to address practices not related to physical injury. The safety alert symbol shall not be used with this signal word.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 2 / 32
Please Note
Electrical equipment should be installed, operated, serviced, and maintained only by qualified personnel.
No responsibility is assumed by Schneider Electric for any consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction, installation, and operation of electrical equipment and has received safety training to recognize and avoid the hazards involved.
Safety Precautions
WARNING
HAZARD OF INCORRECT INFORMATION
Do not incorrectly configure the software, as this can lead to incorrect reports and/or data results.
Do not base your maintenance or service actions solely on messages and information displayed by the software.
Do not rely solely on software messages and reports to determine if the system is functioning correctly or meeting all applicable standards and requirements.
Consider the implications of unanticipated transmission delays or failures of communications links.
Failure to follow these instructions can result in death, serious injury, or equipment damage.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 3 / 32
The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information that is contained herein. If you have any suggestions for improvements or amendments or have found errors in this publication, please notify us.
No part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express written permission of Schneider Electric.
All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and to help ensure compliance with documented system data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper operating results.
Failure to observe this information can result in injury or equipment damage.
© 2014 Schneider Electric. All rights reserved
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 4 / 32
Table of Contents
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 5 / 32
1 Introduction
This application note describes method to connect EXIWAY POWER CONTROL (EXW-P-C) to StruxureWare
Building Operation (SBO) solution with a spaceLYnk (SL).
Added value of this application note
The customer value proposition corresponds to a real use case, connect a EXW-P-C (Exiway Power Control) and a SBO solution.
EXW-P-C manages emergency lighting in a building. All information of the installation are transmitted by spaceLYnk to SBO. spaceLYnk is used like a gateway, it converts information received from EXW-P-C for SBO solution.
Competencies
This document is intended for readers who have been trained on spaceLYnk, EXW-P-C and SBO products.
The integration should not be attempted by someone who is new to the installation of each product. In addition we recommend that you be familiar with:
The concepts of KNX technology
Basic technical knowledge of BACnet, Modbus TCP/IP & RTU, LUA scripting
Basic technical knowledge of EXW-P-C product
Basic technical knowledge of SBO product
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 6 / 32
System prerequisites
Before you begin, ensure you have the proper software. You can download the latest versions here:
Software Version Download spaceLYnk
Building Operation Workstation
Entreprise/Automation Server
Exiway Power Control
EXW_P_C Modbus license
Firefox
1.1 and newer
1.4.0 and newer
Latest version
Latest version http://www.schneider-electric.com
http://www.schneider-electric.com
33.0 and newer http://www.mozilla.org
Table 1: System prerequisites http://buildings.schneider-electric.com
http://buildings.schneider-electric.com
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 7 / 32
2 Design
SpaceLYnk is used as a gateway between one EXW-P-C and one SBO.
This gateway converts the Modbus RTU protocol, coming from EXW-P-C, to BACnet and Modbus TCP protocol for SBO.
Figure 1: Architecture of spaceLYnk integration between EXW-P-C and StruxureWare Building Operation Entreprise server
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 8 / 32
In the image it is better to have the full name EXIWAY POWER CONTROL
What is Modbus?
Modbus is a serial communication protocol originally published by Modicon (now Schneider Electric) in 1979 for use with its programmable logic controllers (PLCs). Simple and robust, it has since become a de facto standard communication protocol, and it is now a commonly available means of connecting industrial electronic devices.[1] The main reasons for the use of Modbus in the industrial environment are:
developed with industrial applications in mind
openly published and royalty-free
easy to deploy and maintain
moves raw bits or words without placing many restrictions on vendors
What is Modbus TCP?
Modbus TCP/IP (also Modbus-TCP) is simply the Modbus RTU protocol with a TCP interface that runs on
Ethernet.
The Modbus messaging structure is the application protocol that defines the rules for organizing and interpreting the data independent of the data transmission medium.
TCP/IP refers to the Transmission Control Protocol and Internet Protocol, which provides the transmission medium for Modbus TCP/IP messaging.
Simply stated, TCP/IP allows blocks of binary data to be exchanged between computers. It is also a world-wide standard that serves as the foundation for the World Wide Web. The primary function of TCP is to ensure that all packets of data are received correctly, while IP makes sure that messages are correctly addressed and routed. Note that the TCP/IP combination is merely a transport protocol, and does not define what the data means or how the data is to be interpreted (this is the job of the application protocol, Modbus in this case).
So in summary, Modbus TCP/IP uses TCP/IP and Ethernet to carry the data of the Modbus message structure between compatible devices. That is, Modbus TCP/IP combines a physical network (Ethernet), with a networking standard (TCP/IP), and a standard method of representing data (Modbus as the application protocol). Essentially, the Modbus TCP/IP message is simply a Modbus communication encapsulated in an
Ethernet TCP/IP wrapper.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 9 / 32
What is BACnet?
Building Automation and Control Network (BACnet) is a data communication protocol for building automation and control through networks. This protocol is supported by:
American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE)
American National Standards Institute (ANSI)
International Organization for Standardization protocol (ISO)
BACnet was designed to allow communication of building automation and control systems for application such as heating, ventilation, air - conditioning control, lighting control, access control, fire detection systems and their associated equipment. BACnet protocol provides exchange information for building automation devices, regardless of the particular building service they perform.
The Enterprise Server manages data from BACnet protocol. This includes:
centralized logging
display
application version of a StruxureWare Building
data management
The Enterprise Server also serves as a single point of administration through your WorkStation or your
WebStation for StruxureWare Building Operation
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 10 / 32
3 Connect spaceLYnk
Connect 24VDC
1
and 0VDC
2
from 24V supply.
Connect Tx
3
to RXD in EXW-P-C COM1 (see the “User Manual” of EXW-P-C).
Connect Rx
4
to TXD in EXW-P-C COM1 (see the “User Manual” of EXW-P-C).
Connect GND
5
to DCD in EXW-P-C COM1 (see the “User Manual” of EXW-P-C).
Connect Ethernet RJ45 socket
6
to your PC (for the first step).
4
3 4 5 1 2
Power ON spaceLYnk.
Figure 2: spaceLYnk connections
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 11 / 32
4 spaceLYnk network setting
4.1
Open spaceLYnk Web IDE
Run Mozilla Firefox (with Windows, OS X, Linux) or Safari (if iOS) with SL URL containing SL IP address (in our example: http://192.168.0.10
) to access the SL start page:
Left click on Configurator
1
.
1
You get a Login page:
The default login and password are:
Login: “admin”
Password : “admin”
Figure 3: homeLYnk start page
Figure 4: spaceLYnk configurator login page
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 12 / 32
4.2
Change network setting
Left click on System
1
Figure 5: spaceLYnk configurator home page
System opens a new page.
On the Network tab, Left click on Interfaces
2
2
Figure 6: System window
System opens the Interfaces setting window
Left click on eth0
3
3
Figure 7: Interfaces setting window
System opens the Interfaces eth0 setting window.
1
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 13 / 32
Select “Static IP” in Protocol
4 combobox.
Set the static IP address in IP address
5
.
Set the Network Mask
6
.
Set the Gateway IP
7
.
Set the PDNS server
8
.
Left click on OK
9
4
5
6
7
8
9
Figure 8: Interfaces eth0 setting window
Left click on Apply changes
10 in the upper right of the window. The spaceLYnk will be restarted.
10
Figure 9: Apply changes
Disconnect the Ethernet cable between spaceLYnk and your PC.
Connect spaceLYnk to your network with Ethernet cable.
Access to the spaceLYnk with new address IP to check the network configuration.
The spaceLYnk network is configurated.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 14 / 32
5 spaceLYnk solution configuration
To integer spaceLYnk between EXW-P-C and a local company server, it is necessary to follow next steps.
1) Import backup in spaceLYnk
2) BACnet configuration
Run Mozilla Firefox (with Windows, OS X, Linux) or Safari (if iOS) with SL URL containing SL IP address to access the SL start page:
5.1
Import backup in spaceLYnk.
Left click on Utilities
1
Left click on Restore
2
1
Figure 10: spaceLYnk configurator home page
2
Left click on Browse…
3
and select
“AN019_v1-1_EXW-P-C&SBOViaSpaceLYnk.tar.gz”
file stored on your PC in unzipped Application Note package (in SL_Backup folder) o The restoration backup will be deleting and replacing all information in spaceLYnk. Think out make a backup before if you need to conserve information actually in spaceLYnk.
Then, left click on Save
4
3
4
Figure 11: spaceLYnk backup restore window
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 15 / 32
You must get following window notifying you the restore has been well carried out
Figure 12: spaceLYnk backup restore success window
Check the following scripts have been installed: o
In Resident scripting part:
AN019_EXW-P-C_SCRIPT_1_ENABLE_GATEWAY
AN019_EXW-P-C_SCRIPT_2
AN019_EXW-P-C_SCRIPT_3
For all script:
Do not modify sleep interval.
Script is disabled by default. o
In User libraries scripting part:
AN019_libEXW-P-C
For all script:
Don’t modify sleep interval.
Script is active by default and it is to be permanently active. o
In Objects part:
Copy of all EXW registers in KNX objects
Do not modify information
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 16 / 32
5.2
Setting spaceLYnk BACnet configuration
Left click on System
1
Figure 13: spaceLYnk configurator home page
System opens a new page
Move the pointer of the mouse on Network
2
Left click on BACnet setting
3
2
Figure 14: System window
System opens the BACnet setting window
3
1
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 17 / 32
Check Server enable
4 checkbox is enable
Set the Device ID
5 of the spaceLYnk BACnet device. o BACnet device ID which must be unique on BACnet network. Range 0 - 4194302
Set the Password
6
Set the Object priority
7 o Define to which priority array spaceLYnk will write to. By default spaceLYnk doesn’t write to a priority array, it only writes to the Relinquish Default Property.
Set the Port
8 number o
BACnet port, default 47808.
Left click on OK
9
4
7
8
5
6
9
Figure 15: BACnet setting window
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 18 / 32
Shared data are shown on Network -> BACnet object
Left click on BACnet object
10
Figure 16: System window
10
System opens the BACnet objects window
Figure 17: BACnet objects window
Property Description
Device name Device name is combined from hostname and device ID
Download Download BACnet objects in CSV file
Table 2: BACnet objects properties
Note: spaceLYnk always write to Relinquish Default Priority. Writing to priority array is optional. We recommend using object priority 16 in StruxureWare Building Operation. Downloaded file name and format is depending of the browser, not spaceLYnk itself.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 19 / 32
5.3
Enable gateway
To enable gateway between EXW-P-C and SBO, it’s necessary to enable the script
“AN019_Modbus_RTU_Slave”
Left click on Scripting
1
Left click on Resident
2
Left click on Active
3
colon of the script “AN019_EXW-P-C_SCRIPT_1_ENABLE_GATEWAY”.
System opens a new page and left click on “Yes” o
Others scripts are automatically enable.
2
1
3
Figure 18: spaceLYnk Resident script
Check in alert display, if the EXW-P-C Gateway is enabling.
Warning: If you use the LCD display of EXW-P-C, the function test or the duration test of EXW-P-C, the
Modbus RTU communication between EXW-P-C and spaceLYnk is stopped during this time.
The spaceLYnk is configurated: SL configuration is finished.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 20 / 32
6 SBO BACnet configuration
Schneider Electric StruxureWare Building Operation is a BACnet certified Building Management System capable of discovering values exported from spaceLYnk (SL). Exported data can be used for information, control, or visualization. Communication between SBO and SL is bi-directional.
Enterprise/Automation server acts as a BACnet client.
To configure the Building Operation WorkStation follow these five steps:
1) Log into SBO
2) Add BACnet interface into Automation Server
3) Configure IP
4) Discover devices and upload BACnet objects
5) Set required priority to reveal actual exported values
Note: Server name in this application note is Enterprise/Automation Server. In case of change this name following steps must reflect this change.
Note: To use BACnet functionality, your Enterprise/Automation Server and your spaceLYnk need to connected in the same level network.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 21 / 32
Step 1: Log into SBO
1) Open your SBO program and enter your user name and password.
Main page of SBO program opens.
Step 2: Add BACnet interface into Enterprise/Automation Server
1) Right click Enterprise/Automation server
2) Click New
3) Click Interface
4) Click BACnet interface
5) Type your BACnet interface Name. You can leave preset name “BACnet interface”
6) Type your Location. You can leave the preset location
7) Click Create
Your BACnet interface is now available in system menu.
Figure 19: Add BACnet Interface into Enterprise/Automation Server
Note: If BACnet interface must be added to additional servers
1) Create your new server
2) Change Location for BACnet Interface object
3) Select your new location
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 22 / 32
Step 3: Configuring IP
Configuring SBO IP network allows you to establish connection between spaceLYnk and SBO to use Device discovery function to discover spaceLYnk device on the network.
Important : To use Device Discovery, you must set the IP settings of SBO to the same IP range as spaceLYnk.
1) Go to Enterprise/Automation server
2) Expand BACnet Interface
3) Click IP Network
4) Type your IP configuration
Figure 20: BACnet Interface configuration
IP address of your SBO is now set.
Note: In case of network collision change the value of the SBO IP port number.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 23 / 32
Step 4: Discovering devices and uploading BACnet objects
1) Click Enterprise/Automation Server
2) Click Device Discovery and select BACnet devices from pull down menu
List of all discovered devices displays
3) Drag and drop your spaceLYnk to BACnet Interface
IP network is displayed in System Tree
A pop up message informs you, that objects have to be uploaded to the database in SBO
4) Right click your spaceLYnk and then select Upload
Figure 21: Uploaded BACnet objects with values
Objects from your spaceLYnk are now synchronized with your SBO application
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 24 / 32
Step 5: Setting required priority to reveal live exported values
1) Click your spaceLYnk in System Tree
2) Expand spaceLYnk to show the Application folder
3) Click Application folder
Sub window with list of spaceLYnk objects appears
4) Right click on Description to see a list of possible BACnet properties to be displayed such as priority, data type, etc.
5) Select the check box of properties of your BACnet object to display them
Figure 22: BACnet objects
Application tab collects all exported values from spaceLYnk to BACnet. Values of BACnet objects are dynamically changed according to their current values. Live update of your spaceLYnk proves successfully established connection between SL and SBO. You can manually change values of your data to test the connection.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 25 / 32
7 SBO Modbus TCP/IP configuration
Schneider Electric StruxureWare Building Operation is a Modbus TCP/IP client certified Building Management
System capable of exchanging values with spaceLYnk (SL). Exported data can be used for information, control, or visualization. Communication between SBO and SL is bi-directional.
Enterprise server acts as a Modbus TCP/IP client.
To configure the Building Operation WorkStation follow these five steps:
1) Log into SBO
2) Import Modbus TCP Gateway interface into Enterprise/Automation Server
3) Optionnal: Import extended Modbus TCP registers
Note: Server name in this application note is Enterprise/Automation Server. In case of change this name following steps must reflect this change.
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 26 / 32
Step 1: Log into SBO
1) Open your SBO program and enter your user name and password.
Main page of SBO program opens.
Step 2: Import Modbus TCP Gateway into Enterprise/Automation Server
1) Right click on Enterprise/Automation server Import…
2) Select on your PC the file “SBO_Modbus_TCP_Gateway_Configuration_For_EXW-P-C.xml”.
3) Click on Import and Close.
4) Select Modbus TCP Gateway Properties Basic
5) Set IP address of the spaceLYnk
6) Set the IP port of the spaceLYnk
7) Click on the disk in the Modbus TCP Gateway tab to save the information.
Step 3: Optionnal: Import extended Modbus TCP registers
1) Right click on Modbus Device Import…
2) Select on your PC the file “SBO_Modbus_TCP_Extended_Registers_For_EXW-P-C.xml”.
3) Click on Import and Close.
Modbus registers from your spaceLYnk are now synchronized with your SBO
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 27 / 32
8 Enable Modbus RTU communication in EXW-P-C
The MODBUS/RTU protocol is enabled in the web interface using the feature key (4 digits) which is based on the system number.
To access at EXW-P-C web interface, use your web navigator and write the IP of the EXW-P-C in the url part.
The key is entered on page “Administration / options” in the option GLT Gateway
1
.
After saving
2
and reloading the page the key is validated.
A positive key validation is indicated with a green bullet or the text “OK”
3
behind the input field (meaning that the key is valid).
2
1 3
Figure 23: Administration frame of EXW-P-C web interface
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 28 / 32
Abbrevation
ASHRAE
ANSI
BACnet
ISO
SL
EXW-P-C
SBO
9 Conclusion
Procedures contained in this application note describe integration of spaceLYnk into a Enterprise/Automation server using BACnet and Modbus TCP. spaceLYnk functionality described in this application note brings benefits to system integrator to create robust automation system complying with international standards.
10 Appendix
10.1
Glossary
The following table describes the acronyms and defines the specific terms used in this document.
Description
American Society of Heating, Refrigerating and Air-Conditioning Engineers
American National Standards Institute
A data Communication Protocol for Building Automation and Control Networks
International Organization for Standardization protocol. spaceLYnk
Exiway Power Control is an emergency power supply system from Schneider Electric which supplies escape route and exit sign luminaires.
StruxureWare Building Operation
Table 3: Glossary
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 29 / 32
10.2
Annexe
BACnet ID
12541
12544
12545
12546
12547
12548
12549
12550
12551
12552
12553
12554
Modbus TCP register EXW register description
0x30FD
0x3100
0x3101
0x3102
0x3103
0x3104
0x3105
0x3106
0x3107
0x3108
GLT Gateway State
0 Gateway error (0=ok, 1=error). Read by the EXW-P-C
1 Gateway has been initialized (0=not initialized, 1=initialized). Set by the EXW-P-C
2 – 15 Reserved
System state A
0 Operating mode (0=charging, 1=operational)
1 Emergency lighting blocked (0=no, 1=yes)
2 Mains operation (0=no, 1=yes)
3 Battery operation (0=no, 1=yes)
4 Cumulative failure (0=no, 1=yes)
5 Charger (0=not active, 1=active)
6 Deep discharge (0=no, 1=yes)
7 Active (mains) / mod. stand-by (0=no, 1=yes)
8 Critical circuit (0=closed, 1=open)
9 – 15 Reserved
System state B
0 – 15 Reserved
Fault memory A (fault: 0=inactive, 1=active)
0 Maintenance required (0=no, 1=yes)
1 Battery earth fault (0=OK, 1=battery earth fault detected)
2 Battery fuse (0=OK, 1=fuse has blown)
3 Battery current (0=OK, 1=invalid range)
4 Battery voltage (0=OK, 1=invalid range)
5 Battery center voltage (0=OK, 1= valid range)
6 DCM / MLD fault
7 LDM / MCHG fault
8 IOM / MSWC fault
9 SAM / MMO fault
10 Fan failure
11 Luminary fault (collective luminary monitoring faults)
12 Current fault (collective current monitoring faults)
13 Circuit fault (collective circuit faults)
14 – 15 Reserved
Fault memory B
0 – 15 Reserved
Fault memory C
0 – 15 Reserved
Fault memory D
0 – 15 Reserved
Subsystem faults (1 to 16)
0 Subsystem 1 (0=OK, 1=errors present)
...
15 Subsystem 16 (0=OK, 1=errors present)
Subsystem faults (17 to 32)
0 Subsystem 17 (0=OK, 1=errors present)
...
15 Subsystem 32 (0=OK, 1=errors present)
Battery voltage (Resolution 0.1V) (signed int)
0x3109 Battery center voltage (Resolution 0.1V) (signed int)
0x310A Battery current (Resolution 0.1V) (signed int)
Table 4: Objects list (part 1/2)
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 30 / 32
BACnet ID
12555
12556
12557
Modbus TCP register EXW register description
0x310B Mains voltage L1 (Resolution 0.1V) (signed int)
0x310C
0x310D
Mains voltage L2 (Resolution 0.1V) (signed int)
Mains voltage L3 (Resolution 0.1V) (signed int)
12558
12560
12561
12800
12801
12802 … 12806
12809 … 12814
12817 … 12822
12825 … 12830
12833 … 12838
12841 … 12846
12849 … 12944
0x310E
0x3110
0x3111
0x3200
0x3201
0x3202 … 0x3206
0x3209 … 0x320E
0x3211 … 0x3216
0x3219 … 0x321E
0x3221 … 0x3226
0x3229 … 0x322E
0x3231 … 0x3290
Mains voltage N (Resolution 0.1V) (signed int)
Temperature cabinet (Resolution 0.1°C) (signed int)
Temperature battery (Resolution 0.1°C) (signed int)
First and last installed circuit
0..7 First circuit number (1..96)
8..15 Last circuit number (1..96)
Circuit 1 to 16 installed
0 Circuit 1 (0=empty, 1=installed)
1 Circuit 2 (0=empty, 1=installed)
...
15 Circuit 16 (0=empty, 1=installed)
Circuit 17 to 96 installed
Bit 3202.0: circuit 17, etc. (0=empty, 1=installed)
Circuit 1 to 96 Operation mode
0=maintained mode (BS), 1=non-maintained mode (DS)
Circuit 1 to 96 Faults
Bit 3211.0: faults on circuit 1, etc. (0=OK, 1=Fault: fuse blown or earth fault)
Circuit 1 to 96: Fuse state
Bit 3219.0: fuse state on circuit 1, etc. (0=OK, 1=fuse has blown)
Circuit 1 to 96: Earth fault
Bit 3221.0: earth fault on circuit 1, etc. (0=OK, 1=earth fault)
Circuit 1 to 96: Current monitoring faults (on circuit level)
Bit 3229.0: current fault on circuit 1, etc. (0=OK, 1=current fault)
Circuit 1 to 96: Circuit power
Measured power during the last test (resolution 1W)
Register 3231: circuit 1, etc.
Circuit 1 to 96: Luminary faults (collective fault on 13138 … 13143 0x3352 … 0x3357
13145 … 13146 0x3359 … 0x335A circuit level)
Bit 3352.0: luminary faults on circuit 1, etc. (0=no faults, 1=faults)
Circuit 1: Luminary failure (on luminary level 1-20)
Bit 3359.0: lamp 1, Bit 3359.1: Lamp 2, ... Bit 335A.3: Lamp 20 (0=OK, 1=fault)
… 13147 … 13334 0x335B … 0x3416
13335 … 13336 0x3417 … 0x3418
13501 … 13522 0x34BD … 0x34D2
13544 … 13545
13546
13548 … 13549
0x34E8 … 0x34E9
0x34EA
0x34EC … 0x34ED
Circuit 96: Luminary failure (on luminary level 1-20)
(Bit 3417.0: lamp 1, Bit 3417.1: lamp 2, ...Bit 3418.3: lamp 20)
System name (43 chars) (22 registers)
System number (32 bit) (2 registers)
NLSR firmware version (16 bit)
System IP address (32 bit) (2 registers)
Table 5: Objects list (part 2/2)
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 31 / 32
Schneider Electric Industries SAS
Head Office
35, rue Joseph Monier
92506 Rueil-Malmaison Cedex
FRANCE www.schneider-electric.com
AN019_v1-1_EXW-P-C_connected_to SBO_via spaceLYnk
Page 32 / 32
advertisement