Building Automation Knowledge Base

Issue TAC Menta, using a dot in the application file name causes the MTA file to grow. Environment Menta Cause Using a dot, or period, in the application file name. Resolution Make sure to not have any dot in the application file name, except for the extension .MTA

Issue What are the current versions of PSI and related programs? Environment Network 8000 Cause Software tools for Network 8000 devices Resolution The latest version of the PSI software is PSI v4.10. It can be downloaded from here. This release contains a software bundle consisting of 8 different PSI tools including: MicroZoneII (MZII) MicroFlow II (MFII) MicroFlow II Air Balance (MFII-Air Balance) LIM PEM XPSI MicroNet-CI (MNet-CI) MicroNet-CI Air Balance (MNet-Air Balance)

Issue Stand-alone Vista 5 applications and Licensing Product Line TAC Vista Environment LMGRD Menta Save Menta View Demo Vista 5.x Cause No license found lc_checkout Failed: Network connect to THIS_HOST failed. The license file indicates THIS_HOST, and the server is not running on this host. Resolution Running Menta, Xbuilder or any of the Vista Applications as a "stand-alone" application i.e. no Vista Server/Workstation, requires a download of the License Server from Exchange Online. Navigate to Product Zone > TAC Vista > Vista Software > TAC Vista 5.0.X > Downloads. Ensure the version matches (5.0X) the version of Vista installed. For instruction set for licensing a Vista Software Entitlement: See How to Host a Vista Site License. Ensure the license is placed in C:\Program Files\TAC(Schneider Electric)\License Files folder. Launch the licensed Vista software of your choice, typically Menta or Xbuilder. When prompted, select "Use a License Server" option. Specify the Computer name that the server exists on, typically the Local Computer Name, or "localhost". To assist in troubleshooting additional Licensing problems: See [Video] Vista 5 Macrovision/Flexnet Licensing: Lmtools diagnostic utility overview See License troubleshooting in Vista 5.1.8 or greater See TAC Vista 5.0 to 5.1.7 license does not work after installation

Issue TGML numeric presentations rounded to integers with no decimals displayed. Product Line TAC Vista Environment Vista Workstation Vista Server   Cause Depending on the component being used to display the numeric data, it may be as simple as a property not set to display decimals. It may also be due to presentation values. Resolution If using the default Numeric Presentation from the provided Snippets library, change the property in TAC Graphics Editor for 'Decimals' to the number of decimals to be presented i.e. 4 decimals = .0001, 2 decimals = .01, etc. If not using this Snippet, check to see if getPresentationValue() is being used in a script, or if the binding itself has the Format attribute set to Presentation instead of None. Presentation value will inherit all formatting from the Vista database and not from the TGML source file.

Issue When upgrading a Niagara G3 ENC-410 / ENC-520 from 3.0.xxx to 3.3.xx, does the license file need to be upgraded too? Environment I/A Series G3 hardware I/A Series G3 software Cause License compatibility question. Resolution View the ENC license file. The first line indicates the version. If the license version="3.3", then the ENC upgrade can proceed without the need for upgrading the license. If the license version is lower than 3.3, the license file must be upgraded. A license file change can only be done by the factory. Use part number IA-LIC-CHG to order it. After upgrading the license, the licensed version and any previous version of the I/A Series G3 software can be installed and run in the ENC.

Issue Controllers are unable to get online after configuration and being added to the relative instance. Product Line Access Expert Environment Access Expert in Cloud or Premise Installations Win 7, Win 8, Server 2012, Server 2014 SSC Controller Cause There are two reason why this could happen: The controller is not communicating with the Feenics Host Service. Outbound Ports are being blocked. Resolution To resolve the issues, please check the following: The controller is not communicating with the Feenics Host Service. The panel may have lost power or network communication. Dip switches may be set incorrectly (Refer to the Mercury Installation Manuals for operating modes) Network Firewall may be blocking outbound communication over port 3001 (Give our Network Tester tool a try, find it within the downloads) Configured DNS server may be unable to resolve at the correct IP.       2.    The user is unable to see events through the Feenics Event Publishing Service. Outbound port 4502 may be blocked. (Give our Network Tester tool a try, find it within the download section) The client has lost internet connection.

