Building Automation Knowledge Base

Issue How is a CSMC controller "Fast Run" enabled / disabled? Environment Satchwell CSMC Fast Run Cause Controller is in fast run mode, how is it returned to normal? Resolution The "Fast Run" mode is enabled / disabled as explained below. This action required the use of the service code 0280.     To view the complete user guide, please click HERE.

Issue RP-C address dial is difficult to see in poor light Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RP-C) Cause The controller modbus address setting dial is difficult to see in poor light conditions. Resolution By default, the dial is set to address '1' (there is a small arrow on the cross head dial) and the dial is numbered 1....9,0 clockwise.

Issue Xdriver is enabled,   Open the BCX1 editor, click "options" tag, display comm port attribute as"Xdriver comm1: 00000009", but there is no "xdriver" listed from the drop down menu when click the arrow on the right of default type of the comm port. Product Line Andover Continuum Environment BCX1-CR-X, 4.500065 Cyberstation 1.81 Cause Continuum support xdriver with BCX1-CR(BCX4040) from 1.82, any version earlier than 1.82 not support xdriver with BCX1-CR controller. Resolution Upgrade all the Cyberstation to 1.9X. To determine if a controller comm port is Xdriver enabled, refer to Determine if a controller comm port is Xdriver enabled.

Issue Troubleshooting 4417 DEVICE_ERR_NOADDR_I2C errors seen in Controller's Error Log. Environment Continuum Controllers Cause 0x00004417 0x00002100 0x021046e2 0x00080002 0x000000200x00004417 0x00002100 0x021046e2 0x00080002 0x00000020 "DEVICE_ERR_NOADDR_I2C" errors are related to the internal bus to the peripherals and RealTimeClock.   DEVICE_ERR_NOADDR_I2C       (no address response)      “DEVICE_ERR_NOADDR_I2C” errors are not I2 errors they are I2C errors. These errors are related to the internal bus to the peripherals (like an onboard RealTimeClock or the expansion bus (modules)).   There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module. Resolution Possible causes can be:   1. A defect with the onboard RealTimeClock. Check for 4417 errors followed by TimeSync errors and/or indications that the time clock is not stable similar to the following error lines.   01/01/1989 00:00:00.00 0x00004417 DEVICE_ERR_NOADDR_I2C (no address response) 01/01/1989 00:00:00.00 0x00010000 Clock change   2. An issue with the expansion bus modules. There may have been an expansion module installed that has been removed while a PE program is still accessing an I/O on the module.

Issue I have an Andover system that I need help with... Can you assist me with my Andover Continuum systems? I have an Andover alarm panel that got wiped out; what is the default IP address? Environment Andover Continuum Cause Phone number and email are not available online. Resolution To contact Schneider Electric for Andover Continuum system support, please visit the Contact Product Support page.

Issue Require a Lua script for using DIM modules Environment SmartStruxure Lite Cause Using a Digital Input Module and Lua script is required to view the Inputs. Resolution For Sontay's DIM4 module download the script here. For Sontay's DIM6 module download the script here. For AXIO's DIM module download the script here. For a generic DIM module download the script here. The voltage received at the AI may need tuning. Copy and paste the text into a Lua program and create the Binary Values (BV).

Issue Sigma controllers that have been cold started do not recover correctly. Product Line EcoStruxure Building Operation, Sigma Environment Sigma Server Building Operation Enterprise Server Cause Having imported a Sigma database into the Sigma Interface on the Enterprise Server, and following a controller cold start, Sigma controllers fail to fully recover. The controller correctly receives the Backup server number, but fails to request the data from the Sigma Server. Resolution This issue is resolved as follows; Data Import the Sigma Data. Stop and restart the Enterprise Server using the Software Administrator Cold start a controller to confirm that it fully recovers. Note: A  restart of the Enterprise Server will be required again if any new additional controllers are to be added to the Enterprise Server. This workaround only works for ARM7 controllers, for V53 devices, the Sigma 4.08 (3.46.79) Hot Fix is available on the Download Centre and needs to be installed at the Sigma Server machine. Note; this hotfix is a separate item to any other Sigma hotfix and the correct Sigma Transition Tool version needs to be installed.

