Building Automation Knowledge Base

Issue Replacements for Schneider Electric SmartX MF41 Damper Actuator Product Line Field Devices Environment SmartX MF41 Cause Replacement of SmartX MF41 Damper Actuators within the Schneider-Electric range Resolution Outgoing Actuator Model         Replacement Model (Part Number)        MF41-6083-G00                         MD10B-24 (875 1015 000)      MF41-6083-G02                         MD10B-24 (875 1015 000) + Aux Switch (914 1061 000)      MF41-6153-G00                         MD20B-24 (875 1025 000)      MF41-6153-G02                         MD20B-24 (875 1025 000) + Aux Switch (914 1061 000)

Issue Replacements for Schneider-Electric SmartX MS41 Damper Actuator Product Line Field Devices Environment SmartX MS41 Cause Replacement of SmartX MS41 Damper Actuators within the Schneider-Electric range Resolution Outgoing Actuator Model          Replacement Model (Part Number)       MS41-6083-G00                        MD10A-24 (875 1019 000)       MS41-6153-G00                        MD20A-24 (875 1029 000)       MS41-6153-G10                        MD20A-24 (875 1029 000)       MS41-6153-G12                        MD20A-24 (875 1029 000) + Aux Switch (914 1061 000)

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 Need a method for mass importing User photos for creating / updating the Users for a Security Expert site. Product Line Security Expert Environment Security Expert Security Expert Data Sync Service (SX-DB-SYNC) Cause Data Sync Service is typically used to import data from the third party system.  In this instance, a CSV file containing the data to be imported into the Security Expert database is used. The Data Sync Service is configured to monitor the folder where this CSV file is located and automatically (if configured) import the relevant data into Security Expert, creating records (including users, access levels, areas, doors, schedules, and so on) for each matched entity. Resolution The Data Sync Service can be used to map specific fields from a CSV file to fields within Security Expert. One of those fields can be the User photos. Below is a guide on how to implement this.   1. Directory Setup Before opening the Security Expert Data Sync Service, it is necessary to setup a CSV file and directory for the Data Sync Service to work with. The only requirement for now is that each image must have a unique name and that the folder housing the images must be called "Photos". Figure 1 shows an example folder structure: Note: The names of the folder, CSV file and image names are not critical. As long as the image names match what is in the CSV file.   2. CSV File A CSV file is a comma separated file with each row being a separate record and columns (fields) separated by comma's. An example CSV is shown below:   UniqueID,FirstName,LastName,AccessLevel,PIN 101,First,User,Visitor,1284 102,Second,User,Visitor,5618 Note: The UniqueID field will need to be the file name of the Users image. For the below example CSV, two images must be present in /Photos/ with the names 101.jpg and 102.jpg.   3. Security Expert Operator It is recommended that a new Security Expert Operator is added for importing from the Data Sync Service. This ensures that records that have been added / modified / deleted by the Data Sync Service can easily be identified. To proceed past the Data Target section the Show PIN numbers for Users option must be enabled in the Operator object.   4. Data Target Now that an Operator, directory and CSV have been set up, open Security Expert Data Sync Service and follow these steps: Select Security Expert from the Target System dropdown. Confirm the SOAP Server Address. If the defaults were accepted during the installation of the SOAP Service, enter http://localhost:8030/SecurityExpertSOAPService/service.svc. Enter the Username of an Operator. Enter the Password for that Operator. From the Site dropdown, select the Site that the records are to be imported to. All Sites that have been added in Security Expert will be available in the dropdown. Overwrite the Site ID during the field mapping process if the records are imported to different Sites within a single import. Note: The rest of the fields on the Configuration window are disabled until a valid Server Address, Username and Password have been entered.   5. Sync Options Set the Resynchronize Every time to a time interval over which the service should resync data. Tick the Enable Error Log checkbox to populate the Event Viewer with events that will make error solving simpler.  6. Data Mapping  Configure the records and import file with the following steps. Select Users from the Record to Sync drop-down.  In the File Directory field, enter the created folder. If importing a single file, enter the name of the file in the Import File field. If the checkbox is left unticked, all files in the File Directory will be imported. From the File Format drop-down, select Delimited. If the import file is a CSV, select {CR}{LF} as the Row and {Comma} as Column delimiters. Enable the option to Start Import At Row 2 to skip the header.    7. Field Mapping The data mapping phase allows CSV columns (Source Column) to be mapped to a record type in the Security Expert Database (Target Field). To import the example CSV, the field mapping must be configured as below. Link a Target Field and Source Column, simply select both in the interface, complete the following: Link the following [Target Field : Source Column]: ImageID : 1, First Name : 2, Last Name : 3, UserAccessLevelGroupDataData > UserAccessLevel : 4 PINNumber : 5, Select ImageID (Column 1) as the Unique Field. For UserAccesLevel, open the Advanced Data Configuration by clicking the [ … ] button. Ensure that Use This Field As The Group Data Identifier is set and Grouping Type is Singular Data. Ensure Target Field Record Type is ticked and set to Access Levels. Click Save and then Start to begin the syncing of Users. 8. Troubleshooting If troubleshooting is required, examine the following logs: All Events - In Security Expert under Monitoring > Status Page View, open the All Events view to view Data Sync Service events. Event Viewer - Open the Windows Event Viewer and navigate to Event Viewer > Applications and Services Logs > Schneider Electric Security Expert event log.

