Building Automation Knowledge Base

Issue Launching Menta by opening an MTA file causes a Buffer Overrun Error The error message: "Buffer overrun detected ... A buffer overrun has been detected which has corrupted the program's internal state. The program cannot safely continue execution and must now be terminated." Product Line TAC Vista Environment Menta Cause Menta's buffer for opening files is limited; if the file you are trying to open by double-clicking has a very long path (of 142+ characters), you will receive the Microsoft Visual C++ Runtime Library Buffer Overrun error message. Resolution Work arounds: Shorten the path to the Menta file. If it is possible to decrease the number of subdirectories or the length of the directory names to make the total path length less than 142 characters, this will correct the problem. Note: Never modify a Menta file name within Windows; only change Menta file names using the Menta application by using "Save As..." from the File menu. (See "Cannot open file" error when opening a Menta file for resolution if this occurs.)   If it is not possible or practical to change the path to the file, files with long paths can still be opened by launching Menta using the Start Menu or a desktop icon. Select File > Open and browse to the Menta file, then click "Open". Opening the file via this method will expand the path length limitation to over 200 characters.

Issue When attempting to get the trace or system logs through WorkStation, you get the following error "Application not found" Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Detected in version 1.6.1 Windows 7 or below Cause The program or editor associated with the file type *.log can not be found on the PC. Resolution Associate a valid program with the filetype *.log 1. Create a new text file e.g. on the desktop 2. Change the file extension on the file from .txt to .log - refer to the following instructions if the file extension is not visible 3. Double click the file, and select a new default editor 4. Get the trace log from WorkStation

Issue Which Modbus driver is required for a Niagara R2 UNC to support Modbus RTU RS-485? Product Line TAC IA Series Environment Niagara R2 UNC Modbus RTU RS-485 Cause The correct Modbus driver must be installed to allow communication between Niagara R2 and Modbus RTU RS-485. Resolution The Modbus drivers can be installed on the UNC-510-1 and UNC-520-2 models with a maximum supported baud rate of 19.2k for the UNC-510 and 76.8k for the UNC-520. The part numbers are: IA-DRV-MOD (master) IA-DRV-MOD-S (slave)

Issue Satchwell VSF or VJF Valve Body controlled by Satchwell Spring Return Actuator requires replacement. Environment Satchwell VSF or VJF Valve Body installed in Water or Steam Control Valve applications. Cause Obsolescence of Satchwell VSF or VJF Control Valve Body. Resolution STEAM APPLICATION 1.  Replace Satchwell VSF or VJF Valve Body with S-E Two-Port Flanged Valve Body. Where an existing Satchwell VSF or VJF Valve Body is utilised in a STEAM application, then the VSF or VJF Valve Body should be replaced by a suitably sized S-E VGS211F Valve Body, thus enabling steam having a steam inlet pressure up to 1300 kPa and a temperature up to 200 deg C to be controlled. It should be noted however that the face-to-face dimension and overall dimensions of each S-E Valve Body will differ to those of the Satchwell VSF or VJF Valve Body. It should also be noted that the operation of the VGS211F Valve Spindle is the reverse of that of the VSF or VJF Valve Spindle. When the VGS211F Valve Spindle is UP, or in the fully extended position, then the Valve is OPEN. Similarly, when the VGS211F Valve Spindle is DOWN, or in the fully retracted position, then the Valve is CLOSED This will therefore result in the need to replace the existing Satchwell Actuator with the correct model of S-E M700 Actuator, in order to ensure the correct operation of the Valve Body in the event of electrical power failure. It is important that the above limitations are recognised when replacing a Satchwell VSF or VJF Valve Body with a S-E VGS211F Valve Body in retrofit projects. Such limitations do not apply to new projects where a new S-E VGS211F Valve Body and a new S-E  M700 Actuator are being selected, providing of course that an Actuator having the correct spring action in the event of electrical power failure is selected. N.B. Steam Control Valves are normally required to CLOSE in the event of electrical power failure. In the case of the S-E VGS211F therefore the S-E M700 SRSD Actuator should be selected. WATER APPLICATION 1.  Replace Satchwell VSF or VJF Valve Body with S-E Two-Port Flanged Valve Body. A number of alternative models of S-E Two-Port Flanged Valve Bodies are available to replace existing Satchwell VSF or VJF Two-Port Flanged Valve Bodies. It should be noted however that the face-to-face dimension and overall dimensions of each S-E Valve Body will differ to those of the Satchwell VSF or VJF Valve Body.  

