Building Automation Knowledge Base

Issue Upon starting the Lon App Tunneling program, a window displays a critical error message: "Exception occurred when attempting to run C:\windows\system32\shell32.dll, control_run.dll natconfig.cpl" Environment Lon App Tunneling Program Google Desktop Cause Google desktop interferes with the Niagara LON App Tunneling service. Resolution Uninstall the Google desktop Uninstall the Lon App Tunneling program from the Windows Control Panel > Add/Remove Programs Re-install the Lon App Tunneling program Re-boot the computer

Issue Registration of TAC Vista OPC server as service fails Environment OPC Server Cause During the installation of TAC Vista OPC server, it might fail to register as a Windows server if you do not have a valid license for the TAC Vista OPC server during the installation phase.  Resolution Uninstall the OPC Server Make sure you have a valid license Reinstall the OPC Server

Issue System requirements for SQL 2005 Express Environment SQL 2005 Express Microsoft Windows Cause Since TAC Vista version 5.0.1, the free version of SQL that is supported is SQL 2005 Express. If you are upgrading from a previous version of TAC Vista that uses the SQL 2000 MSDE version, an automatic upgrade to SQL 2005 Express will be made. Resolution SQL 2005 Express does have some requirements of service packs for the different Windows versions. Supported Operating Systems: Windows 2000 Service Pack 4 Windows Server 2003 Service Pack 1 Windows XP Service Pack 2 Computer with Intel or compatible Pentium III 600 MHz or faster processor (1 GHz or faster is recommended.) Minimum of 192 MB of RAM (512 MB or more is recommended.) 525 MB of available hard disk space (Not including the space needed for the SQL database)  See further at: http://www.microsoft.com/downloads/details.aspx?familyid=220549b5-0b07-4448-8848-dcc397514b41&displaylang=en

Issue After upgrading Vista, upon opening reports you receive the error "Report is of a previous format. Please try updating the database again." Environment Upgraded Vista Workstation Reports Cause Version property may need to be set for each report that needs to be upgraded. Resolution Upgrade the current database. You may have to change the Version property for each report that needs to be upgraded. Right-click on the report, select Properties while pressing down CTRL + SHIFT. This opens the 'advanced' properties dialog. If Version is 1 change it to 0. Run regedit to open the Registry Editor. Open 'HKEY_LOCAL_MACHINE\SOFTWARE\TAC AB\TAC Vista\4.2' (Select folder that matches your version of Vista) and locate the key 'UpgradeReports'. Set this value to 1. (0 means do not upgrade.) Start Vista Server and the reports in the database should be upgraded properly. The file UpgradeReportsLog.txt in the database folder $log contains detailed information about the upgrade process.  

Issue First Key Auto/Unlock Environment SCU 1284 Cause The first key Auto Unlock feature that was available on the SCU 1284 is not displayed on the Door Editor, in revisions 3.22 and above. This can only be seen in revisions 3.21 and below. Resolution To access the feature, the following steps need to be followed: Select the door from the list and then click on the Modify button. Select the ATS button and select the first Entry. Select the first schedule and click Modify. Select First Key Mode and click on the drop down box. Select the Unlock option and then click on the OK button. Close the editor and then read a valid card to ensure that it is working properly.

Issue The Niagara G3 Microsmart Driver Installation and Configuration Guide (F-27523) lists "Applicable Documentation" on page iv. Is that documentation available for download? Environment Niagara G3 MicroSmart Drive (Installation and Configuration Guide) Cause Manuals (F-25695, SOFT-MCN-101) are not available. Resolution Two documents in the list are obsolete and were inadvertently listed as available. They are: DCT MicroSmart Reference Manual (F-25695) MicroSmart Application Manual (SOFT-MCN-101). The remaining documents are available in iPortal > Publication Zone.

Issue On a Niagara R2 computer, the following error appears (in the Niagara Console) when trying to run Workplace Pro: *** Unjar: c:\niagara\r2.301.522\nre\modules\demo.unjar Extract: c:\niagara\r2.301.522\nre\modules\demo.unjar java.util.zip.ZipException. Environment Niagara R2 computer Cause .unjar files in the listed directory on the computer. Resolution The .unjar files are used by the Niagara installer during installation and have somehow been copied into the listed directory on the computer. Stop the Niagara Service on the computer, delete all .unjar files in the listed directory, then re-start the Niagara Service. Workplace Pro will now function.

