Building Automation Knowledge Base

Issue I/NET Seven System Log On Environment I/NET Seven Site Cause Knowledge on I/NET Seven System Log On steps Resolution If you are logging on to the system for the first time since rebooting, restarting the driver, selecting System Log Off, or using the Signoff on Quit option, you must enter your host password. Note: You can configure I/NET to allow operators to logon simply by swiping their key/card at a Wiegand reader connected to the host workstation. Refer to User Enrollment and Auto-logon for more information. If the system is not already displaying the Log On prompt, select System Log On from the main menu. Type your Operator Name. This name can contain up to 30 characters. The following characters cannot be used within the Operator Name:" / \ [ ] : ; | = , + * ? <> The default operator name is "tac". If the system has just been installed and no operator names have been assigned, this default name should still be available. After operator names have been defined, you may wish to remove the default operator name to prevent unauthorized users from gaining access. Type your password at the prompt. This password can contain up to 127 characters. All keyboard characters are valid for use within this password. The system displays an asterisk for each character you type. The default system password is "dacs". If the system has just been installed and no other host passwords have been assigned, this default password should still be available. After host passwords have been assigned to all authorized users, you may wish to remove the default password to prevent unauthorized users from gaining access. Select OK to continue. Caution: The database server should not be shut down while I/NET is running. Shutting down the database server drops all existing connections to the database, and can result in corrupted data displays. (Only users with administrative privileges on the workstation can stop or start the database server.)

Issue Alarm values from LonWorks units in TAC Vista Product Line TAC Vista Environment Vista Workstation LON devices ASCs Xenta 102-AX, Xenta 104-A, Xenta 121 Cause Vista Workstation alarm objects can be used to monitor SNVT values from LON devices and alert the user when a value has gone outside of acceptable limits. For example, An alarm in TAC Vista if the nviSetpoint of a Xenta 104-A goes over 75ºF. This could also be used on programmable controllers -- any point in the database -- to avoid having to make Menta programming changes in order to alarm a point. The only issue with a Vista Server Change of state object is that the Vista Server will need to be running in order for the alarm to be received and actioned.  If multiple change of state objects are to be used consideration must be taken into the interface type as these points will be polled every second to check the state so actions can be taken on an alarm condition. This can easily overload a Lonworks interface if it is already managing lots of messages.  Resolution Create an object of the type "Change of state Dynamic SNVT" Right-click and go to properties. Click on the ALARM tab. Type in the alarm text for the Alarm. In this case, the alarm triggers if the temperature is over 75°F, so set the High limit to 75. Go to the Object tab and browse in the point that you want to monitor. In reference property select value. Click ok Go to the monitored point, right-click and select properties, change the watch setting to "watch"

Issue Need to examine an Xenta 28x or 30x but don't have the MTA file Environment Xenta Programmable controllers Xenta 281, 282, 283, 301, 302, 401, 401:B Menta Cause It is not possible to extract a Menta .MTA file from an existing controller. The function block diagram is not downloaded or stored in the Xenta unit itself. You must have a backup of the .MTA or the Vista database. It is, however, possible to extract the machine code file (.COD) and it is also possible to view live values in table format of any public value in the Menta file. Resolution Open Menta Connect to the controller via serial cable Hit F12, then connect. Select upload and enter a name for the .cod file that will be created. You'll get a list of all of the public signals (which will usually include the physical IO), will be able to see the values and control them if they're set to R/W. Keep in mind that the program will still be running and will change them again upon the next program cycle. You may also be able to detect that the program has failed if the signals are not changing.

Issue "No license for LonWorks communication" error when using a non LE dongle. Product Line TAC Vista Environment Non LE dongle (LE= Limited Edition which has no Webstation or multiserver functionality) Aladdin Privilege Administrator 2.01 Vista IV Licensing Cause One would normally expect this error message when trying to run Webstation server with a Vista LE license. If the system is not using a Vista LE dongle/license, but the error "No license for LonWorks communication" appears, then the problem may be in the Privilege Server service.   Resolution Shut down Vista Server and Workstation. Right click on My Computer and select Manage. Expand Services and Applications. Click on Services. Find the service Privilege Win32 Server. Right click on the service and select Stop. Right click on the service once more and select Start. Restart Vista Server and Workstation and verify that the error went away. Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 "No license for LonWorks communication" in Vista Workstation TACOS startup delay utility

