Issue Security Expert and Security Expert Data Sync Service are running and operational. After a while, the Data Sync Service stops synchronizing. Reviewing the Data Sync Service log file indicates that the connection was lost and that the operator username or password are incorrect. [WARN ] [0 ] - Failed to get Operator where ID = 6. Error Code: 8 (Connection lost/not logged on) [ERROR] [0 ] - Incorrect username or password, or the operator does not have access. Error Code: 0 (Error). Restarting the entire system or the Security Expert Data Service resolves the problem. Product Line Security Expert Environment Multiple Security Expert Clients Security Expert Data Sync Service Cause The number of concurrent clients has exceeded the licensed limit.   The Data Sync Service will make a connection each time it synchronizes and then close that connection when finished. If there are no client licenses available for it to use when attempting to connect then it will fail and present the following events in the log file. [INFO ] [0 ] - Verifying product license information... [WARN ] [0 ] - Failed to get Operator where ID = 6. Error Code: 8 (Connection lost/not logged on) [ERROR] [0 ] - Incorrect username or password, or the operator does not have access. Error Code: 0 (Error). [INFO ] [0 ] - Next sync will begin at 24/07/2019 9:42:59 AM Each Security Expert Client connection will take up a client license. If the SSN is enabled for three concurrent client connections this will allow for two Security Expert Clients and one Data Sync Service. Resolution Purchase more client licenses (SX-CLNT) for the sites SSN. Ensure that no more than [one less than the maximum concurrent clients number] Security Expert Clients are running when the Data Sync Service is also running.

Issue Using valid credentials at the Web Client log in screen results in a log in attempt that fails without an error being shown then being dumped back to the log in screen. "Operator Logon Failed. Too many connections" error messages are seen when reviewing the Security Expert event logs. These login failure events are shown in the Applications and Services Logs > Schneider Electric Security Expert event log by looking at the Security Expert Soap Service events. SOAPService Log in Failure The specific operators that are consuming the licenses can be seen by reviewing the Windows Logs > Windows Application event log​ for Security Expert Data Service events showing New Operator Logins. Operator Log in The Remove Operator by Disconnect events will show when the operators were logged off. Operator Log off Product Line Security Expert Environment Security Expert Server Security Expert Web Client Security Expert SOAP Service Cause There are no available client connections.   When the SOAP service attempts to connect to Security Expert it performs an Operator login to the Data Service, pulls/pushes the information it needs, and then closes the connection. This means that if you are using all your concurrent operator logins at any given time with Thick Client connections, SOAP will not be allowed to log in, and any services requiring the SOAP connection will also not work.   SOAP will only use one concurrent connection even if it has multiple services connected to it, so you would not need multiple connection licenses if you had Web Client, Data Sync, and EWS, for example. Resolution If all the connections are being consumed with Thick Client logins, then reduce the number of people that are logged in at any given time or purchase an additional concurrent client license so there is one free for SOAP to use.

