Building Automation Knowledge Base

Issue When swiping / presenting a card to a Wiegand card reader in Continuum it does not open the door..  When opening a Listview of Events the log shows "Card Bad Parity" or it reads an incorrect card number using Custom Wiegand. Product Line Andover Continuum Environment CyberStation all versions, with any of the Access Controllers - ACX700, ACX780, ACX57xx, NetControllers with any of the AC1 module range. Cause This fault is caused by incorrect wiring to the reader or choice of a 3rd party reader that is not compatible with Continuum. Resolution When wiring between a controller and a Wiegand card reader, all wires must be connected straight through to the corresponding terminal. Data1 to Data1 Data0 to Data0, Gnd to Gnd ..............etc. See relevant controller installation guide for further details on reader wiring and cable types. On HID readers be sure to wire between the two Data 1 terminals and the two Data 0 terminals. Do not refer to the Clock and Data legend that is also on the controllers and many readers, as this is only used for ABA data connections. When using a separate Power supply for the reader, the 0V (Ground) terminal must still be connected back to the controller GND terminal to ensure both devices are working from a common ground potential. When testing out cards and readers always use a Listview showing a relevant Event log, as this will provide more information than the event view from the Door editor itself. To assist with troubleshooting data reads by the controller especially when using Custom Wiegand for non standard Continuum formats: Select only Custom Wiegand in the Door configuration. Rename the "AccessFormat" array if one has been created. Present a card to the reader. Check the Listview for Events as this will show the raw binary data string the controller is receiving. Compare raw binary data against the expected data from the reader used.

Issue What image formats are supported in a TGML graphic? Product Line EcoStruxure Building Operation Environment EcoStruxure ES, AS Vista Graphic Editor Cause Clarification of supported graphic formats required. Resolution When inserting a picture in a TGML graphic you can select the image file from the following file types: Bitmap, GIF, ICO, JPEG, Metafiles, PNG, TIFF  

Issue Security Expert database size increasing rapidly and getting large. SecurityExpert Database size From the screen capture below, it can be seen that the Security Expert transaction log file SecurityExpert.ldf has increased to a large size. SecurityExpert database log file Product Line EcoStruxure Security Expert Environment Security Expert Microsoft SQL Server Cause The Recovery model of the Security Expert database is set to FULL and the database has not been maintained. When using the Full recovery model, regular backups of the transaction log should be performed to prevent the transaction log file size from growing out of proportion to the database size.   New user databases are created with the same recovery model as the model database. The default recovery model for the model database depends on the edition of SQL Server you have installed. Editions targeted at test and development environments (SQL Server Express) set the recovery model of the model database to SIMPLE. Other editions set the recovery model of the model database to FULL. Resolution For Security Expert, it is recommended that the Recovery model be set to the default of SIMPLE.   You can reduce the size of the logs and also prevent them from getting too large again by changing the recovery model of the database from FULL to SIMPLE. The databases are then shrunk to free up drive space.   Refer to the following steps: Take a backup of both the SecurityExpert and SecurityExpertEvents databases and store them in a safe location Change the Recovery Model of the SecurityExpert database from Full to Simple in SQL Server Management Studio. To do this, right click on the SecurityExpert database and go to its properties. Select 'Options'. Change the Recovery Model setting to Simple. Recovery Model Simple Right click on the SecurityExpert database and select Tasks > Shrink > Files Shrink In the Shrink File - Security Expert window, change the File type to Log. Shrink File Type Log Click OK Repeat steps 2-5 for the SecurityExpertEvents database   It is recommended that regular scheduled backups be configured when using the SIMPLE recovery model. In SIMPLE recovery mode, changes since the most recent backup are unprotected.

Issue The FlexNet console shows the following error Vendor daemon down: taclic No such feature or vendor does not exist: taclic Product Line EcoStruxure Building Operation Environment License Server FlexNet TACLIC Cause The taclic vendor daemon which serves the SmartStruxure licenses is down. This indicates that the vendor daemon either does not exist, or that another application using the same vendor daemon executable is present on the PC. You can run one or more FlexNet license servers with different vendor daemons, but a given vendor daemon can only be run once at a time on the PC. The SmartStruxure Building Operation vendor daemon is called taclic.exe. This can be seen as a process in the Windows Task Manager. Resolution 1. Make the SmartStruxure license server is properly installed 2. Follow SmartStruxure license and TAC Vista license on the same PC if both TAC Vista and SmartStruxure Building Operation is installed on the same PC.

