Building Automation Knowledge Base

Issue The documentation for the I/A Series G3 Schneider Electric (TAC) proprietary drivers are not included with the I/A Series G3 software documentation. Where can those documents be obtained? Product Line TAC IA Series Environment I/A Series G3 ASD Driver I/A Series G3 GCM Driver I/A Series G3 MicroSmart Driver I/A Series G3 DMS Driver Cause Documentation for these drivers is not included with the I/A Series G3 software release Resolution The documentation for the I/A Series G3 Schneider Electric (TAC) proprietary drivers can be downloaded from the Publication Zone (under Links) on iPortal (iPortal). The following documents are available: F-27522 -- I/A Series G3 ASD Driver F-27527 -- I/A Series G3 GCM Driver F-27523 -- I/A Series G3 MicroSmart Driver F-27541 -- I/A Series G3 DMS Driver

Issue During the installation of the WorkPlace Tech Tool release 5.8 software, the following error is displayed: Environment Windows 7, Visio 2007sp2 WorkPlace Tech Tool release 5.8 installation Cause The message will be displayed if no Microsoft Office 2010 components have been installed on the computer. Resolution If Microsoft Office 2010 or any of its individual products including Word-2010, Excel-2010, Visio-2010, etc.,  have not been installed on the computer, the message can be ignored.  The Microsoft Office 2010 component upgrade failed because the no upgradable components were not found by the installer.  Click the [Yes] button to continue the installation.

Issue Public time sync Servers for the United States Product Line Andover Continuum, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment IP Level Devices USA Cause Time synchronization is required for accurate alarming and reporting Resolution Here is a web site referencing several US based Time Sync NTP Servers. http://tf.nist.gov/tf-cgi/servers.cgi

Issue Configuration of the OPC Server PC DCOM settings. Environment Sigma ModBMS OPC Server DCOM Matrikon Cause The OPC values could be viewed correctly via an OPC client on the local PC, but could not be viewed by another OPC client across the network. Resolution Configure the OPC Server PC as detailed in the Matrikon OPC document. Click HERE to download this document. To download the Matrikon OPC Client software, please click HERE. Having configured the OPC Server PC DCOM settings, start the MatrikonOPC Explorer programme. In "Network Neighborhood" locate the OPC server PC, and select "ModBMS-OPCserver" Using the RH mouse button, select "Add Group" from the menu. Name as required. Add the required tags to the group. Validate the Tags Using the RH mouse button de-select "Use Async I/O"   The OPC value is now displayed.

Issue Reconditioning  a Satchwell MB/MBX valve using the 617-9-4xx kit. Environment Satchwell MB MBX Reconditioning Valve Cause Drawings of the valve internal assembly were not available. Resolution The reconditioning of an MB / MBX value is not easily undertaken, and it is recommended that the valve is removed from the pipework to carry out this process. If removal from the pipework is not possible, then it is essential that the system water is completely isolated from the valve, and that any remaining water in the valve is drained away. Please note; that if the valve is not isolated correctly, then when the valve front is removed, it will be virtually impossible to reassemble it, and should the water be hot, then serious injury might occur. To refer to the valve internal assembly, please click HERE. It should be noted that the illustration relates to those MB Valve Bodies having 2 shoes (1.1/2”&2” only), the smaller valves only have one shoe. To refer to the "Recondition Kit Drawing", please click HERE. To refer to the "O ring Assembly", please click HERE.

