Building Automation Knowledge Base

Issue How to configure a Niagara G3 ENC serial port for dialup modem. Product Line TAC IA Series Environment ENC-520-2 ENC-410-1 Cause Dialup modem setup. Resolution In the Station, under Platform Services, go to the SerialPortService In the Port Config field, change the setting to Com1_232_com2_modem. Save this setting. Now, go to the Platform of the ENC, and go to Dialup Configuration The Init String should look something like this: ATE0S0=0Q0V1X4&D2&K3\N3%C2&C1&Q5W2 Change the 0 just after the "=" sign to a 2.  This will tell the modem to answer on the second ring. Make sure that the Port field says COM2 Check the Enabled box next to Listen for Calls In the Local IP Address field, type in the IP address of the ENC In the Remote IP Address field, type in an unused IP address on the same subnet as the ENC. Type in a User Name (eg. invensys) Type in a password (eg. niagara) Save your changes, then click the Start button at the bottom of the page.  This will start up the dialup daemon. Re-boot the station in Station Director.

Issue Cant open a hyperlink because internet explorer version is to low Environment Vista Cause The hyperlink is opened with compatibility mode on please read more here 1) http://stackoverflow.com/questions/6717055/how-do-i-turn-off-compatibility-view-on-the-ie-webbrowsercontrol-in-a-winforms-a 2) http://msdn.microsoft.com/en-us/library/ee330730(v=vs.85).aspx Resolution Open regedit Go to Start > Run Enter regedit and press enter Locate the folder 32-bit OS: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION 64-bit OS HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION Right click and choose add Add a DWORD Name it "TACVistaExplorer.exe" Enter the value depending what Internet explorer you use i.e for Internet Explorer 10 enter the value 10001 Restart Vista and Tacos This is how it should look

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 for assistance. Issue The added to parent column shows incorrect information. PCT 1.X  PCT 2.x Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause PCT doesn't detect detachment in WorkStation. Resolution Do not detach the child server from its parent in PCT 1.x and 2.x. Webhelp information: Adding a Virtual EcoStruxure BMS Child Server to a Parent Server.

Issue CX Controller and children i2 devices moved from one DB to another via ASCII dump file. Now when reloading the CX without the children i2 devices getting MFC error on reload of Controller when the IE table is being reloaded. Environment CyberStation CX controller I2 Infinet devices Cause Because all the controllers have been moved to a new DB the information in the  IE table in the I2 devices is invalid. Resolution Must reload the CX including its children i2 devices, this will ensure that a new IE table is sent to all devices as the devices will be reset and reloaded.

Issue BACnet alarm Change Of State 'Alarm On' field is blank in the Algorithm page. Product Line Andover Continuum Environment CyberStation bCX4040 b3s Cause BACnet alarm type must match the type of point that is associated with the alarm in the AlarmEnrollment object. For example, a Change Of State alarm requires a binary point. Resolution Make the object BACnet object type match the alarm event type (Change of State, Change of Value, Out of Range etc). In this example of a Change of State BACnet alarm, when the appropriate binary point is associated with the alarm, the 'Alarm On' field looks like this:

Issue SmartStruxure with I/A Series Micronet BACnet (MNB) controllers Environment SmartStruxure version 1.4 and earlier I/A Series Micronet BACnet (MNB) controllers Cause Need to know if it is possible to use MNB controllers with SmartStruxure.  Resolution I/A Series MNB controllers can be integrated into SmartStruxure as 3rd party BACnet devices. For more information on SmartStruxure with MNB controllers, download document MNB BACnet Support within a StruxureWare Building Operation System Solution Guide.

Issue How to create a set of manual logs to show the state changes of a digital point with time stamps. Environment CyberStation Any CX Any i2s Cause Documentation Resolution How to create a report for a digital input that shows the input change of state with a time stamp.pdf

