Building Automation Knowledge Base

Issue Is it possible for multiple Automation Servers to be placed on the same backplane and use one power supply? Some known issues in this unsupported configuration: Automation Server only partially discovers the IO Modules Function Block Programs (FBP) remain in an unloaded state (see FBP Unloaded) EBO 2022 (v4.0) and higher, Alarm: IO Driver unexpectedly timed out Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (EBO 2022 and above) EcoStruxure Building Operation Power Supply (PS-24V) EcoStruxure Building Central IO Modules Cause The terminal bases provide a path for communication between all connected units on the same backplane; as such, the connection of two or more Automation Servers will cause communication issues between all connected units on that same backplane. See the following article on how to check the CIO node the Automation Server is using: How to identify Automation Server(AS) ID node count   Resolution From EBO 2022 (v4.0.1) due to changes in the Central I/O (CIO), checks are now made in the Automation Server to verify that the server is physically in SLOT 2; if this is not the case, then all Tasks are disabled and will not run.    You cannot connect more than one Automation Server to the backplane. Only one Automation Server is allowed per power supply, the architecture is always "PS-AS-....." and after that I/O modules with additional PS units as needed, but only one Automation Server can exist on the same backplane.   Note that an alarm will also generate if you attempt the following configuration (also not supported)  PS-AS-PS-AS  Alarms will only clear after a restart (warm) of the server 

  Issue A License Violation alarm is triggered without displaying a License Violation banner. Alarm reactivates after acknowledgment, approximately every 10 minutes.     Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Potential communication issue, possibly related to return path or port configuration. An incorrect ES port may be in use, contributing to the issue. The Communication Tab [Communication View] and Server List in xbk Analyzer show only the ES, indicating limited server visibility. Resolution Verify Communication Path Ensure the ES is defined as using the same ports across all servers. Confirm that the ports are correctly configured and open on all relevant servers. Review the Communication Tab [Communication View] and Server List Check that all expected servers are listed and actively communicating. If only the ES is visible, investigate potential network or configuration issues. See article for additional information: Updating a Enterprise Server IP Address - Schneider Electric Community Check AS Logs Log in to the Automation Servers to identify any communication errors. These errors may not be visible from the ES alone. Next Steps If the above steps do not resolve the issue or the root cause remains unclear: Refer to the article for possible communication-related troubleshooting options: Enterprise Server and Automation Server Bindings show Unresolved - Schneider Electric Community Refer to the article for additional license troubleshooting options: Troubleshooting EBO license violation issues - Schneider Electric Community Contact your local support organization for further assistance.

Issue After adding an OPC UA server to EBO an export is done from the Device discovery tab to find the objects in the OPC UA server. When the OPC UA server database is big this can take up to a day to finish and sometimes the export is never finished. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause In EBO version 7 there is a workaround for this issue, it is possible to split the export up in smaller pieces and export objects from specified folders from the OPC UA server instead of all objects in the OPC UA server database.   Resolution Introduction The ‘Export configuration’ section in the settings dialog for discovered devices makes it possible to configure the export procedure. By setting the parameters in this section, you can specify the start node and the depth for each export file. This means that you can break down the export into many files instead of one large file containing everything. When importing the series of export files it is recommended to keep the same structure as the OPC UA server has, but it is not a requirement. You can import the export file anywhere under the device, but again, the recommendation is to keep the same structure as on the OPC UA server.   Selecting start node for browse The start node is specified by setting the ‘Start node namespace index’ (specified as an integer value) and the ‘Start node identifier’ (specified as a string value). The supported ‘Start node identifier’ types are string (s=), integer (i=), opaque (o=) and guid (g=). Both ‘Start node namespace index’ and ‘Start node identifier’ are found as properties on each OPC UA object. If these values are empty, faulty, equal to the object node or equal to the root node, the device object is included in the export file. Otherwise, it is omitted. Selecting the depth of browse The depth of an export file is specified as an integer value. It is recommended that this is set to a low number if the export time is expected to take a long time. Values 0, -1 or empty means that no depth limit is used. Getting started   A first step could be to export the root objects. The following configuration will handle that: The export file with this configuration will produce the following result when imported. Since the ‘Start node namespace index’ and the ‘Start node identifier’ are empty, the device object is included, and the import can be done on the ‘OPC UA Client Network’ object Only the root objects were included in the export file since the ‘Export depth’ was set to ‘1’. Next, we would like to populate the ‘BuildingAutomation’ object with 2 levels of child objects. For that we need the namespace index and the identifier of the ‘BuildingAutomation’ object found at the bottom of the property list:   These values are entered into the export configuration: The export file with this configuration will produce the following result when imported on the ‘BuildingAutomation’ object: Now we have a structure with all the root objects. All of them are empty except for BuildingAutomation that has two levels of child objects.   If you realize that the depth chosen was to low, you can simply set the ‘Export depth’ to a higher value and create a new export file from the same start node. The ‘Export configuration’ will now look like below: When importing the new export file we still use the ‘BuildingAutomation’ object as the start object, but since we already have two level of child nodes we need to select the merge option in the import dialog as in the picture below:    

