Building Automation Knowledge Base

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates 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. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.

Issue Using the EGL, EGRL, EGLL5 which are obsolete Environment Vista Cause temperature/resistance data of EGRL, EGRLL, EGRL5 temperature sensors, or customer needs data to calibrate the sensors. Resolution EGL is replaced by the STD100-250 EGRL - STR100 EGLL  (2 thermistors) was not really replaced, as the average temp calc nowadays is done in the controller. The room version was named EGRLL. All these are for the Vista series. For more information regarding sensors, please visit Exchange Extranet.    Click here for the temperature/resistance chart for the old EGL, EGRL, EGLL5 Click here for the original Product and Installation pdf.

Issue Platform connection using TLS fails. Standard HTTP connection of port 3011 successful. Product Line TAC IA Series. Environment I/A Series Enterprise Server Cause TLS platform connection fails immediately and throws an exception in Workbench. Note that the Niagara Daemon is running and a non-TLS HTTP connection is successful. No station is currently running on the PC. All stations are stopped.   Example exception- SEVERE [08:45:58 02-Sep-20 CDT][wb.shell] Error connecting to platform daemon at localhost: GET /platformInfo javax.baja.naming.UnresolvedException: platformssl: Resolution A possible cause is a zero-byte file size bog file in the Daemon Home 'stations' folder. Check all of the station folders in Daemon Home, searching for any bog file that is zero bytes in size. Look for 'Config.bog.lock' files as one could be orphaned when a station running in the Niagara daemon were to stop unexpectedly, such as the system reboots suddenly or the PC is powered down. Remove all files that are zero bytes in size. Remove any 'Config.bog.lock' files. Test the TLS connection for a successful connection.

Issue BACnet devices not found but are visible in other third party BACnet applications An update may cause devices to go offline Product Line EcoStruxure Building Operation Environment BACnet IP Network Building Operation EnterpriseServer Building Operation Automation Server (AS, AS-P, AS-B) Cause According to BACnet routing rules, each BACnet Device should have a unique BACnet Instance ID and each BACnet Network should have a unique BACnet Network ID  When a BACnet interface is created on an EBO Server, a BACnet IP network is created with default Network ID of 1. This is a local Network address and in not published on the network, it is therefore not a problem if this is duplicated with other EBO Servers. On many site this will remain at 1 for multiple EBO servers with no problems. If a third party BACnet device uses a published Network ID that is identical to the EBO local Network ID, then it will be ignored. There will be a "Duplicate of local network"  System Alarm and line similar to below in the trace log "nsp.pin.BACnet Device <device name>claims to be router to Network #1234 but that is a local network (BACnetMain)" Resolution If the EBO Server is not finding a BACnet device on a different network type (via BACnet routing like MSTP or virtual IP) then it could be the Network ID is identical to the local EBO Server Network ID. If this is the case, then simply change the EBO local Network ID and retest. BACnet Devices on the same IP network, including those on different IP subnets and linked via BBMD or Foreign Devices are not BACnet routed and therefore will not have this issue (no BACnet Network ID route is involved) Some earlier versions of EBO did not ignore these duplicate Network IDs, thus when up grading some devices could go offline. The workaround would be the same. The correction to the BACnet operation occurred in v1.9.3 and v2.0.2

