Building Automation Knowledge Base

Issue Need to protect Continuum Workstations from Virus and Malware threats. Product Line Andover Continuum Environment Continuum Workstation Cause There are many Anti Virus applications on the market, how to choose which one to use on a Continuum Workstation machine. Resolution We do not qualify any specific Anti Virus applications or definitions for use with Continuum software. You can use whatever Anti Virus you want on the machine Continuum is installed on as long as Continuum was installed when that Anti Virus was disabled as this can hinder files from being copied, dll's from being registered, and registry entries from being created / modified. If there are conflicts with Continuum and the specific Anti Virus application being used, you may need to add the Continuum folder and / or the Continuum processes to the exclusion lists. For details on specific environments that have been qualified with Continuum see Software and Firmware compatibility matrix for older versions of the traditional product lines.

Issue Installing I/NET on a PC using MSDE and MSDE won't start. Product Line TAC INET Environment I/NET Version 2.40 and above Windows 7 MSDE Cause MSDE does not run on Windows 7. Resolution If the user has attempted this, more than likely the OS has corrupted SQL. There are a couple of things that can be done as described in Verify in Windows Registry all items are deleted after uninstall of I/NET Seven and MS SQL. However to return the PC to its original state the best bet would be to reinstall the OS, or a backup prior to the installation of I/NET.

Issue During Vista Installation, receive error message “SQL server service cannot be started” or "Failed to start SQL Server service!". Product Line TAC Vista Environment TAC Vista 5.X.X (Tested on Windows XP SP3 with SQL server 2005 EXPRESS) Cause This issue typically happens after uninstall an earlier version of Vista, and then install a newer version of Vista with the built in SQL server (SQL server 2005 express). Sometimes the SQL server registry key is remained on the computer during the uninstall process. When new installation happens, Vista thinks there is an existing SQL sever; however a failure will occur when try to start the SQL Server service. Resolution It is recommended to use the installation file to uninstall TAC Vista 5.X.X. Follow How to uninstall and completely remove TAC Vista 5 to make sure all files and folders are removed.   Check if SQL Server Service still exists: Right click on “My Computer” and choose “Manage”. Chose “Services and Applications" -> "Services". Check if “SQL Server (TACVISTA)” is listed, if yes, go to next step. Otherwise, restart the computer then run the installation again, issue should be solved now.    Go to “start->Run->regedit” to open “Registry Editor”.   Go to “HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services/”. Find “MSSQL$TACVISTA” and “MSSQLServerADHelper”. Then delete both registry folders.   Repeat step 4 for “CurrentControlSet001” and “CurrentControlSet003” under “HKEY_LOCAL_MACHINE/SYSTEM/.   Restart computer and run the installation again. Issue should be solved now.

Issue Error Codes: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Product Line Andover Continuum Environment Continuum Site with BCX Controllers and an Error Log Cause Crash of BCX and log reveals: Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1629 E 04/05/2012 10:51:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000 Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1630 E 04/05/2012 10:53:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1631 E 04/05/2012 10:55:30.00 0x0000640b 0x04dd8500 0x02124e26 0x00005c20 0x00000000  Error Code Meaning: The Error Sys Var has been incremented Line Level Time Stamp Error Code TCB Addr Prg Cntr Data1 Data2 1632 E 04/05/2012 10:57:30.00 0x00001c0b 0x04dd8500 0x02124e26 0x0000640b 0x00000000  Error Code Meaning: GLB_ELOG_DUP_START Resolution It is in the range of “Global System errors” that is usually not good, either faulty controller or need reloading of the O/S. Cold start and update O/S with the latest version supported by the Cyberstation version. Then run it on a test rig with different ID and see if it still crashes, if so will need to be repaired or replaced.

Issue The B0cfglog.txt file located in the Vista database $log folder and Alarms in Vista are getting the error: Physical unit "Unit Name" on node "Node Name" is a duplicate by uid=### with "Unit Name" on node "Node Name" Product Line TAC Vista Environment Noded Vista Server Master / Slave Vista Cause Conflicting UID in a Master/Slave node network. Master Vista Server or Master. In a Vista network/system containing several Vista Servers, one of the Vista Servers is the Master Vista Server, managing and communicating system-specific information and global settings throughout the Vista network/system. Slave Vista Server or Slave. The Slave Vista Servers in a Vista system receive system-specific information and global settings from the Master in the Vista network/system. If once standalone servers are all added to one Master network, the Master assigns a unique ID to each slave. Normally when a UID gets duplicated the master tells the servers correct the duplication. Sometimes this automated fix cannot occur because the duplication prevents the proper communication. In this case, the slaves need to re-establish communication with each other and be restarted. Resolution Delete the slaved node Update Vista to reflect the node is removed Adding the node back Restart Vista Server The UID should be resolved and the error should not be present.  If the error still comes up please try the following steps: Make current backups of all Vista Databases Close the slave server Open the mater server When asked, "Do you want to change identities on this node?" select Yes Close the master server and reopen both the mater and the salve server and the error should be gone Instructions on how to add the Vista Slave node onto the master can be found in Creating TAC Vista multi-server network. For this to work, the slaves need to be able to see each other as well. If you do not want the slaves to see each other, add them while balancing the load on the network. They can later be removed when the problem is not occurring anymore. 