Issue Lifecycle margin versus actual station database resource count in Niagara R2. Environment Niagara R2 Cause When pasting objects that are over the maximum allowance size, it will not paste the object because the copy or cut maximum size is depend on the Lifecycle margin. Resolution The UNC-410, UNC-510, and UNC-520 platforms all have a resource count limitation of 600,000.  The TRD-NXT has a resource count limit of 2,500,000. The total number of available resources is the same regardless of support for Web services. The (Search > Resource Count) function under the WorkPlace Pro Search menu item will count the number of resources used. The count is performed from the object currently selected on the JDE tree and includes all child objects. By selecting the station's root name, the resource value for the entire station database will be provided. The dialog box with the information provides the calculated actual Resource count and also will indicate the Lifecycle margin: 20,000. The Lifecycle margin is a JDE term that specifies the maximum size (in resource count) of any “cut” or “copy” permitted in a running station. A cut or copy effectively creates a temporary new tree of objects within the memory of the host. This mechanism is used to support the JDE's “undo” operation (Edit > Undo). As an example, try to cut & paste something and it won't be allowed because of resources.  After checking, for instance, that there is a 43,000 resource count with a lifecycle margin of 20,000, what is happening is that the cut and paste has a total resource count higher than 20,000 which is the max. Perform the cut and paste in smaller portions.

Issue Getting error message in Vista that Menta is in 'stand alone' mode and cannot edit the .MTA Environment Vista Menta Cause This happens usually when Menta has previously been installed on the system in a "stand alone" fashion and then Vista was installed at a later time. Resolution Go to Start > Run and type "regedit" to open the Registry Editor Navigate to HKEY_LOCAL_MACHINE > SOFTWARE > TAC > TAC Menta Double click the key named StandAlone. Change the value data to "No"   For a 64 bit OS, the path in the Registry Editor is HKEY_LOCAL_MACHINE>SOFTWARE>Wow6432Node>TAC Menta

Issue Obsolescence of TAC VG211, VG222, and VG321 series Valve Bodies. Product Line Field Devices Environment TAC VG211, VG222, and VG321 series Valve Body installations. Cause Obsolescence of TAC VG211, VG222, and VG321 series Valve Bodies. Resolution Replace TAC VG211 series Valve Body with S-E.VGS211F 15 – 100CS series Valve Body. It should be noted that a number of anomalies appear in the current issue of the Data Sheet describing the VGS211F 15 - 100CS range of 2-port Valve Bodies. The VGS211F 15-100CS Data Sheet includes two tables of information. A discrepancy appears in respect of the Kv value stated for the 50mm size Valve Body. The table of information on Page 1 of the Data Sheet displays a Kv value of 38 The table of information on Page 2 of the Data Sheet displays a Kv value of 40 The correct Kv value is 40 The type designation stated in the Data Sheet for this Valve Body is also incorrect. The type designation for this Valve Body should read VGS211F-50CS 40M SD00 Arrangements are currently in hand to correct these anomalies. NB The table on Page 1 of the earlier VG211 Data Sheet displayed a Kv value of 38 This value was also incorrect. The Kv value should have read 40 The VG222, VG222 and VG321 are no longer available, as it is replaced with the following: VG222 Valves will have the family name VG221F VG321 Valves will have the family name VG311F Please find the Product Announcement PA-00085 with the information.

Issue It is not possible to access graphics in a Xenta 5/7xx from a smart phone mobile app. Environment Xenta 511, 527, 711, 731 Smart Phones: Apple iPhone, iPad, Android Cause Graphics in a Xenta 5/7xx webserver render in the web environment using Java.  There is not currently a smart phone in the market that is works with Java applets. Resolution There is currently no supported mobile solution for viewing graphics in a Xenta web server. 

