Building Automation Knowledge Base

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. 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 SP-C Controllers randomly going offline / online.  Restarting the controller resolves the issue for a short period of time. SP-C Controller ports showing TIME_WAIT when a netstat command is run. Product Line EcoStruxure Security Expert Environment Security Expert Controller (SP-C) Cause Under normal conditions an SP-C needs to update the Security Expert Server with new data. During this time the IP Socket of the SP-C is in a Waiting State, refusing to communicate to anyone else while waiting for an opportunity to upload. Once the controllers data has been uploaded to the server however the controller releases the IP Socket and it is open again to new communication. In an extremely small number of cases the SP-C controller goes into this waiting state as usual but then never comes out of that state, holding onto the IP Socket forever and blocking any further communication until the controller is power reset. This only affects a very small percentage of SP-C controllers running Microsoft Windows CE OS Version 16. Resolution In these extremely rare cases the first step is to identify if the affected controllers are indeed running OS Version16.  For SP-C Firmware builds before 2.08.921 Log into the controllers configuration web page. Browse to the Configuration tab. Check the OS Version field at the bottom of the page. For SP-C Firmware build 2.08.921 and above the OS is now shown in a different location.   Once it is clear, that the OS is version 16, Product Support can be contacted to arrange to upgrade the controller OS to Version 20 (or greater) as is found in SP-C controllers shipping now. As this is a high risk procedure and can result in complete failure of the controller if anything goes wrong there are two options for upgrading the OS. Install the affected controller on a test bench with remote access for Product Support to remote in to and perform the update. Have the controller sent back to the factory to be updated and returned to site. Both options will require replacing the controller with temporary stock while the upgrade is being performed.

Issue Security Expert does not run correctly after installation Product Line EcoStruxure Security Expert Environment Security Expert Cause While Security Expert will install and run correctly on a supported platform, there are occasions when an installed security policy will prevent the correct operation of Security Expert.  In the example below, the installation went smoothly, but when the user tried to log in to Security Expert the error "Error - Exception has been thrown by the target of an invocation" is seen. Thus the install could not be licensed. This example had SQL, Security Expert Server and Security Expert Client all installed on the same PC. Exception has been thrown by the target of an invocation Resolution If the new install does not run correctly, then install the software on a clean Windows platform, this will allow the site to be set up and commissioned. In the above example, the customers extra security policies were applied one at a time until the policy that caused the problem could be isolated.  

Issue During the installation of Workstation on a PC that didn't previously had any SmartStruxure software installed, you can get the message: "Failed to install XXXX redist, error: 3010" Product Line EcoStruxure Building Operation Environment Workstation Cause One of the build in Microsoft Visual C++ Redistributeable (VCRedist) installers (2008, 2010, 2012) is failing for some reason. Resolution Restart the PC and start the installer again Note: There is a similar issue but with error 1603, if you get this please see Getting the error "Failed to install XXXX redist, error: 1603" during installation.

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 Services for assistance. Issue Upgrading the MPMs firmware through the boot loader was unsuccessful. 10.50.80.2 is pingable, but not the default IP 10.50.80.3. The LED's keep blinking in tandem (alternating one after the other), even after having the MPM powered over 10 seconds. Product Line EcoStruxure Building Expert Environment SmartStruxure Lite Multi-Purpose Manager Cause This can be triggered by multiple events: - MPM was interrupted (powered off) while the firmware was still being upgraded. - Database does not exist; MPM was formatted and does not have firmware installed. - Database is corrupt (for any reason) Resolution It is strongly recommended that a firmware upgrade be done via the "File Manager" tab in Building Expert. However, if this is not possible, an upgrade can be performed through the bootloader using the following steps: 1 - At the top left part of the screen, make sure "Status" says "Connected". 2 - Format the SD card clicking on the "Submit" button next to "File System Format". "Format Done" will be displayed next to the button once the format has been completed 3 - Click on the "Browse" button and Navigate to the Firmware_update_V2.XX.bp" on your computer then click on "Submit Query". 4 - The previous step will upload the firmware file to the MPM's SD card. Once the file has been transferred, the following message will appear: or 5 - The MPM Must be kept powered-up for at least 15 minutes in order to allow the MPM some time to unpack the firmware file. The best way to determine whether the MPM is back online is to ping its IP address using a "Command Prompt" window. 6 - Once the MPM replies to the ping, Building Expert can be accessible though 10.50.80.3   If the above solution does not work; meaning that every time a new firmware is pushed to the MPM, the MPM keeps coming back to the bootloader, contact technical support