Issue Minimizing network traffic when sharing data between Continuum Infinity controllers Product Line Andover Continuum Environment CyberStation All CXs All i2s, Infinet Controllers Cause Accessing a remote point’s attribute other than value is a point to point operation that generates extra traffic. Resolution Continuum controllers implement an Import/Export strategy in order to minimize network traffic when accessing the value of a point in a remote controller; this is in some ways similar to BACnet COV. When the value of a remote point is referenced in a PE program the system takes care of making sure the owner of the point sends the value to the subscriber(s) via the Import/Export system ONLY when the value changes. Consider the following PE program line… MyNum1 = RemoteCX\Num1 If a looping PE program sits on the line above no extra traffic is generated as the PE program gets the value of RemoteCX\Num1 from its local Import/Export table, information only goes on the wire when RemoteCX\Num1 changes value. The only problem here is that the Import/Export system ONLY works for the VALUE attribute, any other attribute requested from a remote object results in a point to point message on the network to obtain the requested attribute value. Consider the following PE program line in a CX controller we will call LocalCX NyNum1 = RemoteCX\Num1 size If a looping PE program sits on the line above a number of point to point messages would go on the wire every time the line executes. If there are many requests for attributes on remote objects a degrading in communications could take place. One way to avoid degrading communications as explained above is expose the value of the attribute in question by placing it in the value of a numeric object. Example: In RemoteCX create a numeric point (Num1Size) to hold the size of Num1 and use a PE program to set Num1Size Then the program in LocalCX will look like this… NyNum1 = RemoteCX\Num1Size Since the program is now going after the value attribute of Num1Size the import/export system will be used instead of point to point.

Issue Essex Pin Pad Reader Programming in I/Net Seven. Product Line TAC INET Environment Any Windows OS Version and I/Net Seven Version Cause Need to program an Essex Pin Pad reader in I/Net Seven. Resolution Here is the link to programming the Essex Pin Pad Reader Essex Pin Pad requires the site is not using Large Numbers The Essex Pin Pad is for site which wish to use Pin only for entry. Not Pox Card + Pin or Prox only. For information on a Prox card access which includes Pin Pad see HID PIN Pad reader for I/NET Part Number. For a higher security Pin Only option comparable to the Essex see Code-Guard Scramble Pin Pad Reader Programming.

Issue Crystal Reports with I/NET 2.41 and higher Design tab is no longer available (missing) within SevenReports. Can no longer edit Crystal (Seven) Reports Product Line TAC INET Environment SevenReports (Crystal Reports) with I/NET 2.41 and higher Cause I/NET will no longer have the "Crystal Reports" Modify and Design license after May 2012. After 2.41 you must buy a separate CD for this function. Upgrades are not affected by this change. Any SAP Crystal Reports licenses used at existing installations will remain active after an upgrade. Resolution RDC version will no longer be supplied on the I/Net CD.   The NON_RDC version will still allow reports to be Viewed and Printed, as always. Modifying a "Canned" report or designing a "New" report will be impossible unless the new RDC version is installed.   This removal of the Crystal report function will start with I/Net Seven rev 2.41A and beyond.   To receive the Crystal Reports application files and license certificate, the SEVEN-REPORTS-RDC part will need to be ordered in addition to the standard I/NET SEVEN software part for each workstation requiring SAP Crystal Reports. Refer to Unable to install the RDC version for additional information and a copy of the necessary software for upgrading and installing this software.   Upgrades (from I/NET Seven Version 2.21 and above) are unaffected by this change. Any SAP Crystal Reports licenses in use at existing installations will still be active after an upgrade as long as you perform an upgrade of the existing I/NET installation.  If you perform a clean install, so you have uninstalled the previous version of I/NET, you will lose this licensing.      

Issue Using a USB to Parallel converter for the dongle. Product Line Satchwell BAS & Sigma Environment BAS2800+ BAS 2800+ BAS Dongle Parallel USB converter Cause The dongle is not seen when using a USB to Parallel port converter. Resolution In spite of investigations into the use of a USB to Parallel port converter, the BAS dongle cannot be successfully read. It is recommended, that should the BAS 2800+ terminal require replacing, then the new PC is purchased with an additional Parallel port card.. If the PC is acquired from another source, then the appropriate type of Parallel port card should be purchased and fitted. Using "Google" and searching for Parallel port cards, will provide a large selection.

