Building Automation Knowledge Base

Issue LON bindings stop updating in a Niagara R2 UNC station. The following message also appears in the standard output window: MESSAGE: Unmatched LonWorks response received! [LonCommReceive.run] The LON bindings are re-bound but the problem re-occurs. Product Line TAC IA Series Environment  Niagara R2 UNC Cause This message indicates that a LON controller is sending a message to the UNC's subnet/node address that the UNC cannot match to its LON database. This happens when a controller has not had its binding table updated. Resolution Make sure the UNC is the only LON network management tool used on the associated controllers. Compare the UNC's LON database information to the data actually held in the associated controllers. Right click on the LonWorks Service and select Lon Utilities Manager. Leave the "device" to 'localLonDevice' and set the "Command" to 'reports' and the "SubCommand" to 'verify.' The resulting output will show any mismatches in the various tables. To correct, re-commission the localLonDevice, re-commission all other devices (which clears their tables), and then re-bind all listed bindings. Re-run a 'reports' > 'verify' to ensure all devices are up and running on the network.

Issue When a user logs on to Workstation and accesses the hyperlink, the website is displayed without prompt for login credentials Product Line EcoStruxure Building Operation Environment Building Operation Workstation Microsoft Internet Explorer Cause EcoStruxure Building Operation software uses Microsoft Internet Explorer to present web pages. How the page logs on is an IE function and not a function of EBO Workstation Resolution  Log off from the web site before logging off from Workstation  Configure Internet Explorer to delete browsing history on exit Go to Internet Explorer settings and then the Internet Options On the General tab, under the Browsing history, enable the checkbox for 'Delete browsing history on exit' (computer restart may be required)

Issue When using "link builder" in WorkPlace Commissioning Tool, MNB-V2s and MNB-300s link OK but links to MNB-1000s do not work. Product Line  TAC IA Series Environment WorkPlace Commissioning Tool I/A Series MNB VAV I/A Series MNB 70 I/A Series MNB 300 I/A Series MNB 1000 Cause An incorrect value set for APDU retries in the MNB-1000. Resolution Use WorkPlace Commissioning Tool to display the devices, and double click the MNB-1000 in question to display the Device Properties window. Select the Advanced tab and ensure APDU retries is not set to 0. If it is, set it to 3, reboot the controller and the links will function properly.

Issue When an old OGC graphic is converted to a TGML graphic in TAC Vista the conversion will fail if the name of the OGC graphic is longer than 36 characters. The OGC to TGML converter will just close with no error message. Product Line TAC Vista Environment Vista Workstation Cause The OGC to TGML converter does not support OGC graphic names longer than 36 characters, but if you try converting with longer names, the converter just closes down without any error message indicating why the conversion failed. This is a defect in the OGC to TGML converter which is reported to R&D. Resolution Rename the OGC graphic to a name with 36 characters or less.

Issue A temperature input on one device is referenced in an external binding, e.g. a consumer value, in another (BACnet) device. The value on the consumer side is incorrect and seems to have been converted from Fahrenheit to Celsius although the units all show Fahrenheit. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server (Premium) Building Operation Enterprise Server / Enterprise Central BACnet Device(s) supporting external binding (e.g. MP-X or IP-IO) Cause The probable cause is that the value of the temperature input is not configured to a specific unit. This means that the unit is decided by the electrical type of the thermistor. In most cases this is Temperature °C, which means that the values are stored in °C, and this is the value being transferred in the consumer binding. If the measurement system in Workstation is set to United States Customary Units (US), the input value will be displayed in Fahrenheit (°F) and one might think that the unit of the temperature input value is also configured to Fahrenheit, when in reality it is in Celsius. In this situation the value on the consumer side is in Celsius as it has no information about units. Furthermore, if the consumer value unit is configured to Fahrenheit, then we have the situation shown in the screenshot above. Resolution Start by changing measurement system in Workstation to As configured in object. (Refer to the Webhelp for more information about how to do this.) By doing this the values will be displayed unconverted. It is now clear that the temperature input in reality is in Celsius. The next step is to configure the input unit to Fahrenheit. Open up Properties for the Temperature input and click the gear wheel next to Value to configure. Check the box to the left of Unit and click the button with the three dots to the right. Select °F and click Select Click OK to confirm the changes in both open windows. Both the temperature input and the consumer value will now be displaying the correct value in Fahrenheit.

