Building Automation Knowledge Base

Issue How to service pin a Loytec L-IP. Environment Loytec L-IP Cause Commission a Loytec L-IP into a LNS network. Resolution The Loytec L-IP can be service pinned in one of two ways: If you have direct access to the router, press the status button to initiate a service pin. If you do not have direct access to the router, connect to the router via Ethernet to initiate a service pin. By entering the IP address of the router in a web browser you will reach the L-IP Device Info which has a button to send a service pin message.

Issue Re-using symbols library in Vista Environment TAC Vista IV OGC Graphics Editor Cause You can re-use your symbol library that you created in a Vista data base to avoid having to recreate symbols every time you start a new Vista db. After adding or editing symbols in the graphic editor, your changes are stored in the $tmp folder in your db as $symbol.sym. You can use this file or use the database generator to export the $Symbol file to your $wrk folder. Resolution To use a saved .SYM file Find the $symbol object in you database (in workstation) Right click and select properties. Click on the last line, a browse button should appear. Click on the browse button and browse in the saved .SYM file

Issue TAC Vista server keeps restarting itself. How can I make it stop? Environment TAC Vista 5.1.X Possibly remote Workstation Cause Incorrect DCOM settings Resolution This happens because the DSS writerservice that transfers log data to the SQL database uses DCOM to call TACOS (Vista server) and if TACOS is not running it will start it up. That�s why it starts over and over again. Here is the solution: - Start Component Services, either from the Start menu, or via Start -> Run... -> dcomcnfg. - Double-click the Component Services node in the tree on the left-hand side. - Expand the My Computer node, and click the DCOM Config folder. - Locate the TACOS package in the right-hand view. - Right-click and click Properties. - Switch to the Security tab. - Edit Launch and Activation permissions. If Use Default is selected, switch to Customize, and press Edit. - Make sure no one has Remote Launch.

Issue Attempts to connect to an MR-VAV-AX and make a change has no effect. Looking at the MCU Configuration, the address shows to be communicating, but the Communications show a lot of bad CRCs or No Reply.  Environment I/NET site Cause Variety of causes, check below to troubleshoot. Resolution There are a couple of things that you need to look at: Verify that the controller has a proper power supply and it is grounded properly. Verify that it is communicating to the MRI properly and there are no shorts or anything on the Sub-LAN wire. After checking these, go back to the MCU Configuration and look at the comm. Stats again, if these are still showing bad CRC’s or No Reply then the unit (MR-VAV) itself may be bad and would have to be replaced.

Issue Convert Key Card Translation table to a Large Number and then remove the Key Card Table entry from I/NET. Product Line TAC INET Environment I/NET site with Access Control Cause The process described will allow you to do this conversion on an active system without causing the Idisc to fail during process. Resolution For example take the Key card translation table below: With this Individual editor: Make an excel spread sheet that performs this calculation multiple times, or you can do it one at a time manually. The information needed for this calculation is located in the Key Card Table and Individuals editor. Source Number (from Key card table) Individual Number (from Individual editor) Target Number (from Key card table) Decimal Number (from Individual Editor) Source Number + Individual Number - Target Number = Decimal Number Source Number Individual Number Target Number Decimal Number 67806444 00001 1 67806444 67806444 00002 1 67806445 67806444 00003 1 67806446 67806444 00004 1 67806447 67806444 00005 1 67806448   Go into the Individual editor and modify an individual entry Take the calculated decimal number from the calculation above and add it into the Decimal Number area. The I/NET program will calculate the Hex number automatically. This Hex number should be the same as the bottom of the Idisc itself. Note: ONLY delete the Key table lines after you completed the entire tenant conversion. This will insure that all people will get into and out of the building. Note: These changes can be done on an active system. This is the process of adding NEW people in the system that has existing Key Card Translation table and you want to enter the NEW Disk as large numbers. Go into the access Individuals editor and Add a new person. It is not permitted to back-fill any existing Individual Numbers. In the example above Individuals 00001, 00003, and 00004 are defined. It is not possible to add Individual 00002. Go to the end of the Individuals list and choose the last number + 1 number. Set the Individual Number then place the cursor on the middle box and touch the new disc to the wand. This will place the Hex number in that box from the Idisc. The Hex number and Decimal number are listed in the Individual Parameters. Complete the process by filling out the rest of the Individuals editor.

Issue MSDE and the install of I/NET Seven and Vista 4.3.1 version software. Environment Single computer with both I/NET Seven and Vista software. Cause MSDE and instance Resolution MSDE does not allow an unnamed instance to overwrite a named instance of MSDE. I/NET Seven MSDE installs at this time an "Un-Named" instance. Vista 4.3.1 installs a "Named" instance. The work around: Install I/NET Seven first then install Vista 4.3.1. This will be corrected in future release of I/NET Seven.