Issue Unable to successfully use Gmail SMTP server to send out alarms via email from I/A Series G3.  Various errors can be seen in the console output. Some of the errors are indicated below but they may not be limited to these. Error: BOutgoingAccount could not dequeue persistent email: 550 The address is not valid java.lang.Exception: Valid CryptoService not found Environment Enterprise Network Server / Enterprise Network Controller I/A Series G3 version 3.5 and above I/A Series G3 maintenance builds version 3.4.55 and above Cause Improper configuration of the EmailService's OutgoingAccount and missing CryptoService in the station. Resolution Procedure and properties settings required when using the Gmail SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.gmail.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@gmail.com Password: Your Gmail account password Enabled: true Use Ssl: true (Gmail requires SSL) Transport: SMTP Use Authentication: true (Gmail requires authentication when sending out emails) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. If you are still having an issue with authentication, it may need to allow less secure apps to access your Gmail account. Refer to https://support.google.com/accounts/answer/6010255?hl=en for details.  Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 (crypto 3.4.64 / crypto 3.5.34) from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue Often data is required to be exported out from the Continuum system for record keeping or for further analysis, what keywords can be used to help with this? Environment Cyberstation Plain English programs - all versions. Microsoft Excel Product Line Andover Continuum Cause Specific help is available in the product for specific keywords but how can these be put together to export data to .CSV format. Resolution As we do not advocate 3rd party system trying to directly extract data from the Continuum database, you should create a Plain English program in a Workstation that can export logged data directly from the controllers out to a .CSV or .TXT file.   Keywords to use for this purpose are: OpenFile WriteFile CloseFile   Details of the above Keywords are available in the Cyberstation internal help pages.   The attached example dump file could be run on a daily basis to extract temperature logs from a controller and save them to files with a date stamped naming convention.   Click to download the example WriteFile dump file. 