Issue Modbus RTU Serial Device (RS485 - Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus RTU Master RS485 Network Cause Third party Modbus device has an address range between 248 and 255. Resolution For Modbus master/slave RS485 networks, the third party device must be in the range of 1 to 247, this is the Modbus RTU standard. This would apply not only to EBO but to other Modbus master/slave networks.   The KB article Modbus basics explains this amongst other Modbus topics.   If the third party Modbus slave device cannot be changed to an address to within this range, then contact with the product vendor may be required.   For TCP devices see the KB article Modbus TCP Device (Slave) address greater than 247.  

Issue This is useful when you are disarming areas from a card reader as you can secure the disarming portion by requiring a PIN code, preventing somebody from using a lost or stolen card to disarm the area while maintaining the convenience of Card Only once disarming has occurred. Product Line Security Expert Environment Security Expert Client Security Expert Server SP-C-Web Cause Prevent someone from using a lost or stolen card to disarm an area while maintaining the convenience of Card Only once disarming has occurred. Resolution Create a new Schedule (SX = Sites > Schedules, SPC-Web = Time > Schedules) with the following settings: Check/enable all days for Period 1, leave start and end times default so you are left with a 24/7 schedule Under Options enable 'Validate Schedule When Qualify Output is On', set the 'Qualify Output' to whatever output is configured as the Disarmed output for the required Area. If you aren’t using a disarmed output currently you will need to assign one, this can be a Virtual Output if you do not want to use a physical output. Create a new Door Type (Programming > Door Types) with the following settings: Operating Schedule = The schedule from Step 1 Secondary Door Type = The default Card AND PIN door type created by the system Entry Reading Mode = Card Only Exit Reading Mode = Card Only Locate the required Door(s) (Programming > Doors) and change the Door Type to the one created in Step 2. When the Area is disarmed the schedule will be valid so the Door Type will be Card only when the schedule is invalid (which will be whenever the area is armed as the disarmed output deactivates upon arming) the secondary door type of Card + PIN will be used. You can use other combinations of Door Types as required

Issue Unable to drag and drop discovered RP-C with the Zigbee adapter to its Zigbee Device Import File resulting in this error: Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) Cause Application Defined Type is not fully universal Resolution Hold "shift" while you drag and drop the RP-C to associate the discovered device with the imported proxy.