Issue Configuration of BACnet Alarming from 3rd party BACnet IP Device that does not support Dynamic Device Binding. (i.e Notifier Fire Panel and etc.) Environment 3rd Party BACnet IP device Notifier Fire Panel Cause When 3rd party BACnet IP device (i.e. Notifier fire panel) supports Dynamic Object Binding, as Continuum WS supports Dynamic Device Binding only, the alarm recipient device (i.e. alarm recipient Continuum WS) needs to be set up in a different way to provide Static Binding information to the 3rd party device as below in order to get the alarm delivered to Continuum WS from the 3rd party BACnet IP device. Resolution Open the editor of the EventNotification in the 3rd party IP device from BACnet View. Go to Delivery tab, click Add Recipient button, or double click the existing recipient WS. Check "BACnet Address" checkbox, and uncheck "Guarantee Delivery" checkbox. Type NetNumber:MACAddress manually as below and save. ** The NetNumber is the BacNet Number from 3rd party device's perspective. The netnumber is 0 by default for most devices but need to consult with the device vendor to get the correct NetNumber. NetNumber of 65535 can be used for broadcasting. ** The MACAddress is the WS's IP address in Hex+BAC0 at the end. For example, Continuum WS IP address is 10.11.12.13, the MACAddress should be 0a0b0c0dBAC0. ** The value for the attribute is 0:0a0b0c0dBAC0. (It can be set to 65535:0a0b0c0dBAC0 for Broadcasting)

Issue Require directions on how to create an Access Level. Product Line Access Expert Environment Windows Server 2012 and Above Cause The steps are needed on how to create a new Access Level. Resolution To create a new Access Level in Access Expert, the following steps needs to be followed: 1. Select Access Configuration from the main headers, Add New Access Level 2. Name accordingly (7 X 7, Cleaners etc) 3. Assign Access Control Entry (drag and drop users from user list) 4. Use existing schedule or create a new one if needed 5. Use door group that has access to requested area or create accordingly 6. Click on Save

Issue TS-58XX 1,000 Ohm Platinum sensors resistance table Environment TS-58XX 1,000 Ohm Platinum Cause Resistance tables are sometimes required for compatibility measures. Resolution Temp (°C) Temp (°F) Ohms -40 -40 842.7 -39 -38.2 846.7 -38 -36.4 850.6 -37 -34.6 854.6 -36 -32.8 858.5 -35 -31 862.5 -34 -29.2 866.4 -33 -27.4 870.4 -32 -25.6 874.3 -31 -23.8 878.3 -30 -22 882.2 -29 -20.2 886.1 -28 -18.4 890.1 -27 -16.6 894 -26 -14.8 898 -25 -13 901.9 -24 -11.2 905.8 -23 -9.4 909.8 -22 -7.6 913.7 -21 -5.8 917.7 -20 -4 921.6 -19 -2.2 925.5 -18 -0.4 929.5 -17 1.4 933.4 -16 3.2 937.3 -15 5 941.3 -14 6.8 945.2 -13 8.6 949.1 -12 10.4 953 -11 12.2 957 -10 14 960.9 -9 15.8 964.8 -8 17.6 968.7 -7 19.4 972.6 -6 21.2 976.5 -5 23 980.5 -4 24.8 984.4 -3 26.6 988.3 -2 28.4 992.2 -1 30.2 996.1 0 32 1000 1 33.8 1003.9 2 35.6 1007.8 3 37.4 1011.7 4 39.2 1015.6 5 41 1019.5 6 42.8 1023.4 7 44.6 1027.3 8 46.4 1031.2 9 48.2 1035.1 10 50 1039 11 51.8 1042.9 12 53.6 1046.8 13 55.4 1050.7 14 57.2 1054.6 15 59 1058.5 16 60.8 1062.3 17 62.6 1066.2 18 64.4 1070.1 19 66.2 1074 20 68 1077.9 21 69.8 1081.8 22 71.6 1085.7 23 73.4 1089.5 24 75.2 1093.4 25 77 1097.3 26 78.8 1101.2 27 80.6 1105.1 28 82.4 1108.9 29 84.2 1112.8 30 86 1116.7 31 87.8 1120.6 32 89.6 1124.4 33 91.4 1128.3 34 93.2 1132.2 35 95 1136.1 36 96.8 1139.9 37 98.6 1143.8 38 100.4 1147.7 39 102.2 1151.5 40 104 1155.4 41 105.8 1159.3 42 107.6 1163.1 43 109.4 1167 44 111.2 1170.8 45 113 1174.7 46 114.8 1178.6 47 116.6 1182.4 48 118.4 1186.3 49 120.2 1190.1 50 122 1194 51 123.8 1197.9 52 125.6 1201.7 53 127.4 1205.6 54 129.2 1209.4 55 131 1213.3 56 132.8 1217.1 57 134.6 1221 58 136.4 1224.8 59 138.2 1228.7 60 140 1232.5 61 141.8 1236.3 62 143.6 1240.2 63 145.4 1244 64 147.2 1247.8 65 149 1251.7 66 150.8 1255.5 67 152.6 1259.3 68 154.4 1263.1 69 156.2 1267 70 158 1270.8 71 159.8 1274.6 72 161.6 1278.4 73 163.4 1282.3 74 165.2 1286.1 75 167 1289.9 76 168.8 1293.7 77 170.6 1297.5 78 172.4 1301.4 79 174.2 1305.2 80 176 1309 81 177.8 1312.8 82 179.6 1316.6 83 181.4 1320.4 84 183.2 1324.2 85 185 1328.1 86 186.8 1331.9 87 188.6 1335.7 88 190.4 1339.5 89 192.2 1343.3 90 194 1347.1 91 195.8 1350.9 92 197.6 1354.7 93 199.4 1358.5 94 201.2 1362.3 95 203 1366.1 96 204.8 1369.9 97 206.6 1373.7 98 208.4 1377.5 99 210.2 1381.3 100 212 1385.1 101 213.8 1388.9 102 215.6 1392.7 103 217.4 1396.4 104 219.2 1400.2 105 221 1404 106 222.8 1407.8 107 224.6 1411.6 108 226.4 1415.3 109 228.2 1419.1 110 230 1422.9 111 231.8 1426.7 112 233.6 1430.5 113 235.4 1434.2 114 237.2 1438 115 239 1441.8 116 240.8 1445.6 117 242.6 1449.4 118 244.4 1453.1 119 246.2 1456.9 120 248 1460.7

