Building Automation Knowledge Base

Issue The standard opened Unifact Pro stencil provides items for BB83 range of Unifact Pro controllers and does not provide items for older Unifact Pro range. Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma Environment VisiSat NCP Palm Unifact Pro Cause As standard the automatically open stencils do not provide items for the older BB*2 Unifact Pro range. Resolution The current range of Unifact Pros are presented in the standard Unifact Pro stencil. The obsolete Unifact Pro range (BB*2) are not presented in this stencil, a different stencil needs to be added, to provide the older BB*2 Unifact Pros, before there available to use on the drawing. Visio 2003/2007 Go to the Visio menu Click File Click Stencil Click Open Stencil Navigate to C:\Satchwell\Binary\VisiSat\EN\Visio Select the Obsolete.vss stencil You will then have the opportunity to choose one of the older range of Unifact Pro controllers. Visio 2010 Under shapes click More Shapes Click Open Stencil Navigate to C:\Satchwell\Binary\VisiSat\EN\Visio Select the Obsolete.vss stencil These stencils are installed during the VisiSat installation process. If for whatever reason your computer no longer has this file, to save you reinstalling VisiSat, you can download a copy of the VisiSat 2.1 Build 196 (200, 201) obsolete stencil from here. You can store the stencil anywhere on your system and use it, VisiSat's default storage locations is under “C:\Satchwell\Binary\VisiSat\EN\Visio”

Issue How to get data from Rayleigh Instruments RI-78-80-C kWh power meters Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server (ASP/ASB) Modbus RTU Interface Cause The RI-78-80-C meter provides a single 48-bit Modbus RTU word representing energy in kWh. This word spans three 16-bit registers (registers 0, 1, and 2). The meter: Only responds to a valid 48-bit read Does not return exceptions for invalid or partial register reads Resolution To successfully read the 48-bit value: Step-by-Step Instructions Create a Modbus Group Set an appropriate polling interval. Add Registers Add three 16-bit unsigned registers to the group: ModReg0 (Register 0) ModReg1 (Register 1) ModReg2 (Register 2) Create an Analog Value Example name: kWReading Script Program Use the following calculation: kWReading = ((256 * 256 * ModReg0) + (256 * ModReg1) + ModReg2) / 100 ​ This formula accounts for the fact that each register only uses half of its 16-bit range (values from 0 to 255). The register values represent 1/100 of a kWh, so a scaling factor of /100 is applied. Bind Points Bind the Modbus registers and analog value to the script program. Example Calculation If: ModReg0 = 3 ModReg1 = 167 ModReg2 = 59 Then: kWReading = ((3 × 256 × 256) + (167 × 256) + 59) / 100 = 239419 / 100 = 2394.19 kWh ​   Additional Notes The device may appear online in EcoStruxure even if it’s not responding correctly. This is because the online poll interval mechanism expects a response from a 16-bit register. Since the RI-78-80-C doesn’t respond to invalid reads, it may falsely appear online. To avoid this, set the online poll interval mechanism to “Inhibit”. Compatibility Warning: This device may not function correctly in v2.0 and v3.0 due to changes in offline detection. This issue is resolved in v3.1. Resources Example Modbus Objects and Script RI-78-80-C Exports.zip Numeric Output kWReading   Line Calc1 kWReading = ((256*256*ModReg0) + (256*ModReg1) + ModReg2)/100

Issue Need to use the Automation Server port log to view BACnet MS/TP communication Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to capture BACnet MS/TP traffic for troubleshooting. Resolution In EBO 2024 (V6.0) and higher, there is an integrated packet capture feature available in EBO Servers with BACnet Interfaces. This feature allows users to create packet captures that record the BACnet messages that are visible to the EBO Server’s BACnet/IP and BACnet MS/TP networks. Refer to: Packet Captures in EcoStruxure Building Operation

Issue Having issues with the Personnel Manager, need to create a log file for PSS/R&D to help troubleshoot the problem. Environment Cyberstation Personnel Manager Cause Documentation Resolution Edit the file 'PersonnelManagerCtrl.dll.config' in the Continuum installation directory 'Commom' folder Change 'LogFile Enable' from False to True. Use the Personnel Manager to perform the operation causing issues so that diagnostics information can be written to the log file. Make sure to set 'LogFile Enable' back to False. File 'PersonnelManagerLog.txt will be created in the Continuum installation folder, send to PSS for analysis.     NOTE: The 'LogPerformance' option can be used when troubleshooting slowness issues.