Issue Troubleshooting sending email alarms from a Vista Server Mail error 1 – MAIL client needs to be configured first Mail error 2 – Couldn’t connect to server. Error:0  Mail error 2 – Couldn’t connect to server. Error:10022 Mail error 2 – Couldn’t connect to server. Error:10061 Mail error 3 – Couldn’t send message. Response:550 Mail error 3 – Couldn’t send message. Response:503 Unable to relay Product Line TAC Vista Environment SMTP Server Vista Server Workstation Cause There are many reasons why an emailed alarm from a Vista Server wouldn't reach the desired destination inbox.  This document walks through the most common settings and networking issues and how to overcome them. Resolution Vista can be configured to send out alarms via email.  Typically, following the instructions found in the TAC Vista Technical Manual will result in successful delivery of email alarms.  However, there are some factors that can hinder these email messages.  This document is intended to address a few of the most common troubleshooting techniques to resolve these problems. The Basics The first step to getting Vista alarms to email out is to configure the Server Setup.  Reference Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  Enter the address of the Simple Mail Transfer Protocol (SMTP) server as well as the authentication information (if any).  If no SMTP server or login information has been provided, contact an IT professional at the customer’s site to obtain this information. Once Vista Server Setup is correctly configured you must restart the Vista Server. After the Server has been stopped and restarted, set up an Alarm Control Object and an Alarm Receiver – Email.  The steps for this can be found in Chapter 18 Alarm Processing in the TAC Vista Technical Manual. Consider configuring the Alarm Receiver to email a distribution list as opposed to individual email addresses.  Then the distribution list can be edited and maintained by the IT staff without ever having to access Vista. If everything is set up correctly, test the email alarm receiver by forcing an alarm condition.  The alarm should show up in the Vista Alarm Queue as well as at the alarm receiver’s designated inbox.  If the email does not arrive as expected, proceed to the next section of this document titled “Check Vista for Alarms/Errors.” Check Vista for Alarms/Errors If emails are not showing up when expected, the first place to begin the investigation is in Vista Workstation’s Alarm Queue.  There are helpful messages that may appear based on some criteria.  The Alarms will all come from $EE_Mess object under the Vista Server.  Sort the Alarm Queue by Last Change if the alarm just happened, or by Object ID to find the $EE_Mess alarms. Server-$EE_Mess Mail error 1 – MAIL client needs to be configured first Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10022 Server-$EE_Mess Mail error 2 – Couldn t connect to server. Error:10061 Figure 1.  Vista Alarm Queue Mail Errors There are three possible errors that can be seen in the Vista Alarm Queue.  They should occur within a few seconds of the alarm if there is an error connecting to the SMTP server.  If the alarms are acknowledged or disabled, they may not show up in the Vista Alarm Queue.  The other place to look for them is under the Vista database folder on the hard drive.  Inside the database structure there is a folder called $log.  Inside this folder should be a file called b0warlog.txt.  Open this file and scroll to the time/date where the alarm occurred.  If an error occurred, the same text that appears in the Alarm Queue will appear in the error log in a slightly different format.  An example: Mon Aug 17 08:16:26 2009 alrdisp >> Error from SMTPSendMail: Mail error 1 – Mail client needs to be configured first Three possible alarm conditions are discussed here: Mail error 1 – MAIL client needs to be configured first This error refers to the TAC Vista Server Setup.  Refer back to Chapter 3.3 Setting Up TAC Vista Server in the TAC Vista Technical Manual.  If the server is setup correctly, be sure that the server has been restarted since the last change.  Changes in Server Setup will not take effect until the next time server is run. Mail error 2 – Couldn’t connect to server.  Error:0 Unknown cause. Mail error 2 – Couldn’t connect to server.  Error:10022 This error means that the SMTP server is unreachable.  If using a DNS name for the SMTP server, double check the spelling.  If everything looks correct, move to section of this document titled “Check SMTP Server Connectivity” and follow the steps described there. Mail error 2 – Couldn’t connect to server.  Error:10061 This error means that the SMTP server has been reached, but Vista was not allowed access to the server.  Double check the authentication username and password.  Re-enter the password to ensure it is correct (only dots are shown for privacy).  There are three different authentication modes to choose from: CRAM MD5 – (Safest) Password is coded with Message Digest 5. AUTH LOGIN – (Standard) Password coded with base64 method. LOGIN PLAIN – Password is sent uncoded. If the correct authentication mode has not been provided, it may require trying all three until the mail error clears.  If all three result in an error, contact an IT professional to be provided with a valid username and password.  Use the section of this document titled “Contacting an IT Professional” for a template to request this information. Mail error 3 – Couldn’t send message.  Response:550 Unknown user Unknown cause. Mail error 3 – Couldn’t send message.  Response:503 Must have sender and recipient first. Unknown cause.  If no errors occur in the Vista Alarm Queue or in the Vista alarm log text document, refer to the section of this document titled “Vista Indicates No Errors” for more troubleshooting techniques. For troubleshooting unknown errors, read Troubleshooting sending emails using WireShark. Unable to relay If an error "Unable to relay" is returned, this is most likely because authentication is not sent to the SMTP server. Go to Vista Server settings At the email tab set proper authentication (Vista Technical Manual Chapter 3.3 explain this more in detail) You may need to consult with the IT department on site Check SMTP Server Connectivity In order to use an SMTP server, a connection must be established.  In this example, the provided SMTP server is “smtp.ACME.com.”  Pinging is the lowest level of internet communication.  A successful ping will not guarantee communication with an IP device, but a failed ping will guarantee no communication.  Open a new DOS command prompt (Start > Programs > Accessories > Command Prompt).  Ping the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), Figure 2.  Failed Ping Example In Figure 2, a request to ping the SMTP server has failed.  Check that the computer where Vista Server resides has internet connectivity (Start > Settings > Network Connections).  Make sure the connection status is Connected, navigate to an internet website, or ping a known IP address.  If those fail, check the computer’s IP settings.  Figure 3.  TCP/IP Properties - Obtain IP Automatically If the computer is set to obtain an IP address automatically make sure that an IP address has been assigned.  Figure 4.  Local Area Connection Status If no IP address has been defined, then the DHCP server is not available and the computer is not connected a network.  Check the physical connections and contact an IT professional to determine why the DHCP server is not assigning the PC an IP address. If the TCP/IP properties are configured to use a static IP address (which is common in applications where WebStation or ScreenMate are employed), then the DNS server address must also be defined if a DNS SMTP server is used.  Figure 5.  TCP/IP Properties - Static IP If DNS is causing problems, it is possible to bypass this by using the IP address for the SMTP server as opposed to the DNS name. Look back to Figure 2 to obtain the SMTP server’s resolved IP address.  In this example, the IP is 10.10.10.10.  Figure 6.  Using IP Address of SMTP Server When everything is set correctly, try to ping the SMTP server again.  This time, it should go through successfully, which is an indication that most of the basic settings are correct – but should not be viewed as indication that email messages will successfully be delivered by the SMTP server. C:\>ping smtp.ACME.com Pinging smtp.ACME.com [10.10.10.10] with 32 bytes of data: Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Reply from 10.10.10.10: bytes=32 time=1ms TTL=64 Ping statistics for 10.10.10.10: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 1ms, Average = 1ms Figure 7.  Successful Ping Example In Figure 7, the ping has returned four successful results.  This will confirm that cables are connected properly, IP addresses are set, and any necessary gateway routers are communicating.  It does not indicate ultimate success in connecting to the SMTP server. To check connectivity with the SMTP server, use a simple telnet command on port 25 (or the specified port) from a command prompt. C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com... Figure 8.  Telnet command. If there is an error connecting, you will see this: C:\>telnet smtp.ACME.com 25 Connecting To smtp.ACME.com...Could not open connection to the host, on port 25: Connect failed Figure 9.  Failed Telnet Command. If the connection succeeds, the command prompt will clear and show a new line beginning with 220.  Type the word “helo” and press enter.  The SMTP server should again respond but this time with a line starting with 250.  Exit the telnet session by typing “quit” and pressing enter. 220 smtp.ACME.com ESMTP helo 250 smtp.ACME.com quit 221 smtp.ACME.com Connection to the host lost. C:\> Figure 10.  Successful Telnet Session. If a connection can successfully be established through telnet, then the ports are open and SMTP messages should be successfully received from the Vista Server.  That does not guarantee they will be relayed by the SMTP server, so if emails are still not being delivered, continue troubleshooting with the next section titled “Vista Indicates No Errors.” Command not found If a telnet attempt results in the command prompt error "command not found" it is most likely because telnet is not enabled. In newer operating systems (Windows Vista/Windows 7) this feature is not enabled by default. To enable telnet: Go to Start > Control Panel > Programs and Features On the left side, select Turn Windows features on or off Scroll down to Telnet Client and check the box (see Figure 8 below) Figure 11. Enable Telnet Client. Vista Indicates No Errors If no errors show up in either the Vista Alarm Queue or the $log folder, then Vista has successfully contacted a valid SMTP server.  Review Chapter 18 Alarm Processing in the TAC Vista Technical Manual.  Make sure that the alarm is using the correct Alarm Handler that is assigned the correct Alarm Receiver that has the correct valid email addresses defined. If the alarms are set up correctly, the focus should now shift to troubleshooting the SMTP server itself.  Assistance from an IT professional will be helpful at this stage.  Things to check include: Check the incoming/outgoing messages from the SMTP server.  See if the messages from Vista are arriving but not being sent out.  Many companies will set up an “allowed” list that will only pass emails from recognized IP addresses, and all else is filtered as spam.  Make sure the Vista Server’s IP address is listed on the acceptable list. Ask what port the SMTP communication is using.  Port 25 is typically used for SMTP communication, but some companies will change this for security purposes.  Request that port 25 be opened for SMTP communication from the Vista Server.  If this is not an option, the port can be changed manually using registry settings.  See the section of this document titled “Changing the default SMTP Port” for instructions. Look at the selected Text encoding in the Vista Server Setup.  Unicode (UTF-8) is the most common in America and Europe.  If encoding is set to UTF-7, some SMTP servers will filter the messages out as spam. Some companies will block all POP messages on the network.  This will disable the ability to use external SMTP servers.  Make sure POP messages are allowed or that the SMTP server is internal to the network. If you are trying to use an SMTP server of a different ISP than the one Vista Server is connected to, this will most likely be blocked by the SMTP server. This is known as mail relaying – something spammers can and will abuse. Changing the Default SMTP Port Vista defaults to using Port 25 for all SMTP communication.  This is the standard port for SMTP and is typically used by SMTP servers.  However, because it is so well known as the SMTP port, some companies prefer to change this as a security measure.  Request that port 25 be made available to the Vista Server.  Unfortunately, sometimes this is just not possible because of security procedures.  If a different port is required, it is possible to manually change the port by navigating through registry keys. Open up the Registry Editor on the Vista Server PC (Start > Run… > regedit).  Navigate to: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > TAC AB > TAC Vista > 5.1.2 > SMTP Depending on the version of Vista, the path may change slightly.  If a 64-bit operating system is being used, the path will be: My Computer > HKEY_LOCAL_MACHINE > SOFTWARE > Wow6432Node > TAC AB > TAC Vista > 5.1.5 > SMTP Navigate until the SMTP folder is located.  Inside the SMTP folder, the SMTP settings that were set with Vista Server Setup can be viewed.  There is also an additional registry key defining the port.  Figure 12.  SMTP Registry Settings If there is no registry key for Port, create one.  Right click in the key view window, but not on an existing key.  Select New > DWORD Value.  Name the new value “Port.” Double-click the Port registry key to edit.  Radio buttons convert the value from hexadecimal to decimal.  Ports are typically described in decimal values.  Switch to decimal, enter the required port number, and click OK. Figure 13.  Editing Port Registry Key Verify that the value had changed in the registry.  Vista should now be sending out SMTP communication on the required port. Contacting an IT Professional If you need help contacting the customer’s IT department to gather and share the correct data, use the document attached in Appendix A:  IT Request for Information.  A completed example is shown in Appendix B:  Sample IT Request for Information. Disclaimer The information contained in this document is subject to change without notice.  It is also subject to change with versions of TAC Vista.  If further assistance is required, please Call or email Schneider Electric Product Support Appendix A: IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP):   Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable):   Password (if applicable):   Text encoding (if filtered):   To distribution list (if any):   Required TCP Port:   Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses):   From name:   From email address:   From IP address:   Desired TCP port: 25 Appendix B:  Sample IT Request for Information The TAC Vista building automation system installed on your site has the capability to email facilities personnel in certain situations.  Typically, this is used to alert the proper channels of equipment failure or security breaches detected by the automation system.   TAC Vista uses standard Simple Mail Transfer Protocol (SMTP) for these messages.  An SMTP server must be provided in order for these messages to be delivered.  The following document was created to facilitate the sharing/gathering of necessary information between IT and the installation contractor. Information for the Installation Contractor from IT SMTP messages must be sent with the following details: SMTP server address (DNS or IP): smtp.ACME.com Authentication method (choose one): None CRAM MD5 AUTH LOGIN LOGIN PLAIN Username (if applicable): emailuser Password (if applicable): password123 Text encoding (if filtered): UTF-8 To distribution list (if any): facilities_staff@thebuilding.com Required TCP Port: 25 Information for IT from the Installation Contractor SMTP messages will be sent with the following details: (This can be found in TAC Vista Server Setup): To distribution list (or email addresses): facilities_staff@thebuilding.com From name: Vista Server From email address: vista @server.com From IP address: 10.10.10.20 Desired TCP port: 25

