Building Automation Knowledge Base

Issue BACnet bCX MSTP network loses communication when a b-Link is added or removed Product Line Andover Continuum Environment MSTP b3 bCX4040  b-Link Cause The bCX MSTP circuitry is slightly different to the b-Link  MSTP circuitry , thus under some circumstances, other faults on the MSTP network can cause communication to change, when the network is connected via a b-Link Resolution If an MSTP network is installed correctly, then it will operate correctly at all speeds up to 76.8k (assuming all devices operated up to this speed) If the MSTP network is not stable up to 76.8k, or adding or removing a b-Link causing a loss of communication, then it is likely there is some fault on the network. (adding or removing the end of line termination resistors, is also a useful fault finding option) The bCX MSTP components are slightly different to the b-Link MSTP components, thus under some circumstances, other faults on the MSTP network can cause communication to be lost, when the network is connected via a b-Link Example This has been seen when third party variable speed drives (VSDs) were connected to a bCX MSTP network (these unit had switchable termination resistors that by default were in circuit) The communication was ok at a low speed (19200) connected directly to a bCX, but when the network was put on the secondary side of a b-Link, the communication failed. Once the termination resistors were switched out of circuit, the communication via the b-Link was fine. In the example above the VSDs were by ABB Related: How to change the Baud Rate of a field bus (Infinet or Bacnet MSTP) when there is an Infilink or B-link on the network

Issue Using the keypad on the stat to set the comm address may result in duplicate Device Instance IDs on a BACnet network. Product Line Andover Continuum, EcoStruxure Building Operation Environment Viconics Cause Find New BACnet Device does not result in new Viconics stat added to the system. This is due to the default assignment ID scheme used by Viconics. It is resulting in a duplicate Device ID on the BACnet network. Resolution By default, the Device Instance ID (called the Device Node ID in Continuum) is generated using the first two digits of the model of the thermostat + the comm (MAC) address assigned to the stat. Example: For a VT7200C5000 thermostats with MAC address 115, the default Device Instance would be 72115. The problem is that when installing the same model stats on multiple MSTP networks on the same BACnet system, this scheme can easily result in duplicate Device Instance IDs. The resolution is to change the duplicates or use a scheme to assign unique IDs manually to all the stats on a system. Any number between 1 and 4194303 (between 1 and 3FFFFF in Hex) is accepted by the thermostat. One scheme would be to use the BACnet Network ID and append the MAC address to it. Since each BACnet Network ID must be unique across the entire system, and the MAC address on each BACnet Network must be unique, this assures the combination is unique across the system. For example, if you have a bCX with an MSTP bus on comm2 that has a BACnet Network ID - Comm2 of 2765 and a stat with a MAC address of 9, assign it the Device Instance ID 2765009. A BACnet Explorer that provides write access to the Device Instance ID is required to change the default Device Instance ID. See Changing the BACnet device instance of the SE7000 series room controllers for a link to the Viconics VT7000 BACnet Configurator utility. For additional support on the above utility contact Viconics Support at 1-800-563-5660.