Issue Encounter Queue Full Exception in context of "Error writing BACnet point" Product Line EcoStruxure Building Operation, TAC IA Series Environment I/A Series N4 Jace 8000 I/A Series N4 Jace 9000 Niagara Station running as SoftJace or 3rd Party Jace Cause If you notice queue overflow messages in the station dialog, it is essential to know which queue is overflowing. There are many different communications mechanisms in BACnet, and they use different queues. Resolution The canonical reference article is located on Niagara Community: BACnet Tuning Suggestions I have excerpted the following as a Rule of Thumb for the recommended starting configuration: Configure your tuning policies so that write-on-start is not enabled on some of the points - otherwise, the JACE may start with a to-do list that is larger than the queue can handle. The recommended configuration from Tridium is to set BACnet WriteWorker queues to 1.5 times the number of writable points. However, as initial configuration, Product Support has found these values to perform better than the defaults, so change the following values from 1000 to 3000. View the BacnetNetwork Property Sheet Expand Bacnet Comm Expand BACnet Comm -> Server -> Worker and Confirmed Worker Expand BACnet Comm -> Transport Change the various Queue Sizes from 1000 to 3000. Please consult PSS if a change to a value higher than 3000, as that has been found to adversely affect performance. 

Issue  EBO can have license violation bar without a known reason. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause License enforcement is the process of checking whether a software application has a valid license available to it at runtime. If you do not have enough licenses, a license violation occurs. This is accomplished by a license violation bar in WorkStation and WebStation.   Firstly, the license violation will be yellow, and it can be hidden for 8 hours. You can use Hide to hide the License Violation bar for 7 days. After 7 days, the Hide function is disabled. After 30 days, the bar turns red. Resolution Below information can be collected to help in troubleshooting: Refer to the document Part Number Summary and Hardware Software Matrix for software and features that need licenses and note that some feature licenses can be inherited from parent server to child servers. Get a screenshot of the License information page in the control panel, make sure to have all content in license information page are shown in the screenshots, ex child servers' status. It can tell which feature needs a license or which child server needs a license, refer to License Information Get the License Diagnostics, and entitlement certificates to make sure that required licenses are activated. Install the latest CP/hotfix to make sure that the system is not affected by one of the known license related defects, Make sure that all EBO servers have correct date and time, incorrect date and time can cause license violation, as explained in: Incorrect Automation Server date and time leads to license violation - Schneider Electric Community See this article if you do not see the License banner, but still get a License Violation alarm: License Violation Alarm Triggered Without License Violation Banner displayed - Schneider Electric Community  Check Known issues community. Get screenshots for the following: In ES, "System/LicenseManager/LicenseStatus/ConnectedASLicenseStatus" will show all connected Automation Servers. Show the license violation tab to know which Automation Server has violation as Automation Server may have violation although license information doesn't show that, ex. if the "Change Control" feature is enabled in an Automation server and ES doesn't have a license for it. For parent server and any server that has violation, search in folder "/System/LicenseManager/LicenseStatus". In the object name, write "*" and add columns License Violation, Checked Out License, Available Licenses, Required Licenses, and Installed Licenses. Export the results to XLSX. Check license Metadata for the parent server and any servers have license violation, search in folder "/System/LicenseManager/LicensingMetadata". In object name, write "*" and add columns FeatureVersion, FatureName, ProductVersion, EntitlmentID and Activation ID. Export the results to XLSX.   Get screenshot from FlexNet Publisher web interface, localhost:8888, concurrent tab. Make sure all features are shown in the screenshot, and the entire webpage can be saved instead of taking screenshots. If the server has just started, wait for some minutes till all data is collected.   Collect the logs and configuration files listed below: Log files located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\logs Configuration file located in C:\Program Files (x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server\conf Using EBO WorkStation, go to module, '/System/Modules/Trace/Loggers/nsp/nsp.csc/nsp.csc.licensemanager", set trace level to debug, reproduce the issue, if possible. Collect the server logs, then set the module trace level back to "information", refer to Collect logs from an Automation Server - Communities and Collect logs from the Enterprise Server and Enterprise Central - Communities.

