Building Automation Knowledge Base

Issue How much ethernet bandwidth do lonworks systems consume using Loytec L-IPs, iLons, etc.? Environment TCP/IP ethernet network LNS System Cause IT professionals will sometimes hesitate to allow the control system to use the same TCP/IP network as the internet, phones, etc. They may ask what the expected bandwidth usage will be before granting access. Resolution It is impossible to explicitly state how much bandwidth a LonWorks system will consume on the ethernet. It depends heavily on the amount of LON traffic being sent by the controllers. The routers themselves do not produce traffic, they only pass the traffic onto and off of the ethernet. The traffic is created by the LON devices, Xenta controllers, Vista and LonMaker or other HMIs. Vista can create a maximum of 15 LON telegrams/second. This is very little traffic with respect to IP bandwidth. Unless you have made bindings into the LNS NI (which we never do in a Vista-scenario, since Vista cannot read these) there is basically nothing at all going out from LonMaker/LNS unless you are commissioning devices. Starting the LonMaker Browser also generates traffic. But this is also normally just in the design phase of the network, not in "operating mode". SNVT bindings or TAC network variables from one LON network to another over the IP channel also generate traffic. A typical Xenta can produce 2 SNVTs propagation/second and/or maybe 10 TACNV. This is not much (as IP-traffic), but if there are hundreds of nodes communicating simultaneously all passing through L-IP gateways, the amount of IP traffic will grow. If you are using a Loytec L-IP, it uses a protocol feature called "packet bunching". Before it sends out a packet on the IP side, it waits for an adjustable time (Aggregation Time, default = 16ms) if some packets are following, which have to be sent to the same IP addresses. If some packets are following, it puts the packets in the same IP frame and sends it all together in a single IP packet. The receiving node unpacks it and makes multiple EIA-709 (Lonworks) packets again.

Issue The Lonworks Network has been moved under the LNS Port and no longer resides directly under the Vista Server in the tree structure as it was in previous versions.  This will add a level in the binding path and the old paths are no longer valid. This will impact any binding paths to objects on the root level of the System Tree.  Product Line TAC Vista Environment Upgrade Vista from versions older than 4.5 to newer versions OGC Graphic bindings Trend Log bindings Cause Versions of Vista < 4.5 had the Lonworks Network connected directly to the Vista Server in the workstation tree structure. A revision to this tree structure was made in all versions of vista > or = 4.5. After an upgrade from an earlier version to 4.5 the Lonworks Network is under the LNS port and is no longer connected directly under the Vista Server. This will add a step to the path in your graphic bindings that must be corrected in the OGC Graphic Editor. Example: OLD Binding Path: VistaServer_LonWorksGroup_ControllerName_Point NEW Binding Path: VistaServer_LNSPort_LonWorksGroup_ControllerName_Point Resolution You will need to edit the binding path of graphics at the root level of the System Tree. Follow the steps below to repair the bindings: Right click on the folder that contains the graphics that need to be altered in Vista Workstation (This same procedure can be performed on individual graphics as well instead of an entire folder). Select "Change References". Click Search in the Change references window. This will display all references that are contained in this folder. Select all references (Alt A) in the window and click Replace. Type the OLD path into the "Find what" field (example:VistaServer_LonWorksGroup). Type the NEW path into the "Replace with" (example:VistaServer_LNSPort_LonWorksGroup). Click OK. Verify that the reference path in the New column is correct and then click Save. This will repair all of the bindings in this folder.  You will need to repeat these steps for all folders containing items that reference points below the LNSPort . Note: Correcting this path will fix the graphics bindings in all future releases of Vista.

Issue When updating the Vista Database the update fails when trying to transfer a specific MTA object. Product Line TAC Vista Environment Vista System Plugin Cause Errors in the specific Menta file that is being transferred cause the entire Vista Database update process to fail and error out. Resolution Open the Menta file that caused the update to fail and check the following: Click Options > Constants Table ... and verify that the names of all of the constants are no longer than 18 characters. Make sure there are no unnecessary or orphaned constants present in the MTA file. If there are any orphaned or unnecessary constants in the constants table the Delete Unused Constants will be clickable. If not, the button will be grayed out. Clicking Delete Unused Constants will remove the unnecessary or orphaned constants.   Make sure there are no corrupted / orphaned trend logs, as well. You should be able to identify these by generating the project and an error will be returned like the one below. Delete these trend logs. After making these changes to the Menta file either save it directly to the Vista database or save it to the computer then browse it in from the System Plugin. The Vista Database should now update successfully.

