Building Automation Knowledge Base

Issue When configuring a BBMD what is the Broadcast Distribution Mask and what are the valid settings for the field. Continuum EcoStruxure Building Operation Product Line EcoStruxure Building Operation, Continuum Environment Building Operation Automation Server Building Operation Enterprise Server Continuum CyberStation bCX4xxx Cause Documentation Resolution When configuring a BBMD the BACnet protocol defines two methods of propagating the broadcasts messages to other networks. The two methods are referred to as One-Hop also known as a Directed Broadcast and Two-Hop.   Note: In this article the subnet mask is shown using Classless Inter-Domain Routing(CIDR) notation. An IPV4 address is 32 bits long, CIDR notation defines the number of bits used for the subnet mask. The most commonly used are: /8 or 255.0.0.0 /16 or 255.255.0.0 /24 or 255.255.255.0 /32 or 255.255.255.255 One-Hop With the One-Hop method the local BBMD transfers the message directly to the remote devices via the remote router. In this case the IP routers have to support the transfer of IP broadcast messages to remote IP subnets Figure 1 Figure 1 above illustrates the one-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a message directly to the broadcast address of the 192.168.1.0/24 subnet, it is then up to Router2 to send the directed broadcast to all devices on the subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks. (i.e a bCX hosting an MSTP network on COMM2)   Two-Hop With the Two-Hop procedure a BBMD device transfers broadcast messages to a further BBMD in the remote IP subnet, which then distributes the messages in its local network as IP broadcast messages for its IP subnet. Any device on the subnet that is acting as a router to other networks will then also re-broadcast the message on those networks.(i.e a bCX hosting an MSTP network on COMM2) Figure 2 Figure 2  above illustrates the two-hop method, when the bCX1 which has been configured to take the role of BBMD for network 172.16.0.0/16 detects broadcast messages such as WHO-IS, I-AM etc, it sends a unicast message to each BBMD device on its table, it is then up to each BBMD device on each subnet to send a broadcast that will be heard by all devices on the subnet. Which distribution mask should be used? As mentioned earlier, in order for the one-hop method to work, the router on the remote subnet MUST be configured to process incoming messages sent to the broadcast IP address, the two-hop method on the other hand is guaranteed to work, so when in doubt use the two-hop method. Most sites use two-hop distribution for the reason stated above,, the only obvious disadvantage of the two-hop method is that it is a little more verbose than the one-hop method since the message appears twice on the subnet, once as a unicast sent to the BBMD device and then again as a broadcast sent by the BBMD device. In Building Operation and Continuum the distribution mask defaults to the two-hop method (/32 or 255.255.255.255) How to configure the distribution mask For one-hop enter the subnet mask of the remote network in the distribution mask, the system will apply the mask to the IP address to obtain the broadcast address for the remote network. For two-hop enter 255.255.255.255, this tells the system not to do a direct broadcast and instead do a unicast to the remote BBMD device. Sample distribution mask In the BBMD table of a bCX shown in the screen shot above, BDT #1 and #3 use the two-hop method while BDT entry #2 uses the one-hop method.

Issue There is no full end to end description on how to test SNMP alarms in SmartStruxure 1.6.1 and later Product Line EcoStruxure Building Operation Environment SNMP Alarms Cause Only a guide on how to create the SNMP alarms is available, but there is no guide available on how to test them. For general information regarding SNMP traps, refer to the following Web Help links: Versions 1.6 and 1.7 SNMP Notification Properties Create SNMP Notification Wizard – SNMP Notification Page SNMP Notification View Version 1.8 and later SNMP Notification Distribution Method Create Notification Wizard - Configure SNMP Page Resolution Download and install "MIB Browser" from iReasoning Download the mib file for SmartStruxure Load the SmartStruxure mib file into the MIB Browser through "File"-->"Load MIBs", and select the SmartStruxure mib file Create a simple alarm in SmartStruxure and make it trigger on a digital point Create a SNMP notification with the following settings. To get to the conditions/filter, open (double click on it or hit enter) the SNMP notification. Only showing the properties of it will not show the filter settings. "Address" is the address of the SNMP manager that receives the SNMP notification, in this test "localhost" since the SNMP manager is installed locally. "User name" is the user name of the user on the SNMP manager that receives the notification. In filter settings, select normal and alarm state, and add "Source server = *" as a condition In the MIB browser, select "Tools"-->"Trap Receiver" Trigger the alarm in SmartStruxure An alarm will now be seen in the MIB browsers trap receiver window

