Building Automation Knowledge Base

Issue Need a description of Zigbee error codes Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause No list of error codes available Resolution Here is a list of all possible error codes Error Code (HEX) Error Code (Decimal) Error Description   -2 Device offline (communication initialization after changing Ext. Network ID in ZVC)   -1 Device not bound 0x00 0 Success. Operation was successful. 0x01 1 Failure. Operation was not successful. 0x02 - 0x7d 2 - 125 Reserved by Ember 0x7e 126 Not authorized. The sender of the command does not have authorization to carry out this command. 0x7f 127 A reserved field/subfield/bit contains a nonzero value. 0x80 128 Malformed command. The command appears to contain the wrong fields or invalid field. 0x81 129 Unsupported cluster command. The specified cluster command is not supported on the device. Command not carried out. 0x82 130 Unsupported general command. The specified general command is not supported on the device. 0x83 131 Unsupported manufacturer cluster command. A manufacturer specific unicast, cluster specific command was received with an unknown manufacturer code, or manufacturer code was recognized but command is not supported. 0x84 132 Unsupported manufacturer general command. A manufacturer specific unicast, ZCL command was received with an unknown manufacturer code, or the manufacturer code was recognized but the command is not supported. 0x85 133 Invalid field. At least one field of the command contains an incorrect value, according to the specification. 0x86 134 Unsupported attribute. The specified attribute does not exist on the device. ( Zigbee Module not fully compatible with Room controller and FW of MPM) 0x87 135 Invalid value. Out of range error, or set to a reserved value. 0x88 136 Read only. Attempt to write a read only attribute. 0x89 137 Insufficient space. An operation failed due to an insufficient amount of free space available. 0x8a 138 Duplicate exists. An attempt to create an entry in a table failed due to a duplicate entry already being present in the table. 0x8b 139 Not found. The requested information could not be found. 0x8c 140 Unreportable attribute. Periodic reports cannot be issued for this attribute. 0x8d 141 Invalid data type. The data type given for an attribute is incorrect. Command not carried out. 0x8e 142 Invalid selector. The selector for an attribute is incorrect. 0x8f 143 Write only. A request has been made to read an attribute that the requester is not authorized to read. No action taken. 0x90 144 Inconsistent startup state. Setting the requested values would put the device in an inconsistent state on startup. No action taken. 0x91 145 Defined out of band. An attempt has been made to write an attribute that is present but is defined using an out-of-band method and not over the air. 0x92 - 0xbf 146 - 191 Reserved by Ember 0xc0 192 Hardware failure. An operation was unsuccessful due to a hardware failure. 0xc1 193 Software failure. An operation was unsuccessful due to a software failure. 0xc2 194 Calibration error. An error occurred during calibration. 0xc3 - 0xff 195 - 255 Reserved by Ember   256 Device offline   257 Device profile does not match selected device widget in Building Expert

Issue During Energy Expert installation an error is shown, and the floating license manager is never installed Product Line EcoStruxure Building Operation, Other Environment EcoStruxure Energy Expert (formerly Power Manager) Installation Cause "Error 1722" occurs due to a conflict between the version of Java installed on the PC and the version included in the EE installation package Resolution Uninstall all versions of Java from the PC Install the JavaRuntime manually from the install media "..\setup\SetupSupport\Licensing\JavaRuntime\x86\jre1.7.0_02.msi" Run the complete installation again

