Building Automation Knowledge Base

Issue Can Newron NL220 or Echelon LonMaker systems run on a 64-bit operating system? Product Line TAC Vista Environment Windows 7 64-bit Windows Server 2008 64-bit LNS Newron NL220 4.5.12 Echelon  Lonmaker Turbo SR4 Cause Support is  provided for Newron NL220 4.5.13 on 64-bit operating systems. Lonmaker SR4 does provide some support for 64-bit systems. Resolution The current supported operating systems for this environment are as follows: Newron NL220 4.5.12 Windows NT Windows 2000 Windows 2003 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 (32-bit)   Newron NL220 4.5.13 Windows XP (32-bit) Windows Vista (32-bit) Windows 7 32-bit and 64-bit Server 2003 32-bit and 64-bit Server 2008 32-bit and 64-Bit http://www.newron-system.com/index.php?Page=soft&Traite=download&Prod=nl220te (Account needed to view this document) Lonmaker Turbo SR4 32-bit version of Windows 7, Server 2008, Windows Server 2003 R2 with MSXML 6.0 Windows Vista with Service Pack (SP) 1, or Windows XP with SP3.  http://www.echelon.com/support/documentation/datashts/370xx-324_LonMakerTurbo_SR4.pdf 64-bit versions For 64-bit operating systems, please refer to Echelon's Software Compatibility List for restrictions and approved configurations: http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0339-01A   Lonmaker 3.1.3            32-bit version of Windows 98. Windows 2000. Windows XP. http://www.echelon.com/Support/documentation/datashts/370x0.pdf

Issue RAM, Remote Alarm Manager Environment Sigma, Micronet, BAS, Vista, RAM 1.2 Cause Configuration Controller Monitoring Scripts Output Interfaces Resolution There are 3 guides to assist in configuring RAM: Operators Manual Engineers Manual (more comprehensive than the Operators Manual) Script Editors Guide Note: There are scripts that are used in RAM. These can adapted to suit specific requirements. Copy the relevant script and rename. Use the renamed version. The scripts can be found in C:\Satchwell\Binary\Remote Alarm Manager and have the .scr extension. 

Issue What is the replacement for the Drayton Autotherm? Environment Drayton Autotherm Cause The Drayton TA/L1 actuator is obsolete, and no like for like actuators are available, this makes the Autotherm controller unusable. Resolution The TA/L1 actuator provides positional feedback to the Autotherm controller, and actuators providing feedback are very few, and providing the correct feedback is not possible. The Autotherm controller provides considerable functionality, and in our current  ranges of controllers, these cannot be matched. To upload the Autotherm data sheet, please click HERE.     The most appropriate replacement controller is CSC5352. This device will provide a compensated heating system with a timed start, the output relay can be used to enable the hot water system. Please click HERE to upload the data sheet. If separate time periods are required for the heating system and how water system, then the DC1100/1400 should be considered. Please click HERE to upload the data sheet. Please note that in both of the above options, new sensors will be required and possibly actuators too.

Issue Some actuators manufactured by Belimo are also available from Schneider Electric Environment Various Belimo Actuators: AF 230 AF 230-S AF 24 AF 24-S AF 24-SR LF 230 LF 24 LM 230 A LM 230 A-S LM 24 A LM 24 A-S LM 24 A-SR NM 230A NM 24A NM 24A-SR SM 230A SM 24A SM 24A-SR Various Schneider electric actuators, part no: 875-0000-010 875-0010-010 874-0000-010 874-0010-010 877-0000-010 875-0003-000 874-0003-000 875-1001-000 875-1003-000 875-1005-000 875-1007-000 875-1009-000 875-1011-000 875-1015-000 875-1019-000 875-1021-000 875-1025-000 875-1029-000   Cause Cross reference between various actuators of Belimo and Schneider Electric Resolution A cross reference table for these actuators can be found here (.xls).

