Building Automation Knowledge Base

Issue Information on Magelis Opti PC Touch Panels Environment Site wanting to use Magelis Opti PC Touch Panels Cause Need information pertaining to the Magelis Opti PC Touch Panels. Sometimes referred to as HMI or Human Machine Interface  Resolution Magelis Opti PC Touch Panels information is located on Exchange Extranet.  Magelis Opti PC Data Sheet Magelis Opti PC Installation Guide Opti PC User Manual Opti PC User Manual (other languages) For the latest HMI software and Release Notes for VijeoDesigner, please visit the following link VijeoDesign

Issue How to get server date and time into a datetime variable. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building  Operation Enterprise Server Cause Documentation Resolution Create a 'Value' object of type 'Time Stamp Value' in the server. Right click on the server's name and select 'Edit bindings' Find the time stamp value created in step 1 in the object tree on the right. Bind the value of the time stamp object to the server's time as seen in the screen shot below.

Issue How do you get the system information of a Xenta Server from a web browser? Environment Xenta Server Xenta 511, 527, 701, 711, 721, 731, 913 Cause View the most up to date system information for the firmware version loaded into a Xenta Server. Resolution Getting system information using a web browser: Menu Utilities-System Information Displays all system information such as software versions etc. Use cut/paste to save information. Menu Utilities-Error-Error-System Error Log Displays system information and all error messages in the system error log. Use cut/paste to save information.

Issue Seven Reports Error "CRPaige library CRPaig80.DLL cannot be found". Product Line TAC INET Environment I/NET site with Windows OS Cause Missing CRPaig80.DLL error message Resolution CRPaig80.DLL can be found on the original I/NET Seven installation CD (cd-drive:\program files\inet seven). Copy CRPaig80.DLL to the root I/NET Seven folder (c:\program files\inet seven). Click Here to download a zipped copy of the CRPaig80.DLL

Issue Xenta 5/7/9xx System Report shows "Menta: Overrun error (Error#:62468)" Environment Xenta 701, 711, 721, 731 version 5.1.4 and below Cause A Menta application took to long to run a loop. Probably due to temporary high load of the system. Resolution Upgrade the Xenta 700 to version 5.1.4 SP1 or greater, preferably the most recent release of Xenta Server software.

Issue How can the content of an email or pager alarm message be edited? The message is too long to display correctly on a pager. Product Line Andover Continuum Environment Microsoft Windows XP Microsoft Windows 2003/2008 Server Microsoft Windows 7 Microsoft Outlook Cause Alarm messaging can be customized or truncated for display in a pager, where the number of characters is more limited. Resolution Go To C:/Program Files/Continuum or C:/Program Files (x86)/Continuum if using a 64bit OS Open Normalemail.txt or Normalpager.txt Edit the file in this format: Email On Alarm : Continuum Time : <\date> <\time> , Name : <\name> , Value : <\value> , State : <\state> , Message: <\message> , THIS IS THE body of the EMAIL I RECEIVE Email On Alarm : Continuum Time : July 21, 2010 03:12:53 PM , Name : Danet\da9900two\testnum , Value : On , State : Alarm , Message: Error ,​

Issue Satchwell MBF 3-port Rotary Shoe Valve Body Open / Close status determination from Spindle position. Environment Satchwell MBF 3-port Rotary Shoe Valve Body installations. Cause Satchwell MBF 3-port Rotary Shoe Valve Body is installed in pipework and Open / Close status cannot be determined by observing Valve Body Shoe positions. Resolution The Satchwell MBF 3-port Rotary Shoe Valve Body Spindle protrudes through the side of the Valve Body. The position of the Valve Body Shoes may be determined by observing the position of a hole drilled through the Valve Body Spindle. If the hole is ( l ) then Valve Body is fully open to Port 2 If the hole is ( -- ) then Valve Body is fully open to Port 3 If the hole is ( / ) then Valve Body is half open to Port 2 and half open to Port 3   When the hole through the Valve Body Spindle is VERTICAL having turned the Valve Body Spindle fully Anticlockwise, then the Valve Body is fully open to flow and fully closed to bypass. When the hole through the Valve Body Spindle is HORIZONTAL having turned the Valve Body Spindle fully Clockwise, then the Valve Body is fully closed to flow and fully open to bypass. When the hole through the Valve Body Spindle is at an ANGLE of say 45 degrees, then the Valve Body is half open to flow and half open to bypass.   Please check the latest catalog for current equipment.  