Issue After upgrading from EcoStruxure Energy Expert (formerly Power Manager) from version 1.0 to 1.x or newer, the licensing no longer works. Product Line EcoStruxure Building Operation EcoStruxure Energy Expert Environment Energy Expert (formerly Power Manager) License Administrator Power Monitoring Expert Cause There can be some confusion on what licenses are required to run Energy Expert. There are also differences between version 1.0 and 1.x or newer licensing.  Resolution EcoStruxure Energy Expert License In order to use Energy Expert, an Energy Expert license is needed to be purchased before the previous 90-day trail license expires.  The EcoStruxure temporary license (evaluation) is only for EcoStruxure Building Operation software and does not include Energy Expert   It is important to remember that EcoStruxure Building Operation licenses are needed to work along side Energy Expert (e.g. Workstation, Enterprise Server, etc). The EcoStruxure Building Operation licenses need to be activated separately.  How to activate, release and/or transfer a license in EcoStruxure.   Energy Expert Version 2 and 3 Licensing and Upgrading If upgrading from a previous Power Manager 1.x site to Energy Expert 2.x or 3.x a new license(s) will be required. In order to obtain your new license(s), please follow the procedure found in TPA-EBO-19-0001.00 - EcoStruxure Energy Expert v2.0 License Upgrade. (Full support ends 2022 and limited support ends 2024) Energy Expert Part numbers and Licensing The part numbers for version 1.x or newer are listed below. PSWPMNCZZSPEZZ -  Base Energy Expert license PSWDENCZZNPEZZ -  PME license entry range PSWDMNCZZNPEZZ - PME license mid range  PSWSANCZZSPEZZ -  Standard PME. license For a full list of both current date and obsolete part numbers please download the following spreadsheet https://ecoxpert.se.com/pme-digital-power-launch)   Activating a License Full guidance for activation of your licenses can be found on Page 55 of the Energy Expert 3.0 Solution Guide The Energy Expert 3.0 installer and documentation, can also be found here EE 3.0

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Need to replace and upgrade AS (Classic) to AS-P-NL. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (AS) Building Operation Automation Server Premium non-LON (AS-P-NL) Cause From EBO v3.2 the AS-P-NL is available, there is a need to upgrade an AS (Classic) but the AS is only supported up to v3.1. Resolution A lower version of EBO can be installed into the AS-P-NL e.g. from v2.01, but this must only be for the purpose of upgrading the database.   Therefore the upgrade path can be as this example shows, there is a requirement to upgrade an AS from v1.6: Upgrade AS v1.6 to v3.1.x) . Backup the AS. Install v3.1.x) on AS-P-NL ( x needs to be same as in step 1). Note: Installing 3.1.x on an AS-P_NL is only for the purposes of upgrading the database, the following steps 4. and 5. must be completed . Restore backup on AS-P-NL. Upgrade to v3.2 or later.   For details regarding upgrade paths see article - Upgrade path from version 1.0 to current version 

Issue In this specific instance the site was upgraded to Continuum v1.94 and the Cyberstation OS upgraded to Windows 7 64 bit, fresh install. Local Administrator account was logged on to perform Database Initialization which succeeded and Continuum was able to start-up and connect to the SQL Server. Restarting and logging in with another windows user with administrative privileges results in being unable to connect to the database. Logging out and then in as Administrator and re-initializing the Workstation into the Database re-establishes the connection and Continuum is able to be run again. This fails again when another user is logged on. Product Line Andover Continuum Environment Andover Continuum Cyberstation Windows 7 64-bit Cause Windows administrative privileges are required to initialize and make a connection to the database. Resolution Run Database Initialization as an Administrator and re-initialize the Workstation into the Database. Shut down all Cyberstations. Right-click Database Initialization and select "Run as... Administrator".  In Win7 you may need to "Shift-right-click" and select 'Run as a different user...' Select Workstation, confirm details, input password and select OK.

