Building Automation Knowledge Base

Issue MNL-800 LON SNVT Programming Standards Environment Workplace Tech Tool software (any version) MNL-800 controller application Cause Problems occasionally arise as a result of improper LON SNVT programming and configuration in the MN-800 device application.  These issues include problems with the re-commissioning of the updated controller and potential network variable mismatch situations. Resolution  The following standards will prevent these problems from occurring. Network variables MUST be manually indexed. This prevents issues with the network variables becoming renumbered when application programming changes are made. (See NOTE 1) Change the application "Program ID" any time network variables are added or removed from an application.  To change the "Program ID" use the WPT Hardware Wizard,  (See NOTE 2) Select Hardware Wizard from Application Menu Click [Next] in MicroNet Setup Wizard screen Change the displayed program ID by entering a different program ID or adding a suffix letter/number. Maximum length is 8 characters. Click [Finish] to save the changed program ID and exit the MicroNet Setup Wizard.  In addition, one method of minimizing the need to repeatedly change the "Program ID" as the application is developed and debugged is to add a few extra common SNVT input and output definitions when first creating the application, leaving them unconnected to the application program.  If one of these SVNTs is needed, it is available in the LON network image (XIF file) and it is not necessary to change the "Program ID". If the MNL-800 controller has firmware version 2.0 (or later) installed, the standard nci network variables do not have to be indexed as the highest numbered SNVTs in the application.  It is perfectly acceptable to number them as the first 17 indexed SNVTs. Note that there are 17 standard network variables (12 nci, 2 nvo & 1 nvi), not just ten nci SNVTs. SNVT variable names should be limited to 16 characters or less.  Longer names are accepted by the WorkPlace Tech programming tool but the names will automatically be truncated by the LON Network Management tool when commissioning the controller. In addition, when programming the MNL-800 applications with the WorkPlace Tech Tool version 5.0, or later, it is not necessary to put each MNL-800 application in a separate project. NOTE 1: If using the WorkPlace Tech Tool version 5.8 or above, you can use the "Object Indexer" to automatically number all the network variables for you.  This tool also includes functions for detecting duplicate SNVT index numbers and for detecting gaps in the assigned index numbers. NOTE 2: If using the WorkPlace Tech Tool version 5.8 or above, you can set an option in the Hardware Wizard to automatically generate a new ProgramID and reindex the network variables when compiling the application.  Please be aware that this automatic generation of the ProgramID will require the Echelon network image for this device to be updated in any Echelon compatible network management tool.  Please refer to the documentation for the network management tool to determine what actions will be required. For example, if Niagara was used to manage the LON network, then the old shadow will need to be deleted, a new one added, and the device points rediscovered and the device re-commissioned.  

Issue CSC5252 and CSC5352 Climatronic Compensator Controller display flashing. Environment Satchwell CSC5252 CSC5352 Cause Manual Override Switch is set in a mode other than AUTO (Clock symbol) Resolution Reset Manual Override Switch to AUTO (Clock symbol) mode. N.B. Details of this and other Manual Override Switch mode options and associated selection / de-selection may be found in the Climatronic CSC5352 and CSC5252 Compensator User Guide, a copy of which may be viewed here.

Issue Installing Echelon Network Interfaces on Windows 7 Operating Systems Environment Microsoft Operating Systems: Microsoft Windows 7 (64-bit and 32-bit) Windows Server 2008 R2 (64-bit), Windows Vista (32-bit) Windows XP (32-bit) Windows Server 2003 (32-bit) Echelon Network Interfaces: i.LON 10 Ethernet Adapter i.LON 100 Internet Server i.LON 600 Internet Server PCLTA-21 PCI Network Interfaces PCLTA-20 PCI Network Interfaces PCLTA-10 ISA LonTalk Adapter PCC-10 PC Card Network Interface SLTA-10 Serial Network Interface (requires separate driver) SmartServer and SmartServer 2.0 U10 USB Network Interfaces U20 USB Network Interfaces Cause Installing Echelon Network Interfaces on computers with newer Windows Operating Systems. OpenLDV 4.0 Resolution Install and use Echelon OpenLDV network interface driver version 4.0 and above. You can download OpenLDV 4.0 from the Echelon website here Echelon Network Interface(s) manuals can be found here. Echelon has released OpenLDV 5.0. It can be downloaded from here. 

