Issue AS-B/P is unable to upgrade to EcoStruxure Building Operation 3.2.x from out-of-the-box or DFU mode. When checking the upgrade file you receive the following error: Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause In 3.2.1, the change was made to use IP-over-USB as a way to communicate faster through the USB. Due to this, IPv4 and IPv6 need to be enabled on the connected device running Device Administrator. Resolution Check to make sure IPv6 is enabled on your machine. Open a Command Prompt window and run the "route print -6" command If it only shows two IPv6 addresses then IPv6 is disabled and you will need to enable it To enable IPv6 Open Registry Editor on your Windows Machine Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters\ Double-click on  DisabledComponents to edit Change value from "FF" (IPv6 disabled) to "00" (IPv6 enabled) Note: The Disabled Components registry value does not affect the state of the check box. Therefore, even if the Disabled Components registry key is set to disable IPv6, the check box in the Networking tab for each interface can still be checked. This is the expected behavior. Note: You must restart your computer for these changes to take effect.  

Issue Details on how Modbus IP Multiple Queries and Multiple Query Packets work Product Line EcoStruxure Building Operation. Environment Building Operation SmartX Servers Modbus IP Cause Understanding of how the Modbus synchronous and asynchronous transport layers differ. Resolution By default, the Multiple queries is Disabled, this is the synchronous transport layer. To enable the asynchronous transport layer the Multiple queries must be Enabled within the Modbus TCP Network properties as shown below. Setting to "Enabled" allows multiple queries (packets) to be sent to multiple Modbus devices, thus reducing wait times.  It also enables further settings in the Modbus Device properties "Maximum concurrent queries" and "Multi-query packets".   The maximum concurrent queries and multiple-query packets as shown below are configurations for the Modbus asynchronous transport layer. The Maximum concurrent queries setting is only enabled if the "Multiple queries" is enabled in the Network Properties. When enabled, this allows the "concurrent queries" to be sent as a single packet.     Modbus Synchronous Transport Layer Each Modbus query is sent out one after the other. Before sending out the next query the transport layer waits for a specified period for the previous query. Example Poll Sequence Device No. Objects 1 2 2 1 D=Device, Q=Query, R=Reply D1 Q1 Send D1 R1 Receive  D2 Q1 Send D2 R1 Receive  D1 Q2 Send D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 3 seconds. Modbus Asynchronous Transport Layer With the asynchronous transport layer enabled, the queries are transmitted to multiple devices at the same time. The maximum number of queries that are transmitted to that one device is controlled by the “Maximum concurrent queries” setting. The “Multiple-query packet” specifies whether the queries are transmitted in one TCP frame or not. Simple Example Poll Sequence Device No. Objects Maximum concurrent queries Multiple-query packet 1 2 False 1 2 1 False 1 D=Device, Q=Query, R=Reply D1 Q1 Send D2 Q1 Send D1 Q2 Send D1 R1 Receive  D2 R1 Receive  D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 1 second Complex Example Poll Sequence Device No. Objects Maximum concurrent queries Multiple-query packet 1 10 True 5 2 4 False 2 D=Device, Q=Query, R=Reply D1 Q1, Q2, Q3, Q4, Q5 Send D2 Q1 Send D2 Q2 Send D1 R1, R2, R3, R4, R5 Receive  D2 R1 Receive  D2 R2 Receive  D1 Q6, Q7, Q8, Q9, Q10 Send D2 Q3 Send D2 Q4 Send D1 R6, R7, R8, R9, R10 Receive  D2 R1 Receive  D2 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 2 seconds   NOTES The use of this feature should be avoided before EBO v3.1 Some Modbus devices do not support multiple queries or multiple query packets, so the feature should be tested on an individual basis. (Some devices may even go offline until manually reset) This feature will increase the CPU usage on the EBO server. It should be avoided on EBO Servers that are already heavily loaded

Issue Workstation error when logging into a remote Enterprise Server. Enterprise Server has available client licenses. 'No valid client license available. (Error -5: No such feature exists.)' Product Line EcoStruxure Building Operation Environment EcoStruxure Building Workstation  EcoStruxure Building Operation License Administrator Cause Workstation is trying to check out a license from the local computer. The License Server is on the Enterprise Server computer and the Enterprise Server license has been activated on the Enterprise Server computer.  Resolution On the Workstation computer, run the License Administrator and change the License server address from the default '@localhost' to the IP address of the Enterprise Server. Refer to License Server Address on Web Help. License server address default: Change to License Server IP address (example below):