Issue What is the procedure for adding an MR52 to a system. Product Line EcoStruxure Access Expert Environment Access Expert in Cloud or Premise Microsoft Windows 7, Windows 8, Server 2012, Server 2014 Cause Unable to find documentation of the installation process for the MR52. Resolution In order to add an MR 52 sub device to an SSC, the following steps need to be followed:   1. Address the board with proper address via dip switch settings (address switches should be pointing to the numbers on the board) 2. Power up the device and verify that LEDS are displaying correctly 3. Once the controller is Online, click on Add Interface 4. Open up the Live Monitoring Window to check the status of the controller 5. If the devices show offline, Right Click on the controller and select Reboot 6. The Live Monitoring Window will show what is actually being sent to the controller 7. Once completed the status will change to reflect what state the controller is in 8. If correct it will be Online (Green), if not check the configuration and/or wiring again

Issue LonWorks point count recommendation for the Xenta 5/7/9xx series controllers What is the device limitation on the FT-10 LonWorks channel installed on a Xenta Server Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause The load point table can be found in Vista version Release Notes on The Exchange Download Center. When Xenta 700 was released the Product Announcement had a table with the recommended number of LonWorks devices attached to Xenta 5/7/9xx. Below you can see a small revision of the recommendations. The list applies to devices which the applications in the Xenta 5/7/9xx are interchanging data with. Other devices that are completely handled by TAC Vista through the LTA port of Xenta 5/7/9xx are not included in this calculation. These devices will influence the LonWorks network performance in a similar way as if they were connected through a Xenta 911 and have to be considered. Not following the design recommendations and adding too many LonWorks devices to a single channel will cause poor Xenta Server performance. Resolution Each device uses "load points" according to the table. As a general guideline the total "load points" on the network shall stay under 100 to get a reasonable performance. In reality the e.g. intensity of the traffic also has an influence as well as, of course, the expectations on response time. Type of device Load points I/O module 5 Xenta group master 280/300/401      20 Additional Xenta 280/300/401      in the group 2 Standard LonWorks device, including Xenta 100, polled 2 Standard LonWorks device, including Xenta 100, bound 0.75 Refer to The Exchange Download Center for future releases of Vista / Xenta Release Notes containing software and updated load calculations This information is usually found in the Appendix B - Engineer Information, and look for section titled LonWorks recommendation for the Xenta 500 and 700 series