Issue Sometimes just looking at the error message you get from e.g. TAC Vista or SmartStruxure when you try to send an email and it fails can lack information. Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure WireShark Cause It is not necessarily all SMTP error messages and their explanation that are implemented in the software. Resolution For general information on WireShark usage read Using WireShark to analyse communications on an Ethernet network. If McAfee antivirus with HIPS is installed on the PC, use RawCap to capture the communication, as you will not see traffic originating from your PC online in WireShark. Additional reference for this article: Enhanced SMTP status codes   First of all when working with WireShark logs, it's a good idea to filter and focus the communication type you want to look at. In this case it's SMTP, so simply type smtp in the display filter and hit enter.   The easiest way to isolate a single smtp "conversation" between client and server, is to find one of the packets in the conversation, and in the "Analyze" menu click on "Follow TCP Stream".   This will give you the complete conversation in a separate window.   When you have used "Follow TCP Stream" be sure to set the display filter to "smtp" again when closing the window.   This is what happens if authentication is needed by the SMTP server but the client is not using authentication.   Here is the same attempt to send an email, but this time the client has enabled authentication   A little trick when using authentication is that WireShark can actually decrypt the Base64 encoded username and password. Simply right click on any SMTP packet, click "Protocol Preferences" and click "Decrypt AUTH parameters".   He are the packets decrypted   An error not easily detected by e.g. TAC Vista is error 535 "Incorrect authentication data". As stated in the enhanced status code table linked above, it simply means that either username, password or both is incorrect.   Though the product used may not have support for SSL and TLS, you can encounter SMTP server requiring it. Here is an example of a SMTP requesting SSL     For further info on troubleshooting sending emails from TAC Vista, please read Troubleshooting Sending Emails from a Vista Server.