Issue This issue has been seen Modbus TCP between I/A Series G3 ENC and Eaton PXM meters where the PXM does not respond to the ENC within the message timeout period.  The ENC discards the request and sends a new message with a different transaction ID. The Eaton PXM meter responds using the previous transaction ID causing the ENC to discard the message and generate an error. Environment I/A Series G3, ENC-410, ENC-520 Cause Transaction IDs become out of sequence. Resolution The driver now recognizes that the device is responding out of sequence and resets the session with the device. Upgrade ModbusTCP module to revision 3.5.34.1 or newer. 

Issue What value resistors should be used as termination resistors? Environment I/NET site Cause What value resistors should be used as termination resistors? Resolution On a controller LAN, use 100 to 120 ohm resistors. If a repeater is installed, or controllers are being installed on a subLAN, use 620 ohm resistors.

Issue Interfacing with a Trane BCU panel with a 7797-12 ICI Environment I/NET Seven Site with 7797-12 ICI and TRANE BCU Cause The 7797-12 ICI is a PTP (Point to Point) RS232 BACnet device which can be used to interface with Trane systems using their BCU panel. The BCU panel can be equipped with an optional Ethernet card. However the presence of this card can modify the addressing structure of the Trane device disabling communication with the ICI. Resolution The 7797-12 ICI is a PTP (Point to Point) RS232 BACnet device which can be used to interface with Trane systems using their BCU panel. The BCU panel can be equipped with an optional Ethernet card. However the presence of this card can modify the addressing structure of the Trane device disabling communication with the ICI. To resolve this problem simply remove the Ethernet card from the BCU panel. If the Ethernet card is required then a alternative interface will have to be utilized.  

Issue When browsing to graphics file directory on shared drive the following error is generated. Environment WebClient IIS Cause When specifying the virtual directory physical path in IIS DO NOT use a mapped drive. In the example below 'Y' is a mapped drive to ABEPSSZ4002\Program Files\Continuum\NewGraphicsFiles The 'Test Settings" results in an authentication error Resolution Use remote folder path only specifying the remote computer either by name or IP address follow be the name of the share. If the example below, the Program Files\Continuum|NewGraphicsFiles folder on the remote computer that will host all the graphic files has been shared with the proper permissions using the share name NewGraphicsFiles.  

Issue SQL Host not passing data to Xenta 527 Web Server Product Line TAC INET, TAC Vista Environment I/NET 527 Web Server Cause When defining the Host for the primary SQL server, you have options of 1-250. When using a Web Server to send this information to a Vista System you must define the primary SQL server with a Host number less than 63. Resolution In I/NET configuration, define the primary SQL server's Host number between 1 and 63 Restart the I/O server Connect to each Xenta 527 Web Server on site and modify change the SQL Host # to the host number assigned in step 1 Restart each 527

Issue New laptops do not support hardware for Echelon PCC-10 cards Product Line TAC Vista Environment Laptop Computers without PC Card slots or with ExpressCard Slots Cause Some new Laptops do not come with a PC Card slot or have an ExpressCard Slot that does not fit the PCC-10 card Resolution If the PC does not have a PC or express card slot then use NIC-709 USB Lon Talk adaptor. These are available from Loytec. See the procedure for changing from a PCC-10 LTA to a NIC-709 LTA. If the PC has a express card slot, see Can a LON PCC-10 PCMCIA card work in a laptop with an express card slot? for a solution.