Issue Need to Export a Trend log file without using Reports Server Product Line EcoStruxure Building Operation Environment SmartStruxure Workstation Cause Customer needs a log file, but does not have Report Server Resolution In Workstation, right click on a Trend and create a new Trend Log List View Once the List populates, click on the Icon showing a green arrow labeled .csv Save the file to an appropriate location. If this is a frequent action, save the Trend Log List View Please Note that this feature is not available in WebStation  At v2.0 WebStation introduced the option to export to Excel, creating an XLSX file, this can be opened in Excel and saved as a CSV if required (this option is not available if WebStation is directly logged on to the AS/P/B)

Issue Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), while Reports from within Workstation work fine.  Receive an error: "The user session is lost, no specific reason has been set." when logging into StruxureWare Building Operation WebReports from Internet Explorer (browser), and get no Reports folder within Workstation. Login Screen appears as expected, but when attempting to log in with the user name/password; It times out and comes with the message 'Failed to establish connection with server.' Product Line EcoStruxure Building Operation Environment Building Operation WebReports 1.1 / 1.2 Cause The error is most likely due to ports been blocked and/or the incorrect port settings entered during the WebReports installation process. When installing (or upgrading) WebReports, you must enter this information on each occasion as this information is not retained from previous installations. If you need to change these settings, then you should follow the procedure detailed below. Resolution If installed on separate machines, then check the firewall settings and ensure the ports used for the Enterprise Server and the Report Server are not blocked.  If this does not resolve the issue or if you are running both the Enterprise Server and Report Server on the same PC, then the Enterprise Server port configuration during the WebReports installation may need to be changed.  This is achieved as follows: this, and follow these key steps: Run the WebReports Installation setup program, and at the Setup Type prompt, select Upgrade from... Proceed through the other options as normal. Once you reach the Reporting Agent setup, make sure you enter the correct URL (path and port number - this is unique for each installation) used during the Enterprise Server setup. Continue through the other settings as required - Ensure that any Path and URL ports are set correctly.  Once you complete these settings, the WebReports Installer package then goes through the following checks and installation: Checking Installation Requirements Pre-upgrade Configuration Installation of Reporting Agent, WebReports, and WebReports Service Post-Installation Configuration Installation PublishedReports After the above steps, the upgrade is completed. This will now allow login to the WebReports URL using your web browser. For additional assistance in installing/upgrading WebReports, refer to the online help website. 

Issue What are the intervals for Trends when using StruxureWare Building Operations Product Line EcoStruxure Building Operation Environment Enterprise Server or Automation Server Cause Questions regarding what the interval in time is for trending Resolution Intervals can be in Days, Hours, Minutes, Seconds, and Milliseconds. . Trend logs can be of different types and used for different purposes. All logs in StruxureWare use circular storage. The interval trend log collects data at a specific time interval. Each logged value is stored as a record in the trend log. Use this trend log when the logging interval is less than 1 hour. You create interval trend logs using WorkStation or WebStation. In WorkStation, you configure the properties of the interval trend log to meet the specific needs of your site. The interval trend log does not record the values between the intervals. An interval log checks the monitored value at each interval and records the new value if it differs from the previously recorded value by more than the delta. Delta is the difference between the current variable value and the last log value. To log a variable according to the time interval, use a delta of zero. You use an extended trend log to transfer records from a trend log. An extended trend log can be connected to a trend log or connected in a series to another extended trend log. Only one extended trend log can be connected to a trend log. You create and configure extended trend logs using WorkStation. The extended trend log is often saved on a higher server level with more storage capacity than the server of an ordinary trend log. This extra storage capacity enables the server to store more records before it overwrites old ones. The extended trend log can be viewed in a trend log list or a trend chart. Trend log lists and records can be exported in two different formats: CSV (Comma separated values) is a standard file format for digital storage of data structured in a table of lists form. The CSV format can be used by Excel and in databases such as SQL. XML (Extensible Markup Language) is a standard file format for structured data and can be use with a lot of different tools. One last suggestion is the number of records, depending on how many records you want to store is important. For example: a single one minute interval Trend Log, and for 66 day, that would be 99,792 records. The maximum is 100,000 on an AS, so take this into account when configuring. This is why Extended Trend Logging is important. Check out Maximum number using StruxureWare Building Operation (Scalability and Capacity) for information on trends and extended trendlogs.