Issue How can a connection be traced in a WorkPlace Tech drawing when it is difficult to see the wire path? Product Line TAC IA Series Environment WorkPlace Tech Cause When working with objects that have numerous connection wires (perhaps an uploaded drawing), it may be difficult to see the wire routing path. The link style is too small, which may be difficult to see the wire routing path. Resolution Click on a wire to select it (green handles appear). Two clicks may be required, since the first click selects the object that the wire is from. Right click on the wire and select Format/Style. In the Line Style pull-down menu, select "Error Box" (a heavy red wire). Click OK Trace and edit the connections as needed.

Issue Access Events are not being logged with an ACX 57xx in 1.81 Environment ACX 57xx Continuum Cause The most common reason for this is because the ACX 57xx is shipped with a 1.1x version of firmware and NC2 with 2.1, but there are updates in this firmware that are specific to Continuum V1.8x and V1.9x. Resolution Revised 3/15/2018 This article was recently referenced and updated. 1. Uprev Continuum to 1.9x or greater with ACX 1.1x or NC2 2.1x firmware 2. Down rev the firmware in the ACX to the most recent 1.0x or NC2 2.1x version of firmware with 1.8x or less. (Not recommended)

Issue Are the Erie Aux Switches for the Current Pop-Top actuators field replaceable? Environment Pop-Top actuators Cause Replace defeated part without replacing the whole unit. Resolution No they are not. The actuator would have to be replaced.

Issue In Niagara G3, how can a Boolean object's "False" condition be made to disappear? Environment Niagara G3 Boolean Object Cause BoundLabel properties must be adjusted for the desired operation. Resolution In the BoundLabel properties of the object, right-click on the "visible" field, and choose "Animate" In the Animate window, click on the drop-down for the "Converter Type", and choose "I Boolean to Simple" Click the drop-down for the "False Value", and select "false" Click OK to close the Animate window Click OK to close the BoundLabel properties window Save the graphic Now, when the object has a value of "false," it will not be visible in the graphic.

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 A record from a binary external interface file or binary application image file was received out of sequence.  Environment LNS LonMaker Vista NL220 Cause A record from a binary external interface file or binary application image file was received out of sequence.  Resolution If you encounter the error, the XFB or APB file may be corrupted

Issue The specified network variable is not dynamic. Environment LonMaker NL220 Vista LNS Cause This exception may be thrown if you attempt to assign a static network variable to a LonMarkObject with the AssignNetworkVariable method, unassign a static network variable from a LonMarkObject with the UnassignNetworkVariable method, or delete a static network variable with the Remove method. Resolution You can determine if a network variable is dynamic or not by reading its IsDynamic property.

Issue Local network interface is in the wrong state (e.g. unconfigured).  Environment LonMaker NL220 Vista LNS Cause Local network interface is in the wrong state (e.g. unconfigured). Resolution When you encounter this error, set the network management mode to lcaMgmtModePropagateConfigUpdates (0) by writing to the MgmtMode property of the System object. Then, re-commission the network interface, if necessary Run the LNS Database Recovery Wizard: If you are recovering through a PCC-10, PCLTA-10 or PCLTA-20, use the LonWorks Plug 'n Play Control Panel to select the NSI NI Application. Otherwise, error "NS #138 (Local interface is in the wrong state (unconfigured)" is reported, then "NS #67 system is not open)", then "LNS #55". Finally, the LNS Database Recovery Wizard only gives you the option to cancel the recovery. see also Echelon support article 190