Issue Nothing happens when starting the OGC editor Product Line TAC Vista Environment Vista Server Vista Workstation Cause The issue is with data execution prevention (DEP) not allowing the tacdraw application to run.  Resolution If DEP is not required on your system follow these steps: Go to Control Panel > System > Advanced > Performance Settings > Data Execution Prevention Choose "Turn on DEP for essential Windows programs and services only" Reboot the computer and the editor should launch like normal.  If DEP is required on your system follow these steps: Go to Control Panel > System > Advanced > Performance Settings > Data Execution Prevention Choose "Turn on DEP for all programs and services except those I select" Then click the add button and navigate to: For Vista 5.1.4 and up: C:\Program Files\Schneider Electric\TAC Vista 5.1.4 and choose the tacdraw.exe file. For Vista 5.1.3 and prior: C:\Program Files\TAC\TAC Vista 5.1.X and choose the tacdraw.exe file. Reboot the computer and the editor should launch like normal.  

Issue Will public signals in TAC Xenta show up in Echelon Lonmaker? Will AI, DI, AO, DO, PVR, PVI, PVB blocks show up in Echelon Lonmaker?  Product Line TAC Vista Environment TAC Menta LonMaker or NL220 Xenta 30x, 401, 28x Cause Public signal are proprietary and can only be viewed from Schneider Electric products such as TAC Vista Workstation or EcoStruxure Building Operation. Resolution The answer to both questions is no. Only SNVTs are displayed in Echelon Lonmaker, and the SNVTs have to be added in TAC Menta and then downloaded to the TAC Xenta devices.

Issue The B0cfglog.txt file located in the Vista database $log folder and Alarms in Vista are getting the error: Physical unit "Unit Name" on node "Node Name" is a duplicate by uid=### with "Unit Name" on node "Node Name" Product Line TAC Vista Environment Noded Vista Server Master / Slave Vista Cause Conflicting UID in a Master/Slave node network. Master Vista Server or Master. In a Vista network/system containing several Vista Servers, one of the Vista Servers is the Master Vista Server, managing and communicating system-specific information and global settings throughout the Vista network/system. Slave Vista Server or Slave. The Slave Vista Servers in a Vista system receive system-specific information and global settings from the Master in the Vista network/system. If once standalone servers are all added to one Master network, the Master assigns a unique ID to each slave. Normally when a UID gets duplicated the master tells the servers correct the duplication. Sometimes this automated fix cannot occur because the duplication prevents the proper communication. In this case, the slaves need to re-establish communication with each other and be restarted. Resolution Delete the slaved node Update Vista to reflect the node is removed Adding the node back Restart Vista Server The UID should be resolved and the error should not be present.  If the error still comes up please try the following steps: Make current backups of all Vista Databases Close the slave server Open the mater server When asked, "Do you want to change identities on this node?" select Yes Close the master server and reopen both the mater and the salve server and the error should be gone Instructions on how to add the Vista Slave node onto the master can be found in Creating TAC Vista multi-server network. For this to work, the slaves need to be able to see each other as well. If you do not want the slaves to see each other, add them while balancing the load on the network. They can later be removed when the problem is not occurring anymore. 

Issue Satchwell ALM series Linear Actuator requires replacement. Environment Satchwell ALM series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF Series Plug and Seat Valve Body. Actuator type :- ALM series Cause Obsolescence of Satchwell ALM series Linear Actuator. Resolution Replace Satchwell ALM series Linear Actuator with MV15B-230 Linear Actuator and Linkage Kit :-  ALM = MV15B-230 + L7SV (880-0126-000) Linkage Kit N.B.  Should the Satchwell ALM series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the MV15B-230 Actuator as appropriate :-  S2 – MV15B = Two independent 250 volt 10 amp / 3 amp rated SPDT Auxiliary End Point Switches.

Issue Cannot find third party bacnet gateway devices Environment BCX 3rd party bacnet gateway devices Cause Configuration issue will not allow proper communications on Bacnet protocol Resolution The third party Bacnet Gateway devices were setup as foreign device registration and not properly configured. Foreign Device registration is not needed on a single subnet bacnet setup. Disabled foreign device registration and Bacnet communications is now properly established. Also check that the correct subnet mask has been entered for the network