Issue "No license available" message appears some while after having logged in to Webstation. Product Line TAC Vista Environment Vista 5.1.6 Windows 2008 Server Internet Information Services (IIS) IIS 7.0 or higher Cause This is most likely due to a corrupt IIS installation. Resolution Reinstall IIS Reinstall Webstation The steps for this are outlined in Problems installing Vista Webstation 5.1.5 or newer.

Issue Are Standard and Enterprise Editions of Windows Operating Systems supported for use with Continuum / WebClient Software? Product Line Andover Continuum Environment Continuum Cyberstation Continuum WebClient Continuum SQL Server Cause The Compatibility Matrix does not stipulate if the supported Operating Systems are Standard or Enterprise editions. Resolution You can use either Enterprise or Standard Editions of the various supported Operating Systems with Continuum / WebClient. See Software and Firmware compatibility matrix for older versions of the traditional product lines for the current Compatibility Matrix showing supported Operating Systems.

Issue The user logged into Windows doesn't have permissions to the folder that contains the Continuum.mnu file,  the file is set to read only or the path in the continuum.mnu is incorrect. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Permissions are restricted to the Continuum.mnu file or the path in it is incorrect. Resolution One of the follow solutions will resolve this: Click to download an edited default path Continuum.mnu and Menu.bmp  (links for the default path C:\Program Files (x86)\Continuum) Copy these files to each workstation that has an incorrect path Manually edit the file yourself if you have a path that is other than (C:\Program Files (x86)\Continuum) Grant permissions to the folder. The folder that contains the Continuum.mnu can be located by editing the Cyberstation in Continuum Explorer. WS Edit> Preferences tab> The file name of the main menu  Ex. c:\program files\continuum\userprofile\continuum.mnu Right click on Continuum.mnu and select properties. Deselect Read Only if it is selected. Change the path to the Continuum.mnu file to a folder that you have access to and copy the continuum.mnu to it. Ex. c:\program files\continuum\continuum.mnu While in edit mode, right click on each of the buttons and select Properties Use the browse button to select the correct x86 path (C:\Program Files (x86)\Continuum) Repeat this for each of the buttons and then save the Continuum.mnu file Copy these files to each workstation that has an incorrect path Also see Continuum.mnu file with C:\program files (x86) on 64 bit PCs points to C:\program Files and shows a blank screen.

Issue If a Xenta I/O module has experienced a hardware failure it may be necessary to replace it with a new controller. Product Line TAC Vista Environment Xenta I/O Modules Xenta 411, 421, 422, 422A, 452, 452A, 471, 491 Cause Hardware failure of a Xenta I/O module requires it to be replaced. Resolution Physically replace the I/O module The next steps depend on whether the I/O module is part of an LNS system or a Vista Classic Network. LNS System Right click on the I/O module in the LNS management tool (LonMaker or NL220) Select Replace Service pin or manually enter the new neuron ID Open Vista System Plug-in Update the TAC Network Update the Vista database Download the base programmable controller Vista Classic Network Go to How to set the neuron ID of an I/O Module in a Vista classic network for instructions on setting the neuron ID for the new I/O module. Service pin or manually enter the new neuron ID Download the base programmable controller

Issue Can the XPSI 4.1 software communicate to a GCM via a modem connection? Product Line TAC IA Series Environment XPSI/PSI 4.1 GCM-86xxx GCM-84xxx Cause When capturing trend log data over an unapproved modem, the program lost sync with the incoming data after receiving about 10 lines of log data. Resolution The only modem currently approved for communications with GCMs is the USRobotics 56k (USR5686E). The configuration information for this modem was published in Technical Bulletin 00-47 with model update information published in Technical Bulletin TB03-04. NOTE: If using the USR5686E with older modems, the V.92 communications protocol must be disabled -- see Modems fail to connect with the USRobotics 5686 series V.92 modems for details.