Issue Some SNVT's are not updating correctly. Environment Sigma IC IC3 LON SNVT's Cause LON Bindings are not correctly configured as a "Sigma" connection type. Resolution The IC-LON configuration process is explained fully in the "IC-Lon Configuration document attached HERE. Part of the above document deals with the use of the IC-Lon Plug-in. This Plug-in will create the "Sigma" connection type which is used by the IC-Lon. Below is a screen shot of this connection type. This connection type is selected "Unackd", the advanced settings are shown below. If the correct connection type is not used, then the bindings will not operate correctly.

Issue Unable to locate where to configure the SMTP Server in an Acess Expert V3 Instance. Product Line EcoStruxure Access Expert Environment V3 Premise Cause The earlier versions of the on-premise server/client did not have SMTP functioning properly. As a result, the tab to Configure the SMTP server settings was left out of the software. Resolution Newer versions of the software have SMTP functionality working properly. After upgrading the Server and Client software to the newest versions available, the SMTP Configuratiuon tab will be available as shown below.  Note: For Instructions on how to upgrade the Premise Server and Client software, please see Upgrade Premise Software to Latest Version.

Issue Eaton IP BACnet Lighting Panels are successfully discovered via the Find BACnet Devices but then go offline with error "Communications failure due to routing device not available" Product Line Andover Continuum Environment CyberStation Cause IP BACnet level Eaton devices configured with network number other than zero Resolution Set the network number to zero for all Eaton lighting panels. Then they will stay online.

Issue Verification of BBMD broadcast table list Product Line Andover Continuum Environment bCX CyberStation Cause Where is the location of BBMD broadcast table list. Resolution Using a web browser connect to the bCX using the IP address and login. Select the "BBMD Configuration" option to the left.  (If this in not available then BBMD is not enabled). The BBMD Configuration page lists the IP address, broadcast mask, and network port for each BBMD that the bCX knows of. After a successful "Save All To Flash" has been executed from the BBMD Configuration webpage the "Saved" buttons will be checked off. After a "Teach" has been executed from the BBMD Configuration webpage, the Teach Results webpage will be displayed. If there is an entry in the BBMD Configuration webpage that has a "rejected" status on the Teach Results webpage, either continue to troubleshoot until the teach is successful or remove that entry from the BBMD Configuration webpage.

Issue Unable to add PIN to Users in a new v4.2.243 or v4.2.244 Database / Site. Errors similar to below are seen when attempting to add a new PIN.   Fig. 1 - PIN does not meet complexity requirements Fig. 2 - Could not generate a unique 4 digit PIN Product Line EcoStruxure Security Expert Environment Security Expert version 4.2.243 , 4.2.244 Cause The default PIN settings are not be set when the Site is first created during installation of a new Security Expert Database. Resolution Go to Global > Sites and click Save on the newly created Site object to set the default PIN settings.

Issue How to determine if the IOU modules neuron chip is manufactured by Toshiba or Motorola? Product Line Andover Continuum Environment Continuum Cyberstation I/O modules (All modules affected except the AC-1 Plus, VT-1, Infistat, and LC-1) Cause Up-revving I/O modules to new firmware and there are 3 types that have been used,  Motorola, Toshiba and the most recent Cypress neuron chips. The program ID can help determine which neuron is in the IOU module to select the correct firmware. Resolution To determine the chip type, look at the Program ID using the object editor or a list view. The second digit or position of the second number of the Program ID is the chip set indicator. If the second digit is 2, the I/O Module has a Toshiba chip. If the second digit is 1, the I/O Module has a Motorola or if shipped after 2014 a Cypress chip.  See example of object editor below:   ***** Note: The image above doesn't show the Cypress information. a 1 could be Motorola(old) or Cypress (new). If the flash revision is 21 the it is the most recent flash version for the Cypress chip. The IOU modules that could have the Cypress chip are AC-1(Not Plus), A0-4,DI-8,DM-20, D0-4, D0-6, MI-6, UI-8. Motorola or Cypress Ui8s that have an 11 in the second position of the ProgramID are either Motorola or Cypress chips. The modules with ProgramID 11 in position 2 and firmware version 11 in position 4 of the ProgramID are Motorola and 11 is the most up-to-date version. The modules with 11 in the 2nd position of ProgramID and firmware version 21 in position 4 of the ProgramID are Cypress chips.  I have not seen a separate firmware version 21 file for the Cypress chip on Exchange or anywhere. 21 is the most up-to-date version and was shipped with those modules. The email we found indicates that since the Cypress chip was a direct replacement for the Motorola chip they used the same number (1) in the 2nd position of the ProgramID (instead of using 3). To summarize the most up-to-date firmware versions for the Ui8: Motorola: 11 Toshiba: 20 Cypress: 21   There is an old TPA that describes this in detail. You can download the TPA Technical Bulletin 1041 - Continuum IO Modules Now Using the Toshiba Neuron Chip from The Exchange Download Center.