Issue Seeing 0x00001427 Bad RTC chip errors in controller error log along with controller warm start errors. Controller error log contains entries similar to below.    01/01/1989 00:01:10.33 0x00001427       0x04070400       0x02028922       0x00000001       0x0000000                 HardwareErr__ Bad RTC chip 04/16/2011 09:47:24.93 0x00030000       0x00216500       0x00105c62       0x00000000       0x00000000                Warm start 01/01/1989 00:00:00.94 0x00001427       0x00201900       0x0011edba      0x00000001       0x00000000                 HardwareErr__ Bad RTC chip Environment Continuum Controllers Cause The error is a time related error but may not indicate that there is a physical problem with the controllers Real Time Clock (RTC). This can be due to an issue occuring on startup of a controller where there may be requests for time from COV updates. If that request comes in prior to the RTC clock coming up, it can post this error. The COV code will post this error and then try again later.  Resolution If this error occurs after a restart of the controller then this is more than likely a benign error and can be ignored. However, if it occurs when the controller hasn’t just restarted then it could be an actual fault with the RTC chip and may need to be returned for repair.

Issue Attempt to commission b3 device fails with error 'Device other' AS trace log shows error 'Invalid device instance". EXTRACT FROM TRACE LOG 2015-09-24 20:40:23.135 [1241912384] nsp.pin.BACnet Commission Canceled - Invalid device instance (AsyncCommands) 2015-09-24 20:40:23.142 [1241912384] nsp.pin.BACnet Command continuum.command.Commission failed. BACnet error 0x0 (AsyncCommands) 2015-09-24 20:40:23.144 [1241912384] nsp.pin.BACnet Command continuum.command.Commission failed: Device_Other (0xa0003) (AsyncCommands) Environment AS BACnet MSTP Cause The AS has detected a b3 device with the same serial number in the hardware folder. Resolution Associate the device in the hardware folder with the device that you are trying to commission by dragging the device in the hardware folder and dropping it on the device under the BACnet interface that is being commissioned. Note that the device's model numbers MUST be exactly the same in order for the association to succeed.

Issue Multiple issues caused by changing the link after discovering devices. Duplicate entries of MCU devices under a sub LAN interface Deleting duplicate MCUs causes MCU devices to be removed from I/NET Environment Automation Server integrated to I/NET Cause Changing the link address of the I/NET Interface should not be done after devices are discovered. If you must change the link address, do so before you have added devices to the I/NET interface. Resolution Option 1 -  Remove all controllers from the I/NET interface. Change the link to the correct setting Re-discover the devices Option 2 - Determine whether the AS or the I/NET controller has the correct information. (This will require I/NET software) If the AS is more correct, perform a download to the controller if the I/NET controller is more correct, perform an upload to the AS

Issue Continuum video integration using Pelco Endura. When video alarm comes in, Video Monitor starts up as expected and video is recorded for the specified amount of time but the recorded video does not automatically play back as expected. Product Line Andover Continuum, Pelco Environment Cyberstation Pelco Endura Cause The NVRs configuration for recorded video type has been changed from its default of continuous recording which is what the Continuum-Endura integration supports. You should ensure that your Pelco Endura system is set to continually record. While it is possible to change the recording type, continuous recording is the recommended setting from Pelco. As a result, when an alarm or event occurs, it is "marked" on the Endura system at the time of the event based on the recording time and duration. Such events are then visible from the Endura client as a marked event with details included in the comment for that mark. Resolution SOLUTION #1 If a specific recording type such as motion or schedule has been configured remove it to go back to the default continuous recording type. NOTE: As continuous video recording will utilize more storage capacity, one option for reducing the amount of storage used by all the video is to enable Pelco EnduraStor. SOLUTION #2 The other option is to leave the configuration as is and manually start playing back the recorded video by double clicking the video event. In the screen shot above, double clicking the PSS_Test_AV1 video alarm will cause the recorded video to start playing back.

