Building Automation Knowledge Base

Issue Provides additional setup information for the G3 ASD (tacAsd) driver implementation. Environment G3 ASD (tacAsd) driver (all revisions) Cause None Resolution G3 ASD (tacAsd) driver setup basics ...   Monitor properties Ping Enabled = true Ping Frequency = 5m change to 1m Alarm On Failure = true Startup Alarm Delay = 5m The baud rate sync properties is the mechanism that synchronizes the baud rates for the ASD bus. Upon reset, ASD devices initialize to 1200 baud and it is this mechanism that locates those devices and sets the baud rate to 19.2K or 9.6K (if PEMs are used on the bus). These values are part of the ASD specification and should not be changed. Last Time Sync is the last time a successful sync occurred Baud Rate Sync Time = 1m Baud Rate Set Timeout = 0.2s Baud Rate Set Repeat = 1 Baud Rate Change Millis = 800 Total Devices indicates the total number of devices active. Total Down indicates the total number of down devices. Scan Time indicates the total time to poll through the list if devices. The ASD communications protocol is designed to exchange most data between the host (ENC) and device with one transaction. This means that typical data (e.g. EMS, etc.) is written to the device as part of the request and response data (e.g. Window, Output, Diagnostics, etc.) in one transaction. In this case, the scan time is 6.9 seconds for 33 devices or approximately 4.5 devices per second. Tuning Policies (Default Policy) Min Write Time = 0 Max Write Time = 0 Write On Start = false Write On Up = false Write On Enabled = false Stale Time = 0 Note: The stale time actually involves the proxy point objects. The polling mechanism still continues and the internal point information is still updated. The driver does not implement the interaction between the point updates and proxy point stale. The values should be left at their default settings. Poll Scheduler Poll Enabled = true Fast Rate = 5s (defaults to 1s) Normal Rate = 10s (defaults to 5s) Slow Rate = 30s (defaults to 30s) Typically set the Normal Rate based upon the rules specified in the R2 documentation or (Normal Rate seconds = Number of devices / 3.5). For example, a network with 33 devices would be set to (33 / 3.5 = 10 seconds). As indicated earlier, the driver inherits the basic driver properties and mechanisms. G3 implements a complex poll scheduling mechanism that automatically determines and continually adjusts the poll list to achieve the most efficient polling. Retry Count The retry is only used in the event that a response from an ASD device is not received.  This value defaults to 1 and can be increased if needed to a maximum of 3 if devices are unable to respond to the initial message and one subsequent retry,  Devices that do not respond to the initial message may indicate a potential issue with the ASD bus. Response Timeout This is the amount of time the driver will wait for a response to a request before retrying the request.  This value defaults to 2 seconds and should not be changed. Inter Message Delay This value defaults to 0 seconds and should not be changed.

Issue Which files can be backed up safely with an automatic/manual method. Environment Sigma (All) Cause Backing up a live Sigma system is not a recommend as copying ‘live open’ files can not guarantee the integrity of the data. Resolution For either backup method (automatic or manual) those files which could be potentially 'open' by Windows should not be backed up unless the Sigma server and clients have been shut down.  1. Those data locations that can be backup safely while the Sigma is running are those in which archive data is stored, namely; a.  C:\Sigma\Data\ArchivedAlarms b. C:\Sigma\Data\ArchivedLogs c. C:\Sigma\Data\ArchivedTransactions Removing the files from these locations should only be done as a space saving measure as Sigma can be configured to view these data files by the user. 2. For all other files the recommendation is to shut the system down (clients and server) before taking the backup. 3. Restoring data must only be performed after shutting down the system first.

Issue I cannot logon to an AC256 or AC8 controller. My AC256 Xdriver has stopped communicating with the AC256. Environment AC256 AC256+ AC8 AC8+ Cause Unable to establish communications with an AC256 type controller. Resolution The attached document contains a thorough set of procedures for troubleshooting communication issues between an AC256 controller and a computer that is running a terminal emulator program such as ProComm or HyperTerminal. This requires that the computer have a available serial port or a USB to serial converter.  Troubleshooting AC256+ Comm Issues.doc