Issue Can the EasyLobby software be integrated to I/NET Seven only, or can it be integrated to the I/NET Host Tool? Do you have a detailed configuration guide to integrate to I/NET systems? Is there any Visitor Management Software (VMS) that works with I/NET? Product Line TAC INET Environment I/NET Seven I/NET Host Tool EasyLobby Visitor Management Software (VMS) Easy Lobby Cause I/NET site and client is requesting a Visitor Management Software Resolution Concerning EasyLobby, they have a full integration to I/NET; however, it was not a joint effort. They did it on their own without I/NET R&D involvement. I/NET development/PSS has never tested it, and will not support the integration in any way. Please contact  EasyLobby support if there are any integration issues. The product is only supported on Continuum because Continuum in Boston & EasyLobby did that integration together. EasyLobby obtained a copy of v2.40 of I/NET and did their own interface without Product Support Services.  For third party individual management software programs which work with I/NET, search the Knowledge Base for "ID Works."

Issue A Deny Entry Tenant Message is given instead of a valid card read. Product Line TAC INET Environment I/NET Seven AMT Cause The Deny Entry Tenant message is delivered when the credential read is not known to the controller for any of the following reasons: The door being read is not part of the individuals tenant. The SLI does not have the correct database Card Translation is incorrectly enabled/disabled in the door editor There is a hardware error with the Card reader. Resolution General Steps: Determine if the issue only happens to a single individual or a group or all cards. Select Access>Tenant. Verify that the door has been added to the correct tenant(s) Select Edit>Individuals and browse to the card(or a test card) in question. Verify that the card has the been added to the door correctly. Follow the directions in How to force a download of card data to force a download. If this fixes the issue, go to the "SLI does not have the correct database section" In AMT, select window options and add the message column to the window Find a Deny entry tenant message and see if the message column matches up with Hex card number for the badge that was read. If all you get is a scrambled number, There is probably a hardware error. Verify Card Translation is Enabled (this section assumes you are using large card number format) Select Access>Doors Modify the door in question Check the box next to "Card Translation". If this option is not available you will need to flip Dip switch 7 on the SCU Compare this setting to a few other doors on the system. Thy should all have the same setting Hardware Error The easiest way to prove a hardware error is to plug a spare card reader directly into the DPU or SCU. If the problem is immediately solved replace the field reader. If not, try unplugging other readers on the controller and see if the problem goes away for that reader. It is possible that the controllers power supply is no sufficient to power the reader. Use an external power supply instead. Various known fixes for SLI database Errors: Take the SLI to it's boot state and restore bin file and database files from the Server If you are using I/NET 2.15-2.21, upgrade to 2.31 Insufficient memory: The SLI will allocate memory for all possible individuals in a tenant regardless if they are used or not. For example, if the site has only 500 cards, but the tenant is set to 32000 individuals, this will use the same controller memory as a site with 25000 individuals.  Reducing the number of individuals allocated in the tenant has been shown to clear up Denied Entry Tenant messages. System traffic: In I/NET 2.31 and above, the filemaster or server will indicate when badge data is being downloaded on a status bar in the bottom right hand corner of the screen. If this indicator is constantly showing downloads, it is due to poor system communication causing constant polling of the database.  Follow these steps to fix this issue. Turn Automatic DPU restore off on all links and wait for the download messages to stop. (this is done by selecting Edit>Host Computer>Network Configuration, then modifying each link) Wait for the automatic downloads already requested to finish. Re-enable Automatic DPU restore on each link, one at a time. Wait for the system to finish individual downloads before moving on. When you find a link that take an excessive amount of time (compared to others) to finish downloading, troubleshoot that links controller LAN wire.

