Building Automation Knowledge Base

Issue On an existing InVue installation, some additions to graphic screens are being done with ActiveX Controls.  The only one being used for these additions is 'SECValueDisplay Control'.  Each graphic already has several of these ActiveX controls.  After a copy and paste of an existing one, a right-click to go to Properties returns no pop-up box.  There is no way to modify the copied (or existing) ActiveX controls. When clicking on the wizards hat in the toolbar, the ActiveX Controls are missing from the list (see below). Product Line TAC IA Series Environment Wonderware for Intelligent Buildings (WIBS) version 1.1 Cause Support for the ActiveX Controls specific to the 10 starting with "SEC..." is disabled. Resolution To restore the proper settings for ActiveX Control support, follow the steps below. Find to the Wizard/ActiveX Installation setting (see image below). Select all ActiveX controls that start with "SEC...".  There are ten in total (see image below).  Use the CTRL key to make multiple selections. Click the Install button and all ten ActiveX controls appear above in the "Installed ActiveX controls" area. Close the window and now a Properties screen appears allowing for modifications.

Issue Access Expert is able to communicate down to the SSC (a reboot works) but the SSC won't come online and its status shows as unknown. Product Line EcoStruxure Access Expert Environment SSC Cause In IIS the binding has been configured incorrectly. (On Premise ONLY) Mercury port (3001) blocked.  Resolution This is what a properly configured binding looks like. (On Premise ONLY) Reference How to verify ports needed for AX-SSC communication with the Access Expert server are open from within the AX-SSC itself to check status of the Mercury port, if block work with IT department at the site to have it unblocked.

Issue How to create a successful LDAP Query on Version 3. Product Line EcoStruxure Access Expert Environment Win 10 and above Version 3 Premise Hosted Cause There are no instructions on how to create an LDAP Query to bring in users from Active Directory.  Schneider Electric does not normally write the queries as these are duties more geared to a LDAP person or IT person who is familiar with the structure of the AD. Resolution The following steps are needed to create a successful LDAP Query: Make sure the LDAP appliance or Service is running and that the default port 389 is opened From Access Expert, select the General Configuration Tab and then the LDAP Agents Once opened, create a new LDAP Query by entering all the necessary fields and information to connect to the AD (Active Directory) Enter the mapping fields in the Set Person Mapping fields When Finished click on the Save button that will run the query Select the Access Control Tab and click on the List Icon If the query was successful, then all the users that the LDAP Query was based on will be displayed If it was unsuccessful, then it would be blank.  To troubleshoot any issues, connect to the appliance if possible and browse to the SEQ Folder Open up the Browse SEQ Look at what is displayed on the window to determine what the issue could be Click on the Error on the Right Side of the Window to bring up the Error Messages View the error and correct accordingly (for the most part it is probably the query having extra spaces) Once corrected, re-run the query and verify that it updated correctly by following step 6 again

Issue Communicating with a controller via its LAN connection, is not possible when connected to another controller's service port. Product Line Satchwell Sigma Environment Sigma all releases Sigma all firmware versions. Cause The Sigma system is not complete, messages generated by the controllers cannot be sent to the Sigma server and therefore build up in the Alarm Buffers, this can prevent communications with other controllers.. Resolution If a system is to be left without access to the backup/default Sigma server, then the following actions should be taken: Do not programme any object alarms. Do not configure any system logging. Unless the network configuration allows access to all the appropriate controllers, do not configure globals. Create an "Archive" of the controller. If the time period without the Sigma server is to be less than 5 days, then it is possible to "Set Controller Mode". To set the controller mode, go to System Diagnostics, then Options for the appropriate controller number, and then chose "Set Controller Mode". The following options are displayed. Select the items you wish to inhibit, and set the time in minutes, (a maximum of 7200 can be set).

