Building Automation Knowledge Base

Issue There is a need to get logging details for troubleshooting video integration issues in Continuum. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause There is an issue with the video integration and there are specific instructions to enable video troubleshooting in Continuum. Resolution Continuum versions 1.9x and above contain a helpful tool for troubleshooting video integration issues To enable video logging, follow these instructions: Shut down Continuum on the Cyberstation you will use to create the log file Using Windows notepad, edit the file log4net.config located in C:\Program Files\Continuum At the bottom of the file locate the following text:  <root> <level value ="WARN"  /> Change WARN to DEBUG (Ex. level value ="WARN" ---> level value ="DEBUG" ) From the pull down menu, File> Save and close the file         4.Start Continuum and test one isolated procedure at a time (Ex. video isn't displaying on alarm)         5. Email the video.log file from the C:\Program Files\Continuum folder to the support engineer for analysis Note: Make a copy of the video.log file ( to save the file ) and then delete the original. A new video.log file is created each time Continuum is started with the level value="DEBUG" set Video log changes for 1.92/1.93/1.94 The instructions to enable the video.log are the same as for 1.91, however the results have been broken into a number of different files VideoAdmin.log - used for configuration  AccVideoRecordingServc.log - used for camera learn VideoLayout.log - used for video layout  AlarmView.log - used for video alarms Easiest way to see what file was written to is to sort the Windows folder by the Type column and check the txt file(log) dates Note: In Microsoft Vista or Windows Server 2008, if account control is not disabled the video log files may get written to "C:\users\username\AppData\Local\VirtualStore\Program Files\Continuum" Caution: Once the debugging process has been completed, go back into the log4net.config file and edit the file. Change the DEBUG to WARN (Ex. level value ="DEBUG" ---> level value ="WARN") From the pull down menu, File> Save and close the file This will stop the files from growing too large.

Issue Date and time gets incorrect periodically in TAC Xenta Programmable controllers Time stamp in alarm list is incorrect Time stamp in alarm list is wrong  Vista Server local time and the local time in all Xenta controllers in the network go out of synch.   All local time settings are correct in TAC Xenta Environment TAC Xenta 30x/401/28x Cause The time in a TAC Xenta can be changed by TAC Vista TAC OP, note that a change of the time in one controller is broadcasted to the whole network. TAC Xenta group master will broadcast the time to it's group every 24 hours A Xenta Server (Xenta7xx, Xenta5xx, Xenta 913) Menta, this only affects the controller Menta is connected to. Most likely, the problem is a Xenta Server in the network that has the wrong time. It can be enough that a Xenta server is connected to the network, it does not have to be configured in this network.. Resolution Log in to Xenta server from the web interface. Go to Configuration-time If the date and time is incorrect set the correct date and time. Click on time synchronization, the lonworks time synchronization should only be set to enable  if this is a Xenta Server in TAC Vista or if this is a site that does not have TAC Vista on it and it is the only source to sync the time to.

Issue ARCNET LAN Maximum Impedance and Maximum Distance. Environment Sigma all versions using ARCNET. Cause Advice only. Resolution The maximum impedance of an ARCNET LAN should be less than 100ohms. Maximum distance for an ARCNET LAN at 156K baud rate is 800metres using the preferred cable Belden 8762, this will have a resistance of 25ohms. For further information regarding baud rates, cable types, distance and installation guidelines please go to: Cabling Guide 2.2.

Issue What is the default user name and password for MicroNet View? Environment MicroNet View Cause Access level Resolution User name: - Administrator Password: - MicroNet

Issue What are the default passwords for a IAC Touchscreen Environment Satchnet IAC controllers Cause Access level Resolution Read only: -      1234 Read/Write: -   4321 Super User: -    1024 ACK Alarm: -  2513 It is worth noting that these passwords can be changed when programming. If you connect to the Touchscreen using VisiSat software you can identify the passwords under the properties of the Touchscreen.

Issue What are the default passwords for a MicroNet Touchscreen? Environment MicroNet Touchscreen controllers Cause Access level Resolution Read only: -      1234 Read/Write: -   4321 Super User: -    1024 ACK Alarm: -  2513 It is worth noting that these passwords can be changed when programming. If you connect to the Touchscreen using VisiSat software you can identify the passwords under the properties of the Touchscreen.

Issue What attributes are available on a Continuum Activity Listview? Environment Continuum Cyberstation Listview Cause Available attributes for Activity Listview Resolution Creation of a Activity Listview the following attributes are available: ActionCode CallerCode Description EventObjectID EventObjectName Id NodeName OperatorText OTUser TimeStamp UserId UserName

Issue i28xx type of Infinet Controller has different range of WC (Water Column) than i28xx-V Infinet Controllers. What are the input voltage settings for i28xx and i28xx-V controllers' AirFlow sensor input? Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885 & i2885-V) Cause Input settings for Velocity Pressure Sensor is different than the other regular analog input (voltage input) configuration. Resolution The i28xx type of Infinet Controller has 0~2" WC (Water Column) range, the input voltage should be set to 0~2V. The i28xx-V type of Infinet Controller has 0~1" WC (Water Column) range, the input voltage should be set to 0~1V.

Issue Alarm time logged into Vista from a Xenta controller 1 Hour earlier than actual alarm time even though the Xenta and Vista Server have the same time. This can also cause issues with Xenta trend logs where they will have estimated values for the past hour worth of logs. Environment Workstation Xenta Controllers Cause The offline (Engineering) Daylight / Standard time (DST) settings do not match the online (Operating) Daylight / Standard time settings. Resolution The Daylight saving and Standard time settings need to be corrected in the Xenta controller as follow: Place Vista into Engineering mode using the drop down list on the tool bar. Select the controller that is having the alarm time error. Right mouse click and select Properties. Select the Time Settings tab. Correct the Daylight saving and Standard Time settings. Return the Vista into Operating Mode using the drop down list on the tool bar. Retest alarm for correct time stamp or recheck your Xenta trend logs.

Issue What are the solutions available for database fail over system Environment Continuum Cyberstation Stratus Technologies Cause Information about Database fail over / redundant systems. Resolution The everRun product  from StratusTechnologies (formerly Marathon Technologies) is what many sites use for a database fail over system. You can find more information in the everRun Datasheet and on their website below. http://www.stratus.com

Issue Error displayed "Array index too large or too small" when reloading a controller with SmartSensor (Smart Sensor) program created, or saving the SmartSensor (Smart Sensor) program to the controller. Environment Infinet Controllers (i28xx) Bacnet controllers (b38xx) bCX4040 bCX9640 Cause SmartSensor (Smart Sensor) control program uses 7 arrays of the LCDDisplay (or LEDDisplay) InfinityNumeric object to get the keypad input data, display data, change the display format and control the point.  When the point is created with no array, the SmartSensor program fails in saving.  Or, if the LCDDisplay (or LEDDisplay) InfinityNumeric object has been changed from 7 manual entries to no array since the SmartSensor program was created, it fails when reloading the program or the reloading the controller. Resolution Edit the LCDDisplay (or LEDDisplay) InfinityNumeric object and set the 7 manual entries in the Logs tab of the point editor and resave the program or reload the controller.

Issue i2/b3 controller getting error " . . .  OS update fail. Please retry" after OS upgrade is done.  The Continuum Explorer shows exclamation mark (bang) on the controller icon. The control works normal, but it is confusing. Environment Infinet controllers (i2 controllers). Bacnet controllers (b3 controllers). NC2 (CX9680) ACX5740 ACX5720 bCX4040 Cause Controller OS upgrade has failed in the first try due to network issue or unstable system environment but succeeded on the second try or the next try. Resolution Bring up a listview of i2/b3 controllers. Find the one that displays the yellow exclamation mark (bang). Perform SetAttribute (right click on the controller and select "Set Attributes") for the ObjectStatus. Select the ObjectStatus and set the value to 0 .

Issue Viconics Stats will not come on line. Environment Continuum 1.XX Windows XP, 2003 Viconics Stat Cause Viconics Comm address set to 50 BACnet Max Master set to low,  Set to 32. Resolution Open Continuum Explorer Expand Bac Net devices Edit the BCX ( Bac net view) Change the BACnet Max master value

Issue The ACX 57xx series controller supports up to 2 xP or xPB (bi-directional) expansion modules, plus a display for extended input and output configurations. The ACX 57xx series controller is compatible with all of the TAC expansion modules. For more information about expansion modules, see the xP Expansion Module Reference, 30-3001-840 and/or the xPB Expansion Module Reference, 30-3001-883. What are the valid channel numbers for expansion IO on the ACX5740/5720? Environment CyberStation ACX5740 ACX5720 Cause The expansion IO channel number assignments is different in the ACX5720 due to the fact that it has only half the onboard IO as the ACX5740 Resolution The ACX5740 has 12 onboard inputs and 4 onboard outputs, therefore the first expansion input channel is 13 and the first expansion output channel is 5 The ACX5720 has 6 onboard inputs and 2 onboard outputs, therefore the first expansion input channel is 7 and the first expansion output channel is 3

Issue Changing between view and edit modes using Workbench after adding a PxInclude object to a parent px file with a schedule causes Workbench to lockup and fail. A restart of the Workbench application is required. Environment TAC I/A Series G3 ENC-410, ENC-520, and Enterprise Network Server Cause Workbench failed to process the scheduler within the PxInclude. Resolution The issue has been resolved in bajaUi module versions 3.3.34.2, 3.4.64.1, 3.5.34.1 and higher.  The files, bajaui 3.3.34.2 is available for download from The Exchange Download Center.  Download the bajaUi version zip file for the required G3 build. Caution: Always backup the station database before performing any upgrade.   If Enterprise Network Server, stop running station and close the Workbench application.  Extract the file and replace the existing bajaUi jar file in the appropriate modules directory of G3. Start Workbench and start station if Enterprise Network Server. Use the Workbench Platform Software Manager to the upgrade the bajaUi module in ENCs as required.

Issue Does I/NET Seven provide Time and Attendance functionality Environment I/NET Seven 2.xx and above Third Party Time and Attendance solution Cause Possible alternatives to Customers wanting to use or interface Time and Attendance solutions with I/NET. Resolution I/NET does not have a separate Time and Attendance ‘module’. There are three possible options which may provide a suitable alternative to your requirements: SevenReports: I/NET’s SevenReports provides a standard report called “Transactions Attendance”.  The report compares the time stamp for an individual and calculates the time within zones defined in I/NET.  I/NET doors must be configured with entry and exit readers and have defined Zones (i.e. Anti-pass back must be enabled).  It could be as simple as a single zone for the entire site or multiple zones if this is required. This report shows EACH transaction received, therefore if you badge multiple times on the entry or exit readers the system calculates the time difference from the last badge. This must be taken into account by any system when calculating the total time within the “Zone”. Automatic Report Generation (Export of SevenReports to CSV): Using the same report as mentioned above, I/NET is capable of automatically exporting this document to a CSV file. This can be scheduled to run as required for any third party system to use. Third Party Access to InetDb SQL database This option allows third party SQL connections to query the I/NET SQL Database (Read only access), utilizing a predefined login or the INetThirdParty login.  The third party software or application would query data from the InetDb SQL database. For further information and configuration of these features are all available in the same document, TCON301 – Database Connectivity and Reporting.

Issue Some Netcontrollers support 32 I/O Modules, others only 16, how to find out what the limit is when adding more modules to an existing system. Environment Continuum Netcontroller CX9900, CX9940, Netcontroller II CX9680, CX9940 16IO-T X Driver Cause When a site is being extended by adding extra IOU Modules, it needs to be determined if the Netcontroller will support these additional modules. Resolution If the controller is online to Cyberstation, Edit the controller and check the value of "Max IOU Modules" on the Options tab, this will show 16 or 32. If the controller is not online the following apply: All Netcontroller II (CX9680) controllers support 32 IOU Modules. All Netcontroller 1 CX9900 with 8Mb RAM support 32 IOU modules, Most CX9940 with 4Mb RAM support 32 modules the only exception was the 4M-16I/O-T (now obsolete) that supported 16 modules. To determine if the CX9940 is a 4M-16I/O-T, check that the Model on the right side of the unit is defined as CPU-4M also that there are no connectors for the RS485 fitted to the unit on Comm1 or Comm4 (you will see holes where the connectors are not fitted). The CX9940 16IO/T can support an X Driver on RS232 Comm1, but no other port. The 4M-16I/O-T and 8M-32I/OT Do not support any Infinet nodes and cannot be upgraded to support them as the required hardware is not fitted as the time of manufacture.

Issue When Acknowledging an Alarm from one workstation it is not making it to all workstations. Environment CyberStation Alarm Cause The workstation that was not receiving the Acknowledgement had two network cards in it.  Resolution Remove the second network card from the PC.  Pleas note Continuum only supports one network card in a CyberStation.

Issue When ordering Andover Continuum Keys what is the definition of I/O Points? Environment Cyberstation Keys Cause When ordering Andover Continuum Keys what is the definition of I/O Points? Resolution This pertains to the versions of CyberStation keys which include a limitation on the number of Infinity I/O points, such as 250 or 500.  Infinity I/O points are the total number of Infinity Input and Infinity Output points that are configured in the database.  These types of points can be connected to Infinet controllers, Eclipse I/O cards, Continuum IOU modules, or IOU boards  (on the Lbus).  This does not include numerics. 

Issue Remote Client Option is missing from Workstation Options in I/NET 2.40 I/NET Configuration Profile. Environment I/NET Cause The I/O Server must be shut down in order to make this change to an I/NET Configuration Profile. Resolution Close the Configuration Profile Editor Exit I/NET Shut Down the I/O server From the Start Menu, Open I/NET Configuration Profile Editor You should now be able to set the computer to Remote Client