Issue Continuum Graphics (Pinpoint): How do point updates take place and how can I change the update interval and polling speed? Is it different for BACnet points? Product Line Andover Continuum Environment Pinpoint Graphics Bacnet Cause How do point updates take place and how can I change the update interval and polling speed? Resolution In Cyberstation V1.71 and greater, the graphics polling engine was significantly changed. Prior to this change, the Pinpoint application would poll the points within its graphic file directly. If several graphics were open, each graphic would perform its own polling, This engine also applied to Web.client. Each control on the graphic had a separate selection where you could set the polling rate on a per-point basis on the miscellaneous tab of each control. This was the only method to adjust the point polling interval. The main reason for the graphic engine change was for Web.Client graphics. Slow networks, multiple browsers accessing the same graphics, and slow browser machines could make Web.Client graphics unacceptably slow.   The current method to get data into graphics involves a separate graphics polling engine per workstation. When one or more graphics are opened on a workstation or a Web.Client IIS server, the graphics register the points into the polling engine on that workstation. The polling engine then begins updating the values and sends the data to the Pinpoint/web.pinpoint clients. After initially sending all the data values to the graphic, it then only sends the data that has changed since the last update in an XML document format. If several graphics are requesting the same point values, the data is only polled once for all the Pinpoint clients on that workstation or Web.Client. Efficiency was also achieved by registering the points in the polling engine which allowed the polling engine to decrease the number of data requests by 50% to retrieve the same data.   There are now additional settings to adjust the polling rates in a graphic. #11 General preferences "Time interval between requests" This is a global setting and affects all workstations. By default, all polled points which are in the polling queue are sequentially updated at a continuous rate with a default delay between requests of 30 milliseconds. It is often recommended to set this to 100ms (Additional considerations below  under Multiple Cyberstation graphics performance)   General Preferences are accessed by Right Clicking on the Continuum icon in the Windows system tray and selecting General Preferences     There are also a pair of settings in the workstation preferences: #24 Pinpoint active polling rate #25 Pinpoint inactive polling rate These settings are for each workstation individually and do not affect the polling rates of the polling engine, but merely determine how often the graphic requests data updates from the polling engine based on whether a panel is or is not the active window. Typically these settings can be left at their defaults R&D has indicated that #24 is not used as Pinpoint always uses the inactive polling rate whether the window is active or not. Therefore, adjust #25 "Pinpoint inactive polling rate".  It is recommended to set this to keep this at the default of 250ms.   Cyberstation Preferences are accessed by Right Clicking on one of the Cyberstations while logged into Continuum and selecting Edit   Multiple Cyberstation graphics performance Several workstations may be configured to display graphics that are pointing to the same controllers and the controllers being polled may be on a large Infinet or MSTP network. In this case, the controllers could be overwhelmed by simultaneous data requests from the different workstations, slowing down controller scans, the whole field bus and overall system performance. R&D indicates that when multiple Cyberstation Graphics are used there is some randomness as to how the polling requests are accomplished. If graphic or system performance is an issue, it is suggested that another 30 Milliseconds is added to the general preferences "Time interval between requests" (#11) and then measure system performance and add additional time if needed up to 500ms.   When using this setting it is necessary to consider how many Cybersations would be running simultaneous graphics. For example:4 workstations polling graphics simultaneously with "x" number of points in it for 1 Netcontroller could have about 20 requests per second (determined via Wireshark capture at the NC NIC) 30 ms per X 4 Cyber =120ms added In this case, the recommendation was to set the "Time interval between requests" value to 250ms for performance   Note: Individual millisecond settings in each point do not effect polling for the point. They are not used.   BACnet points Bacnet points can be managed differently. Continuum BACnet points can either be polled the same way that Standard continuum points are polled or by using a COV. Standard polling is done by using the point objects from the "Infinity" side of the object tree. If you want to use COV for the point updates which is much more efficient, you should use the "BACnet Points" in the graphic, from the BACnet side of the object tree. The polling engine will then subscribe for COV updates to the respective controllers. When the graphic is closed the polling engine will unsubscribe the COVs. Third-Party BACnet controllers have an additional method to adjust the poll frequency. If the third-party BACnet controller supports COV subscriptions, Cyberstation will subscribe to these points as COV's like the Continuum BACnet controllers however, if the devices do not support COV's their points will be polled. Since many third-party BACnet controllers cannot withstand frequent data requests, there are two additional settings on the BACnet device object editor. The settings are on the Details tab on third-party BACnet controllers only. 1. Max # of Async requests The max # Async requests specify how many requests we should send before we get a reply to the data request, or how many requests can I queue. Typically this should be set to 1. 2. Request interval in ms  The request interval setting will depend on the device. Does it use Ethernet or MSTP network architecture? Are you running "Enhanced MSTP"? How many third-party devices are on the mstp network that cannot run enhanced MSTP? Typically it would be safe to set this in the 1000 to 5000 ms range based on desired data update rates and the controller's capability to handle the polling.

Issue Existing SIM-MTECH communicates with a McQuay OPM (Open Protocol Master) and McQuay controllers under it. Can an AS-P replace the SIM-MTECH? Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series NW8000 GCM/SIM-MTECH (McQuay OPM) Building Operation Automation Server Premium Cause Replacing obsolete NW8000 GCM/SIM-MTECH with currently supported EBO AS-P Resolution The GCM/SIM-MTECH data base can be converted as a normal GCM through the Transition Tool on the Schenider Electric Exchange TAC I/A Series Transition Portal.  The blocks specifically associated with the OPM integration will not be converted. A third-party hardware device can be used that will allow the AS-P to communicate through the OPM to the McQuay controllers. This will be accomplished by BACNet or Modbus protocol to the AS-P depending on the third parties device selected.  Refer to these 2 documents and websites.  NOTE: These are third party devices and have not been tested or approved by Schneider Electric Product Support. FS-8700-80 McQuay MicroTech Open Protocol Mcquay Gateways