Issue How to change the CX level controllers message count to improve I2 Infinet communications. Throttling adjustments using accinfoframe1 and accinfoframe2. Product Line Andover Continuum Environment accinfoframe, accinfoframes, acc info frame Continuum Cyberstation CX 9680 Infinet I2 bus Cause Improve I2 communications on the infinet bus. Changing the CX level controller's message count on the Infinet bus to improve alarm delivery and exported data times when heavy polling is occurring. Resolution TPA-BOST-00-0004.00 describes several fixes, including one that improves field bus with heavy traffic. One of the fixes speeds up graphics and field bus reloads. With the latest version of the firmware the ability to throttle the number of messages during token passing has been added. This will allow a variable to adjust an Infinet bus based on the amount of traffic a particular bus is experiencing. With the latest firmware versions 2.100028, 2.000030 for the Netcontroller 9680 there are variables that can be used to adjust the number of messages per token pass. This is very similar to the MaxInfoFrames setting on Bacnet the devices; we'll call them “accinfoframe” for this document and examples. The value can be adjusted for values of 1-128. Since the TPA was issued, the value is defaulted to 128 and if no accinfoframe variable is created the default value is 128. In order to have the ability to adjust the number of messages in the supported controllers, an infinity numeric needs to be created in the CX/BCX. The name of the variable has to be correctly spelled but is case insensitive. The names are accinfoframe1 and accinfoframe2. Accinfoframe1 will be the setting for comm1 one and accinfoframe2 will control the setting for comm2. When configuring accinfoframe1 or accinfoframe2, make sure to select the SetPoint and back up the flash on your controller, so that you retain the settings in case of power failure. Example of when to use throttling: There will be instances where the accinfoframe variables will need to be throttled. For instance, lets theorize a site “ChillerPlant” and the ChillerPlantCX(9680) has 100 infinet controllers located on Comm1. In our scenario we have 3 workstations each running a graphic polling 2 points(200 points) from each Infinet controller and we are running listviews of infinitynumerics on 8 of the Infinets controllers or perhaps hundreds of points that are being collected for extended logging. As one might think, communications would begin to slow down when polling for values on approx 600 points not to mention the point to point communications of the listviews and extended logs. With all of this traffic, the CX will dominate the network token. Since it can do 128 messages when it receives the token and it receives the token between every Infinet, the token round time can go into minutes. This means that the Infinet controllers can take minutes to deliver alarms and exported data. Another potential scenario is if one selected 4 Infinet controllers to reload, the bus may very well be overloaded at this time and may be receiving errors on the reloads in the distribution window. One of the error messages that could be expected is “Unable to reload object CarlNet\My_9680\My_I2_814\Num_1. An invalid response was received from a remote service request.” In this example we could create a infinity numeric on the CX named accinfoframe1(for Comm1) and start to reduce the number of messages CX would generate before passing the token. On the other extreme, if the ACCInfoFrame setting is set too low, such as to 1 as in the earlier versions of Netcontroller II firmware, this extreme traffic could cause such issues as extreme slowness of graphics and listview updates, Extended logging not being capable of retrieving the required data at the required intervals, and possibly the Infinet controllers randomly appearing to be offline to the system. In the example above the question is “What value should the accinfoframe1 be set to?” The answer entirely depends on how much traffic is on the Infinet bus. How many extended logs, how many listviews, how many graphics, alarms and Plain English programs are creating traffic on the bus? The quick way out here would be set the accinfoframe1 to a value of 1. We know for a fact that this would slow the bus down, and you might want to increase the number to 5. As mentioned this is all dependent on the amount of traffic on the Infinet bus. Or we could take a more in depth approach and find out what the token round time is on the bus and adjust our accinfoframe1 based on token round time. We could create the following points. TOKEN ROUND TIMER PROGRAM InfinityNumeric MaxTokenItem InfinityNumeric MaxTokenRound InfinityNumeric TokenRoundTime Logsize:100 Logtype: LogMaximum InfinityProgram TokenRoundCalc InfinityDateTime LastDateExport Program code: Initialise: LastDateExport = PointMapsTests\Infinity2\i2_851\Date Goto DoTokenRoundCalc DoTokenRoundCalc: If LastDateExport <> PointMapsTests\Infinity2\i2_851\Date then TokenRoundTime = (PointMapsTests\Infinity2\i2_851\Date - LastDateExport) – 1 LastDateExport = PointMapsTests\Infinity2\i2_851\Date Endif MaxTokenRound = maximum(TokenRoundTime) MaxTokenItem = maxitem(TokenRoundTime) E: If TS >= 5 then Goto Initialise The program and points above created in the CX will allow the token round time to be captured and one could essentially get very creative and change the accinfoframe value dynamically through Plain English programming. For these examples we just want to find out the token round time and manually adjust the accinfoframe1 variable to avoid any reload errors. The TokenRoundTime, MaxTokenRound and MaxTokenItem numerics can be added to a watch window or a graphic to visually monitor the TokenRoundTime. If you see that your TokenRoundTime is 5, 10 15 seconds, this is an indication you need to reduce the accinfoframe1 value. As a rule of thumb a TokenRoundTime of less then 2 seconds is acceptable, while keeping the TokenRoundTime below 0.7 seconds is ideal.

