Building Automation Knowledge Base

Issue The object identifier of a BACnet device (device id) must be unique internetwork-wide, different vendors use different methods for calculating the device id default value. When integrating devices from different vendors sometimes it become necessary to change a device's default object id. Product Line Andover Continuum Environment bCX4040 b3s Third party BACnet devices Cause BACnet integration Resolution If the BACnet device is a Continuum device (bCX4040 or b3), Continuum provides a mechanism for changing the default device id. For a third party BACnet device, VTS can be used to write to the Object Identifier of the device in order to change the device id. Note that this will only work if the device manufacturer has made the object identifier for the device object writable. Click here to download VTS Click here to see the procedure to follow to set a third party device id using VTS.

Issue Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate with EBO Script programming Product Line EcoStruxure Building Operation Environment b3 Infinet Building Operation Server Script Programming Cause Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate or cannot be used with EBO Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType

Issue Controller loses data following power failure or mains noise (from transients or spikes). Product Line Andover Continuum Environment All CX, ACX, i2, bCX, b3 controllers Cause Controllers are exposed to operating conditions outside their operating envelope and tested limits. This can cause them to reset, go offline or lose data. In extreme circumstances, poor installation can take controllers outside their operating envelope and cause damage requiring a repair. Resolution If a controller is setup on a bench with a clean power supply and the correct grounding, you will be able to turn off/ on the power and the controller will warm start every time. This test will confirm the controller is operating correctly, not faulty and that the software settings are correctly set for warm starting. Also that the RAM backup battery is connected and operating. If site resets, lockups, loss of memory or other corruption are seen on a site, then here are some of the installation issues to consider: Grounding - All controllers require a clean low impedance earth to sink all of the noise and emission energy a controller may be exposed to. The noise protection circuitry within a controller is designed to dissipate this energy down to earth, if this path is not low impedance the energy can cause a controller to reset or even be damaged permanently. Shared Ground - The earth cable to the Controller should not be shared with any other equipment that is a high inductive or capacitive load, these can generate noise spikes back into the controller. This includes motors (pumps/ fans etc) lighting circuits (capacitive loads), inverters (high frequency noise). Induced emissions - The controller should not be installed near any equipment that may induce excessive radiated emissions into the unit, the radiated emissions from Motors, inverters, radio & microwave equipment, lighting circuits, power wiring can all produce radiated emissions that could exceed the specified limits of the Controllers. By fitting the controllers into earthed metal enclosures you can minimize the external emissions by effectively creating a Faraday cage protecting the controllers circuitry. Power feed - The power requirements for every controller is defined in its datasheet with the defined tolerance, taking the power levels outside these limits can cause incorrect operation. Power spikes - Surges or spikes in power feeds or connection I/O cabling can cause controllers to reset, lose data or even become damaged. Fitting varistors to the power supplies and across any output loads can minimize the impact on the controller, See What Varistors should be used?. Shared Supply - The power feed to a controller should never be shared with other equipment that can generate electrical noise. Never use the same supply to power both controllers and field equipment like valve/ damper actuators in BMS systems or magnetic door locks in Access control, both actuators and the solenoids in Mag locks can generate large back EMF pulses into the controllers that can cause resets or even damage.. Fitting power filters or an external UPS on the controller can protect it from spikes on power up/ down, it is however always best to remove the noise spikes at source, so fit filters the generators, motors, contactors etc. It is also possible for the above issues to cause Infinet networks to Reconfig as well as other networking problems. Note: All controllers are approved and tested to the defined limits for FCC and CE induced and radiated emissions as detailed in the datasheets, for a controller to fail, restart or lose data it must be exposed to levels exceeding these specifications. They are not however power equipment and cannot be exposed to the noise levels power and industrial controls equipment is designed to withstand.

Issue What new features are planned for inclusion in future product releases? Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Access Expert, EcoStruxure Security Expert Environment All product ranges Cause Information required on future Product Marketing plans. Resolution This document is no longer published on the Download Center by Product Management. For further information on the future product planning please contact the Product Manager for the specific product in your region. Americas: Americas.EcoStruxureBuilding@schneider-electric.com EMEA: EMEA.EcoStruxureBuilding@schneider-electric.com Asia Pacific & India: AsiaPac.EcoStruxureBuilding@schneider-electric.com

