Building Automation Knowledge Base

Issue When using the PSI software, the Current Status Screen, All Points History and the graphic data display screens do not properly display the text shown on that screen. Environment PSI software Computer Cause The video bios in the computer does not support the graphics mode used by the graphic displays of the PSI software products. Resolution This problem was first identified several years ago on some models of Gateway brand laptop computers. The problem has been observed from time to time, since then, on various computer makes and models. The problem affects both the "Current Status" screen, the "All Points History" screen and the graphic display screens for analog I/O points. There is no software workaround for the problem. The best solution for this problem is to evaluate the computer model before purchasing any quantity of them. Download test program vga_test on The Exchange Download Center, which allows testing of the computer without having to load the PSI software. The test program can be run from any removable media (diskette, CD, memory-stick, etc.) so the computer can be tested at the computer dealer's store or sales office. The text file included in the zip file explains how to run the test and how to interpret the results.

Issue Input scaling issues with the use of 0 to 5 Vdc and 0 (or 4) to 20 Milliamp transducers on a MNB controller. Environment MNB Series Controller application program using Analog Input voltage or current inputs. Cause The resolution of the Analog Input object value is determined by the maximum value that can be processed. If the scaled input range is less than 163.84, the output resolution is 0.01 If the scaled input range is greater than 163.84, the output is an integer value. Resolution When programming the Analog Input object in the WorkPlace Tech Tool, it is important to properly configure the input range and scaled value range for this object. If configured for a 0 to 5 VDC input, the sensor properties must be configured as follows: Input Sensor Type (Type): 5 - Volts Input Low Value (LInput): 0 Scaled Low Value (LScale): 0 Input High Value (HInput): 5 Scaled High Value (HScale): (value, up to 16383, corresponding to 5 volt input) See note below. If configured for a 0 to 20 milliamp or 4 to 20 milliamp input, the sensor properties must be configured as follows: Input Sensor Type (Type): 4 - Milliamp Input Low Value (LInput): 0 or 4 (depending on transducer) Scaled Low Value (LScale): 0 (value corresponding to LInput sensed value) Input High Value (HInput): 20 Scaled High Value (HScale): (value, up to 16383, corresponding to 20 milliamp input) See note below. NOTE: The HScale value should be set to give an output value for the Analog Input object that corresponds to the maximum temperature, flow, cfm, etc. that the sensor is measuring. The resolution of the value processed by this object must be taken into account when setting the HScale value because the input to output scaling and precision depends on this scaling constant. If the HScale value is less than 163.83, the input resolution is two decimal places and if greater than 163.83, integer resolution. An example of where this scale range is critical would be the use of a 0 to 5 volt air pressure transducer measuring an air pressure of 0 to 2 InWC. If the HScale is set to 2, the output would only resolve to 0.01. If the HScale value were set to 2000, the output would be in thousandths of an InWC, giving you an effective resolution of 0.001. Since this value is one thousand times the actual measured pressure, this 1000x scale factor would also have to be taken into account in any use of that value within the application.

Issue Error "Entry Point Not Found" when starting I/NET Environment I/NET Cause One or more .dll files have been overwritten by another Windows Application on the PC Resolution Verify that the I/NET files .exe and .dll are all the same build by doing a right click, properties and check the version tab Save all files and graphics, then reinstall I/NET again to put back the correct rev of. dlls that are compatible with the I/NET Software.  

Issue Changing the NetController Model Type between 9900 and 9940 Environment NetController CX9900 NetController CX9940 Cause Update NetController model number in Continuum database Resolution Backup the database. Shut down Continuum as precautionary measure Open the SQL Enterprise Manager Open the SQL Query Analyzer Select the ContinuumDB To change from 9900 to 9940, type in update infinitycontroller set CntrlType = 44 where UiName = ‘Infinity1’ and execute To change from 9940 to 9900, type in update infinitycontroller set CntrlType = 42 where UiName = ‘Infinity1’ and execute Please note that you must change ‘Infinity1’ to match the Uiname of your controller Start Continuum up again and verify that the change was effective