Issue Unable to configure reverse proxy for SAML-based Single Sign-On (SSO) in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause Although EBO 7.0 has enhanced reverse proxy support, this does not include SAML SSO and EBO does not support reverse proxy configurations for SAML SSO.  This limitation prevents successful integration when a reverse proxy is used in the authentication flow. Resolution At this time, EcoStruxure Building Operation version 7.0 does not support reverse proxy configurations for SAML SSO. This is a known limitation. An enhancement request has been submitted to the Idea Forum to address this functionality in future releases.   To support this request, please visit the Idea Forum and click the thumbs-up icon on the SAML reverse proxy support idea to increase its visibility to the product management team.

Issue Questions regarding specifications of Central I/O Inputs and Outputs Product Line EcoStruxure Building Operation Environment SmartStruxure I/O Modules: AO-8, AO-8-H AO-V-8, AO-V-8-H DI-16 DO-FA-12, DO-FA-12-H DO-FC-8, DO-FC-8-H RTD-DI-16 UI-8-AO-4, UI-8-AO-4-H, UI-8/AO-4-2, UI-8/AO-4-H-2 UI-8-AO-V-4, UI-8-AO-V-4-H, I/O UI-8/AO-V-4-2, UI-8/AO-V-4-H-2 UI-8-DO-FC-4, UI-8-DO-FC-4-H, UI-8/DO-FC-4-2, UI-8/DO-FC-4-H-2 UI-16 Cause Different I/O modules have varying electrical specifications Resolution Universal Input Specifications Universal inputs can be configured as voltage, current, thermistor, resistance, digital or supervised inputs.   Voltage Input Specifications: Range: 0 to 10 VDC Resolution: 12-bit (UI-8 v2: 16-bit) Accuracy: ±(0.7mV + 0.2% of reading) Current Input Specifications: Range: 0 to 20 mA Resolution: 12-bit (UI-8 v2: 16-bit) Accuracy: ±(0.03 mA + 0.4% of reading) Resistance Input Specifications: 10 Ohm to 10 kOhm 10 kOhm to 60 kOhm Thermistor Input Specifications: Range: -50 to 150° C (-58 to 302° F) Supported Types: 10k Type I (Continuum) 10k Type II (I/NET) 10k Type III (Satchwell) 10k Type IV (FD) 1.8k (Xenta) 10k Linearized (Satchwell DRT) 10k Type V (FD w/ 11k shunt) 1k (Balco) 20k (Honeywell) 2.2k (Johnson Controls) Digital Output Specifications Form C Relay: Terminals: Common (C), Normally Open (NO), Normally Closed (NC) Minimum Pulse Width: 100 ms Isolation: 1500 VAC (coil to contact) Cycle Life: ≥100,000 cycles Contact Rating: 250 VAC, 30 VDC, 3 A Form A Relay: Terminals: Common (C), Normally Open (NO) Minimum Pulse Width: 100 ms Isolation: 1500 VAC Cycle Life: ≥100,000 cycles Contact Rating: 250 VAC, 30 VDC, 2 A LED Indicators: Polarity: Reflects actual output state (ON = active, OFF = inactive) Color: Green Analog Output Specifications Analog outputs can be configured as voltage or current. Voltage Output: Range: 0 to 10 VDC Resolution: 50 mV Accuracy: ±100 mV Terminals: Voltage (V), Return Minimum Load: Source 2 mA, Sink -1 mA Current Output: Range: 0 to 20 mA Resolution: 0.1 mA Accuracy: ±0.2 mA Terminals: Current (I), Return Max Load: ≤650 Ohms Supervised Input Specifications Supervised inputs detect sabotage via resistor monitoring. Detected Conditions: Open circuit, short circuit, contact open/closed Circuit: 5V, 1 or 2 resistors Configurations: Series only, parallel only, series + switch Resistor Range: 1k to 10k Ohms (must be equal values) Note: Resistor value must be defined in the system. RTD Input Specifications RTD-DI-16 specifications are extensive. Refer to the official datasheet: RTD-DI-16 Specification Sheet  