Issue How to set up PWM output in ZBuilder for TAC Xenta 121/122 devices. Product Line TAC Vista Environment Xenta 121 Xenta 122 ZBuilder Cause To be able to set up the PWM function for outputs, you need to understand each entry in the settings windows. Resolution   Activate at % TL The PWM output control starts when Terminal Load reaches this value. Fully active at % TL The PWM output control is fully active when Terminal Load reaches this value. Min control signal % The PWM output will not send out lower percentage of full stroke. Max control signal % The PWM output output will not send out higher percentage of full stroke. Period seconds The time for one full PWM period. This period will be cyclically repeated. Pulse change if change ≥ % Applicable only for actuators giving a position directly proportional to the pulse width and not dependent of cyclic updates (PWM with US terminology). This means the output will only activate when the Terminal Load has changed more than the set value, since last activation. Normally closed The TRIAC output is connected to ground (activated) when Terminal Load is zero, and the PWM output is not active. When the PWM output activates, the TRIAC output will not be connected to ground. Normally open The TRIAC output is open, not connected to ground, when Terminal Load is zero, and the PWM output is not active. When the PWM output activates, the TRIAC output will be connected to ground.

Issue In Vista Workstation you can create a new user and password using all characters of a keyboard. Vista Workstation allows creation but when you try to login to Workstation you get a login error. Product Line TAC Vista Environment Vista Workstation Cause Using characters in the password field that Vista does not recognize. Resolution Don't use the following characters in a password for users: !   @   #   $   %   ^  &  *  (  )  -  =  +  ,  <  >  '  "  ?  \ The following special characters can be used in the password field: _  .  /  : 

Issue After upgrading to TAC Vista version 5.1.7 no new values will be shown when a trendlog is opened.  Error message in Vista: System.Data.SqlClient.SqlException (0x80131904): Incorrect syntax near ')'. at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteScalar() at TAC.DSS.DataAccess.SqlServer.SqlMaintenance.GetDatabaseFragmentationLevel(String tablename) at TAC.DSS.DataAccess.SqlServer.SqlMaintenance.GetDatabaseFragmentationLevel_TrendlogValue() at DssCliLib.Utility.GetDatabaseFragmentationLevel_TrendlogValue(SByte* pszConnectionString, Int32* plSize) Product Line TAC Vista Environment Vista Server version 5.1.7 Cause This issue occurs due to the use of an incompatible SQL server version. A number of new features were introduced in Vista 5.1.7, one of which was a check of the SQL database's fragmentation level. It is this check that fails as it uses a query that is not recognised in SQL 2000. Resolution Upgrade/run the database to/on SQL 2005 server or higher.

Issue Pin configuration of the RJ10 for TAC Xenta OP Product Line TAC Vista Environment Xenta OP Cause The Xenta OP has two connection methods, the 4 pin terminal blocks and an RJ10 port. Some users may have the need for making custom RJ10 cables. Resolution The pin order for the RJ10 port is the exact same as the order on the terminal block right next to it. From right to left they are: C1 (comms 1) C2 (comms 2) G+ (24 VAC power) G0 (24 VAC ground)