Issue With the "Apply initial value" property activated in a script program, there may be confusion on how this impacts the operation of the program after a cold start of the controller, which includes system upgrades. Product Line EcoStruxure Building Operation Environment Script Programs Cause In SmartStruxure versions up to and including 1.9.X, when the “Apply initial value” property of a script program is set to Yes, then the following scenario will occur upon a cold start of the server; The inputs, outputs, and public numerics will revert to the initial values set in the script program. Note: It is important to keep this in mind before upgrading a site that has script programs in the database. If the “Apply initial value” setting is Yes, then the Input, Output, and Public Numerics will be re-initialized with their Initial Value attribute. Depending on whether these attributes were configured and/or the application, upgrade or cold start may result in data loss or unexpected behavior. Resolution Versions up to and including 1.9.X If the values of public numerics need to be retained after a cold start in a script program: The "Apply initial value" property must be set to No. Outcome after a Cold Start: Inputs and Outputs will go to null Public Numerics will retain their last known value   If the values of the public numerics need to go to their configured initial value: The "Apply initial value" property must be set to Yes. Outcome after a Cold Start: Inputs and Outputs will go to their configured initial value Public Numerics will go to their configured initial value   Warning: If "Apply initial value" is set to No, it has been observed in upgrades to version 1.9 that some public numerics do not retain their last known value. The fix for this issue has been assigned to EBO 2.0.

Issue Upgraded Site to Continuum 2.01, now get %N and %D in Alarm Message as seen in the message field in the snapshot below: Product Line Andover Continuum Environment Cyberstation Keywords %D %N Cause This is caused by the Enhanced Alarm Logging and Enhanced Alarm Delivery being unchecked Resolution This can be resolved by using the following steps: Close all the cyberstations Initialise the database making sure you have Enhanced Alarm Logging and Enhanced Alarm Delivery ticked as shown below:  

Issue Offline alarms received from Continuum controllers every few minutes and log error 0x00006c0e Broadcast Storm AKA Error transmitting and/or 0x00006c03 Driver fatal error during operation. Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 4 Controller Continuum CX Gen 1 Continuum bCX4040 Continuum bCX9640 Continuum BCX4000 Cause Excessive ARPs and/or other broadcast traffic on the network. Resolution When troubleshooting controller offline issues that are suspected to have excessive broadcast traffic as the root cause it is important to understand how to interpret Wireshark capture to determine whether too much broadcast on the VLAN  is indeed the problem. Note that taking the percentage of broadcast traffic in a Wireshark capture while a good starting point cannot in itself be solely used as proof that excessive broadcast is indeed the root cause of the controllers going offline, this is because in the absence of much unicast traffic the broadcast traffic will make up most of the packets resulting in a misleading high percentage. A much better way to determine whether the controller maybe going offline due to excessive broadcasts is to look at the average broadcast packets per second over a 15-20-minute capture. The screen capture below shows the statistics from a 20 minute capture filtered by broadcast traffic (eth.dst == ff:ff:ff:ff:ff:ff)  The capture shows that about 63% of the traffic is made up of broadcast at an average of 24 packets per second. The Continuum controllers on the network were going offline multiple times an hour. Note that the Continuum controllers are initially able to handle a much higher rate of broadcast traffic, tests performed in the PSS lab show a CX9680 can handled about 10 times  the amount shown here sustained for 5-10 minutes but over a much longer period of time such as several days or weeks the amount of broadcast traffic shown was enough to cause the controllers  to go offline. The screen capture below shows the statistics after the root cause of the excessive broadcast was identified and fixed. The problem at the site in question here was a defect in the network switch that was making the switch duplicate ARP traffic. Note that Cisco switch model Catalyst 4500 is also effected by the firmware bug. Current version which fixed the issue: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.05.E RELEASE SOFTWARE (fc2)   Previous version which caused the broadcast problems: Catalyst 4500 L3 Switch  Software (cat4500e-UNIVERSALK9-M), Version 03.08.02.E RELEASE SOFTWARE (fc2)

Issue When a Sigma data import is carried out, the following messages are displayed on the SBO ES computer. On the Sigma server computer, the Sigma server service has stopped. Product Line EcoStruxure Building Operation Environment Sigma 4.08 Building Operation Workstation Building Operation Enterprise Server Cause The Sigma database’s longtext file contains unsupported characters. Resolution Option 1: If Sigma longtext is no longer required: On the Sigma computer. 1)      Stop the Sigma server service. 2)      Delete the longtext.rec file from the Sigma Data folder (C:\Sigma\Data\longtext.rec). 3)      Start the Sigma server service. On the SBO computer Carry out the data import again. Option 2: If Sigma longtext is required: On the Sigma server computer. 1)      Start the Sigma server service. Open a Sigma client, either on the Sigma server computer or the SBO ES computer or other. 1)      Log into Sigma’s operator panel 2)      Go to the System Alarm manager 3)      Under the menu “Configure” select Longtext 4)      Open each longtext entry and remove the unsupported characters 5)      Add the longtext message your require. (You may find copies of the original longtext messages you can copy the text from, under “C:\Sigma\Data\Longtext” used by Sigma before the system was upgraded. On the SBO computer 6)      Carry out the data import again.   The data import should now complete.