Issue I have Advanced Display V3 connected to my EBO server. Do I need a client license? Product Line EcoStruxure Building Operation Environment Building Operation Advanced Display V3 Cause Building Operation Advanced Display V3 (AD v3) is an industrial-grade Human Machine Interface (HMI) that can easily be locked to an application such as EcoStruxure Building Operation WebStation to create a dedicated tool for local operation and maintenance of an EcoStruxure BMS. Resolution When connected to EcoStruxure BMS server, AD v3 is counted as one WebStation client. Starting from EBO v2, WorkStation and WebStation will both be considered a client, and each will require a concurrent license to be able to log into the system. Three client licenses are included with each Enterprise Central and each Enterprise Server. When logging directly into a SmartX server, the number of WebStation connections is limited only by the Architectural Guidelines*, which says that a client license is only needed if the AD v3 is connected to Enterprise Server or Enterprise Central directly. *From EBO 3.1 and forward there is no need to activate a Client feature license on SmartX servers to be able to connect WebStation to a SmartX server and log in. While versions 3.0.4 and 3.0.3 with hotfixes accomplished the same functionality, they did so by stating that 99 clients were available.

Issue Modbus TCP Device (Slave) address greater than 247 Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server (AS, AS-P, AS-B)  Modbus TCP Network Modbus TCP Gateway Cause Modbus TCP Device (Slave) address 248 is reserved and cannot be used. (Modbus TCP Network or Gateway) SmartStruxure supports up to address 247, as per StruxureWare Building Operation - Technical Reference Guide (up to v1.6.1). There was a defect within v1.5.0 and earlier that caused address 250 to be used if the Device address is set to "Invalid." This defect was corrected in v1.6.1. Resolution From v1.9 this is corrected, so it is possible to define addresses for Modbus TCP devices from 1-247 and 249-254 Device addresses 0 and 248 are reserved. Device address 255 is used as the Default address.   For Modbus RTU RS485 master/slave networks, slave device addressing is different, see KB article Modbus RTU slave address.   Further information about Modbus can be found in the KB article Modbus basics.

Issue Reporting Agent continuously restarts Windows Event logs show appcrash for Reporting Service  Trend / Event data no longer transferring to WebReports / Report Server.   Product Line EcoStruxure Building Operation Environment Building Operation Report Server  Cause If there are bindings within the Extended Trend Log that is from itself (so a cyclic loop). By default when you select the Transfer trigger variable the SmartLog property is selected (as shown below).  This is an invalid configuration but can be accidentally configured and saved.    This will cause the ES read to go into an infinite loop and cause the application to eventually restart (crash).  By setting the Reporting Agent to Debug (using the SBO Reports Agent Config - Communities (se.com)) the last few messages before the restart within the log file will show messages related to "Entering IncludeLogInReports()" with the same set of Extended trend Logs repeat (if there is more than one).  The image below shows an example of the Extended Trend Log shown in the above screenshot.    Resolution After locating the relevant extended trend logs with these invalid bindings, delete these invalid bindings and restart the Reporting Agent service and the data should then be read correctly.     Remember to revert the log level back to INFO before restarting the agent to not overload the logs with too much detail. 

