Building Automation Knowledge Base

Issue The hostId for a computer running I/A Series G3 version 3.8u1 (or earlier) and N4 versions 4.2 (or earlier) may be changed from the result of a Windows update. Product Line TAC IA Series Environment I/A Series G3  I/A Series N4  Cause The hostId is automatically generated upon first install of the software and stored within the registry.  The location of the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update.The hostId is automatically generated upon first install of the software and stored within the registry.  The location of    the G3 versions 3.8u1 or (earlier) and N4 versions 4.2 or (earlier) registry keys can be affected by a Windows update. Resolution I/A Series G3 version 3.8.213 (or higher) and I/A Series N4 version 4.3.58.18 (or higher) have been modified to guard against Windows updates to prevent hostId changes.  Installations of N4 4.3 and/or G3 3.8u2 will continue to operate normally and will not assume a new hostid after a Windows update.  All previous versions of Niagara could generate a new hostid after a Windows update, requiring a license replacement.   Schneider Electric recommends updating I/A Series G3 and N4 installations to the latest released software in order to maintain the latest security protection and to gain benefit from the latest features.  These builds are:   I/A Series 3.8 Update 2 (3.8.213 and later) I/A Series 4.4 (and later)   Patch to address multiple Host IDs on a single Microsoft Windows© platform   A set of patch files have been created to stabilize the Host ID for cases where customers have not upgraded to the latest version of Niagara (see installation instructions below). Once these patches are applied to the older versions of Workbench the Host ID is stabilized and should not change if Windows updates are installed.   Note: This is a reminder that a 32-bit install will always generate a different host-id than a 64-bit install.   IMPORTANT NOTES REGARDING THE PATCHES   Patches are only supported for the latest update (maintenance) version for the relevant release. Patches are not available for I/A Series G3 release 3.5 and earlier, or I/A Series N4 release 4.0 or 4.1. Builds prior to G3 3.8.213 are considered unsupported. Customers applying these patches do so at their own risk. Newer versions of Niagara (3.8U2 and 4.3) have introduced a stabilized method of managing the Host ID and do not require any patch. The patches do not eliminate the issue of different Host IDs generated when installing 32-bit and 64-bit Niagara. Installation Instructions   The Host ID patch file is available for download on the EcoBuilding Exchange Download website.  Login to the Schneider Electric EcoBuilding Exchange Download Center and enter G3 and N4 Host ID Patches in the search area or the filename of the zip shown below.    Download the G3_N4_HOSTID_PATCHES.zip and unzip into a temporary folder. The archive contains 'nre.dll' for various versions of I/A Series G3 and Series 4.2 in a directory structure identifying them first by version and sub-directory identifying 64-bit or 32-bit Windows. The 4.2 folder also contains 'njre.dll' which will need to be copied only for 4.2 installations.  Follow these instructions:   Verify the installed java version to be either 64-bit or 32-bit. Start a Niagara Command Line (Home>/bin/console.exe) from the desktop of the platform to be patched. From the Niagara Command Line execute the command: nre -version One of the listed items will be java.vm.name. If the text contains “64-Bit” then the installation is 64-bit otherwise the installation is 32-bit. Stop any running station using Workbench's Platform Application Director on the platform to be patched. Exit Workbench if running on the platform to be patched. From the Niagara Command Line ... /bin/console.exe execute the command: plat uninstalldaemon  Prior to replacement, save a copy of the existing nre.dll located in /bin folder. If Niagara 4.2 is being updated also save a copy of the existing njre.dll located in /bin folder. Copy the version appropriate and OS appropriate (64-bit or 32-bit) downloaded version of nre.dll file to the Home>/bin folder. If Niagara 4.2 also copy njre.dll to /bin folder. Overwrite the existing file(s). From the Niagara Command Line (/bin/console.exe) execute: plat installdaemon Start Workbench.  Open a platform connection to the patched platform. Using the Application Director, start the station.  

Issue Customers want to know how to localise their Reports Server  Environment SBO 1.9.3. Cause User may wish to change language on produced Reports etc.. Resolution Localisation of the Reports Server is currently not supported although there are plans to add this feature in a later revision.