Issue The STR-150 Installation Instructions state that the stat wires into D1, X1, and M of the Xenta 100 series controller. However, this is not applicable to the Xenta 121 and 122, which does not have a D1 input. Product Line TAC Vista Environment Xenta 122 STR-150 Cause The correct terminal for the mode input from the STR-122 is labeled differently on the Xenta 122 versus all other Xenta 100 series controllers. Resolution Wire the stat as follows: STR-150 Xenta 122 Label Terminal Label Terminal Mode 11 Y1 5 Data 12 X1 7 M 13 M 9 If you are looking for the wiring diagram for an STR-150 into a Xenta 121 the click here. The Purpose of output Y1 The only function that the STR-150 uses Y1 for is to get an effective occupancy signal from the Xenta 122. When the Xenta 122 is occupied, the man symbol will be displayed on the STR-150. If Y1 is already in use then the Status LED can be moved to a K output as explained is it possible to use an analog valve on the TAC Xenta 121-FC/HP and still have the effective occupancy active on the STR-150?. In order to activate this feature, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. If this feature is not desired then unselect Hardwired status LED and only wire up X1 and M. The STR-150 will still be able to send the controller the temperature, setpoint, bypass signal, and fan speed.

Issue Opening Controller Web Pages (such as those hosted by a bCX) using an external browser,  generates a 'pop up window' where you must enter authenticating credentials (username and password) before access to the controller's various settings is granted. . Using an ES, AS or AS-P Hyperlink however you can log onto to the bCX Main page, but when selecting any option from the menu, you do not see this 'pop up window' to enter your credentials and are instead greeted with an immediate Access Denied message Product Line EcoStruxure Building Operation Environment External web pages and/or controller web pages Cause Technically speaking the 'popup window' is a Frame within the web page which web servers of this kind commonly use.   Unfortunately, the ES, AS and AS-P do not easily handle such Frames or i-Frames and as such logging on becomes complicated. Resolution There is usually as single Frame which handles the Authentication which can be identified looking at the web server (in this case bCX) web page via Chrome + F12 which puts it into Developer Mode.    In this case if you allow the Authentication Frame to open in Chrome and then select cancel the Access Denied message is seen and Frame B4000MainMenu is highlighted Which can then be tested using that specific Frame in Chrome to be sure it does indeed cause the authentication window to appear every time. Once you know that this is the Frame which generates the Authentication you can create a logon Hyperlink in SBO which directly opens this Frame only After entering the correct log on credentials, you can then use a second SBO Hyperlink that connects to the Main web page of bCX and navigate to where ever you need to make changes.  CAUTION:  This authorisation will then remain active allowing access to bCX settings for anyone using that Workstation until the Workstation Session is closed (logging off is not enough)  

Issue Access Expert V2 configured MR52 Interface with inputs and outputs showing as Not attached (See snapshot) Product Line EcoStruxure Access Expert Environment V2 SSC MR52 Interface Cause The MR52 interface was previously configured with elevator controls but now has been detached in some manner. Resolution Remove the configured elevator references on each input and output individually and resave the point. Delete and re-add the points and configure the I/O as needed.  V3 works differently then V2. V3 allows for a more granular configuration so that the I/O selection just allows for the specific elevator other I/O selections. In V3 the assignments doesn't need to be released, only reselected.

Issue What is the procedure for adding an MR52 to a system. Product Line EcoStruxure Access Expert Environment Access Expert in Cloud or Premise Microsoft Windows 7, Windows 8, Server 2012, Server 2014 Cause Unable to find documentation of the installation process for the MR52. Resolution In order to add an MR 52 sub device to an SSC, the following steps need to be followed:   1. Address the board with proper address via dip switch settings (address switches should be pointing to the numbers on the board) 2. Power up the device and verify that LEDS are displaying correctly 3. Once the controller is Online, click on Add Interface 4. Open up the Live Monitoring Window to check the status of the controller 5. If the devices show offline, Right Click on the controller and select Reboot 6. The Live Monitoring Window will show what is actually being sent to the controller 7. Once completed the status will change to reflect what state the controller is in 8. If correct it will be Online (Green), if not check the configuration and/or wiring again

