Issue BACnet Controllers do not show up on the Server side nor the Client side in WorkPlace Tech Link Builder Environment WorkPlace Tech all versions Cause The Extended Data of the controllers has not been discovered. Resolution The extended data of the BACnet controllers must first be discovered in Workplace Tech Commissioning Tool before the controllers will show up in Link Builder. The extended data of the controllers can be discovered two ways: Highlight all of the controllers in the Commissioning Tool then right-click the selected controllers and select “Refresh” before launching Link Builder. Click on "Auto Acquire Extended Data" from the Commissioning Tool menu before launching Link Builder The controllers should now appear when Link Builder is launched.

Issue Can WorkPlace Tech Link Builder be used to link I/A BACnet controllers to third party BACnet devices? Environment WorkPlace Tech (all Version) Cause I/A controllers do not have the ability to write to third party BACnet devices. Resolution Link builder will only link data from a third party device to BACnet "COVs" in our IA controllers. Our I/A controllers can pull data into our controllers as a client, but they can not function as a server and push data to third party devices.  

Issue When trying to edit a OGC graphic from Vista a error message is shown, "Can not find the Symbols file". And the OGC editor is not starting up. Environment Vista 4.2.5 Cause The symbols file used by the OGC graphic editor is not correctly defined. Resolution Open Workstation, click on TAC Vista Right click on $Symbols and select Properties Click on the 'source file name', browse to the $ini folder (in Vista 5.1.7 C:\Program Files\Schneider Electric\TAC Vista 5.1.7), find the symbols.sym file. Click OK

Issue Can not get CIPCL to autostart Environment TAC Vista Windows 2008 R2 Windows 7 Cause Windows will not allow modification of the registry unless the application is started with the "Run as Administrator" option. Resolution Right click on TAC Vista Server and choose Run as Administrator.

Issue Where is more information on Secure View? What is Secure View? Product Line Andover Continuum, Pelco Environment Continuum Secure View Pelco Cause What is SecureView Resolution The UK Buildings Business of Schneider Electric Limited has released Continuum SecureView, the add-on application offering seamless integration between Andover Continuum CyberStation and Pelco Endura CCTV system. This integrated solution provides the user with a powerful interface featuring live and recorded video streaming, PTZ (Pan / Tilt / Zoom) camera control from within the Continuum CyberStation Workstation itself, plus the ability to control external video monitors and layouts. For further details: Contact Technical Services paul.bates@schneider-electric.com PA-UK-11.00001 Continuum SecureView.pdf

Issue Can not edit the graphic pages of a Niagara G3 ENC station via a Web Browser Environment Niagara G3, ENC-410, ENC-520 Cause The PxEditor Module must be loaded on the ENC in order to edit PxViews via a browser. Resolution The PxEditor Module must be loaded on the ENC in order to edit PxViews via a browser. Open the Platform of the ENC Double-click on Software Manager Scroll down and highlight the PxEditor module (is will read “not installed”) Click the “Install” button and then “Commit” button at the bottom of the screen. The PxEditor module will now be installed to the ENC. Once the module installation is completed, the ENC’s graphics can then be edited via a web browser.  

Issue How to replace a 7798 I/Site on an existing system without causing any problems to the existing controllers. Environment All versions of I/Net and 7798B I/Site. Cause Not doing it properly could cause the system to go down and create problems later on that may or may not be recoverable. Resolution To properly replace a 7798 I/Site the following steps should be performed to ensure minimal downtime and the system is operational again. Perform a backup of the software and database of the controller. Remove power, unplug the wires for the C-Lan and Sublan. Change the controller and turn on the device but do not plug the Sublan plug back in. Make the necessary changes like address and baud rate etc to match the existing system. Once communications has been verified, download the bin file and database back to the controller and then plug the Sublan in again. Go to Edit/Host Computer/Network Configuration and penetrate the link summary that the controller is under and verify that all the devices are communicating and online again.

Issue Getting warning " Received bit string (25) is longer than expected length (23)" in the standard output window.  Is this a problem?   Environment I/A Series R2 G3 BACnet Niagara Cause This warning is because the UNC was reading the list of object types supported from the device, and the device was implemented to a different protocol revision, in which there were a different number of object types defined. Resolution The UNC ignores this, and it has no negative impact.  

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 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