Issue Can the Advantech touch screen be used as a Sigma server? Environment Sigma WinCE Advantech Touch screen Panel mounted Cause System has been installed without a Sigma server. Resolution The Advantech touch screen, or any other WinCE device can only be used for general display functions, low level editing, contingency logging review and time updates, it does not have the functionality of a Sigma server. To review the latest Release note, please click HERE. To review the WinCE User guide, please click HERE.

Issue Belden Cables for LonWorks Networks Approved LonWorks cables Product Line EcoStruxure Building Operation,Satchwell, MicroNet,TAC IA Series,TAC Vista Environment LonWorks networks TP/FT-10, TP /XF-78 and TP/FT-1250 Cause The Echelon document 'Junction Box and Wiring Guideline for Twisted Pair LonWorks Networks' indicates Belden 8471 and Belden 85102 as the recommended cables from Belden for LonWorks networks. These may not be available from the local Belden office or the Belden distributor. Resolution Refer to Belden Technical Bulletin TB 102E 'Belden Cables for LonWorks Networks' for a list of Belden cables suitable for LonWorks communications. Take note of the difference in cable drop length and total cable bus length for the various cable models listed.

Issue Is it possible when starting Internet Explorer: To log on automatically. To start in Full Screen mode. To show a TGML graphic (without system tree) and without entering a user name and password by a shortcut. Is it possible to hide the 2 toolbars as described below? Product Line EcoStruxure Building Operation Environment Building Operation WebStation Kiosk Mode Cause For some applications such as Kiosk screens, these features are needed Resolution Automatic logon This can be accomplished either by using the "Remember me" checkbox on the logon screen, or by using the guest logon feature. To make WebStation bypass the logon screen, create a user with a username of GUEST and a password of GUEST, give this user limited permissions. For 1.7 and later, the password for the GUEST account when used for WebStation automatic logon, is not compatible with the default password policies. Automatic logon will only happen if the GUEST account password is exactly "GUEST". If policies are not changed the automatic logon will stop working after 90 days. Full Screen mode To make Internet Explorer go directly to full screen mode, you can use the "kiosk mode" switch. Create a shortcut with the command  iexplore.exe -k [insert your URL here] Display TGML Graphic without toolbars Open the graphic you require, using the "Open in a new window" right-click command. Copy the URL and create a shortcut with it. When you open this URL the user is taken directly to the graphic, without toolbars or menus.

Issue Save time in the field by using the different functions Newron NL220 has to offer. This article contains some tips, tricks, suggestions and ideas. Product Line TAC IA Series, TAC Vista Environment NL220 Cause By not using all of the different tools within NL220 it can take much longer to complete a checkout of a database or resolve a problem. There are a number of shortcuts and hotkeys that can save a substantial amount of time. Some examples include database searches, browser window functions, filters, attaching documents, and meanings behind network menu options. Any addition questions or information can be found by contacting Newron here. Resolution Other Helpful NL220 Articles and PDFs NL220 Manual - Click here Starting a NL220 database - Click here Echelon LonMaker and Newron NL220 on 64-bit operating systems Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220   Searching the Database There are multiple ways to perform a search in the NL220 database depending on what is trying to be found. At the top of the NL220 window there is a search bar as seen above. The buttons found on this toolbar are defined below. When performing a search there are four different ways that a name can be searched. Using an asterisk after the name means that NL220 will search for anything that begins with those characters. Example: Name*   Using an asterisk before the name means that NL220 will search for anything that ends with those characters. Example: *Name   Using an asterisk before and after the name means that NL220 will search anything with those characters somewhere in the name. Example: *Name*   If no asterisks are used then NL220 will search for an exact match of those characters. Example: Name   General Toolbar The general toolbar at the top of the NL220 window has many useful shortcuts and features. Descriptions of some of these tools can be found below.    To use the automatic browser feature , the desired network variables must first be selected in the device templates. Select the template tab at the bottom of the database tree window.   Double click on the template that is desired for automatic browse. This example is using the 102-AX template.   Select the NVs tab in the device template settings window. Check the box in the browse column next to all network variables to include in automatic browse.   Click on the Subsystem tab  at the bottom of the database tree window.   Select the automatic browse button and click on a controller that is using the template that was modified. It will automatically open up the browse window with only those network variables.   Filter Toolbar The filter toolbar seen above is found at the top of the tree window. This toolbar contains the ability to look at nodes in a specific state like commissioned or uncommissioned, only display specific types of network variables, or even filter nodes and variables by name.    Network Functions Right clicking on objects in the tree window gives the pop up menu that contains the Network menu.  The functions of these icons are defined in the chart below.       Network Variables If changes have been made to the XIF file of a controller, the change needs to be applied to the network variables of the application devices that use the template. Click on the Templates tab at the bottom of the tree window. Right click on the template that needs to updated and select "Rename variables of all application devices" A prompt will open that says "Do you want to rename all network variables of the application devices with the template name?". By clicking yes, this will rename all of the network variables of the devices that reference this template to match the names found in the template. Note: Once this has been completed double check the SNVT connections that have been created already. After the rename, it may change the SNVT order if a SNVT was renamed or removed  from the programming. This will cause connections to be binding the wrong variables together.   Creating a New Device Template If adding a new device to the database, a new device template may need to be created. See Adding a Xenta Programmable Controller to an NL220 System for instruction on how to add a Xenta programmable controller to a NL220 system. Click on the Templates tab at the bottom of the tree window. Right click anywhere in the Templates pane and click on "New device template..." In the New device template box, enter the name of the new template and browse the XIF file into the "Description file" box.    