Issue If there are already TAC Xenta 104-A devices commissioned in an LNS database, then it may not be possible to add TAC Xenta 104-A controllers of different system versions into the same database. Nor is it possible to do a replace. Certain firmware versions of the 104-A controller are not compatible with one another. Trying to add a different system version to an existing database will produce an interface does not match error. For more information on this error, see The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Product Line TAC Vista Environment NL220 LonMaker Vista Cause The incompatibility between different system versions of the TAC Xenta 104-A controller is due to a change that was made in the size of the SNVT declaration area residing in the device memory. The change in device memory occurred between version 1.10 and 1.20. For the same Program ID, LNS requires this size to be the same as previously commissioned devices. Resolution The first action that should be taken is to update the LNS network to the most recent version. It has been confirmed that newer LNS versions have addressed this issue so that no further action is required. With newer LNS software, different version types of the TAC Xenta 104-A may be added to the same database.  If upgrading the LNS software is not an option, the firmware in the controllers can be upgraded as a work around to correct the issue. In order for a TAC Xenta 104-A controller with version 1.10 to reside in the same database as version 1.20, the 1.20 controller must be upgraded to version 1.20A. In similar fashion, version 1.21 must be upgraded to version 1.21A to coincide with version 1.10. To add a 104-A controller with version 1.21 to a database with version 1.20 already on it, no further action need be taken. Version 1.20 and 1.21 are compatible. It is important to reference the compatibility matrix found below. Changing the firmware to an "A" version will then make the controller incompatible with versions 1.20 and 1.21. Also note that it is not possible to upgrade from system version 1.10 to 1.20/1.21 due to the memory configuration. The modified "A" versions will not be loaded into the controllers from the factory. These NXE/APB files will only be available on the Buildings Business Extranet. To download the NXE/APB file for v1.20A or v1.21A, go to The Exchange Download Center. Perform a search for TAC Xenta 104-A Firmware. The 1.20A version will be labeled "TAC Xenta 104-A Version 1.20 (78 Kb)" and the 1.21A version will be labeled "TAC Xenta 104-A Version 1.21A (45 Kb)".

Issue When alarm is triggered in the controller sometime the alarm will immediately be displayed on the Alarm View as expected, you trigger the same point alarm a few times and some times there is a delay of up to a minute or two before the alarm shows up on the Alarm View. Looking at a list view of the alarms you can see the difference between the time stamp and the time of log Product Line Andover Continuum Environment CyberStation All controllers Cause The controller has been taught about CyberStation whose network ID has been since changed. Resolution Use a PE program to find out from the controller's perspective what it has been taught. If the controller contains entries in its table that it should not have, then reload the controller to remove them. See Visibility into a controller's list of peer controllers and Cyberstations following a teach for a sample PE program.

Issue TAC TRV-S series Butterfly Valve Body requires replacement. Product Line Field Devices Environment TAC TRV-S series Butterfly Valve Body installations. Cause Obsolescence of TAC TRV-S series Butterfly Valve Body. Resolution Replace TAC TRV-S series Butterfly Valve Body with S-E VF208W series Butterfly Valve Body. Replace TAC MB15 / MB30 Actuator with S-E MF20 / MF40 series Actuator as appropriate. It should be noted that where a TAC TRV-S series Butterfly Valve Body is to be replaced by a S-E VF208W series Butterfly Valve Body the TAC Actuator fitted to the TAC TRV-S Butterfly Valve Body will not be suitable for reuse on the S-E VF208W.Buttterfly Valve Body. TAC TRV-S series Butterfly Valves utilise TAC MB15 / MB30 series Actuators. TAC MB15 / MB30 Actuators are not suitable for use on S-E VF208W series Butterfly Valve Bodies. S-E VF208W series Butterfly Valve Bodies utilise S-E MF20 / MF40 series Actuators. S-E MF20 / MF40 series Actuators are suitable for use on TAC TRV-S series Butterfly Valve Bodies, but then no linkage kit should be mounted. MF20 datasheet MF40 datasheet  