Issue Cannot get the serial communications in the Pocket IA software to work on an HP IPAQ H1945 (or other similar Pocket PC devices). Environment Pocket IA software HP IPAQ H1945 Cause Some Pocket-PC devices do not support a serial interface regardless of the availability of a serial cable that is plug compatible with the Pocket-PC device. Resolution The following procedure can be used to determine if the Pocket-PC device supports a serial interface. On the PDA, from the Start menu, select ActiveSync From the Tools menu (in ActiveSync), select Options On the displayed "PC Synchronization" screen, select the "Options" button. On the "PC Synchronization Options" screen displayed, you should see a checkbox with the description "Enable PC Sync using this connection:" with a pull-down selection box immediately below it. Click on the down-arrow at the right end of that box. If the list in the box shows only "`BlueToothActiveSync" and "`USB", the device does not support serial communications and therefore is not usable with the Pocket IA software.

Issue Door Force Lock schedule configuration Environment Continuum Access Control Cause Enable the Door Force Lock Schedule attribute in the Door object. Resolution Door Force Lock schedule configuration This is a two part setting in order to successfully make Door Force Lock schedule work. If you set up a point in the Door Force Lock Schedule on the options tab, You will need to check either Normal and/or Comm Fail on the entry reader tab of the door editor in order to successfully work.

Issue Intrinsic Alarms (Controller Status, etc) - What are they and how do they work Environment Continuum Site Cause Alarm not written to the database and available via ListView Resolution Intrinsic Alarms - What are they and how do they work Intrinsic alarms are let’s say built-in alarms on each Continuum workstation. The event notifications for these alarms are located under the templates directory in the Continuum Explorer. The event notifications for these intrinsic alarms will need to have recipients added to them and configured in order to receive alarms at the workstations. They function a bit differently than regular alarms since for one there is no alarm enrollment, hence the built-in part. Please look at these alarms as machine specific. Having said that, if you have two workstations and machine A is set to log the alarm and is in the recipient list and machine B is in the recipient list without being set as log for the Controller Status. When a CX controller goes offline you will receive the alarm in both workstations, but will only be logged to the database when machine A has acknowledged based on the Deactivate criteria. If you have both machine A and machine B both set to log the alarm, as mentioned before each alarm is machine specific, then two alarms will be logged into the database.  There intrinsic alarms below work as described. Controller Status Fault Status Logon Status

Issue There is a known issue with the ePadink signature readers when trying to capture a signature through the Continuum Personnel Manager. Environment ePadink Signature reader Epi-Builder Cause Driver issue between the ePad reader and Epi-Builder. Epi-Builder is the latest version of personnel card editor that the later versions of Continuum use. The later versions of the ePad Drivers do not work with the Epi-Builder card designer and will only capture one pixel of a signature. The CD that ships with the latest ePadink readers is 7.52 this will not work. The older CD version 6.24 drivers and 7.1 software version does work. Resolution WORKAROUND: If you have the installed the drivers and software from the 7.52 CD, go into add remove programs and remove the Interlinks Electronic ePad software. Then install the ePad drivers 6.24 and software 7.1 from the older version CD. This is a known issue between Interlinks ePadink and Imageware. The ImageWare reference number is 66251.

Issue How can the factory default settings for the level 3 password and the two serial ports be restored on a DMS-3500? Environment DMS-3500 Cause Factory passwords are changed and need access to they system. Resolution With power on, remove the DMS-3500 cover to expose the circuit board. Locate the "CONFIG" 2-pin connector on the circuit board (near the green LED labeled SYS). There should be a jumper over one of the pins. Remove the jumper and place it over the two pins. Cycle power to the DMS-3500. When the DMS-3500 is powered up with the jumper shorting the "CONFIG" pins, NOVRAM is cleared and the default settings for the password and port assignment elements are restored. This does not affect the remaining configuration or database for the DMS-3500. Remove the jumper and place it back over one of the pins. The default settings listed below are in effect until set to different values: Level 3 Password: 170 Serial Port 1: 9600 1 7 E P N Serial Port 2: 2400 1 7 E P M CAUTION: Return the jumper to its original position. If this is not done, the new password and port settings will be lost the next time power is cycled to the DMS-3500.