Issue java.io.EOFException    at javax.baja.xml.XParser.read(XParser.java:753)    at javax.baja.xml.XParser.parseString(XParser.java:555)    at javax.baja.xml.XParser.parseAttr(XParser.java:492)    at javax.baja.xml.XParser.parseElemStart(XParser.java:421)    at javax.baja.xml.XParser.next(XParser.java:262)    at javax.baja.xml.XParser.parseCurrent(XParser.java:146)    at javax.baja.xml.XParser.parse(XParser.java:119)    at javax.baja.xml.XParser.parse(XParser.java:102)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:77)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:64)    at javax.baja.workbench.px.BWbPxView.loadPx(BWbPxView.java:176)    at javax.baja.workbench.px.BWbPxView.doLoadValue(BWbPxView.java:90)    at javax.baja.workbench.BWbEditor.loadValue(BWbEditor.java:233)    at com.tridium.workbench.shell.NHyperlinkInfo.loadView(NHyperlinkInfo.java:563)    at com.tridium.workbench.shell.NHyperlinkInfo.hyperlink(NHyperlinkInfo.java:100)    at com.tridium.workbench.shell.BNiagaraWbShell.doHyperlink(BNiagaraWbShell.java:350)    at com.tridium.workbench.shell.BNiagaraWbShell.hyperlink(BNiagaraWbShell.java:316)    at com.tridium.workbench.shell.WbCommands$BackCommand.doInvoke(WbCommands.java:718)    at javax.baja.ui.Command.doInvoke(Command.java:303)   Environment G3 (Niagara) station with px files, any revision level. Cause The px file did not copy correctly. Resolution There are three possible approaches to recover from this situation, as follows: Try copying the file again.   Open the px file with a text editor. It might be possible to determine what was either not copied at all, or what might have been corrupted during the copying process. The example shown below is part of the BoilerRoom.px file from niagara-3.6.47 \ stations \ demo \ px \ plant. Lines 489 through 495 contain 'closing tags' for the Canvas Pane, Scroll Pane, Border Pane, content, and px statements that were opened at an earlier point in the px file. If one or more of these 'closing tags' were not copied, or were somehow corrupted during the copying process, the error would result .  If necessary, restore the px file from a backup.

Issue What fingerprint or faceprint readers does Security Expert support? Product Line EcoStruxure Security Expert Environment Security Expert Fingerprint Reader Faceprint Reader Biometric Reader Cause Require information on what Biometrics readers are supported with Security Expert. Resolution We officially support Suprema, Princeton Identity and IDEMIA biometric readers (see SX SRVR Security Expert - Compatibility Matrix) however our reader expanders/controllers are able to work with any reader that provides a standard 26-bit Wiegand output.   If there is a biometric reader that does this it should be able to be connected to Security Expert like a standard card reader supplying the controller with Wiegand data that is assigned to a user. The enrolling of biometrics would need to be handled by the third party system, we would essentially be treating it as a normal card reader and card.   For a list of Suprema devices that Security Expert supports refer to the Suprema Biometric Integration in Security Expert Application Note. For a list of Princeton Identity devices that Security Expert supports refer to the Princeton Identity Biometric Integration  Application Note. For a list of IDEMIA devices that Security Expert supports refer to the IDEMIA Biometrics Integration Application Note.

Issue Since Generation 1 controllers do not have a controller webpage, how can I access the controller configuration to set up the controller or access controller information. Product Line Andover Continuum Environment Hyper Terminal CX9900 CX9940 CX9400 CX9410 CX9200 Cause 1st Generation Controllers do not have an embedded webpage. Resolution Find information about the pin configuration of the direct connection cable in PinOuts for the RS-232 Connection of the older 1st Generation CX controllers. The following document describes how to log into a generation 1 controller via a PC with a terminal emulation application: CX Operators Guide.pdf