Issue Unable to send alarm generated emails via the Yahoo’s SMTP server in I/A Series G3. The following error messages are displayed in the console output window when attempting to send a mail via Yahoo’s SMTP server. javax.mail.MessagingException: Could not connect to SMTP host: smtp.mail.yahoo.com, port: 465; Caused by: java.net.ConnectException: Connection refused: connect Product Line TAC I/A Series Environment Niagara G3 ENS ENC-520 ENC-410 Cause An incorrect STMP hostname was used in the “Hostname” of the OutgoingAccount. The correct Yahoo outgoing mail address, “smtp.mail.yahoo.com”, must be entered for in the OutgoingAccount “Hostname”. Resolution Procedure and properties settings required when using the Yahoo SMTP Server: Add the EmailService and CryptoService to the station's Services folder. If emails are to be sent from an ENC, ensure that the email and crypto modules (and their dependencies) are installed into the ENC. Add the OutgoingAccount to the EmailService. In the OutgoingAccount properties, configure the properties indicated below. Leave other properties as their default settings. Hostname: smtp.mail.yahoo.com Port: 465 (this is the TCP port SMTP over SSL uses) Account: example@yahoo.com (works without the “@yahoo.com” as well) Password: Your Yahoo account password Enabled: true Use SSL: true (Yahoo requires SSL) Transport: Smtp Use Authentication: true (Yahoo requires authentication when sending out emails) Reply to: example@yahoo.com (“The Reply To” must contain a valid Yahoo account) You can test the functionality by right-clicking on the EmailService and selecting 'Actions' > 'Send' to send out an email. Notes: CryptoService enables the SSL feature in the G3 station. The crypto module is included in the installation of I/A Series G3 version 3.6 but it was not included in earlier versions. You can download the crypto modules for earlier versions of G3 from The Exchange Download Center. Ensure that the station is licensed for crypto. You can look into your license file to check. Below is an example taken from a demo license. feature expiration="2012-03-31" name="crypto" parts="ENS-DEMO" ssl="true"

Issue A license is needed for using the Roam IO2 with ethernet Product Line Andover Continuum Environment Roam IO2 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause A license is required to use the ethernet feature with the Roam IO2 Resolution Follow the instructions for Generating a License request in the BACnet Service Tool Generating a License manual, (PDF attached). Include your contact information, PO (purchase order) and RA numbers for the RoamIO2. Send that information to Upgrades.Continuum@schneider-electric.com to process the request.

Issue Is it possible to convert a Xenta 121-HP to a Xenta 121-FC? Product Line TAC Vista Environment Xenta 121 Cause The hardware controller was purchased as a heat pump or fan coil unit, and the opposite is needed for the software application. Resolution As of August 2011, it is possible. Download the NXE file and XIF file for the desired application Download the files to the Xenta 121 using Lonmaker or NL220 This will be blocked in the future.

Issue Unable to connect to a G3 ENC or JACE after attempting to downgrade or install a station. One of several different errors may be displayed in the serial shell console output.  The following are examples: Could not find library libcpp.so.3 Could not find library libcpp.so.4 Error occurred during initialization of VM - Java/Lang/ No Class Def found error: Java/Lang/object Product Line TAC I/A Series Environment I/A Series G3 ENC and JACE (all revisions), ENC-410, ENC-520, TRD-T-645, TRD-T-603, TRD-RB-645, TRD-RB-603, TRD-J-600E, TRD-T-700 Cause The issue is caused by downgrading the ENC / JACE without following the procedure to first install the clean distribution file. In addition, the ENC/JACE will fail if a station is copied into the ENC/JACE without first installing the OS and NRE software using the Workbench Commissioning Wizard. Note: With G3 release 3.3 and newer, the procedure for downgrading an ENC/JACE is included in the Niagara AX Platform Guide - Downgrading a JACE (Clean Dist). Resolution Tools needed: Null Modem Cable Serial Terminal (e.g. HyperTerminal or TeraTerm) Jumper Obtaining the files required to recover the ENC NOTE: If recovery of a Jace-700 is required, please contact Product Support for the recovery file. Download the appropriate OS image and gz file zip file for the ENC/JACE from the Exchange website - https://ecobuilding.schneider-electric.com ENC-410.zip ENC-410-1 standard memory - etfs512 ENC-410-EM.zip ENC-410-1 extended memory - etfs2048 ENC-520.zip ENC-520-2 standard memory - etfs512 ENC-520-EM.zip ENC-520-2 extended memory - etfs2048 NPM6E.zip JACE603/645, TRD-RB-603/645, JACE600E Note: The files used in the following procedure MUST correctly match the ENC/JACE hardware platform, otherwise permanent damage to the unit may occur. The serial shell can be used to determine the file system requirements (standard or extended memory). To find the exact image needed for an ENC (JACE 2/4/5) execute the following while connected to the unit with serial shell: Log into the unit's menu system using the platform username and password. Type sh to exit the menu system and enter the shell mode. At the # prompt, (type: cat sys/info/fs) and enter This will return the file system type of etfs512 or etfs2048. Extract the OS image and gz files from the downloaded zip to a suitable directory on the local computer (e.g. local hard drive such as: c:\temp). Enable ftp: By default, the ftp port is disabled on every ENC/JACE as shipped from the factory.  Enable the ftp as follows. Set the jumper on the ENC to serial shell mode and connect the null modem cable between the PC and the ENC/JACE. Connect to the ENC using the Serial Terminal program and the following port settings: Baud rate 57600 bps (Note: JACE-603/645 baud rate is 115200) 8 data bits, 1 stop bit, no parity After logging in to the menu system from the serial shell, do the following to enable ftp: Select option 4 from the menu Enter the port number (Normally 21). (type: 21) Press the Enter key to confirm the change Note: Leave the serial shell connection open while performing the next steps. FTP the OS image and gz files On the local system, open a command prompt window and change the directory to the location where the OS image and gz files were extracted (c:\temp). Connect to the ENC via ftp and put the OS image in the /tmp directory entering the following from the command line: Create a ftp connection to the ENC by typing: ftp and enter Type the username and password for the platform when prompted Change directory to /tmp (type: cd tmp) and enter Change to binary mode (type: bin) and enter Download the image to the ENC by using the put command. The image name must exactly match the image extracted from the downloaded zip file. ENC-410-1 standard memory (type: put york-etfs512.image) and enter ENC-410-1 extended memory (type: put york-etfs2048.image) and enter ENC-520-1 standard memory (type: put james-etfs512.image) and enter ENC-520-1 extended memory (type: put james-etfs2048.image) and enter JACE-600E, 603, 645 extended memory (type: put npm6xx-etfs2048.image) and enter Download the gz file to the ENC by using the put command. The name must exactly match the image extracted from the downloaded zip file. Change directory to the root (type: cd ../..) and enter Change directory to /ffs0/zip (type: cd ffs0/zip) and enter Download the gz file (type: put clean.tar.gz) and enter Exit ftp (type: quit) and enter Execute OS image update Return to the serial shell connection Type sh to exit the menu system and enter the shell mode At the # prompt, type: osupdate and enter After a short delay the # prompt will return. Shutdown to reboot the ENC (type: shutdown) and press enter. The ENC/JACE will reboot, install the clean distribution image and perform one additional reboot automatically. The ENC/JACE should now be recovered and allow connection to the platform. Connect and use the Workbench Commissioning Wizard to install the version of G3 required.