Issue Set-up the Link Addressing using the Pocket Terminal (LA +) for port 1 via the DNN3 service port and set port 2 on the DNN3 to be Serial PPP.  Can't communicate to the DNN3 from the Sigma server and global data is not being passed between the two VLAN's. Environment Multiple Sigma controllers across at least two Ethernet VLAN's.  DNN3's (version 1.h) connected to each VLAN. Each DNN3 is connected to the VLAN via port 1 and port 2 is configured as a 'virtual' serial PPP port but not connected to a device. Cause No routing information (static routes) entered into the DNN3's.   Although Link Addressing can be correctly configured the DNN3 devices also need to know where to transmit the point to point global data, that is the router device for the local Ethernet VLAN or default gateway. By having two ports configured on the DNN3 network routing messages RIP will be enabled and broadcast and will advertise the port 2 address as a potential but false route off the network, therefore RIP must also be disabled.  Resolution Using Pocket Terminal or Windows Hyperterminal enter a default Static Route to the DNN3 via its service port.  Use the generic entry 0.0.0.0/0 for the destination sub-LAN and mask.  For example; SR+ 0.0.0.0/0 192.168.1.253   1      (Where 192.168.1.253 is the default gateway and 1 is the DNN port number). RIP must also be disabled on the DNN3 port 1.  For example; RIPD 1

Issue Which Ethernet port speeds are supported by Sigma controllers? Product Line Satchwell Sigma Environment Sigma controllers Ethernet New Hardware. ARM 7(S-696, S-x96CPU-AE, S-796, S-x796CPU-AE, S-DNN3, S-DNN3-DT, S-632-E, S-632-AE and S-IC3's) Old Hardware V53  (S-ETH, S-496, S-596, S-532, S-DNN and S-IC's) Cause The newer ARM-7 controller hardware supports more Ethernet connection speeds than the older V53 controller hardware. Resolution Most Ethernet hubs or switches autoscan to find the best connection speed.  For Sigma device hardware types, the supported Ethernet speeds are as follows: ARM-7 (New hardware): 100Base-T (and supports port auto-scanning on connection) 100M Half Duplex 10M full/half duplex V53 (Old hardware): 10Base-T (does not support port auto-scanning) 10M half Duplex Additionally, for direct connections to a Sigma controller: ARM-7 Ethernet connection supports both straight and cross-over Ethernet cables. V53 hardware only supports cross-over cables.

Issue Alarm delivery server window popping up Environment Continuum Cyberstation 1.91 Cause Alarm delivery server window popping up Resolution Updated OS and applied all the current updates. The issue resolved after the updates

Issue What is the difference between the NL220I and NL220M dongle. Product Line Other, TAC Vista Environment Newron NL220 Cause There are two types of NL220 dongles, (install) and M(maintenance).  Each type have their own specific functionality.  The correct dongle should be selected to avoid issues at a later time. Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case. Resolution Newron NL220 functionality.   Administration (Engineering) mode will allow the following (NL220I): Creating a project Adding network infrastructure devices Adding LonWorks devices – application specific devices as well as programmable devices Installing and commissioning network infrastructure devices Installing and commissioning LonWorks devices Creating SNVT and tag bindings Configuring devices using the generic browser and device specific plug-ins Managing devices Deleting devices Replacing devices Maintenance mode will allow the following (NL220M): Configuring existing devices using the generic browser and device specific plug-ins Managing devices Replacing devices   Typically you use a NL220M for the site installation. This dongle is locked with the site NL220 installation, then use a NL220I dongle in conjunction with the NL220M to unlock the Engineering features. Credits are used and replaced on the NL220M dongle in this case.