Issue Upgrading to I/NET Rev 2.13 steps to follow if changing to Server/Remote Client configuration Environment I/NET site with release prior to 2.13 Cause Help with upgrade to 2.13 Resolution Rev 2.13 Introduces a Server/Client option for I/NET Seven. The following steps should be taken if the upgrade is to change from a Filemaster with Equalized Clients to the new Server/Remote Client Configuration. Otherwise the normal upgrade procedure should be used. Note there are new DCU binary files as well as new DPU48k and SCU1284 binary files in this release. The DCU files introduce the Reliable messaging capability and the DPU48k and SCU1284 binaries introduce the door code control option. Open I/NET Config on each Equalized Client Host and drop the equalization. Open Host Masking on each Equalized Client and Clear all masks on all Links. Open I/NET Config on the Filemaster and make sure all Clients have been dropped. Open Host Masking on the Filemaster and make sure masks have been set to receive messages and trends from all hosts and NPRs on the network. Open Network Configuration on the Filemaster and make the Filemaster the Restore Host for all Links. Stop I/NET on all hosts. Start DbCreate on the Filemaster and make a backup. Install I/NET Seven Rev 2.13 on all hosts. Configure one host (Filemaster most likely) to be the Standalone Host which will act as the Server. Configure the remaining hosts to be Remote Clients pointing to the Standalone host. If ID Works was installed on an Equalized Client pc, use Administrative Tools on that pc to configure the System DNS Seven ODBC to connect to the SQL Server on the I/NET Seven Server pc. If there were Seven Trend definitions only on an Equalized Client, they must be created on the Server after the upgrade since Trends are no longer saved on the Remote Clients. Make sure the message and trend archiving is configured as desired on the Server since archives are no longer saved on the Remote Clients. If there were any Network Functions specified only on an Equalized Client they must be created on the Server since the Remote Clients no longer perform Network Functions.

Issue Schlage step by step configuration. Environment Windows Xp, 7,  2008, 2008R2 Continuum 1.94 Cause Single Door set Up examples. Resolution Schlage Door setup examples attached.   Download here

Issue One folder, on a jobsite computer, contains all the DMS backups done over the past several years.  Since each backup contains multiple files, how can the files be identified and then grouped together for easy retrieval in the future? Environment DMS35, DMS350A, and DMS3500 (revisions 9, 10, and 11) Cause Multiple DMS backups were performed from the same jobsite computer. They were not grouped by name or date. All the backup files exist in one folder in a disorganized state. Resolution The files created from a database 'save' for a DMS35 or DMS3500 are: filename.IOC (stores DMS point IDs, records, alarm parameters) filename.UC (stores DMS point configuration elements) filename.PG (stores DMS tables and schedules) filename.UDP (stores UDPs in the DMS panel) The files created from a database 'save' for a DMS350A include the four listed above as well as: filename.Dxx (stores DCM tables, schedules, and other elements) filename.Uxx (stores DCM UDPs) where xx = DCM address 01-32

Issue Can the existing communication wiring from a NETWORK 8000 (ASD) or DMS (Microsmart) project be re-used for a BACnet MS/TP trunk? Environment NETWORK 8000 (ASD) cable DMS (MicroSmart) cable BACnet MS/TP Cause Using ASD cable become an issue as baud rates increases pass the range of 9600 or 19.2 k. Resolution Testing has shown that existing communication wiring of a NETWORK 8000 (ASD)or DMS (MicroSmart) system is compatible at a speed setting of 9600 baud.  It is unlikely that this wire will work at higher baud rates or at extended distances.  Communications will be limited to the slower baud rates (9600 or 19200 baud) on these systems.