Issue The Application Director output window displays an Engine Watchdog Timeout by issuing a thread dump and displaying App Failed.  This condition can occur when installing an upgraded station, after a reboot of the existing station, or during normal station operation. Environment I/A Series G3, Niagara Cause The software watchdog mechanism is designed to periodically report the station's engine cycle count to the platform daemon.  The main purpose is to detect and restart a "stalled" station when the control engine is believed to be in a deadlocked condition.  If the station’s engine cycle count stops changing and/or the station does not report a cycle count to the platform daemon within this defined period, the platform daemon causes the VM to generate a stack dump for diagnostic purposes, then takes the action defined by the Engine Watchdog Policy. Depending upon station operation, the watchdog timeout may need to be increased to compensate for transient conditions where the NRE engine thread is temporarily busy during a single execution cycle.  These conditions include simultaneous execution of multiple objects or point extensions that occur on the same time interval, archiving of log history, custom objects, etc. during normal operation.  The default timeout is 1 minute. Resolution Tuning may be required (increase of the default watchdog timeout value). Open the running station, expand Config, expand Services, right click PlatformServices - View - Platform Service Container Plugin, locate the Engine Watchdog Timeout property.  Increase the value by 30 second or 1 minute increments and monitor controller operation (adjust as required).  If the condition continues, contact Schneider Electric Product Support for further assistance. Watchdog policy selections include: Log Only — Generates stack dump and logs an error message in the system log.   Terminate — (Default) Kills the VM process. If “restart on failure” is enabled for the station (typical), the station is restarted.   Reboot — Automatically reboots the host JACE platform. If “auto-start” is enabled for the station, the station is restarted after the system reboots.   Engine Watchdog Timeout — Default is 1 minute, and range is from 0 ms to infinity.

Issue After powering off, pressing the reset and Reset IP button a bCX1 controller still will not start up. CPU does not flash and controller will not respond to a ping. Product Line Andover Continuum Environment bCX1-CR-INF 9640 bCX1-CR 4040 Cause The controller is connected to an Ethernet network that is in a broadcast storm condition. This scenario can also occur if a patch lead is inadvertently looped back onto the same Switch/Router. Resolution Disconnect the Ethernet cable from the controller and it will start up correctly. On a very busy network or under a broadcast storm condition the controller will protect itself as detailed in Controllers go offline during a broadcast storm.