Issue Nodes not showing up under subsystem view in System plug-in with NL220. However, in NL220 under subsystem tree, everything shows up fine. Environment NL220, system plug-in Cause This can occur if the default root subsystem "Locations" was deleted. The "Locations" root subsystem must be linked to the geography of the site. Therefore, deleting it may cause the lost of the link. You can change the "Locations" root subsystem’s name to something else. However, we do not suggest deleting and adding a root subsystem back. Resolution Before doing anything, please make a back up of your LNS database. Create a new root subsystem. (Right click on the Project object and select the option “New root subsystem”). When asked for the name, type "Locations". Copy all nodes under all subsystems and paste them into the "Locations" root subsystem you just created. Delete all the subsystems outside of the “Locations” root subsystem. Go to "Edit" tab, choose "define location subsystems" Select "Locations" root subsystem. Click on "location subsystem" button on the right. Click on "Yes" Refresh the tree. Go to the System Plug-in, you should be able to view all nodes under subsystem view. Now, you can go back to NL220 and change the root subsystem name to anything you want.

Issue Alarms stop being routed to the Sigma Server after an extended period of computer inactivity. All alarms will start to register on the Sigma Server once a user accesses any point in the Sigma System Manager. Environment Sigma version 4.04 (build 3.41.14) Windows XP Cause The Sigma Server computer network interface card Power Management was set to 'Allow the computer to turn off this device to save power'. Resolution The power management setting 'Allow the computer to turn off this device to save power' for the network interface card needs to be unchecked.  This can be achieved by performing the following steps: Select the properties of the Local Area Connection physically connected to the Sigma network. On the 'General' tab, there is a field that says 'Connect using:'. Click on 'Configure' to configure your network card. In the Network card properties, go to the 'Power Management' tab and uncheck 'Allow the computer to turn off this device to save power.'

Issue Some schedules stop operating correctly after Daylight Savings Time (DST) changeover.  Environment I/A Series G3, all ENS and ENC with builds 3.5.4, 3.4.53.1, 3.3.31.2, 3.2.23.1 or earlier. Cause Any station with a schedule, of any type, with an event set to occur during the "advanced" (missing) hour between 2:00 AM and 3:00 AM on the DST changeover day. The resulting miscalculation of the schedule's "Next Time" or "Next Trigger" time could cause that schedule, or even other schedules in the station, to stop working. This typically affects downstream logic in the station. In some cases it was observed that the CPU usage on an ENC went up to 100% while calculating invalid next event times. Examples A station contains a BooleanSchedule with events at 12:00 AM and then again at 2:05 AM daily. At 12 AM the schedule executes normally and attempts to calculate the next event time. On the second Sunday in March the next event time calculates to a time that does not exist due to the DST change. This causes the Java thread that executes all schedules in the station to become tied up attempting to recalculate the time. A station contains a TriggerSchedule that periodically repeats every 15 minutes, with a range passing through the DST changeover time. On the second Sunday in March the next trigger time calculates to a time that does not exist (say, 2:15 AM). Again, this causes the Java thread that executes all schedules to become tied up attempting to recalculate. Resolution The solution to this issue is to upgrade the schedule.jar file in the platform to one of the versions below, or later. Files are available from The Exchange Extranet.  Release 3.3.31.2 (Download and extract schedule-3.3.34.1) If you are using a build that is higher than the above versions then you will not be affected by this issue.

Issue Negative values presented to an IC3-SNP Integration Controller are displayed starting at 65535. Environment Sigma Integration Controllers IAC Controllers Unifact Controllers Cause The IC3-SNP Integration Controller calculates the negative value incorrectly. Resolution To overcome this issue it will be necessary to create a new Lookup table and to allocate it to the IC3-SNP Analogue Input object. 1 - In Sigma "System Manager" select "System Setup" and create a new lookup table, using the configuration shown below. 2 - Edit the Analogue Input object to include the new Lookup Table number, select to download the object. 3 - In Sigma "System Diagnostics" download the Lookup Table to the IC3-SNP. 4 - The lookup table shown above assumes that the value being presented is in whole numbers, i.e. a received value of 1 equals 1, but there are instances when the value received may have a *10 factor applied. In this case the lookup table is modified as shown below. Input         Output 0               0 32767       3276.7 32768      -3276.8 65535      -0.1

Issue How many global objects can be used in a Sigma controller or IC? Environment X96 controllers X32 controllers Integration controllers - All types Cause Configuration and engineering issue. Resolution A controller or IC can have a maximum of 50 received globals. There are no such restrictions on the number of globals a controller can transmit, but when engineering a Sigma system, additional communications and loading on the controller must be taken into account.