Issue How to put in multiple email addresses for emailing from Email Notification Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Site with at least one ES or AS Cause A good example of when multiple email addresses are required for alarm notifications is a facilities staff. You may need critical alarms to go to several people at once to make sure they are handled in a timely fashion. Note: Consider configuring Building Operation to email a distribution list as opposed to several email addresses. That way the IT department can handle making changes without having to access the building control system. Resolution in the email address field of the Email Notification, addresses should be separated with only a semicolon. No space is permitted between the addresses. Note: This will not work from Webstation, only from Workstation. Example: user1@gmail.com;user2@gmail.com;user3@gmail.com

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 Continuum installer throws a Error 1904, dll failed to register error during the installation process. Environment Continuum Error 1904 Failed to Write to Registry. Cause Virus protection is preventing the Continuum install from writing a .dll to the registry. Resolution Uninstall Continuum completely. Reinstall Continuum with all malware protection software disabled and using a Local Administrator user account. Check the compatibility matrix to ensure that the Windows OS you are using is compatible with the Cyberstation version

Issue SE8000 Best Practices Product Line Field Devices, EcoStruxure Building Expert Environment SE8000 Cause Best Practices for commissioning SE8000 room controllers Resolution The following information has been contributed by a field engineer and their experience to assist others in commissioning the SE8000 device. It brings together or provides leads to various articles that can be found on the Download Center. SE8K Programming Tutorial v1.1