Issue How to bring an MPM-VA online over ZigBee to communicate with the ZigBee Coordinator (which is also the MPM you have your IP interface with). Environment MPM, MPM-VA, ZigBee Cause Cannot figure out how to get the MPM-VA to communicate over ZigBee to the Coordinator. Resolution Use web interface on the bench to set up ZigBee Pro Extended Configuration on the "remote MPM-VA" to match the Coordinator's Channel, PAN ID, Extended Network ID, Stack Profile, Security Profile and Trust Center Link. Save settings and save database to flash. You can now disconnect the IP connection to the remote MPM-VA. Re-discover controllers from the Coordinator MPM. It will appear as a "peer" below the coordinator, i.e., it will not be "under it" like a Room Controller (stat) or TE2.  

Issue For unknown reason, BCX4040 goes offline with solid CPU light, and failed to ping, Webpage can't be accessed, Environment BCX4040 Cyberstation 1.80 and above Cause Not clear what cause this issue, Not all the BCX4040 with solid CPU light can be recovered. Resolution Press "reset" button on PCB board for a long time, at least over 10 seconds, if the CPU light goes off, it is possible to recover the BCX4040 Press "IP Reset" on PCB board for over 60 seconds, Maybe not bring the controller into factory default setting Ping the BCX4040, if success, go to the next steps Start Continuum, and bring BCX4040 online, then downlaod, According to the steps above, I have recovered at least 4 BCX4040 and AX5720/5740.

Issue What camera conditions does Continuum support being shown as a Continuum alarm? Product Line Andover Continuum, Pelco Environment Continuum v2.0 Pelco Video Server Digital Sentry Endura Cause Available documentation is a bit bare on specifically what camera conditions can be monitored / setup to be displayed as alarms in Continuum. Resolution According to the latest Video Compatibility Matrix, only the following video alarms are supported: Video server online/offline Camera video loss (cable connection loss only, not covering of camera lens) Motion detection (per camera) Note: Video loss and motion alarm functionality are not supported on DVX and DVXi Video Servers.

Issue Is it possible to have different stop bit settings in different Serial Modbus devices on the same bus? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Modbus serial communication Cause In Building Operation there is an "Auto" setting for the Serial Modbus communications "Stop Bit" setting. This could be interpreted as "automatically" detecting the Serial Modbus devices stop bit setting. Resolution The "Auto" setting is only designed to detect how many stop bits are required in certain circumstances, such as when the parity setting is set to none and therefore 2 stop bits must be used. The settings used are the Serial Client settings for the entire bus and all the Modbus devices have to be set to match the Serial Client.

Issue When SE7000/SE8000 Series Room Controllers are bound to the MPM via ZigBee, "Effective Occupancy" does not follow "Occupancy Command" if the COV box is checked. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment SSL MPM SSL SE8000 SSL SE7000 Cause Data type mismatch Resolution Uncheck the COV box for Effective Occupancy

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 Error when starting Continuum 1.9: Cannot find acc video recording service. Environment Windows XP SP3 Continuum Cyberstation Cause As with many software installations, installing with anti-virus running will block some registrations and registry entries. Resolution Install Continuum with admin privileges Turn off anti-virus software Stop any firewalls during Continuum installation

Issue After configuring a BACnet Schedule in a BCX or a b3 controller, it goes into Fault with its Reliability field showing "ConfigurationError". Environment CyberStation WebClient BCX40xx b3 BACnet Schedule Object Cause Configuration of BACnet schedule Incorrect point type used to configure BACnet schedule Resolution For each object type within BACnet (input, numeric, trendlog, etc.) each object property identifier (property) has an associated data type.  A list of data types for the each property can be found in Chapter 12 of the BACnet spec under the section for each object type.  The correct data type to configure in the schedule is determined by the Object property that is being controlled by the schedule object.  When using a schedule to control the value of a BinaryInput, BinaryOutput and BinaryValue objects, the Data Type that should be used is Enumerated. When using a schedule to control the value of a AnalogInput, AnalogOutput and AnalogValue objects, the Data Type that should be used is Real. When using a schedule to control the value of a MultiStateInput, MultiStateOutput and MultiStateValue objects, the Data Type that should be used is Unsigned Integer The Schedule object can be tricky to configure, however. There are several properties (Weekly_Schedule, Exception_Schedule, Schedule_Default) that must contain the same data type for all events. Since Enumerated is the “default” data type, the user may need to manually remove any existing events with the Enumerated type and replace them with the desired data type. If while configuring the schedule a message similar to the one above is displayed and accepted  all the events MUST be deleted otherwise a configuration error will result.