Issue Database exchange with third party databases such as CRM, Oracle's PeopleSoft, SAP, HR Data Manager, OPC Server, Automatic Number Plate Recognition ANPR, or DataCard's ID Works Images and thumbs or thumbnail .jpg pictures and ID Works folder structure Product Line TAC INET Environment Campus' with LAN network with multiple departments keeping individual user information. Cause Need to streamline the individual's information into multiple databases or changes such as removing SSN with Employee ID number, or interface with third party software/database. Resolution I/NET works with a software called ID Works which is a product from Datacard. ID Works allows the database in I/NET to be viewed and individuals to be added, updated, and deleted. As far as extracting the data from datacard to any third party software, such as Peoplesoft, HR Data Manager, or SAP, that is out of the range supported by PSS.  The need for constant interchange of the data for new card production, deletion, and update of individuals in the  I/NET database is easy to setup and link to the tables for each category. Altering the tables in the database would void any support with the I/NET product. Imports and additional information from CSV (comma separated value) or a spreadsheet for example, can be added to existing tenant groups. Keep in mind that tenants groups cannot be added from ID Works. Imports usually run in a script program designed by Expert Services on a cost basis. Scripts that run between the I/NET database and third party databases need to be constantly running in the background and replicate personnel changes on campus.  Images and ID Works Images which are brought in from ID Works via a camera are put in a folder for example C:\IDWorks\Images. Make sure you specify the thumbs directory under the Images folder for example C:\IDWorks\Images\thumbs so that when you go into ID Works Production and it creates that thumb nail, it puts it in this thumb folder and not the Images folder. If you have both going into the same folder, there will already be an image there with the same name. INET does not have an OPC Server. One of the main uses of the OPC Server was to run a TAC I/NET system in the background with a TAC Vista front end as an initial attempt to migrate to a newer system platform. The introduction of the Xenta 913 allows the communication of TAC I/NET to Modbus and BACnet which became the preferred replacement of the I/NET OPC Server.

Issue LNS Database errors Corrupted LNS Database Product Line TAC Vista Environment LNS Turbo (3.2 or later) Database LonMaker, NL220 Cause There are various causes for a corrupted LNS database.  Backups, disk defragmenters, older versions of LNS, PC crashes, can cause errors in the LNS database. Resolution Before giving up on a troublesome database and rebuilding everything from scratch, try to repair any background errors by running it through the LNS Database Validator.  It can identify, and sometimes fix errors in the database, restoring functionality. The Validator tool works in "layers". Depending on the corruption, errors may need repaired by a specific hierarchy. This means validation may need to be performed multiple times to correct remaining errors. Backup the LNS database.  Do not proceed until a valid backup is created. Go to Start > Programs > Echelon LNS Utilities > LNS Database Validator This program only works on LNS 3.2 and later, and will not be available to LNS 3.1 PCs Under Network to Validate: browse to the desired LNS database Do not check "Repair Database" the first time.  Just hit Validate. Make note of any errors that are found.  Now check "Repair Database" and Validate again. Make note of any errors that have been corrected. Try to open and use the LNS database again. You may need to repeat steps 5 and 6 until all errors are corrected, or until the Validator refuses to correct the remaining errors.

Issue The VX logging functionality is not included in the 5.15 release. It is functioning in prior and later releases. Product Line TAC Vista Environment Xenta 500 Xenta 700 Xenta 900 Cause VX functionality was not included with the 5.15 release. Resolution Use a version other than 5.15 where the VX log is included.

Issue A multi-port router can be represented in a LonMaker drawing using several LonMaker Basic Shapes routers if the internal structure of the L-IP is understood. Alternatively, Loytec provides a stencil library of their routers that can be used. Product Line TAC Vista Environment LonMaker Visio Loytec L-IP routers L-IP-3ECT, L-IP-1ECT, L-IP-33, L-IP-3333, LS-13333, LS-11333, LS-13300 LS-33300, LS-33, LS-13, LS-11 Cause The LonMaker Basic Shapes router only represents a single port router (near side/far side). To represent the 2, 3, or 4 port L-IP routers requires multiple basic routers with different channel types, or one of the device templates from the Loytec Shapes stencil library. Resolution Download the latest Loytec Shapes 5.0 stencil library here. Extract the contents of the .zip file Move the LoytecShapes.vss files to C:\LonWorks\LonMaker\Visio Note: This is assuming that LonMaker is installed at the default location on the C: drive Start LonMaker Go to File > Stencils > LoytecShapes Select the router part number that matches the physical device. The appropriate channels for the router will be added along with the shape. Each port can now be commissioned separately. See also How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver for more information.