Issue Controllers IP address needs to be changed but any attempt to do so results in the IP address reverting back to what it was previously configured for. Product Line Andover Continuum Environment Continuum CX9702 BCX controllers NC2 controllers ACX57xx controllers Cause The Controller has hit the Flash writes circuit breaker and is no longer able to save any changes to Flash. This includes updating Device settings such as IP address and ACC Node ID. The controller error log may also contain an error similar to below when attempting to make any such changes.   10/08/2014 19:00:22.00 0x00004406         0x03b76100        0x0004cb68         0x003e2000        0x000007d1                                         DEVICE_ERR_ERASE_LIMIT      (Flash circuit breaker tripped. CX97XX code base) Resolution One of the two methods to reset the Flash circuit breaker listed below should then allow the controller to write to Flash again.   1. accstatusbackup = accbackupenable   For more information see Caution when using PE programs to perform an automatic flash backup on a controller.     2. INFFlashDisabled.   Create a numeric in the controller with the following name and alias:   INFFlashDisabled   A value  greater than 0 usually indicates that the flash circuit breaker had tripped, though in some cases you may find these errors occurring when INFFlashDisabled = 0. In either case, once the value of this numeric is set to 0 and applied,  the flash circuit breaker errors should stop.

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 Services for assistance. Issue How can I clone an MPM? How can I upload config.db to an MPM? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause Unable to upload config.db to an MPM Resolution An MPM can be cloned from Building Expert by exporting default.db from one MPM and importing it to another (using the "Export Database" and "import Database" buttons) Note: Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. If it is necessary to clone the system configuration objects as well, refer to the procedure below: This procedure show you how to upload the Database to an MPM. To download a backup of the database, refer to MPM database information. Power up the MPM and ensure either its IP address can be pinged or Building Expert is accessible. In address bar of browser, enter 10.50.80.3/test.html. (assuming IP address of MPM is set to default) In Remote Path field of File Upload section, enter config.db. Click Browse and Navigate to the backup config.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Note: Uploading the config.db file first does not cause the MPM to reboot; which is why it is uploaded first On Browser, click to return to previous page. In Remote Path field of File Upload section, enter default.db. Click Browse and Navigate to the backup default.db file and select it. Click Submit Query. Wait for {“success”: true} to show before you proceed. Allow MPM a few minutes before attempting to access Building Expert. MPM will reboot automatically and install Database files. Note: MPM must not powered off during this time In address bar, enter 10.50.80.3 to connect to Building Expert and validate Database upgrade is correct.

Issue When printing access control cards, there is a need to print the a card number bar code on the card as well as photo's, names, text, logos etc. Environment Continuum Access Control systems, all versions. All Security and Integrated Workstations (with SEC or INT in the part number). Photo badging option (append -B to the part number). Cause As well as a photographs, text, numbers and graphics, barcodes may be added to the card design using the EPI Designer software. To use card badging the system requires that the Continuum Security Key (Dongle) has the badging option enabled (-B in the part number), otherwise the "Create/ Edit Badge" option will not be available to select. Resolution From the EPI Designer menu select the "Draw", "Bar Code" option and the following screen will be displayed allowing the barcode to be configured: The configuration page above allows the type of barcode to be defined, the Personnel "Field Name" to be linked to the code as well as other barcode options shown. Custom fields can also be used.

Issue Alarms are produced by Sigma controllers, but these alarms are not received at the Enterprise Server Product Line EcoStruxure Building Operation, Satchwell Sigma Environment Enterprise Server Sigma 4.08 Alarms Delayed alarms Transition Cause When Sigma alarms are manually tested from the Enterprise Server, the alarms are received normally, but alarms occurring during normal operation on the Sigma system, can be delayed, or not displayed at all at the Enterprise server. This issue is caused by the firewall. If the Enterprise Server is initiating the communication with the Sigma controllers, then the firewall will normally allow any alarm messages from the Sigma controllers to pass through the firewall, and the alarms be displayed normally. When the Enterprise Server is not initiating the communication the Sigma controllers, then the firewall will normally prevent any Sigma alarm messages from passing through, and therefore the Sigma alarms will not be displayed. Resolution The solution is to allow inbound communication to the Enterprise Server PC on port UDP 49152 Depending on the firewall used, the configuration steps can vary. If Windows Firewall is not used: Consult your vendor manual. Example of Windows Firewall not being used If Windows Firewall is used but managed by the IT department: Consult with your IT department. Example of Windows Firewall being managed by IT If Windows Firewall is used and you can manage it: See below Windows Firewall A quick solution is to use "SBO Firewall Config". While the tool is not officially supported, it has been used by various sites. To manually add the exception to Windows Firewall, refer to Using Sigma on Windows 7 with firewall.

Issue AutoCAD wiring symbols for I/A Series MicroNet LON controllers (MNL) Product Line TAC IA Series Environment I/A Series Micronet LON controllers (MNL) Cause The files are not available on the Download Centre Resolution The files can be downloaded from here.

