Building Automation Knowledge Base

Issue Preparing LonWorks Configurations for Upgrade You use this procedure when you want to prepare LonWorks configurations for a version 1.5.x upgrade, a version 1.6.x upgrade, or a version 1.8.x upgrade to a final 1.9.X or Higher version. WorkStation ONLY hotfixes are needed to Prepare the LonWorks configuration in order to upgrade to an SBO system 1.9.X or higher. Links to locating hotfixes on Exchange are needed. Product Line EcoStruxure Building Operation Environment SBO Workstation Hotfix Only v1.5.0.17121 SBO Workstation Hotfix Only v1.6.2.1220 SBO Workstation Hotfix Only v1.7.2.11111 Note: AS-P HW.62 required for a LON system with a minimum SBO Software revision at 1.7.2.X Note: For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 -Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 Cause Difficulties experienced in locating these files on the Exchange. Resolution Prepare LonWorks Systems Running Version 1.5, 1.6, or 1.7. For Systems that are running SBO Software Revision 1.8.X please follow TPA-SBO-17-0002.00 - Server with LonWorks devices - Important software update - TPA-SBO-17-0002.00 SBO Workstation Hotfix v1.5.0.17121 - Contact Country Level PSS SBO Workstation Hotfix v1.6.2.1220 - Contact Country Level PSS SBO Workstation Hotfix v1.7.2.11111- Link To prepare LonWorks configurations for upgrade via the WorkStation Only Hotfix: Bring the system up to the base version within your respective site to SBO V1.5, 1.6.2, or 1.7.2. Then apply the WorkStation Only Hotfix from the list above to your respective version. 1. In WorkStation, in the System Tree pane, select the EcoStruxure BMS server you want to prepare for the upgrade. 2. On the File menu, point to LonWorks and click Pre-upgrade LonWorks configuration. 3. Click Next. 4. Click Finish. NOTE: Any EcoStruxure BMS that is currently at 1.8 or higher can be upgraded directly to 3.1 with one added note,  if the system has LON it will need to go through the LonWorks Pre upgrade before you can upgrade to 1.9.X or HIGHER. If you are upgrading from a version that is older than 1.8, read the documentation that describes the upgrading process for the relevant version.