Issue Adding entries to the Web.config file during installation. Environment WebClient installation. Cause Unclear instructions in webClient Planning and Installations Guide. Resolution When modifying the Web.config file located in: C:\\Program files\Continuum\DNWACServerFactory Add the following lines before the close Configuration tag <system.webServer> <security> <requestFiltering allowDoubleEscaping=”True”/> </security> </system.webServer> </configuration>

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 After upgrade of Building Operation and / or I/NET, I/NET alarms and events have stopped updating within WorkStation. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.4x Integration with Enterprise Server EcoStruxure Building Operation 1.8 and above Cause Within the I/NET Seven SQL database table [InetDb].[dbo].[Events].[EventId], the EventId has not incremented correctly, so there is a missing EventId (causes unknown). Because of this missing EventId Building Operation waits at this missing ID to appear before updating its own event.db database. Since this ID will never show, no events will ever be passed through to Building Operation and effectively stops any I/NET events appearing within Building Operation WorkStation This EventId is seen in a registry entry called NspAmtEventId under the following path: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\CSI - Control Systems International\I/Net 2000\Configurations Resolution Current workaround is to manually edit this registry key NspAmtEventId value to: A value above the highest [InetDb].[dbo].[Events].[EventId].value - if the past events are not required. OR Increment its value by 1 if all past values are required to be retained. i.e. If NspAmtEventId = 82237682 typically only needs to be changed to 82237683 to correct this issue. If not then you should check the [InetDb].[dbo].[Events].[EventId].value After editing this registry value the Enterprise Server service needs to be restarted, after which events will then start to be processed by Building Operation. It should be noted if you use option 2 above that there will be some time for all this data to be updated within Building Operation and there may be some bogus (old) alarms appear, which should be taken into consideration before implementing this resolution.

Issue How to enable Xdriver on a CX9200 Environment Continuum Cyberstation CX9200 Cause When Infinity chips are installed on a CX9200 controller, it will not accept the XDriver upgrade cookie.  Attempting to change the commport configuration to Xdriver will return an error "Invalid Mode." Continuum chips are needed to properly apply the cookie. The controller can then be returned to Infinity by replacing the Continuum chip set. The Xdriver can then be used. Most commonly, the issue is due to the Infinity chip set not allowing the XDriver upgrade, but the chip set is not properly identified before the Xdriver upgrade is attempted. Resolution Enable an XDriver on an Infinity CX9200 must be accomplished from a dumb terminal connection: Log on to the controller via Hyperterminal Load -o -m with the XDriver cookie file provided by the repair department. Go to the Hyperterminal Transfer pull down menu and select "Send to Text File" and select the file as provided by Repair. Hit Enter to start the transfer. Send to database from the Continuum Explorer and only select the specific CX9200 controller. When the upgrade has completed, power down the controller, then repower the controller. Verify that the ACCSetEEVal string point in the CX9200 has been created. Check the Options tab of the Continuum controller editor and verify that the commport has been properly enabled for XDriver.

Issue When integrating a Integral DVR system Vista crashes Video does not work in Vista CCTV video loss in Vista Product Line Pelco, TAC Vista Environment Vista 5.1.3 Vista Integral DVR SDK v6.6.1.57 Integral DVR SDK v7.0.8 Cause Vista uses the same SDK as Controlpoint uses for an Integral DVR system, this mainly means that Vista SDK needs to be at the same versions as Controlpoint's SDK. A good example of this would be that Vista 5.1.3 use SDK v6.6.1.57 and Integral Digital sentry 7 use a newer version of SDK that is not compatible with SDK v6.6.1.57, a integration of this system then causes Vista to crash. An integration with Vista 5.1.3 would need Integral Digital Sentry 4.1/4.2. Please reference Vista Video Compatibility for more information. Vista 5.1.5 has SDK 7.0.8.0 and it appears that HD support was not included prior to SDK7.0.24.0 Resolution Make sure you have the correct version of Integral Digital version versus Vista version.     5.1.5 5.1.4 5.1.3 5.1.2 5.1.1 5.1.0 5.0.3 5.0.2 5.0.1 5.0.0   Integral Digital Sentry 4.1/4.2 X X X X X X           Integral Digital Sentry 7 X X    

Issue Provide the information required to support ProView for LON with Niagara G3 and N4 Product Line TAC IA Series Environment I/A Series G3 (3.5.34 or higher) I/A Series Niagara N4 (4.1.27.20 or higher) ProView for LON (MNL-PROV-WAL) Cause Required files for configuring the ProView for LON display with G3 and N4. Resolution Support for ProView for LON with I/A Series G3 and N4 requires the download and installation of the Distech Controls EC-NET-AX Support Package and EC-Display Configuration files.  Those files are available for download from The Exchange Download Center. Download the following files. BCS Distech Controls EC-Display Configuration v3.4.369 Setup.zip Distech Controls EC-NET AX Support Pack v4.4.17198.1 Setup.zip Unzip the files and run the executables to install the Distech Controls EC-NET-AX Support Package and Distech Controls EC-Display Configuration files. Follow the instructions to install the version(s) required. Install the Distech distribution file into the ENC (if required) using the platform distribution installer. The distribution file will be located in the Distech Controls Files directory added to G3 or N4 during the installation process. Open the distechControls palette (LonWorks - Services container) and add the LonWorksWizardService to the Services. Open the Drivers - ConfigurableControllers container and add the EcDis210 device object to the LonNetwork. Commission the ProView device using the LON Device Manager. Right-click on the EcDis210 and select Views - Ec Dis Wizard to test the wizard connection and launch the display wizard.