Issue Transformer for I/NET Controllers Environment XFMR1, XFMR2, XFMR3, XFMR4, XFMR5, XFMR6, XFMR7, XFMR8, XFMR9, XFMR10, XFMR11 IRB8, IRB8HC Relay boards 7700, 7740, 7741 DCUs 7750, 7760, 78XX, 72XX UCs, 7716 7718, 7780, DPU3100, DPU7910A, DPU7920 78XX TAPs 7780 DLCU 7728 I/SITE I/O Cause The following table describes each transformer, the primary power required, the secondary power supplied by the transformer and the products each transformer model supports. Some of these transformers have two secondary outputs and these are shown in the table. Resolution Download the attached PDF document here. Model Number Description Comments XFMR1 Transformer, 120Vac Primary, 20Vac @ 3.4A Secondary IRB8, IRB8HC Relay boards XFMR2 Transformer, 120Vac Primary, 10Vac @ 3.6A and 36Vac @ 0.7A Secondaries 7700, 7740 7741 DCUs XFMR3 Transformer, 240Vac Primary, 10Vac @ 3.6A and 36Vac @ 0.7A Secondaries 7700, 7740, 7741 DCUs XFMR4 Transformer, 120Vac Primary, 13.5Vac @ 2A and 24Vac @ 2A Secondaries 13.5Vac for baseplate mounted 7750, 7760, 78XX. 24Vac for 72XX UCs, 7716 XFMR5 Transformer, 240Vac Primary, 13.5Vac @ 2A and 24Vac @ 2A Secondaries 13.5Vac for baseplate mounted 7750, 7760, 78XX. 24Vac for 72XX UCs, 7716 XFMR6 Transformer, 120Vac Primary, 24Vac @ 2.4A Secondary 72XXUC, 7716, 7718, 7780, DPU3100, DPU7910A, DPU7920 XFMR7 Transformer, 240Vac Primary, 24Vac @ 2.4A Secondary 72XXUC, 7716, 7718, DPU3100, DPU7910A, DPU7920 XFMR8 Transformer, 120Vac Primary (plug-in), 13.5Vac Secondary (DIN connector) 7750, 7760, 78XX TAPs XFMR9 Transformer, 277Vac Primary, 24Vac @ 2.4Vac Secondary 7780 DLCU XFMR10 Transformer, 120Vac Primary, Dual 24Vac @ 2A Secondaries 7728 I/SITE I/O XFMR11 Transformer, 240Vac Primary, Dual 24Vac @ 2A Secondaries 7728 I/SITE I/O

Issue Expanding a system with a 7798B and unable to connect to other controllers. Product Line TAC INET Environment All versions of I/NET Cause There is no expansion card to connect the LAN Controllers together. Resolution The 7798B requires a CLX Expansion Card to be plugged into the slot to allow it to communicate to other controllers. The part number for this is LAN EXPANSION OPTION FOR RS-485, CLX. See Additional information on CLX LAN Expansion Option for RS-485 for more information on the CLX part. Take the device off the wall, unplug all wires including power. Insert the CLX card into the slot on board, be careful not bend any pins while doing this. Connect the wires again in their respective terminal with the LAN wire connecting to the CLX card, Sublan to those devices and power. Put the device back on the wall, set up accordingly and it should be communicating to the controllers now.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue 7798C stops communicating after BIN file download Is the 7798C supported in the older versions of I/NET Seven (1.14 and below). How to reset the 7798C hardware (i.e. place into boot mode) if no communication is possible with the 7798C    Product Line TAC I/NET Environment I/NET Seven 1.14 and lower I/SITE LAN 7798C Cause I/NET revision 1.14 and lower does not support 7798C and can mistakenly be assumed by the I/NET Host software as a 7798B.  If a software restore is completed to the 7798C with these revisions, it disables the device from communicating via the Controller LAN and disables any communication via the serial port with the Hand Held Console (HHC) software.   Resolution If you have downloaded the incorrect BIN file (i.e. 7798) to the 7798C, the handheld console software will not work, and hence, the device can not be placed back into a boot state, allowing the correct BIN file to be restored to the 7798C.  If the serial port is still configured/enabled for direct connection via the onboard TAP, this is the easiest solution to try a software restore to blank out 7798C with the correct BIN file. If either of these options are not available, the following steps can be performed very carefully directly on the hardware: Very Important:  Make sure you turn OFF the power to the 7798C unit. If you fail to remove power, this process could damage the board.  If unsure, please contact Product Support On the top edge of the board is the EPROM, and just below are two RAM chips. Between the EPROM and the two RAM chips are two mustard-colored capacitors (Labeled C2 & C3) If you short across each Capacitor, one at a time, this will take the device to boot. If you still have issues with the device, sending the 7798C in for repair is recommended. Once the device is communicating again, the correct firmware can be restored to the 7798C. At this point, you should be using I/NET Seven revision 1.17 or above.