Issue How to use bit masking to decode on/off states from a Modbus analogue registers e.g. Holding or Input registers. Where each bit is required to be read individually to indicate the status of a coil. Product Line Satchwell Sigma Software Environment Sigma IC Modbus and IC3 Modbus controllers Cause Configuration technique to read 16-bit Modbus registers for on/off states. Resolution Each modbus holding or input register is 16 bits, where each bit can be on or off i.e. 0 or 1. For example the Sigma analogue input value of 901 represents the state of a number of coils where each bit indicates the on or off.  Hence, this translates to the 16-bit binary value  0000001110000101  where 1 = on and 0 = off Create a Sigma analogue input object to read the Modbus value. Click here for the  Sigma Modbus 4.06 release Note Create a programmable object for each of the required bits (max of 16 for each register) to be read as below.  (Highlight, copy and paste into each programmable object). For Example starting with the Least Significant Bit (LSB) and where point 0|222 is the Modbus value created, the programmable objects are; Bit 1 (LSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1 ) 30 IF YINT = 1 THEN RETURN TRUE "Bit 1 = on" 40 RETURN FALSE "Bit 1 = off" Bit 2 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2 ) 30 IF YINT = 2 THEN RETURN TRUE "Bit 2 = on" 40 RETURN FALSE "Bit 2 = off" Bit 3 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4 ) 30 IF YINT = 4 THEN RETURN TRUE "Bit 3 = on" 40 RETURN FALSE "Bit 3 = off" Bit 4 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8 ) 30 IF YINT = 8 THEN RETURN TRUE "Bit 4 = on" 40 RETURN FALSE "Bit 4 = off" Bit 5 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16 ) 30 IF YINT = 16 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 5 = off" Bit 6 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32 ) 30 IF YINT = 32 THEN RETURN TRUE "Bit 6 = on" 40 RETURN FALSE "Bit 6 = off" Bit 7 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 64 ) 30 IF YINT = 64 THEN RETURN TRUE "Bit 7 = on" 40 RETURN FALSE "Bit 7 = off" Bit 8 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 128 ) 30 IF YINT = 128 THEN RETURN TRUE "Bit 8 = on" 40 RETURN FALSE "Bit 8 = off" Bit 9 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 256 ) 30 IF YINT = 256 THEN RETURN TRUE "Bit 9 = on" 40 RETURN FALSE "Bit 9 = off" Bit 10 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 512 ) 30 IF YINT = 512 THEN RETURN TRUE "Bit 10 = on" 40 RETURN FALSE "Bit 10 = off" Bit 11 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 1024 ) 30 IF YINT = 1024 THEN RETURN TRUE "Bit 5 = on" 40 RETURN FALSE "Bit 6 = off" Bit 12 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 2048 ) 30 IF YINT = 2048 THEN RETURN TRUE "Bit 12 = on" 40 RETURN FALSE "Bit 12 = off" Bit 13 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 4096 ) 30 IF YINT = 4096 THEN RETURN TRUE "Bit 13 = on" 40 RETURN FALSE "Bit 13 = off" Bit 14 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 8292 ) 30 IF YINT = 8292 THEN RETURN TRUE "Bit 14 = on" 40 RETURN FALSE "Bit 14 = off" Bit 15 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 16384 ) 30 IF YINT = 16384 THEN RETURN TRUE "Bit 15 = on" 40 RETURN FALSE "Bit 15 = off" Bit 16 (MSB) 10 XINT = INT POINT 0|222 20 YINT = XINT MASK ( 32768 ) 30 IF YINT = 32768 THEN RETURN TRUE "Bit 16 = on" 40 RETURN FALSE "Bit 16 = off"

Issue CSC5252 and CSC5352 Climatronic Compensator Controller will not display Room Temperature.  Environment Satchwell CSC5252  CSC5352  Climatronic Compensator Controller  Room Temperature.  Cause CSC5252 and CSC5352 Climatronic Compensator Controller may not display Room Temperature for the following reasons :- 1.  No Room Temperature Sensor installed. 2.  Room Temperature Sensor installed but ROOM INFLUENCE MODE default value in CSC Controller has not been amended.. .  Resolution CSC5252 and CSC5352 Climatronic Compensator Controller may be set to display Room Temperature as follows:- 1.  Ensure Room Temperature Sensor is installed and connected to CSC Controller Room Temperature Sensor Input terminals. 2.  Ensure ROOM INFLUENCE MODE (INF) setting in CSC Controller Fine Tune Mode is set to value = 1 N.B. Sensor connection details and the means of entering and exiting the CSC Controller Fine Tune Mode both appear in the Climatronic CSC5352 and CSC5252 Compensator User Guide, a copy of which may be viewed here.

Issue MP-V Air Flow is reading zero flow despite the Velocity Pressure having a positive value. Product Line EcoStruxure Building Operation Environment MP-V-7A, MP-V-9A, RP-V-4A, RP-V-5A Variable Air Volume Data Cause The Air Flow value is an internally calculated value based on the Velocity Pressure. There are a number of values involved in that calculation that could result in no flow. Resolution Validate Variable Air Volume Data > Flow Balance Data > Rated box flow. The rated box flow defaults to 0 ft³/min in a new controller and must be replaced with the rated flow at 1.0inH₂O (provided by the box manufacturer). Compare Variable Air Volume Data > Velocity Pressure > Value to the Zero flow threshold. Any Velocity Pressure below the threshold will result in no flow. This threshold defaults to 0.008inH₂O. Check Variable Air Volume Data > Properties > Balanced k-factor and Balanced flow correction factor. If either of these values are at 0, there will be no flow. These values cannot be directly written to and are only the result of a flow balance calculation. To get them to update: Go to Variable Air Volume Data > Flow Balance Data and record all balancing data (you will need to manually re-enter it later). Set all 7 balancing values to 0 - Rated box flow, Box/Hood measured maximum/intermediate/minimum Right-click on Variable Air Volume Data and Download Re-enter the valid balancing data. The balanced k-factor should now show a value close to the rated box flow and the balanced flow correction factor should show a multiplier ideally between 0.5 and 2. If the box has not been balanced and no valid balancing data is available, leave the minimum flow readings at 0 and enter the same value into both the hood and box maximums (for example, 1000 and 1000). This will result in a balanced k-factor equal to the rated box flow and a balanced flow correction factor of 1.

