Building Automation Knowledge Base

Issue Digital Sentry Control Point  and Cyberstation have conflicts with both pieces of software on the same PC. Environment Cyberstation Digital Sentry Control Point Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause The Cyberstation Video Integration and Digital Sentry Control Point use the same API to communicate and could cause issues. Resolution This configuration is not officially supported or tested, although we have reports that say people are doing it in the field. The reason it is not supported is because they both depend on the same DSConnex API. Installing both may introduce Windows registry issues. (causing issues with whichever application was first installed). From the field Without Control Point installed controllers were online. If only control point is installed they can view Video once Continuum is installed they can no longer view Video. Both program work independently of each other but not together, last one installed works. The configuration of having Digital Sentry Control Point and Cyberstation Video Integration installed on the same PC is not supported. The reason that it is not supported is because both products use the same API (Application Programming Interface) files in order to display video. There could also be Windows registry issues particularly if different versions of the API files are getting installed by each application.   An example from the field If only Control Point is installed the site could view video normally. Once Continuum was installed, video will no longer display in Control Point. Both programs work independently of each other, however, typically the last program that gets installed is the one that will work and the first program installed gets broken, so that video will not display.

Issue Need to obtain points InstanceIDs to provide to third party vendor for system integration. Environment bCX4040 b3s devices Cause Third party vendor system integration Resolution The instanceID of a BACnet object can be shown in a List View. In a list view configuration add a column to display InstanceId, the id will be shown as two numbers separated by a forward slash '/', the number after the '/' is the instance id. i.e. 73009/59 In the example above 59 is the instance id. Note that in BACnet the InstanceId of an object is a 32 bit number where the ten most significant bits contain the object class and the other 22 bits is the actual id. CyberStation strips the object class when showing an object's instance id. If the RoamIO BACnet service tool is used it can be configured to display the full instance id without stripping the object type from the value.

Issue At times it is necessary to get the Cyberstation product and database version without launching Cyberstation Environment Cyberstation Webclient Windows XP Windows Vista Windows 7 Window Server 2003 Windows Server 2008 Cause Need the ability to get the Cyberstation version without launching Cyberstation Resolution Using My Computer or Windows Explorer Navigate to c:\program files\Continuum Right Click on Continuum.exe Select Properties Select Version Select Product Version 1.74.0.20070914= 1.74 with No Service Pack Ex. 1.74.0.20070914 SP2 = 1.74 with Service Pack 2   To determine the database version in SQL: Use the SQL Server Studio Management Express and open the table "dbo.ACCDBVersion". This will show the database version as well as the Enhanced Alarm Logging and Enhanced Alarm Delivery status. 

Issue AccTrace shows error  "SQLSTATE ERROR CODE: 37000" and "ERROR MESSAGE: [Microsoft][ODBC SQL Server Driver][SQL Server]Failed to load msxmlsql.dll." every extendedlog interval.   The ExtendedLog does not work and no log data are found in the Database. Environment SQL Server Cyberstation NetController. Cause The "msxmlsql.dll" file has been deleted from SQL server by an anti-virus software or the security setting changes. Resolution Obtain the msxmlsql.dll and msxmlsql.rll files from the SQL Server installation kit.  

Issue In older versions of Vista (<5.1.5), LMTools version 11.4 is used, and seems to crash sometimes when using the diagnostics functions.  Environment Vista 5.1.4 and older Cause Unstable software Resolution Upgrade LMGRD.exe and LMTools.exe by replacing them with files of version 11.6 that can be found in TAC Vista versions 5.1.5 and later.

Issue Is it possible to create host bindings to Vista using NL220? Environment Vista 5.1.7 NL220 Cause Yes it is possible but you must use a Loytec network interface Resolution Create binding to the LON interface in NL220 and use the Vista System Plug-in to import the project to Vista