Issue The discontinuation of the SVT controller due to component obsolescence. Product Line Field Devices Environment SVT Optimiser 4201 4251 Cause What replacements are available for the SVT 4201 / 4251 controllers? Resolution Important Note - The replacement controller mentioned in this article is no longer available, and therefore a replacement for the SVT 4201 / 4251 is not available. The SVT controller range has been discontinued due to component obsolescence. The SVT controller was a basic optimiser that performed the start calculation using only an internal temperature sensor. There are no exact replacements for this controller available. What is available? The Schneider Electric DC1400 Optimiser / Compensator is the recommended replacement, but this is not a direct replacement. Differences in the controllers. The SVT controller provides only an optimum start, the DC1400 provides optimum start and stop. The SVT controller uses only a room temperature sensor for the start calculation, the DC1400 uses only a room temperature sensor and an outside temperature sensor for the start/stop calculations. The SVT controller has a dedicated "Boost" relay, which allows overriding of a CSC compensator, and control valve. This is an internal function with the DC1400 optimiser/compensator. The DC1400 has many other built in functions.   Controller wiring - Modifications will be required. SVT general wiring connections. Relay R1 is the main plant relay and relay R2 is the boost relay. To see the full controller details, please click SVT Optimiser DS2001 0210.pdf DC1400 general wiring details.   To see the full controller details, please click DC1400 DS2044A.pdf Controller Sensors As already indicated, the SVT controller uses only a space temperature detector, and this sensor is NOT suitable to use with the DC1400. The DC1400 controller will, as a minimum, require a room temperature sensor and an outside temperature sensor, meaning that extra wiring for the outside temperature sensor, and the sensor itself, will need to be installed. For details on suitable sensors, please refer to What sensors does the DC1400 optimiser/compensator require?

Issue After successfully logged into Xenta Server web pages, java loading icon will be displayed as shown below. However, after a while it will automatically log the user out as shown below. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers 5.1.6 (Xenta 511, Xenta 515, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) Java 1.6 update 29 Note: This behavior may happen on other Xenta Server versions with different Java versions. Please refer to the Cause section for the reason. Cause Vista may not support the newest Java versions. For Vista 5.1.6, the recommended Java version is Java 1.6 update 20. Please refer to Recommended Java version for TAC Vista 5 for recommended Java version details. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs. Find Java application (in this example is Java(TM) 6 Update 29), and select “Remove”. Reload the Xenta Server webpage, will find the Java icon will not be displayed this time. Instead, “Download Java” request link will be displayed. Click on the link and download the supported version of Java. The issue should be solved after the recommended version of Java is installed.

Issue What version of Microsoft.Net Framework and ASP.NET is used by Webstation 5.1.9? Product Line TAC Vista Environment Vista Webstation 5.1.9 Cause ASP.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. TAC Vista Webstation is developed using ASP.NET, which is a part of the Microsoft.Net Framework. Resolution TAC Vista Webstation uses Microsoft.Net Framework 4 and ASP.NET 4. For details on additional Vista versions and the .NET framework and ASP.NET versions required please consult the compatibility matrix in the Supported version of .NET framework and ASP.NET for Vista software.

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue Right clicking the controller and selecting "Distribute Personnel" results in NO distribution There is no error Product Line Andover Continuum Environment CyberStation Cause Corrupted Personnel Distribution table in SQL ContinuumDB Resolution Truncate table PersonnelDistribution and re-populate it, then distribute personnel once again. WARNING: Unless knowing exactly what you are doing, deleting entries from your database can cause irreversible harm to your database and can potential cause corruption. Make sure to perform a full SQL Database backup before attempting to make any changes to the database. (See Move / Backup / Restore a database on a Single User SQL2005 Express system for details on how to backup your database and if not already installed, where to get Management Studio from) Make a backup of the Continuum database as a precaution. Close ALL CyberStation workstations. In SQL Management Studio execute the following query. truncate table PersonnelDistribution Once the table is truncated it must be re-populated by one of the following methods... If the total number of personnel objects is reasonably small (in the hundreds) launch Continuum and bring a list view of all the personnel objects, select all then right click and perform a 'Send to controller' OR In SQL Management Studio Invoke the stored SQL procedure that initializes the PersonnelDistribution table using the query dt_DIST_Init_Personnel_Dist_Table IMPORTANT: Truncating the PersonnelDistribution table will remove all pending personnel distribution including personnel deletions; controllers could potentially continue to allow access to doors for the deleted personnel until reloaded. Conversely, removing a pending personnel distribution could potentially cause a person to be denied access at a door until a distribution is performed to the controller.