Issue The time taken for values to change on a Sigma client is a lot slower then the change of values for the Modbus devices, how can this be sped up? Product Line Satchwell Sigma Environment Sigma Modbus RS-232 RS-485 TCP502 Cause Modbus protocol is a polling type and configuration changes to default settings can be made to speed up data collection for the IC3 Modbus controller.   Resolution There are changes that can be made to default settings that can allow the IC3 Modbus to collect data at a quicker or a more efficient way.  It should be noted that these changes can be counter productive and should not be applied without careful thought to the consequences.  That is, the third party Modbus device may not respond quickly enough for the IC3 Modbus request and therefore cause a retry, particularly on RS485 LANs. 1. For RS485/232 communications LAN it is important to check the LAN installation is correct.  See Investigating Modbus devices shown as offline in Sigma particularly if Modbus controllers are going offline.  Note:  Modbus is a polling protocol and failures and subsequent retries will slow down the update rates for those devices online. 2. Changes to the IC3 Modbus gateway.txt file;     a) Increase baud rate ; Default Baud Rate (e.g. 1200) 9600 If the third party device (RS485) supports it, the baud rate can be increased.  But, if the communications environment is poor then reducing may be the better alternative.    b)  Retry counters and timers ; RTU message separation time 18 -  The delay to the next IC3 Modbus request following a previous reply.  Should be increased to 200 or more to prevent timeout ; Retry Check Period 1 - Time in seconds after a failure. Suggest 1 second ; Number Of Retries 3 - Number of times to perform a retry before moving on to the next register.  Suggest 3. ; Device Reset Interval 0x01 ; Device Down Interval 0x01  - Set to 0x01 is the retry time once a failure has occurred and before the next time it will attempt device again (0x01 = 60 seconds)    c) Delay between controllers In the body of the mapping table the 5th field is the minimum time before polling the same device and can be set to zero 31,2,3,0,1,0x0007,0,0,1    d) Up to 7 consecutive Modbus registers can be read simultaneously In the body of the mapping table the 6th field is the number of consecutive fields to be read.  This can be increased up to 7, but both the Modbus register numbers and Sigma object numbers must be consecutive 31,2,3,0,1,7,0,0,1  ;ModBMS Test2 40001 38,2,3,7,1,4,0,0,1  ;ModBMS Test2 40008 3. Changes to the Sigma objects.  Note: these changes do not affect the Modbus update rate but can increase the displayed or graphic update rate.      a) Scan priority number decrease Selected Sigma objects can have there Scan Priority decreased or those Sigma objects that do not update as quickly increased allowing the IC3 Modbus controller to process the critical objects more often      b) Tolerance value - particularly for Graphic, Dynaview and Actipane displays Modify the Sigma object tolerance to match that of the object value.  See Sigma graphic only updates when first opened and no regular updates occur there after

Issue Xenta server trend logs are mixed up or missing when logged to SQL. For example log a from Xenta server 1 is logged under log a in Xenta server 2. This causes duplicates for some logs and missing logs for others. Product Line TAC Vista Environment Vista 5.1.X Xenta server 5.1.X with trendlogs that are retrieved by Vista and logged to SQL. Cause When creating the Xenta servers, copy/paste has been used in Vista. Using copy/paste causes certain references to be created incorrectly. Resolution !If you have already encountered the behaviour described contact Product Support! Otherwise read on... The correct way to engineer Xenta servers in Vista when the XBuilder project is to be reused. Right-click on the server object in Vista and select New->Xenta Server X5\7\9xx Right-click the newly created Xenta server and select Edit In the XBuilder project that opens, configure and download your project to the Xenta server. Close the XBuilder and save the changes to the current project when prompted. Refresh Vista and ensure that everything is online and correct in the Xenta server. To reuse this project in another Xenta server Right-click the Xenta server in Vista and select Edit. Make the appropriate changes to the project e.g. change the IP address. You can now either save the project as a template or choose Save as from the file menu. Rename the file and save it. After saving, select the menu item Vista Database->Save As and navigate to the Vista server object in the dialogue that opens. Right-click in the dialogue window and select New->Xenta Server X5\7\9xx. Choose an appropriate name and then click on Select. Go to Vista workstation and update the server object. The new Xenta server should now appear. Now it has been created it can be edited further and then downloaded to via XBuilder.   Note: If the trend log values are mixed up also in the Xenta Server itself (i.e. in a trend log page) it may be a different issue, see Trend log values from M-bus meters under a Xenta Server are mixed up.

Issue The option is not available to read card data in. Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause An enrollment reader hasn't been configured or the data being read in is duplicated. Resolution Wire a typical reader to an CX9680 with an AC1/AC1Plus or ACX57xx. This will not be attached to a physical door. Configure the enrollment reader in Personnel Manager. For details see Configure an enrollment reader in Continuum. See the attached document from the Continuum help system for additional help on using the enrollment reader to read card info.