Issue When opening a pinpoint graphic on Cyberstation, Continuum displays the error "Can't Create Empty Document." Environment CyberStation Cause This error may be displayed when trying to create or open a graphic file. May indicate that either the XML parser or the Pinpoint.INI file has been corrupted.  Resolution The fix is to reinstall the XML parser. On the workstation displaying the error, exit Continuum gracefully. Open  Windows Explorer Browse to the C:\Windows Folder Find and delete Pinpoint.ini  (Continuum will rebuild this file on startup). Try to edit or create a graphic file. If the problem persists, the fix is to reinstall the XML parser. On the workstation displaying the error, exit Continuum gracefully. Open  Windows Explorer Browse to the Program Files > Continuum > Install folder Run msxml3.msi Run msxml4.msi If you have an older version of Continuum you may only find msxml3.msi. You should not have to reboot the workstation after the install has completed successfully. Start Continuum You may need to Uninstall Continuun, reboot, Reinstall Continuum If the above doesn't correct the issue, go to a restore point prior to the problem or reformat the hard drive and reinstall Windows and Cyberstation

Issue After a flash upgrade to a Net Controller, getting "Copy Protection Violation" error Environment Net Controller Cause After a flash upgrade to a Net Controller, you see a "Copy Protection Violation" error. This can be corrected by flashing with a different flash file. The Net Controller flash files come in 2 versions per Net Controller. On the Support web page, you will see the various versions labeled "SNMP Not Set" and "Standard SNMP." These labels can be misleading. Resolution If you have a controller that has been upgraded to the optional SNMP Alarming, you should use the “SNMP Not Set.” This flash file will upgrade the controller to the specific version of firmware without interfering with SNMP. As of version 1.5, Continuum CX controllers ((CX99xx, CX94XX, CX9201), and as of version 1.2 of the 9702 SiteController and version 1.0 of the bCX1 controllers (96xx and 40xx) can be located and managed on corporate Ethernet networks with support for SNMP. These controllers have “Standard SNMP” functionality. Using an SNMP Browser, the controllers can be seen as part of the corporate network. If SNMP Alarming has been purchased, the controller will deliver Continuum alarms to SNMP Browsers. The SNMP Alarming option can be added in the field by updating the controller with a file purchased from the Repair Department. You can determine if your controller has SNMP alarming enabled by editing the controller and selecting the Options tab. If you only see SNMP: Enabled, this controller is enabled for Standard SNMP. Flash upgrade this controller with the files labeled “Standard SNMP.” If you view the Controller Options tab and see SNMP: Enable, SNMP Notifications, SNMP Alarm Table Size and SNMP Alarm Links, this controller has been enabled for SNMP alarming. Flash upgrade this controller with the files labeled “SNMP Not Set.”

Issue Bacnet MSTP Network ID-Comm2 cannot be duplicated Environment bCX Controller B4 Controller Cause If the MSTP Network ID-Comm2 is duplicated, you'll experience issues when trying to find bacnet devices. Resolution Bacnet MSTP Network ID-Comm2 cannot be duplicated When commissioning a Bacnet Controller either BCX or B4, caution must be taken to ensure that the MSTP Network ID-Comm2 is not duplicated. On jobs that have bacnet systems running on the same ethernet, make sure to avoid using an MSTP Network ID that is already in use independent of our system. The default MSTP Network ID Comm2 setting is 2765.

Issue With the MNL VAV controllers, does the integral damper motor perform a self calibration during which it cycles fully closed or fully open? Environment MNL VAV controllers Cause When main power is applied to the MNL VAV controller, the damper motor will cycle to a full closed position. Resolution Automatic Calibration: An internal calibration feature automatically synchronizes the actuator position whenever the actuator is commanded to the full closed (0.0%) or full open (100.0%) position by continuing to drive the actuator in the requested direction for a time period of at least one additional complete full stroke drive time. If during this “end of stroke” drive period the Input value changes to a value within the control range, the output drive to locate the true end of stroke operation is terminated. Drift Compensation Enable: Setting the Drift Compensation Enable configuration property to On (1) compensates for floating actuator mechanical drift whenever the actuator remains at the full open or full closed position for extended periods of time. Drift compensation is done by periodically driving the actuator in the commanded direction for a time period derived from the Drive Time assigned. Drift compensation does not occur whenever the actuator is within the actual control range between full open and full closed. Refer to the Floating Actuator Object in F-27254 for additional information.

Issue Trends no longer collect Alarms have stopped annunciating Programming changes to any segment do not work A reboot of the UltiVist software and/or of the server does not clear up the issues Environment UltiVist server Cause When this behavior appears unexpectedly on a system that has operated solidly for several years, it is likely that the UltiVist buffer files have grown to an unmanageable size. When this occurs, features and functions of the UltiVist software stop working. Resolution As a good housekeeping step, delete all the existing buffer files. UltiVist will re-create new ones when it is re-started. Here's how to delete the buffer files: Exit UltiVist and shutdown all background programs using "Arnold" Using OS/2, delete any & all buffer files on the partition which the UltiVist software is installed. There will be many located in different directories and sub-directories. The buffer files have many different filenames but all have the same filename extension of ".d$$".   CAUTION: On the root directory of the root drive, there exists a file named "WS_ID.D$$". Do NOT delete this file. Restart the UltiVist software.

Issue A SIGNAL computer is missing the security plug or the original installation diskettes. How can they be replaced? Environment SIGNAL computer Cause Purchase replacement part for SIGNAL computer. Resolution Here are the part numbers: SIG-KEY-CHG -> (obsolete) replacement security plug SIG-UPDAT-ENG -> replacement installation diskettes When ordering, provide the existing serial number so that the replacement part can be coded properly. Note: Both items above cannot be ordered for the same job. If both items are lost, a new SIGNAL software package must be ordered.

Issue The computer hardware for a SIGNAL installation has changed and there are no parallel ports for the security plug. Is there a USB key for SIGNAL? Environment Computer without parallel ports SIGNAL Cause Computer hardware limitation prevent the use of security plug. Resolution As noted in Product Announcement PA-00280, Signal support ended on June 30, 2014.  Replacement parallel port and USB keys are no longer available. Yes. Here are the part numbers: SIG-USB-CHG -> (OBSOLETE) Replaces the parallel security plug with a USB version for an existing SIGNAL installation. Contact Customer Service to order this part.  It is not available via iPortal. SIG-USB-KEY -> (OBSOLETE) Replaces the parallel security plug with a USB version for a new SIGNAL order

Issue The SIGNAL serial numbers on the security plug and the first installation diskette are different. Will they work together? Environment SIGNAL computer Security plug installation diskette Cause Information about the date code found on SIGNAL system. Resolution Every SIGNAL serial number is 8 digits long. The first 4 digits are a datecode and the second 4 digits are the actual serial number: Serial# xxxx-yyyy where x = datecode  and y = serial number The first 4 digits will differ if either the original security plug or original installation diskettes were lost and replaced. As long as the last 4 digits are identical, they will work together.

Issue A new battery is required for a DMS-3500. It looks like an AA battery. What is the replacement part for it? Environment DMS-3500 Cause Replace failed battery on a DMS-3500. Resolution Order part number DMS-BATT-001 for any of the following products: DMS-3500 DMS-350A DCM-1000 MSC-MPC-001 MSC-MPC

Issue In a Niagara R2 / Microsmart integration with revision 9 controllers, what's the best way to implement the MsL9Value object? Environment Unknown Environment Cause Unknown Cause Resolution The only way to effectively implement this object is to do the following: Create a virtual AI point in the revision 9 MicroSmart controller. This is a standard AI point with no input address assigned to the INPUT field. Learn it into the UNC station. Create a MsL9Value object in the workspace of the virtual AI point's shadow object. The only property that needs to be assigned is the "logpt". This must be a numeric value 1 to 250. If more than one MsL9Value object is used under a L9 controller, it should be a different number in each. Refer to ibsMS-2.302.514a Release Notes.pdf for additional details of this object. The UNC can now send a value down to the virtual AI which, in turn, can be used as a manual setpoint input to a Loop point or Mode Control point. The MsL9Value object can be linked to a GxText object providing the building operator the ability to change the value from a web graphic.

Issue What's the best way to uninstall SIGNAL software? Environment SIGNAL software Cause Remove SIGNAL software from a computer that no longer need the software. Resolution Steps: Perform two backups - one with executables and one without executables. The backup with executables can be used to restore the entire SIGNAL installation if that is required. The backup without executables is good to have if SIGNAL is already installed on a computer and only job-specific files are restored In Windows Explorer, delete the SIGNAL folder and two files in the C:\WINDOWS directory: signal.ini & bit.ini Remove any shortcuts created on the desktop and in the Windows startup folder. Reboot the computer.