Issue Use L-IP and NL220 to compose Vista LNS database. How to move the database from the engineering PC to the site PC? Environment Vista 5.X.X LNS Network NL220 Loytec L-IP Cause Due to the complexity of LNS network, it is recommended to follow the steps listed below to move the LNS database and Vista database from an engineering PC to a site PC. Otherwise, it may result controllers offline, Vista database opens extremely slow or freeze. Resolution NL220+L-IP is the most common combination for LNS network. How to move the database completed on the engineering PC to the site PC? The following steps can be followed: The software needed to be installed on site PC: Vista Server, Vista ToolPack, NL220.   A NL220 dongle is needed.  (The dongle does not need to be locked to the site PC for moving database purpose; however, it is recommended to have the dongle locked to the site PC for future maintenance purpose.)   Backup the LNS database on the engineering PC. (Select “Backup Project” in the NL220.)   Make a copy of Vista database.   Copy both backups (LNS and Vista) onto the site PC. NOTE: It is recommended to keep the paths of both databases the same. Otherwise, it may results graphic pages lost.   Specify the folder path of Vista Server on site PC to the backup database.   Add the L-IP interface in the Control Panel.   Plug the NL220 dongle onto the site PC. Open NL220, create a new project and select the interface as L-IP.   Close the project, select “Restore Project” and specify it to the backup database for NL220.   Open the NL220 project again and select the System Plug-in.   Update the LNS database to Vista Server in the System plug-in again.   Select the “Commence Communication” to start the communication.   Open TAC Vista Workstation. Then the LNS interface in the Workstation should be online. NOTE: without a NL220 dongle plugged in the site PC, TAC Vista workstation should operate normally. However, it is impossible to make any change to the LNS database.

Issue How to automatically disable access for Personnel who's expiry date has passed? Environment Continuum Access Control Cause Want to automatically disable Personnel who's cards have gone beyond the expiry date. Resolution The below code sample can be used as a basis to provide this feature. It is a fallthru Workstation Program that can be triggered from one of the time related SystemVariables such as Hour or Minute. It uses the OpenList function to go through all Personnel in a specific folder and compare their expiry dates to the current Date and then disables them if required.   ========================================== 'Fall thru program that will search through the Personnel class for ' an expiration date that is less than today’s date. Object oAPerson Numeric nResult Line 1   nResult = OpenList("Personnel", oAPerson, Root\CardHolders) 'specify CH path Line 2   If nResult = Success then     While GetObject(oAPerson) = Success       'The next line will fail when the Expiration Date attribute is greater than 12/31/2037 (12/31/2099, by default)       If (Date > oAPerson ExpirationDate) then         Set oAPerson State = Disabled       Else         Set oAPerson State = Enabled       Endif     Print oAPerson Name, " is ", oAPerson State 'prints to message window for testing     Endwhile   Endif ==========================================

Issue The icon in device administrator used to launch the PuTTY console is no longer on the toolbar. Environment Device Administrator Cause Starting in SmartStruxure version 1.4, the PuTTY console is no longer used to change the IP settings of the automation server. Resolution In order to change the IP settings of an automation server, follow these steps below. Add the automation server into the Device Administrator. Select the controller and go to the View menu > Network settings. You can also right click on the controller and click "Network settings". In the Properties window under the Network tab, all of the IP settings can be entered for the automation server. You can still access the PuTTY console by holding down the shift key and right clicking on the automation server. You will have the option to open 'Console'.

Issue Unable to find Schlage Xdriver file on Exchange Download Center. Product Line Continuum Environment Xdriver add-on Cause It is unclear of where to download the Schlage Xdriver for Continuum.  Resolution All Schlage Xdriver .xdr files, as well as their accompanying documentation, can be found in the Schlage Wireless Lock Resources Kit on the Schneider Electric Exchange Download Center.