Issue After upgrading to Continuum 1.94, Cyberstation throws the following error: Failed to call pILiveData -> GetLiveData().  ACDataServices has an error. Product Line Andover Continuum Environment Continuum 1.94 Schedule Error Cause This behaviour is due to a bug that was described in TPA-BOST-12-0002 00 Schedule Exception Errors. Resolution Install the CyberStation v1.94 SP1 - Software which can be found on the Exchange Extranet.

Issue Most systems have an Overview Graphic of the whole building.  The user then navigates from this graphic to specific floors and rooms of interest. If the Workspace is configured incorrectly, navigating to a newly selected graphic does not work as expected. The overview graphic does not disappear and the new graphic is forced to open very small at the edge of the screen. Product Line Building Operation Enterprise Server Environment Workspaces Cause The standard Administration and Engineering Workspaces used in EBO contain a Work Area Window (WAW) which is necessary 'space' to show a selected graphic/trend/schedule If an Overview Graphic Pane is created in a Customer Workspace and this graphic takes up most of the screen, there is no space left to show the new object which the customer wishes to see Note: The Overview Graphic 'Building' is now shown in a Graphic Viewer only   When the system tries to open a new graphic, there is not space to open it in, The graphic is forced to open at the very edge of the screen and is therefore very small. Resolution General information about creating and using Graphic Panes, Work Area Windows and Panel Components can be found in the EBO webhelp, But for specific information on how to prevent a graphic opening at the edge of the screen see below.  Rather than adding a Graphic Pane to the Workspace to show the Overview Graphic add a Work Area Window (WAW) instead. Next, define the required Overview graphic as the initial path for the WAW on startup so the Overview graphic opens at user log on. Note: The Overview graphic 'Building' is now shown in the WAW rather than the Graphic Viewer. Graphics will always close themselves on navigation to the next object by default when used with a WAW (this can be changed). As soon as the user needs to navigate away from the overview page to a new graphic/schedule/trend, the system can use the WAW which will then use most of the screen as the 'space' to show it. In this case, as soon as the link to the next graphic 'Floor' is pressed, the first graphic 'Building' closes according to its default and the new object is shown in its place.