Issue Material specification for stainless steel sensor pockets Product Line Field Devices Environment Sensor pockets Cause Some customers require a specification on the material used for the sensor pockets in stainless steel. Resolution Our stainless steel pockets are manufactured from V4A material (1.4571). - material constants: 1. VA   Material No. 1.4571   EN symbol (short) X6CrNiMoTi17-12-2   AISI/SAE 316 Ti   UNS S 31635   AFNOR Z 6 CNDT 17.12   B.S. 320 S 17, 320 S18, 320 S31   alloy —   Registered work's label —   Standards VdTÜV 454     Chemical composition C Si Mn P S* Cr Mo Ni Ti ≤ 0,08 ≤ 1,0 ≤ 2,0 ≤ 0,045 ≤ 0,015 16,5–18,5 2,0-2,5 10,5-13,5 5 x C ≤ 0,70                   * for long products S ≤ 0,30; for products to be processed S = 0,015–0,030                           Special characteristics Temperature range Dichte kg/dm³ Hardness HB 30 up to 550° C 8 ≤215  

Issue Which products have been independently assessed by the BACnet International BTL labs? Environment BACnet approvals BACnet Building Controller (B-BC) BACnet Advanced Application Controller (B-AAC) BACnet Application Specific Controller (B-ASC) Other BACnet Device (B-Oth)  Cause The Continuum & I/A Datasheets define that the products are BTL approved, but where can more information be obtained? Resolution Go to the independent BACnet International BACnet Testing Laboratories web site and select Schneider Electric, This shows all of our BACnet approved products and will answer many typical BACnet related questions. See link:  http://www.bacnetinternational.net/btl/

Issue When closing Continuum 1.9x SU (SQL 2005 Express engine on a stand alone workstation),  it shows MFC error message of ACCDataServices and the Windows Event Log shows AlmUtil.dll error message. Environment Continuum SU 1.82 and higher version. Cause There are 3 Windows Schedule Tasks which are created during the DBInitialization->Creation of the Continuum SU workstation. Some possible causes are: If these Schedule Tasks are missing The Windows Schedule Tasks cannot be executed due to that fact that the current login userID is different than the one setup for the Schedule Tasks The password is not correct Resolution Manually create these 3 Schedule Tasks in the SU Cyberstation Alternatively: Uninstall SQL engine, Continuum Reboot the Workstation Reinstall Continuum SU, create a new DB from DB Initialization. Verify these 3 Schedule Tasks are created as below: CS_Distn CS_hrly CS_Minute

Issue Equalization Failure.  Unable to promote remote or equalized client Environment I/NET Seven Cause I/NET Seven creates and used the user account INETSEVEN within SQL. This account is given full admin rights during installation and any change in these rights will prevent I/NET from correctly using SQL.  The password for this account is encrypted and is specific to each I/NET installation so this password cannot be provided. Resolution Do not change settings on this account.  If modifications are made you will need to uninstall and re-install I/NET Seven.

Issue The department names were created using all caps. When viewing the attribute after changing and saving to mixed case, it is still all caps.  Environment CyberStation (all versions) Cause Trying to change Department attribute from all caps to mixed case. The change will not save. Resolution When changing just the case of an attribute (like Department) and saving it, it will revert to what you had before the change because CyberStation does not regard a case change as a change. If you want to change the department, for example, from pss to PSS you need to change to something with different characters like pss1 and save it. Then change it to PSS and save it. Now it will be PSS.  

Issue Values are displayed in scientific notation (form) when using the folders view. Environment Vista 4 and Vista 5 Cause When Vista needs to display a number larger than 10,000,000 it converts it to scientific notation (or also known as exponential notation).  So the number of character that need to be displayed are less it displays the number in the following format: 10e6. Resolution This is a normal operation of Vista for large values. The best solution is to reduce the size of the number. For example go from kilowatts to megawatts. You can do this by binding the SNVT into a Xenta controller and do a conversion in the controller.  If in a classic lonworks network, you can use an object transfer to bring the SNVT into Menta.

