Building Automation Knowledge Base

Issue Is there a limit to the number of read/writes available for a BACnet Setpoint object? Environment WorkPlace Tech versions 5.1 and later Cause Not applicable Resolution The BACnet Setpoint object (analog or binary) is used for writing setpoint values to a controller, where it is stored in EEPROM. Observe normal precautions to avoid frequent writes to EEPROM. Excessive writes (typically greater than 100,000) can greatly shorten the life of the EEPROM and adversely affect its reliability. The BACnet Setpoint Priority object (analog or binary) represents a Value BACnet object type, of which the data is read-write accessible. This object can be used to write data to the controller. The Setpoint Priority object provides access to temporarily stored application values, usually setpoints or setup values, that are stored in RAM.  These setpoint values can be monitored and changed via BACnet communications, using the BACnet priority array.  When written from WP Tech, the default value is written to the priority array “relinquish default” location. Only this default value is stored in EEPROM. For more information, refer to the WorkPlace Tech Tool Engineering Guide Supplement (F-27356)

Issue Alarm queue in the Vista Workstation states "No license for LonWorks communication" Product Line TAC Vista Environment Vista Workstation Cause The simplest cause of the issue, and the one that should probably be checked first, is that the license for LonWorks communication was not present at the time the server was started.  Oftentimes, this is due to starting server, realizing the engineering or end user dongle was not plugged in (or license server was not started) and then plugging it in.  The server will not actively poll for this license, it must be present at startup. Resolution Stop the Vista Server Ensure the license dongle is plugged in, or the license file is activated and installed on the license server. Restart the Vista Server Related Articles: "No license for LonWorks communication" with TAC Vista Server LE "No license for LonWorks communication" error when using a non LE dongle "No license for LonWorks communication" - LonMaker Recovery Folder "No license for LonWorks communication" error message in Classic Network "No license for LonWorks communication" Error in Windows 2008 Server X64 TACOS startup delay utility

Issue Unable to connect Remote Client to Standalone Server ASTDIR error when attempting to configure I/NET is sometimes caused by not being logged in as an administrator. Product Line TAC INET Environment I/NET Seven Remote Client Workstation type Cause In most cases, the issue that blocks the remote client connection is port 50069. This must be opened between the two workstations, and use an admin-level I/NET password must be used to initiate communication as well as having to be logged in as an administrator on the local machine. Resolution Log in to Windows as an administrator-level user Make sure that the I/O server is not running Open I/NET Configuration Modify the active profile or create a new one Set TCP/IP settings as well as required reference hosts For Workstation type, select Remote Client or Remote Client (w/IO) When the authentication screen comes up, enter an I/NET operator name with full access. Enter the Host name of the standalone machine functioning as the server. (IP address can be used instead) Leave Authentication Type as default. Press OK Press OK and start I/NET For more information, see Remote Client Configuration Issues I/Net 2.31 and prior and Remote Client with I/O in the Workstation Type of the I/O Server 2.4 and later.

Issue Software download location. Where can I download "MicroNet View's Monitor Tool" dongleless software as advised in: PA-00145 - Satchwell MicroNet Range Rationalisation Product Line Satchwell MicroNet Environment MicroNet View Monitor Tool   Cause The MicroNet View dongleless Monitor Tool, software can no longer be ordered, it is available as a free download. Resolution Download the software from The Exchange or Click here to be linked to the Monitor tool. (This link will open a new page) Click here to be linked to the SNP I/O server. (This link will open a new page) Click here to be linked to the NCP/ARCnet I/O server. (This link will open a new page). Click here  to be linked to the USB dongle driver for MicroNet View, that may be required with faster PC's (This link will open a new page).  

Issue Error: "Could not load file or assembly 'vjslib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified." when starting TGML editor    Can not start TGML editor. Product Line TAC Vista Environment TAC Graphics TGML editor Cause TGML editor needs Microsoft Visual J#® 2.0 Redistributable Package to be installed on the machine for the TGML editor to run. If this for some reason is missing it needs to be installed. Resolution Go to the following link http://www.microsoft.com/downloads/en/confirmation.aspx?FamilyID=e9d87f37-2adc-4c32-95b3-b5e3a21bab2c Download and install the program