Issue When using EBO's registration page, the registration website that is opened allows the user to login and enter the new system ID, however, the user then cannot proceed any further. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation Cause The link https://registration.smartstruxure.schneider-electric.com/, which redirects to the https://registration.smartstruxure.schneider-electric.com/WebConnectUI/RegisterUser/home This page may not allow the user to complete the site’s registration with the new system ID. Resolution Register the site’s EBO new system ID using the following website address. https://registration.smartstruxure.schneider-electric.com/ebo/Home

Issue WorkPlace Tech will not recognize the Echelon U10 USB Lon Network Interface adapter. The “Loading Device Driver” is displayed but nothing happens after that. Environment WorkPlace Tech 5.8.x Cause LON1 port may have been previously assigned to another LON interface. Resolution 1. Make sure the Echelon Open LVD 4.0 is installed on PC. 2. Close WorkPlace Tech if open 3. Disconnect the Echelon Lon USB adapter from the PC. 4. Open Control Panel and open LonWorks Interfaces 5. Select View from the Menu and check “Show Detached Interfaces” 6. Highlight LON1 in the tree and click the “Remove” from the menu        - Click Yes in the “Confirm Removal” window to remove the detach device 7. While in same widow, reconnect the Echelon USB Lon Adapter to the PC        - The messages: “Installing device driver” will display in the system tray followed by “Echelon USB Network Interface Installed.        - The LON1 interface should now be displayed You can test the communication if you like Now open WorkPlace Tech and you should be able to discover the LON devices.  

Issue "An unexpected error occurred" shown while downloading a LonWorks device through a Xenta Server Product Line TAC Vista Environment TAC Xenta Server (511, 527, 555, 701, 711, 721, 731, 913) TAC XBuilder TAC Vista Server Cause There are a couple of reasons that you can get this error message. One is that SSL 3.0 is not enabled in Internet Options for the Windows user running TAC Vista Server. This will keep Vista Server from being able to download a Xenta controller using a Xenta Server.  It will also not let you download and XBuilder project to the Xenta Server, and you can not connect to the browser of the Xenta Server using Internet Explorer. The other reason could be, that while running Vista Server as a service, the Windows account running the service is Local System and that this account does not have SSL 3.0 enabled. This could also occur if you have enabled "System cryptology: Use FIPS compliant algorithms for encrypting, hashing and signing" in the local policy setting. Resolution Enabling SSL 3.0 Go to Control Panel and open Internet Options. Choose the Advanced tab and scroll to the bottom of the Settings list. Near the bottom you will see Use SSL 3.0.  Make sure the Use SSL 3.0 box is checked. Configuring the Windows account running TAC Vista Server Download the TAC Vista Run Mode tool and run it. Under the Service Logon section choose Local User for the Logon Type, select or write the Windows user name and password. It has to be the account you are currently logged in with, or another user having enabled SSL 3.0 and has administration rights. Restart the service.   Check the local security policy for FIPS Open Control Panel - Administrative Tools -Local Security Policy (or type secpol.msc in Start-->run) Go to Local Policies-Security Options Find System cryptology: Use FIPS compliant algorithms for encrypting, hashing and signing Change to disable, apply-OK Restart XBuilder