Issue Steps on how to setup BACnet Time Synchronization to 3rd Party BACnet controllers. Product Line EcoStruxure Building Opertaion Environment SmartX Enterprise Server (ES) SmartX Automation Server (AS) BACnet Cause It is not always clear what is required to setup BACnet Time Synchronization and how to confirm that EcoStruxure Building Operation is actually performing it properly. Resolution To use the Time Synchronisation you will need to bring the 3rd Party BACnet device (Eg. Continuum bCX) under the EBO BACnet Interface -> IP Network: Go to the BACnet Interface Time Synchronization Recipients Tab. Add a new Local time synchronization recipient with the '+' button. Select recipient type as 'reference' In the Recipient device object reference field browse for your BACnet Device. Press OK and then save the changes. Right-click on the BACnet Interface and select send time sync now. This will send out an unconfirmed-req TimeSynchronization to that specific Device only.   Test Scenario with a bCX setup as a third-party BACnet controller You will see a unconfirmed-req TimeSynchronization packet being sent from the ES in WireShark but with no response from the bCX.  You may not see responses back from other 3rd party devices. The time in the bCX should be seen to change from within Continuum, (assuming it was incorrect in the first place) 

Issue Is there support for the C-Bus protocol in StruxureWare Building Operation? How can we integrate C-Bus into StruxureWare Building Operation? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.0, 1.1 and 1.2. Cause Requirement to integrate C-Bus protocol into StruxureWare Building Operation, Automation Server or Enterprise Server. Clipsal C-Bus integrated service provide two gateways (BACnet / OPC), that may provide a suitable integration option. Resolution StruxureWare Building Operation does not directly support the C-Bus protocol at this point. Currently Schneider Electric Buildings integration with the C-Bus protocol is typically through the Xenta 913 (See Tip and tricks for communication between Xenta 913 and C-Bus on how this is achieved). When Interfacing the Xenta 913 to the Building Operation offerings you must create connection objects to and from the C-Bus objects via SNVTs, which need to be separately created within the Xenta 913 XBuilder project. Once these SNVTs are exposed, then the Xenta 913 can be added on the LonWorks network allowing the unit to be discovered as a LonWorks device (i.e. only acting as a third party LonWorks device). There are also two offerings provide by the Clipsal Integrated Services division that can be integrated with Building Operation, these are:   1. C-Bus BACnet Gateway (5000BACnet) The C-Bus BACnet Gateway is an embedded device that provides a field bridge between Clipsal C-Bus lighting control systems and the BACnet open protocol. The C-Bus BACnet Gateway provides 255 group addresses from a single application address. The C-Bus BACnet gateway supports the reading and writing of BACnet objects between C-Bus and BACnet and is supplied pre-configured from the (Clipsal) factory. Below is the link to detail of the C-Bus BACnet Gateway (5000BACnet) https://www.clipsal.com/Trade/Support/Software   2. C-Bus OPC Server For larger C-Bus systems (i.e. >255 group addresses) then the C-Bus OPC Server provides a gateway for C-Bus and the OPC Data Access protocols. Current releases of Building Operation does not support OPC, so you will require either an OPC to BACnet or OPC to LonWorks application which can be purchased through third party vendors. SCADA Engine is the preferred Clipsal BACnet OPC Client solution used. http://www.scadaengine.com/ Even though this solution is focused on BACnet, it may also be possible for a similar solution using LonWorks. Below is the link to detail of the C-Bus OPC Server https://www.clipsal.com/Trade/Support/Software There are additional requirements for each of these options that may need to be considered, it is best to discuss these directly with your regional Clipsal representative.

Issue Where is the RSTP setting on a MP-C or MP-V controller? Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller (MP-C) Building Operation Multi-purpose VAV (MP-V) Cause Unable to find RSTP setting on MP-C or MP-V controller Resolution On the controller, find System > Settings, scroll down to Configuration and enable RSTP. ** Be sure to Warm start each controller after enabling RSTP or the setting will not be retained **