Issue How to setup user photos so they are shown when accessing through a Door. Product Line EcoStruxure Security Expert Environment Security Expert Server Cause Unsure how to add photos to users and have them displayed when that user is accessing through Doors. Resolution There is an option for User photos in Security Expert and the Photo Id option is included with the base Security Expert license. With this "Photo ID" feature enabled you will see the Photo tab on the User object and will then be able to add photos to your users.   1. You can associate a photo to your users in the Photo tab of Users | Users.   2. In Monitoring | Setup | Status Page Editor, you can set the Style to Display User Image. Doing this will show the users photo with the access event.

Issue Cannot get comms stats from the DNN or controllers below the DNN. Product Line Satchwell Sigma Environment Sigma Communication DNN RIP Listener Windows XP Persistent routes Cause The Sigma server 'learns' the network architecture by listening to RIP messages broadcast by the network DNN's.   This is performed by RIP Listener which by default is not enabled on Windows XP. Resolution Enable RIP Listener on the Sigma Windows XP server by; In Control Panel select 'Add or Remove Programs' From the left hand bar select 'Add/Remove Windows Components' Highlight 'Network services' and select 'Details' Enable 'RIP Listener'   Select 'Next' and then 'Finish' OR Add persistent routes as an addition to RIP Listener as a backup or if RIP v1 is not permitted on the system see Persistent routing on the Sigma server. Use the DOS Command ROUTE PRINT to list the dynamic and persistent routes, check that the gateway address and network addresses are correct.

Issue Software download location. Where can I download "MicroNet View's Monitor Tool" dongleless software as advised in: PA-00145 - Satchwell MicroNet Range Rationalisation Product Line Satchwell MicroNet Environment MicroNet View Monitor Tool   Cause The MicroNet View dongleless Monitor Tool, software can no longer be ordered, it is available as a free download. Resolution Download the software from The Exchange or Click here to be linked to the Monitor tool. (This link will open a new page) Click here to be linked to the SNP I/O server. (This link will open a new page) Click here to be linked to the NCP/ARCnet I/O server. (This link will open a new page). Click here  to be linked to the USB dongle driver for MicroNet View, that may be required with faster PC's (This link will open a new page).  

Issue Using BACnet Multistate points within Continuum Environment Continuum BACnet Cause Can't use Multistate points values to trigger graphics or other objects Resolution A third Party Multistate BACnet object needs to be mapped to a Continuum Infinity Numeric before it can be read as number. A third Party Multistate BACnet object may be read as State 1, State 2, state 3 or On, Off, -On or other values These should be either mapped to Infinity Strings or Numerical to be displayed or measures as required. eg. ContinuumNum = BACnetFullPath\PointName (if a number is required) Then a ContinuumString can be set based on the ContinuumNum value if the text read from the third party point requires modifying. Other MultiState Bacnet Notes When setting the value of a third party Multistate Bacnet Objects eg "Heat", "Cool", "Auto", "Off", try using an integer ie WriteProperty(Bacnet Object, 4, 1) rather than WriteProperty(Bacnet Object, Heat, 1) Note: Some 3rd party bacnet devices default their multi-state values to 0 instead of 1. Cyberstation will not accept a default value of 0. Get the 3rd party vendor to set the default to 1 if possible.

Issue In some situations, netcontrollers including BCX,CX, and ACX controllers will go offline when doing "teach" and then go back online after a couple of minutes. When reloading the controller, during the period of "teach", controllers go offline. Controller is online with Cyberstation but goes offline during the reload, reloading by class (Numerics, inputs etc) works fine. Environment Cyberstation 1.90~1.93 Windows XP sp3, Windows 7 professional. Cause 1. Some offline cyberstation has same IP address or Network ID as the cyberstation which you are doing the "teach" 2. Also caused by Cyberstation configured for DHCP instead of static ip address Resolution SOLUTION  1: Get rid off the offline cyberstation in the system, or modify ID address and Network ID of your cyberstation. Restart Continuum SOLUTION 2: Assign static IP address to the Cyberstation.