Issue There isn't enough documentation on how to disable the different connection protocols. I.e. TLS or SSH. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Cause Increase the security of the system. Resolution SSL Communication Security Settings: You can edit SSL configuration in WorkStation Control Panel's Security Settings or in the Device Administrator SSL Security Settings tab. SSLv1,v2,v3 are all implicitly disabled. In EBO 2022 (4.0) or higher, TLS 1.3 is available and used as default when logging on with WebStation and for server-server communication with HTTPS. TLS 1.0 and TLS 1.1 are by default disabled but can be enabled in Control Panel. WorkStation is using TLS 1.2, disabling it would prevent logging on to WorkStation. In WorkStation, the only valid protocols are shown when you hover the mouse over disabled protocols. See below.   SSH Port: Port used for communication with Device Administrator can be disabled or changed so that the automation server communicates on another port using SSH. It is also possible to disable all SSH communication. SSH communication settings are available in Automation Server Properties – Network Tab, as shown below. Refer to Disabling Port 22 on SmartX Server and Adding an Additional SSH Port for a SmartX Server .  For more Security guidelines,  refer to EcoStruxure Building Management - System Hardening Guide, Security Overview, and Information Technology System Planning Guide 

Issue Project specifications call for there to be no default administrator password in the BMS.  Can the ACC user in Andover Continuum be deleted? Product Line Andover Continuum Environment Administrator password Continuum CyberStation Permissions Cause By default Andover Continuum always creates the ACC administrative user on all system but this is deemed unacceptable by some project specifications. Resolution The Andover Continuum default ACC admin user cannot be deleted, however it can be renamed and its permissions can be removed/amended.  

Issue How can the format of a custom card be determined/understood Product Line Andover Continuum Environment Access Control AC1 AC1Plus ACX Cause The format of access cards is unknown. Resolution The document Understanding custom card formats in Continuum describes how to determine the custom format of proximity cards.  

Issue Steps for replacing a BACnet B3 controller and things to consider. Product Line Andover Continuum Environment Continuum b3xxx Controller Cause Steps for replacing a BACnet B3 controller and things to consider. Resolution Steps for replacing a B3 controller and things to consider. Use these steps when replacing a B3 controller from brand new stock, it is relatively straight forward. Physically disconnect power and MS/TP data cables from existing B3 Controller. Remove existing B3 Controller. Install replacement B3 Controller. Pull the battery tab on replacement B3. Connect MS/TP data cable to the replacement B3 controller. Connect power to the replacement B3 controller. Edit the B3 controller object in Continuum on the infinity side. On the Runtime tab enter the Serial Number of the new replacement B3 controller and click Apply. Click refresh until B3 controller returns Online. Reload the B3 Controller. Verify existing points and programs are running correctly. Perform a “Backup to Flash” operation on the B3 controller. Perform “Send to Database” operation on B3 controller from BACnet view. One scenario, for example, is the Replacement B3 controller came from a different job that has previously been programmed and has a valid flash backed up onto it. If installed on the new network, when powered up will start trying to communicate with controllers it has routing tables for. Could potentially cause issues on the new network. It is suggested that if you are replacing with a previously used controller from an old site with a valid flash backed up is to flush the controller out before applying to the new network. From a test machine with a test DB bring the controller online, this will require a BCX to do as well. Once the B3 is learned in and online, perform a reload to the controller and then a backup to flash. The only thing that will be reloaded will be the system variables. Another thing to think about is let's say you've already replaced the B3 and sent it off to repair. You've got it back and now want to put it back to its original location. That one is very simple and following the replacement steps above will suffice. Just remember that step 8 above you would make sure the Bacnet Device ID and the serial number match for the original unit integration. But if you wanted to add a new B3 controller to the same site and use the repaired B3 as a newly installed controller, just remember that the previously replaced B3 will have the Bacnet Device ID of the repaired B3 and you'll have to make sure that when manually creating a new B3 with the repaired B3 you'll have to make a new Bacnet Device ID that is unique. Rules to remember: Flush out used B3 controllers before adding to an existing MS/TP network or replacing a defective B3 Bacnet Device ID's must be unique for each given BACnet network  