Issue You need to replace a faulty Xenta 301 controller. However, the existing unit is running System Version 1, and the network comprises approximately 12 Xenta controllers on a Menta-only network using the .nwc and .ndb configuration tools. Product Line TAC Vista Environment TAC Xenta 300 Cause New Xenta 301 controllers are shipped with System Version 3 by default. System Versions 1 and 3 are incompatible on the same network. Resolution To ensure compatibility, downgrade the new Xenta 301 controller to System Version 1.17 before installation. Steps to Downgrade and Replace: Download TAC Xenta 300 system program version 1.17 Use the Download Wizard as usual. Important: When downgrading from Version 3 to Version 1, do NOT retain the old application in the Download Wizard. Select "Clear Application" during the process. Manually Download the Menta Application and Network Configuration Use a serial cable to perform the manual download. Apply the appropriate TAC Menta versions for your network setup. Additional Notes Mixing different system versions on the same network can lead to unpredictable behavior and communication issues. Always verify the version compatibility before deploying new hardware.

Issue Users need a way to identify all Forced Variables without manually inspecting each point. The goal is to have a summary view—not via Reports Server—but directly accessible on the Automation Server (AS) or Enterprise Server (ES). Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no built-in summary page in versions 1.4.1 and older that lists all Forced Variables. This makes it time-consuming to locate which points are currently forced. Resolution You can locate Forced Variables using the system tree in the Workstation. Navigate to: ES/Servers/AS/System/Modules/RuntimeDBManager/VariableManager/Variables Ensure the isForced column is enabled to view which variables are forced. Additional Notes: This method provides a quick overview without needing to open each individual point. It is especially useful for troubleshooting and auditing system behavior.

Issue What does it mean when a TAC controller is said to have a Universal Input? Product Line TAC Vista Environment Xenta Programmable Controllers Xenta I/O modules Cause The term “Universal” is commonly interpreted to mean compatibility with all types of inputs. However, this definition does not accurately apply to TAC Xenta controllers. Resolution In the context of TAC Xenta controllers, the term “Universal Input” refers to compatibility with multiple types of input signals, but not necessarily all types.   Key clarification: It is essential for project planners and system designers to consult the specific device’s datasheet to understand the exact definition of “Universal” as it applies to the particular TAC Xenta model in use. This ensures proper configuration and avoids misinterpretation during system design and implementation.

Issue After the "Windows is shutting down" message, Windows displays a non-specific memory error: lmadmin.exe - Application Error The instruction at "0x00000000" referenced memory at "0x000000". The memory could not be read. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Cause This issue is caused by Flexera Software, the licensing software used within Building Operation. Flexera does not support Windows XP, which leads to this error during system shutdown. This is a known limitation and will not be addressed in future updates. Resolution There are no known operational impacts associated with this error. It only occurs during shutdown of a Windows XP machine. Upgrading the operating system to a supported version will eliminate this error. Additional Notes This issue is cosmetic and does not affect system performance or licensing functionality. Users are encouraged to migrate away from Windows XP due to broader security and compatibility concerns.