Issue As of Continuum version 1.82 the standalone Database Engine is SQL Express, which offers inbuilt backup and restore functionality via Microsoft SQL Server Management Studio (SSMS). What is the process for backing up and restoring Databases prior to 1.82? Product Line Andover Continuum Environment Standalone CyberStation v1.81 and below. Backup/Restore  Cause As of Continuum version 1.82 the standalone Database Engine is SQL Express. Prior to that it was MSDE. What is the procedure to backup/restore an MSDE database? Resolution Visit the Download Center for MSDE Database Utilities:  MSDE Database Utilities Move SQL DB to a different hard drive

Issue Can the red crosses (that indicate that a signal is offline) in Vista or SmartStruxure Workstation/Webstation be disabled? Product Line EcoStruxure Building Operation, TAC Vista Environment SmartStruxure TGML Graphics (Workstation, Webstation) Vista TGML Graphics (Workstation 5.X, Webstation 5.X) Cause When a signal which is bound to an object in a TGML graphic is offline, this is indicated by a red cross when viewing the graphic in Vista or SmartStruxure Workstation or Webstation. Resolution This can easily be disabled in TGML by adding a script to the OnSignalChange event: function signal(evt){   evt.preventDefault(); }  Note, this script will only disable the red X when a point is offline. This does not address any issue that might cause points to be offline. A short video is available on this process, to review, please see SmartStruxure - Graphics - Removing Red Crosses.mp4.

