Building Automation Knowledge Base

Issue How to display the date as an object in Sigma. Environment BAS SIGMA Cause How to display the date as an object in Sigma. Resolution For Day and Month only, the following programmable point needs to be configured: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo / 100.000 30 YFlo = FLOAT ( DAY ) 40 RETURN VIA TEXT 449 VALUE XFlo + YFlo The date will be displayed in the dd.mm format. Shorttext will need to be created as below: %2.2f and will be displayed as 17.07 or Date:%2.2f and will be displayed as Date:17.07 If Day, Month and Year is required the following can be configured: 10 XFlo = FLOAT ( MONTH ) 20 XFlo = XFlo * 100.000 30 YFlo = FLOAT ( DAY ) 40 YFlo = YFlo * 10000.0 50 ZFlo = FLOAT ( YEAR ) 60 RETURN VIA TEXT 449 VALUE XFlo + YFlo + ZFlo The date will be displayed in the ddmmyy format. Shorttext will need to be created as below: Date:%2.0f and will be displayed as Date:170712        

Issue When printing a multiple page application, i.e., an application consisting of a device definition and one or more custom object pages, all pages are numbered 0 of 0. Environment WorkPlace Tech Tool release 5.8.0 or release 5.8.1 Cause The title block stencil script created in WorkPlace Tech release 5.8.0 or release 5.8.1 does not execute properly resulting in all pages showing "Page 0 or 0". Resolution Update to WorkPlace Tech Tool release 5.8.2.  Note that upgrading will not automatically correct the issue in application files created with release 5.8.0 or release 5.8.1.  Use the following procedure to correct the issue in application files created with those releases of the WorkPlace Tech Tool software. Open the application using WPT 5.8.2. Select the "Background" page of the drawing. Press Ctrl-A to select everything on the page then press the Delete key to delete everything from the page. Select the "Annotation" style sheet (stencil page). Drag a new copy of the "Schneider Electric Border" stencil onto the page. Drag a new copy of the "Controller Info Block" stencil onto the page.  This block is normally placed in the lower left corner of the drawing. Save the updated application file.

Issue Controller Error Log shows error code 5128. Environment Error Log Error Code NetController BCX ACX Cause An Infinity Controller is dropping offline. Resolution Controller error code 5128 (0x00001408) is an indication that the controllers network comm buffer is out of memory.  Normally the network transceiver will shut down when this happens to protect the controller.  This is generally an indication that the controllers comm buffer is being overtaxed.  This can happen when there is a data storm present on the network. 

Issue When trying to access the serial number off a Continuum key using MMC or Excel, all fields come up blank or with 0. Environment Continuum Security Key MMC Excel CyberKeyWriter2 Cause Cannot access Continuum Key serial number using Excel or MMC. Resolution From My Computer, navigate to Program Files\Continuum. Launch the application CyberKeyWriter2.

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 Is it possible to downgrade a Continuum Database from one version to an older version? Environment Continuum Cause Want to go back to a previous version of Continuum after upgrading Cyberstations and the Continuum Database. Resolution No, this is not possible. You cannot downgrade a Continuum Database to an older version . You can upgrade but not downgrade. If you have a database that has been upgraded for a specific version of Continuum and you want to go back to using an older version of Continuum, you will need to use a backup of your original Continuum Database that was initialized for that older version...or upgrade all Cyberstations to the newer version. The Database structure is different between different versions of Continuum; corruption of the Database can occur if the above is not adhered to.   

Issue Converting a IC type. Environment IC IC3 Type Converting Cause The customer has purchased the incorrect type of IC and wishes to convert it. Resolution An IC / IC3 has a personality built into it, therefore if you were to change the IC / IC3 firmware, it would still not work, as the personality and firmware would not match.  

Issue Is it possible to send the reports by email based on time schedule. Environment TAC Vista Reports Cause Vista does not provide any email functionality for sending Reports.  Some third party applications may exist to do this but have not been tested. Resolution There is no provision in Vista to send reports by email, it is only possible to generate the reports manually or based on schedule which is available within the Vista Reports function.

Issue When creating a Xenta 102-AX in Vista 5.1.6 the UCPTprogramversn and UCPTapplicVersn is ignored and all SNVT/SCPT PROPERTY_OFFSET values have incorrect values causing incorrect value readings and incorrect default values.  The PROPERTY_OFFSET value is offset by 12. Xenta 102-AX devices that are in LNS networks display correct values in LonMaker or NL-220 and only display incorrectly in Vista. Environment Vista Workstation LonMaker NL-220 102-AX Cause A change in the way Vista handles XIFs in Vista 5.1.6 inadvertently caused it to display incorrect values. Resolution Hotfix 12 for TAC Vista 5.1.6 should be downloaded from the Extranet and installed. From the Buildings Business Extranet Navigate to Products > TAC Vista > Vista Software > TAC Vista 5.1.6 > Hotfixes. Hotfix 12 can be applied following the steps below: Before installing the hotfix, Vista Workstation and Server should be shut down. Double-click the hotfix executable file to install. Once the hotfix is installed rebrowse the 102-AX XIF file into any devices that were experiencing the issue by right-clicking the 102-AX device in Vista Workstation and selecting Properties. Then select the XIF File tab and click the ellipses next to the source file. Reselect the 102-AX XIF file and click OK. It may be necessary to refresh the screen to begin seeing correct values.