Issue Xenta Server reports it is in FAILSAFE mode without shorting out terminals 9 and 10. After connecting via HyperTerminal, restarting and trying to reset the IP address, the screen continues to scroll back to dsh/> Xenta Server has gone offline and can not connect directly to it using Ethernet. The Run light is flashing Green on first start up but then reverts to red and the LON light also flashes red. During boot up it pauses and reports an error (via HyperTerminal) in loading the RAM disk.  IP Address is set to 172.22.1.5 and can not change it.  Not able to load any firmware into the device – error received. "Error: Could not create remote directory." Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 527, 511, 555 Xenta Server 701, 721, 731 Cause Unknown corruption of the Xenta Server hard drive / flash drive, possibly due to electrical noise. Resolution To attempt to recover this device, try to format the device’s flash drive. To achieve this you can follow these steps using HyperTerminal or an equivalent application: (For further assistance with connecting to Xenta Servers and HyperTerminal refer to Connecting a serial cable to a Xenta 5/7/9xx controller).   Login and type the command FORMAT.  (May require device to be placed physically into the fail-safe mode by shorting terminals 9 and 10). The format command can take up to 3 minutes to complete but you should see the confirmation through HyperTerminal while this is occurring. If you have placed the device into Fail-safe mode, remove the link on terminal 9 & 10. Restart the device, by either cycling the power or typing the command RESTART through HyperTerminal. Set the IP address and IP settings (command SETIP). Install the latest firmware. You can download the latest firmware from The Exchange Extranet; ensure that you use the correct version since there various versions for the Xenta Servers. Run the firmware download to the device. During the download you may receive an error regarding "Failure to get the hardware version from the target device…", select OK Continue the installation The download will then occur, it will take some time and may appear that the software is not responding but this is normal. Be patient and if you don’t receive any errors then all should be ok. The device should now restart, after a 1-2 minute window the “RUN” LED should be a solid green. If after following these procedures, the device is still not responding as expected please send into Repairs via your normal repair process.

Issue What specification should the Continuum BACnet MS/TP cable meet? Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation Environment Systems using BACnet MS/TP comm's, with b3 controllers and 3rd party MS/TP devices. MSTP Cable type Spec Cause Often an incorrect cable type is used when wiring MS/TP devices, unless the correct cable specification is used it is unlikely you will get reliable communications. Resolution The BACnet Controller Technical Reference defines the following cable specification for a MS/TP (MSTP) cable: RS-485 Cable Specifications: Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Ohms Velocity of propagation: 78% Capacitance: <12.5 pF/ft (~ 41pF/M) between conductors and < 22 pF/ft (~72pF/M) between the conductor connected to ground and the next conductor. An example of a cable that meets this specification is Belden 3105A. Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Issue Can the Continuum Software be downloaded from the web, or ordered on CD? Product Line Andover Continuum Environment Continuum Cyberstation software Cause Download of Continuum Cyberstation software Resolution The Continuum Cyberstation software is available for download from The Exchange Download Center. The link below will direct you to the Cyberstation software. CyberStation Software If specific older versions of software are required see Older CyberStation versions not found on the Extranet (Exchange Online). If a customer specifically requests the software on a CD, then these can be ordered through the regular Order Entry channel specifying the version required.