Issue How do I read unsigned 8-bit (byte) values from a Modbus holding register and represent the analog value in Building Operation? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In this case, the Modbus holding register is a 16-bit unsigned value that is used by the Modbus device to represent two individual 8-bit values.  The 16-bit unsigned value is an integer with a range of 0 to 65,535 and needs to be converted into two analog values. Resolution Use a Building Operation Modbus Analog Input Point for each value required.  Each object will be configured to read the same Modbus register address with the bitmask value applied before evaluating the value to determine the output. For example: Read Modbus holding register 40001 which is a 16-bit unsigned value and decode as two analog values. Under the Modbus device object - create a Modbus Register Group Under the Modbus Register Group - create two Modbus Analog Input Points Configure each point as follows: Modbus Analog Input Point 40001 (AI-HighByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 8 through 15 Modbus Digital Input Point 40001 (AI-LowByte) Register number 1 Register type 16-bit unsigned Read function code 03 Bitmask - enable all bits 0 through 7 Additional information can be found in the Building Operation Technical Reference Guide - Modbus Point Configuration (Bitmask) or WebHelp at Point and Value Configuration

Issue A license violation alarm is shown in the alarm viewer even though the system has all licenses necessary. The alarm returns to normal without any action from the operator. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The Enterprise Server / Central contacts the License Server installed on the computer to determine what licenses are available. The License Server will then contact the "Trusted Storage" on the computer which is created when activating the licenses and ask how many licenses are available. The issue comes when the "Trusted Storage" creates some metadata once a day.  The metadata is a file created showing which licenses are used at that moment.  This is not currently used but could be by a third-party client who is interested in the license information for the system.  When the "Trusted Storage" creates the metadata it will be busy and not answer the License Server.  This is when the license violation alarm will be activated.  The alarm will return to normal after the "Trusted Storage" has finished creating the metadata. Resolution An investigation is ongoing. This issue has been fixed in EBO 2022. Please refer to License Violation Alarm 

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 Modbus slaves are programmed according to device documentation, but either the wrong values are returned or error codes complaining about invalid address. Product Line TAC Vista Environment Xenta 913 Xenta 731 Xenta 511:B Cause The XBuilder Device Editor has two ways to address modbus registers. The improper usage of these methods can cause communication problems because the wrong register is polled. 1. Fixed Address Blocks This method combines the function code and register address to produce a single number format that serves multiple function codes. This is sometimes referred to as numerical notation. A poll of a holding register uses function 03 and an address from 00 00 to FF FF. When using Fixed Address Blocks a message of function code 03 and address 00 00 is displayed as 40001. Due to this combination it is limited to 9,999 addresses per function code. Type Function Code  Address  Coil Status  01  00001-9999  Input Status  02  10001-19999  Holding Register  03  40001-49999  Input Register  04  30001-39999 When the device editor is using Fixed Address Blocks then the numerical number is parsed from the Register in the following way. Register Function Code Address 1-9999 01 Register - 1 10001-19999 02 Register - 10001 30001-39999 04 Register - 30001 40001-49999 03 Register - 40001 2. Function Code Tables (Discrete Input, Coil, Input Register, Holding Register) This addressing format is closer to the actual protocol and keeps the function code separate from the register address. It also provides full use of the addresses from 0 to 65535. Table Function Code Discrete Input 02 Coil 01 Input Register 04 Holding Register 03   If the wrong format is used it can result in failure to communicate because the wrong register is used. For example polling register address 40010 on function code 03 when it should have been address 9 on function code 03. Resolution The documentation of the product being interfaced with is the best guide on the register addressing and the format they use. If the documentation does not directly specify the information then use the follow hints to guide your selection: Hints to use Function Code Tables Addresses that fall on zero (0, 10000, 30000, or 40001) Non binary data that is less then 30001 or greater then 40001. Devices states it is J-Bus. Register address is displayed in Hexadecimal format. Hints to use Fixed Address Blocks Any address register above 30000 or 40000, unless it claims to be a JBus device. If it is still unclear which addressing format to use then experiment with read only data and value pages in the Xenta Servers. Pick a point that you can easily confirm the value, add both address formats to a device template, and then confirm the proper format with a values page. Once you know how to read one point the rest of the product documentation is easier to work with.

Issue What is the process to replace a CX9400 with a CX9680 NC2? Product Line Andover Continuum Environment Upgrading a CX9200, CX9400 Eclipse, CX9900, CX9940 to a NCII Netcontroller. CMX9924. Model Number, Type change. Cause Where can I get the process to upgrade my obsolete CX controller. Resolution Cyberstation V1.74 SP2 or above is required to support the upgrading process of a CX9200, CX9900 and CX9940 up to a Netcontroller 2. The upgrade process for this is detailed in Appendix B or the NetController II Operating and Technical Reference Guide. For the CX9400 Eclipse controller they require a minimum of V1.91 to support the upgrade. For the older versions of Cyberstation that do not support direct upgrading of a model number, you will need to bring the Netcontroller II on line as a new controller, then in offline editing copy /paste (or Drag /Drop) all objects over to the Netcontroller II. Then go online and fully reload the Netcontroller II and any connected Infinet controllers. The old controller can then be deleted from the system. The objects could also be copied over using edited ASCII dump files if you prefer that method, but either way you may still have to re-animate your Pinpoint graphics unless you upgrade to a version that supports the Netcontroller II replacement. NOTE ACC-LON RS-485 and ACC-LON FTT-10A protocol options A CX9900 may be labeled CPU-8M and a CX9940 labeled CPU-4M. Later CX99 models may have FT added, eg. CPU-8M-FT When replacing a CX9900 or CX9940 it is vital to know if it requires an RS485 or FTT10 IOU module port (if this port is being used) as this CANNOT be modified on site. See article titled No response from I/O module when learning in an IOU This process cannot be used to upgrade the CMX9924 controllers.  The available range of Netcontroller II controllers available has recently been reduced, see PA-00535 "Andover Continuum Offer Optimization"