Issue What are the bCX and b3 COV subscription limits? Product Line Andover Continuum Environment CyberStation bCX4040 bCX4920 b3 devices Cause Confusion on the limits for COV subscription in the Continuum BACnet devices. Resolution The b3 controllers are restricted to 32 devices, which means they can simultaneously establish  COV CLIENTsubscriptions with up to 32 different devices (Andover Continuum or third-party). The bCX1 and the b4920 permit COV CLIENT relationships with up to 255 devices. These limits are device limits and NOT point limits, so if a bCX has established COV subscriptions with 500 points on device X, it can still set up multiple COV subscriptions with up to 254 other BACnet devices. IMPORTANT- See Limit of how many devices a Bacnet controller can know about (Known devices). This limit does not apply to the number of other controllers which a COV exporter can deliver COV data to as a COV SERVER. For instance if a particular controller had a global point like OAT that 50 other controllers wanted and subscribed to this particular controller for that COV, 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 stated regarding this example however. 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.

Issue Need to bring Continuum system into SmartStruxure. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation v1.3, Continuum v1.94 system with BACnet bCX and b3 devices Cause b3 devices under the bCX become BACnet devices as if they were 3rd party BACnet devices. Resolution Test Environment: Cyberstation 1.94, SmartStruxure 1.3 Released, (1) AS-B, (2) bCX4040, one bCX hosting (2) B3 devices. Do BACnet discovery from SmartStruxure. Both bCX's and the b3 devices can be seen From the Hardware\BACnet devices folder, multi-select both bCXs and drag them into the BACnet Interface\IP Network. Upload their BACnet objects to SmartStruxure. From the Hardware\BACnet devices folder, multi-select both B3 controllers and copy/paste them into the BACnet Interface\IP Network. The B3 devices are hosted as, and look like, generic BACnet devices. Once the two B3s have been copied to the IP Network, an upload to SmartStruxure can be done. BACnet Digital Values and BACnet Analog Values on the b3 devices can be seen updating on a SmartStruxure listview. Note: Currently in SmartStruxure v1.3 there is no method to multi-select and host B3 Devices, within an MS/TP network. This functionality is part of the Continuum Migration project (a future version). Also check out the b3 VAV Quick Start Video on the Exchange.

Issue Does Port Based Network Access Control Ethernet 802.1x apply to Continuum controllers? Product Line Andover Continuum Environment Continuum Ethernet Controllers Cyberstation Cause A question that may be asked by Customers IT Departments Resolution No, the 802.1x protocol is not applicable to controllers, it is a Port based Network Access Control (PBNAC) that is used by Routers and computers. It is related to the Operating system user accounts and policies so is above and outside the scope of Continuum. Not all devices support 802.1X authentication. Examples include some network printers, Ethernet-based electronics like environmental sensors, cameras, and wireless phones. For those devices to be used in a protected network environment, alternative mechanisms must be provided to authenticate them. One option would be to disable 802.1X on that port, but that leaves that port unprotected and open for abuse. Another, slightly more reliable option is to use the MAB option. When MAB is configured on a port, that port will first try to check if the connected device is 802.1X compliant, and if no reaction is received from the connected device, it will try to authenticate with the AAA server using the connected device's MAC address as username and password. The network administrator then must make provisions on the RADIUS server to authenticate those MAC-addresses, either by adding them as regular users, or implementing additional logic to resolve them in a network inventory database. Many managed Ethernet switches offer options for this. Network Security is an available option add on for IP level controllers. Please refer to IPSEC and Network Security on Controllers for more information. Another potential option would be to secure the controllers on a separate VLAN.

Issue Muster Report triggered to generate and print Product Line Andover Continuum Environment Muster Reports on a Continuum site Cause With Muster Report loaded, can you trigger from a input (example: fire alarm) for a report to be generated and automatically print? Resolution With some workstation PE programming, you can launch the Muster Report to automatically print. You will need to install and configure the "Plain English Alarm Function" available from Can Plain English interact with the Continuum Alarm Engine? This will trigger a workstation Function each time an alarm is received. You will write PE code to detect the specific alarm and/or point, then "Shell" to launch the Muster Report. Please find the attached Muster Report User Guide and .dmp file which is renamed as .txt file which should be useful.