Issue Permissions are set with multiple tags as the following:      When the user logs into Access Expert and looks at the hardware tree, they are able then to see all the hardware on the instance rather than just those with the matching tags. Product Line EcoStruxure Access Expert Environment Access Expert Hosted Software Access Expert Premise Software Cause The tags are meant to be on separate permissions and shouldn't be used on the same individual permission Resolution Tags and permissions should be set up as illustrated:

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 Contemporary Controls Skorpion Switch configuration setting for using RSP with MPX and RPX controllers Product Line EcoStruxure Building Operation Environment Contemporary Controls EISK8M-100T Skorpion Switch Building Operation Automation Server Premium Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation Room-purpose Controller Cause Contemporary Controls Skorpion switches have several caveats to consider before using them in a site design. Specific Skorpion switch configuration settings are needed in order for the RSTP protocol to work with MPX controllers.  Resolution *NOTE: This is only for Contemporary Controls Skorpion Switches*   Contermporary Controls EISK8m-100T switch documentation: https://www.ccontrols.com/ctrlink/eiskm.php    There are a number of configuration options available to use these switches and MPX/RPX controllers. This article is not meant to be a comprehensive guide.   Two caveats to consider before using these switches:  Contemporary Controls (CC) Support has indicated that these switches have a limitation to 39 devices (MPXs) per switch. Other vendor's switches do not have this limitation and allow 39 devices per RSTP loop. Multiple RSTP loops are not supported on a Skorpion switch. Multiple Skorpion switches may be used and daisy-chained to allow for greater than 39 devices. The 39 total number includes the switch itself, so effectively, 38 MPXs. A static IP address of the switch should not be in the same IP range (10.110.210.x) if the AS-P is being used as a DHCP server. Configuring the switch this way may cause the AS-P to assign a duplicate IP address to 1 of the MPXs in that range. The DHCP server in the AS-P is a very basic DHCP server to allow for quick IP assignments in a private network. There aren't any configuration options for designated exceptions in the AS-P. (Note: This may be a security concern for sites that do not want a switch on their main network. Setting the Skorpion switch to DHCP enable can allow the ASP to assign a non-static IP to the switch and not interfere with MPXs. RSTP enabled - the snapshot below shows the settings to enable RSTP o the switch Redundancy state: STP/RSTP STP State: Enable Hello Time: 2 Version: RSTP Max Age: 40 Forward Delay: 21                                       The Bridge Priority setting should be changed to 4096 to be a higher priority than the controllers. See the Priority setting in the snapshot above. Root ID: Self-populating field will indicate "Self" when set for a single root with 1 RSTP ring Rood ID "mac-address" may indicate a different switch that is the root switch Non-STP State Port Some ports must be set to not pass BPDU RSTP traffic,  i.e. the ASP, a PC used to configure the switch and connecting other network switches. 2 or more switches can be connected to allow for more devices to be connected (38 each) but RSTP traffic must be restricted to each switch. The ports connecting them need to be configured as Non-STP.   Note: Admin edge turns off almost all RSTP traffic, but not all Non-STP State ON disables the port from participating in the STP or RSTP ring The ports that are connecting the 1st, 2nd or 3rd switches need to have Auto-MDX set properly to behave as a cross-over cable. Either that or use a physical cross-over cable. In the Skorpion configuration page, click on the picture of the switch where the ports are showing "Auto-Mdix enable" on one switch and "Auto-Mdix disable" on the other switch. Click on the actual port from the main page to get to this setting. Example: Switch 1 port 8           Switch 2 port 1            General observations: Switch manufacturers have different limitations and options for configuration. Pay close attention to the Vender’s switch and MPX documentation. After a reconfiguration of the switch, give it several minutes for convergence to take place and to let the system settle. A flooding network traffic loop state may happen in several circumstances: a. RSTP not enabled on an MPX (factory default will reset RSTP to disabled) Note: The Device Report will extract information directly from the controller b. MPX not warm started after setting RSTP c. A switch misconfiguration (Ex. Port not set to Non-STP On) A restart (power off) of the switch may be necessary to recover d. Too many RSTP devices in a loop (>39 including the Skorpion switch) e. IP address conflict This state can be observed when all the controllers go offline and access to the switch config page isn’t possible. It’s best to get RSTP working with MPXs on each individual switch with separate rings and then daisy chain them after configuring Auto-Mdix first and finally plug in the ethernet cable into the next switch. Using 2 PCs can be helpful when setting these up so that 1 can be used to access the switch(s) on the 192.168.92.x network and the other with EBO running on the other network that the ASP is set to. Otherwise switching the NIC settings back and forth is cumbersome. Once both switches are configured and both are working with RSTP, controllers may still show offline. A power cycle can clear this up so that the ASP can reassign an IP with both switches connected. *** 1 MPX controller that has not been set to RSTP will throw the whole system into offline mode. Use the device report to ensure every single controller has been set to RSTP AND has been warm started.  ***   Using the Control Panel MP Series devices link, the Search feature and the Device report in EBO can be helpful to observe all the necessary settings for MPX and RSTP Control Panel MP Series devices link