Issue EcoStruxure Building Operation allows using a period embedded in the name of an object (i.e My.AnalogValue) and  the name of a binding variable in the Script program cannot contain a period.     In the Script program all the periods in the binding variable names have to be changed to a different character such as the underscore (_).   This in turn causes a problem for a programmer that has created many objects using the period in the names as it is now NOT possible to use the default name matching binding template. Product Line EcoStruxure Building Operation Environment Script Programs Enterprise Server Automation Server Cause Script programs do not allow a period '.' in binding variable names because the period has special functionality in the Script compiler. Resolution Create a new path matching binding template or edit an existing one to map the underscore to the period.     Here is a second example:   Name of point/value contains embedded '.' as well as spaces      This is what the binding variable would look like in the Script program   and here is the Path Matching Template

Issue How do I time sync my controllers to my workstations? Product Line Andover Continuum Environment Continuum site Cause The workstation will only synchronize its time to the controllers automatically when the controller is reloaded. It is common practice though to have the controller synchronize its time with the workstation on a periodic basis, commonly once a day. Resolution The only way to synchronize time between the Controller and the Workstation is through a Plain English program running the Workstation. This Program only needs to be created in one Workstation. Below is an example of the program as well as how to trigger the program to run. If Minute = 3 then Goto SetTime Else Stop SETTIME: Set NetworkName\LowestNodeCXName\Date to Date Stop E: Stop Note: This program needs to be triggered off the minute system variable. The program is a Fallthru program which resides in the CyberStation. You only need to do the lowest ACCNet Id controller in each Continuum network. Also ensure that the UTC offset has been correctly entered in every Workstation and BACnet device, and that each Network has the correct Time Zone setting.

Issue Need to use Mobile Apps to access EBO. Product Line EcoStruxure Building Operation Environment Building Operation Webstation Building Operation Commission mobile application Building Operation Engage mobile application Cause What are the mobile apps available to use with EcoStruxure Building Operation sites? Resolution WebStation: WebStation is a web-based user interface for day-to-day operation in an EcoStruxure BMS. WebStation, V2.0 or higer, improves user experience by automatically adapting the user interface to the resolution of the device being used: desktop, laptop, tablet or smartphone, using Windows, Linux, Android or iOS, out-of-the-box using standard web browsers, without the need to install additional applications.  WebStation replaces the obselete Technician Tool app. Refer to: WebStation Overview Building Commision: EcoStruxure Building Commission mobile application (requires EBO V2 or higher, formerly eCommission) is designed to help airflow balancers, electricians, and technicians carefully and quickly pre-commission and commission SpaceLogic BACnet/IP devices and RP controller expansion modules. The Commission mobile application does not require a license for activation and is available at no cost to the user. It is designed for use with Android, iOS (Apple), and Microsoft Windows 10 and Windows 11 devices, and is available for download from Google Play, Apple App Store, and Microsoft Store. Refer to: Commission Mobile Application Engage: The Engage mobile application (requires EBO V3.1.2 or higer) enables control of room temperature, fan speed, lights, and blinds/shades directly from a smartphone. A user can manage these settings when the application is connected to the RP-C controller. The Engage mobile application connects easily via BLE (Bluetooth Low Energy) to the RP-C controller. The application is compatible with RP-C (HVAC) and RP controller expansion modules (lights and blinds). The Engage mobile application is free and available for download from Google Play and Apple App Store.  

Issue What actuator can be used as a replacement for the MF-63123? MF-631x3 Series_F_24732_8.pdf (209 KB) MFC 8000_F_25124_4.pdf (260 KB) Product Line Field Devices Environment MF-63123 Cause Original actuator has failed, or requirement for a non US actuator. Resolution Using the installed valve details, the actuator can be selected from the Schneider Electric Valve and Actuator selection Tool.