Issue I/NET Physical Layer Issues, Lan Reconfigure, and/or Controllers going on or offline 1 at a time. Product Line TAC INET Environment I/NET Cause Physical Layer Issue Resolution Some or all of the following may indicate a physical layer issue. Abnormally large number of Lan Reconfigure messages Controllers going offline individually or in groups and sometimes all together Large numbers of Station Lost/Restore Messages Frequent problems connecting to controllers and data interruption To Troubleshoot a suspected Physical Layer error: Determine if this is a Controller LAN layer issue by direct connection to the Controller LAN using a tap.  If you continue to experience the same errors, as while connected via TCP/IP then the issue is on the Controller LAN Verify that you are using the correct wire gage (22 or 24) and that you controller LAN is less than 4000 feet for 24 AWG and less than 5000 feet for 22 AWG. Verify shield drain wire. Shield drain wire continuity must be maintained as the LAN cable passes through each controller. Shield drain wires from each controller LAN cable must be twisted together, insulated, and tied back such that wires do not come in contact with ground or any conductive surface within a controller. Shield drain wire must be directly connected to Electrical Service Earth Ground at only one end of the cable. The issue at this point can either be a wiring fault or a controller that is broken. Disconnect all controllers from the controller LAN by removing the LAN terminal strip from each controller Reconnect each controller one at a time and watch for the original errors. During this process a LAN Reconfigure is expected each time a device comes online While at each controller watch for any frayed wire, unusual/unneeded splices and if needed re-seat each wire into the terminal block When a controller is brought online and the error returns, examine that leg of the LAN wire for shorts or replace that section of wire Replace the suspect controller with a different device to ensure that the controller is not the source of the problem. (On critical systems you can plug in a spare controller at the location for testing without taking the existing controller offline) Typically if a controller is causing the error it will display alarms or LAN reconfigure on it's LEDs. Consult the TCON for the specific controller for more details (TCON Cross Reference available in TCON Number and Title Cross Reference (with links)). If it is not feasible to replace long sections of wire, or if it is determine that the controller LAN exceeds the specified length, then you may want to consider using Distributed Link Architecture.

Issue Personnel Manager displays "Error getting root folder name" when launching. Product Line Andover Continuum Environment CyberStation Personnel Manager (PIM) Cause At boot time, Personnel Manager queries the ContinuumDB to find the Root container by ID using the following SQL query: SELECT uiname FROM Dictionary WHERE objectidhi = 0 AND objectidlo = 536870913  "Error getting root folder name" will be generated if PIM is unable to access the ContinuumDB or can not find the root object for any other reason. Resolution The User account control slider on a Windows 7 PC will need to be moved all the way to the bottom. Check/resolve for database connectivity errors. Make sure Firewall settings are not preventing the PIM from getting to the SQL server. If the problem persists try the following:   Check to see if Badgemanager.exe is starting. If not then a perform clean uninstall of EpiBuilder with the following steps: From Add/Remove programs (Programs and Features in Windows 7) Uninstall Run Regedit (Start > Run > regedit) Get a registry back by Right clicking on HKey_Local_Machine\Software\ImageWare Systems\EpiBuilder  and select Export and save the selected branch to a file location. This can be used to restore the registry key if necessary. Windows 7: HKey_Local_Machine\Software\WoW6432Mode\ImageWare Systems\EpiBuilder Right Click the same registry branch from step c and select Delete Reboot the PC Reinstall EpiBuilder by going to My Computer or Windows explorer, double click on C:\Program Files\Continuum\EpiBuilder\SDK\InstallEpiBuilder.bat Note: This runs very quickly Start Cyber and open a badge in Personnel Manager If using a VBScript File to redirect communication between principal DB server to mirror DB server, coding may need to be updated. Example: x32 vs x64 bit coding differences For x32: strRegName = "HKLM\Software\Andover Controls\Continuum\Primary Database\Server" strRegData = WshShell.RegRead(strRegName) For x64: strRegName = "HKLM\Software\Wow6432Node\Andover Controls\Continuum\Primary Database\Server" strRegData = WshShell.RegRead(strRegName)

Issue When adding a duplicate card into Access Expert, an error is generated. Environment Access Expert Hosted Instance (cloud) Premise Windows Server 2012 SQL 2012 R2 Version 2 Version 3 Cause Existing customers who may have multiple Tenants using multiple card formats and Facility Codes run into the the problem where there are duplicate cards that may have been ordered or handled differently. In Access Expert, when the card is added an error shows up indicating that the card is already assigned and cannot be added to another person. Card offsets can be introduced in order to ensure no overlapping card number values. Resolution In order to resolve this issue, the following steps need to be followed: 1. Create a new Card Format using the same Tenant Information 2. Add a card number offset, which is added to the original value. ie. a Card Offset of 1000 would make card 100 read as 10100.   3. Save and Close 4. Reboot the controller