Issue Cannot use the Hall Effect Sensor object under the Onboard IO of an MP-X   Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Multi-purpose VAV Cause The object is an internal sensor for measuring the position of the actuator. Resolution The hall Effect Sensor Object is not an user configurable object.

Issue Clicking a graphic page link fails to open any graphic page, but when opening the path using the System Tree of the server that contains the graphic page, successfully allows the link to open the graphic page. When opening the same page using WebStation, the graphic pages all open successfully. Product Line EcoStruxure Building Operation Environment Building Operation WorkStation 1.9.x or below. Cause Typically having 'dead links' or unresolved binds in any graphic page is the reason for the issue. WorkStation pre-loads all objects of the references to the graphics. This call (CSP GetObjects) fails since (at least) one path of the objects points to a server that does not exist. Unfortunately the protocol can't return the objects that do exist and WorkStation then marks all these objects as non-existent and fails to open the respective binding. This operation cannot be corrected in this version of WorkStation and requires an upgrade to 2.x or above to correct this. Resolution Two options are available Correct/remove all link bindings that are shown with unresolved references to invalid server paths. Example showing an Unresolved Binding Upgrading to Building Operation 2.0 or higher will also resolve this issue.

Issue What file types or graphical components does Pinpoint support? Cannot import a GIF file in to a Pinpoint graphic. Product Line Andover Continuum Environment Continuum Cyberstation 1.XXX MS Windows XP Server 2003 Cause GIF files are not supported. Resolution Pinpoint graphical components supported: Lines Rectangles Polygons Curves Ellipses Text Bitmaps Enhanced Metafiles (EMF) Icons DIBS (Device Independent Bitmaps) Jpeg

Issue Can you use either Micronet ARCnet or LON version Touchscreen on an NCP network? Environment MicroNet ARCnet Touchscreen MicroNet LON Touchscreen NCP Network Relates to specification numbers: MN50-TS-ARC MN50-TSP-ARC MN50-TS-NCP MN50-TSP-NCP MN50-TS-LON MN50-TSP-LON Cause Touchscreen compatibility Resolution ARCnet The MicroNet 100 Series ARCnet Touchscreen ((MNN-TS-100 or MNN-TSP-100) + MNA-C). The Touchscreen has NCP communications by default, they were supplied with an ARCnet daughter board. Removing the ARCnet daughter board, would revert the Touchscreen to an NCP type. The MicroNet 50 Series ARCnet Touchscreen (MN50-TS-ARC or MN50-TSP-ARC) The Touchscreen has NCP communications by default, they were supplied with an ARCnet daughter board. Removing the ARCnet daughter board, would revert the Touchscreen to an NCP type. LON The MicroNet 100 Series LON Touchscreen, (MNL-TS-100 or MNL-TSP-100) removing the LON board would not revert the Touchscreen an NCP type. The LON Touchscreen firmware allows for a limited Bubbleland program and is different to that of the NCP version. The NCP touchscreen firmware is no longer available to be retrofitted. A specific MicroNet 50 Series Touchscreen version was not produced, the hardware remained the 100 Series model.

