Building Automation Knowledge Base

Issue After moving the License server to another computer the license server address in the License Administrator is changed to the IP address of the new computer, but EBO Workstation gets a license error when trying to login to it. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The License Administrator can be used to select which license server EBO uses. This is done by going to the License Server Address tab and entering the license server address in the License Server Address field. Note that the license server address must be preceded by an @ in order for it to work, e.g. @servab48. The License Server Address in The License Administrator is not always used when Workstation or the Enterprise server asks for a license, Resolution The request for a license is handled in the following order:   If there are licenses located locally on the machine running WorkStation/Enterprise server (activated from ASR files), those are used first. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is used. This registry key contains all license server addresses that have been successfully used to obtain a valid license previously. If this key is not empty, each server contained in the registry key value is asked for a valid license until one is obtained. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, and the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is empty, the license server set in License Administrator is used. The license server address is stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\StruxureWare\License Administrator\TACLIC_LICENSE_FI

Issue Implementing a pre-entry access card anti-passback using Plain English program Product Line Andover Continuum Environment Continuum Net Controller II Continuum ACX 2 Controller Continuum ACX 4 Controller Cause The anti-passback implementation in Continuum engages when the credential holder enters the area as detected by the door switch/contact. (if no door switch is configured, then the credential holder is considered to have entered the area immediately after access has been granted by the system) When doors are located in close proximity to each other, as is the case with a bank of turnstiles, for example, the built-in anti-passback scheme is easily defeated as a cardholder is able to unlock multiple nearby turnstiles before triggering the door contact and engaging the built-in anti-passback functionality. Resolution The simplest solution to the issue described above is to configure the door objects WITHOUT a door switch/contact, this, however, is not always possible depending on on-site requirements. A second solution is to take control of the doors using Plain English. The solution presented here is for a bank of three turnstiles, (A, B, and C), it uses a PE program per turnstile. The solution can easily be adapted for a bank of less or more turnstiles. NOTE: The PE programming here is provided as a sample, for guideline purposes only, the programs are not intended as a complete solution, significant modifications may be required for site deployment. Program code for door/turnstile A 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' |_____X______X______X______ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the 'initialization line which specifies which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileB, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_B, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_B, theLastCrdTime_C Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_A theTurnstileB = Turnstile_B theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_A_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileA_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM '------------------------------------------------------------------------------------------ Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile B 'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of the following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileC 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_C, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_C '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_B theTurnstileA = Turnstile_A theTurnstileC = Turnstile_C 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_B_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_B_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_C = Trnstle_C_CrdNum thisAlarmPoint = TurnstileB_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_B_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_C = Trnstle_C_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_C Value) and (Date - theLastCrdTime_C Value) < theTurnstileC DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING Program code for door/turnstile C   'This program implements a pre-entry antipassback strategy to prevent a credentail holder 'from granting access at multiple access points (i.e turnstiles) that are physically located in close proximity to each other. '| | ' __/-\_______/-\_______/-\___ ' | | ' | Main Lobby | ' | Turnstiles | ' | | ' | ______X______X______X____ | ' ^ ^ ^ ' A B C 'OPERATION 'Upon detecting a Valid Attempt at say turnstile A, the program will deny access to the card used at turnstiles B and C 'until one of following two conditions takes place: '1-The person attempting access goes thru turnstile A as detected by the door contact. (this activates the regular ' built-in antipassback functionality if engaged) '2-The door strike time at turnstile A expires, and the system re-locks turnstile A ' 'Each turnstile requires its own program, the programs will be identical except for the initialization line which specifies 'which objects the program uses 'Program written for 3 turnstiles, can be easily modified for 2 or for more than 3 ' '11/30/2020 v1.0 SE PSS 101010111110 **THIS PROGRAM PROVIDED FOR SAMPLE AND GUIDELINES PURPOSES ONLY** 'Program is LOOPING/AUTOSTART ' 'OBJECTS USED 'DOORs '*** All the doors are configured with Door Output Channel set to ZERO Object thisTurnstile, theTurnstileA, theTurnstileB 'OUTPUT '*** Output wired to door striker to lock/unlock the door Object thisDrOutput 'NUMERICs Object thisLastCard, theLastCard_A, theLastCard_B, thisAlarmPoint 'DATETIMEs Object thisLastCrdTime, theLastCrdTime_A, theLastCrdTime_B '------------------------------------------------------------------------------------------ Line SETUP 'ENTER THE PATH TO THE 3 DOORS HERE thisTurnstile = Turnstile_C theTurnstileA = Turnstile_A theTurnstileB = Turnstile_B 'ENTER THE PATH TO THE INFINITYOUTPUT HERE thisDrOutput = Trnstl_C_Striker 'ENTER THE PATH TO THE INFINITYNUMERICs HERE thisLastCard = Trnstle_C_CrdNum theLastCard_A = Trnstle_A_CrdNum theLastCard_B = Trnstle_B_CrdNum thisAlarmPoint = TurnstileC_ALM 'ENTER THE PATH TO THE INFINITYDATETIMEs HERE thisLastCrdTime = Trnstle_C_EvntTm theLastCrdTime_A = Trnstle_A_EvntTm theLastCrdTime_B = Trnstle_B_EvntTm '------------------------------------------------------------------------------------------ Goto MONITORING Line MONITORING thisDrOutput Value = 0 'LOCK THE DOOR If thisTurnstile ValidAttempt then 'ACCESS HAS BEEN GRANTED AT THIS DOOR... thisLastCard = thisTurnstile EntryLastCard 'RECORD THE CARD # USED... thisLastCrdTime = (Date + 0) 'AND THE TIME OF THE TRANSACTION Goto VALID_ATTEMPT Endif Line VALID_ATTEMPT 'IF SAME CARD USED AT ANY OF THE OTHER 2 DOORS WHILE THE CURRENT TRANSATION IS IN PROGRESS DENY ACCESS If (thisLastCard Value = theLastCard_A Value) and (Date - theLastCrdTime_A Value) < theTurnstileA DoorStrikeTime then Goto PASSBACK If (thisLastCard Value = theLastCard_B Value) and (Date - theLastCrdTime_B Value) < theTurnstileB DoorStrikeTime then Goto PASSBACK thisDrOutput = thisTurnstile DoorStrikeTime 'UNLOCK THE DOOR If thisTurnstile DoorSwitch = Opened then Goto PROCESSENTRY 'PERSON HAS OPENED THE DOOR If TS > thisTurnstile DoorStrikeTime then Goto MONITORING 'VALID ACCESS NO ENTRY Line PROCESSENTRY 'VALID ACCESS WITH ENTRY If TS > 0 then thisDrOutput = Off 'RELOCK THE DOOR Goto MONITORING 'GO WAIT FOR NEXT ACCESS ATTEMPT Line PASSBACK 'ANTI PASSBACK VIOLATION thisDrOutput Value = 0 'LOCK THE DOOR TurnstileA_ALM = TurnstileA_ALM + 1 'SEND ALARM Goto MONITORING Line E If TS > 10 then Goto MONITORING        

Issue An SP-C-WEB needs to be upgraded.  Can this be done without removing the controller? Product Line Security Expert Environment Security Expert Controller (SP-C) Security Expert WEB Controller (SP-C-WEB) Cause Due to site expansion, it is necessary to upgrade an SP-C-WEB to an SP-C.  Resolution It is not possible to upgrade an SP-C-WEB to an SP-C in the field. The SP-C-WEB will need to be replaced and re-programmed via Security Expert Server.

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 During certain situations, it may be required to remove and re-install PCT to address software conflicts with other software applications. While trying to remove/install PCT you may receive an error preventing you from completing the installation. The setup had detected that no version of SBO Project Configuration Tool is installed.  The specific command-line options require that the application be installed to continue. The setup will now terminate. Error: -1603 Fatal error during installation. Consult Windows Installer help(Msi.chm)or MSDN for more information. Error 1722. There is a problem with this Windows Installer... Product Line EcoStruxure Building Operation Environment Client versions (64 Bit Only): Editions: Pro, Home, Enterprise Windows 10 Windows 8.1 Windows 8 Windows 7       Server versions (64 Bit Only): Editions: Standard, Enterprise Server 2008 R2 Server 2012 Server 2012 R2  PCT versions (64 Bit OS Only): SBO Project Configuration Tool v 1.0.0.487 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.0.0.510 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.0.47 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.1.49 - SmartStruxure Solution - Software SBO Project Configuration Tool v 1.1.2.57 - SmartStruxure Solution - Software Cause In order to get past a possible installation loop, you will need to locate and delete the following Windows registry key: [HKEY_CLASSES_ROOT\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B] Resolution Note: Always make a backup of your registry before making any modifications.   Run regedit.exe Locate/Search: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\B2A4F0AEC8BB0E2438706F07E2E2560B Delete Registry Key entry: B2A4F0AEC8BB0E2438706F07E2E2560B  

Issue Not sure how to configure sending emails to multiple recipients when an Input or Area goes into alarm. Product Line Security Expert Environment Security Expert SP-C-WEB Cause Correct formatting must be used when sending alarms to multiple email recipients. Resolution Separate each address with a semi-colon and surround the entire string with double quotes, see examples below.   Security Expert Navigate to Events | Actions, create a new Send E-mail Action and add your multiple addresses to the E-mail Address field. "address1@email.com;address2@email.com" Email Addresses The email address field is limited to a maximum of 128 characters. All email addresses must be within this 128 character limit to be sent correctly. SP-C-WEB To add multiple recipient addresses, navigate to Programming | Areas or Programming | Inputs. For an Area, select the Configuration tab and add a recipient email address to the command window and use the format:email:"address1@email.com;address2@email.com" For an Input, navigate to the Commands window for your selected input and use the format: email:"address1@email.com;address2@email.com"

Issue Import Vista Alarms and Events into an Excel file Product Line TAC Vista Environment Vista 5 SQL 2005 Cause Unable to import Vista Alarms and Events in to excel file from Vista Resolution Select Data > Import External Data > Import Data as shown in below screen capture.   Select New SQL server connection as shown in below screen capture.   Enter Vista SQL Server instance name as shown in below screen capture.   Select taclogdata from dropdown menu as shown in the below screen capture.   Select Event table as shown in the below screen capture.   Rename .odc as .dsn as shown in below screen captures.   Click finish button.   Select Edit Query as shown in below screen capture.   Select SQL as shown in below screen capture.   Paste the Query as shown in below screen capture. Click OK button to apply the query.   Click OK button as shown in below screen.   Click OK button as shown in below screen.   Events are imported in to Excel   Query for Events based on dates: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN '10/12/2009' AND '10/12/2009 23:59:59.997') Query for One Day Events: SELECT EventId, EventType, EventDatetime, OperatorUnit, UserName, ObjectType, [FreeText], ObjectPathNameId, ShortcutPathNameId, ObjectKey FROM Event WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE()) Query for Alarm based on dates: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (Event.EventDatetime BETWEEN '08/24/2010' AND '08/25/2010 23:59:59.997') Query for One Day Alarm: SELECT AlarmEvent.Priority, AlarmEvent.EventId, Event.EventDatetime, Event.OperatorUnit, Event.UserName, Event.ObjectType, Event.[FreeText] FROM AlarmEvent INNER JOIN Event ON AlarmEvent.EventId = Event.EventId WHERE (EventDatetime BETWEEN DATEADD(day, - 1, GETDATE()) AND GETDATE())