Issue Cannot download LON controller that is in the "Unconfigured" state. Environment I/A Series MNL series controllers Cause Controller was placed in the "Unconfigured" state by accidentally holding the service pin button too long. Resolution 1a.  If running the WorkPlace Tech Tool software under Microsoft Visio 2007 or earlier, select the "Configure LON Device" function under the Tools menu.  Continue with step 2, below. 1b.  If running the WorkPlace Tech Tool software under Microsoft Visio 2010, select "Configure" under the "Device" selection on the WorkPlace Tech Ribbon Bar. 2.  The "Configure Device" window will be displayed.  Use any of the standard methods; enter Neuron ID, Browse for device or Listen for Service Pin, to select the device. 3.  Click the [OK] button to reconfigure the device. 4.  A WorkPlace Tech status window will be displayed, normally displaying "Successfully configured the device.".  Click [OK] to close the window. The device is now in the configured mode and can be downloaded.

Issue Using Database Initialization to create a new ContinuumDB but get a login error for Andover97. The ContinuumDB is then actually created on the server but is only a shell with no tables existing. The MDF and LDF files are also created. Environment Continuum SQL Server Cause Continuum had been uninstalled and then installed again with a newer version ( v1.94). The problem was due to the previous install of Continuum. Due to this the Andover97 user was already created in the SQL Server and  at some point the password for this user was changed from the default. Resolution After changing the Security\Logins\Andover97 user's password to the default and deleting the ContinuumDB shell, the database was able to be created successfully. 

Issue In OPRIF 11.6, the "database save" command does not work.  When pressing "S" for save, the first prompt asks for the drive letter where the files will be saved (i.e. C drive).  After pressing enter, the second prompt requests a filename.  An eight-digit filename can be entered.  A file path is optional.  After pressing enter, a new screen should appear as the database save begins.  However, after pressing enter, the screen returns to the main database menu. There are no errors reported. Environment DMS OPRIF 11.x Cause A graphic screen is missing from the installation of OPRIF.  After entering the driver letter and filename for the database save, a new screen should appear.  The graphic file is requested but doesn't exist.  As a result, the database save command aborts and returns to the main database menu screen. Resolution The simplest solution is to re-install OPRIF 11.6 "overtop" the existing installation.  The missing file(s) will install.

Issue When you get a replacement dongle for a lost NL220 dongle, NL220 will not let you confirm that dongle with the PC. You get an error message that indicates "Only one key can be confirmed and that the key confirmation will be canceled" Product Line Other, TAC IA Series, TAC Vista Environment NL220 Cause There is a NLS credit conflict that prevents the replacement dongle from confirming with the PC. Resolution You can force a confirmation by following these steps. You run NL220 and wait the error message to appear When you have the error message press Ctrl+shift+n This will then let you confirm the new dongle on your computer.

Issue A TGML Graphic is added or imported into Vista. Then when you right click on the TGML Graphic and select " Open Bindings Window" a blank bindings window is opened. None of the objects defined in the TGML Graphic appear in the binding list to be bound to objects in the Vista database. Environment Vista 5.1.7 Cause The TGML Graphic is named with .(dot) characters in the name. E.G. VAV1.1.7 Resolution Do not use dots, dashes or hyphens in the naming convention for any Vista objects. Either eliminate it altogether, or use underscores (_) instead. To correct this issue after the TGML Graphic has been added  with the incorrect naming convention, is: Edit the TGML Graphic and save it out of the database. Delete the TGML Graphic with the name including the . (dot) character. Add a new TGML Graphic using the correct naming convention E.G. VAV1_1_7 Open the TGML Graphic that was saved out of the database and save into the new TGML Graphic you created with the correct naming convention. Note: Renaming the TGML Graphic object from VAV1.1.7 to VAV1_1_7 in the Vista database does not fix the problem.

Issue 3rd Party RS485 to Ethernet or other connection types are available. Will they work with Infinet? Product Line Andover Continuum Environment Infinet networks Infilink 200, Infilink 210 Cause Sometimes existing cabling is available on a site, using this could reduce install costs. Resolution Third party converters and extenders are not supported on Infinet networks. It is not possible to use most 3rd party devices as the latency (delay) times will be too long for the protocol to operate correctly. This will include: RS485 - Ethernet converters RS485 Tied line Modems Any other type of Modem Any GSM packet modems Other RF devices