Issue I/NET Seven does not support the 7791/7792 MCI platforms. Only the 7793 MCI platform is supported. Consequently, a conversion from the 7791/7792 MCI platforms to the 7793 MCI platform is necessary. The following steps should insure a correct conversion. Environment 7791/7792 MCI platforms Cause I/NET Seven does not support the 7791/7792 MCI platforms. Only the 7793 MCI platform is supported. Resolution A Hand Held Console (HHC) is required for this process. Turn EVERY sub-LAN device “Internal” using the MCU Configuration Editor under Edit > Controller > MCU Configuration. Save the current databases in the MCIs (7791/7792). Attach the Hand Held Console (HHC) to a MCI. Use the following keystrokes to clear the MCI memory: CTRL, MEM, ENTER, “0”, ENTER. Press the red RESET button on the MCI The indication on the HHC should be seconds counting up from zero. Using the HHC, enter CODE, 90, and press the ENTER key.  The display should show the current MCI configuration (i.e., 7791 or 7792 and TAP emulation of 01, 03 or 06).  Using the increment/decrement keys advance the display to show 779301 or 779306 (use the –06 if dialing into a MCI with the RS-232 Expansion board attached--otherwise use the -01) and press the ENTER key.  The display should indicate seconds counting up from zero.  Check the COMM port speed on the MCI using the HHC.  Enter in CODE, 91, and press the ENTER key.  The display will show the COMM port speed, typically 19,200 if directly connected to a PC.  Change the port speed using the INC key to 19200 if necessary. Move the I/NET 2000 saved databases (DCUXXXX.sav) to the SAV folder in I/NET Seven. In I/NET Seven connect to the Link address where the MCI is located.  Go to Edit > Host Computer > Software Restore, and check the MCI address to download the .BIN file only (do not load the .SAV file here).  After the .BIN file downloads to the 7793, connect to the MCI.  Go to Edit > Controller > Station Restore, and download the .SAV file to the controller.

Issue How can a remote BACnet/IP network be accessed using the WorkPlace Commissioning Tool (WPCT)? Environment BACnet/IP network WorkPlace Commissioning Tool (WPCT) Cause Remote connectivity is needed to access a BACnet device that exists on an outside network where WPCT resides. Resolution When WPCT starts, it sends out a "whoIs" (broadcast) message. The responding devices send the reply ("iAm") using its IP address. If the responding device is on a private IP network that is using NAT or Port Forwarding to access the Internet, it is this private IP address that is populated in the "iAm" response. After the response, WPCT starts using directed messages using the address it received from the responding device. Private IP addresses cannot be routed through the public Internet. Therefore, NAT or Port Forwarding cannot be used to access remote BACnet/IP networks using WPCT. There are two ways around this issue: Use a public IP address in the internal BACnet network Use a VPN to access the network For more details, consult the I/A Series Micronet BACnet Wiring, Networking, and Best Practices Guide (F-27360).

Issue MB30A or MB30B have been discontinued. Need find new serial butterfly valve actuator could work with TRV-S. Environment Butterfly Valve / Actuator Cause MB30A and MB30B have been discontinued. Resolution - New serial actuator, MF20-R and MF40-R, could work with butterfly valve TRV-S. No linkage needed. - MF20-R could work with up to DN125 size TRV-S butterfly valve; - MF40-R could work with DN150 and DN200 size TRV-S butterfly valve. - For detail, please see datasheet.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue Exporting data from a corrupt taclogdata database because it's no longer possible for Vista to log data to the database. Product Line TAC Vista Environment Tac Vista 5.1.X SQL 2005 or newer SQL Management Studio Cause The original database is corrupt, there are no backups available and Vista is unable to write to the database. Resolution If not already installed, download and install SQL server management studio. Use a search engine to search for the appropriate version for your installation. Once installed, log on to your database instance (localhost\TACVISTA by default) and locate/select the taclogdata database in the Object explorer. Then follow the steps below: BACKUP! BACKUP! BACKUP! before starting this procedure! Create a new clean DB via Vista server setup - don't start Vista. Right click on the source DB in SQL management studio and select Tasks->Export Data. Follow the wizard and select the source and destination DBs. When you get to the "Select Source Tables and Views" stage, select the tables you want to copy. For each table selected, select the table and click on the "Edit Mappings" button. In the dialogue that appears, select "Append rows to the destination table" and check the "Enable Identity insert" check box. Click Next twice and then Finish. The data should be copied from the old database to the new. The progress can be monitored in the wizard.