Issue AMT is Displaying Link 200 and a partial point address. Environment I/NET site Cause Error Message AMT is Displaying Link 200 and a partial point address Resolution AMT can report a LINK 200 + a partial point address. When this occurs the system has defaulted to an error handling code to let the system programmer know that there is a hardware addressing conflict in a direct connect system. To correct this; open active profile in the I/NET configuration editor and modify the link configuration editor. The error generally occurs when the host hardware address is different then the actual hardware address. For example: 7801 Tap is addressed "0" and the Host hardware address is something other than "0". When connecting to a Host/Link/Lan tap (either a 78010 that connect directly to the controller lan or an emulated 78010 on a controller), the hardware address is always 0 and cannot be any different. Please read TAP and Repeater TCON 101 for a more detailed explanation on configuration parameters.

Issue 'Program interface does not match previously defined interface' when downloading/commissioning a Xenta 400/300 controller. NS, #59 Environment Vista System Plugin TAC Xenta Programmable Controllers LonMaker/NL220 Cause You get this error if you have 2 controllers that are using the same device template (XIF file) and one is system program version <3.5 and one is >3.5. Typically you will get this when you are replacing an older controller or adding a new controller to an older network. Controllers can share device template even if they have different applications as long as the are using the same SNVTs. Different types of Xenta controllers can also share the same XIF file. Resolution To fix the problem you have to make sure that the new controller you are adding (replacing) gets a new XIF file and it’s own template. Open the application form System plug-in by right clicking on controller and select configure-edit. To give the application a new XIF either add a “dummy” SNVT or go to device configuration and uncheck the tick box for “XIF header generated according to LonMark standard” Hit F12, select commands and generate. F12 again and save the application to the hard drive by selecting File-save as. In system plug-in, browse in the application that you just saved on the hard drive. Update TAC Network and TAC Database. If you are asked to resynchronize, do so. In Menta create a new application with just one PVR block in it. Go to the controller, connect a serial cable and download the small application that you just created. Go back to the system plug-in and download the controller. Commission in LonMaker.

Issue LonMaker restore backup error message: "The operation failed because access was denied to the target drive or directory. Please verify that you have write access" Environment LonMaker Cause This will happen if the TAC Vista server is running and already using the database. Resolution Close TAC Vista server and try again. If that doesn't work, make sure that you have full write access to the folder you are restoring to and that you are an administrator on the PC.

Issue One of the properties for the LON object in the 511 is 'Use subnet node addressing' what does this do? Environment Xenta 511 LTA LON Network Cause If you import a LNS network into XBuilder and are going to use polled values from a LonWorks devices, you can choose if the Xenta 511 is going to use subnet/node or neuron ID to address the current LonWorks devices. Resolution The advantage to using subnet/node addressing is that importing the LNS network into XBuilder again if node is replaced in the LNS network is not necessary, provided that the node keeps the same subnet/node and the same application.  

Issue Order of Operations for Creating a New Detail in ProjectBuilder 2 Environment I/NET or Vista site Cause Desire for a Order of Operations for Creating a New Detail in ProjectBuilder 2 Resolution Drag and drop a blank Placeholder onto the page from the TAC Device or TAC Wiring Details stencil. Create the detail drawing on the paper space in Visio. Make sure the drawing is the appropriate size to fit in the blank Placeholder. Select all of the detail drawing and copy it to the clipboard. Select the blank Placeholder that has been dropped on the paper space in Visio. Select Open Placeholder from the Visio Edit Menu. After the blank Placeholder has been opened, select Paste Special from the Visio Edit Menu. While in the Paste Special window, select Picture (Enhanced Metafile) and select OK Position the detail drawing in the Placeholder. Close the group window. Once back in the Visio window, RMA on the new Detail and select Edit Detail Info. Enter the Detail Name in the Name field and the Detail Description (Manufacturer) in the Description field, select OK. RMA on the new Detail and select Format/Special. Change the Name field from “Placeholder” to the exact Detail Name used two steps earlier. RMA on the new Detail and select Shape/Custom Properties. This drop down box should be blank. Select the type of shape from the list that this detail can be associated to. It might be necessary to change this property during the course of the drawing to be able to associate the detail to more than one kind of shape. Select OK. If you wish to save this detail, put a stencil into the edit mode by left clicking on the stencil icon in the top left hand corner of the stencil window and choosing edit. Copy the new detail and paste it into the stencil in edit mode. In the stencil set, RMA on the new detail and select Master Properties. In the Name field, enter the same name as you did for Detail Name earlier. In the Prompt field, on the first line put the Manufacturer and on the second line put the Detail Description used earlier. Take the stencil out of the edit mode by left clicking on the stencil icon in the top left hand corner of the stencil window and choosing edit. When prompted whether or not to save changes, click yes.

Issue Is there a way that I can present date and time of the TAC Vista server and TAC Xenta controllers on a graphic page in TAC Vista? Environment Vista IV OGC Graphics Cause Display the PC's current time (which should also be the Vista Server's current time) on a customer's graphics page. Resolution Choose a digital presentation in the graphic editor. Browse in the server object or the controller that you want the local time from. Choose the attribute Local time and mark presentation format.