Issue How to use the Telnet command to troubleshoot network connectivity and check for blocked network ports. Product Line TAC INET, TAC Vista, Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, Field Devices, EcoStruxure Building Operation, Other, Pelco, EcoStruxure Building Expert, Access Expert, Security Expert Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet.     Open Windows Command Prompt Enter :telnet <address_of_remote_server> <port_number>" - telnet 192.168.1.2 443 Result if Port open: blank window with blinking cursor Result if Port closed: error message displayed similar to "Connecting To 192.168.1.2…Could not open connection to the host, on port xx: Connect failed" The example above test for connectivity against the remote server that has the IP address of 192.168.1.2 over port 443

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. 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 Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Cause This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If the baud and MAC id have been set successfully, the device will automatically pop up in the tree but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right click on the device then select 'Update OS', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)

Issue 3rd party BACnet Gateway can be seen  and points found when performing "send to database" but the Life Safety points do not show up. Product Line Continuum BACnet Environment Andover Continuum, EcoStruxure Building Operation Cause We do not currently support the BACnet Life Safety objects with the Andover Continuum or EcoStruxure Building Operation product lines Resolution Use an object that we do support, either an AV (Analog Variable) or MV (Multistate Variable) would probably suffice as long as the 3rd party Gateway can provide this instead of the Life Safety objects. See our BACnet PICS statements at the link below that show what BACnet objects each of our products support. https://www.bacnetinternational.net/btl/index.php?m=20

Issue b3 controllers sometimes get stuck in bootloader mode (refer to Why do Continuum controllers go into bootloader mode). In b3 devices, this is indicated by the CPU LED blinking at at about half the rate of normal CPU LED blink rate. Product Line EcoStruxure Building Operation,Andover Continuum Environment All b3 devices Cause Need a way to recover b3 stuck in boot loader in the field. Resolution Disconnect the b3 device from field bus and connect RoamIO directly to device. In the BACnet Service Tool, de-select the view by Networks option then click the green 'Connect' icon Observe the RS-485 LEDs, both on the b3 device and the RoamIO, if the connection is established the green connect icon on the service tool will have changed to red but no device will be shown since the application is missing in the device, the TD and RD LEDs will be blinking rapidly indicating the RoamIO is communicating with the boot loader in the device, if this is NOT the case then stop, recovery will not be possible, otherwise proceed to next step. In the 'Tools' menu, select 'Update all B3s', then send the appropriate firmware file for the device. After the update operation is complete, re-start the b3 device  

Issue b3/i2 885, 885-V,, 887 and 887L needs Internal Resistance values for voltage inputs but some devices like SpaceLogic SLA do not publish these values Product Line Andover Continuum, EcoStruxure Building Operation Environment b3885, b3885-V, b3887 and b3887L i2885, b2885-V, i2887 and i2887L Cause These controllers have a pull up resistor that cannot be disabled, unlike most of the i2/b3 range The below is taken from the b3 technical manual. Resolution Not all devices publish the Internal resistance,  for example the SpaceLogic SLA, this device has a varying Internal Resistance, but using a value of 25 Ohms, will ensure the maximum error is less than  0.3% of full scale (5ppm for CO2, 0.15 degC) Generally for most devices, where the internal resistance of a device is not available, it can be calculated by noting the voltage on the output device unconnected, then connected to the i2/b3 device and also noting the actual reading (Temperature, CO2 level, Humidity)

Issue The motion sensor on the secure side of an access control door is not fast enough in sending the request to exit signal to the controller which result in nuisance (forced entry) alarms. How is this prevented in Continuum?  Product Line Andover Continuum Environment CyberStation ACX5740/ACX5720 AC-1 family ACX781 Cause The motion sensor on the secure side of an access control door is not fast enough in sending the request to exit signal to the controller which result in nuisance (forced entry) alarms. How is this prevented in Continuum?  Resolution The channel tab of the Continuum door editor has a field for this purpose. It is called ForcedEntryDelay. Simply enter the number of seconds. The delay will allow more time for the request to exit signal to be seen by the access controller, avoiding the nuisance forced entry alarm. 

