Building Automation Knowledge Base

Issue Can the profile in a MNL standard LonMark controller be changed in the field?  For example, can a MNL-20RH3 (heat pump profile) be changed to a MNL-20RS3 (satellite 3 profile)? Environment MNL standard LonMark controllers Cause The LonMark Profile is stored in the controller's firmware. Resolution No, the LonMark Profile cannot be modified.

Issue If you have a double address on an SCU 1284, and the operation of the LEDs are wrong after you installed I/NET Seven rev 2.21 what do you do? Environment I/NET Seven rev 2.21 SCU 1284 Cause I/NET Site Resolution If you had set a double address in the SCU 1284, the operation of the LEDs are wrong. Both LED (Green and Red) are active permanently no matter what you set in the Door Editor(Anode/Cathode), the LED will just flash once when the door is operated. If the SCU is set to single address, the LED will work correctly. The equipment setting that will cause this issue is having a 7798C with BIN file Rev 1.08 and SCU1284 with BIN Rev 3.25. To correct this issue requires you to only change the BIN file in the 7798C from rev 1.08 back to Rev 1.06. This 1.06 Bin file is from the I/NET Seven rev 2.16 release. Please note the SCU1284 LED issue DOES NOT exist in the following BIN files in the I/NET Seven rev 2.21 release. 7798B Bin is OK 7793 Bin is OK SCU1284 Bin(3.25) is OK

Issue Power to devices are Full Wave or Half Wave. Device is connected to 24VAC and begins to smoke because the voltage power input from transformer is not wired correctly. Product Line TAC INET, TAC Vista Environment Devices such as a Xenta Router or a controller which is powered by an external 24VAC transformer. Cause Devices such as a Xenta Router or control board is connected to 24VAC and begins to smoke because the power input from transformer is not correct. Resolution Download Full Wave Half Wave.pdf which illustrates the transformer to device wiring configuration. PoE is not supported for any of the Ethernet ports on I/NET devices.  

Issue The Neuron ID assigned is already being used by another device in the network. Environment LonMaker NL220 Vista LNS Cause The Neuron ID assigned is already being used by another device in the network. Resolution If you are typing in the Neuron ID manually, check to make sure a device actually does have that neuron ID already.  If you are service pinning and you are certain that no other device is using that Neuron ID, then it may be a “phantom node” that will come to the surface by attempting a resynch.  You can then delete that phantom node and proceed.

Issue i28xx type of Infinet Controller has different range of WC (Water Column) than i28xx-V Infinet Controllers. What are the input voltage settings for i28xx and i28xx-V controllers' AirFlow sensor input? Environment Infinet controllers (i2865 & i2865-V, i2866 & i2866-V , i2885 & i2885-V) Cause Input settings for Velocity Pressure Sensor is different than the other regular analog input (voltage input) configuration. Resolution The i28xx type of Infinet Controller has 0~2" WC (Water Column) range, the input voltage should be set to 0~2V. The i28xx-V type of Infinet Controller has 0~1" WC (Water Column) range, the input voltage should be set to 0~1V.

