Issue Xenta Server reports it is in FAILSAFE mode without shorting out terminals 9 and 10. After connecting via HyperTerminal, restarting and trying to reset the IP address, the screen continues to scroll back to dsh/> Xenta Server has gone offline and can not connect directly to it using Ethernet. The Run light is flashing Green on first start up but then reverts to red and the LON light also flashes red. During boot up it pauses and reports an error (via HyperTerminal) in loading the RAM disk.  IP Address is set to 172.22.1.5 and can not change it.  Not able to load any firmware into the device – error received. "Error: Could not create remote directory." Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server 527, 511, 555 Xenta Server 701, 721, 731 Cause Unknown corruption of the Xenta Server hard drive / flash drive, possibly due to electrical noise. Resolution To attempt to recover this device, try to format the device’s flash drive. To achieve this you can follow these steps using HyperTerminal or an equivalent application: (For further assistance with connecting to Xenta Servers and HyperTerminal refer to Connecting a serial cable to a Xenta 5/7/9xx controller).   Login and type the command FORMAT.  (May require device to be placed physically into the fail-safe mode by shorting terminals 9 and 10). The format command can take up to 3 minutes to complete but you should see the confirmation through HyperTerminal while this is occurring. If you have placed the device into Fail-safe mode, remove the link on terminal 9 & 10. Restart the device, by either cycling the power or typing the command RESTART through HyperTerminal. Set the IP address and IP settings (command SETIP). Install the latest firmware. You can download the latest firmware from The Exchange Extranet; ensure that you use the correct version since there various versions for the Xenta Servers. Run the firmware download to the device. During the download you may receive an error regarding "Failure to get the hardware version from the target device…", select OK Continue the installation The download will then occur, it will take some time and may appear that the software is not responding but this is normal. Be patient and if you don’t receive any errors then all should be ok. The device should now restart, after a 1-2 minute window the “RUN” LED should be a solid green. If after following these procedures, the device is still not responding as expected please send into Repairs via your normal repair process.

Issue TAC Vista Webstation licenses are not released after the Webstation browser is closed. When log into Webstation again, get error message: The following errors have occurred. Please correct these errors and/or contact the system administrator. X No license available Product Line TAC Vista Environment TAC Vista Webstation Cause Closing the Webstation browser does not log out the user. Logged in user needs to use the “Log Out” button (as shown in the picture below) or wait till the Webstation times out in order to log out. The default time out period is twenty minutes. Setting can be changed in Webstation settings. Resolution If need to change the time out period setting, please follow the steps below: Go to “Start/All Programs/Schneider Electric/Web Applications X.X.X/Vista Web Settings” (by default). NOTE: for TAC Vista 5.1.3 and prior, go to “Start/All Programs/TAC/Web Applications X.X.X/ Vista Web Settings” instead.   Select “Preferences/Login and Logout/Automatic Logout”. In the right panel, click on the down arrow to expand the drop down list and choose the desired the logout time period.  

Issue How to set up extended logging. Product Line Andover Continuum Environment Continuum Cyberstation Extended Log Cause Configuration of extended logging. Resolution Sample configuration for extended logging. This example would create enough entries for a 24 hour period. Create an Infinity Numeric Select the logs tab Number of entries (96) Type will be LogInstantaneous (Stores the current value of this point at the beginning of every interval) Interval will be 15 minutes (15 minutes in a 24 hour period is 96 which is what we set for the Number of entries) By default the Workstations are setup for 5 minute checks to the controllers to see if there are extended logs to enter into the database. For more in-depth configuration of extended logging, please review Extended Logs in the Continuum Online help system.  For performance and load balancing please see Extended Logging gaps, performance and load balancing.

Issue Recommended USB to Serial RS-232 adapter Environment I/A Series R2 UNC’s, G3 ENC’s, MicroNet 2000 MN-CIM, and MicroSmart MSC-LIM. (NOTE: MN-CIM is obsolete as of December, 2011. See Product Announcement PA-000164. There is no functional replacement available) Cause PC or Laptop without RS-232 Serial Port (DB-9 male) connector. Resolution IOGEAR (p/n: GUC232A) has been validated to work in the following applications: 1. HyperTerminal  with a direct connection to the ENC/UNC’s serial port (COM1) using RS-232 adapter and Schneider Electric p/n: UNCC-405 (RJ-45 socket to DB-9 socket adapter, null modem) and CBL-RJ45-** (flat silver satin cable). 2. MN-CIM interface module for use with the TAC MicroNet 2000 series controller interface and Air Balance software. 3. MSC-LIM interface module for use with the DMS MicroSmart Controller Interface (equipment with a handheld port). Click here for product data sheet on the IOGEAR adapter