Issue How is Sigma data transferred between Sigma Clients (Remote and Web) and the Sigma Server? Product Line Satchwell Sigma Environment Sigma Remote Client WebClient Cause How is Sigma data transferred between Sigma Clients (Remote and Web) and the Sigma Server? Resolution Data e.g. Index, point files, log data, alarm data etc is transferred between client and server using ports TCP 3614 and HTTP 8080. The HTTP port 8080 is configurable via "SetupSvr" in c:\sigma\bin. Data is not encrypted but a proprietary method is used. The TCP Port 8080 is also used by the clients for keep alive communications. Passwords are encrypted and are also transferred by TCP internet protocol using ports 8080 and 3614, Usernames are not encrypted. See Sigma Username and Password encryption for further detail.

Issue All or a group of Analog Inputs on my Controller (DCU 7700) are reading high (flooding), in alarm and / or displayed as "OLD'. Product Line TAC INET Environment I/NET All model series DCU 77xx Cause The inputs on a DCU 7700 are 1-5 Volt DC inputs. If the voltage of an input goes above 5 Volts DC the voltage will flood across the other inputs and they will all go out of range or OLD. Resolution To diagnose the problem sensor perform the following: Measure all inputs (Between terminal 9 and the respective input terminal) one at a time and identify the input that is the highest voltage (above 5 Volts.) Disconnect this input and then place your meter between terminal 9 and the identified input terminal. The excess voltage will slowly drain away and all the other points will come back into normal operating range. If the voltage does not drop repeat the above steps. Replace / Repair the fault sensor(s). Also refer to Analog inputs are reading too high or too low on a 7780.

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 After time settings have been confirmed as per "The time on the workstation is less than the time of one or more controller log entries"., some ExtendedLog points are not being gathered. The below time synchronization errors are seen in the Errors Listview. Extended logging time synchronization problem. The time on the workstation is less than the time of one or more controller log entries. Product Line Andover Continuum Environment Continuum Cyberstation Cause Due to the incorrect time settings previously configured, the controllers may have log events that occur in the future (as far as the Workstation gathering the logs is concerned). Resolution Reload the controller that has the ExtendedLog points showing this error, this will clear out the local log entries and allow the Workstation to gather new log entries.

Issue When the need arises to change object paths in OGC graphics the Vista reference changer does not work. Product Line TAC Vista Environment Vista 5.x.x Cause For unknown reasons the reference changer does not seem to work well on all OGC databases. Resolution The first thing to try is to edit the OGC after an attempt has been made with the reference changer. If the links have been updated saving the OGC back to the Vista database can sometimes work. If this did not work you can use the reference changer in the OGC editor. Graphics binding were broken after a Vista upgrade to 4.5 from an earlier version is a link on that process.

Issue Site License is not working after upgrading to Vista 5.1.4 or newer. Product Line TAC Vista Environment Vista License Cause The path to the License Server (lmgrd.exe) and License File (Licensename.lic) is incorrect because the default Vista installation folder changed from TAC in 5.1.3 and older to Schneider Electric 5.1.4 and newer. Resolution Stop and close TAC Vista Server, Workstation, etc. Open the LMTOOLS utility from the Start menu: All Programs/Schneider Electric/TAC Tools 5.x.x/LMTOOLS Under "Config Services Tab", ensure the path to licenses file is correct ,C:/Program Files/Schneider Electric/License. Under "Start/Stop/Reread" tab, check "Force Server Shutdown" box. In order click, "Stop Server", "Start Server", "Reread License File". You should receive a message stating the Reread License File Completed. Start any TAC application other than Vista Server (for example: TAC Menta). You will be prompted to "Specify the License Server System" or "Specify the License File". Select "Specify the License Server System" and enter the computer name. Alternatively, If the License Server resides on the local machine, you may type "localhost" as the computer name. If the above is unsuccessful, follow the full steps in the resolution of TAC Vista 5.0 to 5.1.7 license does not work after installation which will also correct the path name to Schneider Electric.

Issue Need a wiring diagram of the breakout box connections between the Reader and the 7910 or 7920 DPU. Product Line TAC INET Environment I/NET site Cause Need a wiring diagram of the breakout box connections between the Reader and the 7910 or 7920 DPU. Resolution Recommend you look in TCON 112 (Readers) for illustrations the match your requirements. Check for TCON Number and Title Cross Reference (with links).

Issue Determine if the DX Series of video recorders is compatible with Continuum Product Line Andover Continuum Environment Pelco DX Series Video Recorder Continuum Cause Sites may have existing DX Series Video or want to purchase them for their video needs and may want to integrate that video into Continuum Resolution Check to see if the  DX Series video recorder is compatible with Continuum Please see the following link for the Continuum and Pelco compatibility matrix in Software and Firmware compatibility matrix for older versions of the traditional product lines