Issue Issues being experienced can vary, here are some examples: The digital clock gains a minute every few seconds. The code (0112) when entered to accept alarms, is not accepted. Environment DC1100 controller DC1400 controller Cause The unit has not been correctly cold-started after first being powered on. Resolution The DC1100 / DC1400 controllers must be correctly cold-started after first powering up, this ensures that the default configuration is correctly installed. Cold-start the controller using the following process: Turn off the power to the controller. Press and hold in the ENTER and EXIT keys. Power up the controller whilst continuing to press the ENTER and EXIT keys. Release the ENTER and EXIT keys. The controller will now go through a self test programme and load its defaults. To review the DC1100 / DC1400 controller overview, select here To review the DC1100 controller general data sheet, select here To review the DC1100 controller installation, wiring and Commissioning information select here To review the DC1400 controller general data sheet, select here To review the DC1400 controller installation, wiring and Commissioning information select here

Issue How to filter in a listview AlarmEvent based on the EventNotification Environment Continuum Cause Continuum pre 1.91 did not allow filter in a listview AlarmEvent, based on the EventNotification Resolution See Continuum CyberStation Release Notes Version 1.91(Downloadable here) Fixed Problems 4.007 Cannot filter an AlarmEvent table based on the EventNotification using the query wizard (21101) Find another way to filter or upgrade your version of Continuum.

Issue Troubleshooting controllers can be aided by observing the CPU light Product Line Andover Continuum Environment Continuum controllers Cause A video created to show the differences between Normal, Error and Bootloader modes Resolution This will not show specifically what mode the controller is in, but it can offered to try to help to determine the mode. The speed of the CPU light on some of the controllers may vary, but this gives a general idea. Normal Mode is on the left, Error Mode is in the middle and Bootloader Mode is on the right. Note if the CPU LED is constant on or off see the KB article - Continuum controller CPU light solid or not illuminated

Issue StruxureWare Building Operation uses the old PI-Modbus-300 protocol Environment StruxureWare Building Operation using Modbus protocol Cause Does StruxureWare Building Operation use the MODICON protocol with the reference PI-MBus-300? Resolution Modicon was purchased by Groupe Schneider (which eventually became Schneider Electric) in 1996, way before Schneider Electric bought TAC. The PI that referred to is just a prefix of the technical document describing the Modbus communication protocol. The 300 is the version of the protocol. StruxureWare Building Operation supports a subset of the Modbus protocol. StruxureWare Building Operation does not support all Functions defined by the document specified. Modicon is still the only one that does.

Issue What is the maximum number of registers that can be read/written using the multiple read/write function codes in Modbus Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Modbus Register Groups Cause When deciding how to group registers using a Modbus Register Group, what are the maximum number of registers that can be grouped. Resolution There is a limit to the number of packets that can be polled in a single packet, however, if this number is exceeded then two or more polls will be made (blocks).  The nominal Read multiple registers maximum is 125 16 bit registers (250 8-bit bytes, so the register count will vary for 32 and 64bit polls).  The Register Group Properties Tab shows the number of blocks being polled. The Modbus register grouping function has a direct effect on system performance. A poorly grouped device can easily increase the overall poll time as points, or blocks, in each Modbus network are polled sequentially.  See the section "Batch Read Function" in the EcoStruxure Building Operation Technical Reference Guide for full details. Note: Multiple group writes are not possible and are not controlled via Modbus Register Groups.  