Issue Measuring dry bulb temperature and relative humidity and need to use them to calculate the following Enthalpy Wet Bulb temperature Dew Point temperature Product Line TAC Vista, Ecostruxure Buildings Operation Environment Function Block applications Cause Need to calculate Enthalpy, Wet Bulb Temperature, or Dew Point Temperature.  These values are typically used to compare the latent heat in the outside air versus inside air for economizer cycles, in chilled water applications where condensation must be avoided, or in humidity control applications. Resolution Enthalpy - the total energy of both the dry air and water vapor per pound of dry air. Wet Bulb temperature - the temperature a volume of air would have if cooled to saturation by evaporation. Dew Point temperature - the temperature to which a volume of air must be cooled for water vapor to condense into water. Download the appropriate HFB below: Psychrometric Calculations in US Imperial Measurements Psychrometric Calculations in SI Metric Measurements

Issue Where are the DUI expander objects for the MNB-300 and MNB-1000 controllers in Workplace Tech? Product Line TAC IA Series Environment I/A Series WorkPlace Tech version 5.1 through 5.9.4 I/A Series WorkPlace Tech version 5.10.0 till current Cause The standard stencils do not include an object for Momentary SS or a DUI multiplexer.  Resolution The I/A Series BACnet controllers do not currently support the DUI object directly within the MNB-300 or MNB-1000. An application performing the same basic function was created and factory tested. This application was created as a custom object named "DUI_App". For support of these objects in Workplace Tech 5.1 until 5.9.4, log into The Exchange Download Center and download the file Application Objects_rev1.zip. There is also a detailed DUI_Application_Documentation_rev1.pdf that describes the operation of the "DUI_App". For support of these objects in Workplace Tech 5.10.0 until further notice, log into The Exchange Download Center and download the file Application Objects_rev2.zip. There is also a detailed DUI_Application_Documentation_rev2.pdf that describes the operation of the "DUI_App". Note: VAV box controllers do not have DUI expander objects available. See TB06-02 for additional details.