Issue How to redirect from default website to webstation. Want users to get to webstation even if they only type in the server name Environment TAC Vista 5.1.5 Windows 2008 IIS7 Cause It is easier for customers to just type in the server name and not have to remember the /webstation Resolution  Open IIS manager Click on Default Website Double click on HTTP redirect     4.Type in the URL to Webstation (default http://localhost/webstation) 5. Click on apply under actions.

Issue EPI Builder will not run even though the security key is enabled for badging Get error Badge Manager Cannot init license after clicking on Create/Edit Badge in Personnel Manager BadgeManager Cannot init license Environment Continuum EPI Builder Windows XP Keywords: account, admin, administrator, user, account, dongle, permission Cause The logged in user account does not have enough permission to run EPI Builder Administrator account runs EPI Builder OK Resolution Give the required user account enough permission to run EPI Builder Eg. Windows "Users" account may not have enough permission to run EPI Builder, where Windows "Power Users" normally have enough permission to run EPI Builder

Issue Extended LonTalk is supported In Vista 5.1.5 but it doesn't work, it is possible to read but not write to the device. Error message when writing: "Local network management failure" Product Line TAC Vista Environment Vista Server Cause When adding a Extended LonTalk device in to TAC Vista, TAC Vista will see in the xif file that this is a Extended LonTalk device and set a Extended LonTalk device flag for that device. It is possible to see the flag if hold down shift+Ctrl and click in properties for the lon device, it is called "EXTENDEDLONTALK".  If the xif file is imported to a TAC Vista with a version earlier than Vista 5.1.5 the Extended LonTalk will not work. Resolution Make sure the "EXTENDEDLONTALK" flag for the lon device is set, if not import the xif file again in Vista 5.1.5.  

Issue How can more than 50 globals be transmitted from a Sigma controller when I have a lot of digital objects states to pass between controllers? Environment Sigma Controller (all) Cause Sigma controllers are limited to 50 broadcast globals. Resolution Up to 16 Sigma Digital objects states can be reference in a single programmable object.  By performing a binary count the various states can be represented by a single analogue value which can then be broadcast as global data. Sigma programmable object MASK command can be used to decode analogue representation of a single analogue value that represents up to 16 digital states (on/off).   For example the value of 901 represents the state of a number of Sigma DI Objects where each bit indicates the on/off.  Hence, this translate to the 16-bit binary value  0000001110000101  where 1 = on and 0 = off To set-up bit masking click here for details. 1.  Create a program object in the transmitting controller that 'binary' counts up to 16 digital objects. 2. In the receiving controller create up to 16 programmable objects to decode the transmitted analogue value.  e.g

Issue Under objects such as Doors and Inputs what is the "Commands" option used for? Product Line Security Expert Environment Security Expert Cause Unsure how to use the Commands option showing in some of the objects options. Resolution These cannot be adapted for general use by installers/integrators. These are mostly used for controller instructions that have been included in the firmware but have not been built into the UI yet, as well as internal testing. Leave these alone unless you have a specific need and the instructions from Product Support on how to configure the command.

Issue How to generate an alarm in TAC Vista, if some event happens in Modbus units. Generating alarms in Vista from Modbus devices. Product Line TAC Vista Environment TAC Vista 5.x Xenta Servers Xenta 511, 527, 701, 711, 721, 731 (since Vista 5.1.5), 913 Cause It is possible to see alarms generated in Modbus devices in TAC Vista but these will not automatically create an alarm that appears in the alarm pane. Resolution Create a change of state object that is connected to the alarm signal from the Modbus device. If the Modbus device goes offline the value will remain at its last polled value. In this case, there may be no alarm generated so you can also monitor the online option in the Modbus device template to give an alarm that the Modbus device is offline.

Issue Communication to LON controllers is lost.  After a re-start of the station, the following errors appear in the standard output window: ---------- Station Starting:   MON MAY 02 14:53:10 2011 ---------- Tridium Niagara Station, r2.301.529.v1 [test] MESSAGE: ErrorLogService installed [/test/services/ErrorLogService] Start service: ControlEngineService [3] ControlEngineService Start service: UiEngineService [7] UiEngineService Start service: NotificationService [6] NotificationService Start service: LogService [5] LogService Start service: AuditLogService [2] AuditLogService Start service: ErrorLogService [4] ErrorLogService Start service: LonWorksService [9] LonWorksService Error opening driver LON1 java.lang.Exception: Unable to open lonworks driver *************************************************************** ERROR: Cannot startService [Sys: LonWorksService [9] LonWorksService] java.lang.IllegalStateException: Unable to open lonworks driver at tridiumx.lonworks.services.LonLinkLayer.start (bytecode 143) at tridiumx.lonworks.services.LonWorksService.startService (bytecode 12) at tridium.foundation.Sys.startServices (bytecode 49) at tridium.foundation.Station.startStation (bytecode 63) at tridium.foundation.Sys.boot (bytecode 27) at tridium.foundation.Sys.bootLocalSns (bytecode 17)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) tridiumx.lonworks.LonException E_LON_COMM_SERVICE_NOT_STARTED    at tridiumx.lonworks.services.LonCommService.doLonCommSendRequest (bytecode 19)    at tridiumx.lonworks.services.LonCommService.lonCommSendRequest (bytecode 3)    at tridiumx.lonworks.services.LonCommService.lonCommSendRequest (bytecode 68)    at tridiumx.lonworks.util.Neuron.readMemory (bytecode 29)    at tridiumx.lonworks.util.Neuron.readMemory (bytecode 9)    at tridiumx.lonworks.util.Neuron.isNMAuthSet (bytecode 32)    at tridiumx.lonworks.util.Neuron.isNMAuthSet (bytecode 16)    at tridiumx.lonworks.devices.LocalLonAppDevice.verifyDevice (bytecode 2)    at tridiumx.lonworks.services.LonWorksService.stationReady (bytecode 28)    at tridium.foundation.Sys.stationReady (bytecode 23)    at tridium.foundation.Station.startStation (bytecode 87)    at tridium.foundation.Sys.boot (bytecode 27)    at tridium.foundation.Sys.bootLocalSns (bytecode 17)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) MESSAGE: Station started successfully. (HTTP port=80) [test] These errors follow a short time later: Freeing transaction from transmit driver, tag is 4 The LonException code is java.lang.Exception: ldvWrite() failed - rc = 6, in transmit driver Freeing transaction from transmit driver, tag is 5 The LonException code is java.lang.Exception: ldvWrite() failed - rc = 6, in transmit driver  ... repeated Environment Niagara R2 UNC-520-2 Niagara R2 UNC-410-1 (including the -N international versions) Also applies to obsolete models:  UNC-500, UNC-510, UNC-600, UNC-610 Cause These errors indicate the Niagara operating system is not communicating to the (on-board) Echelon MIP chip.  To confirm, run the following test: Open the running station in Tree View Go to the Properties of the localLonDevice, specifically the Engineering tab Blank out the "neuronId" and click Apply Reboot the UNC When the station has started successfully, return to the neuronId field and observe the value in the box If the neuronId field is all zeros, then there is a hardware problem with the Echelon MIP chip. Resolution This issue is not field-repairable. Contact Product Support Services for a return authorization number.