Issue Can more than one Modbus device be mapped to the same IP Address? Product Line Satchwell Sigma Environment IC3 Modbus TCP502 Cause Configuration not documented in release note Resolution More than one device can be mapped via the same IP Address.  For example the gateway.txt file can be: 1,1,3,1,1,0x0001,0,0,1  ;Modsim1 40001 2,1,3,2,1,0x0001,0,0,1  ;Modsim1 40002 3,2,3,1,1,0x0001,0,0,1  ;Modsim2 40001 4,2,3,2,1,0x0001,0,0,1  ;Modsim2 40002 5,3,3,1,1,0x0001,0,0,1  ;Modsim3 40001 6,3,3,2,1,0x0001,0,0,1  ;Modsim3 40002 7,4,3,1,1,0x0001,0,0,1  ;Modsim4 40001 8,4,3,2,1,0x0001,0,0,1  ;Modsim4 40002 OUTPUT ; IP_ADDRESS_TABLE 1,10.158.72.254 2,10.158.72.254 3,10.158.72.254 4,10.158.72.254 ;Do not write below this line   Note: The IC3 Modbus can only be mapped to a single IP Gateway or PC application, and it is not possible to map to two applications on the same PC.

Issue After migrating a TAC Vista export containing TAC Xenta IO modules to SBO, some or all TAC Xenta IO modules are missing the neuron ID's Environment Migration TAC Xenta IO module Cause During the migration, the TAC Xenta IO modules are matched on their name. If the name in TAC Vista differs from the actual name in the associated Menta file, the match can't be made and the properties on the IO modules can not be set. Example of this scenario In TAC Vista   In TAC Menta Resolution 1. Edit the Menta application through TAC Vista Workstation 2. Rename the IO modules in Menta 3. Save to Vista 4. Device gets dirty and need download - download to get rid of the dirty mark 5. Export database in through TAC Vista Workstation 6. Convert to SBO using the Conversion Tool

Issue Can not enter the unlock code in WorkPlace Tech Purchasing Software, the “Unlock” button is grayed out. Environment WorkPlace Tech Tool software, release 5.7 or newer Cause WorkPlace Tech Purchasing Program was not properly closed after the codes were generated.  The Purchase program was closed using the “X” button, not the “Done” button.  Registry and file information does not get saved to the computer when the purchase program is closed using the “X” button. Resolution Re-run the purchasing program and select the same options. This time close the purchasing program using the "Done” button, not the “X” button.

Issue SigmaX PCID changes each time the PC is restarted, Juniper Networks Virtual Private Network (VPN) has recently been installed. Product Line Satchwell Sigma Environment Windows XP with Sigma, SigmaX and Juniper Networks VPN virtual network adapter Cause SigmaX uses the Media Access Controller (MAC) address of the first network adapter on the PC to generate the SigmaX PCID, when the VPN adapter from Juniper networks is installed it is placed by windows as the first adapter. If the ipconfig /all command is run from a command prompt it can be seen that new MAC address is assigned to the Juniper adapter each time the PC is started. A search of the Juniper Networks knowledgebase shows that it is normal behaviour and the MAC cannot be fixed Summary: Is there any way to have static MAC address for Network Connect virtual adapter? Problem or Goal: Assigning static MAC address for Network Connect virtual adapter. Solution: As of now, it is not possible to have a static MAC address for Network Connect virtual adapter. The virtual MAC for Network Connect virtual adapter will always start with 00:FF and the rest of the MAC is generated dynamically. The MAC address of the Network Connect client machine is randomly generated based on the algorithm whose result will change with system and time. Resolution SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. SigmaX uses the Media Access Controller (MAC) address of the first network adapter on the PC to generate the SigmaX PCID, when the VPN adapter from Juniper networks is installed it is placed by windows as the first adapter. Since there is no way of fixing the MAC address of the Juniper virtual network adapter the work around is to disable the adapter when SigmaX is used. There are two ways that this can be accomplished:- Disable the adapter from Windows Device Manager Note that the Juniper network Connect Virtual Adapter is a hidden device in Device Manager Right Click on My Computer and select Manage from the available options Select Device Manager from the management tree Once in Device manager select "Show Hidden Devices" from The View menu Expand the network adapters tree and right click the Juniper network Connect Virtual Adapter entry and select Disable After a short delay a red X will be shown across the icon for the adapter SigmaX will now use the next adapter to generate the PCID, note that the adapter will need to be Enabled in a similar fashion to above if a VPN connection is required at a later time. Disable the adapter via a script It is possible to disable/enable the Juniper Virtual adapter from a script, this requires that the Microsoft DevConutility be first downloaded to the PC Download the DevCon utility from http://support.microsoft.com/kb/311272 Extract DevCon.exe from the i386 folder of the zip file and place it in the root directory of the PC Create a new notepad file with the following text: cd\ devcon disable *DSNCADPT* end Save this file as DisableJuniper.bat Create a second new notepad file with the following text: cd\ devcon enable *DSNCADPT* end Save this file as EnableJuniper.bat Executing these files will control the adapter and once disabled SigmaX will now use the next adapter to generate the PCID