Issue   An error occurred while setting the system language property. Please validate that your language resource files are valid. Invalid format. (Subsystem: LNS, #40) Product Line TAC Vista Environment LonMaker Cause Resource File Languages have become corrupt. Resolution Restore the Resource File Languages:  Shut down LonMaker. Go to http://www.lonmark.org/technical_resources/resource_files/ At the time of this article, the latest version is LonMarkResourceFiles1304.exe.  Download this file.  If a later version exists, download the latest file. Run the executable. Restart LonMaker.

Issue Complexity of SQL and which version is compatible  Product Line TAC INET Environment TAC I/NET Seven and congruent Windows Operating System. File Master, Filemaster, EqualizedClient, Compatibility, SQL, SQL 2008, Full SQL, SQL 2005, SQL2008, SQL2005, SQL Express, Express SQL, MSDE, 2.31, 2.40, 2.40a, 2.41, Server, XP, Windows 7, 7, 32-bit, 64-bit, Microsoft SQL, Service Pack, SP Cause Filemaster and either Equalized Client or Remote Client is desired. Problem is to know which versions of SQL are compatible. Resolution Below is a handy chart designed to help in determining what versions of SQL are compatible in I/NET Seven. Pertains to MSDE, SQL Express, SQL 2000, 2005, 2008. File Equalization Chart       Note: 1. 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, 2008, or 2008 2. 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. 3. The use of any edition of Microsoft SQL Server 2005, 2008, or 2008 R2 will require that the PC have at least 2 GB of RAM. 4. No Express edition of Microsoft SQL Server can be used on a TAC I/NET Seven filemaster. Golden Rule: You cannot move the db or downgrade from I/NET db SQL 2008 to I/NET db SQL 2005, see Downgrade SQL 2008 to SQL 2005, What version is used? 

Issue In the event of a lost or broken connection between the Vista Server and SQL server, the Vista Server will begin to queue up its events and log values in the $queues\insertevents and $queues\insertlogvalues directories. Once your connection has been re-established those queued files will then be written to the Vista DB, however this process can take an extremely long time,  and possibly cause the Vista server to hang at start up and even crash.  Product Line TAC Vista Environment Vista 4.3.0 or higher with SQL  Cause Broken SQL connection between Vista and local or remote SQL server. Resolution If you are not in the need to this queued event and log data you can manually delete all of these queued files. Opening this directory with Windows, highlighting all files and deleting them usually does not work, because of the enormous amount of files that may be stored in their respective directories. The best way to delete these files is to use DOS. Remember stopping both TAC Vista Server and the DSS Writer service before deleting the files.   Method 1: The proper steps to delete these files with DOS using the "rmdir" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues Type "rmdir /S /Q insertevents" - all files and folders including the "insertevents" folder will be deleted Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5.   Method 2: The proper steps to delete these files with DOS using the "del" command are: Click Start > Run Type "cmd" and press enter Use the DOS command "cd.." followed by enter to navigate up one folder in the hierarchy.  Repeat this command until the prompt is at the root directory and shows C:\> Use the DOS command "cd " to navigate to the Vista database folder location and the $queues folders.  For example: C:\>cd Projects C:\Projects>cd School C:\Projects\School>cd VistaDB C:\Projects\School\VistaDB>cd $queues C:\Projects\School\VistaDB\$queues>cd insertevents C:\Projects\School\VistaDB\$queues\insertevents> Type "del *.*" and then "Y" to confirm that all files on that directory will be deleted. C:\Projects\School\VistaDB\$queues\insertevents>del *.* C:\Projects\School\VistaDB\$queues\insertevents\*.*, Are you sure (Y/N)? y Use the cd.. and cd commands to navigate up one folder and back down into the insertlogvalues folder C:\Projects\School\VistaDB\$queues\insertlogvalues> Repeat step 5. Now both of these directories should be emptied and if your SQL connection issue has been rectified your events and logs will write as normal to SQL.     Alternatively, this utility will split the queued files into folders of 4,000 files each.  Windows can handle each of these folders and make the task of deleting the queued files more manageable.  Click the screen capture below to download the utility.  

Issue All values in the Xenta 102-AX Plug-in are blank. Product Line TAC Vista Environment Xenta 102-AX Plug-In LonMaker Cause If the Resource File Languages have become corrupted on your PC, then the plug-in will not know how to display the required data. Go to LonMaker > Network Properties > Resource File Languages.   If the only Language listed is "ENU," then the language files are corrupted. ENU is the default language and will display all data in the LNS environment -- plug-ins, browser, get values -- in an enumerated format that is not usable. Everything will continue to work, but monitoring data in the LNS environment and configuring ASCs via plug-ins will be impossible. Resolution Restore the Resource File Languages: Shut down LonMaker Go to http://www.lonmark.org/technical_resources/resource_files/ Download LonMarkResourceFiles1300.exe Run the executable Restart LonMaker Check Network Properties again. US English should be listed and the plug-in should populate with data. Note: There may be Beta versions 13.04 and 13.10 on this website. Do not use these LonMark resource files. The newer versions cause errors in the 102-AX plug-in. For more information see Opening the Xenta 102-AX plug-in results in "request for LonMark Object status" error .

Issue Values sent from a 102-AX via SNVT bindings are not making it to the receiving controller. Viewing the outbound SNVT on the 102-AX shows a value, but the inbound SNVT on another controller is invalid or a default value. Product Line TAC Vista, EcoStruxure Building Operation Environment Xenta 102-AX LNS SNVT bindings LonMaker NL220 Cause The Node Configuration parameters are set with a send heartbeat of 0 seconds, which tells the controller to never send an update on the output SNVT.  All 102-AXs come with a default send heartbeat of 0 seconds, so for them to function in an LNS network where they must send data to another controller, the send heartbeat must be set to something greater than 0 seconds. Resolution Open the Xenta 102-AX device Plug-in Go to the Node Configuration Tab Set the Node Minimum Send Time (SCPTminSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoSpaceTemp nvoStatOccBtn nvoSetPtOffset nvoLocalOccLatch nvoEmergCmd nvoUnitStatus nvoBoxFlow nvoTerminalLoad nvoEffectSetPt nvoFlowControlPt nvoOccpncyStatus Set the Node Send Heartbeat (SCPTmaxSendTime) to a non-zero value. The range is 0-6553.4 seconds. nvoAirFlow nvoAuxTemp1 nvoAuxTemp2 nvoUnvInput1 nvoUnvInput2 nvoUnvInput3 nvoUnvInput4 nvoCO2sensor nvoFanLoad nvoHeat1Load nvoHeat2Load nvoMotorPositn nvoActualValue nvoOAirFlowRatio nvoAirPressure It is typical to set the Node Minimum Send Time and the Node Send Heartbeat to 60 seconds and the Node Receive Heartbeat to 0 seconds.  

Issue How to find a dongle ID (PSU ID) if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista IV TAC Dongle Utility Cause The dongle ID (PSU ID) can be found printed on the side of a Vista IV licensing dongle. However, on older dongles, this number can rub off. It is still possible to extract the dongle ID using the TAC Dongle Utility. Resolution Download the TAC Dongle Utility Install TAC Dongle Utility and run the program. Start > Programs > T A C > TAC Tools > TAC DongleUtil Plug in a valid Vista IV end user dongle. Hit Refresh on the Dongle Utility PSU ID is displayed. This is the ID required to add new licensing to an existing dongle. ReadFind a Vista 5 dongle ID for how to find a Vista 5 dongle ID.

Issue Plug-in 'TACZBuilderPlugIn.Application' launch failure. Unspecified error Product Line TAC Vista Environment LonMaker 3.X TAC ZBuilder Plug-in Cause An unspecified error in the launching of the TAC ZBuilder Plug-in is either caused by a faulty installation or registration of the plug-in. Resolution Check under Start > Settings > Control Panel > Add or Remove Programs. Look for TAC ToolPack 5.X.X. Make sure the version number 5.X.X matches the current Vista installation. If it does not, uninstall the current version of the ToolPack and install the correct version. If it is the correct version, proceed. Check the plug-in registration. In LonMaker go to LonMaker > Network Properties > Plug-in Registration. Look for TAC Vista System Plug-In (Version 5.X.X) Make sure the version number 5.X.X matches the current Vista installation. If it does not, unregister the current version of the Plug-in and register the correct version. If everything appears to be installed and registered correctly, but the error persists, uninstall and reinstall the correct ToolPack. Reboot the PC, reregister the plug-in, and try to launch it again.

Issue   The requested information is not available from the device. (Subsystem: NS, #28) Product Line TAC Vista Environment LonMaker 3.2 (Turbo) Cause The requested information is not available from an application node. For example, transceiver status, SI/SD data, and the network variable names are not always stored in the node. This error is a known issue with LonMaker 3.2 (Turbo). Resolution Navigate to http://www.echelon.com/support A username and password are required to access the download section, but it is free to register. Download LonMaker Turbo Service Pack 2 Install LonMaker Turbo Service Pack 2.

Issue The Echelon LonTalk PCC-10 PCMCIA Network Adapter will not work with a Dell E6410 laptop. Product Line Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Echelon LonTalk PCC-10 PCMCIA Network Adapter Dell E6410 laptop Cause Dell E6400 Chipset Resolution To correct this, an entry needs to be added into the Windows registry. Option 1 Download a Windows registry import file from The Exchange. Navigate through Products > Satchwell > Sigma or MicroNet > Downloads > Hot Fix (Or you can download the file here RegedittoaddPCMCIACard.zip). Once downloaded, double click the file and the entry will automatically be added. Reboot the computer before the entry is read. Option 2 Manually add the entry into your registry. Use caution when making changes to the Windows registry. Mistakes can be fatal to the operating system. To manually add the entry, carry out the following: Go to Start > Run and use “regedit” to open the Windows registry. Navigate through to HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet Services Pcmcia Parameters Add a new DWORD entry called “IrqRouteToPciController” Modify the new entry and give it a hexadecimal value of 8 Reboot the computer before the entry is read. If option 1 or 2 do not resolve the issue, it may be necessary to perform the following:  Option 3 Open the registry editor. Go to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2} or HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{68EE3401-D4CA-11D3-8DBB-0060082936F2}\0000 and look for the key name "PcmciaExclusiveIrq". Delete the key name "PcmciaExclusiveIrq" (If it exists). You may need to reboot the PC. Further information may be available in the Echelon Knowledge Base on the Echelon website. This information can be found in Solution: KB763. For more information, please refer to TPA-SACH-10-0009.00 - LON PCC-10 PCMCIA Card with Dell E6410 Laptop

Issue Step-by-step instructions for calibrating airflow on a Xenta 102-AX (or I/NET MR-VAV-AX) using the M/STAT. Test and air balance procedure for balancing airflow Product Line EcoStruxure Building Operation, TAC INET, TAC Vista Environment Xenta 102-AX MR-VAV-AX M/STAT Cause The preferred method for calibrating airflow in Xenta 102-AX or MR-VAV-AX is through the plug-in.  However, this is not always an option, especially when the responsibility for calibrating is given to a third party test and balance company.  Pocket references exist for navigating through the M/STAT menu, but there aren't clear step-by-step instructions to tell exactly how to perform the calibration. Resolution Click here to download this document in Microsoft Word format Connect M/STAT Plug the M/STAT into the jack on the thermostat. The initial display shows the set temperature.   Enter Password Press the Service button. This prompts you to enter the service mode password. Default password is 183. Use the +/- keys to set each digit and the enter key to submit. If the password is incorrect, the display will blink. Airflow Parameters If the password is correct, the first menu option – Unit Parameters (UP) – is displayed. Hit the select button down twice until Airflow Parameters (AP) is displayed. Press enter. Cooling Low Flow Setpoint The first option is Cooling Low Flow Setpoint (CLF). Press enter to view the setpoint (divided by 1000). Record this value. Press the service key to escape out of the menu. Cooling High Flow Setpoint Navigate to Cooling High Flow Setpoint (CHF). Press enter to view the value (divided by 1000). Record this value. Press the service key to escape out of the menu. Reset Factory Calibration Navigate to Factory Calibration Settings (FCS) and press enter. Use the change keys to display “YES” and press the enter key. This will set the box back to default settings. This is a good idea to do prior to every calibration. Press the service key to escape out of the menu. Calibrate Low Airflow Navigate to Calibrate Low Airflow (CPL). Press enter and the current airflow is displayed. Wait for the airflow to reach the CLF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual Low Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. Choose One or Two-Point Now Calibrate High Airflow (CPH) is displayed. If one-point (offset only) calibration is desired, press the service key to escape out of this mode and calibration is complete. If two-point (gain and offset) calibration is desired, press enter to continue to the next step. Calibrate High Airflow The current airflow is displayed again. Wait for it to rise to meet the CHF and level out. Once the value is steady at setpoint, press the enter key only once. The display does not change. Enter Actual High Airflow Measure the actual airflow. Use the change keys to set the display value to the measured value. Press the enter key. CPH is displayed again, this time as a general menu item. Escape Service Mode Press the service key to escape out of the menu. If you are finished configuring the box, escape all the way back out of the service menu before disconnecting the M/STAT. Disconnecting in configuration mode can leave the stat displaying “00” or other incorrect numbers.

Issue Epibuilder Dynamic Text fields are not displaying in a badge layout or Errors related to EpiBuilder or EPIDesigner Product Line Andover Continuum Environment EpiBuilder Badge Layout Cyberstation Cause Install didn't make the connection properly or badging wasn't enabled during the initial Continuum installation or Windows permission restrictions  Resolution From Make Edit badge in Continuum, Open Badge layout in EpiBuilder (If you have a problem opening Badge Layout see Note #2 below) View Options> Data Fields Select Use the data fields defined in a database If nothing is there, click the Other Database button Select Use an ODBC database Select the Data Source button Select System DSN tab and then select EPISDK then OK Click the Select button add the path to SDKNoDB.mdb (C:\Program Files\Continuum\EpiBuilder\Data) Click Open, Click OK All fields should now be available or the error should no longer happen on startup If receiving: ** Error Opening EpiDesigner Configuration Database error when selecting MakeEdit Badge,    Note #1: Permissions can affect the configuration of the Data Sources. If some options aren't configurable or have been changed from the default like buffers are not set to 2047 then try the configuration with increased permissions. Start>run odbc32.exe and check that the System DSN had EPISDK, If not, add it and then follow the instructions able to set the SDKNoDB.mdb  If the site is utilizing hard drive encryption on the hard drive.  Move the sdknodb.mdb to an unencrypted network share to correct the errors after updating the episdk datasource.  Note #2:  If you cannot perform step #1 from above check the following: On a 32 bit system run the following command from either the run window:  odbcad32.exe and check that the User DSN has an EPISDK entry with the datasource set to SDKNoDB.mdb .  The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\ On a 64 bit system run the following command from either the run/search window:  C:\Windows\SysWOW64\odbc32.exe and check that the User DSN has an EPISDK  entry with the datasource set to SDKNoDB.mdb . The file should be located at the following path: C:\Program Files (x86)\Continuum\EPIBuilder\Data\

Issue Error displayed: Enhanced Alarm Delivery "There appears to be a problem with the configuration of this system. Please check to make sure that you have correctly installed MSMQ. The system will now shutdown."   Product Line Andover Continuum Environment Windows OS Cause The issue is that MSMQ is not installed on the machine or the installation is corrupted. MSMQ is a windows component that needs to be installed for enhanced alarm delivery. Resolution Install MSMQ from the Windows Control Panel > Add/Remove programs or Add/Remove Windows Components Reinstall Continuum NOTE: There have been instances where uninstalling MSMQ from Add/Remove Windows Components then allowing Continuum to install MSMQ resulted in a successful installation of the MSMQ.

Issue The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Product Line TAC Vista Environment LonWorks Network Cause A LonWorks network test and diagnostic tool are needed. Resolution NodeUtil is a Windows console application that can be used with Echelon’s family of network interfaces (including the PCLTA-20, PCLTA-21, PCC-10, i.LON® 10, i.LON 100, i.LON 600, Loytec Devices, SmartServer, SLTA-10, U10, and U20 network interfaces) to diagnose and configure LonWorks® network interfaces, routers, and devices. NodeUtil is a test and diagnostic tool - it is not a network management tool.  It will not assign destination addresses or bind network variables. Nor will it format LonMark® interoperable device information. This tool can be used in the following conditions: The xif file needs to be uploaded without LNS Management Tool All the devices on the LonWorks network needs to be searched The device mode or state needs to be changed Other network test and diagnostic need This software can be downloaded at http://www.echelon.com/support/downloads/detail.aspx?partNum=153-0373-01A The username and password are needed. This site is opened to the public for registration, so everyone can obtain it. Once you are logged in by default "Recommended Downloads" will be selected. Select "Development Tools" instead to locate the NodeUtil software.

Issue After changing a controller's IP settings, it does not come online and cannot be accessed via its web interface. The controller can be accessed via its web interface by temporarily defaulting the IP address. Still, changes to its IP settings cannot be saved and are instead met with the following "Invalid Port" errors. Invalid Port – Module UDP Port Invalid Port – Touch Screen UDP Port Product Line Security Expert Environment Security Expert Controllers (SP-C, SP-ACX, SP-AC1, SP-C-WEB) Cause The controller's HTTP Port has been set to 0. If this field is set to no value, this is converted to an invalid 0 value, the controller will no longer be accessible via the web interface and will require defaulting the IP address to connect. Resolution Change the HTTP Port to a valid value. The default HTTP Port is 80, but it should be changed to another available port for increased security.