Issue Knowing the procedure to follow when hosting a site license for the first time with Vista. Product Line TAC Vista Environment Vista Licensing Cause The TAC licensing website is divided up into different areas depending on the task to be performed. An account must be created the first time using the site before creating a license file from the entitlement ID. Resolution Note: In order to rehost an existing Vista license file, see Rehosting a Vista 5 License on the FlexNet License Server. Log onto https://schneider-electric.flexnetoperations.com/flexnet/. Click on the link that says "New User?".   Fill out the entire page with your information. Insert the Entitlement ID that was purchased in the space titled "Activation ID". Once everything has been filled out, click Complete.   This will log you into the Start Page of the licensing site. A temporary password will be emailed to the address you provided on the New User page. This temporary password is required to set your new password which can be done by clicking on Profile in the top right corner of the screen.   Enter the temporary password into the "Old Password" field. Then enter your new password into the "New Password" and "Confirm Password" fields. Click Save.   On the left side of the Start Page, click "Activate" underneath Manage Entitlements.   Check the entitlement ID that you want to use and click Activate.  Fill out all of the information on this page. Click Next.   Click on "Add New Host" at the top of the Server Hosts panel. Select MAC address or Hardware dongle as the Server Hosts. Type in the MAC address of the computer or the dongle ID of the hardware dongle that the license file will be associated too and click OK. In order to find out the MAC address of your computer, reference How to locate a computer's MAC address.   Check the box next to the host name that was just added. Click Next.   Enter the number of licenses you would like to activate in the "Fulfill Count" box and click Verify. The file should verify successfully. Click Next.   Review all of the information. Click Generate.   Select the box next to the newly created license file. Either select to "Save to File" (save a copy of the license file to the local PC) or "Email License" (email the license file to a desired address). Click Complete.  

Issue The TAC Xenta group master is online but not the other Xenta devices in the group. Product Line TAC Vista Environment TAC Vista 5.1.x Classic network Menta 5.1.x Cause The TAC Xenta Group Master is a TAC Xenta 301/302/401/901 (in the TAC Xenta Group) that monitors the on-line and off-line status of the TAC Group and its members. The Group Master forwards the on-line and off-line information to TAC Vista. If devices have been added it's possible that  the current group isn't updated. Resolution The entire Xenta group must know it has a new device for proper communication to occur. To accomplish this download the applications and parameters to the entire group.  If the Group master goes offline, the whole group will be considered off-line by TAC Vista. The separate on-line group members, however, can send alarms and other information directly to TAC Vista as usual. Information about resolving this issue with an LNS network can be found in Xenta Programmable Device is Offline in Vista but Online in LonMaker.

