Building Automation Knowledge Base

Issue When attempting to create OP Trees for Xenta controllers, some public signals in the application do not appear in the OP/32 Configuration Tool. Environment Xenta OP OP/32 Configuration Tool Cause While Menta allows you to use both uppercase and lowercase module names, the OP/32 Configuration Tool is case sensitive and can only use one version of a particular module name. For example, if you refer to Air Handler 1 as both "AH1" and "ah1" modules in an application, the OP Tool will only list the points from either the capitalized module or the lowercase module; never both. Resolution To correct this issue and make the missing points visible in the OP Tool: Close the OP Tool Standardize the module names to the same case format To change module names: Select one or more blocks with the mouse When they are highlighted in green, right click and click on "Module" Type in the new module name and then click "OK". Save the application Re-open the OP Tool

Issue Commissioning i.LON 600 Routers Environment i.LON 600 LonMaker 3 Cause i.LON 600 routers require backwards compatibility and a configured IP port. Resolution To commission an i.LON 600 in LonMaker 3 the user needs to make sure that the following are done. When creating the channel in the Echelon LONWORKS/IP Configuration server the channel mode selected should be "Backward Compatible" so that it can communicate with computer hosting the LNS Server. A device needs to be added to the channel that represents the computer hosting the LNS Server. It will share the same IP address as the channel, but utilize port 1628 rather then 1629.  

Issue How can I avoid getting an asterisk  (*) on all my devices when adding a controller to an existing TAC Xenta group in the system plug-in. Environment Vista System Plugin Cause When you do the "Update TAC network" after adding a new controller a group is created and when a new group is created all devices have to be downloaded. Resolution If you use the "Update TAC Network" command (or button) the controller is added to a new group. You can move the controller to the group you want it to be in, download to the controllers in that group and it will work, but now all your other controllers will have * next to them telling you that they need to be downloaded. To avoid this drag and drop the new controller directly into the group you want it to be in. Now only the controllers in that group have the * and needs to be downloaded.