Issue What is the BACnet attribute COV Increment and how to use it Product Line Andover Continuum Environment BACnet Cause The COV Increment attribute on a BACnet point is equivalent to the Threshold attribute of standard Continuum Infinity inputs. When a Continuum BACnet point is subscribed to by other BACnet devices using COV (Change of Value), its value must change by at least that COV Increment value before a new Value Notification will be sent out. Using this attribute will decrease network traffic especially on the MSTP network when subscribing to frequently changing values.  Resolution This CovIncrement attribute can be set in the BACnet point's Editor on the Basic Alarms Tab.   If you have a CyberStation prior to Version 1.8, setting this value from the point editor will not stay persistent in the controller after the controller is reloaded, it will default to 0. In order to keep the value after a reload, you will need to write a PE program to set the desired value after a reload. The program should be Autostart and Fallthru. A sample of the program is below: Line SetCov Writeproperty("Full Bacnet Path to Point", CovIncrement, "Desired Value") Stop If you have several points that need the CovIncrement set, you would just add the additional lines into this program.   In 1.8 or greater, this program is not needed as these attributes get sent to controller on a reload. Suitable initial CovIncrements still need to be added to each BACnet point however as they default to 0.

Issue Performing Load Sources in the EcoStruxure ETL tool causes errors with the following headers:   There was no endpoint listening at http://localhost:8080/EcoStruxure/DataExchange that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. The HTTP request is unauthorized with client authentication scheme 'Digest'. The authentication header received from the server was 'Digest realm="ews@SxWBM",qop="auth",nonce="AEEE5A9347E49ECADC753B5AA17EECE0",OPAQUE="5B4718"'. Product Line EcoStruxure Building Operation Environment EcoStruxure Energy Expert (formally Power Manager) Enterprise Server Automation Server Cause The EBO EWS Extract Task settings are incorrect in regards to the EcoStruxure ES or AS that it is trying to access.    There was no endpoint listening at... This error is due to the use of the incorrect port numbers in the EWS Web Service URL.   The HTTP request is unauthorized with client authentication scheme 'Digest'... This error is due to the use of the incorrect admin Username and/or Password.  Resolution The settings of EBO EWS Extract Task need to be verified and corrected.    Click on the Tasks tab in the ETL tool and select the "EWS Extract Task". The extract task settings will be displayed on the right side of the screen.                                                                               Verify that the port number in Web Service URL address corresponds to the port number being used by the ES or AS  Verify that a valid Username and Password has been entered into the EWS Web Service User Name and Web Service Password fields. 

Issue Issues being experienced can vary, here are some examples: The digital clock gains a minute every few seconds. The code (0112) when entered to accept alarms, is not accepted. Environment DC1100 controller DC1400 controller Cause The unit has not been correctly cold-started after first being powered on. Resolution The DC1100 / DC1400 controllers must be correctly cold-started after first powering up, this ensures that the default configuration is correctly installed. Cold-start the controller using the following process: Turn off the power to the controller. Press and hold in the ENTER and EXIT keys. Power up the controller whilst continuing to press the ENTER and EXIT keys. Release the ENTER and EXIT keys. The controller will now go through a self test programme and load its defaults. To review the DC1100 / DC1400 controller overview, select here To review the DC1100 controller general data sheet, select here To review the DC1100 controller installation, wiring and Commissioning information select here To review the DC1400 controller general data sheet, select here To review the DC1400 controller installation, wiring and Commissioning information select here