Issue Is there a way to see what personnel objects are in the Netcontroller? Also, there is no way to send the personnel records (or area objects) from the controller into the SQL DB. Doing a 'Send to database' will NOT send personnel records or area objects. Product Line Andover Continuum Environment All Access Controllers Cause Viewing personnel records Resolution There is no way to view the personnel records stored in a NetController.   Check to see if the personnel record has been distributed to the controller using the Access Distribution View filtered by the controller. Set to the controller's ACCNet Id for local validation only.  Use the AccessServer system variable on the controller (accnetid found in the controller's config page) and set it to the Accnetid of the controller, not a Workstation or the Primary Access Server (typically in the 191-254 range). Doing this specifies that the system looks only at the controller's internal database. If a cardholder can get 'valid access' to a door (associated with a specific controller) and local validation is used, then the cardholder record is in the controller's local database. If the cardholder can only get 'valid access' when a workstation accnetid is set for the AccessSystem variable in the controller, then the cardholder has not been distributed to the controller.

Issue Modbus XDriver for BCX1-9640/4040 (ModbusRTU_bCX_xxxxxxx.xdr) on comm2 for RS-485 does not work even when the comm2 port says that the driver is installed, no errors and the comm parameters match the Modbus protocol device (ie, 19.2k, n, 8, -). Product Line Andover Continuum Environment bCX1-9640/4040 Controller Modbus XDriver Cause Check the Communication Configuration Point (Function Code 99) of the XDriver. Resolution Function Code 99 is used to select between RS-485 and RS-232 when using a bCX1-9640/4040 controller with Modbus XDriver installed in Comm2 port. Unlike the Modbus XDriver for CX ModbusRTU_2xxxxxx.xdr), the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) requires user to set correct value to the FileNumber attribute of Function Code 99 (Communication Configuration Point ). If the FileNumber attribute of the Communication Configuration Point is not set to "1", the Modbus XDriver for bCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) uses the default value, which is "0". When the FileNumber attribute is set to "0", the Modbus XDriver for BCX1-96404040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-232. When the FileNumber attribute is set to "1", the Modbus XDriver for BCX1-9640/4040(ModbusRTU_bCX_xxxxxxx.xdr) considers the interface as RS-485. For detailed information, refer to the Modbus RTU XDriver User Guide on page15: Function Code 99 – Communication Configuration Point.

Issue Example programs for the xP Display and LD-1 Product Line Andover Continuum Environment XP Display LD-1, LD1, LD 1 ACSM Cause Need example code for these displays to act as a starting point for programming  Resolution example programs for the xP Display.  example programs for the LD-1.  Note: These applications were developed by a UK branch and should be used as a starting point for your specific application. Further information on the programming of these displays is available in The Exchange Download Center for the specific devices. xP-Display Installation and User Guide LD-1 Installation and User Guide

Issue Incorrect settings in the BCX will prevent BACnet communication. Product Line Andover Continuum, TAC INET, TAC Vista Environment BACnet MSTP BACnet IP BCX Xenta 913 Cause Because the Xenta 913 has a limitation of 127 addresses, the default BACnet Address will most likely be out of range. Resolution The BCX4040 must be addressed properly to allow BACnet communication to the Xenta 913. The setting can be changed on the BCX's Controller Configuration page by accessing the controller via IP address to its web interface. On this page, you will see a setting for BACnet Network ID Comm2 which is the device's BACnet address. This number must be unique on the BACnet Network and must range from 0-127.   To Enable BACnet IP communication: Modify the BACnet Ethernet settings from the web interface. Set the BACnet Ethernet Enabled to Yes Set the BACnet Network ID Ethernet. This is the device's BACnet address. This number must be unique on the BACnet Network. The BACnet Device Id is by default the last 7 characters of the BCX serial number and must be unique to all devices in the Continuum network. Many people try to set the BACnet Device Id field to represent a BACnet address but this is not correct. This setting does not affect the Xenta 913 in any way.

