Building Automation Knowledge Base

Issue How do the 7793 and 7798 handle retries?  Improving I/NET sublan communications Excessive MCU Lost messages in AMT Command Error messages in AMT Product Line TAC INET Environment I/NET sublan 7793, 7798 Cause If there are issues on the physical layer of the network, this will effect the reliability of I/NET communications. However, these risks can be lessened with some best practices. Resolution Best Practices and Troubleshooting measures to improve sublan communications: Ground the 24V line coming into MRs and ASCs Connect ground to the earth ground terminal of DPUs and SCUs. Bond the shield of the LAN cable all the way through the network, not landing it on any controller anywhere and then tie it to earth ground in one location. (see diagram)   SubLAN Communication Explained: The first packet to any sublan device goes out on the primary channel, terminals 1 and 2 of the sublan connector on the 93/98. If the device doesn't respond in time, a second packet is sent out on the alternate channel, terminals 4 and 5. If there is still no reply, a third packet goes out on the primary Finally, if there is still no reply, that device is marked as lost which generates an "MCU Lost" message. Optional Configuration for only using Terminals 1 and 2:  If you are using only Terminals 1 and 2 you could be missing 33% of it's retry capacity. If you follow wiring guides and best practices the device will answer on the first packet every time, however if you have not followed the guide all it takes is a little noise to make the retries necessary. If you are unable to use a loop configuration, or want to avoid the extra potential for noise and EMI, in stall a jumper on the sublan connector from terminal 1 to 4 and from terminal 2 to 5 The allows you to get the extra retry, without the extra cable This will also function if you have some controllers on channel A and some on Channel B The SLI doesn’t have to be at the end of line on sublan communication  

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 The local time inside a Xenta programmable unit is dependent upon server time, time zone, and daylight savings time settings.  Incorrect DST settings result in incorrect times in the controller which causes problems from incorrect start times on HVAC equipment, to incorrect alarm time stamps in alarm queues. Product Line TAC Vista Environment Xenta Programmables version prior to 3.74 Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Cause In 2007, most of the United States and Canada changed when DST is observed to the second Sunday in March to the first Sunday in November.  Because it had never changed prior to that, programmable controllers retained the old settings (first Sunday in April to last Sunday in October). Resolution The issue was resolved with the release of firmware MOT version 3.74.  Upgrading your controllers to 3.74 is a viable solution, however not always cost effective.  There are two ways to work around the issue. Note: For information on how to download firmware to Xenta programmable devices using the Download Wizard please see Download an .MOT file into a Xenta Programmable controller. Configure TAC Xenta Central DST Settings Refer to the TAC Vista Technical Manual Chapter 19.6 In the folders pane, right-click the folder where you want to place the time event object. Point to New, point to Object, and then click Time Event – Object. Type the name. Open the time event object. On the General tab, type a description. On the Time Event Settings tab, set a suitable repeat interval, for example, first Monday in each week. Click OK. In the folders pane, right-click the folder where you want to place the Central Daylight Settings – Xenta object. Point to New, point to Object, and then click Central Daylight Settings – Xenta. Type the name. Open the Central Daylight Settings – Xenta object. Two options are available. You can use Windows start and end times for the daylight saving time or specify your own start and end times. If you want to specify your own start and end times: Clear the Use Windows settings check box. In the Daylight saving starts box, set the start time for the daylight saving time. In the Daylight saving ends box, set the end time for the daylight saving time. In the Update schedule box, browse to the time event object that triggers the push to the TAC Xenta devices. Click Select. Click OK. Note: You must select Manual DST Mode and Central DST for each controller in the system for a global change to take effect. Manually set DST Settings for each controller The DST Xenta object is not available in all versions of Vista.  If that is not an option, DST settings on each controller can be manually set for the start day and stop day.  Unfortunately, time settings do not allow for designations of "first Sunday" or "last Sunday," only calendar dates.  So each controller will have to be edited each year to maintain correct time settings. In order to facilitate this, this utility:  ODXentaTimezoneChanger was created.  It must be used each year to update the settings, but it will allow you to change all time settings on all controllers in a Vista database simultaneously, greatly reducing the time it takes to correct a system. NOTE: If the Lonworks network has not been properly commissioned & downloaded the tree will not properly communicate with the Vista Server. Check your network tree for asterisks to see if any downloads are required.

