Building Automation Knowledge Base

Issue This typically happens after upgrading Continuum on a workstation that uses add-on reporting. When attempting to run the reports this error pops up. Environment Continuum Environment with reporting requirements Cause ODBC settings altered on the upgrade.   Note: No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the “Reset_Password.bat” batch file to re-enter the default Continuum DB password.   Note: No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the “Reset_Password.bat” batch file to re-enter the default Continuum DB password. Resolution   The password needs to be re-entered. No password checking is performed by this screen. The password is only saved. When you subsequently launch Continuum Reports, the password will be used to connect to the Continuum Database. If the password is incorrect, or entered incorrectly, an ODBC error screen will appear when it tries to connect using the invalid password. In this situation, re-run the C:\Program Files\Continuum_Reports\Reset_Password.bat batch file to re-enter the default Continuum DB password. (i.e. Andover97)

Issue MSMQ error starting Continuum. "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ." Environment Continuum loaded on a Microsoft Operating System computer Cause MSMQ has become corrupt on this PC. Resolution Continuum cannot be installed on XP HOME(XP Professional only) Verify that the msmq service is started Go to Add/Remove programs > Add/Remove Windows Components does not give the option of installing Message Queuing. Go to a DOS Prompt and change your directory to C:\Program Files\Continuum\Install (cd \Program Files\Continuum\Install) Run the batch file Runafterreboot.bat (This will reinstall the Continuum version of MSMQ. NOTE: Most recent versions of CyberStation RunAfterReboot.bat has been renamed InstallMSMQ.bat Run the batch file and re-boot the machine then run Continuum ** In some cases Windows Add/Remove programs may not completely remove MSMQ and a utility like Revo Uninstaller may be helpful in getting a clean uninstall, so that a reinstall is successful.

Issue RAM can generate an interface alarm after Sigma has been upgraded to release 4.05. Environment All Windows supported versions. Cause Prior to Sigma release 4.05, the Alarm manager (Alarmcli.exe) was monitored by the Remote Alarm Manager. Sigma 4.05 no longer has this file, and therefore the Remote Alarm Manager produces an interface alarm because it is unable to see the Alarm Client running. Resolution When using Sigma 4.05, start the Remote Alarm Manager services and open the Console. Select the configuration tab, and then choose “Interfaces”, now select “Sigma (R4) RAMServer”. Go to the “Applications” option and deselect “Sigma Alarm Manager (alarmcli.exe)”.

Issue The Remote Alarm Manager is unable to send Sigma Longtext messages as part of the RAM message. Environment All supported Windows platforms. Cause Prior to Sigma release 4.05, Long Text messages were stored individually in the Sigma\Data\LongText folder. Sigma 4.05 introduces a new combined format of record (LongText.rec) and a storage location in the Sigma\Data folder. The Remote Alarm Manager does not recognise the file. Resolution Upgrading an existing Sigma site to Sigma 4.05 with RAM installed, and where RAM is required to use Sigma Long Text messages. Upgrade the Sigma system and retain the Sigma\Data\LongText folder.   Adding a new Long Text message Create the new message using the Sigma 4.05 Long Text editor. Copy the message and create a new message called Ltxt???.txt under Sigma\Data\LongText,   Configuring a Sigma 4.05 system where RAM is to be installed, and where RAM is required to use Sigma Long Text messages. Creating a Long Text message Create the new message using the Sigma 4.05 Long Text editor. Create a new folder Sigma\Data\LongText. Copy the message and create a new message called Ltxt???.txt under Sigma\Data\LongText, where ??? is a unique number.

Issue When trying to right click on the Xenta object in LonMaker to get the Plug-in option, it is not in the dropdown list. Unable to open plug-in for Xenta 100 series devices Environment Xenta 100 Plug-in LonMaker NL220 Xenta 101-VF, Xenta 102-ES, Xenta 102-B, Xenta 102-VF, Xenta 102-EF, Xenta 103, Xenta 104-A, Xenta 110 Cause If the option to launch a plug-in is not available, it may be because the plug-in is not installed and/or registered.  Plug-ins for most Xenta 100 devices are accessed through the function block, right-clicking on the controller will not bring up the correct menu. Most LON plug-ins are launched by right-clicking on the function block, not the controller.  The exception to this rule is the Xenta 102-AX, which requires you to right-click on the controller. Resolution Ensure the correct version of the plug-in you are trying to launch is installed and registered. Navigate to LonMaker > Network Properties > Plug-in Registration > Already Registered. If not, Register. In general, Xenta ASCs require you to right-click on the function block and select Plug-Ins to launch the plug-in. Note: It may be necessary to first add a function block in LonMaker, even if SNVT bindings are not required.

Issue It is not possible to access graphics in a Xenta 5/7xx from a smart phone mobile app. Environment Xenta 511, 527, 711, 731 Smart Phones: Apple iPhone, iPad, Android Cause Graphics in a Xenta 5/7xx webserver render in the web environment using Java.  There is not currently a smart phone in the market that is works with Java applets. Resolution There is currently no supported mobile solution for viewing graphics in a Xenta web server. 

Issue When service pin the device in LonMaker system plug-in, an error message pops up saying: Neuron ID has been used by another device, and NID went to all 0. Environment Cause some old device information got stuck in the database the device was added into the network earlier, and the user forgot about that Resolution Delete the node/device from the network. Resynchronize the drawing with database. If the device comes back, then means some information was stuck in the database. Simply delete the device again. Resynchronize again to make sure it was truly deleted. Redo this procedure if needed. If nothing changes on the drawing, then the device was added into the network before, now you need to find where it was added. Open the Echelon LNS Report Generator (Start-> All programs-> Echelon LNS Utilities). Select the network Leave the rest sections as default. Click “Generate” to generate the report. Go to the “Report Filename” Path to open the “.csv” file. You can search the problem Neuron ID under NeuronId column. With the information that report provide, you should be able to locate the node in the network. You can go back to your drawing delete it or keep it if that’s a necessary node.

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter Will not work with a Dell E6400 laptop Environment PCMCIA slot Cause Dell E6400 Chipset Resolution Go to the Dell website and upgrade your laptops chipset to the latest version from the dell drivers and downloads section. The file download is a self extracting file, follow the instruction provided and when you re-boot your computer your LonTalk PCC-1 PCMCIA Network Adapter should be fully functional. For further information see TPA-SACH-10-0008.00 - LON PCC-10 PCMCIA Card with Dell E6400 Laptop

Issue Not possible to filter alarms on priority using comma. If alarms with priority 1 and 4 to 10 should be shown in the alarm window, it has been possible in earlier versions (before Vista 5.1.4) to write "1,4-10" in the filter for alarm priorities. Today it is not possible to use the comma. An error message saying "Invalid input, check values and syntax" will appear when closing the filter. Environment Vista Workstation 5.1.4 Cause It is only the user interface which will not allow a comma. Resolution Use the raw dialog for filtering the alarm window instead. Hold down Ctrl+Shift and click on the filter button Change APPRIO. Fixed in version 5.1.5.

Issue Problem with downloading bin file with more than one door defined causes second set of doors to deny reads. Bin files connected to this issue are 3.24, 3.25, 3.26 Environment TAC I/Net Seven using Access Control. SCU 1284 configured with two doors. (Dip Switch 6 ON gives double address)  Cause Bin file failure to download with double address setting. Resolution On an SCU, an SCU is configured for 4 doors. 2 of those doors are working. 2 of the doors on the SCU are not working. Only thing that has changed is the SCU was downloaded with a new bin file. Nothing in door configuration was changed, no dip switches were altered. Solution: Find out which doors were not working, (probably the second two doors like 0104) Go to Edit/controller/MCU Configuration and Set those doors to Internal, and then download the SCU with the bin file again. Go to Edit/controller/MCU Configuration and Set the doors back to DPU. 

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 taclogdata_log.ldf file is too big Environment SQL 2005   Cause Fail to perform frequent SQL DB maintenance   Resolution To Shrink the LOG file (.ldf) follow the procedure. Connect to taclogdata.mdf using SQL server management studio. Run the following command: dbcc shrinkfile (taclogdata_log,100,truncateonly)   This will reduce the size (taclogdata_log.ldf) to 100 mb. Note : You can get the logical file name for the log by running the following select statement: (select * from sysfiles) The following are the query results: 1          1          6400    -1         6400    2          0          taclogdata         c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata.mdf   2          0          2624    268435456      1280    66        0          taclogdata_log  c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata_log.LDF   If the database has the truncate log checkpoint turned off, then the transaction log file will be shrink to the target size only when the transaction log is backed up. OR If the truncate log on checkpoint is turned on then go to Enterprise Manager - all tasks - and click "truncate log". This will shrink the file down to the target size and will release all the unused space to the Operating System.

Issue Installation question on XP module Environment Cause Installation question on XP module Resolution Yes. Modules can be connected to the bottom of the controller with the built-in expansion port connector or they may be connected remotely via a 3-foot (1 m) or 10-foot (3m) ribbon cable. A total of 10 feet of cable may be used for all Expansion Modules. Mounting and securing of the xP modules is provided through four mounting holes in the base plate.

Issue Error when starting Continuum 1.9: Cannot find acc video recording service. Environment Windows XP SP3 Continuum Cyberstation Cause As with many software installations, installing with anti-virus running will block some registrations and registry entries. Resolution Install Continuum with admin privileges Turn off anti-virus software Stop any firewalls during Continuum installation

Issue The maximum stat adjustment range that can be set using the Xenta 102-AX Plug-in is 10°C (17.98°F) or roughly 5°C (9°F) above and below the base setpoint. This limitation is applied to the 102-AX Plug-In, Operating Parameters, Stat Adjustment Range. Environment Xenta 102-AX Plug-in Cause The LNS Xenta 102-AX Plug-in limits the values that can be written to the stat adjustment range parameter. Resolution Write to the stat adjustment range variable through Vista Workstation.  There is no limitation applied to this value when the LNS Plug-in is not being used.  The point can be found in the Xenta 102-AX controller at VAV_Controller.nviSetpoint.SCPTmaxRnge. If the 102-AX Plug-In is accessed after the change, the plug-in will limit the value again resulting in 10°C (18°F) being written back into the 102-AX.

Issue In some situations, the STR-350 is needed to send an absolute setpoint to another device on the network, and the nviEffectiveStpt is needed to be able to raise or lower that setpoint over the network. When doing this, the nvoSetpoint will not mirror the set value in the nviEffectiveStpt.  Environment STR-350 v1.2 & v1.3 Cause If the nciSendHeartbeat is greater than 0, the stat will only use the adjusted value at the stat and will ignore a network value from the nvi.  Resolution Set the nciSendHeartbeat to 0 and any change on the nviEffectiveStpt will be reflected on the nvoSetpoint and as the current setpoint on the stat.

Issue BACnet values drop out occasionally BACnet devices update slowly, or miss updates Xenta Server must be power cycled to restore communication Environment Xenta 913 BACnet Cause BACnet physical layer best known practices were not followed. Resolution The following must be verified on your installation. The physical BACnet layer must be wired as specified to have the wire grounded at each BACnet card and at the 913. The physical layer must be terminated with end of line terminators of the type specified in the documentation. It is recommended a BACnet segment should not exceed more than 15 per segment. It is recommended BACnet cards must be sequentially addressed leaving the 913 as Master node address 1. The 913 Xbuilder project and BACnet cards must reflect a "max master" setting of the last master address on the BACnet segment. A default baud rate of 38.4k may be attempted but it is safe to slow the network to 19.2k if you experience communication issues.

Issue When update Vista database through System Plug-in got error message saying “Update Vista database failed”. Open Workstation, in the alarm window, there is error message saying “unable to request license”. Environment CIRCON Network Integrator or other LNS network builder, customer license file Vista 5 Cause Vista cannot recognize the LNS server license. This happens when you use some LNS network builder besides LonMaker or NL-220, and you are using a purchased license file instead of a demo license file or an engineering dongle. Resolution If you get the “Update Vista database failed” error message in system plug in. Make sure you have done the group binding or redo the group binding. If the issue still exists, check the system plug-in output window and see if there is any error message before the “update vista database failed” message. If not, open TAC Vista Workstation and check the alarm window. If you see the error message says “unable to request license”, this means TAC Vista server cannot file the LNS server license. The TAC Vista demo license or an engineering dongle has a full version of all licenses which includes the LNS server license. You will see a line below in your demo license file: FEATURE Vista.Server.LNS taclic 5.1 31-oct-2010 uncounted HOSTID=DEMO However, the purchased customer license file does not have “Vista.Server.LNS” license included. The solution to this issue is either rebuilding the LNS network in LonMaker or NL-220, or purchasing an engineering dongle or using the demo license file.

Issue In Vista / Menta 5.1.4  it is possible to have illegal characters such as spaces or - in the program specification name of a Menta file. This will cause this $.mta file to fail when transferring to the Vista DB inside of the system plug-in. It will also cause a Xenta controller to never come online if installed in a Vista Classic DB.  Environment TAC Menta 5.1.4 Cause When leaving the program specification blank in a 5.1.4 Menta file, it will automatically be filled in with the name of the entire Menta file when it is saved for the first time. So if you do not fill in the program specification and name/save the Menta file "AHU-1," the program specification will be filled in with AHU-1. This "-" in the AHU-1 is not a legal character and will not be accepted within the Vista DB or the system plug-in.  Resolution When creating a Menta file for the first time, always remember to set the program specification to a name and without any illegal characters (maximum 12 characters). Once you are in the program specification name editor, it will let you know if you have entered proper syntax. 

Issue Remote Serial Port  Driver, RSPD, is not working. Environment Windows 7 Windows 2008 Cause Security in OS . Resolution Install and start the program as administrator. Right click on the program and select run as administrator.

Issue OPC Server setup for TAC Vista will not save the information when you change the user type from Windows account to TAC Vista account. Product Line TAC Vista Environment TAC Vista OPC Server 1.6.1 Cause This is a known issue that requires a specific reinstall procedure. Resolution Install version 1.6.0 of OPC Server Change to TAC Vista login in the TAC OPC setup Uninstall it Install 1.6.1 again. For more OPC Server issues please Vista OPC Server Installation and Known Issues.