Issue An error occurred while installing DSS: Cannot Start Service Product Line TAC Vista Environment DSS Vista Installation Cause This error can be found when installing Vista 4.3.x or higher after selecting Vista Administration of the SQL database. In the Application Event Log you will have an error stating the following: Cannot start service DSSWriterService on Computer '.'. --Stacktrace- at System.ServiceProcess.ServiceController.Start(String[[,args) at System.ServiceProcess.ServiceController.Start() at TAC.DSS.Install.ServiceInstallTask.Install() --End of stacktrace-- The reason this is happening is because when you selected to have Vista Administrate your SQL database it created local PC accounts (TACA_PCNAME and TACM_PCNAME). The TACA_PCNAME account is used to start the TAC DSS Writer Service and that account does not have access to the file to launch it. The access problems are typically caused by installing Vista on Windows Server 2003 and the "Authenticated Users" group has been removed from the User group on the PC. Resolution Click "Yes" at the install prompt and let the installation complete. Right Click on My Computer, and select "Manage". Navigate to Groups found in System Tools\Local Users and Groups. Double Click the "Users" group. Click the "Add" button. Click the "Locations" button and select your PC at the top of the list and then "OK". Type in TACA_PCNAME and click "OK". Note: This error should only occur if you have a non default security scheme on the network or PC. You should consult the IT department to make sure the TACA_PCNAME account will not be removed from the User group which will cause this problem to return.

Issue What should I set the Access Server System variable to on Continuum access controllers? Environment CX9200, CX99xx, ACX57xx or CX9702 controller with an ACX780 or ACX700 controller. Access Server, AccessServer Cause Below are the different configurations and what their different AccessServer system variable settings mean. Unlike Infinity when changing the setting in the controllers the controller does not reset. It is best if you set the AccessServer setting to the ACC Net ID of the Primary Access server workstation. This will keep the Access Control system operational should there be any distribution problems. Resolution CX9200, CX99xx,  or CX9702 controller with an ACX780 or ACX700 controller. The CX can stay at the default of it’s own ACC Net ID. In the above configuration the AccessServer variable in the CX is ignored. The AccessServer variable in the ACX controller can be one of the following: AccessServer value set to 0 in the ACX (Default setting).This means that access validation of personnel records will only be done locally in the ACX. If the person is not found in the ACX or the person is denied access locally in the ACX the person will not get in. AccessServer in the ACX controller set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the ACX first. If the person is not found in the ACX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. If the AccessServer value in the ACX controller is set to the ACC Net ID of the parent CX controller it has no effect and is ignored. CX99xxor CX9680 controller with AC1 modules  or ACX57xx. The CX can stay at the default of it’s own ACC Net ID.  AccessServer value set to the CX’s own ACC Net ID (Default). This means that access validation of personnel records will only be done locally in the CX. If the person is not found in the CX or the person is denied access locally in the CX the person will not get in. AccessServer value set to the ACC Net ID of the Primary Access Server workstation (valid values are 191-253). This means that access validation of personnel records will be done locally in the CX first. If the person is not found in the CX or if the person is denied access the controller will double check at the workstation to verify whether or not the person is supposed to have access. If the person is also denied access at the workstation then the person will not get in. AccessServer value set to 0. This is not a valid setting for a CX controller.

Issue While attempting to import files to through WorkStation or libraries from the Script Editor, the program crashes with the error message below. It can even happen when doing mass create or mass change, or when adding columns to a list view. "StruxureWare Building Operation has stopped working" Environment Building Operation WorkStation Building Operation Script Editor Cause It has been identified that a program called "F-Secure Key" interferes with other installed programs, and can ultimately leed to other programs crashing. "F-Secure Key" hooks into the Microsoft dll "UIAutomationCore.dll" which is used to idenitfy and manipulate elements in the user interface. If "F-Secure Key" is installed, it can easily be identified, as you will see a blue circle with a key when logging in through WorkStation Resolution Uninstall all "F-Secure Key" related program from "Programs and Features" in the Control Panel on the PC

Issue An error occurred while installing DSS: MSDTC The content of the dialog box or windows event entry starts with: System.EnterpriseServices.RegistrationException: Unable to open COM+ 1.0 catalog to configure components. ----> System.Runtime.InteropServices.COMException (0x8004E00F): COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator Product Line TAC Vista Environment Vista Installation DSS Cause This happens when there is a problem with Microsoft Distributed Transaction Coordinator (MDTC) Resolution Go to Control Panel Administrative Tools – Services Check if MSDTC in running as a Service. The name that you should see in the service list is 'Distributed Transaction Coordinator' Make sure that this is Started, Automatic, Network Service (for XP and Win2003) Here is how to install it if it is not already running: Open cmd prompt Navigate to C:\Windows\%windir% Type "msdtc -install" which installs Msdtc. The service now appears under the 'Services' area. After installing follow the steps in Microsoft Technical Bulletin.

Issue When should the MSTP bias resistors be enabled on a MNB-1000? Product Line TAC IA Series Environment BACnet /MSTP trunk under an MNB-1000 Cause RS-485 biasing rules apply to BACnet / MSTP Resolution An MSTP network requires at least one set of bias resistors but no more than two sets. If a UNC device exists on the network it will provide one set of resistors.  No others are needed. If one or more MNB-1000s are on the network, enable only one set of bias resistors.

Issue Having trouble communicating to an NPR or other I/NET hosts over a slow/busy ethernet. Product Line TAC INET Environment Any Version of Windows OS and Any Version of I/NET Seven Cause You can make I/NET more tolerant of communication delays over the IP network by making the following change. Resolution Open regedit. Browse to HKEY_LOCAL_MACHINE\SOFTWARE\CSI - Control Systems International\I/Net 2000\Configurations. Select your active profile. On the right side, right click and modify the DWORD value "EthernetTimeout" and click "Decimal". The default value is 500mS or half of one second. Increasing this value will determine how long I/NET waits for a response over the ethernet before it gives up. Raise it to 1000, 2000, 2500, etc. and see if it helps. For additional information please see NPR's giving you "Host Lost - Host Restore" messages.

Issue SNMP Flashing options for Netcontrollers and BCXs Product Line Andover Continuum Environment All Continuum master controllers Cause Documentation Resolution BCXs & Netcontrollers can be in 3 states: SNMP Standard is how all controllers are shipped by default. This means that the controller model and some other object info can be obtained via SNMP. SNMP Alarming Enabled means Standard SNMP as well as SNMP Alarming is enabled in order to send alarms to a network management system. This is a paid for option either initially when the controller is ordered or by contacting repair. To enable this option in the field, repair sends a file and instructions after payment. SNMP Disabled means that no SNMP information will come from the controller. Upgrading controllers with future firmware versions Depending on which SNMP option state the controller is in will determine the application flash that should be used going forward. Selecting the incorrect file can disable or re-enable SNMP options. Netcontroller v1.5300x SNMP Not Set means no SNMP options will be changed when upgrading firmware v1.5300x Standard SNMP means use with Standard SNMP (default) v1.5300x SNMP Alarming Enabled means use when SNMP Alarming is enabled (Not Set could be used also since it will not change the enabled option) v1.53 SNMP Disable means this will disable All SNMP traffic, Standard and Alarming BCX Use the default firmware upgrade after SNMP is enabled. If you use the BCX SNMP Disable flash files and then upgrade to a newer version of firmware, you will have to run the disable flash file again to disable SNMP. NOTE: The flash files used to disable SNMP are posted on The Exchange. Note2: If the flash file doesn't enable the options because it was sitting at resetting controller,  Reload the controller which will force a reset and then try the flash file again.

Issue The properties of a BACnet or Infinet Schedule shows Next transition time as 2106-02-07 07:28:14. Where does this date come from? EBO BACnet schedule shown below Product Line EcoStruxure Building Operation, Andover Continuum Environment b3 BACnet Schedule Infinet Schedule Cause The reason it displays the date of 7 Feb /2106 is that there are no events in the controller for the current week. Resolution The next transition time is evaluated and will display the next transition time when the following week has an event scheduled.

Issue Use Modulus in Menta Expression Block. Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause The Modulus operation in Menta is used to obtain the remainder of a division. If for example you want to perform 10 Modulus 7 the result would be 3. Resolution To perform this function in Menta, use an expression block with the contents of A%B. However, the built in Modulus function does not work with numbers larger than 65535. To perform the Modulus function with such large numbers, write out the Modulus calculation in the expression block instead of using the % symbol. This expression accomplishes the same thing: A-(B*INT(A/B))  

Issue WebClient login screen has the webClient background, but no login fields   Product Line Andover Continuum Environment webClient Cause This typically happens when webclient has been installed prior to IIS, so .Net framework does not get registered with IIS. Resolution The resolution is to run the regiis.exe command as follows: From a DOS Command Prompt (as an admin) For Windows 2000 Professional it is: "c:\WinNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\WinNT\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i" For Windows XP Professional, Windows Server 2003 it is: "c:\windows\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i" "c:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i"   For Webclient 1.94 and above, .Net Framework 4 is used "c:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i" Once this command is run the normal login prompt will be presented.

Issue After loading SigmaX on to a new laptop it does not run.  An error appears "The file SigInterfaceMfc.dll is not found." If accepted then another error message occurs, "The file SigShell.dll is not found." Product Line Satchwell Sigma Environment SigmaX Windows XP, 7, 10 Cause The Windows Environment Path "C:\sigma\bin" is not set when SigmaX was installed. Resolution Manually add the setting “c:\sigma\bin” to the Windows Environment Path. On Desk Top find the icon "My Computer". Using right hand mouse button select "Properties". Select the "Advanced" tab. Select the "Environment Variables" button. In the "System variables" window highlight the "Path" variable. Select the "Edit" button Scroll to the end of the "Variable value" text box and append the text string with “;C:\Sigma\bin\” Select "OK" buttons to close and save the changes (three times).   Also see similar KB article - SigmaX reports a missing DLL.

Issue "Controller doesn't know Infinet Id" error when attempting to share data from a BCX9640 to a b3 under a BACnet BCX 4000 Product Line Andover Continuum Environment BCX9640 b3 BCX4000 Cause A program that is attempting to map a point value from a BCX 9640 to b3 under a BCX 4000 receives a program error "Controller doesn't know Infinet Id." The infinity protocol does not get routed. Resolution The BCX4000 must be upgraded to a BCX4040 by requesting this from repair. Follow Share data between standard Continuum controllers and Continuum BACnet controllers to get the best performance.

Issue S-E L2SV Linkage Kit and S-E L7SV Linkage Kit compatibility with Satchwell Plug and Seat Valve Bodies. Environment Satchwell 1 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 2 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 3 series Plug and Seat 2-port and 3-port Valve Bodies. Satchwell 7 series Plug and Seat 2-port and 3-port Valve Bodies. Cause Use the correct S-E Linkage Kit with Satchwell Plug and Seat Valve bodies. Resolution 1.  Observe specification number of Satchwell Plug and Seat Valve Body Generally where a Satchwell AL series Linear Actuator is fitted to a Satchwell plug and seat Valve Body, the Actuator may be replaced by an equivalent S-E Forta or MV15B series Linear Actuator and appropriate S-E Linkage Kit. It should be noted however that neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series MZ/MZF or a Satchwell 7 series VZ/VZF plug and seat Valve Body. The internal screw threads of the Neck Adaptors included in the S-E L2SV Linkage Kit (880 – 0124 – 000) and S-E L7SV (880 – 0126 - 000) Linkage Kit are compatible with the external screw threads on Satchwell 1, 2 & 3 series Valve Body necks only. The external screw threads on Satchwell 7 series Valve Body necks however differ to those on Satchwell 1, 2 & 3 series Valve Body necks. Consequently neither the S-E L2SV Linkage Kit nor the S-E L7SV Linkage Kit will enable an S-E Forta or MV15B series Linear Actuator to be mounted on a Satchwell 7 series Valve Body. A S-E Forta series Linear Actuator may be mounted on a Satchwell 7 series Valve Body however using Linkage Kit 880 – 0135 – 000.  No equivalent Linkage Kit is currently available for use with the MV15B series Linear Actuator. The Satchwell Valve Body series may be determined from the Valve Body specification number stamped on the Valve Body Identification Collar, where the single middle digit of the specification number denotes the series. In the case of a Satchwell 7 series Valve Body for instance the single middle digit of the specification number will be the number 7 (e.g. 626 – 7 – 402)

Issue Steps in obtaining a Return Authorization (RA) number for a defective Niagara R2 UNC. Product Line TAC IA Series Environment Niagara R2 UNC Cause Failed unit requires repair or replacement. Resolution Before calling Customer Service for a Return Authorization, review the following steps to ensure the unit needs to be sent back to the factory. Symptom: Unit has a constant / steady heartbeat LED A UNC with a steady heartbeat LED indicates that the unit is not booting to the operating system. If a power cycle does not correct, there is not a way to recover without repairing with the factory fixtures. The only alternative is to provide a return authorization for repair or replacement. UPDATE: There are some issues that have been identified since this article was originally published that are field repairable.  To identify these field repairable issues, connect the serial console (see Need to correct invalid IP address or subnet mask entered into a UNC 520), power cycle the UNC and capture the console output.  Provide the console output information when you contact Product Support. Symptom:  Unit has a rapid heartbeat A rapid heartbeat typically indicates a memory issue.  During shipping the memory card has been known to have shifted in its socket. Power the unit down and remove then reseat the memory card in the UNC several times and then power up and monitor. Symptom: Unit is continuously rebooting In a new unit, this continuous rebooting could be a memory issue.  During shipping the memory card has been known to have shifted in its socket. Power the unit down and reseat the memory card in the UNC several times and then power up and monitor. Typically, if the fuse is bad you would see a watchdog or battery failure in the standard output window every 15 minutes or so. The fuse in the UNC-410 and UNC-520 is soldered into the board and is not field replaceable. The UNC-510 fuses are field replaceable.  Remove the shield from the UNC enclosure and remove the board from the shield. The main fuse (F1) is a 5 X 20 mm Fast Acting 1.5 amp 250 volt (Bussman GMA-1.5). The battery fuse is a 5 X 20 mm Slow Blow 2.0 amp 250 volt (Bussman GMD-2A). The battery fuse is the fuse on the right when the power connector is oriented to the upper right. Both fuses are labeled on the circuit board legend. The control board tests the battery’s charge every 5 minutes by placing a momentary short across the battery and monitoring its recovery. A failing battery will cause the unit to reset and reboot when self- tested. Remove the battery red wire and if the unit continues to operate, replace the battery. To test the battery, disconnect the battery and measure the voltage across its terminals with a voltmeter. It should read above 12 Vdc. The charging circuit in all UNCs usually provides a voltage of 13.5 Vdc (approximately).   Replacement battery, part number UNC-500-BAT. Notes: UNC will power itself down within 5 minutes after the power fails. The battery will retain the clock and other dynamic memory data for about 12 hours. A fully discharged battery will recharge in about 12 hours. The life of a battery is 3 to 5 years under normal conditions. Excessive discharge cycles or operation at high ambient temperature (>122F) will shorten the life of the battery. UPDATE: There are some additional issues that have been identified since this article was originally published can cause the UNC to continuously execute a Watchdog Reset and become disabled. See I/A Series R2 (Niagara) station opened in the Admin Tool displays "Disabled"), for more information on this issue. Symptom: AC power failure or Transformer problem The UNC-410 and UNC-520 have an internal transformer. The transformer voltage and wiring should be verified before returning the unit.. This is a center-tap transformer and is wired to the first three terminals on the circuit board connector.  The wires, top to bottom, should be Green, Green Yellow, and Green respectively. The voltage should read approximately 30 VAC Green to Green and approximately half the value (15 VAC) between either Green wire to the Green Yellow wire. Returning unit for repair The symptoms above are a sample of common, sometimes field repairable, failures in a UNC. If the UNC-410 or UNC-520 needs to be sent to the factory for repair, you will only need to return the circuit board (UNC-410-500 or UNC-520-500), not the entire UNC. The printed circuit assembly will be exchanged or repaired and returned. The repaired UNC will come with a 3 month warranty. To issue a Return Authorization (RA#) the factory will need to know the following information: The product part number Is the unit still under warranty? Warranty note: Warranty on a new UNC is 2 years from date of manufacture. The date code format is yyww. Example:  0815 is  2008 week 15 Serial number Job name (site name for unit) Factory order number Project ID Host ID (in the license file) The reason for return Network settings (IP, Subnet, name) Username and Password Station DB Username and Password Any special shipping instructions Have a purchase order number ready when you call. Note: Customer Support Services sends/bills for advance warranty replacement units. When the customer returns the correct unit within 30 days, a credit is then issued., Call Schneider-Electric at 888-444-1311 and select option 2 (Product Support). Product Support will enter a support case identifying the unit and that an attempt to troubleshoot was done prior to issuing the RA number. The caller should request the Product Support Case number and RA number for future reference. An RA will be issued based on the following criteria: Credit AWR (Advance Warranty Replacement). Customer is sending back an inoperable unit to the factory for credit and needs a replacement unit right away. OOWR&R (Out of Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. IWR&R (In Warranty Repair and Return). Customer sends back an inoperable unit to the factory for repair and return. NOTE: When issuing an AWR, hold the defective unit and use the packaging from the replacement to return the UNC board. This will help guarantee that the units are not damaged during shipment. When the units are received damaged and improperly packed, they are returned as received and no credit issued. Ship the device to: Schneider Electric 1354 Clifford Ave.   Dock 3 Loves Park, IL. 61111 Attn: Repair Dept. RA ###### Put the RA # on the outside of the box. Include your return address in the box.

Issue Wiring detail for using the B&B Electronics model USOPTL4 converter with PSI / XPSI Revision 4.1 Product Line TAC IA Series Environment PSI (Personal System Interface) Revision 4.1 XPSI (Xtended Personal System Interface) Revision 4.1 B&B Electronics USOPTL4 converter Cause PSI / XPSI Revision 4.1 does not work with the Patton Electronics RS-232 / RS-485 converter, model 2089-bc, that was widely used with earlier versions of PSI (rev. 3.13) and XPSI (rev. 2.0). Resolution One converter recommended for use with PSI / XPSI Revision 4.1 is the B&B Electronics model USOPTL4. To connect directly to the RJ-12 jack on an ASD device, or on a stat: Cut the RJ-12 plug off one end of an RJ-12 cable. Connect Black and Yellow wires and tape back. Connect the Green wire to the RDB(+) on the screw terminal of the USOPTL4. Connect the Red wire to the RDA (-) on the screw terminal of the USOPTL4. All four switches of the DIP switch on the USOPTL4 must be in the ON position to allow it to work properly on the ASD bus.

Issue Connecting from a TAC Vista Remote Workstation says "Ensure that TAC Vista Server is started" error, even though DCOM is set correctly Environment Vista Server Remote Workstation PCs in a network workgroup, not a domain Cause Connecting a TAC Vista Remote Workstation to a TAC Vista Server where both PCs are in workgroup rather than a domain. Resolution It is important to set the right DCOM permissions AND also remember that the Administrator password has to be the same on both PCs.