Issue The purpose of this verification checklist is to provide documentation to the Project Manager that the Site Engineer has confirmed the Continuum Security configuration. Basic Settings Access Events Reporting Alarm Event Notification and Alarm Enrollments Door Alarms Other Alarms Time Sync Video including Pelco Digital Sentry IP Camera System Administrative Tasks Other Tasks Basic Checklist Access Events Reporting Checklist Alarm Event Notification and Alarm Enrollments Checklist Door Alarm Checklist Other Alarm Checklist Time Sync Checklist Video Checklist Administrative Tasks Checklist Other Tasks Checklist Environment Continuum with Security enabled Pelco Digital Sentry IP Camera System Cause Beneficial checklist for Verification of security site settings. Resolution Please find the attached pdf document which will walk you through the Continuum Security Checklist. The first section provides step by step instructions for novice users. The second section is the actual checklist where each task should be initialed by the Site Engineer, and the whole document signed by the Site Engineer and the Project Manager. To print the Checklist section of this procedure, start printing on page 21 of the attached checklist. Please find the attached pdf document which will guide you through a Pelco Digital Sentry IP Camera System Quick-Setup

Issue Why does the PID example function in the Script editor library not operate like the bPID? Product Line Andover Continuum, EcoStruxure Building Operation Environment Script/ Plain English differences Cause PID example does not operate as expected with regard to the integral action. Resolution The Script Program editor contains various library functions that can be selected from the "Library" tab at the lower right of the editor screen. Plain English program/ function examples were available and used in Continuum and known as the "Andover Controls Standard Modules" ACSM, they are available in Where can I obtain standard Plain English example functions? This document also contains further information about the PID use and application. In both the script PIDLoop (Long version) library function and the bPID function as used in Andover Continuum the Proportional component is the same, they both use Proportional Gain which is defined as 1 / Proportional Band. In the Script Editor Library PID function this requires the Integral Gain constant, this is defined as 1 / Integral Action Time as used in the Continuum bPID function. In the Script Editor Library PID function this requires the Derivative Gain constant, this is defined as 1 / Derivative Action Time as used in the Continuum bPID function. Either of the functions may be used in the SmartStruxure Script editor, but you need to ensure your calling program is passing the correct arguments for the PID function used.

Issue Setting up the override value to show the damper feedback on an i2/B3 866-v Product Line Andover Continuum, EcoStruxure Building Operation Environment i2/B3 866-V Plain English Script Cause Activate the damper position feature in the 866-V. Resolution SBO: See this video on creating a program that calculates damper feedback position.  Also reference the article How to show damper feedback for an i2/b3 866-V which describes what needs to be done to show damper position and calibrate the damper. Sample objects, code and images showing configuration are supplied.   Continuum: There is a description in the 866-V installation manual on how to activate the damper position feature, but there are some additional pieces of information that this article has been created to address. This was initially to just get the feature working as mentioned in the next section below. Getting the damper feedback operational: Once the end stops are determined initially during the Learn process, the controller can then determine the position of the damper. Create a PE program to set the DamperOutput LCDState = Disabled and back to Enabled in the next line. This will run through its stroke to determine the end stops. ‘Example program named "damperstate" Fall thru, auto start ‘a 2 line program to initialize the stops Line 1 Set damper LCDstate to disabled goto 2 Line 2 Set damper LCDstate to enabled stop To run from the command line Run damperstate Note that the Feedback will not start working until the Damper has gone full stroke in both directions. This will take several minutes. Set the damper point to on or –on depending on the position so it will move Print Damper OverrideValue from a command line or display it on a listview of the damper output after adding the overridevalue column Self Calibration - The LCDState toggle actually activates the "self calibrate" process. It doesn't just enable the feature. It is necessary to know this because you will need to activate the self calibration again whenever the damper is manually moved using the red actuator clutch release button. Using the clutch can cause the damper position to be reported incorrectly. Periodic re-calibration should be as a part of normal procedure for the controller. Once the clutch is used, the damper position will still report, but the value may be incorrect. Re-calibrate recommendation- Use a PE program that recalibrates the damper (i.e. LCDState as mentioned in Section A) on manual command by the service technician on a power cycle or at the end of an occupancy period. Note: For controlling the Damper motor output create an Infinity Output point of type Triac on Channel 1. It can then be opened / Closed like any other Triac output with the use of On, -On or Off commands