Issue Windows authentication is not working with Security Expert once configured. Environment Security Expert Windows Authentication Cause Windows authentication was not installed or configured properly during initial install/setup of Security Expert. Resolution 1. Install the Security Expert Server, and any Security Expert Clients, with the "Use Windows Authentication" option enabled during the installation process. If this was not initially done at install then you will need to backup your SecurityExpert and SecurityExpertEvents databases, uninstall Security Expert (installing overtop or repairing install may not work) and then re-install Security Expert with the "Use Windows Authentication" option enabled.   2. Go to Global | Operators and create a new operator. The Name can be anything you want. The User Name must be the domain name and domain username you want to have access to Security Expert. This is in the form of "domain\username" as shown in the example image. Set a Role for this operator. And then enable the "Use Windows Authentication" checkbox and save the changes.   3. Go to Global | Home and logout of Security Expert. 4. On the login page select the "Use Windows Authentication" checkbox, set the Server to your Security Expert Server machine name (or blank if it is the local machine) and press Logon.   5. You should now be logged into Security Expert with your Windows username being used.   If you receive an "Access Denied" or other error then confirm the following before contacting Product Support for further help. Security Expert Client and Server were installed with "Use Windows Authentication" option enabled. There is an operator object created in Security Expert with the same domain and user name as the domain user you are trying to login with. The "Use Windows Authentication" option is enabled on this operator object. At the login screen you have enabled "Use Windows Authentication" and set the Server correctly.

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

Issue LMTOOLS was not installed on the computer that Vista 5.1.8 was installed on. Product Line TAC Vista Environment Vista LMTOOLS LMAdmin Cause The TAC Vista license administrator tool has been upgraded to LMAdmin, a web based license administration tool accessible using a web browser. Existing license files are compatible with the new LMAdmin tool that is included in the TAC Vista Server and TAC License installers. Resolution If the license server is not running as a service, Vista is unable to locate the license, or you need general troubleshooting help then see License troubleshooting in Vista 5.1.8 or greater. Flexnet License Admin   The default license file folder has changed with the new LMAdmin license tool. The new default license file folder is "C:\Program Files\Schneider Electric\License Server\taclic\licenses\". For 64-bit OS the default license path is "C:\Program Files (x86)\Schneider Electric\License Server\taclic\licenses\". The license server administration, LMAdmin, is installed as a web server and is accessible at http://localhost:8080 after the installation; a shortcut will also be placed in the start menu. The location of this shortcut can be found by going to Start > All Programs > Schneider Electric > TAC Tools 5.X.X > FlexNet License Admin. To check what your license file contains, how many seats are available for each program, and how many are in use click on the Concurrent icon.   To log into LMAdmin, click on Administration in the top right corner. The default login and password is admin/admin and it is recommended that this is changed after the installation is finished. User accounts can be managed in the Administration area, under the User Configuration tab. Click the New icon at the top of the window to add users. The edit button at the end of the row of each user will allow the user name and password to be changed. There is also a delete button to remove unwanted users. If the computer running the TAC Vista License server enters a power save mode, the license server may have to be restarted manually in Computer Management > Services and Applications > Services.   TAC License Setup It is recommended to use the "License Setup tool" in the start menu instead of the license popup dialog when specifying a license server name or license file location. The License Setup tool can be found here; Start > All Programs > Schneider Electric > TAC Vista Server 5.X.X. Note: When upgrading Vista from a version 5.1.7 or older to a newer version, the old license file path may still exist in the registry. This will not impact the license server in any way. The old path can be removed if you desire through the TAC License Setup. During the installation of TAC Vista Server and TAC License, any license files located in the old license file folder are automatically copied to the new license file location; the original files are not removed.

Issue There is a need for Xenta I/O modules to be added as standalone devices on a Lon network. Product Line EcoStruxure Building Operation Environment Xenta I/O modules Building Operation Enterprise Server Building Operation Automation Server Premium Building Operation Automation Server Cause The Building Operation ES/AS structure allows I/O modules to operate without a Xenta programmable base unit. Resolution The following Xenta I/O modules can be added directly once the Lon interface and network have been created: I/O Module DI DI status DO DO override UI TI AO AO override Xenta 421A  - - 5 - 4* - - - Xenta 422A - 4** 5 5 4* - - - Xenta 451A - - - - 8* - 2 - Xenta 452A - 8** - - 8* - 2 2                   * - DI, 0–10 V DC or 0–20 mA, 1.8/10 kohm TI         ** - Status indication only when the corresponding universal inputs (UI) are being used as digital inputs. Once the I/O module is set up for SNVT communication the green LED will flash once every 10 seconds. For more information see Configuring Xenta I/O module inputs when used as stand-alone Lonworks devices.