Issue Steps to setup a NIC-IP for Vista Product Line TAC Vista Environment NIC-IP Cause Setting UP a NIC-IP Resolution 1. Download and install the latest NIC software. Here is a link to this site 2. Start the LConfig application. This is located in the LOYTEC Network Interfaces menu. 3. Select the NIC-IP/RNI tab. 4. Select the Assignment & Configure button. 5. The next popup screen will search for the NIC-IP. If your NIC-IP is powered up and plugged in to the network it should appear in this list. 6. Select the NIC-IP and then select the Configure button. 7. Setup the IP address, IP Netmask, IP Gateway and DNS servers if required. Select the OK and the device will write the new configuration to the NIC-IP 8. Take note of the Assignment and change if required. Press OK and the Assignment & Configure screen will close. 9 In the LConfig application select the Device from drop down list that matches the notes assignment from step 8. 10. Press the Test Device/Serial Number button to check for the correct setup of the NIC-IP. The return screen should look like this. 11.Close the LConfig application by selecting the OK button. 12. Start the Vista server and log into Vista workstation 13. Under the Vista server object add a new Device-communications Port - Loytec 14. Select the properties of the new Communication port and select the Network interface from the dropdown list. this should be the same interface noted in step 8. 15. You can the add Lonworks networks under the NIC-IP device.    If your NIC-IP does not appear in the dropdown list, Configuring Loytec NIC in Vista discusses this related issue.  

Issue Unable to Upload or display point data on an I/NET Controller in StruxureWare Workstation Environment I/NET to StruxureWare Integration Cause The most common cause for I/NET controllers to not integrate with StruxureWare are duplicate point names or illegal characters in use Resolution In Building Operation Workstation, right click on the errant I/NET controller and select "Upload" This is expected to fail at this point Browse to the Enterprise Server Directory as displayed in Building Operation Software Administrator Look in the db/Logs folder Locate the trace log and open it using a text editor scroll to the last line of the log and look for an entry that contains inet information. If the error is caused by duplicate point names, this will be the trace log entry: 2014-01-30 20:00:25.587 [6220] nsp.pin.inet.GetAllPoints InetPlugIn::ProcessChangeSetList failed RecoverableException: d:\dev\rb-int-v140-sp1-system\source\packages\commons\components\C3Po\nsp_servers\csc\changesetmanager\source\ChangeSetTransaction.cpp(987) Error: Object_Already_Exists (0x40006), module Runtime_Db_Manager(41), moduleCode 0, dispString "~/INET Interface/0321 - SBOtester/Point1", techString "" Note the text dispString "~/INET Interface/0321 - SBOtester/Point1", techString "" This indicates that there is a point on the controller named "Point1" which is causing the error Option 1: In I/NET workstation, connect to the controller Rename the point indicated above Perform a station save and attempt to upload the controller again. If it fails a second time, repeat steps 3-10 until you have removed all illegal entries Option 2: Use RdInet to view the Save file. Click on Save Page Open the .csv file in Excel and sort the data by Name Locate the Point indicated above and notice that there will be 2 objects of the same name. In I/NET identify these 2 points. Very likely, one will not actually exist. Copy the Point that exists to the address that was indicated as a duplicate in Excel Delete the newly created point to permanently remove the object from the .sav file. Perform a station save and attempt to upload the controller again. Repeat this process if necessary.

Issue When using the SmartStruxure Interface, is it necessary to configure any DCOM or firewall settings to run TAC Vista and SmartStruxure on different computers? What protocol is used for communication between the SmartStruxure interface for TAC Vista and the ES? Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista server TAC Vista SmartStruxure Interface SmartStruxure Enterprise Server (ES) Cause Communication issues between interface and SBO Resolution Only HTTP/HTTPS are used. You can configure the interface to use only one of the protocols. You can also configure what ports to use.

Issue How can the Niagarad service for Niagara G3 be started? Environment Niagarad service Niagara G3 Cause There are three different ways to start the Niagarad service manually. Resolution From the Windows Start menu: click Programs > Vykon AX Supervisor 3.x.x > Install Platform Daemon Open a DOS window and type - cd\Niagara\Niagara-3.x.x\bin then type plat.exe installdaemon Create a desktop shortcut with the following: C:\niagara\niagara-3.x.x\bin\plat.exe installdaemon

Issue Changes in I/NET Seven Rev 2.15 Video Product Line TAC INET Environment I/NET Seven Rev 2.15 Cause Video tutorial for Changes in I/NET Seven Rev 2.15 Resolution I/NET Seven Rev 2.15 has three changes: The number of individuals per tenant has been increased from 24,000 to 32,000 The maximum number of online records in AMT has been increased to 20 million A new editor has been added to host passwords that allows limiting operator permission based on groups These changes will be demonstrated and explained in this video.