Issue What is difference between valve rangeability and turndown ratio? Product Line Field Devices Environment Valves Cause Definition of the terms helps explain the flow outcomes. Resolution Rangeability - maximum controllable flow divided by minimum controllable flow Turndown ratio - normal maximum system flow divided by minimum controllable flow.   Rangeability is the inherent characteristic of the valve and turndown ratio is the installed characteristic.

Issue There are 31 different Parser Errors that can result from a Menta direct download to a programmable controller. Product Line TAC Vista Environment Xenta programmables Xenta 280, 281, 282, 283, 300, 301, 302, 401, 401:B Menta Cause Causes vary by error code.  See details below and any links to additional information. Resolution No. Name Comment 0 PARSER_OK   1 PARSER_CREATE_OBJ_ERROR Seen immediately on an attempt to download directly.  Subsequent attempts result in "Download Failed."  Resetting the device caused the error to come back.  See in the error in COD window that its showing 0,0 coordinate pairs and underlying information.  The error's not in the Menta code itself.  No spaces allowed in the Program Specification -- a change from earlier versions.  May render your device unusable after attempting to download -- correct files won't download either. 2 PARSER_ALLOCATE_FLASH_ERROR   3 PARSER_IOMOD_SAVE_ERROR   4 PARSER_VERSION_ERROR   5 PARSER_APPNAME_ERROR   6 PARSER_ABBREV_ERROR   7 PARSER_TYPE_ERROR   8 PARSER_SOURCEFILE_ERROR   9 PARSER_SIGNAL_ERROR Error 9 has to do with the signal list (ESP-file) there all the public signals are transferred from Menta into the GraphOP tool by a sort of a long list. Normally, if you just make the application in Menta, this should not be any problem, however search and replace on signal names could give you headache. 10 PARSER_ALARMTEXT_ERROR Seems to download and fails on resetting device.  Had a case where this occurred when the application was too large due to generation of an OP tree where there wasn't one before.  Check memory. 11 PARSER_TIMESCHEDULE_ERROR   12 PARSER_IOMOD_ERROR   13 PARSER_IO_ERROR The terminal may not exist in this unit type.  Could also include situations where the same terminal reference is used in multiple references (this could be on the Xenta or the IO module). Typically caused by copy/paste. Reference to unsupported I/O Error in COD file - Error:13 for more information. 14 PARSER_CYCLETIME_ERROR   15 PARSER_CODE_ERROR Constants table has scientific notation, PVR blocks have scientific notation, Expression block attempting to use scientific notation, application size too large PARSER_CODE_ERROR Error in COD file - Error:15 for more information. 16 PARSER_DST_ERROR   17 PARSER_CHECKSUM_ERROR   18 PARSER_EOF_ERROR   19 PARSER_SNVT_ERROR   20 PARSER_SNVT_CRC_ERROR   21 PARSER_AUTHOR_ERROR   22 PARSER_BLUEPRINT_ERROR   23 PARSER_NO_BPR_FILE   24 PARSER_TLOG_RAM_ERROR   25 PARSER_TLOG_FLASH_ERROR   26 PARSER_TLOG_TO_MANY   27 PARSER_TLOG_ERROR_IN_DEF   28 PARSER_TOLG_PARSE_ERROR   29 PARSER_IMAGE_TOO_BIG   30 PARSER_RESET_BEFORE_PARSED   31 PARSER_SELF_DESTRUCTION_PERFORMED  

Issue The re-install of the Continuum system and security key is not being recognized. Product Line  Andover Continuum  Environment Continuum Cyberstation Sentinel Security Key Cause Driver not loaded Resolution Make sure the antivirus is not running on installation. If so, disable and re-install Continuum, or try to reinstall the Sentinel Key driver. The Sentinel Key driver is located in "\Continuum\ISSetupPrerequisites\{1F0227D8-C348-45F0-9789-1DEE3E8C5889}" directory and is an executable that can be run to install the driver. Sentinel Key drivers can be located on their website: http://www.safenet-inc.com/support-downloads/sentinel-drivers/ At times, the removal and reinstall of the driver still don't recognize the key even when it can be seen in another PC. If that is the case then do the following: Go to http://www.safenet-inc.com/support-downloads/sentinel-drivers/ and download SSDCleanup and run it. This will do a clean removal of sentinel drivers on the PC. Reboot and then reinstall the Sentinel driver from \Continuum\Install\Sentinel directory (SSDv7_xx.exe) Test multiple Windows accounts. There can be restrictions placed even on local admin accounts that interfere with reading the key.