Issue An SP-RDM2 will be used to add doors to an I/NET-transitioned site. The readers connected to the SP-RDM2 will need to read Hex Card Number credentials. Product Line Security Expert, TAC INET Environment Security Expert Controller (SP-C) Security Expert Reader Module (SP-RDM2). Cause After transitioning an INET site to Security Expert, you may find it necessary to add one or more new doors. In Security Expert, you add doors to your system by attaching one or more SP-RDM2 modules to the RS-485 bus of an SP-C (up to two doors per SP-RDM2). That is still true for the transitioned system; however, some configuration tasks must be performed to allow the SP-RDM2 to coexist with the SCUs and DCUs that are already communicating with the SP-C.  You will also configure the SP-RDM2 to use the custom Hex Card Number credential you created as part of the INET transition process. Resolution For an SP-RDM2 module to work in conjunction with I/NET modules it must be configured in a specific way. You will need: SP-C firmware 2.08 build 911 or later SP-RDM2 firmware 1.12 build 546 or later Configuring the SP-RDM2: To the existing transitioned I/NET site, add a new Reader Expander for the additional SP-RDM2 reader module. (Note that the last reader expander defined in your existing system may be assigned to a dual-address SCU. If this is the case, make sure the address you assign to the SP-RDM2 is at least two addresses higher than the SCU to avoid address conflict.)  Set the Reader 1 Format and the Reader 2 Format to "Custom Credential". (Note that if the Port 1 Network Type or Port 2 Network Type is set to "Schneider Electric RS485" then this will need to be changed to "Wiegand" to allow you to set the reader format; it is greyed out otherwise. The network type can be set back to "Schneider Electric RS485" afterward.) Set the Port 1 Network Type and Port 2 Network Type according to the type of readers that are connected. In order to correctly convert the card read to the hexadecimal credential format that is programmed for the users, the reader expander must know what card format is being presented. This is done using commands. For the reader on port 1, add the command "R1RawFmt = #" where # is one of the descriptions shown in the table below. Similarly for the reader on port 2, add the command "R2RawFmt = #" where # is one of the descriptions shown in the table below.  If the command is absent, then Wiegand 26 is used as a default. Command Card Type R1RawFmt = Wiegand 26 26-bit Wiegand R1RawFmt = Wiegand 32 32-bit Wiegand R1RawFmt = Wiegand 34 34-bit Wiegand R1RawFmt = Wiegand 66 66-bit Wiegand R1RawFmt = Custom Wiegand Any Wiegand card - parity check is skipped Additionally, the SP-C controller must know which reader expanders to expect on the I/NET network and which reader expanders to expect on the Security Expert module comms network. By default, if the controller command "INET = true" is present in the SP-C, then all modules are considered to be on the I/NET network. Adding an SP-RDM2 to the Security Expert module comms network with no additional commands will result in partial operation but there will be problems. To use a mixture of I/NET modules and Security Expert modules, a command must be added to the programming of all I/NET modules. This command is: "HardwareType = INET" If this command has never been added to any module, and the command "INET = true" is present in the SP-C, then all modules are treated as I/NET. This maintains backward compatibility with existing sites. As soon as the "HardwareType = INET" command has been added to even one module, then it must be added to the programming of all I/NET modules from then on for the site to function as expected. Configuring the SP-RDM Doors to Accept Hex Card Number Credentials Create a new Door Type for reading cards as a Hex Card Number credential and configure it as follows. In the Entry section on the General tab, set the Entry Reading Mode to "Custom". In the Entry Credential Types section, add the "Hex Card Number" credential type. Save the Door Type. Configure each door on the SP-RDM2 to use the new Door Type as follows: In the Setup section on the General tab of the door, set the Door Type to the name of the Door Type you just created in step 1. Save the door.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Introducing a previously commissioned Continuum IOU module such as an AC-1 to an Access Expert or Security Expert site can cause communication issues in the LON bus due to duplicated node id. Product Line Andover Continuum, Security Expert, Access Expert Environment Continuum AC-1 Continuum Net Controller Continuum Net Controller II Access Expert Controller Security Expert Controller Cause When IOU modules are commissioned in a Continuum system, the Net Controller assigns each module a Node ID, this is in addition to the LON Module ID that is unique to each module hardware, the purpose of the Node ID, is to decouple the identifier used by Continuum for communication from the specific piece of hardware, this in order to facilitate the replacement of a failed module without the need to change its Continuum identifier. The module stores the Node ID in nonvolatile memory so that it persists across power loss. If a Continuum IOU module is introduced to a LON network (Security Expert SP-AC1 or Access Expert AX-SSC) without clearing its Node ID, there is a risk of creating a duplicate Node ID condition that will prevent the LON network from operating properly. IMPORTANT This should not be an issue during the normal transition of Continuum site to Security Expert or Access Expert, as all the modules on the running LON bus should have unique Node IDs, this is only a problem when adding a module, or replacing a module with one that has been used before. Resolution In order to signal its presence on the LON network, each module will transmit on resetting its status network variable. If upon receiving this message, the Net Controller determines that the module is NOT in its local database, the controller will decommission the module by setting its Node ID to zero. Before introducing a Continuum IOU module that has been previously commissioned to the LON network of an SP-AC1 or SX-SSC controller, decommission the IOU module using the steps below: Attach the module to an empty Net Controller that is powered down with its battery removed. For a Net Controller II, in order to be absolutely sure that the Net Controller has an empty database, you may need to clear its backup in flash from a browser or by the use of the reset IP switch. See LL on how to use the controller's reset IP switch to clear its flash backup https://community.exchange.se.com/t5/Building-Automation-Knowledge/How-to-clear-the-controller-flash-backup-from-the-hardware-using/ta-p/5877 Power up the Net Controller Once the CPU led on the Net Controller starts blinking, press the 'Reset' button on the IOU module. Wait 30 seconds to make sure the decommissioning process has completed. Power down the Net Controller Remove the IOU module

