Building Automation Knowledge Base

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  

Issue Enterprise Server ES crash Product Line EcoStruxure Building Operation Environment Enterprise Server ES Enterprise Central EC Cause The ES/EC runs on a Windows platform and there are circumstances that can lead to a single crash or multiple crashes leaving the ES/EC not running Background - The ES service is usually running. The service can be seen below under the Windows services and via "Building Operation Software Administrator"  The ES v4.0 has crashed and will not restart. The "Building Operation x.x Connect Agent" collects any core dumps and packages them, so they can be quickly analyzed. It also checks if an ES is registered and online, then uploads the core dump files for automatic analysis. If the site is not registered or is offline, then these files are stored locally at %ProgramData%\Schneider Electric [EcoStruxure|StruxureWare]\Building Operation [n.n]\Enterprise [Server|Central]\db\Crash information (default for v4.0 "C:\ProgramData\Schneider Electric EcoStruxure\Building Operation 4.0\Enterprise Server\db\Crash information") The "Building Operation x.x Connect Agent" is a Windows Service and installed with the ES, the service should be left to run continually. If it is not running during an ES crash, the core dump may still get created, but does not get packaged up in a way that can be easily analyzed. Each packed crash dump file may look like "ES_ES_MYCOMPUTER_20221104T121314Z.zip" and likely be between 40MB and 200MB in size. The individual core dump will look like "server_20230314_132853__r4.0.3.176.dmp", but is very time consuming to analyze, without the other associated files Resolution Following a crash,the EC/ES will usually restart and operate correctly, however in some cases the EBO database or install file structure may be damaged and the EC/ES may fail to restart correctly EC/ES has crashed and is now running correctly Send the following information to Support - All core dumps from the "\db\Crash information" folder - All data from the "\db\logs" folder - Ideally a full backup of the ES (with history), always zip before sending to Support If the "Crash information" folder is empty, then check the "Building Operation x.x Connect Agent" is running. It is possible the core dumps have already been uploaded and analyzed automatically EC/ES has crashed, tried to restart but just stops again. (as seen in the first screen shot, "The server has made too many unsuccessful attempts to start..." is seen It is important to gather all the data as stated above, but also collected the EC/ES and AS backups from "\db_backup" It can be useful to get full copy of the files in "/db" Ideally the EC/ES is not critical to the operation of a site, but it can still cause a big problem. Checking the Trace and System logs may give a clue to the problem, e.g. a lack of disk space, but often there are only a few options   Collect the files above, then wait for a reply from support. Please state if the EC/ES is stopped and a resolution is being sort. Reinstall the EC/ES at the same version and choose repair current version, or upgrade to a newer CP Fix version or maintenance version. Uninstall the EC/ES, then re-install the same version with an empty database, then restore the last good backup to the ES. If option 2 or 3 is used, it is still important to log a case with support, so the crash can be investigated. The backup can be checked for errors using the XBK Analyzer.

Issue Can I remove the permanent override feature or limit the maximum override duration from the station or an individual point in I/A Series G3? Environment I/A Series G3 Cause Can I remove the permanent override feature or limit the maximum override duration from the station or an individual point in I/A Series G3? Resolution Starting in version 3.4.51, the permanent override can be removed globally from the station by adding a facet to the SysInfo facets property on the root of the station. Add a new BRelTime value to the SysInfo facets and assign it the name "maxOverrideDuration." This enables a station global limit on the duration for any control point. The value of this BRelTime should be the MAX duration allowed. A value of zero means that 'Permanent' is allowed. A non-zero value limits the custom to a maximum time value.  Note that 'Permanent' is the default if no "maxOverrideDuration" facet is found. Starting in version 3.5.25, the feature was enhanced to allow specifying the max duration on an individual control point basis. Follow the same procedure as defined above but add a new BRelTime value to the individual point's facet. Example: Right click on the station's Config container and select View - Property Sheet. Click on the Sys Info >> to open the Config Facets dialog box. Select + to add a facet. Click inside the Key area and enter the new key name maxOverrideDuration. Click on the Type drop down and select RelTime. Click on the Value ... and enter the desired time. Select OK

Issue What are the sourcing and sinking specifications of the analog voltage outputs on the different controllers? Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 XP IO modules Cause Sourcing and sinking refer to the ability of a DC circuit to PUSH or PULL a direct current through the circuit. Resolution Voltage Sourcing In a controller's voltage sourcing output, the output provides a voltage source that PUSHES a direct current through the load as indicated in the illustration below. The current flows from the output's positive (V/+) terminal through the load to the output's negative terminal (-/ RTN). Current Sinking In the illustration below, a controller's voltage output is sinking a current from the load. Note the voltage source in the load's circuit which is at 15 VDC. Because current always flows from positive to negative, the voltage coming from the controller's output (0 - 10 VDC) will ALWAYS be more negative than the load's source of 15VDC, thus a current will flow from the load's voltage source through the controller's output circuit to reach the negative (RTN) side of the output's circuit. The lower the voltage coming out of the controller's output the more negative it will be as compared to the load's voltage source, thus the output will be sinking the most current when it has a value of 0 volts. It is extremely important when using a controller's voltage output in a way that will make it sink current to know the maximum amount of current the output will be sinking and to ensure it does not exceed the current sinking capacity of the controller's output. The following table shows the sourcing and sinking capabilities of the voltage outputs of the different controllers. CONTROLLER VOLTAGE SOURCING CURRENT SINKING COMMENT i2/b3 814 Voltage output 0-10 V @5 ma max 1 ma max Exceeding the 1 mA sink limit will cause the IO readings to be incorrect. ie, inputs may read 999.99

Issue Need to ensure that there are not any unresolved or invalid bindings Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Workstation v1.5 and above Bindings Diagnostics Cause Bindings are invalid because they point to something that cannot be bound together or they are unresolved because the binding points to an object that is not in the database. Resolution From the Workstation run the Bindings Diagnostics to check for invalid or unresolved bindings.   Open the Control Panel To Check the Status of Bindings  click the option for Bindings Diagnostics.   Observe the Status to identify any invalid or unresolved bindings. Refer to the EBO Webhelp Binding Status Icons topic for more information Right-click the invalid or unresolved binding, edit the binding or view properties, and correct as appropriate.

Issue Need to send Continuum alarm messages to email addresses  Product Line Andover Continuum Environment Continuum Cyberstation Cause Alarm delivery required to remote users via email.  Resolution Please note this resolution is applicable to all versions of Continuum Cyberstattion and requires Microsoft Exchange or Outlook to send emails.  However, CyberStation version 2.xx does not necessarily require Microsoft Exchange or Outlook to send emails for alarm notifications. Instead, it is possible to configure an SMTP server on the network and use it to send alarm email notifications directly to the intended recipient.  Please refer to SMTP Email Alarm Configuration in Continuum 2.00 to 2.03    Here are some requirements for forwarding Continuum workstation alarm events via email and paging: The Continuum workstations that have been designated primary and backup email and/or page handlers must have an email client such as Microsoft Exchange or Outlook. The email client application must communicate with an existing email server application, such as MS Exchange Server. The primary or backup email/paging workstation must be running Continuum at the time an alarm is generated. Each EventNotification object associated with the alarms that you wish to email or page must have its own email distribution list in the personal address book of the client email application using a specified naming convention as outlined in the table below. This email distribution list must be stored in the first address book shown in the list of available address books in the email client application. For example, if you create an EventNotification distribution list in the Personal Address Book in Microsoft Outlook, then the Personal Address Book must be the first one showing in the address list dropdown box when you open the Address Book.   How to Create an EventNotification Distribution List Note: The following steps are based on Microsoft Outlook. Other mail applications may have different menu names and choices but the general procedure is the same. Step Action 1 Open the Address Book for the email account on the Continuum workstation that will be providing the email/paging services. Your toolbar may have a button for this. If not, use the Address Book option of the Tools menu. 2 Select New Entry from the Address Book File menu. 3 Select the entry type Personal Distribution List and put this entry in the Personal Address Book. 4 In the Name field enter a name for the distribution list using the following format: For E-mail: ACC.name For Paging: ACC.page.name where name is the name of the EventNotification. 5 Add members (the email addresses or pager and service numbers of those to whom the notification of the alarm will be sent) to your personal distribution lists. 6 Set address book options so that the address book where your personal distribution lists are stored is the first one to be searched when sending emails or pages.

Issue No Communications when directly connecting to a MicroNet Controller. Product Line Satchwell MicroNet Environment MicroNet controller (MN300, MN440, MN500, MN620 or MN350, MN450, MN550, MN650) using VisiSat Cause Controller subnet setting incorrect. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Go to the VisiSat server on the taskbar by the clock.      Drop down the Network menu Then select restart. This will reset the controller subnet setting to 1 Now the Visisat server should be able to connect to the controller.  

Issue Replacing an older style 400 I/O with 400A series hardware, the Digital Inputs need changed to reflect the newer style of Universal Input. Product Line TAC Vista Environment Xenta 400 I/O Xenta 421, 422, 451, 452 Xenta 421A, 422A, 451A, 452A LonMaker Replace Cause Hardware changes in the Xenta 400 "A" series I/O will not function as a replacement to a non-"A" series without additional changes to Menta and LonMaker. Resolution Part 1- Changes needed within Menta Open the controller’s application (a Menta file). For ES projects, this file should be stored within C:\TAC\Vista\Applications. Note the I/O module that needs to be replaced. A list of I/O modules can be found under the Options menu on the Device Specification page:   Find and record all input points on the I/O module to be replaced. This list is found in the I/O Configuration Table under the Options menu. For example, write the "Name" and "Bound To" address for every point referencing M2.   After you have noted all of the addresses for input points on the I/O module that will be replaced, you can edit the device type for the I/O module to reflect the new type (421A or 451A). Making this change WILL remove all DI mappings (421: X1-X4) and all thermistor mappings (451: B1-B4) affected by the change in module type.   Double-Click on each DI block from the 421 (X#) or on each AI thermistor input block from the 451 (B#) that you are updating to a 421A or 451A.   The following window will appear. Click the Bind button.   Update Menta FOR 421A POINTS: The controller’s DI points are now UI points. Select the Terminal Ref based on the old mapping: X1-U1, X2-U2, X3-U3, X4-U4 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. FOR 451A POINTS: The controller’s thermistor inputs (B#) are now additional Universal Inputs. Select the Terminal Ref based on the old mapping: B1-U5, B2-U6, B3-U7, B4-U8 After selecting the new Terminal Ref, click the OK button and then the OK button again for the Edit Block window. **Repeat step 7 for all affected points on the I/O module you’ve updated. Repeat steps 2-7 for every I/O module that needs to be replaced by a 421A or a 451A. PART II - Integration Within LonMaker locate the controllers that you want to change out for a 421A or 451A   Right click on them one by one, a click "Delete."   Open the Vista System Plug-In. Right click on the controller in which you want to change the .MTA application. Click "Configure."   Click "Browse," and locate the updated .MTA file you saved   Click "NO" when asked if you want to remove the devices   Click "Add and Match"   Click "Apply"   Re-Synchronize LonMaker   Your controllers should now be 421As or 451As

Issue Error Getting IIS object: IIS://LocalHost/W3SVC/1/Root/webclient. Automation error Invalid syntax when installing webclient Environment Webclient Windows XP Windows 7 Cause IIS must be installed prior to webclient or the webclient applications cannot be created Resolution 1. Install IIS prior to the webclient install (See the installation guide section Pre-installation Microsoft Tasks) 2. If IIS is already installed, run the following command from a DOS prompt (Start>Run>cmd) CD\ + enter Cd \Windows\Microsoft.net\Framework\v2.0.50727> aspnet_regiis.exe -i + enter Reboot the PC and reinstall webclient Windows 7: Ensure that all the specific IIS components are selected according to the webclient installation guide See the section Configuring IIS for Windows Vista and Windows 7. There are specific components that must be selected in order for the webclient applications to work properly. If a component was missed, select it, then restart IIS and Continuum.

Issue Do IP settings go to defaults when flashing from 4040 to 9640? Product Line Andover Continuum Environment bCX9640 bCX4040 Cause Have a need to flash a controller from bCX4040 to bCX9640 over a remote connection access. Do not want to have to go to the site to reset IP settings.  Resolution Using CyberStation v1.93 a bCX4040 was flashed to a bCX 9640 and it did NOT lose its IP info. Notes: At the end of the upgrade an error was received: “The uprev could not communicate with the specified controller”. From the webpage it was noted that the IP address had not changed and the upgrade was successful. It did not come back online in CyberStation. From the webpage, resetting it still did not bring it back online in CyberStation. Changing the model number in CyberStation to bCX9640 (from bCX4040) to bring it back online was not an option. The flash upgrade had reset the ACCNetID to 1. The 4040 was then deleted (Bacnet side first then Infinity side) and a new 9640 was created. The proper ACCNetID was set up in the webpage and the changes committed. It was then online in CyberStation. Bottom line – IP address never changed. ACCNetID did. The controller never had to be touched during this process so remotely doing this is expected to work. This was only tested using the latest firmware and CyberStation v1.93. Of course, the best way to do this is on the bench not on a live system. Please be aware that the model flash change will cause node count and/or xdriver upgrades to be reset if they were added as post-factory-shipment upgrades (via the Repair Dept) since these upgrade UPD files are model specific. See Node or XDriver Upgrade of BCX Inf (9640) to BCX BACnet (4040) or reverse. Also see Update b3 or i2 OS, changing (converting) a controller, BACnet to Infinet or Infinet to BACnet .

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 setup SAML SSO with Azure EntraID Product Line EcoStruxure Building Operation Environment Building Operation Workstation Azure Cause The SAML configuration requires details setup Resolution Part 1: EBO configuration Creating and Configuring the SAML Configuration Object To create and configure a SAML configuration object. In WorkStation, in the System Tree pane, expand the System folder. Expand the Federated Authentication folder. Select the SAML Authenticator object. On the File menu, click New object. Select SAML Configuration. Enter a name, path, and description on the object you want to create. Click Create. Configure the settings. Enabling Federated Authentication To enable federated authentication In WorkStation, in the System Tree pane, select the EcoStruxure BMS server you want to configure. Click the Control Panel tab. Click Security Settings. Select Enable federated authentication. Click the Save button. Configure SAML Configuration object Service Provider To configure the service provider. In WorkStation, in the System Tree pane, click the SAML Configuration object. Click the Service Provider Settings tab. Configure the settings. Identity Provider To configure the identity provider. In WorkStation, in the System Tree panel, click the SAML Configuration object. Click the Identity Provider Settings tab. Configure the settings. Configuring the Security To configure the security. In WorkStation, in the System Tree pane, click the SAML Configuration object. Click the Security Settings tab. Configure the settings. Create and configure domains Create and configure a domain to be used for Federated Authentication. Create a Domains Create a group Configure the permission for the group Part 2: Azure Configuration Login to https://azure.microsoft.com/ Create SAML application under Entra ID Click Microsoft Entra ID Click Enterprise Application Select Create your down application Enter the name of the App Select “Integrate any other application you don’t find in the gallery (Non-gallery)” An Enterprise Application is created with the name Create a group Select Groups Click New Group Select “Microsoft 365” for the Group type Enter the name of the group, the “Group name” must match the Domains Groups name in EBO. Add Owners and Members to the group Configure Entra ID Select Assign users and groups in the Enterprise Application Overview Select Add user/group then click Assign The selected group is under the application Select Set up single sign on in the Enterprise Application Overview Under Basic SAML configuration Enter the information from EBO SAML Authenticator Basic Tab The Sign on URL is Base URL The Identifier is Entity ID The Reply URL is AAssertion Consumer Service URL Click on Edit from Attributes & Claims Click on “Add a group claim” Select Groups assigned to the application Select Cloud-only group display names under Source attribute update the “Unique User Identifier” Value to user.displayname Download the “Federation Metadata XML” certificate Open the XML file and find the line with certificate, it will start with <XXXXCertificate> Copy the string between the two brackets and paste it in Public key certificate under Identity Provider Settings Copy the Entity id and Single Sign On Service URL from Azure to EBO. The Entity Id is Microsoft Entra Identifier. The Single Sign On Service URL is Login URL. Part 3: Testing Test Single Sign On Go to Webstation by entering the SmartX Server network address. Click on Log on with SSO Select the account within the Azure Group Successful login screen

Issue "You need to enable JavaScript in your web browser to be able to use Building Operation" message is displayed in the browser window when accessing EBO WebStation using the URL "https://<IP>/login/login.html" Product Line EcoStruxure Building Operation Environment Building Operation Webstation 5.0.3 and later Cause In order to bypass automatic guest account login, some sites have used https://<IP>/login/login.html as a direct URL to the login page. In EBO 5.0.3 this direct URL has been changed to "https://<IP>/login.html" to allow PCT 2.0 to operate correctly. Resolution Use the new "https://<IP>/login.html" URL to bypass automatic guest account login and update any saved browser bookmarks.

Issue What are the replacement battery part numbers? Product Line Andover Continuum Environment Continuum and Infinity controllers i2, b3, CX, bCX1 SCX920, LCX810, LCX800, TCX850 Cause Replacement part numbers required. Resolution All the i2/b3 controller battery types are covered on pages 48/49 of the b3 Controller Technical Reference The CX9200, CX9400, and CX9900 all use 2 off: 12V 6.5A lead acid gel cells, Part number: 01-2100-423 The Part number for the bCX1 battery is: BCX1-BAT-KIT The Part number for the ACX57xx battery is: ACX2-BAT-KIT The Part number for the NC2 battery is: NC2-BAT-KIT For the older Infinity Controllers: SCX920, LCX810, LCX800, TCX850 – ½ AA 3.6V 850mA-Hr  e.g. LS14250

Issue EcoStruxure Building Operation Automation Server, Enterprise Server and BACnet object names limitation Dragging converted I/NET TGML graphics into Workstation causes Workstation to crash with following message: Exception message: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at SE.WorkStation.Base.Windows.Views.TgmlFileDropHandler.Drop(FileInfo, Path, IOperationContext, IProgressInfo) at SE.WorkStation.Base.Windows.Views.FileDropCoordinator.ExecuteDrop(Path, IList`1, IProgressInfo) at SE.WorkStation.Base.Windows.Views.<>c__DisplayClassd.b__9(IProgressInfo) at SE.WorkStation.Framework.Services.<>c__DisplayClass1.b__0(IProgressInfo) at SE.WorkStation.Framework.ProgressIndication.ProgressActionOperation`2.Run(IProgressOperationInternal, IProgressResult, IProgressOperationInfo) at SE.WorkStation.Framework.Services.ProgressItem`1.b__1a(Task) at System.Threading.Tasks.<>c__DisplayClasse`1.b__d() at System.Threading.Tasks.Task`1.InvokeFuture(Object) at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute()  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The number of characters and the use of special characters in a EcoStruxure Building Operation object name and EcoStruxure Building Operation BACnet objects names Resolution Refer to the Webhelp Object Names topic for information on naming restrictions The statements in Webhelp also apply to EcoStruxure Building Operation BACnet objects unless is it a Continuum b3 object.  If you are creating a Continuum b3 object etc., the b3 object display name is limited to 16 characters consisting solely of letters, digits, and underscores (as per Continuum limitation). Basically, any objects you create for Continuum, for example, a 'BACnet Analog Input (Continuum)' will be subjected to the Continuum limitation. If you add a standard 'BACnet Analog Input' into an Automation Server or an Enterprise Server, then it is not limited by the Continuum limitation of 16 characters. The most common issue when bringing I/NET TGML converted graphics into Workstation is not checking for spaces at either the beginning or end of the converted file name.  Make sure there are no spaces (white space) before or after any characters of the file name before copying into Workstation.

Issue After moving the License server to another computer the license server address in the License Administrator is changed to the IP address of the new computer, but EBO Workstation gets a license error when trying to login to it. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The License Administrator can be used to select which license server EBO uses. This is done by going to the License Server Address tab and entering the license server address in the License Server Address field. Note that the license server address must be preceded by an @ in order for it to work, e.g. @servab48. The License Server Address in The License Administrator is not always used when Workstation or the Enterprise server asks for a license, Resolution The request for a license is handled in the following order:   If there are licenses located locally on the machine running WorkStation/Enterprise server (activated from ASR files), those are used first. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is used. This registry key contains all license server addresses that have been successfully used to obtain a valid license previously. If this key is not empty, each server contained in the registry key value is asked for a valid license until one is obtained. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, and the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is empty, the license server set in License Administrator is used. The license server address is stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\StruxureWare\License Administrator\TACLIC_LICENSE_FI

Issue What is the Intel Floating point number as used in the Modbus X Driver? Product Line Andover Continuum Environment Modbus RTU X Driver Cause It is not clear how the two special floating point function codes vary. Resolution There are two different floating point data formats (248 & 245) these are both standard 32 bit floating point numbers but the data bits stored in memory (or read over the protocol) differently.   The 32 bits of Function 248 are stored as one string of bits, bit 0 through to bit 31.   For the 245 format the upper and lower words are swapped around, so it stores the data as bits 15 to 0, then bits 31 to bit 16. This format is called Intel format as it is the way Intel microprocessors handle floating point data.   Here is a link to information on floating point numbers FYI: https://en.wikipedia.org/wiki/Floating-point_arithmetic   These two formats can also be called Big Endian (Function 248), or Little Endian (Function 245). Little Endian is also known as the Intel format. Information on Endianness can be found at: https://en.wikipedia.org/wiki/Endianness

Issue Point under the Application folder of MP-x device shows error "Contains unresolved BACnet reference" Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation IP-IO Cause Incomplete entry in point's BACnet priority array. The screenshot below shows the XML file obtained from exporting the point, as it can be seen, 'Priority16' is missing the 'Type' section. Resolution Perform the following steps to correct the problem: Export the point out to a file. Delete the point. Import the file created at step 1, once the point has been re-created via import the unresolved error is gone. NOTE: There is no need to make any modifications to the XML file, it can be imported as is, the system will automatically correct the incomplete entry for priority16.

Issue DC1100 / DC1400 Displays two horizontal black lines when powered up. Product Line Field Device Environment DC1100 / DC1400 Discrete Controller. Cause Cold Start has not been performed. Cold Start has been performed incorrectly. Mains borne corruption has affected processor. Resolution Carry out Cold Start: Isolate Controller power supply. Press and hold down "Enter" and "Exit" buttons. Keep "Enter" and " Exit" buttons depressed while restoring power. Display should show "Self Test" and "Initiating System Variables" Release "Enter" and "Exit" buttons. Controller may then be programmed in accordance with Data Sheet instructions.   Or, if the controller is non-recoverable, the DC1100 and DC1400 units are now obsolete. However, there are several 3rd party companies offering refurbished units, these can be found by using a browser and searching e.g. DC1100 repairs.    

Issue On a system requiring Semantics after adding Enterprise Servers to an Enterprise Central alarms are generated that cannot be cleared.  Changing the password for the Servers does not fix the issue. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Central Building Operation Enterprise Server Building Operation Workstation Cause Incorrect method used when setting up Semantics during installation, Semantics were enabled on the Enterprise Server as well as the Enterprise Central.  After adding to the Enterprise Central the Enterprise Server points to a different address where the alarm is for the original Enterprise Server address.   Resolution On the Enterprise Server the alarm needs to be verified against the original connection, this involves removing the lead object link and changing the settings to look at the original Semantic Database.   On the Enterprise Server Semantic Settings remove the lead object entry pointing to the Enterprise Central.  Open the Services Manager and Stop and Re-Start the GraphDB service, if stopped start it. Additionally, Stop and Start the Enterprise Server service, this can also be done in the Services manager using Software Administrator to stop and start will show any errors if evident. Log back into the Enterprise Server and the password alarm should be cleared, this may take a minute or so but not any longer.  This is only if the password has been changed, please see Semantic DB authentication failure" alarm. Also, in the EC the password alarm should have cleared. Once the alarm is cleared the GraphDB service can be disabled from within services as it is not required. Re-instate the lead object entry pointing to the Enterprise Central that was initially removed. For more information on Semantics please see Semantic Overview

Issue Controller replacement Product Line Field Devices Environment Field   Cause Controller Replacement Resolution The CXC controller provided compensated control. The CSC 5252 or CSC 5253 (With time clock) is the current replacement. Downloads The CXC data sheet can be downloaded here. The CSC data sheet can be downloaded here. The CSC User guide can be downloaded here.   Please be aware: since July 2016 the CSC compensator and other descrete controllers were withdrawn from service. To see "PA-00479 - Discrete Controllers - Notice of Withdrawal - Satchwell" click here.