Issue WorkPlace Tech 5.x BACnet IP communications is not working. BACnet Ethernet communications works. Environment I/A Series WorkPlace Tech 5.x Symantec Endpoint Protection version 11.0.4202.75 Cause This has been found to be caused by the Symantec Endpoint Protection version 11.0.4202.75. It appears to be blocking the BACnet IP traffic. BACnet IP communications in WorkPlace Tech is working on another computer which has Symantec Endpoint Protection version 11.0.6200.754 installed and the Symantec Management Client service running. It is not known if the issue is actually an issue with the Symantec version or if it is caused by settings in the Symantec Endpoint Protection application. Resolution Stop the Symantec Management Client service when you need to use BACnet IP communications in WorkPlace Tech. (In Windows, go to 'start' > 'run'. Type in 'services.msc' and click 'OK'. This is the shortcut to the Services). The Symantec Management Client service provides communication with the Symantec Endpoint Protection Manager, controls SMC.exe and SMCgui.exe processes. Explanation for Processes and Services used by Symantec Endpoint Protection can be found here. It is recommended that the Symantec Management Client service be restarted after using WorkPlace Tech to ensure that your computer is protected against threats.

Issue Which adaptor should be used when mounting a M3000 actuator on a V321 DN125/150? Environment V321 Forta M3000 M22 M50 Cause Forta actuators are a direct fit to V321 on all sizes DN100 and smaller unless stated differently in the catalogues/data sheets. Resolution The M3000 actuator will not fit on the V321 DN125 and DN150 sized valves due to the different design of the valve body. For DN125/150, actuators M22 and M50 should be used. 

Issue How to log / create an alarm for Continuum invalid login attempts. Environment Continuum Cyberstation Cause Need to log and / or create an alarm for when there are invalid attempts from a user to login to a Continuum Cyberstation. Resolution We have the ability to monitor the Continuum user logins for a specific number of failed attempts, to log an alarm event in the Database, and also send this alarm to Cyberstation recipients. 1. Configure the number of failed attempts using "Setting 16 - Maximum consecutive invalid login attempts before alarm is triggered" located in the Continuum General Preferences. 2. Then configure the EventNotification at Root\Templates\LogonStatus with Recipient Workstations on the Delivery tab. 3. When the number of user logon attempts reaches the number you specified in step 1, the user is forced to restart the process and an alarm is generated and sent with a description similar to below. "User acc has exceeded the maximum number of invalid logon attempts at workstation AdamWS1!" An operator at another Cyberstation can then determine if the user flagged in the alarm needs to be locked out by disabling the user object or some other activity is required.  

Issue Can options be purchased for S-150 and S-400? Environment S-150 S-400 Cause Customer wishes to purchase an additional client for his system. Resolution Additional options cannot be purchased for S-150 or S-400 systems, they must first be upgraded to S-Full by purchasing S-UPG. Once the Sigma licence has been upgraded to Sigma Full (S-Full), all options can then be purchased.

Issue When the firmware in a Continuum second generation controller is changed via uprev flash file, the controller adds an informational item in its error log that includes the FROM and TO versions. This article describes how to get those revisions from the error log. Environment bCX CX9680 ACX5720/40 Cause Documentation Resolution Following an uprev operation there will be three new Informational entries in the error log Example: 6660 I 01/01/1989 00:00:00.00  0x00006409 0x09289b00 0x0190da1c 0x00008748 0x0000d384                                         Software revision change 6661 I 01/01/1989 00:00:00.00  0x00006409 0x09289b00 0x0190da40 0x000025d0 0x00200b3f                                         Software revision change 6662 I 01/01/1989 00:00:00.00  0x00006409 0x09289b00 0x0190da64 0x000025d0 0x00200b41                                         Software revision change The last column in the entries contains the version number information. The first entry with a value of 0x0000d384 in the example above can be ignored The second entry specifies the FROM version, in the example above the controller was flashed FROM 2100031 (0x00200b3f) The third entry specifies the version the controller was flashed TO. in the example above the controller was flashed TO 2100033 (0x00200b41)

Issue Photo export Environment CyberStation Cause Need to export photos in personnel records. Resolution When a personnel record in Continuum has a photo included, the photo can be exported as a JPG file by doing a "Send to Text File" for that record.  The JPG file will be created with the following naming convention:  NamePhoto.jpg where name is the object name (uiname).    The JPG file will be created in the same directory as the DMP file. If multiple personnel objects containing photos are dumped out, a JPG for each will be created in the directory of the DMP file.