Issue Does Sigma 4.04 support a Windows 7 operating system? Environment Sigma release Windows 7 Cause Sigma release 4.04 does not support a Windows 7 operating system. Resolution Sigma 4.04 cannot be used on a Windows 7 operating system. It is recommended that the earliest release of Sigma to be used is 4.05 SEB, To review the release note, please click here.

Issue LON communications not working and error in Application Director: Error initializing LonNetwork javax.baja.LonWorks.LonException: Unable to initialize local lon port {Lon1} Environment G3, ENC, niagara Cause Typically this indicates a hardware issue with the neuron in the ENC. Resolution Open the platform for the ENC and use the Commissioning Wizard to commission the ENC again and see it if recovers.  If error remains the unit must be replaced.

Issue Needing to monitor a controller's online or offline status. I/NET AMT will generate a station lost alarm when a controller is offline, however it is sometimes desired to have a point that can be monitored to alarm as well. Product Line TAC INET Environment subLAN Controller Lan; C-LAN Xenta 527 Cause I/NET AMT will generate a Station lost alarm when a controller is offline, however it is sometime desired to have a point that can be monitored to alarm as well. Resolution Monitoring SubLAN Controllers Connect to the Sub Lan Interface Controller (7798, 7793) Create an internal DA point called LLSSPP_Offline, with LLSSPP being the address of the subLAN device Add a Calculation to the point LLSSPP_Offline Enter this Calculation: OLD(P0) Set P0 to equal any External input point the subLAN device LLSSPP Click okay The result of this calculation is that the point will equal 1 whenever the referenced point goes old Monitoring Controller LAN or C-LAN devices Connect the Controller you wish to monitor Change an external point's Global Level to "Link" (If a point already is set to system, use it.) Connect to a second Controller on the same physical C-LAN (for best results use one physically closer to the NPR or Tap) Create an indirect point referencing the point created in step 2 Create an internal DA point called LLSS_Offline, with LLSS being the address of the controller Add a Calculation to the LLSS_Offline point Enter this Calculation: OLD(P0) Set P0 to equal the indirect point created in step 4 Click OK The result of this calculation is that the point will equal 1 whenever the indirect point goes old, which should only occur when the controller is offline.  Monitoring NPR or Xenta 527 devices Connect to a Controller under the device you wish to monitor Change an external point's Global Level to "system" (Use an existing global point if available) Connect to a second Controller under the device you wish to monitor Change an external point's Global Level to "system" (Use an existing global point if available) Connect to a controller underneath a different NPR or 527  Create an internal DA point called Link _LL_Offline, with LL being the Link address of the 527 or NPR being monitored Create 2 indirect points referencing the global points created in steps 2 and 4 Add a Calculation to the Link _LL_Offline point Enter this Calculation: OLD(P0)&OLD(P1) Set P0 and P1 to equal the indirect points created in step 7 Click okay The result of this calculation is that the DA point will equal 1 whenever both of the referenced indirect points go old.  This should only happen when communication is interrupted to both controllers indicating the most likely cause is the NPR being offline. Please be aware of other potential causes of 2 controllers on the same link going offline. Examples include power circuit failure or cut wire when selecting which controllers to monitor. 

Issue Sigma IC-GEN 4.05 SEB and supported operating systems Environment Sigma IC-GEN release 4.05 SEB Cause New installation of IC-GEN and customer wants to know the latest version and its supported operating system(s). Resolution The latest version of Sigma IC-GEN is Sigma IC-GEN 4.05 SEB. Release 4.05 SEB IC-GEN provides rebranding to Schneider Electric. There are no other changes except for new build and release numbers. This release is shown as Sigma IC-GEN Build 3.43.07 in the installer, uninstaller and ‘About’ box. This release supersedes the previous Release 3.17 for IC-GEN (shown as Build 3.34.12 in the About box and Build 3.34.24 when uninstalling). This version is supported to run on Microsoft Windows XP Professional (32-bit) and Microsoft Windows 2000. (Microsoft Windows Vista and Windows 7 are not supported) Refer to 'Sigma Release 4.05 SEB IC-GEN' release notes for details. The IC-GEN 4.05 SEB software can be downloaded from the Exchange Extranet. Once logged on, go to 'Products' > 'Satchwell' > 'Sigma' > 'Downloads' > 'Upgrades and Software'. The release note can be downloaded from 'Products' > 'Satchwell' > 'Sigma' > 'Release Notes' > 'Options'.