Issue Need to upgrade V3 Access Expert On Premise software to the most current version in order to gain additional functionality. Product Line Access Expert Environment Access Expert Premise Software V3  Cause It is unclear how to upgrade the Premise V3 software to the most current version of V3. Resolution Access Expert Premise Upgrades now require an SLA to obtain the actual software. Please contact your Sales and/or Security Contact for more details. Both the Access Expert (AX) Premise Server and Client Software need to be upgraded in order for additional features to work. Please note that you will experience issues if your AX clients do not match the AX server version. Take a backup of Mongo database (See MongoDB Backup section located here: https://community.exchange.se.com/t5/Building-Automation-Knowledge/Backup-and-Restore-MongoDB-for-Windows-for-Access-Expert-On/ta-p/583) Ensure ALL Windows Updates are completed. Capture screenshots of software installed on server. This can be done by navigating to Control Panel > Add/Remove Programs. It is imperative that you capture the following software and their versions: Access Expert Keep MongoDB SEQ At the writing of this, AX 20.3.1 is the latest. Please check this link to see if there is a new release. Once you have the software downloaded, there will be seven (7) files in the folder: Right-click on “Feenics.Keep.Installer.exe” From there, follow the steps from the Keep by Feenics On Premise Deployment Walkthrough starting from page 8 through page 18.  Note: You must be logged into the Feenics website to access the link in this step.  Navigate to https://www.feenics.com/training/ to login and then click the link above in this step. After a successful installation, click on the “Setup_AX.msi” or “Setup_AX.exe” file to install the latest On Premise client for customer machines. If you run into any issues, please contact Product Support and Services by submitting a case here: https://www.nampss.com/ If you require assistance or would like Schneider Electric to perform this upgrade for you, you can submit a request for that here: https://www.nampss.com/apps_request.php

Issue Information not available in product documentation. Product Line Satchwell Sigma Environment Windows versions Cause Documentation not updated to show additional operating systems now supported. Resolution Sigma 4.0.8.57, as a front-end user interface, is supported on the following operating systems: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 80 – 89), as an engineering tool for Sigma when transitioned into SBO/EBO Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 Sigma 4.0.8 (build 104 onwards), as an engineering tool for Sigma when transitioned into SBO/EBO system Sigma is supported on: Windows XP Pro Service Pack 3 Windows 7 Professional Windows 7 Ultimate Windows Server 2003 Windows Server 2003 R2 Windows Server 2008 Windows Server 2008 R2 **1 Windows 10 **1 Windows Server 2012 **1 The additional operating systems support is only applicable when Sigma is part of a SBO/EBO installation. (This confirmation was provided to PSS by R and D).

Issue Data Sync Service won't run after installation Product Line Security Expert Environment Security Expert Server Cause Mismatch in authentication type during the installation of Security Expert Client and Security Expert Soap Service Resolution First completely uninstall the Security Expert Soap Service and Security Expert Client... Then reinstall Security Expert Client ensuring to UNTICK the box to hide advanced database configuration options When asked about Customize WCF TCP/IP Port, make note of your selection. Please note that using TLS 1.2 is the recommended method for authentication. Then reinstall the Security Expert Soap Service matching up the authentication type used for the Security Expert Client.

Issue Is it possible to trigger a manual Battery Test in a SP-C or SP-C-Web? Product Line Security Expert Environment SP-C SP-C-Web Cause The SP-C Web Security Expert - Programming - Reference Guide refers to indication of when the SP-C-Web passes or fails its Dynamic Battery Test, but what if a user wishes to manually perform or trigger such a battery test. Resolution The Dynamic Battery Test is a purely automated process and cannot be manually forced or triggered, however these tests are performed every ten minutes when mains power is present.