Issue Port 23 is opened through Telnet and can provide a security access breach into a system. Product Line TAC INET Environment All versions of I/Net Software on All Supported Operating Systems. Cause When the Delta Debug tables are set to 1 or 2, it opens up port 23 for use but also Telnet can be used as well. Resolution The following steps need to be followed to resolve this issue: Go to Run and type regedit Open up HKEY_LOCAL_MACHINE Expand the Software tab and expand CSI-Control Systems International On x64 Based Systems the above folder is located under the HKEY_LOCAL_MACHINE\Software\WOW6432Node Open up the Configurations tab and click on the Active Configuration that is currently running in I/Net On the right side window, scroll down to Debug Tables, right-click and modify the setting Change the value to a 0, close out of it, close I/Net and I/o server and restart it again. P.S. This should close that port but be aware that Telnet would not be able to function when this is done.

  Issue EBO 5.0 and all other revisions, In workstation When selecting `View history` of an alarm, we get columns more focused on alarms such as Alarm state, Alarm text,.. etc  But  in WebStation, we have “ View Events “ that shows columns that are more focused on object event history (including Value before, Value After, etc) rather than alarm history.       Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Building Operation Automation Server Premium Cause Navigating to View Alarm history in webstation is different than in workstation Resolution Alarm is a subset of Event, so it is reasonable to see it is under 'Event viewer'. There is no such a thing called 'Alarm history record' in webstation.This is Function as Designed (FAD) If we click on any of the events, after opening it we can see full alarm details.

Issue Many electrical power meters provide a high resolution Modbus or M-Bus output for cumulative parameters such as kWh, kVAh and kVARh.  This output can be displayed in Vista or on an Xenta Server web page, but the resolution can be degraded by inappropriate conversions in XBuilder and choice of display format.  This article shows how to maintain the full resolution of a meter reading from acquisition through to display on a Vista graphic or Xenta Server web page. Environment Xenta 511, 527, 555, 701, 711, 721 (5.1.5 up) Xenta 731, 913 (all versions) XBuilder PM710 Cause Applying scaling or connections in XBuilder, or processing in Menta, reduces the precision of a high resolution Modbus value to that of a Real or Float. Resolution The following comments refer to Modbus registers in the Schneider Electric PM710 energy meter, although many other meters deal with extended precision values in a similar manner.  Acquiring Data from the meter: 1. If you want to maintain the full precision of the meter 'Real Energy, Total' reading, use register 4000 which is a 32 bit signed integer, representing scaled kWh. The scale factor is stored in register 4108 as a 16 bit integer and the two registers should be used in conjunction for display purposes. The maximum full precision value that can be displayed this way is: 2147483647 - 10 decimal digits - before the scale factor is applied. 2. An alternative to register 4000 is provided in register 1000, which is of type 'Float'.  This equates to the REAL type in XBuilder, so it already has only 21 bit precision. However, there is no need to scale it as the exponent is built in to the Float type. Processing input in XBuilder: 3. For register 4000 in the device template, apply a gain of 1 and keep the converted value as INTEGER.  This will maintain the full 32 bit precision of the Modbus register.  If you apply any gain less than 1 or convert the value to a REAL, you will only end up with a 21 bit precision result.  This equates to a loss of 2 decimal digits approximately. 4. Avoid using Connection objects.  For example, a variable of type 'SNVT_elec_kwh_l' has theoretically the same precision as register 4000 in the PM710, so it would seem to be a direct conversion.  However, because you have to use a Connection object to link the two in XBuilder, the value is converted to a REAL internally and you end up with a 21 bit precision result. 5. Xenta Servers can provide full precision Modbus values for display in Vista. Create new Signal objects in the System pane in XBuilder and drag and drop the Modbus values from the Network pane onto the Signal objects.  The Signal objects will have the same precision as the original Modbus registers and are visible in Vista. Displaying values in Xenta Server and Vista: 6. Value pages in the Xenta Server and TGML graphics pages in Xenta Server and Vista can display a 10 digit integer. In the case of item 1 above, all 10 digits will be accurate. In the case of item 2 above, only the most significant 8 digits will be accurate. 7. A value page in the Xenta Server will display a real as 8 digits plus exponent. However, only the 7 most significant digits will be accurate. 8. The object view in Vista will display a real up to 8 significant digits, with only the most 7 significant digits being accurate.  Vista will attempt to show this as fixed point 6.2 and no exponent.  If the actual value is too big or small for this format it reverts to 3 significant digits plus 3 digit exponent.