Issue How to control an output with one or more inputs. Product Line EcoStruxure Security Expert Environment Security Expert Cause Unsure how to program one or more inputs to directly control an output. Input Control Output Resolution The below guide details how to use an Input to activate an Output on Security Expert and SP-C-WEB systems. An output can be assigned to the Input Type and to the Input allowing many to one and one to many configurations.   In order for an Input to activate an Output it needs two things: To be inside an always armed area - This can be an Automation/Dummy area with its only purpose being to activate the output. To have an Input Type that tells it to activate an Output   Single/Multiple Input Activating the same Output If one or more inputs are required to activate the same output, this output can be defined by the input type. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Set the Control Output to the required output Under Options 2 enable the required control options for your scenario e.g. to have the output follow the input exactly enable Activate Control Output on Alarm and Deactivate Control Output on Restore. To have the output activate for a time simply enable Activate Control Output on Alarm and set the Activation Time under the General tab of the Input Type Menu (Control Output Time) For more details on the option see The difference between using "Control Output" and "Input Control Output" Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following: Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Check for any related health status messages that need to be resolved Arm both portions of the Area Activate the Input to confirm Output Activates   Multiple Inputs Activating Different Outputs When multiple inputs are required to activate different outputs, one input type can be used and the outputs can be defined at each input. The below is a simple scenario where when the Input turns ON the Control Output turns ON, when the Input turns OFF the Control Output turns OFF. Other types of output activations can be configured if required. Creating the Area Navigate to Programming > Areas Add a new area and name it Automation Area, set the Entry and Exit Delay Times to 0. All other settings can be left default. Creating the Input Type Navigate to Programming > Input Types. Create a new Input Type Under 'Options 3' enable the required control options for your scenario. e.g. to have the output follow the input exactly enable Activate Input Control Output on Alarm and Deactivate Input Control Output on Restore. To have the output activate for a time simply enable Activate Input Control Output on Alarm and set the Activation Time at the Output itself For more details on the option see The difference between using "Control Output" and "Input Control Output" Set any other options that may be required Configuring the Input Navigate to Programming > Inputs select the Input and set the following Set the Control Output to the appropriate Output Set the Area to the Automation Area created in Step 1 Set the Input Type to the Input Type created in Step 2 Testing Arm both portions of the Area Activate the Input to confirm Output Activates

Issue What is the replacement actuator for the EM42? Environment EM42 Actuator Cause The EM42 is obsolete. Resolution The EM42 actuator is generally associated with the V280/290, and the V380/390 series valves. The replacement actuator for the EM42 is the Schneider Electric Forta M310 Actuator. Please note that an adaptor kit (880-0252-000) is required for DN15 valves. For a copy of the EM42 data sheet please click HERE. For a copy of the M310 data sheet please click HERE.

Issue In WorkPlace Commissioning Tool, the following error message appears when browsing a BACnet/IP network: "A critical error occurred in the communication server rtmonitor.exe. Please shutdown this application and the communication server then try again." Product Line TAC IA Series Environment Windows 7 computer WorkPlace Tech Tool software version 5.7 or later Cause The WinPcap driver, used in WorkPlace Tech BACnet communications was configured to start on demand and the WPT module that is attempting to start WinPcap does not have the necessary Windows security rights.  Resolution NOTE 1:  Before using this procedure, please verify that the issue noted in WorkPlace Commissioning Tool UDP Port: "A critical error occurred in the communication server rtmonitor.exe" has been corrected, if present, and did not solve the problem. NOTE 2: If the computer is running Windows 7-64 bit, replace the following references to "Program Files" with "Program Files (x86)". To correct this issue, perform the following steps. Open Windows Explorer, i.e., "My Computer" or "Computer" from the Windows Start menu or computer desktop. Open the folder "C:\Program Files\WorkPlace Tech" For each of the following program files listed here, in turn: RTMonitor.exe, WPCT.exe, WPFB.exe and WPTech.exe Right click on the program name, Select Properties from the pop-up menu, Select the "Compatibility" tab. In the Compatibility display, click the button [Change settings for all users]. Locate "Privilege Level" section of the displayed window and check the box "Run this program as an administrator". (See snapshot below) Click the [OK] button to save the settings for all users. The window will close. You will see that the Privilege Level option is no longer selectable. Click the [OK] button to save the compatibility settings.   After setting the privilege option for each of the four programs in the Workplace Tech folder, repeat the same setting change for the Microsoft Visio program itself, VISIO.EXE. Depending on the version you are using, it will be located in the C:\Program Files\Microsoft Office\OfficeXX folder where xx is 14, i.e., Office14, for Visio 2010, 12, i.e., Office12, for Visio 2007 or 11, i.e., Office11, for Visio 2003. After setting these options, the computer should be shut down and restarted before using the WorkPlace Tech Tool software.  