Issue "Ethernet 1 Configuration" of a SmartX Server in the Device Administrator for EBO version 3.2.1 or higher shows "Dynamic DNS" as enabled and grayed out. Is it possible to disable "Dynamic DNS"? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium version 3.2.1 or higher Cause The  Dynamic DNS  service procedure supports the assignment of  dynamic  IP addresses to a particular domain. A comparison with the internet provider's  DNS  databases takes place automatically. The Dynamic DNS automatically ensures that changes to the IP address are detected and  DNS  entries are updated accordingly. Resolution In EBO version 3.2.1 or higher it will not be possible to disable Dynamic DNS, it will always be enabled.

Issue BACnet Interface has "!" with unresolved references Product Line EcoStruxure Building Operation Environment Building Operation Automation Server v2.0 or later Building Operation Multi-purpose VAV Building Operation Multi-purpose Controller Cause During the startup of a Smart-X controller, the auto-association feature fails and the data becomes corrupted Resolution Go to BACnet Interface -> Time Sync Recipients Find any devices listed as DEVICE_<Instance ID>, select & delete Verify all devices listed are configured as follows: SmartX controllers Recipient Type: Reference Recipient Device Object Reference: <Device in System Tree> If Recipient Name does not match, copy from Object Reference and paste in the field. This helps humans troubleshoot the issue. DO NOT set Recipient Type = MAC Address, Network ID = Global Network or Local Network, Mac Address = Broadcast. This will set time on other ES/AS with BACnet Interface on the BACnet System.

Issue Many campuses are configured with 1 BACnet Network ID number for Primary IP that is unique per building whether or not they are in the same IP subnet or multiple (with BBMDs). Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause Page 2887 of the 3.0.x technical reference guide does not clearly explain the configuration and it also does not extend to multi-building systems using BBMDs. Resolution BACnet network numbers are assigned at BACnet routers, with a Range of 1-65,534 (where 65535 is reserved for broadcasts). Routed networks are assigned unique network numbers and can only have 1 router per network. Routed networks are usually BACnet MSTP, BACnet Ethernet, and Secondary IP networks. Standard practice is to have primary IP networks consisting of IP routers/devices in the same IP subnet or across multiple IP subnets joined by a BBMD and/or foreign device configuration uses the default BACnet network number 1.

Issue The documentation notes a TC900 can be changed from a 4-pipe system with a 2-wire motorized valve to a 2-pipe system with a 3-wire motorized valve. What parameter changes are required? Product Line Field Devices Environment TC907-3A4LAB TC907-3A4LMAB TC907-3A4DLSAB TC907-3A4DLMSAB TC907-4FMSAB TC907-3A4DPSAB TC907-3A4DPMSAB TC907-3A4DPMSA-24B TC907-4FMSA TC907-3A4LMA TC907-3A4LA TC907-3A4DPSA TC907-3A4DPMSA-24 TC907-3A4DPMSA TC907-3A4DLSA TC907-3A4DLMSA Cause Documentation is unclear in how a TC900 is configured to use a 3-wire valve actuator Resolution Access the parameter settings by pressing and holding the mode button for six seconds during thermostat power up. Press the mode button or Fan button to move forward or backward between the parameters until parameter 09 is displayed. Press the up and down buttons to set the parameter to 04.  

Issue Pressing the Read Card button in the User object instantly crashes the Security Expert Client. Product Line Security Expert Environment Security Expert Client 4.2.259.19 and earlier Cause There was an issue when attempting to assign new card details to a User by pressing the Read Card button on one of the Card Number slots will crash the client. Read Card Resolution This was fixed in Security Expert version 4.3. Other methods for adding new credentials to Users also include: Manually adding the Facility and Card Numbers to an available slot in the User object. Badging the card at a Card Reader and right-clicking the resulting access event in the Status Window and selecting to add to an existing or create a new User. Use the Data Sync Service to import Users, and changes to Users, from CSV files. See Mass importing User Photos into Security Expert using Data Sync Service for an indication of how the Data Sync Service is configured.