Issue At time it is necessary when troubleshooting to check specific communication settings on a comm port Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Specific commands needed to check communication parameters with precision and to edit them if necessary Resolution Examples of command line parameters needed for Xdriver modbus communication. Command Result p comm2 defaultbaud 9600 comm2 defaultbaud=baud19200 (To set) p comm2 defaultbaud 19200 p comm2 parity None comm2 parity=Odd (To set) p comm2 parity Odd p comm2 stopbits stopbits1 comm2 stopbits=stopbits2 (To set) p comm2 stopbits stopbits2 p comm2 datalength databits8 comm2 databits=databits7 (To set) p comm2 datalength databits7

Issue How do I request a new TIP license for the I/A Series R2 software? Environment I/A Series R2 software installation Cause I/A Series R2 License request process for field offices on the TIP program has changed. Resolution See Product Announcement PA-00186 for details. Please note that the demo license described in this document is only available to our partner offices that participate in the TIP program.  If your office does not participate in the program, please contact your regional sales manager for more information.

Issue Replacement stuffing box for valve V222 Environment V222: 721-2254-000 DN65 721-2258-000 DN80 721-2262-000 DN100 721-2266-000 DN125 721-2270-000 DN150 Gland Service kit (Packing box, Stuffing box): DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0 Cause Replacement parts for gland service Resolution Replacement gland service kits for V222: DN65-100:  1 001 0820-0 DN125-150:  1 001 0821-0