Issue How to get answers for project specification responses or how to get a product enhancement implemented. Product Line Security Expert, EcoStruxure Building Operation Environment Security Expert EcoStruxure Building Operation Cause Unsure who to go to for help with specification replies or how to get a potential product enhancement added to the offer. Resolution Create an idea on The Exchange Community for your specific Offer. The more Likes an idea floated on the Community receives, the more attention it is given by offer management for that associated product line. Even if you do not yourself have an Enhancement Request, help raise the profile of others by Liking theirs Contact your local solution category manager for the Offer as they will be able to point you in the right direction for answers to specification questions and can help escalate enhancement requests to Product Management. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com When providing your feature request make sure to include as much detail as possible about the feature as well as any specifics that might help justify the need for the new feature.

Issue How to reset an NC2 9680 model controller Environment CX 9680, NCII, NC2 Cause While upgrading/downgrading the controller firmware, communications was lost and the controller was not able to communicate afterwards.   Resolution Reset controller and re-commission. Please click here for document on how to reset the CX9680 controller.

Issue Security Expert client Status Window is not showing live point status for inputs, outputs, doors. Shows an error message “Status Unknown” instead. The client is still however able to receive access control events such as reader entry/exit. Product Line EcoStruxure Security Expert Environment Security Expert Cause MSMQ (Microsoft Message Queueing) is not enabled. This is a requirement for MSMQ to be installed on the Security Expert Server, the Security Expert Client machines do not need this but the machine where the Security Expert Services are installed does need this feature installed to function properly. Resolution Windows 10 In Windows Features settings (Turn Windows features on or off) turn on the “Microsoft Message Queue (MSMQ) Server” and the “Microsoft Message Queue (MSMQ) Server Core” features. Windows Server 2016 or above  Start Server Manager. Select Manage / Add Roles and Features. Click Next. Select Role-based or Feature-based installation Click Next. Select the server where to install the feature. Go to Features, and navigate to Message Queuing / Message Queuing Services and select Message Queuing Server. Click Install to start the installation. The setup may require a system restart. Click OK to finish.  

Issue Not all 3rd party manufacturers use the same Modbus addressing. Product Line Andover Continuum, EcoStruxure Building Operation Environment Modbus RTU X Driver bCX1, CX controllers, NC2 Building Operation Enterprise Server Building Operation Automation Server Cause Not all manufacturers use the same Modbus addressing. Resolution Many manufacturers have put their own slant on the "Modbus Standard" for addressing and number formats. The standard only defines 16 bit integer and binary data, but many manufacturers needed to use long integers (or swapped) and floating point numbers. They will transmit them as 2 integers over the protocol, then the receiving system needs to interpret them accordingly. To cope with this, special function codes were added which cover most formats. There are various interpretations by different 3rd party systems on addressing. Some number from 0 and others starting at 1. Some require a 30000 or 40000 offset including in the address, depending on I/O type. What is implemented in the X Driver is that whatever decimal address you enter in the X Driver point is what is sent down the bus. If the other system supplier is asked exactly what address they want sent down the bus, that is what is required in the X Driver point. Sometimes this is not the address that is on their datasheets. Sometimes there may be a need to add or subtract a value of 1, 30000 or 40000. This article was written for Continuum, but is still relevant to EBO Also see Helpful Modbus register Information for further information on Modbus registers.  

Issue Where can you obtain the Database Schema for the EBO WebReports / Report Server Database Product Line EcoStruxure Building Operation Environment Building Operation Report Server Cause From EBO version 3.2.x WebReports/RS is no longer being developed as we move to External Log Storage with Postgres and Timescale DB.    To allow our customers to continue to work with existing WebReports/RS databases if they so wish, it may be helpful to provide the DB Schema. Resolution An inbuilt Report already exists within WebReports call 'Database Schema' which allows you to select which Tables you would like to see in the WebReports / RS Database Running this will produce a .pdf Report detailing the RS Database Schema tables, to aid with 3rd Party integrations and other DB manipulation. A full database schema report is attached for reference (Version 3.2.3) 