Issue How do I locate the latest patch files (modules) for the I/A Series G3 maintenance builds (3.6.407, 3.7.108, 3.8.41) Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.407, 3.7.108, and 3.8.41 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution The latest consolidated patch files for I/A Series G3 maintenance builds 3.6.407, 3.7.108, 3.8.41 are listed below.  The files contain updated modules and a set of release notes.  The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric EcoBuildings Exchange Extranet and enter Consolidated_Patches in the search area or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes bacnet3.6.407.2 baja 3.6.407.3 eibnetip 3.6.407.1 hx 3.6.407.1 mbus 3.6.407.3 ndriver 3.6.407.1             Consolidated_Patches_3.7.108.2.7_SE_02092016.zip   ...  Click here for Release Notes     Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes   Consolidated_Patches_3.7.108.2.7.1_SE_06282016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1 weather 3.7.108.1   Consolidated_Patches_3.8.41.2.9.1_SE_06282016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 weather 3.8.41.1 web 3.8.41.1           ********* Previous Release History ********* Consolidated_Patches_3.7.108.2.7_SE_02092016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1       Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes bacnet 3.8.41.12 baja 3.8.41.2 bajaui 3.8.41.1 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.1 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1 Consolidated_Patches_3.8.41.2.9_SE_04052016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1   Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes

Issue Satchwell ZKM series Rotary Actuator requires replacement due to obsolescence. Environment Satchwell ZKM Rotary Actuator installed on Satchwell MBF series Rotary Shoe Valve Body. Satchwell ZKM Rotary Actuator installed on Satchwell MZF series Plug and Seat Valve Body. Cause Obsolescence of Satchwell ZKM series Rotary Actuator Resolution OVERVIEW The Satchwell ZKM Actuator was compatible with both Satchwell MBF series Flanged Rotary Shoe Valve Bodies and Satchwell MZF series Flanged Plug and Seat Valve Bodies, subject to the installation of an appropriate Linkage Kit. Various models of the ZKM Actuator were available, each differing in the number and type of electrical interface provided, enabling the Actuator to be installed in a range of control applications. Interfaces included Transfer Switches, Auxiliary Switches and Feedback Potentiometers, thus resulting in differing wiring connection options between the ZKM Actuator and its associated Controller and other peripherals. Details of the numerous ZKM Actuator variations available may be viewed here. In view of the differing wiring connection options that may be found on site, it is intended to deal only with the most common 6-wire connection option here. Please therefore check the number of wires connected to the ZKM Actuator before proceeding, as this will assist in confirming the suitability of the ZKM Actuator 6-wire connection option replacement suggestion described here.   1. ACTUATOR REPLACEMENT The Actuator comprising a 6 wire electrical connection enabled it to be operated from a Satchwell Z Monotronic or CZT Climatronic Proportional Controller as follows :- Terminal 1 – Open signal Terminal 2 – Close signal Terminal 3 – Common Terminal A – 135 ohm Feedback Potentiometer – winding Terminal B – 135 ohm Feedback Potentiometer – wiper Terminal C – 135 ohm Feedback Potentiometer – winding If all 6 wires are connected then the ZKM Actuator may be replaced either by the Schneider Electric MD20A Actuator or the M800 Actuator, depending on the type of Valve Body to be controlled :- MBF ROTARY SHOE VALVE BODY APPLICATIONS :- MD20A-24 + Linkage Kit LMD-MBF (914-1070-000) Details of the MD20A Actuator may be viewed here Details of the LMD-MBF Linkage Kit may be viewed here N.B. Should the Satchwell ZKM series Actuator include a wired Auxiliary Switch then the following Accessory should also be installed on the S-E MD20A Actuator as appropriate :- MD-S2 - Two independent SPDT 1mA -- 3(0.5)A, 250 V AC Auxiliary Switches. (914-1061-000) Should the Satchwell ZKM series Actuator include a wired Transfer Switch then the following Accessory should also be installed on the S-E MD20A Actuator as appropriate :- MD-S2 - Two independent SPDT 1mA -- 3(0.5)A, 250 V AC Auxiliary Switches. (914-1061-000) Details of the MD-S2 Auxiliary Switch Kit may be viewed here MZF PLUG AND SEAT VALVE BODY APPLICATIONS :- M800 + Linkage Kit L2SV (880-0124-000) Details of the M800 Actuator may be viewed here Details of the L2SV Linkage Kit may be viewed here N.B. Should the Satchwell ZKM 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) Should the Satchwell ZKM series Actuator include a wired Transfer 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 S-E Forta M800 Actuator to replace an existing Satchwell ZKM series Actuator. The S-E Forta M800 Actuator may be used to replace an existing Satchwell ZKM series Actuator but it should be noted that where this is to be connected directly to a Satchwell Controller, an independent Transformer rated to provide the greater level of power required by a single S-E Forta M800 Actuator (50VA) compared to that available at the CZT Controller (10VA) will also be required. (e.g. S-E Transformer Type TR60) Details of the Schneider Electric TR60 Transformer may be viewed here In such installations not only will the ZKM need to be replaced but the associated Proportional Controller will also need to be replaced.   2. PROPORTIONAL CONTROLLER REPLACEMENT The ZKM Actuator was compatible with a number of Satchwell Proportional Controller types including Z Monotronic, CZT Series 1 and CZT Series 3 Z MONTRONIC CONTROLLER APPLICATIONS :- If the Proportional Controller is a Z Monotronic type then this should be replaced by the Satchwell CZT5305 Proportional Controller. The associated Satchwell 3 wire Sensor will also need to be replaced by a S-E 2 wire Sensor compatible with the CZT5305 Details of a compatible Room Temperature Sensor may be viewed here. Details of a compatible Duct Temperature Sensor may be viewed here. Details of a compatible Immersion Temperature Sensor may be viewed here. The replacement Immersion Temperature Sensor may be installed in the existing Immersion Temperature Sensor Pocket with the aid of an Adaptor DWA0001. Details of the DWA0001 Adaptor may be viewed here. Details of the CZT5305 may be viewed here.   CZT CONTROLLER APPLICATIONS :- If the Proportional Controller is a CZT Series 1 or CZT Series 3 type then this should be replaced by the Satchwell CZT5305 Proportional Controller. The associated Satchwell 2 wire Sensor may be retained if desired. Details of the CZT5305 may be viewed here.