Issue Upgrade Xenta I/O modules Environment Xenta 421A, Xenta 422A, Xenta 420A Xenta 411, Xenta 412 Xenta 491/492 Xenta 451A, 452A, 450A Xenta 471 Cause It is not very common to upgrade I/O modules. If it must be done, they are upgraded the same as any other LonWorks device without a host processor. Resolution Right click on the target file to store the file locally on the hard drive. To be able to download the NXE-file, you need both the NXE and the according XIF-file for the specific device. In LonMaker, select Replace or Commission, depending if the device are already in the database or not. If the XIF-file already exist in the database, select the correct Device Template. In the next dialog, select Load application image. Browse to find the directory for the NXE-file. Change File of type to NXE. Browse to find the directory for the XIF-file. Select Next to decide about source for CP values. Select Next, if you do a Replace, you could select the Neuron ID manually, and the old Neuron ID will already be in the dialog. Select Finish to download the new NXE-file into the device.

Issue Procedure to replace Satchwell MicroNet MN300, MN440, MN500 or MN620 controller with Satchwell MicroNet 50 series controllers MN350, MN450, MN550 or MN650 Environment Satchwell MicroNet series controllers: MN300, MN440, MN500, MN620 MN350, MN450, MN550, MN620 Satchwell VisiSat version 2.1 and above. Cause Satchwell MicroNet series MN300, MN440, MN500 and MN620 are no longer available for sale and they are replaced by the MN350, MN450, MN550 and MN650 controllers respectively. See Product Announcement for details. MN300, MN440, MN500 and MN620 controllers installed on existing installations that are required to be replaced would have to be replaced with the new range of controllers. Resolution To replace Satchwell MicroNet MN300, MN440, MN500 or MN620 controller with Satchwell MicroNet 50 series controllers MN350, MN450, MN550 or MN650 follow the procedure below. Pre-VisiSat 2.1 projects (VisiSat 1.2 and VisiSat 2.0) should be upgraded to VisiSat 2.1 using the Project Upgrade Utility. Download VisiSat 2.1 Engineering Guide here. Refer to pages 47 - 50 for using the Project Upgrade Utility Open the VisiSat project Right-click on the existing controller and select "Upgrade Controller." There is a prompt to save the controller configuration (.CLC file). Select 'Yes'. The controller object in VisiSat will now be converted to a MN50 Series controller. Replace the controller hardware. Make sure the jumpers are set correctly and that communications card, if existing should  be taken out and installed into the new controller. Right-click on the controller object in VisiSat and select 'Configuration Library'. Select 'Download Configuration' (2nd button from the left in the Configuration Library). This will download the configuration to the new controller. Refer to pages 135 - 140 in the VisiSat 2.1 Engineering Guide for using the Configuration Library. NOTE: In the Configuration Library, the first button from the right is the "Upgrade Controller" option. This performs the same function as the "Upgrade Controller" mentioned in step 3 above.