Issue Backup and Restore Process for WebReports Product Line EcoStruxure Building Operation Environment WebReports Reports Server SQL Server 2008 R2 Cause Need detailed backup process Resolution Refer to Online Help Topic for details Backing Up the WebReports Database  On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect.   Note: When using a remote computer to connect to the Report Server SQL database, the Windows Accounts must exist on both machines and have administrative rights for the SQL database otherwise a successful backup will not occur.  In this instance, it is recommended to use the SysAdmin ' sa ' login / password details when connecting in remotely.   Expand the Databases folder. Right-click StruxureWareReportsDB , point to Tasks, then click Back Up. Under Destination, click Add. Click OK. In the Destination on disk box, select the backup destination. Click OK. Click OK.   Restoring the WebReports Database Ensure the Enterprise Server is up and running with the correct database.  Stop the SQL Server Reporting Services and WebReports Agent (if installed).  Note: If moving the WebReports Database it is recommended to restore the database then Install WebReports.  Then when Installing WebReports select Upgrade existing (as shown) and NOT New database  Restore the WebReports database to recover reports data from backup.  This will include any Dashboard reports saved. On the Windows toolbar, select Start, and then click SQL Server Management Studio. Click Connect. Expand the Databases folder. Right-click StruxureWareReportsDB and select Tasks, then select Restore, then select Database. In the Restore Database dialog box, select the database set(s) that you want to restore. Click OK. Click OK. If not already installed now complete the installation of WebReports 

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 SP-C Controllers randomly going offline / online.  Restarting the controller resolves the issue for a short period of time. SP-C Controller ports showing TIME_WAIT when a netstat command is run. Product Line Security Expert Environment Security Expert Controller (SP-C) Cause Under normal conditions an SP-C needs to update the Security Expert Server with new data. During this time the IP Socket of the SP-C is in a Waiting State, refusing to communicate to anyone else while waiting for an opportunity to upload. Once the controllers data has been uploaded to the server however the controller releases the IP Socket and it is open again to new communication. In an extremely small number of cases the SP-C controller goes into this waiting state as usual but then never comes out of that state, holding onto the IP Socket forever and blocking any further communication until the controller is power reset. This only affects a very small percentage of SP-C controllers running Microsoft Windows CE OS Version 16. Resolution In these extremely rare cases the first step is to identify that the affected controllers are indeed running the affected OS version 16. Log into the controllers configuration web page. Browse to the Configuration tab. Check the OS Version field at the bottom of the page. (For SP-C firmware build 921 and greater this is in a different location.) Once it is clear, that the OS is version 16, Product Support can be contacted to arrange to upgrade the controller OS to Version 20 (or greater) as is found in SP-C controllers shipping now. As this is a high risk procedure and can result in complete failure of the controller if anything goes wrong there are two options for upgrading the OS. Install the affected controller on a test bench with remote access for Product Support to remote in to and perform the update. Have the controller sent back to the factory to be updated and returned to site. Both options will require replacing the controller with temporary stock while the upgrade is being performed.

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

Issue If more than 3 Operators are created in Security Expert, the License page of the Thick Client will show more Licenses in use than the maximum three (3) clients provided with the standard  SX-SRVR License. To see what the site is using, select About > License and scroll down to the Feature: Web Operators. As shown below, there are four web operators active out of the three (4/3) allowed. Product Line Security Expert Environment Licensing Cause A Web Operator is defined as any Operator who can log onto the Security Expert Server using a browser.                           In the example shown below there are four Operators: admin 2nd Operator 3rd Operator 4th Operator The system allows each to log in successfully: The License option SX-WEB-OPR  enables 'x' number of browser connections depending on customer needs and should effectively ensure that the correct number of Operators are purchased, but the feature is currently in development and is not yet enforcing limits on the number of operator connections.  This allows the number of connections to exceed the maximum limit (I.e.4/3) for the time being. Resolution Note: The Operator does NOT even need to be logged on for the count to register 4/3, the fact that 4 operators have been created is enough. The restriction of operators via Web Client could be enabled/enforced at any time in the next release of the software, so it is strongly advised to purchase the correct number of Licenses required at the time of installation, to prevent a loss of user connectivity going forward.