Issue How can the firmware version of Security Expert Smart Card Readers be determined. Product Line EcoStruxure Security Expert Environment Security Expert Smart Card Readers Cause It is not possible to easily identify the firmware which a reader has been shipped with. Serial Numbers are not sequential and cannot be used as general guide. Resolution There are two supported methods to determine the firmware version of a Security Expert Smart Card Reader: 1. Via Product Support If you need to identify the original firmware version shipped with a reader: Raise a case with Schneider Electric Product Support. Include the reader’s serial number in your request. Product Support will contact Manufacturing to obtain confirmation of the firmware version originally installed on the reader. 2. Via Controller Web Interface (Requires Reader Expander Firmware 1.12.605 or later, Security Expert Controller Firmware 2.08.1498 or later, SP-C-WEB Firmware 4.00.2261 or later) From firmware version 1.12.605 and above, the Security Expert Controller’s web interface displays the serial numbers and firmware versions of connected card readers via RS-485 or OSDP. Steps to View Firmware Version: Log in to the Controller Web Interface. Navigate to Application Software. Open the Module dropdown to view connected readers. Important Notes: Wiegand-connected readers are not displayed in the web interface. If the Reader Expander address has changed, a power cycle is required for the readers to reappear in the interface.  

  Issue Understanding the size of individual tables within the Security Expert databases is essential for effective database management. This insight helps optimize system performance and supports archiving strategies. Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Microsoft SQL Server Cause Managing SQL database size is critical to maintaining system performance. Identifying which tables consume the most space provides actionable data for optimization and archiving. Resolution To determine table sizes in the Security Expert and Security Expert Events databases, follow these steps using SQL Server Management Studio (SSMS): Open SSMS Right-click on the relevant database (e.g., Security Expert or Security Expert Events). Navigate to: Reports > Standard Reports > Disk Usage by Table Review the report to identify tables with the largest data footprint. Examples: Security Expert DB Security Expert Events DB Exporting the Report You can print or export the report for documentation or analysis: Print Export to Excel, PDF or Word Right-click on the data results and select Export Note: The “Disk Usage by Table” report is available in SQL Server 2008 and later.

Issue Sites using Report Server need to upgrade to EcoStruxure Building Operation (EBO) 2022 or higher, where WebReports/Report Server is no longer supported. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Report Server Building Operation Timescale Database Cause WebReports/Report Server is not supported in EBO 2022 (version 4.0) or higher. Resolution To address this, Schneider Electric provides a Data Migration Assistant (DMA) tool that: Reads data from WebReports 3.x Writes data to External Log Storage Download the DMA Tool External Log Storage Overview Stores historical data from EcoStruxure BMS Storage capacity is limited only by your hardware Historical data is displayed in WorkStation and WebStation (event and trend views) Any server can be configured to write data to TimescaleDB   Any server in the system can be configured to write historical data to the TimescaleDB database. Licensing Requirements External Log Storage requires a license Refer to: Software and Features that Require Licenses Part Number Summary and Hardware Software Matrix Hardware & Software Requirements Ensure compatibility with: TimescaleDB PostgreSQL Recommended specs for large systems (e.g., 100 BMS servers): High-performance SSD Minimum 64 GB RAM Additional CPU capacity Refer to: IT System Planning Guide Merging Log Data External Log Storage reduces extended trend logs on BMS servers You can merge extended trend logs into source logs in External Log Storage See: Merging of Trend Log Data Enhanced Reporting (XLSX Templates) EBO servers (v3.2 or higher) support native reporting with: Text and XLSX formats Advanced XLSX features: formulas, conditional formatting, charts, sparklines Historical data pulled from External Log Storage (PostgreSQL/TimescaleDB) Refer to: Examples for Native EBO Notification Reports