Issue Xenta 5/7/9xx locks up during boot up sequence. Plugged into the service terminal (RS-232-B) during the boot up sequence, it can be observed that it stops processing on the "InstallDrivers" command. In some situations the error log produces the 49154 error code. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause In some situations the error log produces the 49154 error code. If the Xenta 511/527/913 is not booting correctly and stops processing on the "InstallDrivers" command, visible via a Hyperterminal connection, the cause typically is that the Xenta controller is underpowered. Resolution The Xenta controller can survive some drop in power after the initial boot up sequence, but it vulnerable to an insufficient power supply during the boot up sequence. To avoid this problem simply provide the Xenta controller with a stable power within the documented range. The 49154 error code is typically an issue with the power coming to the Xenta, the transformer or something, and a smaller chance of a short from the LAN which is causing this power instability. Mark said they can recycle the power, the Xenta comes back and works for a bit, then the same error. Check the transformer, then with a replacement Xenta in hand, upgrade firmware if possible. If not able, replace Xenta and if not to expensive, replace transformer at same time. 

Issue If you are using OPC Server for I/NET on a computer with Windows XP with SP2 you may have some difficulty connecting to the OPC Server from another computer. Environment OPC Server for I/NET Windows XP SP2 Cause Incorrect DCOM settings will prevent a connection from another PC. Resolution Start > Run > dcomcnfg Right click My Computer found under Component Services, Computers. Click on the COM Security tab. Click the Edit Limits on the Launch and Activation permissions. Add ANONYMOUS LOGON with remote launch and remote activation permissions.  

Issue STR-350 will not send a service pin message. Environment STR-350 LNS Database Cause If the STR-350 has been commissioned previously then deleted from the LonMaker database it will not send out a service pin message until taking the steps below. Resolution Manually enter the Neuron ID of the STR-350 and commission it into the network. This will restore the service pin functionality.

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 Can not browse graphic objects in the OGC Graphics Editor. Environment TAC Vista IV OGC Graphics Editor Cause If the Vista Server is not launched prior to opening the Graphics Editor from the TAC Tools in the Start menu, the editor will close on an attempt to browse an object into one of the graphic objects on the page. Resolution Always launch the graphic editor from Vista Workstation. If you must work on graphic pages offline, just remember not to hit the browse button.

Issue Loaded I/NET Seven revision 2.10 for the first time on a PC and reports come up with an error that "Server has not yet been opened" Environment I/NET site Cause Loaded I/NET Seven revision 2.10 for the first time on a PC and reports come up with an error that "Server has not yet been opened" Resolution There are a couple of items that needs to be checked to get this working again and there is a workaround to it as well. First, check these items: Verify that TCP/IP is checked in the Active profile in I/O Server Configuration. Using Windows Explorer, open C/Program Files/MSSQL Server/80/Tools/Binn/SVRNETCN.exe, double click and verify that the TCP/IP is listed in the Named Pipes in the Enabled Protocols window. If it is not, then please enable it by selecting the Enable button; this moves it over to the other column. Now restart I/Net and try the reports again, they should be working now. The work around to this is to install an older version of I/NET, version 2.01 or 2.02 first on the PC and then upgrade to 2.10. Do remember that you would have to Un-install/Re-install MSDE again. When prompted to upgrade to Service Pack 4, select the Yes Option. Once this is done and the upgrade is complete, start I/NET and try running Seven Reports again.

Issue Upgraded to 4.4.0 but don't see the SCPTs on a LonWorks Unit yet? Environment Vista 4.4.0 Lonworks units Cause When you upgrade your Vista database, it doesn't automatically create new database objects.  Resolution From Vista Workstation, navigate to a LonWorks unit Right click and select Properties. Click on the "Xif file" tab Click on the browse button (the one next to the "source file" field with 2 dots on it). Browse to the xif file for that unit, e.g. C:\lonworks\import\tac\x100\102AX101.XIF for an Xenta 102-AX Click "Open" then "OK" When you refresh that unit in the tree, you'll see the available objects/function blocks for that unit and they will contain most of the SNVTs, SCPTs and UCPTs in them. Some of them will not show up, e.g. ucpt_vavselection in the 102-AX.

Issue Generating an XIF in XBuilder for a Xenta 5/7/9xx device.  Where is the XIF file located? Environment XBuilder Cause If you right click on the root object of the network pane of XBuilder (on the Xenta 5/7/9xx object) and choose "Generate XIF File," a window pops up that says "XIF File generated."  But it doesn't tell you where it put it. Resolution Find the XIF in \\your project\Target image\configdb\lon.   The file is named TAC_XENTA_527.xif (for example) Check the time stamp on the file to double check that it is the correct one that was just generated.