Issue Requirement to set the BACnet max master setting on a SE8000 series room controller Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation Automation Server SE8000 BACnet MS/TP Cause The BACnet max master setting is not available to be set locally on the SE8000 room controller Resolution The max master setting of the SE8000 can be changed in EcoStruxure Building Operation Workstation.  Add the SE8000 to the EcoStruxure Server Open the SE8000 device properties On the Advanced tab, change the Maximum master property (which is a read/write property) to the required value. 

Issue When logging in via WorkStation all is fine, but logging in via WebStation shows a blank initial screen (see below). Environment WebStation Cause The system has been configured with a user defined default workspace. The default workspace contains an 'ampersand (&)' in the name. Resolution Apply hot fix 1.6.1.28100 or remove the ampersand character from the workspace's name. NOTE: This issue exists in all versions of StruxureWare Building Operation prior to 1.8, as of the writing of this article only 1.6.1 had a hot fix available to solve the problem. The issue has been resolved in StruxureWare Building Operation version 1.8

Issue When a MPM is replaced on a BACnet IP network, a "Duplicate network identifier" alarm is generated Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment MPM Automation Server Cause If the BACnet name and instance number in the new controller is not exactly the same as the original MPM, the Automation Server will consider that an additional device has been installed and an alarm will be triggered stating that the new device has the same BACnet ID as an existing device. Resolution Steps to replacing a MPM to prevent the Duplicate ID alarm being triggered: When replacing the original MPM, note the BACnet name and Instance ID. Install the new MPM and enter the same BACnet name and Instance ID. Refer to BACnet device can't be discovered due to duplicate name for more information about duplicate BACnet names.

Issue Infinity schedules (as opposed to BACnet schedules) may not work correctly if downloaded to the controller before or after the current week of events ends. Consider the scenario above, CX1 is located in LA (Pacific Time Zone) and CX2 is located in Boston (Eastern Time Zone), the Cyberstation performing schedule downloads is located in Dallas (Central Time Zone). If the schedules are configured with default download time of Sunday at midnight, CYBER1 will download the schedules to both CX1 and CX2 at (or shortly after) Sunday @ 12:00:00 Central time. Meanwhile, where CX1 is located in LA, the time is Saturday @ 10:00 PM and CX2, located in Boston, has a time of Sunday 1:00 AM The controllers can only hold one week worth of events. How a schedule download 2 hours ahead of time would affect the schedules in CX1?  Any events in CX1 between 10:00 PM and midnight would be over written with events for the same period of the following week. How a schedule download 1 hour late would affect the schedules in CX2? On Saturday @ 11:59:59 PM Eastern time CX2 runs out of events for the past week. Since it has not yet received the events for the next week, it starts repeating the events in the schedule for the week that just ended.  If the schedule events for the week that has just started but not yet been downloaded to the controller happens to be the same as the previous week, in terms of events, then this does not present any problem. But if the two weeks differ in the events they have between Sunday midnight and 1:00:00 AM, the schedule will not function correctly. IMPORTANT NOTE It is important to note that the scenarios described in this article are only applicable if a schedule contains exceptions or happens to differ from week to week in terms of the events entered in the schedule. If the schedule happens to be the same week after week, then it should not make a difference whether the controller receives a schedule download or not, from week to week. In fact, even if no download takes place at all, the schedule will function correctly as the controller will just repeat the same events week after week. Also, BACnet schedules do not have this problem, when a BACnet schedule is created Continuum sends ALL of the events in the schedule to the controller instead of just one week worth of events as is the case with Infinity schedules. Environment Cyberstation All Continuum controllers Cause Continuum Infinity Schedule download functionality does not automatically take into account time zone differences between Cyberstation and controllers. Resolution When configuring Infinity Schedules download day and time, it is very important to take into account the locale of the Cyberstation performing the download, as well as the locale of the controller receiving the downloaded schedules. Configure the schedules' download time so that the download takes place on Sunday @ 12:00:00 AM IN THE TIME ZONE WHERE THE CONTROLLER IS LOCATED. The schedules residing in CX1 in Los Angeles should be configured to download on Sunday @ 2:00:00 AM Central time which corresponds to Sunday @Anonymous user:00:00 AM Pacific time. The schedules residing in CX2 in Boston should be configured to download on Saturday @ 11:00:00 PM Central time which corresponds to Sunday @Anonymous user:00:00 AM Eastern time. Note that the schedule download engine always downloads one week worth of events starting at the configured download time. In this case all events from Saturday @11:00:00 PM to the next Saturday @11:00:00 PM will be downloaded, which will ensure that CX2 never has to repeat any events from the previously downloaded week.

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 Services for assistance. Issue Log data is not being logged into SQL. The Reports Server indicates that the database is full.   This view will be shown when logging into the WebReports interface. If this chart is not shown, the PC is not running an Express edition of SQL. Product Line EcoStruxure Building Operation Environment Reports Server Cause In most instances, the data that quickly fills the SQL database are Events. Event data fills the SQL Database and prevents log data from passing to the Reports Server database. If the data has filled within a few days, this would indicate an issue, and contacting your local support is the best option here. The Process below allows the user to stop the reporting agent from passing specific information to the Reports Server. If the data files are due to the amount of data stored, then an upgrade to the Standard/Full version of SQL is recommended.   Resolution To verify that the Events table is the likely cause of the SQL filling up, there are Standard Reports in the later versions of SQL.  The below example uses SQL Server version 13.x and shows the "Disk Usage by Top Tables."   If the Standards Reports are not available, then use the following article Building Operation Reports SQL Database Full, for instructions on how to show the details for each table.     The Process below allows the user to stop the reporting agent from passing Event information to the SQL Database: Download the latest SBO Reports Agent Config tool from the community. Load the Tool onto the Reports Server PC. Stop the Reporting Agent Using the Tool Press F7 to get to the Advanced Agent Configuration Page Change the numEventRecordToRead property to 0. This will prevent future event data from being written to the Reports Server database. Press Ok Under the Maintenance tab of the tool - there are two options under Events  Delete future events, alarms, and trends  Delete events and alarms older than... Restart the Reporting Agent This will stop any further Events from being passed through to the SQL Database.  