Issue Converting the Velocity Pressure measured by the pressure sensor to Flow velocity (CFM) Product Line Andover Continuum,TAC INET,TAC Vista Environment Air flow measurement / balancing Cause Requirement for converting the velocity pressure to flow velocity (CFM) Resolution To calculate Air Flow in Cubic Feet per Minute (CFM), determine the Flow Velocity in feet per minute, then multiply this figure by the Duct Cross Sectional Area. Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A)   Determining Flow Velocity The easiest way to determine Flow Velocity is to measure the Velocity Pressure in the duct with a Pitot Tube Assembly connected to a differential pressure sensor. The Pitot Tube Assembly includes a Static Pressure Probe and a Total Pressure Probe. A Total Pressure Probe, aligned into the airflow, senses the duct velocity pressure and the static pressure, which equals the total pressure. A Static Pressure Probe aligned at a right angle to the airflow senses only the static pressure. The difference between the total pressure reading and the static pressure reading is the Velocity Pressure. If you connect the Total Pressure Probe to the HIGH port on a differential pressure sensor and the Static Pressure Probe to the LOW port on the differential pressure sensor, then the sensor’s output will be the Velocity Pressure, as shown in the figures below. The Flow Velocity is then determined with the following equation: V = 4005 x Sqrt(ΔP) V = Flow Velocity in feet per minute. Sqrt() = Square root of the number in the parenthesis. ΔP = The Velocity Pressure measured by the pressure sensor Example: Measuring a Velocity Pressure of .75” W.C. equals a Flow Velocity of 3,468 Ft/Min. V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min   Determining Duct Cross Sectional Area After obtaining the Flow Velocity from the previous procedure, that figure is now multiplied by the Duct Cross Sectional Area to determine the Air Flow in CFM. There are two different equations for determining the Duct Cross Sectional Area, one for round ducts and one for square or rectangular ducts. The equation for a round duct is: A = π x r 2 A = Duct Cross Sectional Area π = 3.14159 r = radius of duct in feet The equation for square or rectangular ducts is: A = X x Y A = Duct Cross Sectional Area X = Duct height in feet Y = Duct width in feet. Example: An 18” diameter round duct has a Duct Cross Sectional Area of 1.77 Ft 2 A = π x r 2 or A = 3.14158 x .5625 18” diameter is 1.5 feet, therefore the radius is .75 feet • r 2 = 0.752 = 0.5265 • π = 3.14159 A = 3.14159 x 0.5625 = 1.77 Ft 2   Determining Air Flow in CFM After obtaining the Flow Velocity and the Duct Cross Sectional Area from the previous two procedures, the Air Flow in CFM is determined by multiplying the two: Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Example An 18” diameter round duct with a Velocity Pressure of .75” W.C. has an Air Flow of 6,128 CFM The Flow Velocity is 3,468 Ft/Min. V = 4005 x Sqrt(ΔP) V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min The Duct Cross Sectional Area is 1.65 Ft 2 A = π x r 2 π = 3.14159 • r 2 = 0.752 = 0.5625 Duct Cross Sectional Area (A) = 3.14159 x 0.5625 = 1.77 Ft 2 The Air Flow in CFM is 6,128 Ft 3 /Min Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Air Flow in CFM (Q) = 3,468 Ft/Min x 1.77 Ft2 = 6,128 CFM

Issue Inovonics Wireless Interface problem Product Line Andover Continuum,TAC Vista Environment Inovonics FA7403 receiver Inovonics EN4000 Universal Serial Receiver Cause Inovonics provides an interface to access wireless temperature sensors. The FA7403 receiver can be used to interface with Xenta equipment or Continuum equipment, however these interfaces use different protocols. Resolution The Xenta equipment requires a hexadecimal protocol which corresponds to the FA7403 receiver. The Continuum equipment requires an ASCII protocol which corresponds to the FA7403-ASC receiver. If you have the wrong receiver for the equipment you are trying to interface with then contact Product Support for steps to reconfigure this device. Note: Inovonics EN4000 Universal Serial Receiver**, REPLACES FA7403  

Issue Xenta 913 Device Template cannot map to "native" BACnet using 485 Virtual Link Layers. Product Line Andover Continuum,TAC Vista Environment Xenta 913 BACnet Cause The Xenta 913 cannot connect to anything below the IP layer. "Virtual Link Layer" is not able to be used if the points are not exposed at the IP level there is not a way to address defined modules below. Resolution Any point that needs to be exposed at the IP level must have the ability to be mirrored in the BACnet IP device. If the IP device does not have the ability to mirror the 485 layer points, the 913 will not be able to map them.                              