Issue Security Expert controller appears offline even though all IP Address and Port settings appear to be correct. Product Line Security Expert Environment Security Expert Server Windows Operating System Cause The Security Expert Server computer name is larger than 15 characters. There is a maximum limit of 15 characters which can be used in the Security Expert Client for both the Download Server and the Event Server settings, any more than this and the Client cannot resolve the computer names correctly. For further details on this restriction refer to the Naming conventions in Active Directory for computers article on Microsoft's Support website. The Download and Event Server settings can be found in the Global Menu. Download and Event Servers In this example the full computer name, PCName123456789Long, is being used in the Download and Event Server Computer Name fields. Download Server Event Server Security Expert is not able to find the Download Server or Event Server with that computer name as it is expecting a computer name of a maximum of 15 characters. Resolution In circumstances where the PC Name is longer than 15 characters there are two options. Either enter the first 15 characters of the computer name into the Download Server and Event Server settings rather than the longer full name. In the example computer name above the name "PCName123456789Long" would become "PCName123456789". Or change the Security Expert Server computer name so that it is 15 characters or less and use this in the Download Server and Event Server settings.

Issue After configuring an I/NET workstation to connect as a Remote Client the I/NET Configuration profile editor does not start. INetCfg.exe appears in the Windows Task manager processes but no application user interface (GUI) is displayed. Product Line TAC INET Environment I/NET Seven 2.13 and above configured as Remote Client Cause I/NET Configuration profile editor attempts to connect to its active profile database server, if this is not active it will sit and wait for the database server to become active before displaying the I/NET Configuration Profiles user interface (GUI). Resolution It is possible to change the default (or active) profile, provided you have more than one configuration profile.  This is achieved by changing the following settings in the registry. If you only have one profile on your I/NET workstation, you could export a known working profile from another I/NET workstation.  Refer to the following Exporting/Importing Configuration Profiles for the procedure to do this. Ensure that the INetCfg.exe application is not running in the processes, if it is then use the Windows Task Manager to check and end the process before proceeding with the following steps: From the Windows Start menu select RUN Enter in the command regedit Locate the Registry Key > HKEY_LOCAL_MACHINE> SOFTWARE> CSI - Control Systems International> I/Net 2000> Configurations> In this container (Configurations) there is String named "Active" this should display the name of the active profile been used by I/NET. Edit this string to another profile that exists, typically the initial profile called "Config1" is the safest. Close the Registry Editor Run up I/NET Configuration – the profile editor should now start and display the Active configuration you selected above. Modify the profile you wish to use Ensure that the Database Server name is now local to your machine name or is online. If not you can edit this my selecting the Connection Button within the profile.  Make any necessary changes required to the profile Select OK. Ensure the profile you modified is now made active Close the I/NET Configuration Profiles editor and I/NET is now ready to run.

Issue Vista Workstation displays a data point as a signed integer data type that reads from a modbus device, but the modbus point is defined as unsigned integer data type in Device Editor. When a modbus point's raw value is greater than 32768, Vista Workstation displays a negative value. Environment Xenta Servers Ver 5.1.4 or previous Xenta 511, 527, 555, 701, 711, 721, 731, 913 Device Editor Cause Xenta Servers will read Modbus data as 16-bit signed data, whether the modbus point is defined as 16bit SIGNED or 16bit UNSIGNED in the Device Template. Resolution Upgrade Xenta Servers firmware to 5.1.5 or above; Upgrade Vista software environment to 5.1.5 or above. include  Vista Server, Xbuilder, Device Template, Menta