Issue Importing a .CSV file into Access Expert gives the following error: Product Line Access Expert Environment .CSV File Cause During the import the Excel doc holds the file open and causes a sharing violation in Access Expert. Resolution Close the Excel .CSV file during the import. This will happen with the sample file from Access Expert or one created manually with the appropriate fields.

Issue Integration to the Veris H80xx Entercept power meter with the Xenta 5/7/9xx and Modbus RTU Environment Xenta 511, 527, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder Veris H80xx Entercept Power Meter Cause Integration instruction and programming example for integration to the Veris Entercept power meter. Resolution Please use the following .dev files as a starting point and a guide to the integration of a 100 amp or 200 amp Veris Entercept meter. This .dev file contains a set list of registers that PSS assumed would be seen as critical and important to the integration process. If any other data is needed please see this supported document to make the necessary changes to the modbus mapping or this supporting document for data scaling changes. If mapping for larger amp meters is needed, please contact product support.   100 AMP .dev file 200 AMP .dev file   To use these files in XBuilder please follow these steps: Extract the .dev file from the .zip file in the link above, and place it on the harddrive. In Xbuilder, right click on the Modbus Master device and choose Add Device Browse to the needed .dev file and click Open. Rename the newly added device to a unique name within the Modbus Master network.   Disclaimer: This device template is intended to provide a starting point for an integrator, and is in no way written to be the mandatory points list for your integration effort. Product Support has written this device template in an effort to give our customers a starting point and solid example of how to develop a device template for the above product. The integrator will be responsible for any additions or modifications to this device template.  

Issue How to find a Vista 5 dongle ID if it has rubbed off of the dongle. Product Line TAC Vista Environment Vista 5 Windows Command Window Cause The Dongle ID is required for locking TAC Vista licenses to a site dongle. Normally, the dongle ID can be found on the side of a Vista 5 licensing dongle. However, on older dongles, this number can rub off.  It is still possible to extract the dongle ID using the GetTACHLInfo.exe dongle utility software. Resolution On the Start menu, click Run. In the Run dialog box, type cmd Click OK. In the dialog box, go to the folder C:\Program Files\Schneider Electric\License Server (as default) NOTE: for TAC Vista 5.1.3 and prior, go to the folder C:\Program Files\TAC\License Server. Use command "cd.." for going to the parent directory and command "cd folderPath" for going to a child directory. Can also view items in the current directory by typing "dir". In the dialog box, type GetTACHLInfo (or GetTACHLInfo.exe) and press Return. The dongle ID is listed after "TAC_HL_ID=". Read Find a Vista IV dongle ID (PSU ID) for how to find Vista IV dongle ID.