Issue How are BACnet controllers established as being Online / Offline? Product Line EcoStruxure Building Operation Environment BACnet Cause BACnet controllers may appear offline in the system, even though they can still be communicated with. This raises questions about how their online/offline status is determined. Resolution The online/offline status of BACnet devices is managed by the BACnet device manager plugin, which processes BACnet I-Am messages to maintain a device table.   The following rules and mechanisms are used to determine the status of BACnet controllers: Device Discovery and Initial Probing When a new device is discovered, an entry is added to the device table. The system probes the new entry up to four times at 5-second intervals. If the device does not respond within this time, it is declared offline. Offline Detection via MSTP Driver Building Operation uses the MSTP dev driver to monitor token passing. If three consecutive tokens are missed, the device is marked as offline. Probing Offline Devices Once a device is offline, the system sends a Who-Is message every 60 seconds. Offline devices are probed indefinitely at 60-second intervals until they respond. Online devices are never probed. Status Transition A device is considered online once it responds to a request. If it fails to respond, its status is updated to offline, and probing resumes.

Issue How to get data from Rayleigh Instruments RI-78-80-C kWh power meters Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (ASP/ASB) Modbus RTU Interface Cause The RI-78-80-C meter provides a single 48-bit Modbus RTU word representing energy in kWh. This word spans three 16-bit registers (registers 0, 1, and 2). The meter: Only responds to a valid 48-bit read Does not return exceptions for invalid or partial register reads Resolution To successfully read the 48-bit value: Step-by-Step Instructions Create a Modbus Group Set an appropriate polling interval. Add Registers Add three 16-bit unsigned registers to the group: ModReg0 (Register 0) ModReg1 (Register 1) ModReg2 (Register 2) Create an Analog Value Example name: kWReading Script Program Use the following calculation: kWReading = ((256 * 256 * ModReg0) + (256 * ModReg1) + ModReg2) / 100 ​ This formula accounts for the fact that each register only uses half of its 16-bit range (values from 0 to 255). The register values represent 1/100 of a kWh, so a scaling factor of /100 is applied. Bind Points Bind the Modbus registers and analog value to the script program. Example Calculation If: ModReg0 = 3 ModReg1 = 167 ModReg2 = 59 Then: kWReading = ((3 × 256 × 256) + (167 × 256) + 59) / 100 = 239419 / 100 = 2394.19 kWh ​   Additional Notes The device may appear online in EcoStruxure even if it’s not responding correctly. This is because the online poll interval mechanism expects a response from a 16-bit register. Since the RI-78-80-C doesn’t respond to invalid reads, it may falsely appear online. To avoid this, set the online poll interval mechanism to “Inhibit”. Compatibility Warning: This device may not function correctly in v2.0 and v3.0 due to changes in offline detection. This issue is resolved in v3.1. Resources Example Modbus Objects and Script RI-78-80-C Exports.zip Numeric Output kWReading   Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100

Issue The MPM controller does not adjust the clock automatically when Daylight Saving Time (DST) period occurs. Product Line EcoStruxure Building Expert Environment SmartStruxureLite Multi-Purpose Manage Cause DST settings in the MPM are configured for North America. Canada and United States: Daylight saving time begins on the second Sunday of March and ends on the first Sunday of November Europe: Daylight saving time begins on the last Sunday of March and ends on the last Sunday of October Resolution In Firmware 2.15, DST properties can be configured in the Controller Configuration Object (CFG1) and/or configuration page. DST start and end configuration on month, week, weekday, hour and offset can be set. If using a firmware version older than 2.15, a script can be used to correct the issue. The script can be found here: Daylight_Saving_Time_DSC.lua

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 Installing and Configuring Email Service Accounts in Niagara G3 Environment Niagara G3 Cause The need for a quick reference guide Resolution The following document can be found at Niagara-Central.com as well.

Issue How to configure a LON router in Niagara R2. Environment Niagara R2 LON Cause Troubleshooting Resolution Review / download documentation here.