Issue Is it possible to setup more than one custom card format in Security Expert? Product Line EcoStruxure Security Expert Environment Security Expert Custom Card Formats Cause Have a requirement for two or more custom card formats. Resolution Currently, only one Custom Format can be configured.   It is possible to add a Secondary Format to a Reader port in Reader Expanders, but only one port can be setup with a Custom Format.    However, Credential Types have now been introduced with the release of Security Expert 4.3, which largely supersedes Custom Formats going forward and allows multiple custom card formats and even QR codes where required.  Please see AN 276 Security Expert - Configuring Credential Types - Integration Guide for more information on setting up Credential Types and Maximum number of Credential Types for more info on how many can be used.

Issue Some jobsites require the use of conduit for all wiring between controllers. Is there a specific enclosure made for this purpose?  A general purpose enclosure such as the ENCL-100 can be used but must be punched or drilled to fit the damper shaft. Product Line TAC IA Series Environment MN-FLO / MN-FLO3T MNL-V1RVx / MNL-V2RVx MNB-Vx Cause Installation manual with reference to part number was misplaced. Resolution MNA-FLO-1 This enclosure is listed as an optional item in the installation manuals for all VAV controllers listed above. Click here to see F-26282-5, Installation Instructions for the MNL-V1RVx and MNL-V2RVx. Click here to see F-27346-4, Installation Instructions for the MNB-V1 and MNB-V2 Click here to see F-25718-6, Installation Instructions for the MN-FLO and MN-FLO3T

Issue Getting the error "The RPC server is unavailable" when attempting to write to a Vista Database.  This error can also be shown in the plug-ins output pain as "Error: Failed to access object xxxxxxxxxx." Product Line TAC Vista Environment TAC Vista System Plug-in Cause Incorrect DCOM or Firewall settings. This often occurs when installing a new system or restoring an existing Vista Database to a new PC. Computer is running out of memory. Resolution If it is cause due to computer memory shortage, please restart the TAC Vista Server. If the restart does not solve the issue, please follow the steps below. Install the DCOM utility located in Helpful Vista Utilities - Configure DCOM instantly, Register ASP.NET. or manually set the DCOM settings as instructed in the TAC Software Installation Unzip and execute the utility. If the problem persists and Vista Server is not on the local machine, ensure there is not a Firewall preventing a connection. If steps above does not resolve the issue, please reinstall TAC Vista software.

Issue The Enterprise Server service keeps stopping, and Windows restarts it right away. This is preventing WorkStation or WebStation from logging on. When viewing the Building Operation Software Administrator, the "Start Service" option is greyed out, and the server status is Stopped. Product Line EcoStruxre Building Operation Environment Building Operation Software Administrator Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Workstation Cause The Enterprise Server or Central service uses TCP port 80 by default.  If another service on the PC is using port 80 (e.g., Internet Information Services), this will cause the service to stop and re-start constantly. Resolution Two options: Stop the conflicting service from running (e.g., IIS, Dropbox, Skype) Change the HTTP or HTTPS port in Enterprise Server or Enterprise Central to a unique port (e.g., 8080) To change the ports, open Software Administrator and stop the server if it is not already. Then the port fields will no longer be grayed out, and they can be changed. Finally, restart the server. Refer to: Configuring Server Port Settings Note: Once the port has been changed to a unique one, this must be specified when logging into WorkStation, as seen below.