Issue Unable to print a badge preview when designing a layout in Access Expert Product Line Access Expert Environment Access Expert Win8.1 Premise Hosted SQl 2012 R2 SQL 2014 Cause Operating system incompatibility with version 3. Version 3 only support Windows 8.1 and above. Resolution If the user is running Windows 7, the Preview will not work. Use a compatible OS, like Windows 10, and try again.

Issue Personnel Manager not operating correctly but Personnel Editor is fine Product Line Andover Continuum Environment Seen in Continuum 1.94 Cause Personnel Manager seems to run correctly but the Area names, Assigned and Unassigned data does not show correctly and cannot be modified. Blank spaces at the end of the Area Names or Alias cause the Peronnel data (Assigned and Unassigned Areas) to show incorrectly in Personnel Manager, but all correct in Personnel Editor. Resolution Remove the spaces at the end of the Area Names and Aliases Restart Continuum

Issue Needing to convert a site from V2 to V3. Product Line Access Expert Environment Win 8.1 and above Hosted Version 2 Version 3 Cause There are no directions on how to convert a Hosted Site on V2 to V3. Resolution When converting from V2 to V3 there are a few things that need to be verified first before attempting this action: Verify that the site does not have any SSC's that are configured as FN-4502, this information would have to be passed on prior to attempting the conversion by creating a case with your local country support group. Once the all clear has been given by product support, then the process can be started. Using two monitors bring up an instance on each for comparison Verify that all users, Access Levels, Schedules, Trigger and Procedures etc are in place Once confident, then connect to each SSC and change the Host IP name from the xxx.accessxpert.com to us.accessxpert.com Click on the View All Hardware Icon to see when the SSC comes online Once this happens, click on the Update firmware to get to the latest version downloaded to the controller When the device comes back online, verify that all the sub devices comes online as well If not then perform a Push Controller Database to the controller again When the controller comes online, all the subdevices should come online as well as Readers etc. At this point everything in V2 will become Unknown and can then be deactivated

Issue Need to a method to automatically enroll users into Access Expert? Product Line Access Expert Environment Premise Install Hosted Instance Cause Enrollment readers are not used in Access Expert.  Resolution When a card is read at the Door Reader, it will result in an "Access Denied/Card Pin Not Found" event being generated. This event can then be used to create a new user. Once this user has been created and added to the system, the card will become active and have access to the doors it's assigned to. 

Issue Maximum number of expansion modules and doors per controller Environment SP-C Security Expert Security Expert Controller SP-RDM2 Security Expert Security Expert Door Expansion Module Cause Documentation states that one SP-C supports up to 128 doors but this is dependent on the communications.  Resolution The current recommendation from Product Management is a maximum of 24 to 34 doors per SP-C. This equates to about 10 to 17 reader expansion modules.  

Issue After starting up the SmartX Advanced Display for the the first time, the operator finds himself stuck in SmartXKiosk mode before having any chance to select a password/PIN code. Product Line EcoStruxure Building Operation Environment Advanced Display v1 Advanced Display v2 Cause SmartXKiosk has been selected as launcher. The first time the SmartX Advanced Display is booted up the operator is presented of a choice to use  SmartXKiosk or TouchWiz as launcher. If SmartXKiosk then is selected instead of TouchWiz the operator will enter SmartXKiosk without having set a password first. Resolution Request an unlock code (PIN) from your local support center, which will enable the operator to exit Kiosk Mode. Press the Home (Hardware) Button at the SmartX Advanced Display. This will enable you to choose launcher again. Make sure that "TouchWiz" is selected. Note: In the next release this will note be an issue, since you are forced to select "TouchWiz" at first use to proceed (if SmartXKiosk is selected, you will be prompted to choose again)

Issue SP-C-WEB Recommended Limits Product Line Security Expert Environment Security Expert SP-C-WEB Cause The SP-C-WEB limitations are mentioned in briefly in the SmartX Controller SP-C-WEB presentation but detailed information on this is not available in the current SP-C-WEB documentation.  Resolution Schneider Electric's recommended limits for the SP-C-WEB:Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000 Number of Areas: 32 Number of Doors: 32 Number of Aperio Doors: 0 Number of Sallis Doors: 0 Number of Allegion Doors: 0 Number of Credential Readers: 0 Number of Cameras: 2 Number of Elevators: 0 Number of Floors: 0 Number of Inputs: 512 Number of Keypads: 32 Number of Outputs: 512 Number of Input Expanders: 32 Number of Output Expanders: 32 Number of Reader Expanders: 32 Number of Analog Expanders: 32 Number of Users: 10000