Issue How to upgrade remote MPMs with a Canbus, Zigbee network. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager MPM Cause Cannot connect to an MPM directly to perform a firmware upgrade Resolution This procedure explains how to perform a firmware upgrade on multiple remote devices at once, in order to save time and standardize the firmware versions across your deployment. This process will induce traffic on the network, therefore it is recommended that this procedure be performed after-hours or when it is less likely to disrupt normal operations. Step 1: Verify your monitor Manager's firmware version Ensure monitor MPM has the same or higher firmware version than the the version intended to be installed on the remote MPMs. Highlight the MPM in the Network Panel on the left side of your screen and either click on the "About" button or navigate to CFG1 object to verify firmware version. Step 2: Download and rename the firmware file The firmware can be downloaded from the Exchange then firmware file must be renamed "upgrade.bp" Step 3: Upload the firmware file to your Manager Choose the File Manager tab and click on the “Upload File” icon. A dialog box will open to select the firmware file on your local PC. Browse to the correct file and select it. Click the “Upload” button to send the file from your computer to the controller. When the file upload is completed, the file will be shown in the Upload Manager list.   Step 4: Initiating the remote upgrade Inside the File Manager panel, either right-click on the firmware file that was just uploaded and select “Add to all” to copy the same file to all the remote nodes, or drag and drop the file from the left panel onto the desired Manager on the right panel. The file will be displayed under each of the remote nodes (or a single node if the file was copied using drag and drop) under the Network panel, on the right side of the window.   In order to initiate the file transfer to the remote nodes, click the Start button. The status will change to “In Progress” and you will be able to follow the progress of each node in the Network panel. Once the file transfer is complete, the remote nodes will reset and perform the firmware upgrade. Step 5: Verify the firmware version of the remote nodes You can verify that the upgrade process completed successfully by highlighting the remote node in the left panel and then select the “Controller Configuration” (CFG1) object. The version # will be displayed in the bottom section.

Issue Need to protect Continuum Workstations from Virus and Malware threats. Product Line Andover Continuum Environment Continuum Workstation Cause There are many Anti Virus applications on the market, how to choose which one to use on a Continuum Workstation machine. Resolution We do not qualify any specific Anti Virus applications or definitions for use with Continuum software. You can use whatever Anti Virus you want on the machine Continuum is installed on as long as Continuum was installed when that Anti Virus was disabled as this can hinder files from being copied, dll's from being registered, and registry entries from being created / modified. If there are conflicts with Continuum and the specific Anti Virus application being used, you may need to add the Continuum folder and / or the Continuum processes to the exclusion lists. For details on specific environments that have been qualified with Continuum see Software and Firmware compatibility matrix for older versions of the traditional product lines.