Issue In this specific instance the site was upgraded to Continuum v1.94 and the Cyberstation OS upgraded to Windows 7 64 bit, fresh install. Local Administrator account was logged on to perform Database Initialization which succeeded and Continuum was able to start-up and connect to the SQL Server. Restarting and logging in with another windows user with administrative privileges results in being unable to connect to the database. Logging out and then in as Administrator and re-initializing the Workstation into the Database re-establishes the connection and Continuum is able to be run again. This fails again when another user is logged on. Product Line Andover Continuum Environment Andover Continuum Cyberstation Windows 7 64-bit Cause Windows administrative privileges are required to initialize and make a connection to the database. Resolution Run Database Initialization as an Administrator and re-initialize the Workstation into the Database. Shut down all Cyberstations. Right-click Database Initialization and select "Run as... Administrator".  In Win7 you may need to "Shift-right-click" and select 'Run as a different user...' Select Workstation, confirm details, input password and select OK.

Issue What is the procedure on transferring Continuum from one PC to another PC? Product Line Andover Continuum Environment CyberStation SQL Cause Workstation hardware needs to be upgraded or replaced altogether Resolution Collect information from the existing machine Collect all IP address, DNS server and Windows Server IP information from the existing workstation. Run Continuum Database Initialization on the existing machine. Select Workstation and record the following information. Workstation Name Folder Name Device Node ID Network ID Data Source Name Database Name User Login ID Server Name. Verify that correct Database Passwords are known for both Andover97 user and sa accounts Start Continuum and run PinPoint. From the View menu select Options Record the folder path indicated under Graphics (Pin Files) and archive these files.  Record the folder path indicated under Background and archive these files.  If any customization has been done to the menu pages (i.e. hot spot) then the User Profile folder( C:\Program File\Continuum\UserProfile) should also be archived. Backup the Continuum Database Move the database backup and the contents of the archived folders described above to a secure external drive or a network folder (not on the workstation itself). Install CyberStation on the new machine Before removing the existing machine from the network, start the new Workstation without connecting it to the network. Configure the IP Address, DNS server and Windows Server IP address collected from the existing machine. Install CyberStation on the new Workstation PC Note: Do not forget to disable all Virus Protection and Firewalls.  When prompted run Database Initialization Use the information collected on the existing machine to initialize the StandAlone Database. Use the information collected on the existing machine to initialize the WorkStation. Start Continuum and verify that the CyberStation operates normally. Copy data collected from the existing workstation onto the new workstation. Copy Database backup file to the Backup folder under C:\Program Files\Microsoft SQL Server\ Copy contents of the archived Graphics folder to the same folder on the new workstation PC. Copy contents of the archived Background folder to the same folder on the new workstation PC. Copy contents of the archived User Profile folder to the same folder on the new workstation PC. Run PinPoint From the View Menu select Options Under Graphics (Pin Files) enter the folder path to where the Graphics files have just been copied (see above). Under Background enter the folder path to where the background image files (see above). Select the Check button and verify that a failure notice (a red "X") does not appear beside any item. Close PinPoint Restore the Continuum Database. On the new workstation, run SQL Server Management Studio Express. Navigate to the Continuum Database. Right click on the Continuum Database, select Restore Browse to the folder where the existing Database backup file was copied to.  When the restore has completed successfully. Change the DB Owner: Right clicking on the Continuum database Selecting new query. In the query window type SP_ChangeDBOwner Andover97 From the tool bar select Execute. The result window should return............Command(s) completed successfully Reset the passwords for Andover97 and SA Open Security from the main tree, Select Logins. Right click on Andover97 and select properties enter and retype new strong password password, retype the correct password. Repeat for SA password. Now restart the PC. Run Database Initialization Under StandAlone, update the database. Re-Launch Continuum CyberStation and verify that CyberStation is working properly. Shut down the new workstation. Swap the workstations Shutdown the existing workstation and remove it from the network. Connect the new workstation to the network Start the computer. Launch Continuum and verify all functions are operating as expected.

Issue When trying to use WriteProperty to a 3rd Party BACnet device the following error is generated : "An attempt has been made to write to a property defined as inaccessible through the BACnet protocol write service" Product Line Andover Continuum Environment BACnet  Cause The error can be seen when using WriteProperty OR when attempting to Manually Command a BACnet Point on a 3rd Party Device Resolution The property that is being commanded, is not available to be written to in the 3rd party device. Many properties and object classes cannot be written to on BACnet devices, this is often defined in the devices PIC Statement which has hopefully also been BTL Tested. Some BACnet devices allow writing to be enabled/ disabled, but this must be set up on the 3rd Party device itself depending on the site requirements.  An example of this is in the Jace unit where there is a regular BACnet user that has no write capabilities from 3rd party devices, so to allow this requires a tick a box for "Super user".