Issue What are the differences between the IAC 400 and the IAC 420 controllers? Product Line Field Devices, Other, Satchwell MicroNet, Satchwell Sigma   Environment IAC 400 IAC 420 Cause The IAC 400 controller is obsolete and its replacement is the IAC420. Resolution Hardware differences; The IAC 400 has 3 Temperature, 2 Analogue and 1 Digital input, where as the IAC 420 has 6 Universal inputs. Communications differences; The IAC 400 controller uses terminal 3 to earth the communications cable screening, on the IAC 420 the screening must be connected to a good earth and not terminal 3. Tables and offsets; Because the IAC 420 has different inputs that tables and offsets are changed, please review IAC Controllers - Tables and Offsets. IAC 400 Wiring details. For the full data sheet please click HERE.   IAC 420 Wiring details. For the full data sheet please click HERE.

Issue The Drayton Theta YBM2A Valve Body / Actuator assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve YBM2A Cause The Drayton Theta YBM2A Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBM2A Valve Body / Actuator assembly is obsolete, and there is no purpose built replacement. The Valve Body was available in 1.1/4", 1.1/2" and 2" B.S.P. sizes and was normally installed as a mixing valve in variable temperature, constant volume, compensated heating circuits. No Valve Body / Actuator assemblies are currently available in these sizes. Details of the YB Valve Body may be viewed here.   VALVE BODY REPLACEMENT To replace the YBM2A Valve Body the following is required:- S-E Satchwell MB Valve Body of appropriate size - MB1552 (1.1/4"), MB1602 (1.1/2"), MB1652 (2") Details of the MB Valve Body may be viewed here.   ACTUATOR REPLACEMENT The YBM2A Actuator comprised a 3-wire electrical connection enabling it to be operated by a Mains Voltage changeover contact device as follows :- Terminal M1 – Open signal Terminal M2 – Close signal Terminal M3 – Common The YBM2A Actuator may be replaced by one or other of the following S-E Actuators :- MD10B-230 MD20B-230 (if MD10B-230 not available) Details of the MD10B-230 Actuator may be viewed here. Details of the MD20B-230 Actuator may be viewed here. N.B. The YBM2A Actuator also included an additional 3-wire electrical connection associated with an integral S.P.C.O. Auxiliary Switch wired as follows :- Terminal S1 – Normally Closed Contact Terminal S2 – Common Terminal S3 – Normally Open Contact Where external wiring is connected to the YBM2A Actuator Auxiliary Switch then an Auxiliary Switch Kit containing a S.P.C.O. Auxiliary Switch should be installed on the MD Actuator. Auxiliary Switch Kit MD-S1 (914-1060-000) Details of the MD-S1 Auxiliary Switch Kit may be viewed here. The MD-S1 Auxiliary Switch Kit should be wired as follows :-. Terminal S1 – Common Terminal S2 – Normally Closed Contact Terminal S3 – Normally Open Contact   LINKAGE KIT A Linkage Kit will also be required in order to enable the MD Actuator to be mounted on the MB Valve Body. Linkage Kit LMD/AR-MB (914-1071-000) Details of the LMD/AR-MB Linkage Kit may be viewed here In such 3-wire installations the YBM2A Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV property  0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue Activation of the Security Expert SSN with a new installation of the client software, software extensions (e.g. SX-VIM, SX-DOR-50) and integration licenses (e.g. SX-NVR, SX-CAM-10) need to be completed manually because there is no Interne access. Product Line EcoStruxure Security Expert Environment Licensing Cause The computer which the Security Expert client is installed on, does not have Internet access to use the 'Automatic License Update' method to activate the license. The manual method must be used to register and obtain the new license. Resolution In the Security Expert client go to About | License | information make a note of your system's SSN In the Security Expert client go to About | License | License Update and select Generate a License Request File for this System Copy the 'ICT_LicenceRequest.req' license request file produced onto a machine that has Internet access. Navigate to https://se.ict.co/license/ and enter your details on this web page. Enter the SSN for your system Upload the 'ICT_LicenceRequest.req' license request file generated previously and Submit. You should then be able to download a 'Security Expert YJWB...............O4PJ5W License.lic' file. Return to your offline Security Expert Client and go to About | License | License Update , Select Browse for your Downloaded License file Select the 'Security Expert YJWB...............O4PJ5W License.lic' file downloaded previously. Once the license update is complete shut down the client and restart the services   Support for manual activation: v4.2.194 - Manual activation is supported. v4.2.216 - Manual license activation's are no longer supported and an Internet connection is required on the Security Expert installation to be able to perform a new activation or update a license. v4.2.243 - Manual activation is supported. v4.3.x - Manual activation is supported.