Issue The Drayton Theta YBM3 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBM3 Cause The Drayton Theta YBM3 Valve Body / Actuator assembly is obsolete.> Resolution OVERVIEW The Drayton Theta YBM3 Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBM3 Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT The YBM3 Actuator comprised a 3-wire electrical connection enabling it to be operated by a Mains Voltage changeover contact device as follows :-  Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common  The YBM3 Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-230 MD20B-230 (if MD10B-230 not available) Details of the MD10B-230 Actuator may be viewed here. Details of the MD20B-230 Actuator may be viewed here. N.B. The YBM3 Actuator may also have included an additional 2-wire electrical connection associated with integral Transfer Switches wired as follows :-  Terminal M4 – M1 made to M4 when YBM3 Fully Closed (230Vac) Terminal M5 – M2 made to M5 when YBM3 Fully Open (230Vac) Where external wiring is connected to YBM3 Transfer Switch Terminals M4 or M5 then an Auxiliary Switch Kit containing two S.P.C.O. Auxiliary Switches should be installed on the MD Actuator. Auxiliary Switch Kit MD-S2 (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here. Where external wiring is connected to YBL3 Terminal M4 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S1 (Common) - connect to 230Vac power source Terminal S2 (Normally Closed) - connect to 230Vac device previously connected to YBL3 Terminal M4 Terminal S3 (Normally Open) - no connection necessary Where external wiring is connected to YBL3 Terminal M5 then the MD-S2 Auxiliary Switch Kit should be wired as follows :- Terminal S4 (Common) - connect to independent 230Vac supply Terminal S5 (Normally Closed) - no connection necessary Terminal S6 (Normally Open) - connect to 230Vac device previously connected to YBL3 Terminal M5   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBM3 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue When trying to distribute personnel to Netcontrollers, about half of them fail with the message: Error text undefined (TBD) 0x00002001 under the Last Error column in the Access Distribution View. Environment CyberStation Access Control Cause Access distributions are failing with the same error message in the access distribution view. Resolution Make sure that there are no access controllers that are offline. If there are, and they cannot be brought back online right away, such as during a site renovation, set them to "Out of Service" until they are able to communicate. If they are no longer to be used then delete them - as CyberStation may be trying to distribute to them. This same error message came up on a different project. It was noted that the personnel that failed to distribute (with this error) had schedules attached to their assigned areas, and the schedules reside in the controller that gives the error. The problem was resolved by reloading all the access controllers one-by-one.   Make sure if there are remote area schedules that network issues are not blocking the controller receiving the personnel distribution from getting to the remote controller that own the area schedule point. You can test this by creating test points in each controller and using a program to import the point, in some cases you will see that the program will give the same 0x00002001 error on compilation which indicates network issues. Work with IT to find out what is blocking comm between the two controllers.

Issue Controlli S300 Actuator Environment Controlli S300 Actuator Cause Controlli S300 Actuator terminal details. Resolution L=Neutral L'=230Vac B=Close signal from thermostat or control device R=230V to thermostat or control device V=Open signal from thermostat or control device To test: Place a wire link between R and B, the valve actuator will close, place a wire link between R and V, the valve actuator will open. If a auxiliary switch kit D22 is fitted, this can be used to signal the boiler/pump to start if the installation was a domestic. For the actuator datasheet click here.

Issue How to place an order for more LNS credits to allow LNS plug-ins to work and to be able to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available.   To order more LNS credits: Go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, Click the Copy to Clipboard button to copy the PC key generated by LNS Server License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard. Click next and paste the application key into the field titled "Application Key". Click Finish.

Issue At time it is necessary when troubleshooting to check specific communication settings on a comm port Product Line Andover Continuum Environment Continuum Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Specific commands needed to check communication parameters with precision and to edit them if necessary Resolution Examples of command line parameters needed for Xdriver modbus communication. Command Result p comm2 defaultbaud 9600 comm2 defaultbaud=baud19200 (To set) p comm2 defaultbaud 19200 p comm2 parity None comm2 parity=Odd (To set) p comm2 parity Odd p comm2 stopbits stopbits1 comm2 stopbits=stopbits2 (To set) p comm2 stopbits stopbits2 p comm2 datalength databits8 comm2 databits=databits7 (To set) p comm2 datalength databits7

Issue When using the SBO xbk Analyzer, a warning with the following details is observed:  *** possible configuration issue *** (QC#49504)  Issue: 'Communication failed' alarms between servers, even if no bindings are made Action: Make sure servers can communicate with each other so they can synchronize. Product Line EcoStruxure Building Operation Environment Building Operation Server backups version 3.x and above.  Cause The defect mentioned in the tool (QC#49504 / DBSQA-57599) was initially created because alarms were generated between two (or more) Automation Servers that had no bindings (or references) between them. This behavior is considered normal. This occurs because the servers attempt to synchronize references but fail due to communication issues, resulting in the alarms. These Automation Servers were previously part of the same system but were separated before reference synchronization was completed. A possible scenario for this issue is: Two servers can see each other. Bindings are established between the two servers. The connection between the two servers is then disrupted (i.e., offline). Subsequently, one or more of the bindings are deleted, leading to offline alarms between these servers, even if no binding exists now, due to pending synchronization. Resolution  The XBK analyzer tool detects this situation via a "SyncPending" flag, indicating that it needs to be investigated if a "Communication Alarm" exists between these servers. This warning can be ignored if no communication alarms are associated with the servers listed by the analyzer tool.   In most cases, if the server names listed by the tool are part of the system, the issue can be resolved by checking and verifying for unresolved bindings via Binding Diagnostics. while connected to a working EBO System.   If the tool lists any other server names that are not part of the system, these server names can be cleared by upgrading to EBO 2024 (v6.0.x) and above.  As stated, it is only a warning for earlier versions and can be ignored, as there can be instances where this is not cleared until upgraded to this release.        

Issue Receive Error: "Unexpected file format" when attempting to open Graphic Page Environment I/NET Seven 2.41 graphic pages Cause When creating, modifying and saving graphics in revision 2.41 and then attempting to open these graphic pages in previous versions of I/NET this error "unexpected file format" is presented. Resolution This issue has been rectified in 2.41A and above. I/NET Software are available for licensed Partners to download on The Exchange Download Center.

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 for assistance. Issue In some cases, the event and trend databases can grow really big, although not all the space in the files is used. Therefore, one needs a way to verify that vacuuming the database will help. Product Line EcoStruxure Building Operation Environment SQLite Building Operation Enterprise Server Building Operation Enterprise Central Cause Frequent inserts, updates, and deletes can cause the database file to become fragmented - where data for a single table or index is scattered around the database file. Running VACUUM ensures that each table and index is largely stored contiguously within the database file. In some cases, VACUUM may also reduce the number of partially filled pages in the database, reducing the size of the database file further. Read further information here: https://www.sqlite.org/lang_vacuum.html Definitions are documented here: https://www.sqlite.org/pragma.html  PRAGMA schema.freelist_count; Returns the number of unused pages in the database file. PRAGMA schema.page_count; Returns the total number of pages in the database file. PRAGMA schema.page_size; Returns the page size in bytes (B), which must be a power of two between 512 and 65536. Resolution Stop the Enterprise Server or Enterprise Central. Open SQLiteStudio (link to download) Select "Databases" --> "Add database" Find the event.db or trend.db file from the "historical" folder of the EBO database folder. Use this article to locate for your installation - Clean db for Enterprise Server or Enterprise Central On the added database, right-click and select Connect to the database In the query tab, paste the following command: SELECT (SELECT freelist_count FROM pragma_freelist_count()) AS FreeList_Count, (SELECT page_count FROM pragma_page_count()) AS Page_Count, ((SELECT page_count FROM pragma_page_count()) - (SELECT freelist_count FROM pragma_freelist_count())) AS Used_Page_Count, ROUND(CAST((CAST((SELECT freelist_count FROM pragma_freelist_count()) AS REAL) / CAST((SELECT page_count FROM pragma_page_count()) AS REAL)) * 100 AS NUMERIC),2) AS Percent_Free, (SELECT page_size FROM pragma_page_size()) AS Page_Size_B, ROUND(CAST(((SELECT freelist_count FROM pragma_freelist_count()) * (SELECT page_size FROM pragma_page_size())) / (1024.0 * 1024.0) AS NUMERIC),3) AS Estimated_Space_MB; Click the blue play button above the Query tab.  Review the Percent_Free and Estimated_Space_MB, which will be returned at a minimum, to decide if you want to perform the 'vacuum' command. The vacuum process is slow, as it was designed to operate in the background. Shrink the SQLite event and trend databases. If the Percent_Free is above 80, this is the better option: Shrink the SQLite event and trends databases (Option 2) by creating a new file.

Issue Where should door connection be made on a SCU1284 Termination, Terminal number, PIN, SCU1284 Environment I/Net SCU1284 Cause What output to use for door contact Resolution This information is taken from TCON 312.