Issue For the Niagara R2 MicroSmart Driver (ibsMs), what are the latest firmware revisions for MicroSmart controllers that are supported? Environment ibsMs MicroSmart controllers Cause Check and upgrade MicroSmart controller firmware to the latest firmware to avoid intermittent problems. Resolution ibsMS a Supported Controller Part Number Cntlr Type Cntlr Level Description P/N To Order Firmware P/N Revision CheckSum IC# Yes 1 ENV-III AHF L11 Anemostat Envirotrak III PROM-KIT-10 PROM-48-119 11.1X $8F1E IC12 Yes 1 ENV-III-MPC AHG L11 Anemostat Multi-Purpose Controller PROM-KIT-11 PROM-48-120 11.1X $63F1 IC11 Yes MN-MSI MIM L11 Integrator for MicroSmart Bus PROM-KIT-4 PROM-42-100 11.1T $0B48 IC20 Yes MSC-L1000 ELC L11 Lighting Controller PROM-KIT-16 PROM-48-125 11.2H $31B4 IC3 Yes MSC-MPC-001 HPA L11 Multi - Purpose Controller PROM-KIT-5 PROM-48-104 11.2H $2996 IC11 Yes MSC-P-751/752/753/754 SVA L11 Package Unit Controller PROM-KIT-7 PROM-48-106 11.2H $B762 IC3 Yes MSC-P1501/1502/1503/1504 PCB L11 Package Unit Controller (early version) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-P1501/1502/1503/1504 PCC L11 Package Unit Controller (enhanced AI) PROM-KIT-6 PROM-48-105 11.3A $44CC IC3 Yes MSC-V-511/512/521/522 VAC L11 VAV Controller PROM-KIT-9 PROM-48-107 11.2H $7D17 IC9 Yes MSC-V-751/752/753/754 SVA L11 VAV Controller PROM-KIT-8 PROM-48-106 11.2H $B762 IC3     ELC-001 SVC L10 SiteManager Controller PROM-KIT-12 PROM-48-121 10.2 $C708 IC4 Yes 1 ENV-III-MPC AHE L10 Anemostat Multi-Purpose Controller N/A       IC11 Yes MSC-MPC EHP L10 Multi - Purpose Controller PROM-KIT-2 PROD-EHP 10.3 $0FEE IC11 Yes MSC-P1000 ELP L10 Enhanced Low PUC PROM-KIT-13 PROM-48-122 10.1 $C25B IC18 Yes MSC-P2000 EMP L10 Enhanced Medium PUC PROM-KIT-14 PROM-48-123 10.1 $AC7A IC24 Yes MSC-U1000 EUC L10 Enhanced Unit Controller PROM-KIT-3 PROD-EUC 10.4C $945F IC21 Yes MSC-V501/502 VAD L10 VAV Terminal Controller PROM-KIT-17 PROM-48-126 10.4D $345C IC9 Yes MSC-V501/502 VAB L10 VAV Terminal Controller PROM-KIT-15 PROM-48-124 10.3 $017C IC12   Yes 1 ENV-IIB (N1-1087) A2B L9 Anamostat (2) Fume Hood Controller N/A PROD-A2B 9.1 $6858 IC23 Yes 1 ENV-II(N1-1058) AHC L9 Anamostat Unit Controller PROM-KIT-1 PROD-AHC 9.1 $320F IC37 Yes MSC-GPC GPC L9 General Purpose Controller PROM-KIT-18 PROM-48-736 9.4C $4E78 IC25 Yes MSC-IOC SIO L9 Input/Output Controller PROM-KIT-21 PROM-48-739 9.4C $64A7 IC43   MSC-L-100 MLC L9 Lighting Controller PROM-KIT-25 PROM-48-743 9.1R $AA35 IC5 Yes MSC-P-100/112/120 LPC L9 Low PUC PROM-KIT-22 PROM-48-740 9.4C $C9FE IC17 Yes MSC-P-200 MPC L9 Medium PUC PROM-KIT-20 PROM-48-738 9.4C $9031 IC23 Yes MSC-T-100 STC L9 Temperature Controller PROM-KIT-23 PROM-48-741 9.4C $558E IC6 Yes MSC-UC UC L9 Unit Controller PROM-KIT-19 PROM-48-737 9.4C $FB25 IC22 Yes MSC-V-100/V110 VAV L9 VAV Terminal Unit Controller PROM-KIT-27 PROM-48-749 9.4C $45AE IC12 Yes MSC-V-200 VSD L9 VAV Terminal Unit Controller PROM-KIT-24 PROM-48-742 9.4C $5CE8 IC13   MSC-V-200E (ETI) VE1 L9 VAV Terminal Unit Controller N/A TEST VE1 9.0C $6A7E IC13 Yes MSC-V-300 VDD L9 VAV (Dual) Terminal Unit Controller N/A PROD-VDD 9.3 $7DC6 IC15 Yes MSC-V-400 MOV L9 Mobil Package Unit Controller PROM-KIT-26 PROM-48-744 9.4C $5148 IC17 a The firmware revisions listed above were validated with this driver. Other versions may function correctly but were not tested. If difficulties are experienced, upgrade firmware. 1 Controller validated with ibsMS-2.302.514a.v1 or greater.