Issue In an MP-V controller, Box flow is reading air flow when the VAV damper is closed Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose VAV FW v2.00.01.00016 Building Operation Workstation (Version 2.0.x or later) Cause Confinguring the MP-V Box Flow Zero Point WebHelp article in Building Management System WebHelp is missing steps needed for MP-V with firmware version 2.00.01.00016. Resolution In addition to the procedure described in Configuring the MP-V Box Flow Zero Point, two additional steps are required to zero the Box flow on an MP-V using firmware version 2.00.01.00016. Under Flow Balance Data... The Box Measured maximum flow must be an appropriate value based on the box size.  The Hood Measured maximum flow must be an appropriate value based on the box size. Once the procedure in WebHelp is followed and these to settings are configured, the Box Flow will read zero when the Velocity Pressure is below the Minimum value setting in Velocity Pressure properties.   If the Box Flow is still a non-zero value: While the damper is closed, put in an offset value to counter the Box Flow Make sure that the minimum value setting is a small positive value ex/ 0.002

Issue Where can I find information on LCX89x controllers. Environment LCX89x LCX890, LCX898 Cause While LCX89x controllers are being sold by Schneider Electric as of April 19, 2013, there is not a lot of information on the LCX line at the Extranet website. Resolution Series LCX 890 Infinet Controllers       Part Number Description     01-0008-036 LCX 890 Lighting Controller, 8 outputs w/RR9 relays     01-0008-037 LCX 890 Lighting Controller, 8 outputs no relays     01-0008-039 LCX 891 Lighting Controller, 16 outputs w/RR9 relays     01-0008-040 LCX 891 Lighting Controller, 16 outputs no relays     01-0008-042 LCX 892 Lighting Controller, 24 outputs w/RR9 relays     01-0008-034 LCX 892 Lighting Controller, 24 outputs no relays     01-0008-081 LCX 898 Lighting Controller, 48 outputs no relays     01-0008-083 LCX 898 Lighting Controller, 48 outputs w/RR9 relays   LCX890 Series Controller Installation Guide

Issue EcoStruxure Building Operation WorkPlace Tech Editor Supported Microsoft Visio Versions The following error context is encountered when trying to run WorkPlace Tech Editor to edit a program: WorkPlace Tech Editor returned errorClass not registered 0x80040154 REGDB_E_CLASSNOTREG Product Line EcoStruxure Building Operation, TAC I/A Series Environment EcoStruxure Building Operation WorkPlace Tech Editor I/A Series MNL, MNB Controllers (MNB - from SBO v1.8.1 and newer) Cause Only the 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. The error is seen when a 64-bit version of Microsoft Visio 2010 is installed. Resolution Currently, only 32-bit versions of Microsoft Visio is supported for use with WorkPlace Tech Editor. SBO 1.5, 1.6, 1.7 Microsoft Office Visio 2010 SP1, 2007 SP2, 2003 SBO 1.8 Microsoft Office Visio 2010 SP1 (32-bit), 2007 SP2, 2003 SBO 1.9, EBO 2.x, 3.x Microsoft Office Visio 2016 (32-bit), 2013 (32-bit), 2010 SP1 (32-bit) EBO 2022 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2023 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit) EBO 2024 Microsoft Office Visio 2021 (32-bit), 2019 (32-bit), 2016 (32-bit), Microsoft Office Visio Plan 2 (32-bit)

Issue Calculation for converting static air pressure to cfm Product Line TAC INET Environment INET HVAC Site Cause What are the calculations for converting static air pressure to cfm? Resolution SRVP ("water column") * 4005 = FPM (feet per minute). The second calculation is FPM * AreaFtSQ (size of box) = CFM You will need an airflow monitoring device and duct static pressure sensor to measure SRV P (v of Vs of P).