Issue Questions regarding specifications of SmartStruxure Hardware Inputs and Outputs Product Line EcoStruxure Building Operation Environment SmartStruxure I/O Modules: AO-8, AO-8-H AO-V-8, AO-V-8-H DI-16 DO-FA-12, DO-FA-12-H DO-FC-8, DO-FC-8-H RTD-DI-16 UI-8-AO-4, UI-8-AO-4-H UI-8-AO-V-4, UI-8-AO-V-4-H UI-8-DO-FC-4, UI-8-DO-FC-4-H UI-16 Cause Different I/O modules have different electrical specifications Resolution Universal Input Specifications Universal inputs can be configured as voltage, current, thermistor, resistance, digital or supervised inputs. Voltage Input Specifications: Range - 0 to 10 VDC Resolution - 12 bit Accuracy - ±(0.7mV + 0.2% of reading) Current Input Specifications: Range - 0 to 20 mA Resolution - 12 bit Accuracy - ±(0.03 mA + 0.4% of reading) Resistance Input Specifications: 10 Ohm to 10 kOhm 10 kOhm to 60 kOhm Thermistor Input Specifications: Range - -50 to 150° C (-58 to 302° F) Thermistors: 10k Type I (Continuum), 10k Type II (I/NET), 10k Type III (Satchwell), 10k Type IV (FD), 1.8k (Xenta), 10k Linearized (Satchwell DRT), 10k Type V (FD w/ 11k shunt), 1k (Balco), 20k (Honeywell), 2.2k (Johnson Controls) Digital Output Specifications Form C Relay: Terminal - Common (C), Normally Open (NO), Normally Closed (NC) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 3 A Form A Relay: Terminals - Common (C), Normally Open (NO) Minimum Pulse Width - 100 ms minimum Isolation - 1500 VAC minimum, coil to contact Cycle Life - At least 100,000 cycles Contact Rating - 250 VAC, 30 VDC, 2 A LED Specifications: LED Polarity - Represents the actual state of the output; ON if the output is active, OFF if the output is inactive LED Color - Green Analog Output Specifications Analog outputs can be configured as voltage or current. Module Voltage Output: Range - 0 to 10 VDC Resolution - 50 mV Accuracy - ±100 mV Terminals - Voltage (V), Return Minimum Load - Source, 2 mA; Sink, -1mA Current Output: Range - 0 to 20 mA Resolution - 0.1 mA Accuracy - ±0.2 mA Terminals - Current (I), Return Maximum Load - Output load should not exceed 650 Ohms Supervised Input Specifications Supervised inputs can be used to detect sabotage. Detected resistor values - Open circuit, short circuit, contact open, and contact closed. 5 volt circuit, 1 or 2 resistors, monitored - Series only, parallel only and series and switch combinations. For a 2-resistor configuration, each parallel. Resistor value range - 1k to 10 k resistors should have the same value. The selected resistor value needs to be defined in the system. RTD Input Specifications The specifications of the RTD-DI-16 are extensive and thus are best viewed directly in the data sheet available on the Buildings Download Center: RTD-DI-16 Specification Sheet You can also download the specification sheet here: IO Module RTD-DI-16 Specification Sheet (July 2014).pdf.