Issue The reason for TAC dummy nodes and the logic behind the number of dummy nodes created. Product Line TAC Vista Environment Vista NL220 LonMaker TAC Vista System Plug-In Cause TAC dummy nodes are added to Xenta groups automatically in the LNS network. The dummies are made after group bindings have been created. Resolution The TAC dummy nodes are created when group bindings are made. For more information about group bindings see Verifying Xenta Group Bindings in an LNS system. Vista requires that the TAC Group and the TAC Xenta group differ in the number of devices. If you only have one Xenta group in your system, TAC Vista System Plug-In will create a dummy device and use its tag_0 (also first row of the address table) in the group binding for the TAC Group. This will allow Vista to differentiate between the TAC and Xenta groups. Notice that in both LonMaker and NL220, this dummy node that is created to represent a second Xenta group appears to be located in the same Xenta Group as the rest of the controllers. This is fine, the system plug-in is not going to create a new group to put it in, just realize why the dummy node is there. Modules do not count in the group bindings therefore the example below only has three devices in Xenta group 1.   Xenta Groups must consist of at least three Xenta devices. If you only have two Xentas in a Xenta group, TAC Vista System Plug-In will also use a dummy device, since a binding between just two devices is not considered a group binding. To create a group binding, a third device is needed. Consequently, you will need two dummy devices if you only have one Xenta in your Xenta group. Thus, if just one Xenta device exists in a single Xenta group, three dummy devices will be needed: one to separate the TAC group binding from the Xenta group binding and two more to form a Xenta group.

Issue How is the time synchronized between the Automation Server and Xenta Programmable Controllers? If the time synchronization is offline, what can be done to correct this? Product Line EcoStruxure Building Operation Environment Automation Server Building Operation Workstation Cause Time Synchronization occurs between the Automation Server and the Xenta Programmable controllers during two events: When the Xenta programmable controller is commissioned. Periodically the time is synchronized (default 10 minutes, but configurable). For the time synchronization to work properly it is critical to ensure that the time zone of the automation server is correct and the date/time of the automation server is correct. Resolution Walk through these steps to troubleshoot the synchronization of the Automation Server and Xenta controllers.   Check that all Xenta devices are at software revision 3.74 or higher Check the local time of the Xenta programmable controller by accessing the properties of the programmable controller and using the "Xenta" property tab group. The local time is listed there. Check the time zone of the automation server. By default the "Factory time zone" needs to be changed for proper operation. Check the server time of the Automation Server in the Basic property tab of the Automation Server. Check Time Synchronization Interval setting of the LonWorks Network object under the advanced tab in the Xenta General section. Default is 10 minutes. Either wait for the interval to elapse or manually commission the controller to synchronize the time and check the local time of the controller to ensure it completed properly.   Note: Keep in mind that the time displayed time in Workstation reflects the time zone of the local machine. If you are logging into an Automation Server in a different time zone, the alarms and events will be displayed in your local time, not the time of the Automation Server's time zone. For more information on Time settings and Synchronization see Time Synchronization of the ES and AS.

Issue If you do work with I/NET and Emergin and have an issue with the Alarms not getting cleared after it goes back to normal, this information might be helpful to you. Environment I/NET Seven Site Cause I/NET and Emergin and have an issue with the Alarms not getting cleared after it goes back to normal Resolution Successfully Implemented: Paging via snpp (corporate paging server) and SMTP (e-mail). Paging on alarms generated from DA points, as well as analog points that are out of range and giving the value at the time of the alarm. Escalating pages through to a list of people at certain times and canceling via "Return to normal" or "Alarm Acknowledged". This pages those on the list who have been paged the first time that the message has been cancelled. Issue Canceling alarms with specific cancellation keys. Within Emergin Alarms Messenger - each alarm has the opportunity to define a certain cancellation key. However the software scans all cancellation keys to see if it meets the criteria to cancel, NOT THE SPECIFIC ONE. EXAMPLE: Givens: 2 alerts with specific keys - AHU1 Fan Alrm & AHU2 Fan Alrm 1 general cancellation key for "Return to Normal" 1 general cancellation key for "Alarm Ack" AHU1 Fan Alrm alert is assigned the cancellation key for "Return to Normal" AHU2 Fan Alrm alert is assigned the cancellation key for "Alarm Ack" Execution Working as Planned: AHU1 Fan Alrm goes into alarm and sends pages. AHU1 Fan Alrm returns to normal and cancellation page sent to all previously paged. Execution not working with specific cancellation: AHU1 Fan Alrm goes into alarm and sends pages. AHU1 Fan Alrm is acknowledged in INET and sends a cancellation page to all previously paged. Then the point returns to normal and nothing pages. ***Because the "Alarm Ack" was setup for AHU2, it was lumped in the cancellation list with "Return to Normal." Therefore the first condition cancels - not the one specifically assigned. EMERGIN WORKS AS FOLLOWS: Emergin lumps ALL Cancellation together. Any alert is cancelled with the FIRST cancellation tag it matches - NOT the specific one assigned in the alert.