Issue Unable to configure alarms to remain active after being acknowledged if they are still in the alarm condition. Product Line Security Expert Environment Security Expert Cause Security Expert handles alarms a little differently to the rest of our product lines. The main difference being that everything is event based with each transition being an event which can itself trigger an alarm if it has been configured to do so. Those alarms are then seen as "active alarms" in the system (showing up in the Active Alarms Status Page View) until they are acknowledged by an Operator. Each alarm transition is separate with there being no direct tie to the current status of the object/condition that triggered the original alarm. Resolution What you can do is have both an Active Alarms list and an Acknowledged Alarms list in the same status page view. That way you will be able to see the last events that have triggered an alarm and if it has been acknowledged by an operator yet or not. This coupled with a status list of the objects you are monitoring can provide the operator with enough information to identify and manage each event transition of the alarm condition.

Issue Converting the entries from an MPX controller error log can be useful when there has been a software revision change. Product Line EcoStruxure Building Operation Environment EBO MPX Cause There may be an entry in an MPX error log that shows as follows: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change Resolution The ability to extract the firmware revision numbers from the controller error log is useful especially if you do not have the device report. Take a look at the last 2 numbers of the following line: 25 I 2018-07-02 10:07:36.56 0x00006409 0x20000015 0x80018a15 0x10000134 0x18061101 Software revision change 0x10000134  == 1.00.01.00134  (please disregard the missing 01) 0x18061101 == 2018 06 11 (ignore the trailing 01 in the hex number)

Issue Partners and branches need to understand the terminology used with Security Expert and what those terms mean from a Continuum perspective Product Line Security Expert Environment Security Expert Continuum Cause A table key to map object terminology between Security Expert and Continuum Resolution   Continuum Security Expert Objects Records User Operator Personnel User Area Door Group (Area) = Intrusion/Antipassback/Counting Area Rights Access Levels AC1/IOUs Reader Expanders/RDM2 Numerics Virtual Inputs/Outputs Plain Enlgish Programmable Functions/Function Code/services Event Viewer Status Pages Alarm Viewer Status Pages Listview Status Pages Power Supply Analog Expander Network Sites NC/ACX Controller SPC Doors Doors Security levels Security levels Schedule Schedule Scedule Exception Calendar Action Holiday Holiday Reset Manual - Factory default – short Reader, L2D0, download Array Data Values Permisssions/Security Levels Record Groups +V V+ Ground V- Data 1 1 1 Clock 0 0 0 LED L1    

Issue Satchwell AZ2401 Rotary Actuator requires replacement. Product Line Field Devices Environment Satchwell AZ2401 Rotary Actuator installed on Satchwell MBF Series Rotary Shoe Valve Body. Cause Obsolescence of Satchwell AZ2401 Rotary Actuator Resolution The Satchwell AZ2401 actuator would normally have been installed on a Satchwell MBF Valve Body. The Actuator comprised a 6 wire electrical connection enabling it to be operated from a Satchwell Z Monotronic or CZT Climatronic Proportional Controller as follows: Terminal 1 – Open signal Terminal 2 – Close signal Terminal 3 – Common Terminal A – 135 ohm Feedback Potentiometer – winding Terminal B – 135 ohm Feedback Potentiometer – wiper Terminal C – 135 ohm Feedback Potentiometer – winding If all 6 wires are connected then the AZ2401 actuator may be replaced by following SE actuators: MD20B-24 + Linkage Kit 914-1070-000 from Schneider Electric and an accessory kit   P140A from Belimo If only 3 wires are connected, that is to terminals 1, 2 and 3 then the P140 accessory kit is not required.