Issue The Drayton CRL 240 Actuator / Valve assembly is to be replaced. Product Line Field Devices Environment Replacement Drayton Actuator Valve CRL 240 Cause The Drayton CRL 240 Actuator / Valve is obsolete Resolution The Drayton CRL 240 Actuator / Valve assembly is obsolete and there is no purpose built replacement. The associated Drayton Valve Body was available in numerous sizes.  These sizes are not available in current combined Actuator / Valve designs. To replace one of the above Actuator / Valve Body combinations the following are required :- Valve sizes ½” – 2” Valve – MB(1/2" - 2") Actuator -  MD10B-230 (  MD20B-230 could  be used if MD10B-230 is not available) Auxiliary Switch - MD-S1 ( MD-S2 could be used if MD-S1 is not available) Linkage Kit - LMD/AR-MB or the RM3601 actuator without the need for a linkage kit Linkage Kit Select S-E LMD/AR-MB Linkage Kit. (914-1071-000) MBF Valve sizes 65mm – 100mm Could be replaced by the VTRE range To view the MB Valve Data Sheet, please click here. To view the MD10B Actuator Data Sheet, please click here. To view the MD-S1 Auxiliary Switch Data Sheet, please click here. To view the LMD/AR-MB Linkage Kit Data Sheet, please click here. To view the LMD/AR-MBF Linkage Kit Data Sheet, please click here. To view the RM 360 data sheet please click here

Issue Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly requires replacement. Environment Stand alone Satchwell “M 1201” Actuator forming part of combined Actuator / 2-port Valve Body assembly M 1201 Actuator 2-port Valve Body Cause Obsolescence of Satchwell “M 1201” forming part of combined Actuator / 2-port Valve Body assembly. Resolution There is no direct replacement for the "M 1201" Actuator and as a result both the "M 1201" Actuator and the 2-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly with Schneider Electric MD10B-230 Actuator, LMD-MB Linkage Kit and Satchwell MB series 3-port Valve Body of appropriate size. Details of the original Satchwell “M 1201” combined Actuator & 2-port Valve Body assembly may be viewed here. Details of the replacement Schneider Electric MD10B-230 Actuator may be viewed here. Details of the replacement Schneider Electric LMD-MB Linkage Kit may be viewed here. Details of the replacement Satchwell MB 3-port Valve Body may be viewed here. N.B. Satchwell MB series 3-port Rotary Shoe Valve Body may be converted for use as a 2-port Zone Valve by means of the installation of a plumber’s plug in Port 3 Install plumber's plug in Port 3 of MB series 3-port Rotary Shoe Valve Body. Tighten plumber's plug sufficiently to ensure PN 10 rating of Valve Body is not compromised. It is possible that the "M 1201" Actuator may have been fitted with an Auxiliary Switch. If so then an MD-S1 Auxiliary Switch may be fitted to the MD10B-230 Actuator if required. Details of the MD-S1 Auxiliary Switch may be viewed here.