Issue When attempting to open a Niagara R2 UNC station in Workplace Pro, a pop-up error explains that the station was "Not Found (404)". Environment Niagara R2 UNC Workplace Pro Cause Generally, this error indicates that TCP port 80 is blocked on the PC accessing the UNC. Resolution Most frequently, it is the Windows Firewall blocking the port, although there are other applications that can block the port (e.g. remote access software, antivirus software, Microsoft's IIS). The best way to resolve the issue is to disable the offending application while accessing the UNC. If this is not feasible, then create an exception policy in the application that will allow port 80 communications for the IP address of the UNC. Specific procedures vary from application to application.

Issue Error: Subsystem NS, #149 lcaErrNsConflictWithCurrentNetwork This error will be generated if you open a network that is already opened using a different network interface, LNS type, or database directory. Environment LonMaker NL220 Vista LNS Cause After restoring a LonMaker database, or upgrading a LonMaker system, each LNS database has to be opened before the Vista server is started or you get this error. Same as with LonMaker, if you start the NL220 stand alone, and then start Vista, the LNS server will not be conflicted.  If switching between LonWorks Interface types (example:  RNI to PCLTA) you may receive this error when trying to open the LonMaker drawing.   Cannot run LNS Database Validation Tool with the database open (Start > Programs > Echelon LNS Utilities > LNS Database Validation Tool 3.2). Resolution Shut down the Vista Server. If Vista Server is set to run as a service (Control Panel > Administrative Tools > Services > TACOS) manually stop the service. Open each LNS database network attached and onnet.  Restart the server. If this error occurred from switching LonWorks Interface types, rebooting the PC should clear the error.

Issue The IP address can be entered into a UNC-520 using the Admin Tool but after rebooting or power cycling the device, the IP address is reset back to the factory default. Environment I/A Series (Niagara) R2 UNC-520-2(-N) with serial number greater than 36183  Cause The newer UNC hardware manages stored OS configuration data in a different manner than the older UNC-520 devices.  Because of this change, the factory default operating system has the capability to read, but not permanently change the device IP address. Resolution You must use the Admin Tool Installation Wizard to install the r2.301.527 (or newer) version of the OS and NRE (system software) before you can save any new Ethernet address information to the UNC. Follow the procedure in the UNC-520 installation manual (F-27391) section "Upgrade, License and Configure the Host" to install the OS and NRE system software.  Click here to see the referenced page of the manual.

Issue Site inquiring as to know the limit to how many workstations can be connected to a Continuum LAN system. Product Line Andover Continuum Environment Windows Server SQL Cause Site planning and architecture requires information on the limit of how many workstations can be connected to a Continuum LAN system. Resolution The Continuum LAN system itself has no real limit to how many workstations you can connect, but there are some limits to take into consideration. You can have up to 64 Workstations with ACC NET ID's between 191 - 254 which you will be able to setup to receive Continuum alarms. If the requirement is to have more than the 64 workstations allowed, you can add workstations after this limit but you will not be able to receive alarms and will need to set their ACC NET ID set to 0 If you add extra workstations you may also need to purchase additional Microsoft CAL (Client Access Licensing) licences for the Server and SQL which the database will reside on. For more information please see Microsoft Volume Licensing.  Also see Client Access License (CAL) for more detail about CAL.