Issue Issues resizing SBO graphic editor frames with Windows 10 Lenovo P51 or T470 laptop with a Schneider Electric image. The following picture shows that the Graphic Editor did not re-filled the screen after resizing either the component/snippet area or the Object/property area, a border can be seen to the right and below the editor’s frame. Product Line EcoStruxure Building Operation Environment Lenovo P51 or T470 Schneider Electric imaged laptop. Cause Scale and layout: Microsoft .NET Framework version: Resolution 1. Scale and layout: Right mouse click on the desktop and select “Display settings” Set Scale and layout to 100% Re-boot computer   2. Microsoft .NET Framework 4.7.2: Download and install Microsoft .NET Framework 4.7.2 (Microsoft .NET Framework 4.7.2. can be downloaded from the Microsoft support site) Re-boot computer If these suggestions do not provide a solution or if you would like to provide some other feedback, please contact your local product support entity

Issue When the Ethernet is removed from an AX-SSC controller, all of the devices underneath that controller inexplicably lose their connection to the controller. Product Line EcoStruxure Access Expert Environment AX-SSC Cause The firmware of the SSC is outdated. Resolution The firmware of the SSC needs to be upgraded to version 24.01.241 or newer. This can be accomplished with the following procedure:   1. From Access Expert (the firmware of the SSC can only be updated within Access Expert, not from the Device Administrator), select the "Hardware Provisioning" tab. 2. Click "Controllers", and then select the correct SSC controller. 3. Under "General Info" verify the "Reported Version Number". If less than 24.01.241, the firmware needs to be updated. Click "Update Firmware".

Issue Unable to locate where to configure the SMTP Server in an Acess Expert V3 Instance. Product Line EcoStruxure Access Expert Environment V3 Premise Cause The earlier versions of the on-premise server/client did not have SMTP functioning properly. As a result, the tab to Configure the SMTP server settings was left out of the software. Resolution Newer versions of the software have SMTP functionality working properly. After upgrading the Server and Client software to the newest versions available, the SMTP Configuratiuon tab will be available as shown below.  Note: For Instructions on how to upgrade the Premise Server and Client software, please see Upgrade Premise Software to Latest Version.

Issue The Drayton Theta YBL1A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBL1A Cause The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBL1A Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBL1A Valve Body the following is required:- S-E SatchwellMB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT (6-WIRE INSTALLATION) The YBL1A Actuator normally comprised a 6-wire electrical connection enabling it to be operated by a Theta Potentiometric Controller as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  Terminal M4 – 135 ohm Feedback Potentiometer – winding Terminal M5 – 135 ohm Feedback Potentiometer – wiper Terminal M6 – 135 ohm Feedback Potentiometer – winding Where 6 wires are connected to the YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here   IMPORTANT NOTE In such 6-wire installations not only will the YBL1A Valve / Actuator assembly need to be replaced but the associated Theta Potentiometric Controller and its Sensors will also need to be replaced.   CONTROLLER REPLACEMENT The Theta Potentiometric Controller may be replaced by the S-E Satchwell CSC5252 or the CSC5352 Compensator Controller. Details of the CSC Controllers may be viewed here.   SENSOR REPLACEMENT Theta 3-wire Temperature Sensors may be replaced by S-E Satchwell 2-wire Temperature Sensors compatible with the S-E Satchwell CSC 5252 or CSC5352 Compensator Controllers selected from the following as appropriate. Outside Air Temperature Sensor (STO 600) Contact Temperature Sensor (STC 600), or alternatively :- Immersion Temperature Sensor (STP 660) + Sensor Pocket Adaptor (DWA 0001) Room Temperature Sensor (STR 600) – OPTIONAL ONLY Details of the STO 600 Outside Air Temperature Sensor may be viewed here. Details of the STC 600 Contact Temperature Sensor may be viewed here. Details of the STP 660 Water Temperature Sensor may be viewed here. Details of the DWA 0001 Sensor Pocket Adaptor may be viewed here. Details of the STR 600 Room Temperature Sensor may be viewed here.   N.B. ACTUATOR REPLACEMENT (3-WIRE INSTALLATION) Should only 3 wires be connected to a YBL1A Actuator then the Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-24 MD20B-24 (if MD10B-24 not available) Details of the MD10B-24 Actuator may be viewed here. Details of the MD20B-24 Actuator may be viewed here. N.B. The YBL1A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :-  Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBL1A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBL1A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue Having difficulties integrating an SED-T stat with the MPM (Stat not being "learned" by the MPM) Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager SED-T00 SED-TS0 SED-TH0 SED-THS Cause Installation manual does not provide enough information Resolution Commissioning tips and recommendations   Dip Switches: SED-T series stats come directly from production with all dip switches set to 0. The dip switches settings must be changed otherwise the device will not send any telegrams. Tip: When pairing an EnOcean Temperature Sensor with the MPM, always set at least one pin of the DIP switch to the ON position before learning it in. Otherwise the MPM will not display any readings regardless of dip switch configuration even if the Enocean ID had been populated in the EODC object. The workaround at this point would be to click on the learn button again, the device will be learned successfully when the “RSSI” value and a “Last Communication” time stamp are displayed.   Example on how to use the dip switches: If the dip switches are set to 1= OFF, 2 = ON, 3 = ON, 4 = OFF, the stat would wake up every 10 seconds and take a look at the values. if they changed, the stat will send a new telegram with the new value. if the value did not change however, the stat will go back to sleep until the next 10 seconds elapse (first iteration). If the value did still did not change before the 7th iteration, then the stat will randomly send a telegram with the unchanged value at any time between the 7th and the 14th iteration. that is a minimum of 10*7 = 70 seconds and maximum of 10*14 = 140 seconds.   Solar cell: When removing the unit from the box for the first time, its energy banks (super capacitor) need to be charged using one of the methods below in order to be able to learn the device. A minimum of 2.1VDC is required before the stat can wake up and send a telegram and Ideally, the Super cap voltage should be between 4 to 5Volts. Method 1: Power the sensor with 24VAC for 1 hour (3volts/hour) Method 2: expose the solar cell to light for x amount of time depending on the light source: 1- Room with LED panels: 24hr minimum charging time (0.1Volts/hour) 2- Lit room with day light: 3-4 hours minimum charging time (0.7Volts/hour) 3- Direct sunlight: 1/2 hour minimum charging time (3.5Volts/hour)   Battery: The 20mm coin cell battery does not charge the super capacitor, however it slows down the depletion of super capacitor once its charge drops below 2.1Volts.