Issue MNB-1000 BACnet MS/TP communications do not auto-baud (synchronize). Product Line TAC IA Series Environment I/A Series MNB-1000 Firmware 1.2 and above Cause I/A Series MNB controllers with firmware 1.2 and above support baud rate synchronization (auto-baud) for BACnet MS/TP communications. This auto-baud feature is available if the device is configured for BACnet MS/TP communications only.  If the MNB-1000 BACnet Ethernet (or BACnet IP) communications are enabled, even though this is not being used in normal operation, it will cause the auto-baud to be disabled. Resolution 1. Disable the BACnet Ethernet (or BACnet IP) communications on the MNB-1000. Use a compatible RS-232 to RS-485 converter or the Roam IA to access the MNB-1000 via BACnet MS/TP communications. 2. Set the baud rate of the MNB-1000 MS/TP port to a fixed speed that matches the configured baud rate of the RS-485 port of the Jace. - Connect to the MNB-1000 using the WorkPlace Commissioning Tool. - Go to the MNB-1000 device properties, MS/TP tab, and set the baud rate of the MNB-1000 MS/TP port. See the example below.

Issue For various reasons it maybe necessary to change a b3's device id, one way to accomplish this is using the RoamIO2 with the BACnet Service Tool. Product Line Andover Continuum, EcoStruxure Building Operation Environment B3 RoamIO2 BACnet Service Tool Cause The device ID of a b3 controller needs to be changed. Resolution Disconnect the b3 from the MSTP network and connect the RoamIO2 directly to the b3's service port. Launch the BACnet Service Tool and in the 'View' menu de-select 'By Networks' and 'BACnet Only' menu entries   Click the green icon to make the RoamIO 2 join the MSTP network and discover the b3. (NOTE: If the b3 has not been previously assigned a valid MAC ID see How to change b3's mac ID using RoamIO service tool) Once you see the b3 in the object tree select it then switch to the grid view and double click on the device id value on the 'object-identifier'  field. In the 'Property View/Set' window enter the new device id to set and click on apply. You should get a feed back of 'Success!' if the device id was changed.

Issue XIF files for Version 1 and Version 2 of MNL controllers Product Line EcoStruxure Building Operation, TAC IA Series Environment SmartStruxure with MNL Cause Not available on other online resources Resolution Download the zip file available here for the following profiles:

Issue As part of a site power feed problem investigation where varistors are being blown, how are they connected to the power feed? Environment i2920, b3920, b4920. Cause When a site is experiencing power problems and the mains input varistors blow, it is required to know how the damaged varistor is connected. Resolution The 3 varistors are connected between: Live and Earth, Neutral and Earth, Live and Neutral. The attached sketch shows how  the 3 varistors are connected. The connections are the same for the i2920 and b4920.

Issue When using TAC Vista 5 Demo License and Site License at the same time, Vista returns “Your application was not able to obtain a license because the FLEXnet license server manager could not determine where to find the licensing data it needs. Please choose one of the following: Specify the License Server System Specify the License File Product Line TAC Vista Environment Vista 5.X.X with Site License and Demo License Cause Using Vista 5 Demo License concurrently with Site Licenses, or having an expired Demo License in the License File folder with Site License may cause Vista ignore the Site License or not fully read the Site License. Resolution Remove Demo License from the License File folder. Restart the computer. If the issue still exists, follow Switching from the Demo license to the site License in Vista 5.1.7 or older.