Issue References Guide and changes from release 1.3 to release 1.4.x and forward Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with regards of release 1.3 to release 1.4.x Cause In release 1.3 and earlier the reference system was relaxed allowing for bindings to be created in ways that made the applications error prone. In release 1.4 this is now being more strictly controlled, which will allow the system to: Help the user to not unintentionally create faulty combinations of references, resulting in bad/unpredictable application behavior and last man win situations Better understand and control how references will behave in copy/paste/move/delete situations. Improve performance in the system, e.g. the limitation of variable connectors is removed. For the complete Reference Guide, please download the pdf from the Download Center For instructions on how to upgrade an Automation Server and how to get the conversion log, See Upgrading Automation Servers from 1.3 to 1.4. For explanations of the entries found in the conversion log, See AS Conversion Log Analysis. Resolution What has changed There are 2 areas which have changed:   1. Rules Programmatic control: A reference means that data is sent from A to B. In Release 1.3 it was possible to send data from A to B and from C to B. This gave a "last man win" situation. In Release 1.4 it is only possible to send data from exactly one source to a recipient. This means A to B and C to B is no longer allowed. User control: This is where properties are displayed in graphics, watch windows and other client components. In release 1.3 it was possible to change a property that was programmatically controlled. This gave a "last man win" situation. In release 1.4 it is not possible to change a property as a user if this property is programmatically controlled by something else. The property will automatically be read only for the user.   Public signals: In release 1.3 and earlier, it was possible to programmatically control a public value in programs. Public signals are intended to be used for user control, while inputs are intended for programmatic control. In release 1.4 this is now changed to the following: Public signals in programs (FB/Script/Menta) can be referenced by user control - NOT by programmatic control Public signals intended for programmatic control must be changed to inputs and rebound. This will give the following benefits: Public signals cannot be forced, while inputs can. If a user needs to take control of a programmatically controlled input, via e.g. graphics or watch window", he will force the signal and there will be no risk of a program overwriting the user value. As stated above - if an input is programmatically controlled, this will for the user be read only. However, force is still possible. There is no more risk for "last man wins" situation between user control and programmatic control. The system will remove any ambiguity with these new sets of rules. Update: Release 1.4.1 and later version add the feature of binding to PVB/PVI/PVR back. But for Script, it still keeps the same. LonWorks Local Node nvis: In release 1.3 it was possible to programmatically write to local node NVIs. These NVIs exist to receive data from the LonWorks network. This gave a "last man win" situation. In release 1.4 it is no longer possible to programmatically control local node NVIs.   2. Definitions In release 1.3 a reference could be a) relative b) system absolute c) server absolute In release 1.4 a reference will be a) "normal" b) Locked A reference created by the user will always be normal (which means relative). In the bindings view the user can then choose to "lock" a reference (which means server absolute). The references will behave identically until a copy/paste (or import/export)  operation is done.         Upgrade Upgrading from release 1.3 to release 1.4 will apply the new sets of rules. It is there for very important to read the log to understand if any existing references in release 1.3 will be impacted during the upgrade For AS: In the Device Administrator the logs are available before the upgraded DB is deployed to the AS. It is up to the user to either examine the upgrade log, make changes in running release 1.3 and rerun the upgrade, or to make the changes after upgrade. It is recommended to do changes prior to upgrade to ensure a fully functional system directly after upgrade. Some warnings are benign and can be disregarded, please refer to release notes for more information. IF an upgrade detects that references will be impacted, the user will be informed about this with a orange progress bar indication and a written information that the upgrade succeeded with warnings. After upgrade, all invalid or unresolved references will be visible from WorkStation for further examination if needed.

Issue Many customers still have a requirement to run Lonmaker 3.13, but have project specific issues related to software fixes in newer version of LNS Server, and an LNS Server upgrade is required. Product Line TAC Vista Environment Echelon Lonmaker LNS Cause Older versions of Lonmaker 3.1 and LNS server had multiple defects that were addressed in later version of Lonmaker Turbo and LNS Server Turbo. However, it is possibly to run Lonmaker 3.1 and only upgrade the LNS server engine to take advantage of software fixes over time. Resolution NOTE: Any LNS Server version older than 3.10 needs to first be upgraded to 3.2x before 3.2x service packs can be installed. Also, please take into consideration that after upgrading the LNS Server on a system that any other system that needs to open that same database will have to be at the same version or higher. For example: a database upgraded to 3.27 can not be opened on the machine running 3.08.   Please follow these steps for upgrading LNS server to 3.22 and finally up to 3.27: Identify what version of Lonmaker and LNS server are currently running on the system. Please see How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS Server currently running. As seen in the screen shot below the system is running Lonmaker 3.13.10 with LNS Server version 3.08. Download LNS Server 3.22. Once this file is downloaded please unzip all of the contents to the desktop of the local machine. Run setup.exe from the extracted files in the LNS Server 3.22.zip, and step through the installation process. Once the installation of 3.22 is complete please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.22. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.22 like below: Now that the system is upgraded from LNS Server 3.08 to 3.22, service pack 7 should be installed to upgrade the system to LNS Server 3.27. Please download LNS Server/Turbo edition Service Pack 7 file to your local machine. Unzip the contents of the LNSServerTurboSp7.zip to the desktop of the local machine, and run the LNSturboServerSp7.exe file. Step through the installation process. When the installation is completed please reboot the machine. After the machine has rebooted please verify that the system is now running LNS Server 3.27. Using How to determine what version of LonMaker and LNS Server on a computer for instructions on how to find the current version of Lonmaker and LNS server the system should now show LNS Server version 3.27 like below:

Issue Webclient currently unavailable Error 80070005 Check your DCOM permissions when launching webclient or webclient is currently unavailable. Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause A remote reboot will not write DCOM permissions the same way a local reboot does. Other Server configurations can cause this. Resolution A webClient installation was performed using Windows Remote Desktop or some other remote access software and the reboot after the webclient install was executed using the remote software. To fix this, reboot the Webclient server directly from the server itself. There are security permissions that do not get written properly when rebooting remotely and a direct reboot corrects this problem. Start Continuum on the Webclient PC locally, not remotely. Be sure Continuum has been started on the webclient PC. Also see, Webclient unavailable error when attempting to logon which mentions making sure the Network Service is selected for the default app pool. 64-bit OS will cause this error as well. Webclient versions pre 1.94 are not supported on any 64 bit platform. If that doesn't work then a complete reinstall and reboot on the server will be required. Remote installs are typically problematic. If changes were made to .net try the following steps: Start> Run> cmd (Enter)  To get to a DOS prompt cd\Windows\microsoft.net\framework\v2.0.50727 (change directory to this folder) run the command aspnet_regiis.exe -i (It will say installing .net, this re-registers .net with IIS) Restart Windows on the webclient PC and restart Continuum

Issue When trying to add a Xenta 421A, 422A, 451A or 452A I/O module in Menta to a Xenta 300/401, the following warning is displayed. Tam32 Warning, IO modules of type TAC Xenta 421A, 422A, 451A and 452A requires at least system program version 3.6. Environment Menta Vista Xenta 301, 302, 401 Cause To utilize the full functionality of the "A" series I/O modules, the version of Menta and firmware in the associated programmable controller must be compatible. Resolution Use the Xenta 4XXA modules as old 4XX modules The I/O modules with an "A" in the name can be used with programmable controllers earlier than 3.61 as well as Menta earlier than 4.2.2 but the functionality will be limited. The functionality is limited to that of the modules' predecessors, modules without the letter "A" in the name (Xenta 421, 422, 451, 452). The TAC Xenta 421A/422A modules can only have digital inputs and the TAC Xenta 451A/452A modules can only have four 1.8k ohm thermistor and four limited universal inputs (digital input, 1.8k ohm thermistor or 0-10 V). In any running system with TAC Xenta 300/401 version 3.X, TAC Xenta 421, 422, 451, and 452 can be replaced with an "A" module the same way as an old module. The "A" module will detect that it is sitting in an old environment and behave as an old module. Use the full functionality of the Xenta 4XXA modules In order to gain full functionality of the "A" modules, the firmware in the Xenta 300/401 controller must be upgraded to a version 3.61 or higher and Menta must be version 4.2.2 or higher. Instructions on how to download a .MOT file can be found in Download an .MOT file into a Xenta Programmable controller. The additional features of these controllers include all inputs are universal inputs (0-10 V, 0-20 mA, 1.8k ohm and 10k ohm thermistor), universal inputs set as digital inputs can act as a pulse counter, and all configurations, inputs, and outputs can be accessed by means of the SNVT interface. Note: If updating the firmware in a Xenta 300/401 and the following conditions apply than see the Xenta Programmables section of The new program interface does not match the previously defined program interface. (Subsystem: NS, #59). Working on a database with multiple Xenta programmable controllers that reference the same device template A firmware version earlier than 3.52 is installed