Issue Binding a SmartStruxure Analogue value to a Analogue output in the SE IntesisBox (Panasonic Air Conditioning). Environment IntesisBox Panasonic RPM Read Property Multiple Cause Attempting to bind the analogue value to the IntesisBox analogue output causes the following error; Resolution In this case, the AS database has the wrong unit (no-units) associated with the object, since it does not match to the units in the device "Degrees-Celsius" the failure occurs' This is corrected in StruxureWare Building Operation 1.5, where the unit id is not uploaded if the device does not support read-property-multiple, and it appears from the device documentation, that the IntesisBox does not support RPM. As an immediate workaround, the user can configure the unit id of the analog output object directly - configure the "Value" property to have a unit of Degrees Celsius.  To view the IntesisBox Panasonic manual, please click HERE.

Issue .xif file not available for download. Product Line Field Devices, Other, TAC Vista Environment MF20-24M 1M54 00 MF20-24L actuator Cause When configuring the MF20-24L in LonWorks, .xif file is necessary.  Resolution All necessary files for LON connectivity are available here: lon_actuator_v3.0 (1).zip

Issue What are the setup requirements for a L-switch on a classic network Environment Loytec L-Switch Cause What is the best way to setup a L-switch in a Vista classic network. Resolution The best option for a L-Switch on a classic network is in the Smart Switch Mode. In this mode the L-Switch decides based on the destination address of the message, which port(s) the message will be forwarded to. This functionality isolates network traffic. The dip switch settings for this setup are shown here.  Here is a link to the Loytec manual for the wiring configurations.