Issue Ramp/Timer Calc Environment I/NET Seven Site Cause application that requires a calculation that will ramp up automatically or use a Timer Resolution Do you have an application that requires a calculation that will ramp up automatically or use a Timer? Take a look at these and see if it will fit: Ramp Scan Rate 10 = 600 sec Ramp Time LOW((L0+C0)*(L1>C0),C1) C0: 1 C1: 100 L0: Output from O/A Time Delay Output L1: Module Output Timer Scan Rate 60 seconds LOW((P0+C0)*(P1|(P0>=C0&P0 P0: Timer output P1: Timer start C0: Increment (1=1 minute increments) C1: High Limit (30=30 minute timer)

Issue Adding a Trend to a controller and an error comes up saying that the memory is full Environment I/NET Seven Site Cause memory full error when adding a Trend to a controller Resolution Follow these steps to trouble shoot and see if it will resolve itself. Check the memory on the PC and controller itself to see if the error is valid. Check the masking etc. on the points as well as the Trend Extension for the correct cell number. If you are still unable to add then please contact Product Support to receive a script that will allow you to add the Trend.  

Issue I/NET to DVR interface communications port Environment TCP/IP Cause A firewall may prevent communication between a PC and the DVR Resolution Integral DVR communicates on port 18772.

Issue Using Time Schedules in the Xenta 527 Environment Xenta 527 I/NET system I2V integration Cause Users should exercise caution when creating time schedule objects and pages in the Xenta 527. If a time schedule is created and directed at an I/NET point that already has a time schedule on the controller, the point value will be incorrect until the schedules synchronize. Due to the risk of improper results, possible harm to equipment in an HVAC environment, possible security breaches in a security environment, and the risk that if Ethernet communications fail the point will not operate according to the schedule it is recommended that time schedules in the 527 not be used with I/NET points. Resolution The I/NET time schedule object, which is created during the save file conversion in XBuilder, should be used . This object will direct you to a page that modifies the I/NET time schedule on the controller.  

Issue How can I give other users and SYSTEM the right to filter events in the Event viewer? Environment Vista Workstation Cause For a user to be able to filter events in the Event viewer it has to have at least authority level change (RWXD) on the $EVENTVIEW object. Resolution For more information on how to change authority on an object see Chapter 3 - Authority Levels for TAC Vista Workstation in the Administrating TAC Vista Workstation Manual.

Issue Digital Sentry Product Line with I/NET Seven 2.01 and future revisions. Environment I/NET site with Digital Sentry Cause Digital Sentry working with I/NET software Resolution The following Integral DVR products are compatible with I/NET Seven DS Enterprise - I/NET Seven 2.01 and above DS Enterprise SAVR - I/NET Seven 2.01 and above DS XPress - I/NET Seven 2.00 and above DS Enterprise Hardware –Distributed system –Redundant data hard drives for video storage –Redundant hard drives for operating system –Redundant power supplies –Uses XMUX2 units for video connections Software –Digital Sentry DS Enterprise SAVR Hardware –Single server –Redundant video data hard drives –Redundant operating system hard drives –Redundant power supplies –Uses XMUX2 units for video connections Software –Digital Sentry DS Xpress Stand Alone Hardware –Single server –Non-redundant power supply –Non-redundant operating system hard drives –Non-redundant internal video data hard drives –Optional external redundant video data hard drives Software –Digital Sentry

Issue When adding a third-party controller to a Vista database, some SNVT values are not present in Vista. The unit commissions and functions properly in Lonmaker, but certain valid SNVTs are left out of the Vista database, such as nvoSpaceTemp on the Trane device. Environment Trane LCI-R rooftop unit Smart Controls SmartStat ST-35F LonMaker Vista Workstation Cause Some information in the XIF did not transfer properly to the Vista database. Resolution Locate the correct .xif file for the device Browse to the device in Vista Right click and select Properties. On the XIF information tab, select the button next to the xif file name and browse in the original .xif file. Refreshing your page values should now reveal all the valid SNVTs in the device.

Issue There are two standard acronym video formats. What do PAL and NTSC stand for? Environment I/NET site Cause Answering the question of what do PAL and NTSC stands for. Resolution PAL This is short for Phase Alternating Line, the dominant television standard in Europe. The United States uses a different standard NTSC. Whereas NTSC delivers 525 lines of resolution at 60 half-frames per second, PAL delivers 625 lines at 50 half frames per second. Many Video adapters that enable computer monitors to be used as television screens support both NTSC and PAL signals. NTSC This is short for National Television System Committee. The NTSC is responsible for setting television and video standards in the United States (in Europe and the rest of the world, the dominant television standards are PAL and SECAM). The NTSC standard for television defines a composite video signal with a refresh rate of 60 half-frames (interlaced) per second. Each line contains 525 lines and can contain 16 million different colors. The NTSC standard is incompatible with most computer video standards, which generally use RGB video signals. However, you can insert special video adapters into your computer that convert NTSC signals into computer video signals and vice versa.

Issue Using Lonmaker to replicate settings in a specific function block from one Lonworks unit to others of the same type Environment LonMaker LON Devices Cause It is very time-consuming to configure VAV controllers and other Lonworks units in large systems. Fortunately, it is possible to configure the settings in one controller and then replicate those settings to all of the other controllers. This can be accomplished by using "ResynchCPs" but that applies to all settings in a controller. Using this function can replicate the settings in only one function block. For example, maybe you want to change all of the temperature setpoints and heating configuration but not the duct area and other airflow settings. Resolution First, make sure that each controller in the Lonmaker drawing has a functional block of the same type, e.g. "VAV Controller." To quickly create multiple functional blocks, drop a functional block onto the drawing; in the dialog box, give the FB a name, and where it says "Number of FBs to Create," enter the number of VAV controllers in the subsystem. Use the plug-in or browser to configure the parameters in one of the controllers. Make sure the parameters get downloaded to the controller. Next, right-click on the functional block for that controller and select "Replicate Settings." Select the parameters that you want to copy and then click Next. Under "Target Subsystems," select the subsystems that contain the same type of controllers. Under "Target FB Selection" select "Matching FB Type", then click Next. It will show you a list of qualifying targets, including the current value and new value of the parameters. Highlight any settings you don't want to be changed and select remove. Click Finish to replicate the settings

Issue Can not open LonMaker database Error window pops up saying "Invalid parameters - LNS error #44" When you click on OK it pops up another window asking you to either attach or detach the network. Once this is done, it comes up with an NSS assigned error. Environment Windows 2003 server, with SP1 installed. Cause If you have Windows Terminal Server installed (used for remote desktop connections to the server) then LonMaker does not work. Resolution Fully uninstall Windows Terminal Server (you don't need the CD for this operation) and reboot. You can not just turn the service off in Windows, this has no effect at all.

Issue Access specific variables in the Xenta 511/527 via HTML. Product Line TAC Vista Environment Xenta 511 Xenta 527 HTML Cause View certain values inside the 511 without accessing a graphic page within the device. Resolution Individual variables can be accessed using HTML addresses in a 511/527 if you use the following address: https://x.x.x.x/sys/varaccess?Variable&UID=root,PW=root Where: x.x.x.x = IP address of the unit Variable = name of the variable being referenced UID = User Id PW = Password If you are already logged into the 511/527 or wish to use the address in a link page then leave off the &UID=x,PW=y part. In order to identify the name of the variables available, consult the SB_ProjectTree.gz which is a compressed XML file containing the project. It is located in the TargetImage\ConfigDb subdirectory of your project directory. Use the value field in the XML section for the signal you wish to reference. NOTE: This can not be done with a 527-NPR since it does not contain any of this information

Issue Getting an IDisc Wand to work after an upgrade from I/NET 2.XX to I/NET Seven Environment I/NET Seven IDisc Cause Getting an IDisc Wand to work after an upgrade from I/NET 2.XX to I/NET Seven Resolution Go to I/O Server and look at the Peripherals Section, Select the correct type of reader (IDisc) and the COM Port (Com 1 or 2) for communications. Go to Access, Options, select the supply card number from reader and check this box. It will probably be grayed out. Read a card or IDisc and see what happens. If it is set up correctly it will work, if not recheck the settings. Verify that the Individual Option is set for Individual as the selection.

Issue Sub-Lan Interface (SLI) Not Available. Environment I/NET site with SLI Cause Controller is not available to translate a big card number when it has been read at a card reader. . Resolution If you are using Access control and wondered what "SLI Not available" means or how it should be used when setting up Messages on the Door Point, the following description should clear up any misconceptions about it. "SLI Not Available" means that the controller is not available to translate a big card number when it has been read at a card reader. This can be set up as a Transaction or an Alarm. A Transaction will be displayed in the Transaction Window whenever this occurs. An Alarm will be generated if this is selected but it has to match the settings that are selected for the various Alarm type and distribution masks.

Issue Have you had an issue connecting to your system on a Direct Connect with a PC that has Palm Pilot Software installed and get an Error that you cannot connect to the specified device? Environment I/NET Seven I/O Server Palm Pilot Software Cause I/NET talks on Com Port 1 to the system. A sync can be done before starting I/NET or after shutting it down, but they cannot run concurrent with each other because they are using the same port. Resolution The following steps will allow the user to get past this issue: Close all programs including I/NET and I/O Server. Go to Start > Programs > Palm and select Hot Sync. Unselect Always running. Select only when HHC is on the cradle. Start I/NET again and try connecting to the controller.

Issue Will the type of SNVT binding affect the controller address table? Environment Vista LNS Network LonMaker NL-220 Cause Different types of SNVT bindings affect the entries made in the address tables of the sending and / or receiving devices. Resolution One to One Bindings The binding type (Acknowledged, Unacknowledged, or Repeated) has no effect on the address table entries. Instead the determining factor are the send and poll flags. The sending state on SNVT outputs causes the SNVT to update the signal it is bound to. The polling state on a SNVT input causes the SNVT to poll for values on a regular basis. The effect these signal flags have on the address tables are detailed below: Any one to one binding Sender Receiver   Poll No Poll Send Both Sender Only No Send Receiver Only Unbindable Group Bindings When creating group bindings the type of binding (Acknowledged, Unacknowledged, or Repeated) and the signal flags (Poll/Send) complicate the table greatly. However in situations where direct control of these signal flags is possible the effects on the address table is very simple. A group binding where the output is a Send signal and the inputs are Not Poll then one address table slot will be consumed by all members of the group (Both sender and receiver). This scenario is the default settings for inputs and outputs for SNVTs created by Menta. If the equipment being used is not configurable then the address table entries can become full very fast. Care should be taken if group bindings are used and it does not match the Send & No Poll defaults.

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