Issue Audible alarms not sounding when there are active alarms. Workspace has multiple tabs for graphics navigation and a tab for Alarm View. If a user is not on the alarm tab when an alarm is activated, the audible alarm is not heard, and the user does not know that an alarm has been activated. The audible alarm works when the user navigates to the alarm tab.  Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Building Operation WebStation Cause The Workspace content does not have an Alarm Pane added.  Resolution Edit the Workspace to add an Alarm Pane to the Workspace content. If the user does not wish to display the Alarm View due to screen space etc., configure the Alarm Pane Default visibility to Hidden.  Note: Audible alarms are available in WebStation from 3.2 onward.

Issue ACCTrace and Windows error log show multiple DBFaultDetection, SQLSTATE ERROR CODE:  S1000, ERROR MESSAGE:  [Microsoft][ODBC SQL Server Driver][SQL Server]Warning: Fatal error 823 occurred Environment CyberStation Cause Device (disk) error. Resolution Recommended course of action from Microsoft: Error 823 Severity Level 24 Message Text I/O error %ls detected during %S_MSG of %S_BUF. Explanation Microsoft SQL Server encountered an I/O error on a read or write request made to a device. This error usually indicates disk problems. The parameters in the error message refer to internal structures and don't often help determine which device is involved. However, additional kernel messages in the error log, recorded before error 823, should indicate which device is involved. Action Check the accessibility and condition of the device in question. After you have identified and corrected the problem, execute DBCC CHECKDB to ensure that no other damage was caused by the bad device. For information about using DBCC CHECKDB, see "DBCC CHECKDB" in Microsoft SQL Server Transact-SQL and Utilities Reference. Important If executing DBCC CHECKDB with one of the repair clauses does not correct the index problem or if you are unsure what effect DBCC CHECKDB with a repair clause has on your data, contact your primary support provider. In addition, run hardware diagnostics and correct any problems

Issue How to change the default SMTP port in Vista 5.1.5 running on 64-bit operating systems Environment Window 7 64-bit Windows 2008 server 64-bit Vista 5.1.5 Cause The registry key that allows the SMTP port to be changed is located in a different folder when running 64-bit operating systems. Resolution Open the registry editor. Start\run and then type regedit Go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TAC AB\TAC Vista\5.1.5\SMTP and locate the entry named Port. Double click on this entry and change it to the desired port number. Click OK. (The Wow6432Node folder is a folder that contains information about 32-bit applications being run on 64-bit operating systems).

Issue Some X Drivers on the Third Party Interface datasheet are classed as 1st Generation and others are 2nd Generation, which drivers should I use? Product Line Andover Continuum Environment All X Drivers Any controller with XDrivers enabled on a Comm port. Cause Sometimes the incorrect file is being used on a controller and this will stop the X Driver from working correctly. Resolution You can only use a 1st Generation X Driver on a 1st Generation controller and a 2nd Generation X Driver on a 2nd generation controller. - 1st Generation controllers are: CX9200, CX9400, CX9900, CX9940, CMX9924 - 2nd Generation controllers are: Netcontroller II (CX9680), bCX1 (4040 or 9640), ACX II (5740, 5720)   Download the Third Party Interface datasheet Note: Not all X Drivers are available for both generations of controllers, consult the above datasheet for availability.

Issue In the TAC Vista System Plug-In, a programmable controller is configured through the Xenta Device Plug-In. Browsing to a Menta file on the hard drive should associate that application with the controller to be uploaded to the database later. Instead, an error message is displayed:   TAC Xenta Device Plug-In Could not generate MTA application Environment TAC Vista System Plug-In TAC Xenta Device Plug-In Xenta programmable controller Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause An error in the Menta file is keeping it from generating the necessary background files for the download to occur. Resolution Open the Menta file Go to Options > Simulate If no error occurs, choose Commands > Generate Either at simulation or at generation, an error should be highlighted in the Menta file that is responsible for the failure to generate. Fix this error and save the Menta file back to the hard drive. Attempt to browse in the Menta file again.