Issue TGML Graphic Alert: TypeError: Cannot call method "getAttribute" of null (cmd#52) TGML Graphic Alert: TypeError: Cannot call method "setAttribute" of null (cmd#52) Environment Vista 5 TGML Graphic Cause A Javascript tag in the TGML file has attempted to perform an action on a null pointer.  Oftentimes this is due to a component being deleted or renamed without realizing that a script elsewhere in the graphic was pointing to it. Resolution Determine which script tag is generating the error. When did the error occur?  When the page loaded?  When a value changed?  When the user clicked?  Did it happen once or multiple times?  These questions can help you narrow down which script has thrown the error. Save the graphic under a different name.  Delete portions of the graphic until the error clears.  The component that was removed holds the offending script. The cmd# syntax is indicating which line of the script has the error.  Launch the script editor by clicking the "..." button next to the script Content attribute.  In this example, go to line 52 of the code. The text in quotes tells which method was being used.  In this example "getAttribute."  Investigate what is in the parameters of the getAttribute() function.  Verify that object exists as defined. Edit the script to point to a valid object, rename or restore any deleted object.

Issue MSMQ error message: "Appears to be a problem with configuration of system please check to make sure you have MSMQ correctly installed" Environment Continuum 1.9X Windows XP and 2003 Server Cause Message Queuing Not installed Resolution Open Control Panel Select Add and Remove Programs Select Add / Remove Windows Components Select Message Queuing Restart System and test.

Issue Created a digital schedule in an Automation Server folder and it never changed the value of the digital value Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Automation Server (AS) Cause Digital value bound to a digital schedule failed to change the value at a time when a scheduled event should have triggered. The probable cause is that the Automation Server time setting is incorrect. Resolution Configure Date and Time of an Automation Server: Click on the Automation Server in workstation Go to the Date & Time tab Set the proper time zone and save the changes. Use Network time synchronization or manually adjust the time if needed and save the changes again. Note that it might take some time before changes to the Date & Time settings affects the Automation Server system clock if you use Network time synchronization.

Issue The ACX 57xx series controller supports up to 2 xP or xPB (bi-directional) expansion modules, plus a display for extended input and output configurations. The ACX 57xx series controller is compatible with all of the TAC expansion modules. For more information about expansion modules, see the xP Expansion Module Reference, 30-3001-840 and/or the xPB Expansion Module Reference, 30-3001-883. What are the valid channel numbers for expansion IO on the ACX5740/5720? Environment CyberStation ACX5740 ACX5720 Cause The expansion IO channel number assignments is different in the ACX5720 due to the fact that it has only half the onboard IO as the ACX5740 Resolution The ACX5740 has 12 onboard inputs and 4 onboard outputs, therefore the first expansion input channel is 13 and the first expansion output channel is 5 The ACX5720 has 6 onboard inputs and 2 onboard outputs, therefore the first expansion input channel is 7 and the first expansion output channel is 3

Issue When executing a Find New BACnet Device a third party controller (Trane) would not come into the system.  Product Line Andover Continuum Environment Continuum BACnet Trane Cause BACnet Network ID was assigned to 1 in the third party device. Both the CyberStation Device node ID and the third party device Node Id can not be set to 1.  Resolution Have the vendor change the device node ID from 1 to a unique value on the network. See Could not learn in a new 3rd Party BACnet device.  

Issue "Invalid attribute property" error when trying to create NetController II in Continuum v1.74 SP2 as Controller Type "9681". Environment Continuum v1.74 SP2 NetController II Cause Trying to create new NetController II device object with a "Controller Type" of "9681". "A Guide to Version 1.74 Support for NetController II and ACX 57xx" states that there is only one NetController model, the CX 9680. Please ignore references to the 9681. Resolution Create the Netcontroller II as  a Controller Type "9680" as stated on page 15 in document number 30-3001-1001 "A Guide to Version 1.74 Support for NetController II and ACX 57xx".

Issue When using the IC_LON Plug-in an error is reported indicating that the SNVT is not supported. Unknown SNVT Type:  92 Environment Sigma IC-LON Version 1.E Cause The Sigma IC3-LON corresponds with version 11 of the LONMARK Resource files. Not all SNVT types are supported. Resolution Not all SNVT types are supported, please confirm which SNVT’s are supported by viewing the IC3-LON release note.

Issue Upgrading Loytec L-IP to the latest firmware or checking current firmware version. Environment Loytec L-IP Vista Network Interface Cause UL 864 v.9 for Smoke Control requires at least version 5.04 firmware in all system L-IP's. Resolution Verifying L-IP Firmware Version via Console Connection To use the serial interface, the DB9 console connector of the L-IP can be connected to the RS-232 port of a PC. The L-IP-3ECTB and L-IP-33ECTB use a standard null-modem-cable must be used to connect the L-IP’s DB9console connector to the RS-232 port of the PC. The PC will communicate with the L-IP using a HyperTerminal program with the communication settings set to 38,400 bps / 8 data bits / no parity / 1 stop bit / no handshake. The L-IP displays the console menu shown in Figure 1 upon a successful HyperTerminal connection initiated by a “enter” keystroke or power cycle of the L-IP: LOYTEC electronics GmbH www.loytec.com L-IP Configuration Menu ======================= [1] Show device information [2] Serial firmware upgrade [3] System configuration [4] EIA-709 configuration [5] IP configuration [6] EIA-852 device configuration [7] EIA-852 server configuration [8] Reset configuration (factory defaults) [9] Device statistics [0] Reset device Please choose: Figure 1: L-IP main menu. Select Option 1 to Show device information  This menu item shows information about the L-IP and the current firmware version. The output should look like what is shown in Figure 2. Product information =================== Product code: L-IP-3ECT Firmware: L-IP Primary image Version: 5.0.5 Build date: Fri Mar 18 10:41:29 2005 Serial number: 002304-80000000E73C Free memory: 557K,57K System temp: 33.3C Supply volt: 12.0V Unique Node IDs =============== Port 1: 80 00 00 00 E7 3C EIA852: 80 00 00 00 F7 92 Figure 2: Device information. (For UL 864 v9: If the Firmware Version does not reflect a Version 5.0.4 or Version 5.0.5, you must update the firmware to an approved version in the next steps. If the L-IP contains an approved version, further action is not required.) L-IP Firmware Upgrade To download the firmware via the console connected the L-IP to the RS-232 port of a PC via its console interface as outlined above. Download the lswitch_lipxxx.zip located at www.loytec.com to the PC. Install the LOYTEC serial upgrade tool (LSU Tool) by double clicking LSU_2_0_1setup.exe. Double click on the lswitch_lip_xxx.dlc file. This will start the LSU Tool and load the firmware image referenced in the . lswitch_lip_xxx.dlc file. The start window of the LSU tool is shown in Figure 3. *note that the lswitch_lip_xxx.dlc file and the lswitch_lip_xxx.dl file must be stored in the same folder. Figure 3: LSU Serial Upgrade Tool in idle mode. If the L-IP is not connected to COM1 you can change the port to COM1, 2, 3, or 4. Press “Download” to start the download. A progress bar as shown in Figure 4 can be seen. Figure 4: Progress bar during firmware download. If the upgrade is successful the following window appears (Figure 5). Figure 5: Successful firmware upgrade. Exit the LSU Tool. Reconnect through HyperTerminal connection and  initiate the console by a “enter” keystroke or power cycle of the L-IP. At the console main menu, select option [1] Show device information, and press Enter. This will bring up the current device information as shown in Figure 2, for verification that the firmware version has updated successfully.

Issue A version of the WorkPlace Tech Tool software prior to version 5.7 had previously been installed on the computer and licensed with an expiring license.  The WPT software was updated to version 5.7.x.  When the previous expiring license was about to expire, the next expiring license renewal was requested.  However, when the previous expiring license did expire, the new one also expired. Environment Initial WIBS/WPT license on computer created by installation of any version Wonderware for Intelligent Buildings Software (WIBs) or any version prior to 5.7 of the WorkPlace Tech Tool software (WPT). New version (5.7.x or later) of the WorkPlace Tech Tool software installed on same computer. Cause New license request was incorrectly generated using the WIBSPurchase ("Purchase WIB Software" icon) program instead of using the "Purchase WorkPlace Tech Software" icon on the computer desktop. Resolution Use the "Purchase WorkPlace Tech Software" icon on the computer desktop to request any license updates for version 5.7.x and newer of the WorkPlace Tech Tool software.

Issue Binding to Security Expert values through EWS results in "Type does not exist" error when attempting to save a binding. Environment SmartStruxure Security Expert Cause The value being bound was coming through and mistakenly being created by SBO as an enumerated value which is not supported. The value is actually an integer. Resolution A hotfix has been created to resolve this in SBO 1.9.1.6700.   There is also a workaround that works for previous versions of SBO.   If you update (configure) the value type of the EWS ValueItem property Value with the system.pt.Int32 it will work to do bindings.   1. Open the propertydialog of the EWS ValueItem and click the configuration button of the Value property.    2. Check the Type checkbox which already contains the value type system.pt.Int32. 3. Press Ok and save the change in the dialogproperty. 4. Now it's ok to do bindings with this Value.

Issue IAS stands for Intrusion Alarm System. If stopped in "Initializing" then follow these steps. Normally if using the bin file from I/NET version 2.21, the display will show correctly. The bin file for version 2.30 and above may have to complete the step to get past the initializing screen. Intrusion Alarm System (IAS) also referred to as the OP5 or Remote Arming Terminal RAT Environment I/NET Seven with a 7798C and Intrusion Alarm System I/NET version 2.21 and above. I/NET version 2.16 and bellow do not support the OP5 Terminal. Cause Configuration Settings and database download. Normally if using the bin file from I/NET version 2.21, the display will show correctly. The bin file for version 2.30 and above may have to complete the step to get past the initializing screen. Resolution After a software download from I/NET Seven 2.30 to current, the OP5 is always in Initializing Mode.  Hot to correct this? In the MCU Configuration Editor, the type has to be DPU The device has to be saved in Network Configuration If these two are true, it will pass the initialization part of initializing mode. Here are the steps in order to get the OP5 terminal to setup at my desk:  Set the OP5 as link 29 Backup the existing database. If DCU password is requested, it is 4444 Backup existing database. Copy the Database from CD\support\IAS Templates\8_Zones to local hard drive Copy the SAV file from CD\support\IAS Templates\8_Zones to local hard drive in the Sav folder of I/Net. Be sure to rename DCUxxxx.sav Restore database you just copied from CD Go into Network Configuration and delete link 94 Go into Network Configuration and save the link penetrating down all levels Do a station restore from the SAV file you copied to the 7798 and renamed from CD. I recommend SLI then DPU, in that order. Go into Edit, Controller, MCU Configuration and make OP5 29 link DPU Go to Edit -  Controller - Intrusion Alarm System Add point OP5 - 2 (This one is configured to link 29), Choose one or all if so desired. Click OK twice. The led light in the upper left corner on the OP5 will be lit now. Make a station restore and the OP5 keypad appears. Go into pull down menu for Access Add Door to Tenant Add Door Schedule for all three groups Go into MCU Config and check OP5 is on Link 29, and set for DPU If OP5 is still ‘Initializing’ then change MCU Config Link 29 to Internal, exit Go into MCU Config and change Link 29 to DPU My OP5 works using I/Net 2.40, Xenta 527, 7798C, OP5. I have the OP5 link as 29. Please alter the instructions to fit your link number. Step 6 refers to the link 94, which is part of the database here, you can delete since it is not relevant to your location. Here is a pdf with an example of the setup of a typical OP5. Another paper written on the steps they performed using the OP5 is found Here.

Issue Have Cyberstations and BCXs and/or 3rd party devices on different subnets Product Line Andover Continuum Environment Cyberstations BCX 40xx 3rd Party MSTP/IP BACnet Cause Unable to communicate with B3 devices or get B3 point values. Resolution Review LAN configuration. Each separate subnet requires a single BBMD for communication. See BACnet documentation on line via Cyberstation or "Introducing BACnet" document in Cyberstation. See Simple BBMD setup.

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue A message that can be intercepted by a guard at a monitoring station. When you configure your access control system to accept PINs, I/NET has the ability to detect PIN entries When you configure your access control system to accept PINs, I/NET has the ability to detect PIN entries made under duress conditions. For example, if an employee is being forced to provide an unauthorized individual access into a secure area, the employee can substitute the final digit of their PIN with a digit that indicates a duress condition. In this case, I/NET will allow access but will also silently generate a duress message that can be intercepted by a guard at a monitoring station. Product Line TAC INET Environment TAC I/NET Seven with Access Control using a pin pad. Cause Duress entrance causes a security guard to be notified that there is a situation to be resolved. Resolution Duress detection is active anytime a door is operating in a mode that requires the entry of a PIN. I/NET supports selectable duress schemes that you can assign on a per-tenant basis. The following duress schemes are available: Default — I/NET's default duress scheme detects when an individual substitutes their PIN with a substitute number. The default duress last pin is 9. The duress code is the user's PIN number with the last digit changed. For example, 12345 becomes 12349. Add n (where n is a value from 1 to 9) — I/NET detects when an individual substitutes a digit of their PIN with a predetermined digit. For more information on this sensitive topic, contact Product Support to begin a conversation about Duress Notification in I/NET.