Issue What is the current firmware revision for a Network 8000 GCM and is an upgrade kit available? Product Line TAC IA Series Environment Network 8000 GCM Cause Looking for a firmware upgrade part number. Resolution The following table lists the part number and upgrade kit part number for the system firmware installed in each version of the GCM, LCM and similar type controllers. The listing of a particular device part number, EPROM part number or Firmware Upgrade Kit part number does not guarantee that the specific item can be ordered. Update - 12/31/2011 - All firmware kits listed below are now obsolete and can no longer be purchased. GCM / LCM Model Current Version EPROM Part Number Firmware Upgrade Kit GCM-84x1x (GCS Version) 5.4 PROM-12-100/200/300 GCMA-120-054 GCM-84x2x (ASD Version) 5.41A PROM-12-120/220/330 GCMA-137-054 GCM-85x1x (GCS-CCL Version) 4.7C PROM-12-110/120/130 GCMA-132-047 GCM-85x2x (ASD-CCL Version) 4.7AC PROM-12-140/240/340 GCMA-141-047 GCMA-114 4.2 PROM-19-100 GCMA-130-042 LCM-84x1x (8k EEPROM) 5.4 PROM-23-100/200/300 LCMA-138-054 LCM-85xxx (CCL Version) 4.7C PROM-23-110/210/310 LCMA-141-047 LCM-88x1x (32k EEPROM) 5.4 PROM-23-100/200/300 LCMA-138-054 GCS-xxxxx 4.0 PROM-18-120 GCSA-103-040 GIM-2100 4.7G0 PROM-12-130/230/330 GCMA-140-047 GIM-MTECH 4.8G2 PROM-12-150/250/350 GCMA-143-048 GCM-ECH-002 (Echelon NIM) 11.1B PROM-48-204 GCMA-147-111 GCM-86x11 (GCS Version) 5.4 PROM-41-100 GCMA-145-54 GCM-86x21 (ASD Version) 5.4A PROM-41-110 GCMA-146-54 GCM-ECH-001 (Echelon NIM) 11.1B PROM-48-203 GCMA-148-111 GCM-ETH-001 (Ethernet NIM) 11.2T PROM-48-202 GCMA-149-113 LNC-100 5.4GL PROM-41-160 LNCA-100-054 SIM-CCM 5.4G3 PROM-41-120 SIM-CCN-U SIM-MTECH 5.4GM PROM-41-150 SIM-MTECH-U SIM-TRANE 5.5GT PROM-41-140 SIM-TRANE-550 SIM-YORK 5.6GY PROM-41-130 SIM-YORK-U

Issue Point values are not displayed in Vista Workstation.  Instead, all of them say [??787]. Product Line TAC Vista Environment Vista Workstation Cause The most common cause of the ??787 error message is a mismatch in the XIF between the device and the Vista database.  It may also be duplicate SNVT names in the XIF. Resolution There are a few common troubleshooting techniques that have been applied successfully to the ??787 error and resolved the issue.  The first is to upload parameters from the device.  The second is to browse the correct XIF to the device to eliminate any mismatch. Upload parameters Right-click on the device in Vista Workstation. Select Upload Parameters. Shut down Vista and restart. Make certain you are using the correct XIF The only way to be absolutely certain that the XIF in the device matches the one in the database is to upload the XIF from the device.  You may need to create a dummy LNS database to do so.  Add a generic device and commission with the option to upload the XIF from the device. Update the Vista database.  Again, this may need to be a dummy Vista database. To obtain that XIF, right-click on the device in Workstation and select Properties.  The XIF File tab lists the database copy of the XIF file (hexadecimal file name) that can be found in the Vista database directory in the $thisfil folder. Browse the correct XIF into the Vista Workstation If you are certain you have the correct XIF, right-click on the device in Vista Workstation.  Select the XIF File tab. At the bottom under Source File, click the "..." button and browse to the XIF file. Click okay.  Log out of Workstation and log back in to see the changes take effect. It may then be necessary to right-click on the controller and select Commission and Download. Remove duplicate SNVTs Open the XIF in a word editor (Notepad, Wordpad) Find the duplicate SNVT name using the Find feature Rename one of the SNVTs to a unique name. Use the above steps to browse this new XIF into Vista Workstation. XIF file contains internal variables Open the XIF in a word editor (Notepad, Wordpad) Search for the variable whose value displayed as [??787] If the variable is not listed in the XIF file, it is possible that this is an internal variable which Vista cannot read a value from Contact the manufacture of this device and ask if they can expose the value with a network variable in order for Vista to read it.