Issue Serial connection to I/A Series R2 UNC VxWorks Target Shell using Windows HyperTerminal Product Line TAC IA Series Environment I/A Series R2 Universal Network Controllers: UNC-410-1 UNC-410-1-N UNC-520-2 UNC-520-2-N Cause There maybe a need to access the UNC via its serial port if the IP address of the UNC is unknown or for troubleshooting purposes when the UNC's Ethernet port is not functioning. Resolution Hardware required for connection to UNC's RS-232 port: 8-conductor flat silver satin stranded cable with standard male (plug) RJ-45 connectors RJ-45 to DB-9 adapter (part number: UNCC-405) or a socket-to-plug type RJ-45 to DB-25 adapter (part number: UNCC-430) A functioning COM port on a computer A 2-pin jumper for connection to the UNC's "Mode" connector Refer to the Installations Instructions for UNC-520 (page 15) for details on the cable and adapter (applies for both UNC-410 and UNC-520). Pinout configuration for a RJ-45 to DB-9 Null Modem Adapter (part number UNCC-405) also refers to these pin outs. Connection to UNC's VxWorks Target Shell using Windows HyperTerminal (for operating systems without HyperTerminal, please refer to Hyperterminal on Microsoft Windows Operating Systems😞 Connect the cable and adapter between the UNC's RS-232 port and the RS-232 COM port used on the computer. Start HyperTerminal (Programs > Accessories > Communications > HyperTerminal). In the 'Connection Description' dialog, type a name for this session. For example, 'Connection to UNC'. Click OK. In the 'Connect to' dialog, use the 'Connect using' drop-down list to select the COM port used on the computer. Click OK. In the Com(n) Properties dialog, choose the following settings: Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: Hardware Click OK. On the UNC circuit board, locate the 4-pin Mode connector and put a 2-pin jumper on the 2 outer pins. Refer to page 17 UNC-520 Installation Instructions for position of the Mode connector (top right corner). With the HyperTerminal session active, remove power from the UNC, let it cycle down, then reapply power. After some number of seconds, text should appear in the HyperTerminal window similar to: Press any key to stop auto-boot... To enter commands to the UNC, press any key to break out of the boot sequence. A prompt similar to the following is shown: [VxWorks Boot]: To determine the IP address / subnet mask of the UNC, do not break the auto-boot sequence as described in step 7. Allow the UNC to finish booting. When the controller stops displaying new messages, press ENTER to reach the command prompt. The prompt is similar to the following: -> Using the scroll bars on the HyperTerminal window, scroll up until the section that begins with the line 'Press any key to stop auto-boot...'. The IP address of the UNC is listed on the line that begins 'inet on ethernet (e)' The IP address is listed (in dotted decimal), followed by a colon, and then the subnet mask (in hexadecimal). Disconnect from the UNC when complete. Press the 'Disconnect' button on the HyperTerminal toolbar. Exit from the HyperTerminal application, selecting to Save if planning to reuse this HyperTerminal setup for future connection to an UNC. Remove the 2-pin jumper from the Mode connector of the UNC. Reboot the UNC by removing the power connector, waiting for all lights to extinguish, and plugging the power connector back in. * If troubleshooting the UNC, send the HyperTerminal start up messages to Product Support for analysis.

Issue Reload of BCX receives error "Infinity controller error: Controller has no assigned Infinet port An error was detected while attempting to set an attribute in a remote Infinity object" Product Line Andover Continuum Environment Continuum Cyberstation BCX 9640 BCX4040 Infinet controller b3 Cause Reloading of a BCX 9640 resulted in error "Infinity controller error: Controller has no assigned Infinet port.  An error was detected while attempting to set an attribute in a remote Infinity object"   Suspected that a learn on the commport was performed or infinet controllers were manually created causing no assigned comm port. Resolution As with any edit of the Continuum system, please make sure to backup the database.   Follow these steps: Send BCX to text file  Add commport to each Infinet controller entry as below Import newly edited text dump file into the BCX. Reload BCX   Example of an original dump file exported in step 1 and the new dump file after the commport is added in step 2. Original Dump File New Dump File Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   SerialNum : 12345   VersionNum : 2.160000  EndObject   Object : Spare   Type : InfinityInfinetCtlr   LastChange : 1/11/2011 4:01:19 PM   DeviceId : Zoo\GreenHouse   Alias : Spare   CreateTime : 8/24/2010 8:28:22 AM   CreatedBy : Root\Acc   TimeLocked : 2/15/2011 12:53:26 PM   InstanceId : 7015/7167   CntrlType : 851   Description : Spare Controller No Points   InfinetId : 1   Location : Control Cabinet   NetworkId : 11   Port : comm2   SerialNum : 12345   VersionNum : 2.160000  EndObject  

Issue Continuum supports different Wiegand card formats and Custom formats, what is the largest card number that can be used? Product Line Andover Continuum Environment ACX57xx (ACX5740, ACX5720) AC1, AC1-A, AC1 Plus ACX780, ACX700 Custom Wiegand - AccessFormat Array Corporate 1000, 26 bit, 32 bit, 37 bit. Cause When ordering access cards and configuring personnel you need to know the maximum numbers allowed. Resolution When configuring a Personnel object the maximum card number that can be entered is 4,294,967,295 the largest 32 bit number. This is the largest possible card number when working with Custom Wiegand. The maximum site code that can be used is 65,535 the largest 16 bit number. Other Wiegand formats: Continuum 37 bit: (Also known as Infinity 37) Card number range: 1 - 524,287.  Site Code range: 1 - 4,095 Note: This is a proprietary format and further format details are not available. Continuum 32 Bit (old format, not recommended for new sites): Card number range: 1 - 8,191.  Site Code range: 1 - 2,047 26 Bit open standard: Card number range: 1 - 65,535. Site Code range: 1 - 255 Corporate 1000 standard: Card number range: 1 - 1,048,575. Site Code range: 1 - 4,095 NOTE For custom formats the maximum format must not exceed 64-bits (i.e. start/end bit of the site code, card number, etc.) See Which HID card formats are supported by Continuum?.

Issue Using the RD and TD LEDs to help commission and Fault finding a Modbus RTU Continuum Xdriver Using the RX and TX LEDs to help commission and Fault finding a Modbus RTU AS, AS-P, AS-B Product Line Building Operation Automation Server Premium Continuum bCX4040 (BACnet) Environment Continuum Automation server Cause How to use the TD RD(TX RX) LEDs to help commission or check an installation Resolution Continuum The Comm Port LEDs on a net controller can be helpful when first setting up or fault finding an Xdriver (ModbusRTU) Every time the net controller transmits the TD LED will flash and every time another device on the bus transmits (such that the net controller can receive it) the RD LED will flash. Thus if Xdriver seems not to be working correctly this is often the first thing to check A simple check with Modbus RTU would be to stop any automatic polling on the network, then manually refresh a modbus point and watch for a single Transmit (TD) followed by a Receive (RD). SmartStruxure The Comm Port LEDs on an AS controller can be helpful when first setting up or fault finding ModbusRTU Every time the AS transmits the TX LED will flash and every time another device on the bus transmits (such that the AS can receive it) the RX LED will flash. A simple check with Modbus RTU is to create only a  single device (or inhibit polling to all but one device) and watch for a single Transmit (TX) followed by a Receive (RX). Modbus Simulation Another useful technique when commissioning or troubleshooting with Modbus is to simulation software on a PC (with RS232/485 convertor for RTU if required). A Slave device or the Master node can be simulated eg ModSim, ModScan, ModbusSlave, ModbusPoll, Mod_RSsim

Issue Netcontroller is running slowly or occasionally goes offline (bCX NC2 ACX CX) Product Line Andover Continuum Environment Continuum Netcontroller, Net Controller, Infinet, MSTP, Bacnet, Xdriver, x-driver Cause There are various reasons why the operation of one or more Netcontrollers and or attached controllers is slow and/or goes offline occasionally.  This guide is primarily to help collate the right information which may identify the issues.  If the reason cannot be identify then this information can be provided to support for further analysis. Resolution General troubleshooting techniques should be used. Define the exact problem. What exactly is slow? eg. Sending to the controller or its connected devices, opening or refreshing graphics, opening or refreshing points, updating Xdriver points, saving programs, creating new points. Is the controller slow from all cyberstations? Is the controller always slow? If not then try to find what makes it go slow, it is time related? Can certain steps be taken to cause the slowness or offline to happen? Get a screen capture of any errors. Gather site information. Continuum version, Continuum hotfixes and service packs applied, number of Cyberstation. Cyberstation operating system, details of Ethernet network and subnets used, with BBMD information of Bacnet sites (Asbuilt or a spreadsheet with IPs, etc.) Continuum Analyzer report, site controller map or spreadsheet or text dump Check the PCs running Cyberstation, do they meet the system specifications? Gather controller information What is the Scan rate? Is the controller time sync. correct? How many objects are on the controller, how many programs are running? What is the firmware version of the netcontroller and b3 or i2 controllers? Ethernet connection - Is the controller on the same subnet as the Cyberstations? A wireshark trace may help to establish the quantity of traffic on the Ethernet (See Using WireShark to analyze communications on an Ethernet network) Comms Ports - XDriver being used? What is on the comms ports? Xdriver (how much communications, points etc) Comms Ports - Bacnet MSTP - How many b3 controllers? How much extended logging? How many alarms being sent? How many 3rd party devices? Look at bacnet settings, how many values are being sent across the network? Check COV settings. Try removing the MSTP cable from the bCX (there could be an issue with an MSTP device causing the bCX to go offline/go slow) Comms Port - Infinet - How many infinet controllers? How much extended logging? How many alarms being sent? Look at infinet settings, how many values are being sent across the network? Check port reconfigs and errors. Try removing the infinet cable from the NetController (there could be an issue with an infinet device causing the NetController to go offline/go slow) Comms Port - other. Again try removing the comms cable from the NetController (there could be an issue with a device on this network causing the NetController to go offline/go slow) Run the Controller error log tool to gather the controller errors See Gather Continuum Controller error logs if requested by Product Support for troubleshooting If the controller goes offline, run the alarm listview.  Does it line up with the Controller error log? Check the CPU LED flash rate on all connected devices (i1, i2, b3 etc) as Can't bring bCX online in Continuum but do get a response to pinging its IP address, also the RD and TD LEDs should be checked for anything unusual This guide is primarily to help the on site engineer by helping them to assess the site. If there is still a need to contact support, please review and record as many items above as possible and send them to the case owner.  Further tests can be carried out including an ACCtrace to determine if the restriction could be at the Cyberstation, See How to capture Continuum Cyberstation activity using ACCTrace NOTE: Ensure all Cyberstations, Controllers and other laptops used for logging are in time synchronization before recording any logs. If it is believed there is an issue with the Infinet or MSTP network see Infinet and mstp bus troubleshooting If it is believed the problem is with extended logging see Extended Logging gaps, performance and load balancing It is possible that something connected to the controller causes the controller to go offline, try disconnecting all other cables and connections to the controller and then re-testing Where a controller is offline when connected directly to a PC/Laptop, try resetting the IP address, otherwise the controller will probably need replacing. NOTE Disconnecting all networks from the NetController is often a good starting point (reconnected IP/Ethernet cable)  

Issue Satchwell "M 1301" Actuator forming part of combined Actuator / 3-port Valve Body assembly requires replacement. Product Line Field Devices Environment Stand alone Satchwell “M 1301” Actuator forming part of combined Actuator / 3-port Valve Body assembly M 1301 Actuator 3-port Valve Body Cause Obsolescence of Satchwell "M 1301" forming part of combined Actuator / 3-port Valve Body assembly. Resolution There is no direct replacement for the "M 1301" Actuator and as a result both the "M 1301" Actuator and the 3-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1301” combined Actuator & 3-port Valve Body assembly with Schneider Electric MD10B-230 Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “M 1301” combined Actuator & 3-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B-230 Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. It is possible that the "M 1301" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B-230 Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.

Issue The following error asserts when attempting to convert a Cloudscape database to SQL 2005 in the Niagara R2 console window: java.sql.SQLException: Invalid object name STATION_NAME.dbo.sysobjects'. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254) at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:477) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:777) at tridium.util.MSSqlServer.doesTableExist(MSSqlServer.java:341) at tridium.util.MSSqlServer.checkTableWithKey(MSSqlServer.java:316) at tridium.datax.sql.DxSqlUtil.checkTableWithKey(DxSqlUtil.java:190) at tridium.datax.sql.DxSqlUtil.checkTable(DxSqlUtil.java:173) at tridium.tools.DbAdmin.migrateData(DbAdmin.java:1007) at tridium.tools.DbAdmin.main(DbAdmin.java:198) at tridium.tools.DbAdmin.main(DbAdmin.java:122) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at tridium.nre.Nre.mainImpl(Nre.java:663) at tridium.nre.Nre.main(Nre.java:603) Environment Niagara R2 WorkPlace Pro version 529 and higher Windows SQL 2005 Cause The Enterprise Server and SQL 2005 database names do not match. The Enterprise Server and SQL 2005 database names have to be the same when migrating the Cloudscape database to a SQL 2005 database. Resolution Rename either the Enterprise Server station or SQL Server database so that the names are the same. Once the names are the same, the migration should go without issues.

Issue How can we exclude Hosts or Users from accessing the Workstation Professional license i.e. Script, Function Block and Graphic editors from another Workstation? Product Line EcoStruxure Building Operation Environment Building Operation License Server FLEXnet Cause When accessing various editors from within Workstation a particular license does not differentiate host or user who should have access to which editors. Using the option file taclic.opt allows you to exclude certain Host / Users of StruxureWare Building Operation from accessing these Workstation clients. The Workstation clients referenced are as follows: client.station (Workstation) client.script (Script Editor) client.functionblock.view (Function Block Editor) client.graphiceditor (Graphic Editor) Resolution FLEXnet Licensing provides the options file to be included in the License Server directory. Each time the License Server service is started this file is checked. Syntax and use can be found in the attached document - Chapter 13 The following option file must reside on the License Server in the following path: Building Operation 1.9 and below: C:\Program Files(x86)\Schneider Electric StruxureWare\Building Operation 1.x\License Server Building Operation 2.0 and above: C:\Program Files(x86)\Schneider Electric EcoStruxure\Building Operation x.x\License Server Once this file is copied into the License Server folder, you must restart the license service (via the Windows Control Panel, Administrative Tools, Services). Examples: # The following text excludes the features from Workstation Professional # # Use the following 3 Exclude statements if you wish to exclude an entire Workstation from accessing editors # EXCLUDE client.script HOST enter_host_name EXCLUDE client.functionblock.view HOST enter_host_name EXCLUDE client.graphiceditor HOST enter_host_name # # Use the following 3 Exclude statements if you wish to exclude a Building Operation User from accessing editors # (remove #'s below as required) # # EXCLUDE client.script USER enter_user_name # EXCLUDE client.functionblock.view USER enter_user_name # EXCLUDE client.graphiceditor USER enter_user_name # Notes: The HOST can be defined by either DNS or IP Address The USER is the user name as defined in Building Operation, this may be the same as the Windows username if using Windows Domain.

Issue The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. In cases where multiple BACnet networks containing SE7000 BACnet room controllers are connected to the same BACnet internetwork there could be duplicate ID's when using this schema. In these instances a T7600 Device Configurator Tool can be used to change these fields. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment • Building Operation Workstation • Building Operation Automation Server • SSL SE7000 Cause The Device ID and name in a BACnet SE7000 room controller is factory set to the model number plus the MAC address. By default the MAC is set to 254 in the room controller, meaning the device does not communicate since valid MAC addresses need to be in the range 0-127. For example when a VT7200F5000B room controller with a MAC address of 41 is connected to a network, its default Device Name will be VT7200F5x00B-41 and its default Device ID will be 72041. The device ID and name will change as soon as the MAC address is changed at the controller. The MAC address is set in the Installer configuration parameter menu using the Com Addr parameter. These fields can also be set by any BACnet management tool that can access these properties. Resolution The goal of this document is to give simple instructions on how to change the Device Instance of the VT7000 series thermostats using the T7600 Device Configurator tool and the recommended connections and wiring. 1. Converter (can be other models): Model 485OT9Lor USOTL4 from B&B Electronics. A USB-to-RS485 converter, like one used for MSTP captures, will work as well.  2. Recommended wiring for the configuration of Device Instances: The SE7000 room controllers have to be connected only to the converter (which has to be powered up) and disconnected from the network controller. The EOL resistors should remain at both ends of the trunk. 3. Setting up the software The software is supplied as a simple installer file download the software from here and run the installer. Prior to running the program for the first time setup steps 4 and 5 must to be accomplished. 4. Setting Windows Compatibility mode The T7600 Device Configurator Tool is legacy tool and therefore is only supported in a Windows 9X operating system, It has been tested and found to work in later versions of Windows by setting the compatibility mode to Windows 95 Locate the executable file T7600_MSTP_Config.exe in the C:\Program Files\Fastek\T7600 Config\ folder. Right click the file and select properties Go to the compatibility tab and change select Run this program in compatibility mode for: "Windows 95" from the drop down menu then click OK 5. Set the PC communications port Open the BACDOCM.ini located in the C:\Windows folder and enter communications port number in the line highlighted below and save the file. If a valid com port is not entered here the program will generate errors when launched and will not operate. Instructions on how to use the converter (file T7x00 MSTP Config.exe): 1. Open the configuration Tool 2. Double click on the BACDOOR icon in the icon tray on the bottom right of the PC. 3. On the window BACDOOR OEM MSTP Client status, click configure and in the configuration window set the Device instance to any number that does not conflict with any other device instance on the network.: 4. Close the BACDOOR configuration window and in the T7000 Device Configurator, click refresh device list. 6. All the devices on the trunk should appear and you can start changing the device instances one after the other. To do that: a. A- Select the first device.     B- Click Connect to device. The connection process can be long, wait for all the objects to be discovered.     C- change the instance ID using the keyboard.     D- click Apply changes. b. Select the next device and do the same. c. Repeat this action for all the discovered devices. 7. After making all the recommended changes, remove the RS-485 to 232 converter and reconnect the network.

Issue How to transfer data from TAC Vista to EBO(EcoStruxure Building Operation) as a temporarily solution while a transition between TAC Vista and EBO is done?    Product Line EcoStruxure Building Operation, TAC Vista Environment TAC Vista SmartStruxure Solution EcoStruxure Web Services TAC Vista SmartStruxure Interface 1.5 Cause If EBO need data from TAC Vista during a transition period the TAC Vista SmartStruxure interface can be used.   Resolution Please see the video or follow the instructions below:   On the Vista server(s) install the TAC Vista SmartStruxure Interface first. Refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if there are any issues installing or getting the two programs to communicate when on the same PC. In StruxureWare Workstation, on the Enterprise server object or the Automation server object right click and create new interface, and select the EcoStruxure Web Service interface in Workstation. Click next. In the Server, enter the IP address of Vista server. If it is local, just use localhost. Enter the username and password of Vista Server. Pay attention that only the user in the default System user group can be used. Don't try to create other System group. And all the letters in the password field need to be in capital letters. This is a defect that will be addressed in the next release of TAC Vista to SmartStruxure interface. Please be selective with the port that you are using. If the Vista to SmartStruxure Interface program is on the same PC as the Enterprise server than a different port other than 80 or 443 will have to be used. Please refer to TAC Vista to SmartStruxure Interface will not connect when TAC Vista and SmartStruxure are installed on the same machine if the two softwares need to be on the same machine. Click Create. The next step is to Host TAC Vista objects into SmartStruxure. Refer to How to host TAC Vista objects using Web Services in StruxureWare Building Operation for the guide of how to host Vista objects into SmartStruxure. NOTE: There is a defect for Version 1.0 of TAC Vista to SmartStruxure interface under Non-English operation system. The EcoStruxure Web Services interface will not come online in SmartStruxure. Refer to TAC Vista to SmartStruxure Interface does not connect in non-English Operation System for solution.

Issue When attempting to open the WorkPlace Tech Tool software, a Windows fatal error box is displayed: WptEd has encountered a problem and needs to close. We are sorry for the inconvenience. If you were in the middle of something, the information you were working on might be lost. Please tell Microsoft about this problem. We have created an error report that you can send to help us improve WptEd. We will treat this report as confidential and anonymous. Product Line EcoStruxure Building Operation, TAC IA Series Environment WorkPlace Tech Tool software WorkPlace Tech Editor Cause This problem can occur when you use an unsupported version of Visio, such as Visio 2000, prior to starting WorkPlace Tech Editor. Only Visio 2010 SP1, Visio 2007 SP2, and Visio 2003 SP3 can be used with the WorkPlace Tech Tool or WorkPlace Tech Editor. Resolution In the warning message, click [Don't send]. Close Visio. Open Visio 2010 SP1, Visio 2007 SP2 or Visio 2003 SP3.  This causes Windows to initialize and configure that specific version of Visio. When Visio opens, confirm that the selected version opens.  If the wrong version opens, you may need to repair the installation of the selected version. Close Visio. Restart WorkPlace Tech

Issue Error messages in Workstation saying "No valid license to add AS found", when trying to add one more AS-P to the ES. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium (AS-P) Demo License file Cause The error message is caused by an expired demo license. When using the Demo License file, the ES checks the Licence at startup, and when doing some operations, like adding AS-Ps. If the Demo license expires, the ES may still work, but you cannot add any more AS-Ps. License Administrator is unable to locate the License Server by using @localhost or IP address(@xxx.xxx.xxx.xxx). Resolution Download a new demo license file from EcoXpert Extranet – The Exchange, and upload it to License Administrator. After the new Demo license file has been added to the License server, you may also need to restart the ES to make sure the new license file will be in use. For more information about the Demo license, please refer to the article EcoStruxure Building Operation Evaluation License for 2.0 and up. When using EBO 2022 v4.0.x and later, the error message (No Valid License to add AS found) can also be displayed if the attached AS-x embedded demo license has expired. Add a current embedded demo license to the device administrator and then re-activate the license to all AS-x servers that require it. Please refer to the article How to activate a demo license on an Automation Server at EBO 2022  Go to Control Panel> System and copy the Device Name Update @localhost in License Administrator > License Server Address to the @"Device Name" Reboot the System(PC) Example The Device Name is "computer1".     Update the License server address to "@computer1" since the Device Name is "computer1"  

Issue What is the limit of how many devices a BACnet controller can know about (Known devices) and what does that mean. Product Line Andover Continuum Environment BACnet bCX bCX4040 Cause More details required about Known devices Resolution The known device limit of a Continuum Ethernet level BACnet controller is 255 and for a B3 level MSTP controller it is 32. This limit means is if a controller needs to either subscribe to a COV from another controller or deliver alarms (Event notifications) to a workstation, that each one of these target devices is a known device. So, for example, if a b3 controller is subscribing to COV's from 30 other controllers and needs to deliver alarms to 3 WorkStations, it would require 33 known devices and the last request for a target device would fail. If a Controller is making 30 COV Subscriptions from one a single controller that would only count as 1 known device. This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to. For example, if a controller had a global point (OAT) that 50 other controllers needed to subscribe to, this is allowed because each COV subscription has within it the target controller's address information and does not use the known device limit. There are two cautions that must be considered. Refer to What are the differences between Standard Continuum Import/Export and Continuum BACnet COV?. Each COV subscription in an exporting controller takes away user memory. Each subscription uses approximately 56 Bytes of user memory. So the limit of how many other devices can subscribe COV's in an individual controller is limited by free memory in the exporting controller. NOTE: To reset  the known devices following a change in the Controllers that will effect the number of known devices, the controller needs to be reloaded.

Issue How do I change the Baud Rate of a field bus (either Infinet or Bacnet MSTP) if there is either an Infilink or B-link on the network? Product Line Andover Continuum, EcoStruxure Building Operation Environment Infinet BACnet Cause The Infilink and B-link must have their baud rate set manually. Resolution All Infinet or Bacnet B3 controllers autobaud on initial startup or when the fieldbus commport is changed from the parent controller's commport editor. The Infilink and B-link must have their baud rate set manually. The proper procedure to change the fieldbus baud rate is to first go to the commport editor and change the fieldbus baud rate. At this point a message is sent to all field bus controllers to change their baud rate. They will all change immediately, however the Infilink and B-link have not yet changed, so the bus will now be in a confused state and there will be offline issues. The next step is to go to the Infilink or B-link repeater and manually change the baud rate to the new setting. At this point the network should work normally, however if the procedure is not followed there may be network issues where you have some controllers that are running at different baud rates causing the network to be totally shut down. If this is the case the way to resolve the issue is to make sure the Infilink or B-link repeater is set to the desired baud rate and power down or reset those controllers on the network so that they will all synch up to the correct Baud Rate upon power up. ** Changing many controllers A method that may help when needing to change the baud rate of many controllers is to bypass the b-link Connect segment 1 of the b-link directly to the BCX comm port and change the baud rate Reconnect the B-link and verify the controllers are now online, repeat the baud change if necessary. Repeat this process for each segment You may still have some isolated controllers that need to be powered off/on. Related: BACnet bCX MSTP network loses communication when a b-Link is added or removed

Issue What is the SubLAN and what is the C-LAN in regards to Ethernet and termination resistor information? Explanation of termination resistor, RS-485, baud rate, token passing, and polling method. Is the Host LAN above or below the Ethernet LAN? Product Line TAC INET Environment I/NET Seven Network Cause A better understanding of the I/NET network architecture and communication components can help to avoid the need to troubleshoot issues later. Resolution When defining the network in I/NET, the chart below helps to explain which components communicate to others including resistor termination. This is a simple explanation on where the various I/NET components are located in an I/NET Seven Network. C-LAN & Sub-LAN Wiring Specifications are available here as a PDF document. Selecting the link Network Definition CLAN SubLAN downloads and opens the pdf document shown below.