Issue Temperature Sensor Location Valve Location Actuator Location Product Line Field Devices Environment Actuator Sensor Valve Cause Where to fit and locate field devices. Resolution Valves: If the valve is lift and lay type and the application is diverting, then the valve must be fitted in the return. If the valve is lift and lay type and the application is mixing, then the valve must be fitted in the flow. The rule of thumb for lift and lay valves is "2 ins and 1 out" Rotary (shoe) valves can be fitted in either the flow or return for either mixing or diverting applications. Use pipe unions, so that the valve can easily be removed. Actuators on Valves: If the heating medium is steam then the actuator/valve arrangement is not fitted vertically, tilt the valve/actuator to an angle so that heat can convect away vertically and the actuator is not subjected to as much heat. In all cases, do not fit the actuator/valve arrangement so that the actuator is vertically under the valve. If the valve leaks, it will damage the actuator. Temperature Sensor location, in both wet and air applications the sensor need to sense correctly the medium it is in. Where possible install in a location for easier maintenance e.g. at a height reachable from a fixed floor level. Pipe Temperature Sensors: The tip of the sensor needs to be in the core of the medium i.e. the centre. The sensor needs to be fitted where stratification does not take place or is reduced. This can be achieved by fitting after a pump or after a bend where turbulence provides a good mix. If the sensor is fitted on a bend, then the probe faces the flow of/oncoming water. In CHW applications, fit the pocket just off horizontal, so that any condensation forming in the pocket can drain away. Adequate insulation will prevent condensation forming in the pocket. If fitting vertically in the top of the pipe is unavoidable see Oil for the DWT0001 (or STP660) pocket sensor to prevent problems with condensation. Duct Temperature Sensor: Supply Air - If a probe type sensor is fitted, it needs to be ideally 3 meters downstream and in the centre of the duct from the supply fan and preferably after a bend fitted with turning vanes. Return Air - The temperature sensor needs to be fitted before/upstream of the extract fan. Frost Coils - Temperature sensor, due to the short distance available, probe sensors are difficult to locate, but try to be as far away from the coil e.g. on the other side of the pre-filter bank and in the centre of the duct/AHU. Even better is to use an averaging type temperature sensor. Frost Coils - Fan Hold Off thermostat. Allow sufficient capillary to cover the battery surface. Lace the capillary across the frost battery on the downstream side using the correct clips. If the thermostat body needs to be fitted on the external side of the AHU, then fit with the minimum of capillary on the external of the AHU. Use a grommet or stuffing gland to protect the capillary as it goes through the AHU skin. If the AHU is fitted outside or is in an unheated space then the thermostat needs to fitted internal to the AHU. Do not cut the capillary if it is too long. Tidy capillary ends so they do not flap in the airstream. Outside Temperature Sensor: Outside temperature sensors should be located correctly to the local region you are in and the application they are serving i.e. compensated outside sensor in the UK are fitted on a wall facing north. The sensor should not be fitted on flues, chimneys, near opening windows. They should not be fitted near to compounds containing plant expelling heat e.g. chiller compounds. The sensor should be fitted at a height that does not require the use of steps or ladders for maintenance. Room Temperature Sensor: Sensors should be fitted at an agreed height and not fitted on external walls, near opening windows and doors or above radiators. They need to be exposed to the area they are controlling and not be directly influenced by heat sources e.g. computers. Sensors with exposed setpoint adjust or controls need to be fitted at a lower height so that people with disabilities can adjust them. Sensors that are fitted onto partitioned walls or have a conduit need the hole plugging so that there are no draughts. Sensors that are fitted directly to concrete or steel beams should be packed out with a thermal insulating material. Valves and Sensor Wiring: Allow sufficient cable to allow removal of actuator or sensor without having to disconnect the device. See the full Building Controls Group - Control Sensor Installation guide.

Issue The majority of the Satchwell MicroNet and Satchnet product ranges is now re-branded to Schneider Electric. Product Line Satchwell MicroNet Environment IAC-420-F IAC-420-P IAC-440-F IAC-440-P MN350-LON MN450-LON MN550-LON MN650-LON MN50-TS-LON MN50-TSP-LON MNN-COM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM MNN_RTC M50_RTC MN-TK MN-VWIO-NCP MN-VWIO-SNP MN-VW100-UK MN-VW500-UK MN-VWP500-UK MN-VWP2K-UK MN-VWP10K-UK MN-VWP60K-UK Monitor Tool MicroNet View Cause The branding exercise provided some insightful information regarding sales volume. As a result, a number of products that were low or zero sales have been discontinued. Resolution Updated June 2019   The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- For more information on the re-branding of the Satchwell MicroNet product range, see PA-00145A - Satchwell MicroNet Range Rationalisation and Schneider Electric Re-branding. Old Part Number New Part Number IAC420-F IAC420-P MN350-LON MN350-NCP + MNL-C (LON card) MN450-LON MN450-NCP + MNL-C (LON card) MN550-LON MN550-XCOM + MNL-C (LON card) MN650-LON MN650-XCOM + MNL-C (LON card) MN50-TS-LON MN50-TSP-LON (Panel Mounted Only) MNN-COM MN550-XCOM or MN650-XCOM MN550-NCP MN550-XCOM MN650-NCP MN650-XCOM  

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