Issue How can objects of a SmartStruxure™ Lite network be made available as BACnet points to third party BACnet building management system (BMS)? Product Line EcoStruxure Building Operation Environment SmartStruxure Lite BACnet Cause The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet and this will need to be changed if BACnet over IP is required. Resolution The BACnet protocol is always active, as long as the network cable is connected. However, two different BACnet options can be selected: IP or Ethernet. The default option is Ethernet. To verify or to change which BACnet protocol is currently in use, select the SmartStruxure Lite Manager that you want to configure from the left-side Network panel. Then choose the BACnet configuration list item. Define the Network Number (if the protocol selected is BACnet IP). Note: The Network number must be defined only on the monitor Manager. It shall be different then the Parent Network where the monitor is connected. A BACnet Device is uniquely located by a network number and a MAC address. Creating two or more B/IP networks, each with a unique network number, can be useful for limiting the propagation of local broadcast messages and for providing security by confining traffic to a particular geographic or logical area. Select the desired protocol type from the drop-down list between BACnet IP and BACnet Ethernet. Then choose an optional port number (if the protocol selected is BACnet IP). Default is 47808. Select the BACnet Priority of the BACnet write action of the SmartStruxure™ Lite's network monitor. Default is 10. Note: SmartStruxure™ Lite does not support BACnet Write Priority, per se. However, in Firmware version 2.4.x and newer, it is possible to assign the write priority for all SmartStruxure™ Lite BACnet points. Default value is 10, except if you upgrade a Manager using a version 2.3.x or older, BACnet priority will be 8, but can be changed. Click the Save button to apply the configuration changes. Click hit the Save All button to make the modifications permanent and reboot the Manager for the new options to enter into effect. Change the BACnet instance number of the Manager if required. IMPORTANT Each Manager must have a unique BACnet device instance number. A Manager device instance number can be changed by selecting the top-left icon inside the left-side Network panel.

Issue Using BACnet IP to add a SmartStruxure Lite MPM to a StruxureWare Building Operation Enterprise Server or Automation Server Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment StruxureWare Workstation Cause SmartStruxure Lite systems may desire an Enterprise Level Solution to bring multiple sites into one system. Resolution Configure the SmartStruxure Lite MPM for BACnet IP as shown in MPM BACnet Integration. Ensure that the BACnet Network ID is Unique to the system and does not match the Network ID in use by the Enterprise Server Save the BACnet Configuration Be sure to Right Click on the Root Object of the MPM and save the database. Open StruxureWare for Building Operation Workstation Right Click on the Server Object and add a BACnet Interface Ensure that the BACnet interface has a unique BACnet Network ID which does not match the Network ID used by the MPM Expand the BACnet Interface Click on the Server Object and select the Device Discovery Tab Select BACnet Devices NOTE: There have been instances of Skype causing interference with this process. Please completely close Skype if you are using it and unable to discover any devices. ALSO NOTE: There may be 2 instances of the MPM shown. If so, use the MPM that is part of the Enterprise Server BACnet Network Drag the MPM to the BACnet Interface/IP Network object in the Enterprise Server System Tree Right Click on the Device and Upload it If any devices are connected to the MPM such as a Zigbee Wireless State or Enocean switch, these will be discovered in the BACnet Network configured in the MPM Add these devices to the Enterprise Server by dragging and dropping them to the BACnet Interface/IP Network object Right Click and upload all devices.

Issue After changing a controller's IP settings, it does not come online and cannot be accessed via its web interface. The controller can be accessed via its web interface by temporarily defaulting the IP address. Still, changes to its IP settings cannot be saved and are instead met with the following "Invalid Port" errors. Invalid Port – Module UDP Port Invalid Port – Touch Screen UDP Port Product Line Security Expert Environment Security Expert Controllers (SP-C, SP-ACX, SP-AC1, SP-C-WEB) Cause The controller's HTTP Port has been set to 0. If this field is set to no value, this is converted to an invalid 0 value, the controller will no longer be accessible via the web interface and will require defaulting the IP address to connect. Resolution Change the HTTP Port to a valid value. The default HTTP Port is 80, but it should be changed to another available port for increased security.

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 Elements in Sigma Graphics within EBO are not displaying correctly when its bound object commands the element to display or not to display. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Cause The issue arises on a machine that has a Windows Language Pack e.g. Norwegian Bokmål installed where the decimal separator uses a comma (,) rather than a dot (.).   In the example, using the EBO Graphics Editor, it can be seen that the decimal separator in 0,5 is a comma in the 'condition' command, other commands are also effected e.g. Bitmap, Alarm etc; Resolution When a Sigma graphic Data Import is undertaken the decimal separator dot (.) used by the Sigma machine is replaced by a comma (,).   On the Sigma server machine using Registry Editor. Registry Edit can be run by typing RegEdit in the Windows search box on the Task Bar. 1. Goto > Computer\HKEY_USERS\S-1-5-18\Control Panel\International\ 2. Locate sDecimal. 3. sDecimal will be set to a comma (,). Change to a dot (.). 4. Re-import the Sigma graphics using the Graphics Data Import in EBO. 5. Select a graphic and edit using the EBO Graphics Editor, select an element and check that a .(dot) is used.   Finally, check operation by changing object states on the graphics and the respective element changes state too. Note: This will be auto checked and be incorporated into the Sigma Transition Tool in the future.