Issue How to use bit masking to decode on/off states from a Modbus analogue registers e.g. Holding or Input registers. Where each bit is required to be read individually to indicate the status of a coil. Product Line Satchwell Sigma Software Environment Sigma IC Modbus and IC3 Modbus controllers Cause Configuration technique to read 16-bit Modbus registers for on/off states. Resolution Each modbus holding or input register is 16 bits, where each bit can be on or off i.e. 0 or 1. For example the Sigma analogue input value of 901 represents the state of a number of coils where each bit indicates the on or off.  Hence, this translates to the 16-bit binary value  0000001110000101  where 1 = on and 0 = off Create a Sigma analogue input object to read the Modbus value. Click here for the  Sigma Modbus 4.06 release Note Create a programmable object for each of the required bits (max of 16 for each register) to be read as below.  (Highlight, copy and paste into each programmable object). For Example starting with the Least Significant Bit (LSB) and where point 0|222 is the Modbus value created, the programmable objects are; Bit 1 (LSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1 ) 30 IF YINT = 1 THEN RETURN TRUE "Bit 1 = on" 40 RETURN FALSE "Bit 1 = off" Bit 2 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2 ) 30 IF YINT = 2 THEN RETURN TRUE "Bit 2 = on" 40 RETURN FALSE "Bit 2 = off" Bit 3 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4 ) 30 IF YINT = 4 THEN RETURN TRUE "Bit 3 = on" 40 RETURN FALSE "Bit 3 = off" Bit 4 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8 ) 30 IF YINT = 8 THEN RETURN TRUE "Bit 4 = on" 40 RETURN FALSE "Bit 4 = off" Bit 5 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16 ) 30 IF YINT = 16 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 5 = off" Bit 6 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32 ) 30 IF YINT = 32 THEN RETURN TRUE "Bit 6 = on" 40 RETURN FALSE "Bit 6 = off" Bit 7 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 64 ) 30 IF YINT = 64 THEN RETURN TRUE "Bit 7 = on" 40 RETURN FALSE "Bit 7 = off" Bit 8 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 128 ) 30 IF YINT = 128 THEN RETURN TRUE "Bit 8 = on" 40 RETURN FALSE "Bit 8 = off" Bit 9 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 256 ) 30 IF YINT = 256 THEN RETURN TRUE "Bit 9 = on" 40 RETURN FALSE "Bit 9 = off" Bit 10 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 512 ) 30 IF YINT = 512 THEN RETURN TRUE "Bit 10 = on" 40 RETURN FALSE "Bit 10 = off" Bit 11 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1024 ) 30 IF YINT = 1024 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 6 = off" Bit 12 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2048 ) 30 IF YINT = 2048 THEN RETURN TRUE "Bit 12 = on" 40 RETURN FALSE "Bit 12 = off" Bit 13 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4096 ) 30 IF YINT = 4096 THEN RETURN TRUE "Bit 13 = on" 40 RETURN FALSE "Bit 13 = off" Bit 14 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8292 ) 30 IF YINT = 8292 THEN RETURN TRUE "Bit 14 = on" 40 RETURN FALSE "Bit 14 = off" Bit 15 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16384 ) 30 IF YINT = 16384 THEN RETURN TRUE "Bit 15 = on" 40 RETURN FALSE "Bit 15 = off" Bit 16 (MSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32768 ) 30 IF YINT = 32768 THEN RETURN TRUE "Bit 16 = on" 40 RETURN FALSE "Bit 16 = off"

Issue What 10k Thermistor sensors are compatible with the I/A Series MNL and MNB families of controllers? Product Line TAC IA Series, Andover Continuum Environment I/A Series LON Controllers (MNL-xxxxx) I/A Series BACnet Controllers (MNB-xxxxx) Continuum 10K T3 Sensors Cause Specification information Job spec requires a specific family of sensors.  Need to know how to compare the TC curves. Resolution Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850, TS-57011-850, TS-57031-850, and TSMN-90110-850 Series.  NOTE: These sensors are no longer available for purchase. The TW2XAXK is the replacement Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S.Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span.   This includes the Continuum 10K T3 sensors.  The table below shows that the resistance in its normal operating range is within a few ohms of the TSMN non 11K shunted sensors.  The Continuum sensor can be used with a parallel 11K ohm resistor. The full temperature / resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor can be found here.  Please note that the controller may not be able to use the full temperature range shown in the table.    

Issue What is the difference between a Numeric Input, Numeric Output and Numeric Public within a script program. Is using a Numeric Public a less efficient choice (as opposed to using a Numeric Input or Numeric Output) that will generate negative overhead in the AS? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS, AS-P or AS-B) Building Operation Workstation b3 and Infinet controllers Cause Want to determine best practices when choosing numeric types during script programming. Resolution Numeric Input is a read only numeric (from the point of view of the script program) that accepts a binding. Numeric Output is a write only numeric (from the point of view of the script program) that accepts a binding. Numeric Public is both read and write (from the point of view of the script program). Numeric Public also accepts a binding. (A Numeric Public can be bound to both a Graphic and a Value Object to allow overriding of values from a Graphic. See SBO Script Public.zip for an example) When choosing the numeric type in a script program there is no overhead cost difference between using one of these numeric types vs the others. Also check out the Script Programming - Writing the Script Program Quick-Help video on the Exchange. NOTE b3 and Infinet Controller scripts do not support "Numeric Public", but "Numeric Output", in these controller scripts, can be used in a similar way to "Numeric Public" The Bound value is read by the script as well as being written to.