Issue How to reset an ACX 57xx model controller Product Line Andover Continuum Environment ACX 57xx Cause While upgrading/downgrading the controller firmware, communications were lost and the controller is not communicating afterwards. Resolution Consult How to reset a ACX 57xx controller to reset the controller and then re-commission.

Issue Controller is unresponsive and does not respond to a hard reset or power cycle with the battery disconnected..  CPU light remains on constantly. Product Line Andover Continuum Environment InfinityController, b3 Controller NetController II, CX9680 ACX57 bCX Cause Controller stopped functioning after power cycled. Resolution Test controller with a known working PS power supply and/or test the supply voltage is correct If the controller still does not respond to a hard reset then return for repair. See the appropriate manual for reset instructions

Issue When a TGML graphic is opened from Webstation red crosses is shown on the whole graphic or sometimes over certain components. After a few seconds the red crosses disappear. Product Line EcoStruxure Building Operation Environment Building Operation Webstation version 2.x and 3.0.x Cause The red crosses only appear when values from field bus devices are displayed in in the TGML graphic, and only in Webstation version 2.x and 3.0.x. When the graphic is opened from Workstation no red crosses are shown in the graphic. Resolution This issue is fixed in EBO version 3.1.1

Issue Modbus TCP Device (Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus TCP Network Modbus TCP Gateway Cause Modbus TCP Device (Slave) address 248 is reserved and cannot be used. (Modbus TCP Network or Gateway) SmartStruxure supports up to address 247, as per StruxureWare Building Operation - Technical Reference Guide (up to v1.6.1). There was a defect within v1.5.0 and earlier that caused address 250 to be used if the Device address is set to "Invalid." This defect was corrected in v1.6.1. Resolution From v1.9 this is corrected, so it is possible to define addresses for Modbus TCP devices from 1-247 and 249-254 Device addresses 0 and 248 are reserved. Device address 255 is used as the Default address.   For Modbus RTU RS485 master/slave networks, slave device addressing is different, see KB article Modbus RTU slave address.   Further information about Modbus can be found in the KB article Modbus basics.

Issue BACnet tuning policies improperly applied can cause BACnet network problems Product Line TAC IA Series Environment I/A Series G3 ENC I/A Series AX / N4 Jace Cause Configuration parameters in the BACnet tuning policies can initiate high polling rates, force high volumes of writes, reads, and apply confirmed COV to BACnet proxies in the Jace / ENC. Resolution The following video will help us, Configure the "DefaultPolicy" as well as creating additional tuning policies for BACnet proxies   Apply tuning policies to regulate BACnet network utilization

Issue Software Licensing for Continuum 2.0 & StruxureWare Solution Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum Site integration with the StruxureWare Solution Continuum Cyberstation software & Licensing Cause Request for Software Licensing compared to the Hardware key.  Resolution There is a Ordering and Activation document available on the Buildings Exchange Download Center. A link is provided below: Ordering and Activation of Software License for Continuum v2.0 Software license is a dedicated license per workstation and locked to both the hardware and the operating system. Recommended not to install on old hardware. Software licensing is available for both new and existing installations after Continuum 2.0.  A Hardware key is required in order purchase a software license.  This is because the Continuum features and options are purchased with the physical Hardware key, not with the keyless license.   When purchasing the Keyless license, the serial number of the Hardware key is submitted along with a License Information file (c2v) that has been created on the workstation that is to be licensed.  The License Information file is created using the Hasp Key Utility.   Continuum installations pre version 2.0 (e.g. v1.94) who wish to upgrade to v2.0 and would like to benefit from Software Licensing feature must download and install the required files. Those are outlined in the document above. Note: For Continuum Interface for SmartStruxure Solution the demo StruxureWare Building Operation license has all required features. Your Continuum 2.0 key must have the Advanced Webserver feature enabled.You can use the Continuum Interface Server for any Continuum installation: Standalone or Multi-User (LAN). All existing Andover Continuum configurations are supported in the Continuum Interface Server.  

Issue When a MicroNet 100 series LON controller is upgraded to a MicroNet 50 series LON controller, reference in/out objects and the bindings to the LON SNVT bindings are lost. Product Line Satchwell MicroNet Environment VisiSat Software version 2.1 Builds 137, 148, 148 SP1, 185 and 196. Cause The upgrade process removes various items/objects from the original scheme. Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- The upgrade process removes various items/objects from the original bubbleland scheme. See MicroNet 100 to 50 series upgrade precautions.pdf to view more detailed information.

Issue What is the maximum number of devices that can be placed on the MS/TP trunk of the ENC-520, UNC-520 and MNB-1000? Product Line TAC IA Series Environment Niagara R2 Niagara G3 UNC-520 ENC-520 MNB-1000 Cause Unit Load is a measure of the electrical loading of an EIA-485 (MS/TP) network. An EIA-485 network may have 32 unit loads. One unit load consists of one full-load transceiver, two half-load transceivers, four quarter-load transceivers, or eight eighth-load transceivers. Resolution All MNB-xxxx, UNC-xxx, and ENC-xxx devices use quarter load transceivers, which mean that a MS/TP network comprised solely of MNB devices can have up to 128 total devices (1 router plus 127 controllers). The maximum number of BACnet devices allowed per MS/TP trunk, if all devices are quarter-load transceiver, is 127 plus the ENC/UNC or MNB-1000 controller. Note: 32 unit loads times 4 transceivers per unit load equals 128 maximum transceivers per network (32 X 4 = 128). UNC/ENC Resource Limit Although the 128 BACnet devices is the stated maximum for a MS/TP trunk, this maximum is normally not achieved. This is because the number of MS/TP devices that can be placed on a MS/TP bus is limited by the resource limit of the UNC/ENC controller. A shortage of resources will limit the devices on an MS/TP network to a number less than the physical limit. Exceeding the resource limit will negatively affect the UNC/ENC-520s, possibly causing poor performance and resets (of the UNC/ENCs). Reference Appendix A of BACnet Wiring and Networking Practices Guide for additional information.

Issue What actuator can be used as a replacement for the MF-63123? MF-631x3 Series_F_24732_8.pdf (209 KB) MFC 8000_F_25124_4.pdf (260 KB) Product Line Field Devices Environment MF-63123 Cause Original actuator has failed, or requirement for a non US actuator. Resolution Using the installed valve details, the actuator can be selected from the Schneider Electric Valve and Actuator selection Tool.

Issue Locating the IC3-Modbus documentation Environment Sigma IC3 Modbus Documentation Cause Unable to locate documentation. Resolution To download the IC3-Modbus Gateway.txt file click HERE. To download the IC3 configuration guide click HERE. To download the IC3 data sheet click HERE.

Issue The ETL job configuration tool freezes when running the load sources task under the mappings tab. Product Line EcoStruxure Building Operation Environment Extract Transform Load Administration Tool (ETL) Power Manager for SmartStruxure EcoStruxure Web Services (EWS) Enterprise Server Automation Server Cause The ETL default HTTP query size is set to 10 which in some cases can impact the performance of the tool. Resolution Make sure that you read through Energy Expert (Power Manager for SmartStruxure): Best Practices. This article will provide a lot of tips to avoid issues or improve system performance. ETL locks up while loading sources Adjust the HTTP query size to a higher value. This will reduce the number of queries between ETL and the SBO Server. Close ETL. Go to the location where ETL is installed. The default path is C:\Program Files\Schneider Electric\ETL X.X (SBO to PME). Under the Jobs folder there is a project file named "JOB_ETLProjectName.xml". Open this XML file with a text editor. Search for the setting called "ContainerQueryBatchSize". It is set to 10 by default, change it to 100 and save the job. Open the ETL user interface again and try running the Load Sources task. The folder count at the bottom of the screen will increase slower then before because each call is gathering ten times as much data. Note: If the ETL tool locks up again with the query size set to 100, try other values until it is able to complete the task such as 50, 25, etc. ETL takes a very long time to load sources When dealing with very large systems it can take hours for ETL to search through the entire database for all trends. To help reduce the searching time filters can be created to restrict what is exposed to EWS. Go to the System folder EcoStruxure Web Services > EWS Server Configuration. Click on the Filter Hardware Folder tab. Under the "Filter Hardware Folder by Path" section, click on the green addition symbol. In the pop up window, name the path filter and click create. Select the newly created filter path and click on the edit symbol. Enter the path of the folder or item in the database that you want to exclude from EWS. Click Okay. Note: All filter paths created here will NOT be searched by the ETL tool. Save changes. Once the ETL tool has loaded sources and the project has been created, the EWS filters may be removed.