Issue When you're having issues with Continuum you need to check if the Windows account you are logging on with is part of the Local Administrators Group. Product Line Andover Continuum Environment Windows XP Windows Vista Windows 7 Windows 2008 Server Continuum 1.9X Cause Permission issues running or installing Continuum 1.9X Resolution Download the attached TestUserAdmin.zip file unzip the TestUserAdmin.exe file to your Desktop Open the Command window (DOS prompt) and run the TestUserAdmin.exe  The program will indicate if the logged on Windows user is a member of the Local Administrators Group or not.  

Issue No license is available for Vista Webstation Webstation installation issues ASP.NET Authority issue Product Line TAC Vista Environment Vista Windows 2003 Windows 7 Windows 2008 R2 Cause Sometimes it is not enough to let ASP.NET be run by NetworkServices. The user LocalSystem needs to be used instead. Resolution Windows 2003:  Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Expand application Pools Right click on  "SE ASP.NET v4.0 Classic" and choose Properties. Under "Identity" choose user "LocalSystem" from the Predefined drop list. Click OK and restart webstation. Windows 7: Right click on my Computer and choose "Manage" Go to Services and Application Click on Internet Information Services Click on application pools Right click on  "SE ASP.NET v4.0 Classic" and choose Advanced settings Under "Identity" choose user "LocalSystem" Click ok Restart webstation Windows 2008R2: Go to Start and administrative tools. Click Internet Information Services (IIS) Manager. Click Application Pools under the serve Right click on SE ASP.net v4.0 Classic and choose Advanced setting. See attachment IIS manager 1 Click the button beside Identity under the process model. See attachment IIS manager 2 Change the built-in account from networkservice to LocalSystem. Click OK and restart the webserver in Internet Information Services (IIS) Manager. If the problem persists, please see Problems installing Vista Webstation 5.1.5 or newer for additional helpful information.

Issue Can't communicate with more than 1 device on LG Gateway at the same time. Updated with solution on 12/15/2017 Product Line EcoStruxure Building Operation Environment LG Gateway Model:PQNFB17C1 Firmware version: 1.11.4 Cause The gateway can only provide one source address when there are multiple device IDs. The wireshark capture confirmed that no unique source ID provided by the gateway with different device IDs. Resolution Update the firmware version to 5.08.1h Configure the "BACnet Type Setting" to "B Type".