Issue VisiSat 2.1 Build 185/196 Cannot find VisiSat “CustomiseUI” add-on to Visio. Environment Internal error 0x86DB08A9 VisiSat CustomiseUI Visio VisiSat 2.1 Build 185 VisiSat 2.1 Build 196 Cause Visio 2003 does not recognise or register VisiSat 2.1 Build 185/196 installation CustomiseUI. Some or all the files required by VisiSat are missing. You may need to re-install Visio and/or VisiSat to clear the problem. Resolution When VisiSat 2.1 Build 185/196 on some Windows XP pro / Visio 2003 computers the following error is displayed. Carry out the following; which should fix the problem. Open Visio 2003 (Not VisiSat) On the menu bar, under tools select options. Select the advance tab. Select file paths. Delete all entries. Then select OK Select OK. OK the next window Visio 2003 should now close. Run up VisiSat VisiSat should run up OK now. If you close VisiSat and open Visio 2003 the paths should now show. VisiSat should open correctly now. Options: Most of the enhancements in VisiSat 2.1 build 185/196 are to incorporate StruxureWare functionality. If you are running VisiSat on Windows XP with Visio 2003, then consideration could be given to using VisiSat 2.1 build 148 instead. If you are running on Windows 7 you could consider upgrading the Visio 2003 software to Visio 2007 or Visio 2010. Click here to download VisiSat 2.1 Build 148. (Direct link) (files size is 42 meg). (your original VisiSat registration form (version 2.0/2.1 only), provides proof of purchase and will be required when unlocking this VisiSat version. If you require further assistance, please contact Product Support.

Issue Resistance readings Environment Sensor Resistance Chart Type T Cause Resistance Resolution SENSOR CHARACTERISTICS   DRT DOT   DD 1401 DW 1202   DW 1204 DWS 1202   DO 2202 -40 to+40'c     DDT DWT   DR 2253 DWS 1301                 DST DOS                                                 Sontay Type SAT 1   Sontay Type SAT 2   Sontay Type SAT 3   Sontay Type SAT 4                               °C Ohms   °C Ohms   °C Ohms   °C Ohms                               -40 9711   0 2094   20 2708   -40 2317     -35 9604   1 2079   25 2592   -35 2246     -30 9465   2 2063   30 2474   -30 2163     -25 9288   3 2046   35 2346   -25 2067     -20 9067   4 2027   40 2216   -20 1962     -15 8796   5 2010   45 2086   -15 1849     -10 8472   6 1992   50 1950   -10 1733     -5 8093   7 1973   55 1818   -5 1617     0 7661   8 1953   56 1792   0 1504     5 7182   9 1934   57 1766   5 1397     10 6667   10 1911   58 1741   10 1298     15 6126   11 1892   59 1718   15 1208     20 5573   12 1872   60 1694   20 1128     25 5025   13 1851   61 1669   25 1057     30 4492   14 1830   62 1646   30 996     35 3987   15 1809   63 1622   35 942     40 3518   16 1787   64 1600   40 897     45 3089   17 1764   65 1578           50 2702   18 1740   66 1553           55 2358   19 1716   67 1530           60 2056   20 1690   68 1508           65 1792   21 1667   69 1484           70 1563   22 1644   70 1461           75 1364   23 1621   71 1439           80 1193   24 1596   72 1417           85 1047   25 1574   73 1396           90 921   26 1549   74 1375           95 815   27 1524   75 1353           100 722   28 1500   76 1333           105 643   29 1476   77 1312           110 575   30 1452   78 1293           115 517   31 1430   79 1276           120 466   32 1406   80 1258           125 423   33 1383   81 1240           130 386   34 1359   82 1222           135 353   35 1336   83 1205           140 324   36 1312   84 1188           145 300   37 1289   85 1171           150 278   38 1267   86 1154                 39 1243   87 1138                 40 1219   88 1122                 41 1198   89 1107                 42 1176   90 1089                 43 1155   91 1075                 44 1134   92 1061                 45 1113   93 1047                 46 1092   94 1033                 47 1072   95 1020                 48 1052   96 1004                 49 1033   97 991                 50 1013   98 978                       99 964                       100 950                                   Click here to download a pdf with this information.

Issue Modem commands for the internal modem for the 9680 are needed Environment 9680 RAS Cause Troubleshooting the modem in the 9680 may require knowledge of the Microtech modem and the commands Resolution The Netcontroller II Operation and Technical Guide references "RJ Modem AT Commands Reference" in order to customize the modem initialization string Click her to download RJ Modem AT Commands Reference There is no option for changing the DTMF frequency Guide"