Issue Shielded twisted pair cable may have been installed in an area of high EMI/RFI, and proper grounding of the shield wire is necessary to make the shield effective. Environment A segment of LON trunk with shielded, twisted-pair cable. Cause Proper grounding helps to avoid DC and 50/60 Hz ground paths from being formed through the shield. Resolution Follow the Guidelines as presented in the Echelon FT 3120/ FT 3150 Smart Transceiver Data Book, page 114, Figure 5.7 "Terminating and grounding Shielded Twisted Pair Cable." Grounding Shielded Twisted Pair Cable When using shielded twisted pair, terminate the twisted pair and ground the cable shield, as shown in Figure 5.7. Figure 5.7 Terminating and Grounding Shielded Twisted Pair Cable The twisted pair is terminated according to the guidelines listed in the previous sections. The cable shield should be grounded using a capacitor to tie the shield to earth ground, and a large-value resistor to bleed off any static charge on the shield. Tie the shield to earth ground through a capacitor, instead of a direct connection, in order to avoid DC and 50/60 Hz ground paths from being formed through the shield. Typical values for Rb and Cc are as follows: Cc = 0.1 µF, 10%, Metalized Polyester, ≥100V Rb = 470kΩ, 1/4W, ±5% The cable shield should be grounded at least once per segment, and preferably at each device.

Issue Doctor and SigmaX Index edit password Doctor and SigmaX Binary file edit password Environment BAS Doctor Sigma SigmaX Doctor Cause Need a password that allows access to edit an index or binary file. Resolution IE is the password for index edit. BE is the password for binary file edit. These passwords are not case sensitive. Either IE/BE or ie/be can be used.

Issue How can I run Windows programs from a workstation plain english program? Environment Cyberstation Plain English Windows programs Cause Launching windows programs from Continuum Resolution Please see this link for information on using the Shell plain english function NOTE A Plain English script can be added to some graphics objects (Plain English Script tab), so for example you could run a batch file (in the continuum directory) from a graphics button using Shell "test.bat"

Issue I/A Series Software Compatibility with the Windows 7 Professional Operating System Product Line TAC IA Series Environment Microsoft Windows 7 Professional operating system (32-bit, 32-bit XP Mode, 64-bit XP Mode) WorkPlace Tech Tool (WPT) 5.7 and later PSI / XPSI  4.1 MNCI 4.0 MICROFLO Balance 4.0 PSOPRIF 11.6 Tree Tech 3.1 LON Flow Balance 3.0  Cause I/A Series software should only be run on tested and compatible equipment to avoid problems with software or hardware. Resolution See Product Announcement PA-00163 for detailed information on compatibility of current I/A Series Software tools and Windows 7. (Updated 3-14-12, replaces PA-00114 with PA-00163). See I/A Series (Niagara) R2 Windows Compatibility Matrix for information on the I/A Series (Niagara) R2 compatibility See WorkPlace Tech 5.8.x and 5.9.x Operating System and Microsoft Visio Compatibility for information on the I/A Series Workplace Tech compatibility

Issue What are the fiber cabling specifications for an Infilink i2210? Product Line Andover Continuum Environment Infinet Infilink i2210 Mstp B-link-F Series Cause Fiber connections have specific parameters to work properly Resolution From the I2210 and B-link-F Series Installation Guides Fiber Optic cable: 62.5/125 duplex glass multimode fiber optic cable with ST-style connector Maximum attenuation allowable: 12 db For some additional information related to fiber optic terminology, see the following: https://arcelect.com/fibercable.htm

Issue After an Upgrade to an Automation Server controller, the Requested values of some outputs and actual values do not match. Product Line EcoStruxure Building Operation Environment Enterprise Server Workstation Automation Server with I/O Modules Cause The upgrade process somehow has caused some issues with the comm between the AS with I/O modules and the Enterprise Server/Workstation. Resolution Perform a cold start on the AS.

Issue Can I/A ENC-520 interface to a Honeywell Q7700 Network Interface for boiler/burner monitoring? Environment I/A Series G3 (Niagara) ENC-520 Cause Driver for Interface Resolution Tridium reports that there is no G3 driver to support an interface with this product.

Issue Firmware version and bootloader version do not match Product Line Andover Continuum Environment BCX b3 Cause Verification required on why the two do not always match Resolution When firmware versions (application firmware files) are posted to the web, they do not always included the associated bootloader version. The reason for this is that rarely is a bootloader version changed. When bootloader versions do change it will be announced in the release notes for the particular firmware version.