Issue When upgrading to a different revision of software in I/NET Seven, there are a few steps that are highly recommended to ensure that the database doesn't get corrupted during the upgrade. Product Line TAC INET Environment I/NET Seven Cause Performing an upgrade of I/NET Seven software. Resolution Close I/NET Start DB Create and select the Verify Database option. Verify that the database has 0 differences. Select Upgrade Database to force an upgrade Select the Verify Database option again. Now back up the database to the local drive or media and proceed with the upgrade. Once completed, Select Restore database and proceed to where the back up is and restore the database to the system.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Cannot find any installation instructions documentation for the WorkPlace Tech Tool software, versions 5.8 or 5.8.1. Product Line TAC IA Series Environment WorkPlace Tech Tool software version 5.8 & 5.8.1 Cause An updated version of the document "WorkPlace Tech Tool Version 5.7 Installation Instructions" has not yet been released by our publications group. Resolution The existing "I/A Series WorkPlace Tech Tool Version 5.7 Installation Instructions", F-27367 can be used for installing the release 5.8 or release 5.8.1 of the WorkPlace Tech Tool software. There are two items applicable to the newer versions of the WorkPlace Tech Tool software that are not covered in the published installation instructions. The WorkPlace Tech Tool software, releases 5.7.7, 5.8 and 5.8.1 will run on the 32 bit versions of Windows-XP, Windows Vista or Windows-7.  These releases of the software will also run in XP-Mode under the 64-bit version of Windows-7.  See I/A Series (Niagara) R2 Windows Compatibility Matrix and the linked PA-00163 product announcement for more information on Windows 7 compatibility.  Make sure that the computer meets or exceeds the recommended requirements, not the minimum requirements, for the operating system being used. Beginning with release 5.8.5 of the WorkPlace Tech Tool software, Windows 7 64-bit Professional and Microsoft Visio 2010 is supported (32-bit version only), in addition to the documented Microsoft Visio 2003 and Microsoft Visio 2007 (32-bit versions). The use of Visio 2010 and its ribbon bar menu system are described in the WorkPlace Tech Tool release 5.8 release notes.  This same version of the release notes (5.8) is applicable to the use of Visio 2010 with the WorkPlace Tech Tool software release 5.8.1.

Issue What is the unit load of SE8300 that will help me to count how many SE8300 controllers that can be added on AS ComA and ComB Product Line EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices Environment SER8300 room controller SE8300 room controller Automation Server Cause Documentation does not state the unit load of the SE8000 range Resolution The Generic application note AN01 can be applied with answers to the transceiver interface attributes below. The SE8000 range use the ADM4850A transceivers which are a failsafe transceiver (not requiring bias) and reduced 1/8 UL load. In addition the 100K local bias resistors have been eliminated and therefore the 1/8 UL of the transceiver would be the total UL presented to the bus by the SE8000.   Transceiver Xcvr Unit Load Xcvr Failsafe Adaptor Circuit Bias Circuit Bias Load Total Unit Load Isolated 485 Bus ADM 4850A0 0.125 Yes None None 0.125 Yes** ** Unlike the normally recommended interconnection of the communication common/reference (ground) terminal on all bus devices such as documented in the generic application note for the isolated RS485 bus interfaces, the Viconics bus should be operated with the communications REF (reference) terminal open on each SE8000 and not connected to the bus shield wire, or to any other circuit. Based on the above the total number of devices can be calculated as 32/0.125 = 256 The BACnet MSTP standard specifies that the address range for BACnet master devices is 0-127 and therefore an Automation Server is limited to 127 devices per com port (254 total per AS) so this should effectively be the limiting factor.   Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.