Issue How does controller part number relate to the controller type Environment Continuum 1.7 onwards for bCX Continuum 1.74SP2 onwards for NC2 Cause Require details on Controller type, these detail are available in the Operation and Technical Reference Guide Resolution Part Number Type NC2  9680 bCX1-R-?? 4000 bCX1-CR-??? 4040 bCX1-CR-???-INF 9640 The actual type can be confirmed by logging on to the controller web page Full details from relevant guide CX9680 NetController II with optional Network Security code linked with firmware, although the code may not be activated at run-time. This option provides secure, encrypted communication between the controller and a workstation. CX9681 NetController II without optional Network Security code linked with firmware. bCX4000 BACnet Router and BBMD only .. bCX1-R-64 = 64 MS/TP Nodes No xP module support No PE Driver support BACnet/IP, BACnet/Ethernet bCX4040 BACnet controller with MS/TP Bus xP expansion bus for up to 2 I/O modules + 1 Display module 1 MS/TP port and 1 RS232 port BACnet limitations are indicated by the bCX1 part number, and include: .. bCX1-CR-0 = 0 MS/TP Nodes .. bCX1-CR-8 = 8 MS/TPNodes .. bCX1-CR-32 = 32 MS/TP Nodes .. bCX1-CR-64 = 64 MS/TPNodes .. bCX1-CR-127 = 127 MS/TP Nodes .. bCX1-CR-0-SA = 0 MS/TP Nodes w/SMNP Alarming .. bCX1-CR-8-SA = 8 MS/TP Nodes w/SNMP Alarming .. bCX1-CR-32-SA = 32 MS/TP Nodes w/SMNP Alarming .. bCX1-CR-64-SA = 64 MS/TPNodes w/SMNP Alarming .. bCX1-CR-127-SA = 127 MS/TP Nodes w/SMNP Alarming bCX9640 Full function controller with Infinet Bus xP expansion bus for up to 2 I/O modules + 1 Display module, 1 Infinet and 1 RS232 port Infinet bus limitations are indicated by the bCX1 part number, and include: .. bCX1-CR-0-INF = 0 Infinet Nodes .. bCX1-CR-8-INF = 8 Infinet Nodes .. bCX1-CR-32-INF = 32 Infinet Nodes .. bCX1-CR-64-INF = 64 Infinet Nodes .. bCX1-CR-127-INF = 127 Infinet Nodes .. bCX1-CR-0-INF-SA = 0 Infinet Nodes w/SMNP Alarming .. bCX1-CR-8-INF-SA = 8 Infinet Nodes w/SNMP Alarming .. bCX1-CR-32-INF-SA = 32 Infinet Nodes w/SNMP Alarming .. bCX1-CR-64-INF-SA = 64 Infinet Nodes w/SNMP Alarming .. bCX1-CR-127-INF-SA = 127 Infinet Nodes w/SNMP Alarming The bCX can have XDrivers on comm1, comm2 or both ( add -X1, -X2 or -X12)

Issue Sending the results of a Listview to a Report.   Product Line Andover Continuum   Environment CyberStation   Cause Available options are not commonly known   Resolution There are two ways to display the contents of a Listview in a Report.   The first method is to create a Report and set its data source to 'Listview'.  Then in the filter tab add the desired Listview as a filter. Please note that only ONE list view can be added. When the Report executes it populates data from the Listview object.   The second method is to create an HTML Report template Then the HTML Report in the Listview's Report Template field In this case the report can be invoked right from the Listview

Issue Can't communicate with more than 1 device on LG Gateway at the same time. Updated with solution on 12/15/2017 Product Line EcoStruxure Building Operation Environment LG Gateway Model:PQNFB17C1 Firmware version: 1.11.4 Cause The gateway can only provide one source address when there are multiple device IDs. The wireshark capture confirmed that no unique source ID provided by the gateway with different device IDs. Resolution Update the firmware version to 5.08.1h Configure the "BACnet Type Setting" to "B Type".