Issue Running SQL 2008 on a Windows 7 OS Product Line TAC INET Environment I/NET version 2.41 SQL 2008 Windows 7 Cause SQL 2008 and I/NET version 2.41 on a Windows 7 PC. Resolution Note: Do not install Microsoft SQL Server 2008 Express Edition on the filemaster of an equalized TAC I/NET Seven system. This database engine does not provide the replication services that are required on the filemaster. Microsoft SQL Server 2008 Express Edition is a scaled down, free edition of Microsoft SQL Server 2008, which includes the core database engine. While there are no limitations on the number of databases or users supported, it is limited to using one processor, 1 GB memory and 10 GB database files. Microsoft SQL Server 2008 Express is included on the TAC I/NET Seven installation disk in the SQLExpress folder (installation instructions are in the SQL2008 Expr Install Inst.pdf file included in the folder). Microsoft SQL Server 2008 Express Edition does not provide the replication services that are required on the filemaster. To use Microsoft SQL 2008 as the SQL engine for an equalized TAC I/NET Seven system, install Microsoft SQL Server 2008 Standard Edition on the filemaster. You can then use Microsoft SQL Server 2008 Express Edition on each equalized client. I/NET Seven supports the use of Microsoft SQL Server 2008 Express 32-bit Edition running on Windows 7 Professional 32-bit. The PC should have at least 2 gigabytes of RAM. Microsoft SQL Server 2008 32-bit (see notes 1, 2, 3, and 5   Freely Distributed with I/NET Maximum Database Size Maximum Concurrent Users Operating Systems Supported SQL Server 2008 Express (32-bit) (See note 4) Yes 10 GB Unlimited Windows 7 Professional 32-bit SQL Server 2008 Standard (32-bit) No Unlimited Unlimited Windows 7 Professional 32-bit Do not mix versions of SQL server among equalized or client/server workstations in your TAC I/NET Seven system. Ensure that the edition of SQL server installed on each workstation used in a client/server or equalized setting are based on the same version of Microsoft SQL, either 2000, 2005, or 2008 It is strongly recommended that you defragment the PC’s hard drives on a regular basis. Severely fragmented hard drives can cause poor system performance and in some cases can introduce data errors. The use of Microsoft SQL Server 2005 Standard or Enterprise edition, or any edition of Microsoft SQL Server 2008 will require that the PC have at least 2 GB of RAM. Microsoft SQL Server 2005/2008 Express Edition cannot be used on a TAC I/NET Seven filemaster. Only 32-bit versions of SQL Server and Windows 7 Professional are supported.

Issue TGML function Convert Status doesn't seem to work for forced Values Environment TGML 5.1.5 or higher. Cause Vista will always identify forced values as online values. As mentioned in 5.1.7 release notes Resolution This can be scripted in other ways in TGML if it is necessary to show when a value is forced.

Issue Customer has previously purchased the WorkPlace Tech software release 4 and wants to know if there are any controllers available that can be programmed with the release 4. Environment WorkPlace Tech release 4.0 Existing MNL controllers of various releases. Cause WorkPlace Tech release 4.0 generates an error message when an existing application created for an old version of an MNL controller is downloaded into a new controller. Resolution See the section "Controller Firmware Revisions" in Chapter 1 of the WorkPlace Tech Tool 4.0 Engineering Guide for a explanation of the LON controller firmware versions.  If the controller application was programmed for use with an earlier version of the controller,  the application must be updated to the current version before the application can be downloaded into the controller.  Current production controllers contain revision 4.1 firmware.  The revision 4.1 controller model numbers are as follows:  MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F3, R3, H3 , S3 or S4), MNL-11RF3, MNL-13RF3 or MNL-VxRV3 (where x is 1, 2 or 3).    Older production controllers can be identified by the following model number series: MNL-10Rx1, MNL-20Rx1, MNL-VxRV1, MNL-5Rxx, MNL-10Rxx, MNL-15Rxx, MNL-20Rxx (where xx is F2, R2, H2 , S1 or S2), MNL-11RF2, MNL-13RF2 or MNL-VxRV2 To convert the application controller version, use the WorkPlace Tech "Hardware Wizard" after opening the application file. Open the Hardware Wizard. Click the [< Back] button at the bottom of the Hardware Wizard window to display the Controller Selection screen. Note that the current controller version for the application will be displayed in the box at the bottom of the window. If the old controller type is a MN V1, MN V2 or MN V3, select the [MN VAV] tab otherwise select the tab corresponding to the displayed controller type. On the controller selection page, select the model number of the new controller to be used for the application.  If the controllers are using the "Satellite" profile and the old controller was a "Satellite 1" profile, select the "Satellite 3" profile for the new controller.  Select "Satellite 4" if the old controller was a "Satellite 2" profile.  For all other controllers, select the new controller with the same profile type (Fan Coil, Heat Pump, Roof Top) as the original.  After selecting the controller profile for the replacement controller (in step 5), verify that the controller model number shown (MNL-xxxxx) matches the original controller, except for the last digit.  This is the model number of the controller that should be used for the replacement. Click the [Next] button to accept the new controller type selection then click the [Next] button to accept the controller configuration. Click the [Finish] button to exit the Hardware Wizard and apply the changes to the application. The application can then be compiled and downloaded to the new controller.

Issue ACX5740 controllers are found to have lost configuration and programming after power loss.  Environment ACX5740 ACX5720 NCII BCX B4920 Cause Controller cannot restore data from flash memory due to the presence of corrupt or a flash backup that was saved before the controller was redeployed at another location or that has been upgraded to a different firmware version. Resolution From the controller configuration page select Clear Database Backup and commit changes to controller.  Reload the controller. Backup controller to flash to ensure that current information is backed up.

Issue Opening a pinpoint graphic from Continuum Explorer takes long time or cannot open with the error Timeout error.  Environment Continuum LAN with WSs' pointing the shared folder of the pinpoint files. Continuum SU with additional WSs' pointing the shared folder of the pinpoint files Cause It takes longer time for workstation to get connection to the shared folder on the network when the pinpoint is configured to use the ServerName\SharedFolderName (or IP_Address\SharedFolderName) instead of Mapped drive. Resolution Map the shared folder of the server to each workstation as a network drive and use the mapped drive name in the Options setting of the pinpoint editor. Also, check if the issue is related to a Windows profile. Create a new Windows Admin user and see if the slowness persists. If it doesn't then the issue is a corrupted Windows profile.