Issue Converting the Velocity Pressure measured by the pressure sensor to Flow velocity (CFM) Product Line Andover Continuum,TAC INET,TAC Vista Environment Air flow measurement / balancing Cause Requirement for converting the velocity pressure to flow velocity (CFM) Resolution To calculate Air Flow in Cubic Feet per Minute (CFM), determine the Flow Velocity in feet per minute, then multiply this figure by the Duct Cross Sectional Area. Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A)   Determining Flow Velocity The easiest way to determine Flow Velocity is to measure the Velocity Pressure in the duct with a Pitot Tube Assembly connected to a differential pressure sensor. The Pitot Tube Assembly includes a Static Pressure Probe and a Total Pressure Probe. A Total Pressure Probe, aligned into the airflow, senses the duct velocity pressure and the static pressure, which equals the total pressure. A Static Pressure Probe aligned at a right angle to the airflow senses only the static pressure. The difference between the total pressure reading and the static pressure reading is the Velocity Pressure. If you connect the Total Pressure Probe to the HIGH port on a differential pressure sensor and the Static Pressure Probe to the LOW port on the differential pressure sensor, then the sensor’s output will be the Velocity Pressure, as shown in the figures below. The Flow Velocity is then determined with the following equation: V = 4005 x Sqrt(ΔP) V = Flow Velocity in feet per minute. Sqrt() = Square root of the number in the parenthesis. ΔP = The Velocity Pressure measured by the pressure sensor Example: Measuring a Velocity Pressure of .75” W.C. equals a Flow Velocity of 3,468 Ft/Min. V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min   Determining Duct Cross Sectional Area After obtaining the Flow Velocity from the previous procedure, that figure is now multiplied by the Duct Cross Sectional Area to determine the Air Flow in CFM. There are two different equations for determining the Duct Cross Sectional Area, one for round ducts and one for square or rectangular ducts. The equation for a round duct is: A = π x r 2 A = Duct Cross Sectional Area π = 3.14159 r = radius of duct in feet The equation for square or rectangular ducts is: A = X x Y A = Duct Cross Sectional Area X = Duct height in feet Y = Duct width in feet. Example: An 18” diameter round duct has a Duct Cross Sectional Area of 1.77 Ft 2 A = π x r 2 or A = 3.14158 x .5625 18” diameter is 1.5 feet, therefore the radius is .75 feet • r 2 = 0.752 = 0.5265 • π = 3.14159 A = 3.14159 x 0.5625 = 1.77 Ft 2   Determining Air Flow in CFM After obtaining the Flow Velocity and the Duct Cross Sectional Area from the previous two procedures, the Air Flow in CFM is determined by multiplying the two: Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Example An 18” diameter round duct with a Velocity Pressure of .75” W.C. has an Air Flow of 6,128 CFM The Flow Velocity is 3,468 Ft/Min. V = 4005 x Sqrt(ΔP) V = 4005 x Sqrt(0.75) Sqrt(0.75) = 0.866 • 4005 x 0.866 = 3,468 • Flow Velocity = 3,468 Ft/Min The Duct Cross Sectional Area is 1.65 Ft 2 A = π x r 2 π = 3.14159 • r 2 = 0.752 = 0.5625 Duct Cross Sectional Area (A) = 3.14159 x 0.5625 = 1.77 Ft 2 The Air Flow in CFM is 6,128 Ft 3 /Min Air Flow in CFM (Q) = Flow Velocity in Feet Per Minute (V) x Duct Cross Sectional Area (A) Air Flow in CFM (Q) = 3,468 Ft/Min x 1.77 Ft2 = 6,128 CFM