Issue It would be helpful if the MAC Address of an SP-C could be worked out when the physical controller is not readily accessible or has not yet been delivered Product Line Security Expert Environment SP-C Cause Cases may arise where a newly ordered or existing SP-C is going into a system but no MAC address is known.  MAC addresses are often required in order to obtain an IP address for a project.   The MAC address is not shown when connecting into the SP-Cs web browser (although the Serial Number is) and can only be shown via an Arp in the correct section of the network Resolution In normal circumstances each SP-C should have a Label on it which indicates the MAC address in full However in cases where the Label is not accessible it can also be derived from the Serial Number which can be viewed in the SP-C web browser, preceded by 00:1B:   Eg  00:1B:C2:AF:14:24  

Issue In Access Expert's 'View All Hardware' window, the status of controllers does not update. For example, controllers say 'Online' even though they are actually 'Offline' and vice versa. Live Monitoring window does not show disconnect/online events. Seq log shows error: Failed to Publish event.Moniker:MonikerItem {"Namespace":"MercuryServiceEvents","Nickname":"mercury:15-12-1"} Product Line Access Expert Environment Access Expert Premise Software Cause Enterprise Administrator group, under root, is missing permissions for Mercury service. Resolution Log into the Root instance, edit the Enterprise Administrator group, in the "Event Types" tab, make sure permission is granted to the Mercury Service and Mercury Commands

Issue Unable to connect to the detected RPCs using Engage app v1.2.1 or later and RPC 3.02.01 Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) (all types) v3.02.01 Building Operation Engage Application Cause EFR32 BLE chip needs to be upgraded to fw3.01.00.00012 but looking at the device report you see there is a Failure to upgrade EFR32 error. Resolution From workstation open the control panel and select the Firmware upgrade view. Right-click the RPC from the list of available SmartX controllers > Device> Upgrade Firmware>Select Device Firmware Select 3.01.02.00046 Firmware package Wait for the RPC to fully upgrade and return to an online state before going to the next step. This may take 6 to 9 mins which is normal. Right-click the RPC from the list of available SmartX controllers > Device> Upgrade Firmware>Select Device Firmware Select 3.02.01.00247 Firmware package Wait for the RPC to fully upgrade and return to an online state before going to the next step. This may take 6 to 9 mins which is normal Once the RPC is online Right Click the RPC > Device> Download All Objects If not upgraded in this order, the Bluetooth Chip isn't correctly upgraded and will fail.    

Issue What is the unit load of the SpaceLogic SLP Room Units that will help me to calculate how many SLP Room Units that can be added on ComA and ComB of a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment SpaceLogic SLP Room Unit SmartX Server Cause Documentation does not state the Unit Load (UL) of the SpaceLogic SLP Room Unit. Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SpaceLogic SLP Room Unit range use the SN65HVD1781DR transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/10 UL. In addition there are no local bias resistors and therefore the 1/10 UL of the transceiver would be the total UL presented to the bus by the SpaceLogic SLP Room Unit. Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus SN65HVD1781DR 0.1 Yes None None 0.1 No Based on the above the total number of devices can be calculated as 32/0.1 = 320. The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore a SmartX Server is limited to 127 devices per com port (254 total per Server) so this should effectively be the limiting factor. Since the SpaceLogic SLP Room Unit does not have an isolated RS-485 interface it conforms to Generic RS-485 Network Device Configuration 1 in EBO Webhelp.  A network consisting of only SpaceLogic SLP Room Units should only require a 120 ohm termination resistor at each end of the bus and not require any bias resistors. Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.

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