Issue Satchwell ALE series Linear Actuator requires replacement. Product Line Field Devices Environment Satchwell ALE series Linear Actuator installed on Satchwell MJF, MZ, MZF, VJF, VSF, VZ or VZF series Plug and Seat Valve Body.  Actuator type :- ALE series.  Cause Obsolescence of Satchwell ALE series Linear Actuator. Resolution Replace Satchwell ALE series Linear Actuator with Schneider Electric M800 Linear Actuator and Linkage Kit :-   Linkage kit to mount a M800 actuator to a Satchwell valve (MZ,MZF, VZ, VZF, VSF and MJF) = L2SV Replace ALE Actuator with M800 + L2SV combined part number 880-0650-000 Replace ALE with Auxilary Switch kit with M800-S2 + L2SV combined part number 880-0651-000 Just linkage kit = 880-0124-000 Just M800 = 880-0310-030 N.B.  Should the Satchwell ALE series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E M800 Actuator as appropriate :-  S2 - Two independent 24 volt 4amp AC-1 rated SPDT Auxiliary End Point Switches. (880-0104-000)   Particular care should be taken when selecting an Schneider Electric Forta M800 Actuator to replace an existing Satchwell ALE series Actuator. The Schneider Electric Forta M800 Actuator may be used to replace an existing Satchwell ALE series Actuator but it should be noted that where an existing Satchwell ALE series Actuator has been connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) will also be required. (e.g. Schneider Electric Transformer Type TR60)   Where an existing Satchwell ALE series Actuator has been connected via an independent Transformer, it is possible that the Transformer may have been rated to provide the level of power required by a single ALE series Actuator (9.5VA) only.   In such circumstances the existing independent Transformer may also require replacement by another independent Transformer, rated to provide the greater level of power required by a single Schneider Electric Forta M800 Actuator (50VA) (e.g. Schneider Electric Transformer Type TR60) Details of the Schneider Electric M800 Actuator may be viewed here Details of the Schneider Electric TR60 Transformer may be viewed here

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 Problems with alarms or configuring alarms in Vista Environment TAC Vista Workstation Cause Improper alarm configuration Resolution Here are steps to configure each part of the Alarm  in Vista. Change of State Object - This is the source of the alarm. Right click on a folder in Vista and select New > Object > Change of State Name the object Double click on the object to modify it Provide a description of the alarm and set a priority level if required. Click on the Object Tab and select the Object to Monitor and the Reference property Click on the Alarm Tab Select an Alarm processing control.  These should be located under the TAC Vista Root object. The default is $Alr_Cntrl Fill in the appropriate text field.  Note: "Text for" fields are text issued as the result of the alarm. "Triggering" text should only be used when monitoring a string value. Set Low and High Limit for the alarm to occur Set Minimum change: This is the smallest deviation required to trip an alarm when using numeric values. Alarm Receiver Objects - These objects route alarms that are intended to go outside of Vista. There are 3 types: Print, file, and Mail (email) Right click on a folder in Vista Workstation and select New>Object>Alarm Receiver - E-Mail (or applicable type Name The Object Double Click on the Object to modify it In the General Tab provide the description and appropriate information for your alarm type (email recipient) In the Alarm Fields Tab, select the fields you wish to appear in the printout or email If you are using Alarm Receiver - Video you will need to set the video settings in the General tab and select cameras to record in the Video Cameras Tab Click Okay Alarm Control Group - This allows us to control distribution of an alarm.  Multiple control Groups will allow multiple distribution lists.  From Vista Workstation, right click on the TAC Vista folder (Alarm Control Objects can only be created here) Select New > Object > Alarm Control Name the Object Double Click on the Object to modify it Enter a description Click "Add" and browse to the desired Alarm Receivers Click on the Acknowledge tab and configure appropriate parameters Click on the Time Control Here you can browse to a time variable that will determine when to use the Alternate Receivers list Add Alternate receivers Click OK

Issue A Pelco IWP221-1ES IP camera is being used and configured as a direct camera in Security Expert but the image from the camera is not being displayed in the Security Expert. Product Line Security Expert Environment Security Expert Pelco IWP221-1ES IP camera Cause The wrong URL to the image feed was used. When we use the IP address of camera to display the camera image in a web browser, it requires the Pelco Media plug in or Quicktime but these cannot be used in Security Expert. Resolution Use a direct URL to the camera stream. For the Pelco IWP221-1ES IP camera, use "http://camera.ip.address/jpeg/pull".

Issue When attempting to trust a self signed certificate, the option to permanently trust the certificate is not enabled. When viewing the certificate, you see the message "Bad server certificate" in the field "Issued by" Refer to WebHelp Article 10326 for further information about certificate types Product Line EcoStruxure Building Operation Environment Certificates Cause There can be various reasons why a certificate can not be trusted, and many or these are described in SSL Certificates - Security Certificate Risk warning logging in to WorkStation or WebStation using HTTPS. In this specific case where you see the message "Bad server certificate", the cause is that the certificate is not deemed trustworthy. First of all, you need to check what the reason behind the certificate being flagged as bad is. This is easiest done by examining the "CRL Distribution Points" property of the certificate, to determine which service is checking or affecting the certificate. In this example, we can see that it is ZScaler (a proxy server provider) is listed, so the reason why the certificate is deemed as bad, is most likely because the certificate is self signed, and that is not accepted by the company policy. If disabling the usage of a proxy server on the PC you are working on allows you to trust the certificate, you can confirm that it is an issue with the proxy server not allowing the self signed certificate. For more information about how e.g. ZScaler handles certificates, refer to the How does ZScaler protect SSL traffic article. Resolution Either reconfigure the proxy to allow the self signed certificate, or (the better option) get a proper CA signed certificate. For more information about preparing and importing a CA signed certificate, refer to Preparing and importing a signed CA certificate.

Issue The CPU light condition allows for limited troubleshooting of Expansion Modules Environment Continuum i2 controllers b3 controllers BCX B4920 ACX 57xx Cause Expansion modules require troubleshooting and the CPU light offers some information Resolution The expansion module closest to the controller will blink once at a 2Hz rate. A second module connected to the first expansion module will display 2 short blinks every 2 seconds Incompatible or malfunctioning expansion modules may display the CPU light as a steady ON or ON and then completely OFF When main power supply does not provide enough power for the controller and connected expansion modules, the CPU light of expansion module display a steady ON.

Issue Some controllers do not support direct 0–20 mA current input signals. To ensure compatibility, the signal must be converted into a voltage format that the controller can accept—typically 0–10 V DC. Product Line Satchwell BAS & Sigma, Satchwell MicroNet Environment UNCX96 controllers UNCX32 controllers IAC controllers Satchwell Micronet controllers Cause Certain controllers are designed to accept voltage inputs only. Direct connection of a 0–20 mA signal may result in inaccurate readings or failure to register the signal. Resolution To convert a 0–20 mA signal into a 0–10 V DC signal: Install a precision resistor: Use a 500 ohm resistor with 0.1% tolerance. Connect the resistor in series with the 0–20 mA signal. Measure voltage across the resistor: The voltage drop across the resistor will range from 0 V (at 0 mA) to 10 V (at 20 mA). Connect this voltage to the controller’s Universal Input (UI) or Analog Input (AI). Configure the controller input: Set the input type to standard voltage input (0–10 V DC). Additional Notes Ensure the resistor is rated for the expected power dissipation. This method is also applicable for 4–20 mA signals, with appropriate scaling. Always verify controller specifications before applying this conversion.

Issue When replacing an EP1501 controller, do all doors and schedules have to be recreated? Product Line Access Expert Environment Microsoft Windows Server 2012 or later Microsoft SQL 2012 R2 or later Access Expert EP1501 Controller Access Expert v3 Premise Software Access Expert v3 Hosted Software Cause Recreating all the doors and schedules can cause a lot of downtime during the replacement process of an EP1501 Resolution Open up the instance that the device is configured on From the hardware tree, select the device that needs to be replaced and double-click on it to open a new window Once the replacement device is powered and configured, copy its MAC address and paste it where the old devices MAC address is showing Click save and close at the bottom right of the screen Right-click the controller in the system tree and select Push Controller Database Once the controller comes online again it will start communicating with the sub devices Open up a Live Monitoring Window and verify that events are being properly reported

Issue After launching WebClient logon screen appears but attempt to logon results in "Webclient is unavailable"  Product Line Andover Continuum Environment Windows Vista Windows 7 WebClient Cause Incorrect Internet Information Services (IIS) configuration. Resolution 1. Open Internet Information Services Manager 2. Expand the Computer Name in left pane and click on Application Pools in treeview 3.  Select DefaultAppPool and click Set Application Pool Defaults 4. In Application Pool Defaults dialogbox select Identity under Process Model. A selection control should appear in the second column. Click this button 5. Under Built-in account select Network Service in the dropdown listbox. Click OK 6. Click OK button in Application Pool Defaults dialogbox

Issue The status of a TAC Xenta 301 or 302 does not go 'online' in TAC Vista, although the Neuron Status property of the controller is 'online' and 'Commission and Download' from TAC Vista is apparently successful. Values read "Failed to Read Signal" in a values page of a classic network. Values read "Invalid Address" in a values page of an LNS network (also see [Invalid Address]) Controllers without /N/P (networking and presentation) designation cannot communicate in a Network. Product Line TAC Vista Environment Vista Workstation Vista Server Xenta 301 Cause Attempt to commission a standalone (non-/N/P) TAC Xenta 301 or TAC Xenta 302 in a TAC Vista Classic LON network.  Non-/N/P controllers are designed to run stand-alone and be configured/interact only with a Xenta OP. Resolution Check the sticker on the side of the controller where the controller type, hardware version, and neuron ID are found. Example of a 302/N/P label. Example of a non-/N/P 302 label.    If the sticker does not have /N/P following the controller type, this is not a network presentation controller.  It will never communicate on a network Replace the non-/N/P controller with an /N/P enabled version.

Issue Is there a limit to the number of read/writes available for a BACnet Setpoint object? Environment WorkPlace Tech versions 5.1 and later Cause Not applicable Resolution The BACnet Setpoint object (analog or binary) is used for writing setpoint values to a controller, where it is stored in EEPROM. Observe normal precautions to avoid frequent writes to EEPROM. Excessive writes (typically greater than 100,000) can greatly shorten the life of the EEPROM and adversely affect its reliability. The BACnet Setpoint Priority object (analog or binary) represents a Value BACnet object type, of which the data is read-write accessible. This object can be used to write data to the controller. The Setpoint Priority object provides access to temporarily stored application values, usually setpoints or setup values, that are stored in RAM.  These setpoint values can be monitored and changed via BACnet communications, using the BACnet priority array.  When written from WP Tech, the default value is written to the priority array “relinquish default” location. Only this default value is stored in EEPROM. For more information, refer to the WorkPlace Tech Tool Engineering Guide Supplement (F-27356)

Issue Unable to reload entire database using "Send to Controller" option. The error "Not enough memory" is seen in Distribution View when trying to reload some objects. Product Line Andover Continuum Environment Continuum b3 Series Controllers i2 Series Controllers Cause Data is corrupt in controller Database or individual points such as Infinity Programs have become corrupt and are unable to be reloaded to the controller. Resolution Clear the database in the controller and retry a "Send to Controller" as follows: Open the Device object of the i2 or b3 controller. Go to the "Runtime" tab. Press the "Reset" button to reset the controller and clear its memory. Retry "Send to Controller".

Issue How do you configure VisiSat to communicate with MicroNet or IAC controllers using a port-powered RS-232 to RS-485 converter? Product Line Field Devices, Satchwell MicroNet Environment Satchwell VisiSat Any port-powered RS-232 to RS-485 converter Cause Proper configuration of the RS-232 to RS-485 converter is required to establish communication between VisiSat and field controllers. Resolution Port-powered RS-232 to RS-485 converters such as the LIB-4-485 allow serial communication between a PC and RS-485-based controllers without requiring an external power supply. Power Requirements Powered directly from the PC’s RS-232 port. Ensure the PC’s serial port complies with RS-232 voltage specifications. Most modern PCs (e.g., Dell) are compatible, but some laptops or USB-to-serial adapters may not supply sufficient power. Wiring Guidelines TD (A) → Connect to negative (-) terminal of the controller. TD (B) → Connect to positive (+) terminal of the controller. GND → Connect the shield/screen only at the converter end, not at the controller. ⚠️ Always refer to the converter’s datasheet for pinout and wiring specifics. VisiSat Server Configuration Open the VisiSat Server Client from the system tray. Go to Network Menu → Settings. In the Configure Network Settings window: Set Transport Type to Serial Port Click Configure Serial Port Settings Choose the appropriate configuration based on the controller type: MicroNet Controllers: Use the following MicroNet-specific settings. IAC Controllers: Use the following IAC-specific settings. Click OK to apply settings. VisiSat is now ready to communicate with the controller via the RS-485 converter. Additional Notes The VisiSat Engineering Guide contains additional information regarding the VisiSat server. If using a USB-to-serial adapter, ensure it supports port-powered converters. For long cable runs, consider using isolated converters to prevent ground loops.

Issue Continuum 1.9x and above may fail to install correctly on domain-joined machines. A common error during installation is: "You must have local NT administrative privileges to run this application." Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows 7, 8, 10, 11, Server 2016 and later SQL 2005, 2008, 2012 and later Cause Microsoft SQL installations require elevated local administrator privileges. Domain accounts often lack these rights due to group policies or security restrictions. A local administrator account is required to complete the installation successfully. Resolution Resolution: Create a Local Administrator Account 🔹 Windows 7 / 8 / 10 (Classic Method) Open Control Panel → Administrative Tools → Computer Management Navigate to Local Users and Groups → Users Right-click in the right pane → New User Enter a username and password Uncheck User must change password at next logon Check Password never expires Click Create → Close Right-click the new user → Properties → Member Of tab Click Add → Type Administrators → Check Names → OK 🔹 Windows 10 / 11 (Modern Method) Open Settings → Accounts → Family & other users Under Other users, click Add someone else to this PC Select I don’t have this person’s sign-in information → Add a user without a Microsoft account Enter a username and password After creation, click the account → Change account type Set to Administrator → OK 🔹 Windows Server 2016+ Open Server Manager → Tools → Computer Management Go to Local Users and Groups → Users Right-click → New User Fill in the details and assign to the Administrators group as above 🔹 Command Line (All Versions) Run the following commands in Command Prompt (Admin): net user LocalAdmin P@ssw0rd123 /add net localgroup Administrators LocalAdmin /add Replace LocalAdmin and P@ssw0rd123 with your preferred username and password. 🔐 Additional Notes Ensure the account is local, not domain-based. You may need to disable UAC temporarily for installation, but re-enable it afterward. For Server OS, PowerShell can be used for automation if needed.