Issue When a Modbus device comes back online after being offline a message is sent from the Building Operation Server to the Modbus device which looks similar to: WriteData TX on /dev/tac_comporta: 01 2B 0E 01 00 70 77 ReadData RX on /dev/tac_comporta: 01 AB 01 9E F0 This message can cause the Modbus device to restart or stop responding, is it possible to disable it? Product Line EcoStruxure Building Operation Environment Building Operation 1.5.x to 2.0.3 Modbus Device  Socomec Power Meters Cause A feature was added in release 1.5 that is intended to read the device's identification (0x2B). It works by polling this function code (FC). If the Building Operation server does not get a valid reply to this message, it assumes it is not supported by the device and will not request this again. This is usually not a problem but some Modbus devices, such as those listed in the Environment above, are unable to handle this message and will stop communicating with the AS or ES. Resolution In Building Operation 2.0.4 and above the option to enable or disable the device identification request (Function code 2B) has been introduced, allowing the poll interval (and online detection) to be set. In previous versions this message cannot be disabled, however, if device polling is disabled the device identification request won't be requested, which can be used as a work-around. To turn off the device polling: Open Properties Set "Poll interval" to "Inhibit" The trade-off with this work-around is that the online detection for the device is turned off, so the device will never go offline in Building Operation.

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue When transitioning Continuum access control to Security Expert or Access Expert the Continuum power supply may need to be configured for auxiliary IO power mode.  Product Line Security Expert Access Expert Environment Continuum AC-1 IO Module Security Expert Controller Access Expert Controller Cause The UPS versions of the 120/240 AC Continuum power supply include two status signals that are meant for use by a CPU module. When connecting directly to an I/O module you must disable these signals. If signals are left enabled they will cause communication issues between the AC-1 IO modules and the Security Expert or Access Expert controller. Resolution This applies  ONLY to the UPS models of the Continuum power supplies (PS 120/240 AC 50-U, AC 65-U and AC 85-U)   Remove power from the unit. On the Continuum power supply, press both cover removal tabs inward simultaneously and pull up. Locate the Mode switch using the diagram below. *** With the tip of a small screwdriver, carefully slide the switch to the AUX position. Replace the cover.   NOTE: On older versions of the power supply, instead of a switch, two jumper components must be removed from the printed circuit board.  

Issue When using the Modbus RTU and Modbus IP XDrivers it is important to determine which controller and port can support the electrical standards used by the 3rd party device. Product Line Andover Continuum Environment Continuum Netcontroller II and bCX1 controllers that have been XDriver enabled. XDriver, Modbus RTU, IP, Infilink, Infilink200, B-Link. RS-232, RS-485 JBUS Cause Controller ports and 3rd party devices come in various electrical standards (RS-232, RS-485, RS-422), which ports support the various standards? Resolution There are two Continuum Modbus XDrivers: Modbus RTU: This allows the connection of 3rd party Modbus RTU slaves via the serial data RS-232, RS-485 or RS-422 electrical standards. RS-232 is a point to point connection to 1 device, RS-485 & RS-422 support a bus topology for connection of multiple 3rd party devices. The Continuum controller will be the Modbus RTU Master and will poll the 3rd party device that must be a slave. The bCX1-CR controllers have 2 ports that can be configured for Modbus: Comm1 RS-232 Comm2 RS-232 or RS-485 port The Netcontroller II controllers support: Comm1 - RS-232 or RS-485 Comm2 - RS-485 Comm3 - RS-232 Comm4 - RS-422 The ACX57xx controllers support: Comm1 - RS-485 Notes An Infilink200 or B-Link may be used to convert RS-232 to RS-485 if required. The J Bus protocol is a subset of the Modbus protocol and so the Modbus XDriver is used for J Bus Systems. Modbus IP: The bCX1, ACX57xx and the Netcontroller II all support the Modbus IP protocol that connect via the Ethernet IP connection. This XDriver can be configured to support either Client or Server modes. Although the communication is physically via the Ethernet port, one of the Serial ports is required to be X Driver enabled to load the software, this serial port is then no longer available for other purposes. This XDriver requires Ethernet X Driver support to be enabled on the port. NOTE Netcontroller II and bCX1 can have an XDriver ENABLED on more than a one Comms port, however only one IP XDriver should be INSTALLED on each controller, also only one Modbus RTU XDriver should be INSTALLED on each controller. It is possible to INSTALL a Modbus RTU and a Modbus TCP/IP XDriver on a single controller, but it would be very easy to overload the controller, so this setup is only suitable for smaller networks. (note the difference between enabling XDriver support and Installing an XDriver) See Articles  Can multiple Modbus TCP/IP XDrivers be installed on a single 2nd Generation NetController? and BCX Controller can use Comm 1, Comm2, or both ports for Modbus RTU X-Driver