Issue Will the Bond Sensor Input Channel contribute to the Door Forced and Door Ajar alarms? If so, does it have to be in conjunction with the Door Switch Input Channel? Environment Continuum Access Control Products CX9900 CX9680 AC1, AC1A, AC1Plus ACX5720, ACX5740 CX9702 ACX781 Cause Not sure how the Bond Sensor works in relation to the Door Switch and the various Door Alarm states. Resolution BondFailure is an attribute of the Door object that represents a fault with the Bond Sensor. The way this works is if Valid Access = True and the Door Switch = Open and the Bond Sensor = Open, then BondFailure = False. If Valid Access = False or the system sees the Door Switch = Closed but the Bond Sensor = Open then you will get a BondFailure = True. This is another attribute (BondFailure) that can be monitored with an AlarmEnrollment in addition to the DoorForced and DoorAjar attributes. A Door Switch needs to be used for the Bond Sensor to operate correctly, otherwise BondFailure will always be False after a ValidAccess if there is no Door Switch value. Note: The actual value of the BondSensor attribute in the Door object may not seem to update properly if monitoring with a ListView. For this to show the correct BondSensor value make sure that the attribute Source is set to "Live" instead of the default "Database". Note2: A bond senor (usually an output from a maglock) should not be used as an alternative to a door switch, as it does not give indication of the door position.  

Issue MNL-800 LON SNVT Programming Standards Environment Workplace Tech Tool software (any version) MNL-800 controller application Cause Problems occasionally arise as a result of improper LON SNVT programming and configuration in the MN-800 device application.  These issues include problems with the re-commissioning of the updated controller and potential network variable mismatch situations. Resolution  The following standards will prevent these problems from occurring. Network variables MUST be manually indexed. This prevents issues with the network variables becoming renumbered when application programming changes are made. (See NOTE 1) Change the application "Program ID" any time network variables are added or removed from an application.  To change the "Program ID" use the WPT Hardware Wizard,  (See NOTE 2) Select Hardware Wizard from Application Menu Click [Next] in MicroNet Setup Wizard screen Change the displayed program ID by entering a different program ID or adding a suffix letter/number. Maximum length is 8 characters. Click [Finish] to save the changed program ID and exit the MicroNet Setup Wizard.  In addition, one method of minimizing the need to repeatedly change the "Program ID" as the application is developed and debugged is to add a few extra common SNVT input and output definitions when first creating the application, leaving them unconnected to the application program.  If one of these SVNTs is needed, it is available in the LON network image (XIF file) and it is not necessary to change the "Program ID". If the MNL-800 controller has firmware version 2.0 (or later) installed, the standard nci network variables do not have to be indexed as the highest numbered SNVTs in the application.  It is perfectly acceptable to number them as the first 17 indexed SNVTs. Note that there are 17 standard network variables (12 nci, 2 nvo & 1 nvi), not just ten nci SNVTs. SNVT variable names should be limited to 16 characters or less.  Longer names are accepted by the WorkPlace Tech programming tool but the names will automatically be truncated by the LON Network Management tool when commissioning the controller. In addition, when programming the MNL-800 applications with the WorkPlace Tech Tool version 5.0, or later, it is not necessary to put each MNL-800 application in a separate project. NOTE 1: If using the WorkPlace Tech Tool version 5.8 or above, you can use the "Object Indexer" to automatically number all the network variables for you.  This tool also includes functions for detecting duplicate SNVT index numbers and for detecting gaps in the assigned index numbers. NOTE 2: If using the WorkPlace Tech Tool version 5.8 or above, you can set an option in the Hardware Wizard to automatically generate a new ProgramID and reindex the network variables when compiling the application.  Please be aware that this automatic generation of the ProgramID will require the Echelon network image for this device to be updated in any Echelon compatible network management tool.  Please refer to the documentation for the network management tool to determine what actions will be required. For example, if Niagara was used to manage the LON network, then the old shadow will need to be deleted, a new one added, and the device points rediscovered and the device re-commissioned.