Issue General questions and best practices for RS-485 protocol including cable length and terminating resistors Product Line Andover Continuum, EcoStruxure Building Operation Environment MSTP Cause Understanding best practices for installing, cabling, and terminating RS-485 networks can avoid a lot of problems with communication and hours of troubleshooting communication problems. Resolution MS/TP MS/TP stands for Master Slave Token Passing. Each device on the link is considered the master when it has the token. If it does not have immediate need to use the token, it is required to pass the token along to the next device. This is the token passing part. All devices on the link which do not currently have the token are regarded as slaves, and are expected to listen to any messages the current master may have for it. Because all devices take turns being master, the link is effectively peer to peer. Electrically, MS/TP adheres to standard RS-485, physically wired using two-conductor shielded twisted pair cable. RS-485 Cable Specifications Cables used to form the RS-485 network should conform to the following specifications: Wire Size: 22-24 AWG Cable Type: Twisted-pair, copper wire, tinned Shield: Braid Nominal Impedance: 100-120 Velocity of propagation: 78% Capacitance: <12.5 pF/ft between conductors and <22 pF/ft between the conductor connected to ground and the next conductor. Topology Daisy chain bus topology. Star topology can be achieved using Infilink/B-Link repeaters. Maximum Cable Length Cable lengths of up to 4000 ft (1220m) daisy chained from controller to controller on one arm of a star are supported. After 4000 ft (1220m), a signal repeater (b-Link) is required to add more nodes to the network or further extend the cabling. Using a b-Link fiber repeater allows you to extend the length of RS-485 with fiber optic cable, recommended for running cable between buildings and through noisy environments. Maximum Number of Devices TAC's MS/TP RS-485 supports a maximum of 127 nodes overall. Each controller represents a single node on the network. RS-485 Termination The MS/TP field bus requires a 120 ohm terminator resistor at both ends of a daisy chain segment. The following diagram illustrates the connection of the terminator: Also check out the SmartStruxure-RS485-Network Installation Quick-Help video on the Exchange.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue Error: "Could not create remote directory" or "Failed to establish connection with the target device" when trying to upgrade/downgrade a Xenta 5/7/9xx controller     Product Line TAC INET, TAC Vista, Satchwell MicroNet Environment Xenta Servers Xenta 511, 527, 527-NPR, 555, 701, 711, 721, 731, 913 XBuilder Cause This error can be caused by any of the following reasons: Trying to downgrade a Hardware version 2.x Xenta Server device to System Program version 2.10 or older Internet Options are configured to use a proxy server IP communication is not properly established due to incorrect IP settings, a bad cable or a faulty device The controller is 5.1.8 or lower and Microsoft KB 2661254 or KB 2661254-V2 is installed on the PC. In this upgrade Microsoft has changed the criteria for the certificate Key. Service packs are available on the extranet to correct this issue. Download blocked because of other Windows updates SSL 2 and 3 is not activated Resolution First, establish that the System Program that you are attempting to load is compatible with hardware version of the device. The older HW 1 versions can be upgraded to System Program 5.1.2 or older. Only system program versions 2.2.0 and newer can be loaded into devices that are hardware version 2.X. Hardware Version System Program 1.0 5.1.2 or older 2.X 2.2.0 or newer 3.X 5.1.6 SP1 or newer Note: Hardware version 1 devices are not labeled as HW 1 since only one version of hardware existed at the time. Hardware devices can be identified by the lack of any hardware version printed on the Neuron ID sticker. Note: If running the firmware update software, ensure you are running as an administrator. Next, check to verify that IP communications are configured properly and are functional: Check the IP address defined in XBuilder Verify a good connection to the IP port of the controller (10Base-T port on the far right) with a crossover cable. If that is all good, then a reformat of the controller may be necessary. Connect via Hyperterminal to the unit and at the dsh> prompt type format and press enter command . This will recreate the directory structure of the controller and allow you to attempt the upgrade/downgrade again. Finally, verify that the Internet Options are not configured to use a proxy server or, if they are, temporarily change them as follows: To temporarily change this setting follow these steps: In Internet Explorer select the Tools Menu and select Internet Options. Or select Internet Options from your Control Panel. Go to the Connections tab. Click the LAN settings button. Uncheck the Use a proxy server for your LAN box. Click Ok in the LAN settings window and the Internet Options window. Complete the System Program download. Return to the Internet Options window and re-check the Use a proxy server for your LAN box in the LAN Settings found in the Connections tab. Another Matrix explaining the compatibility of each with Vista versions can be found in Xenta-Server-firmware-versus-Vista-Server-versions If you have the Xenta FW 5.1.8 or lower and KB 2661254 or KB 2661254-V2 were installed during a Windows Update you will need install the service packs. These new service pack builds have been released and are available on the extranet. See TPA-VSTA-12-0028.00 - TAC Xenta Servers, Not Possible to Download Firmware for more info. Another issue has been reported to support relating to the bit length of the Xenta server boot certificate. The Xenta server installer uses a 512 bit key length of the boot certificate, and Windows in some instances can be configured for a 1024 bit length certificate. If the issue still exists after removing the above mentioned Windows Updates, or if you are getting this error and the Windows Updates are not on your machine. Download the attached tool, Allow Weak Certificates.zip, and execute the file, chose "Allow Weak Certificates", and "Update".   Here is what the tool set: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\OID\EncodingType 0\CertDllCreateCertificateChainEngine\Config] "EnableWeakSignatureFlags"=dword:00000002 "minRSAPubKeyBitLength"=dword:00000200 If taking the preceding steps fails to resolve the issue then see the following articles for additional steps that can be taken: Xenta Server "Run" light is solid red, with no communication via Ethernet,  Fail to upgrade the TAC Xenta Server system software (firmware)  An unexpected error occurred while downloading using a Xenta Server