Issue How to add Web Service and create Simple XML Web Service with Graphic Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation site with release 1.2 or later Cause What are Web Services and how to add to my existing StruxureWare Building Operation site. How to add XML files and how to add to a project or site How to create values from the XML Files added How to make a graphic that uses the values from XML Service Resolution Wikipedia: A Web Service is a method of communication between two electronic devices over the web (internet). W3C: A "Web Service" as "a software system designed to support interoperable machine-to-machine interaction over a network." Web Services: Are hardware, programming language, and operating system independent Applications written in different programming languages and running on different platforms can seamlessly exchange data over intranet or the internet using Web Services Web Service interfaces are supported in both the AS and ES(does not support connection over a ProxyServer) Like BACnet, Lon, and Modbus, you can create a Web Service interface. EWS Interface - EcoStruxure Web Services Script Web Service - Generic Consume via Script (Web Service addition Script Web Service) Simple XML Web Service - Rest Generic Consume via Binding Tool SOAP Web Service - SOAP Generic Consume via Binding Tool (Web Service addition SOAP Web Service) This article explains adding Weather for a particular location data using Simple XML: Select New > Interface > Web Service > Simple XML Specify the URL for this data (to find the weather for your area, Google XML data Make changes to polling, alarm, retry interval Choose Create Now you can Create a value from that Simple XML Web Service by highlighting and select New > Value > and type of value. Select Analog for temperature, String Value for wind direction and so forth. One can add as many of the values as desired. The Simple XML List View would look like the below screen capture. Lastly for Simple XML Web Service a graphic is created and the values which come from the XML Web Service are place on the page. Also check out the SmartStruxure - Web Services - Simple XML Interface Quick-Help video on the Exchange.

Issue Types of TAC Erie Pop Top valves and actuators available from Schneider Electric in the UK  Product Line Field Devices Environment Pop Top Valves Pop Top Actuators Cause Actuator Part no's available in the UK Valve Part No's and connection types available in the UK ZY valve and actuator replacement Resolution   Actuators AH13U230 - High Close Off - Spring Closed 230Vac Actuator c/w 36" Lead AH13U23A - High Close Off - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG13A230 - Spring Closed - 24Vac Actuator c/w 36" Lead AG13A23A - Spring Closed - 24Vac Actuator c/w 36" Lead + Aux Switch AG13U230 - Spring Closed - 230Vac Actuator c/w 36" Lead AG13U23A - Spring Closed - 230Vac Actuator c/w 36" Lead + Aux Switch AG23U230 - Spring Open - 230Vac c/w 36" Lead AG23U23A - Spring Open - 230Vac c/w 36" Lead + Aux Switch AG23A230 - Spring Open - 24Vac c/w 36" Lead AG23A23A - Spring Open - 24Vac c/w 36" Lead + Aux Switch Valves (Note:NPT is American connection) VT2222 - 2way - 1/2" NPT 2.5Cv VT2223 - 2way - 1/2" NPT 3.5Cv VT2231 - 2way - 1/2" BSP 1.0Cv VT2232 - 2way - 1/2" BSP 2.5Cv VT2233 - 2way - 1/2" BSP 3.5Cv VT2325 - 2way - 3/4" NPT 5.0Cv VT2327 - 2way - 3/4" NPT 7.0Cv VT2332 - 2way - 3/4" BSP 2.5Cv VT2333 - 2way - 3/4" BSP 3.5Cv VT2335 - 2way - 3/4" BSP 5.0Cv VT2337 - 2way - 3/4" BSP 7.0Cv VT2437 - 2way - 1" BSP 8.0Cv VT3231 - 3way - 1/2" BSP 1.5Cv VT3232 - 3way - 1/2" BSP 3.0Cv VT3233 - 3way - 1/2" BSP 4.0Cv VT3332 - 3way - 3/4" BSP 3.0Cv VT3333 - 3way - 3/4" BSP 4.0Cv VT3335 - 3way - 3/4" BSP 5.0Cv VT3337 - 3way - 3/4" BSP 7.0Cv VT3437 - 3way - 1" BSP 8.0Cv Erie™ PopTop™ Series Valve Bodies and Actuators - Installation Instructions.pdf for the VT and VS valve, AG and AH actuator. Note: Only those listed above are available in the UK.

Issue Need to configure SMTP settings to use a Google SMTP server Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause There is no SMTP settings configured by default Resolution Note: As of May 30, 2022 please also consult Less secure apps & your Google Account 

Issue Connecting a serial cable to a Xenta 5/7/9xx controller Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Xenta Servers have a service portal for use with HyperTerminal with a serial connection to the RS-232B port. Resolution Connect a serial cable, Programming Serial Kit, part no. 0-073-0920-0, between the PC and the RS232 port B on the TAC Xenta.  For more information about the cable see Cable Guide OFL-3972. Go to Start/All Programs/Accessories/Communications/HyperTerminal, and open the HyperTerminal. In Connection Description Windows, type any name you like in the Name box. Click OK. In the Connect to window, choose the correct COM port that the RS-232 cable is using. If you do not know which COM port it is using. Go to your computer device manager. (Right click on “My computer” icon, and choose “Manage”. Then under “System Tools”, choose “Device Manager”. Find “Ports (COM & LPT)” and expend it Find the COM port number that is used by the RS-232 cable. Click OK. In the COM Properties window, type 9600 for “Bits per second”, 8 for “Data bits”, “Parity” is None, “Stop bits” is 1, and “Flow control” is None. Click OK. Options: you can save this setting for future use. Click on File Menu and Save. Press ENTER to activate the command prompt. Default username and password is both “root”. Type “root” and press ENTER for both the username and password. Type “setip” and press ENTER. NOTE: Product support has also witnessed strange behavior with serial connections when certain laptops were not plugged into a power source or the Xenta Server was not grounded. If connection problems persist after the connection setting above are verified, make sure the Hyperterminal PC is plugged into a 120 vac power source.

Issue Update OS, changing a controller, BACnet to Infinet or Infinet to BACnet Can b3 controllers be converted to i2 controllers? Can i2 controllers be converted to b3 controllers? Converting between bCX4040 and bCX9640   Product Line Andover Continuum, EcoStruxure Building Operation Environment i2 b3 Controllers - See Compatibility Matrix bCX Controllers - Continuum 1.7 onwards Cause Only a limited number of controllers can be converted, BACnet to/from Infinet, using Update OS. Resolution The following controllers can be converted between Infinet and BACnet, using the appropriate firmware files: bCX (bCX4040 to/from bCX9640) (options like Xdrivers, node count, IO modules and expansion IO modules are not effected) i28xx-V - b38xx-V (i2865-V to/from b3865-V, i2866-V to/from b3866-V, i2885-V to/from b3885-V) Please see link for swapping the firmware of non -V model i2/b3 Attempting to flash (Update OS) any other controllers BACnet to/from Infinity is not recommended. In nearly every instance, the result will be a non-functioning controller.   UPDATE: A procedure is now available to convert the non -V i2s to b3s in the field https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/416712    (Note: In the bCX controllers, the ACCNetID will revert back to the default of "1", you may need to change this in the Controllers configuration webpage back to what it should be.  See Will IP settings persist when flashing a bCX4040 (BACnet) to a bCX9640 (Infinet)? for details.)   Please refer to Exchange for specific firmware: BACnet Firmware Infinet Firmware The following can be used as a general rule to determine which OS is currently running in the controller. bCX only. (b3 & i2 CPU is green) CPU LED is Green = BACnet OS CPU LED is Yellow = Infinet OS

Issue Modbus Register Groups feature can overcome some Modbus communication problems. It has been seen before where the Modbus controller falls offline for a few seconds then comes back online. This cycle will repeat every few seconds. When register groups are not used, there may also be issues with the amount of time it takes for a Modbus points to update. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Enterprise Server Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Cause In a normal Modbus network, a Modbus polling device obtains data from a polled device by sending a query message to the device and then waiting for the response message that contains the requested value from the selected register. If data from another register is required, the polling device sends out a new query message and awaits the response message. This process is repeated until all subscribed points values have been read. The Modbus Register Groups are a batch read function to poll Modbus devices. Instead of reading each register individually, the batch read function reads registers in manually created groups. When all registers in a group have been read, the response message returns subscribed register values for the whole group. Register grouping provides a dramatic saving in the time taken to poll your devices. For more guidance and tips on this topic, see Section "Batch Read Function" in the EcoStruxure Building Operation Technical Reference Guide.  Note: When viewing a graphic containing Modbus values, those values will update at the same interval as their Modbus register group. Resolution When grouping Modbus points, it is important to keep in mind some of the following points. Try to ensure that as many Modbus points as possible are contained in as few groups as possible. This will reduce the overall time it takes the Enterprise Server or Automation Server to read all the subscribed points in each Modbus device. Network performance can be enhanced by choosing the method of grouping that is most suitable for each device in the Modbus network.  Network performance can be enhanced by selecting a different default poll time for each register group. Network performance can also be enhanced by grouping points that have the same or similar polls. Start with higher group poll times to ensure a stable system before reducing the poll time. Make sure to delete Modbus points out of a register group individually before deleting the group. If this is not done, it can cause system delays. See article Modbus Batch Read Multiple Registers Groups Creating a Modbus Register Group In Workstation, in the System Tree pane, right-click on a Modbus device and select New Object (1).  In the create object window select Modbus Register Group (2), provide a name and select Create (3). Now that the group has been created, existing Modbus points can be dragged and dropped into the group. New Modbus points can also be created in the group.  Right-click on the Modbus Register Group and select New Object (1).  In the create object window expand Modbus Point (2), select a point type (3), provide a name and select Create (4).

Issue How to change the firmware version in a controller. Product Line Andover Continuum Environment All flash-upgradeable controllers: CX9900, CX9940, ACX5720, ACX5740, all i2, b3, and bCX controllers.  Cause Controller firmware needs to be changed. Resolution Locate the firmware version that you need for each controller you want to change. The Continuum firmware files can be downloaded from the Schneider Electric Ecobuilding Exchange. The downloaded files are often a zip file which includes the release notes in PDF format and the flash file (UPD file). Note: You may need to upgrade or downgrade firmware (see also Is a controller shipped from the factory with the latest firmware revision supported in older versions of Continuum?) Make sure you check the document Andover Continuum Software and Firmware Compatibility Matrix for the appropriate firmware version for your system.   Copy the file to a disk drive accessible to your CyberStation workstation. Edit the controller object in ContinuumExplorer and click on the "Update OS" button. Browse to the file location in step 2 and click "Open". A progress box "Updating Controller OS..." will appear. During this time the controller is reset and not functional.  Once complete, and if successful, you will get  a dialog box indicating that the upload was successful and the controller will return On-Line momentarily. Click OK. Click the refresh button in the controller editor. Once the controller is on-line the version field should indicate the new version. At this point some controllers may need a reload, others will be reloaded from flash memory. This depends on the controller type. For example, the CX9900 has no flash memory and therefore will need to be reloaded. This procedure also applies to upgrading controller options such as adding Xdriver support. In this case a UPD file will be provided by the Repair Dept. In the case of added Xdriver support, after doing the Update OS procedure the version will not change. Look at the controller Options tab after it comes back online following the upgrade. The information here, such as a non-zero entry in the numbers next to the appropriate Xdriver Commport will be changed. The above procedure was based on an IP level controller such as the CX, bCX and ACX II. Infinet and MSTP controllers are done in a similar manner. IOU models are also upgraded similarly via the "Update IOU" button in the IOUModule editor. However, the files are .IOU files instead of .UPD files and the versions are in the fourth pair of characters in the Program ID field.  

Issue Where to find a statement of discontinued products if needed. Product Line Andover Continuum Environment Obsoleted Continuum Controllers DCX250 DCX 250, Netcontroller CX9000, CX9400 Infinity products Cause Which products are no longer available? Resolution The following link details all products that were discontinued in 2007/ 2008: 2007/ 2008 Discontinued Products Also the DCX250 was obsoleted in 2011 see Product Announcement Discontinuation of Infinity 01-0008-300 (DCX 250) Also see Display options now the DCX250 is no longer available for DCX250 alternatives.  Search for all discontinuation announcements on The Exchange.

Issue Which SQL query can be used to identify the database layout being used? Environment Vista 5.1.X log database Cause With the release of Vista 5.1.7 came a new logdatabase layout which is designed to improve performance especially in the area of trend and event log management. This means that there are now 2 possible logdatabase configurations. It can be important to know which version is being used before running any queries or accessing the external log data with external tools. Resolution The following query will return the database layout version when run in SQL management studio: select taclogdata.dbo.DSS_SchemaVersion() More information can be found in the Vista 5.1.7 release notes.

Issue Looking for more information on the Schneider Electric Advanced Display offering from the Smart X family of controllers. Product Line EcoStruxure Building Operation Environment SmartStruxure SmartX Controller Advanced Display Technician Tool Mobile App Cause Unsure where to locate more detail about the Advanced Display and do not know the part numbers to order the products. Resolution The Advanced Display is a convenient option for users to access, monitor, and service their SmartStruxure system. For additional information please reference the SmartX Controller - Advanced Display documents found on the The Exchange. Applications The Advanced Display comes with the SmartXKiosk application already installed on it. This app, when launched, limits which other applications may be accessed on the tablet. The only way to exit the Kiosk mode is to enter a six character PIN. Any of the available Schneider Electric apps found on the Google Play Store can be added to the SmartXKisok. Technician Tool mobile app AdaptiApps custom user apps WebStation The Technician Tool provides a simplified user interface for operation and maintenance of the SmartStruxure solution.   Communications and Wiring Options Communication Options Available Availability Wi-Fi to the BMS network (requires straight USB cable) All SmartStruxure versions USB direct communication to the Automation Server (requires Y-shaped USB cable) Versions 1.7 and newer Wi-Fi or USB direct communication to the Automation Server Premium (requires straight USB cable) Versions 1.7 and newer   The Advanced Display communicates with the SmartStruxure servers through an access point or starting in version 1.7 directly to the Automation Server via the USB port with the application named SmartX-Ad Link. If using an Automation server, the Y-shaped cable must be used to connect to a locally sourced power supply as well as to the Automation Server. The power required is 5 VDC with a minimum of 500 mA up to 1.3 A. The USB port on the Automation Server Premium (AS-P) has the ability to power the tablet directly thus only requiring a straight USB cable.    Ordering Part number Description SXWADTAB410001 Advanced Display 7 - inch - - No longer available! SXWADBUND10002 Advanced Display 10 - inch Bundle Includes Advanced Display tablet unit, mounting frame, bezel, and Micro USB 2.0 data cable 1 m (3 ft) SXWADUSBA10001 USB cable, Straight 1.5 m (5 ft) for connection to AS-P or AS-B SXWADUSBA10002 USB cable, Straight 3.0 m (10 ft) for connection to AS-P or AS-B SXWADUSBB10001 USB cable, Y-shaped 1.5 m (5 ft) for connection to Automation Server SXWADUSBB10002 USB cable, Y-shaped 3.0 m (10 ft) for connection to Automation Server   Note: The Advanced Display 10 - inch Bundle does not include a power adapter.  For configurations where the external power adapter is required the appropriate power adapter must be ordered separately for the country in which it will be installed.

Issue During certain situations, it may be required to switch from a hardwired to a wireless connection or wireless to a hardwired. In addition, you may be required to replace a failed NIC card with a new variant that may or may not be the same in terms of connection type. Other more rare situations where a technician travels with a laptop that has PCT "SERVER" mode installed would also be affected. Example: PCT Version - 1.1.2.57 Server mode was set up on a physical server that has two NIC cards. The initial setup was performed on NIC1 and now we are required to utilize NIC 2 which is wireless as a temporary solution. NIC card 1 is disabled and NIC card 2 is set up with the same IP details as NIC card1. In addition, the wireless network is an extension of the original network that was configured in NIC card 1. The server then gets rebooted. Once the server is up you start PCT and attempt to open a project. You receive the following errors: "VBoxManager.exe: error: Nonexistent host networking interface" "Failed to open project."    Product Line EcoStruxure Building Operation Environment Windows Client versions (64 Bit Only) Windows Server versions (64 Bit Only) PCT SERVER versions (64 Bit OS Only ) SBO Project Configuration Tool All versions Cause During the initial setup of Project Configuration Server mode, you are prompted to select a network interface card from a list of available NICs. PCT requires that you continue to use the same interface and if you change your connection type at the windows level PCT has no method of knowing this and will not be able to connect to previously created projects. PCT will produce the following complaint as seen in the log below: "Nonexistent host networking interface"   You can find the log path as follows: C:\ProgramData\Schneider Electric StruxureWare\Building Operation\Project Configuration Tool\loggermodule "ProjectsModule.log"   Resolution There are two solutions to address this: Revert your connection type back to the original Network Interface Card. Reboot the machine. Open PCT and attempt to get back into the project. If the idea is to stick with a different NIC, you would simply need to reinstall PCT and select the new NIC during "SERVER" mode setup. Reboot the machine. Open PCT and attempt to get back into the project.

Issue Send an SMS text message when an alarm occurs. Product Line EcoStruxure Building Operation Environment Alarming SMS Text Cause Sending an SMS Text message in response to an alarm condition will allow the responsible personnel to react immediately, even if they are not currently at the workstation. Resolution EcoStruxure Building Operation does not support direct SMS texting. One workaround is to use an Email to SMS Test service provider that handles conversion of emails to SMS, as emails are easily created in EcoStruxure Building Operation.   If direct SMS functionality is required there are work arounds with 3rd party programs such as SysManSMS via file output options (see Using Sysman alert server with StruxureWare Building Operation). Note that this third party products such as this are not supported or tested by Schneider Electric.