Issue Tips for Configuring HID OSDP Reader LED Colors Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert OSDP Reader Cause Additional tips for configuring OSDP Reader LED Colors Resolution The Configuring LED Colors section of AN-254 Configuring OSDP Readers in Security Expert  details the basic steps for LED configuration. This article details some additional areas of the HID reader setup and Security Expert configuration that may be useful when configuring the LED colors.   Note: The steps in this article are specific to an HID Signo RP10 Reader BLE and may not apply to other HID reader models or other brands of OSDP readers.   Upgrade the Reader firmware to the latest version. Earlier versions of the reader firmware would not correctly allow LED control. The Bluetooth option allows the configuration of the reader using the HID Reader Manager App. For detailed information see HID Reader Manager App Information Note: To use the HID Reader Manager App to configure a reader, the Security Technician or Security Installer needs to create and register an account with HID. The Reader Manager Administrator for your organization or company needs to enroll this new account using the Reader Manager Service and issue an invitation code and key authorization for this and other readers. The Security Technician can then verify the key authorization has been received in the HID Reader Manager app. Detailed instructions for all of this are included in the HID Reader Manager App Information URL listed above.   HID Reader Manager App Firmware snapshots       In the HID Reader Manager App, change the Reader Options for LED color to "Host Controlled" in 2 places. The reader must be controlled by the Security Expert controller. Credential Reader AV LED Idle Color Ensure that the firmware for the following hardware is upgraded to these versions or greater in order for LED Color Output to work. Security Expert 4.3.308.46 SP-C 2.08.1234 MRDM2 1.2.590 In Security Expert the Outputs to control the LEDs need to be manually created. Programming> Outputs> Add A pop-up asking to Invert Output will display, select 'No' when prompted Output 3 (GreenLED Port 1) Output 4 (Red LED Port 1) Output 6 (Green LED Port 2) Output 7 (Red LED Port 2)   Name the Outputs whatever is appropriate Example:  GreenLEDPortON RedLEDPortOff LED Colors The default LEDs are Blue when Idle and Green when active. As an example, the LED colors will be changed to Red when Idle and Green when Active. Color Options:   Set the colors for both Red(idle) and Green(active) in the Security Expert Output Command Window for the newly created outputs RedLEDPortOff   GreenLEDPortOn Update the modules and wait for about 15 seconds before activating the output to test. Just saving the updated command setting doesn't work, the module must be updated.   Activate the GreenLEDPort1 - the color should change to what the output was set to in the command. In this case, green. Deactivate goes back to Off (idle) Red. GreenLEDPort1 = On State RedLEDPort1 = Off State   Note: The Off state if left at the default of Blue can't be used with the On state of custom(non-default). Both Outputs must be specified in the command window for the colors to work together.   Example: If the OFF state is left at the default of blue and the color of the ON state is set in the command window and Activated, the LED color will change to what it is set to(green), but when deactivating the Off(idle) output it will not turn blue.

Issue Modbus RTU Serial Device (RS485 - Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus RTU Master RS485 Network Cause Third party Modbus device has an address range between 248 and 255. Resolution For Modbus master/slave RS485 networks, the third party device must be in the range of 1 to 247, this is the Modbus RTU standard. This would apply not only to EBO but to other Modbus master/slave networks.   The KB article Modbus basics explains this amongst other Modbus topics.   If the third party Modbus slave device cannot be changed to an address to within this range, then contact with the product vendor may be required.   For TCP devices see the KB article Modbus TCP Device (Slave) address greater than 247.