Issue Running I/NET Seven as a service on Windows Product Line TAC INET Environment I/NET Seven All supported Operating Systems Cause When you log out of Microsoft Windows or restart the computer, all running processes are shut down. These processes are not resumed at log on or at restart. You have to start I/NET manually again. To get I/NET to start up when the computer restarts, you can run it as a service. Running a program as a service means that it runs in the background, but it is not visible on the Windows task bar. Resolution Use the INET Run Mode tool available on the Community.  Alternatively, you can perform the following steps to set/unset the InetIoSrv.exe as a service or application. To register I/NET Seven to run as a service Open a Windows command prompt. Go to Start > Run and type "cmd" Use right-click on the command prompt and select "Run as Administrator" Use commands cd.. (to go back one directory) and cd (to go into a folder) to navigate to the following location: C:\Program Files\INET Seven\ If this is being run on a 64 Bit OS, the location then would be: C:\Program Files (x86)\INET Seven\ Type the following command. This will unregister I/NET as an application inetiosrv /unregserver Type the following command. This will register I/NET to run as a Windows service inetiosrv /service To verify the changes have taken effect Right-click on "My Computer" and select "Manage" Select Services and Applications > Services Look for Inet7Iosrv. It should be set to Automatic. You are now running I/NET as a service. IOSrv will now be running in the background when the PC boots up. This does not require a Log On to the PC, however, you will have to Log On to the PC as a user to launch I/NET or AMT from the desktop icon. You will notice that IOSrv has been logging all AMT transactions, messages and alarms. The SQL Server and Agent were also running in the background receiving data to the database. To set I/NET back to running as an application Open a Windows command prompt. Go to Start > Run and type "cmd" Use right-click on the command prompt and select "Run as Administrator" Use commands cd.. (to go back one directory) and cd (to go into a folder) to navigate to the following location: C:\Program Files\INET Seven\ Type the following command. This will unregister I/NET as a service inetiosrv /unregserver Type the following command. This will register I/NET to run as an application inetiosrv /regserver

Issue What is the latest specification For a Continuum PC Product Line Andover Continuum Environment Cyberstation SQL Server Cause Computer specification required. Resolution The PC specifications for a version does not change from the time of release, so there is no "Latest Specification" as such. For all versions the hardware requirements are defined in the installation guide (Installation.PDF) on the software CD, or in the downloaded zip file from The Exchange Download Center for the version to be used. This document will contain the minimum and recommended specification required for that Cyberstation version on a typical site, if any other software is to be installed on the computer or the computer is to be heavily loaded; the requirements should be increased accordingly. The same RAM and Processor requirements will also apply to the SQL Server on a typical LAN system. You also need to check the Software and Firmware compatibility matrix for older versions of the traditional product lines for details on the compatible operating system requirements for the version to be used. For a V2.01 system the recommended hardware for servers and workstations are: Intel 8 Cores, 2 GHz or better 8Gb RAM 30Gb Available HDD space (NTFS Partition) CD ROM Drive Video resolution: 1024 x 768 pixels Parallel or USB port For larger systems and where there will be a lot of Extended logging or Alarming, the Hard drive, RAM size and processor speed should be increased.