Issue Starting in EcoStruxure Building Operation 2.0, a new licensing structure has been implemented to reflect the new scalable pricing model.  This new pricing model is different from previous versions. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Version 2.0 and up Cause Due to the change in our pricing model within EcoStruxure Building Operation 2.0 and later, we have new policies regarding scalable pricing which has been different in the past. Resolution In regards to questions around the new scalable pricing structure For EcoStruxure Building 2.0, please reference the sources below. EcoStruxure Building Operation Scalable Pricing Frequently Asked Questions EcoStruxure Building Operation v2.01 - Scalable Pricing Policy Scalable Pricing Overview Video - EcoStruxure Building EcoStruxure WebHelp Article about Licensing Model General Notes: An upgraded or newly purchased 2.0 license will work with sites running older versions of EcoStruxure Building Operation. Each Enterprise Central and each Enterprise Server license comes with one client license.  It will always be possible to operate the system and will always be possible to add to the system (besides attaching automation servers to the enterprise server) if you do not have enough licenses. After certain time periods, the warnings, banners, and prompts will get larger and more noticeable.  If ONLY hosting IP devices and no Automation Servers under the Enterprise Server, it is still necessary to purchase the minimum size Enterprise Server license (10 or fewer Automation Servers) as well as then the appropriate number of hosted node licenses.  The intent of this is to limit the development and support costs of having a highly resourced user interface at the Enterprise Server and to distribute this load across multiple servers.

Issue Is there an option to disable the Forta actuator zero point check/adjustment on power up?  Environment Schneider Electric Forta actuators Cause The Forta actuator running the zero point check/adjustment on power up is causing an issue in the control sequence of the plant.  Resolution It is not possible to disable the zero point check/adjustment on power up of the the Forta actuator by any configuration of the dipswitches. The function is coded into the actuator firmware. 

Issue Trying to create a Lon binding from two or more nvo's in one Lon device (hub) to two or more nvi's in many Lon devices (targets), a so-called fan-out binding. The binding between the first Lon devices works fine, but when trying to create the binding from the Hub Lon device to the second Lon device (target) it does not work. The binding window for the second Lon device (target) is opened; the Lon device (hub) is chosen in the browser window on the right side; and the nvo in the hub is dragged to the nvi in the second target device. But the binding tool will not accept this binding. It is not possible to release the nvo from the Hub Lon device on the nvi in the second target Lon device. Product Line EcoStruxure Building Operation Environment Building Operation Workstation LON Devices Cause Normally when creating a binding using the EBO binding tool you open the binding window for the target (receiver of the value). But in this particular case you need to do it the other way around and open the binding window for the hub (sender of the value) instead, and then drag the target to the hub. Read more about Fan-out Bindings in the Webhelp. Resolution Go to the Lon device with multiple ins or outs (hub) and open the bindings window In the browser window on the right side find the target Lon device Drag the nvi from the target device to the nvo in the hub Lon device

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 Unable to download MP-V Flow Balance Data object to a controller using download all Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose VAV Cause The inability to use download all is a protection added to prevent overwriting any flow balance data inadvertently Resolution All Flow Balance Data Object properties are downloaded by explicitly downloading the Flow Balance Data Object as shown in the video below    

Issue On a cold start, the i2 or b3 controller does not retain the configuration stored in flash memory. The controller error log shows a 0x000014fb error.   12     E      01/01/1989 00:02:10.00     0x000014fb     0x0928ab00     0x019085a6    0x1442000c Product Line Andover Continuum Environment Continuum b3 Controller Continuum i2 Controller Cause i2 and b3 controllers must compile the controller configuration prior to backing the configuration up to flash memory.  An invalid configuration will prevent the compilation process from completing, thus preventing the backup process from succeeding.     The most common causes of OMS Backup failures are Plain English programs that contain errors. Input or Outputs that are configured without a channel number.   Resolution Correct any configuration errors.  Initiate a backup of the controller configuration to flash memory. Verify that the backup has been successful.  There should be no 0x000014fb  errors in the controller error log. 

Issue Connecting to an ES that is on another machine through WorkStation and trying to force a BACnet input or output point located on a b3, connected to an AS-P, causes WorkStation to freeze. The only way to get out of freeze is by ending the system task in Windows.   Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server v2.0.2.x Building Operation Automation Server v2.0.2.x Building Operation Workstation v2.0.2.x Continuum b3xxx Controller any version Cause EBO v2.0.2.x has communication issues when connecting to an ES that is not on the machine you have WorkStation on.  Resolution Upgrading to 2.0.3.45 or later will resolve this