Building Automation Knowledge Base

Issue Drayton Theta ll EC Compensator Controller requires replacement. Product Line Field Devices, Satchwell Sigma Environment Stand alone discreet Drayton Compensator Controller :- Theta ll EC Cause Obsolescence of Drayton Theta ll EC Controller. Resolution Replace Drayton Theta ll EC Compensator Controller with Satchwell CSC Compensator Controller. N.B. Two models of the Satchwell CSC Compensator Controller are available. CSC5252 without programmer details of which may be viewed here. CSC5352 including programmer details of which may be viewed here. It should be noted that the Actuator / Valve Body assembly connected to the Drayton Theta ll EC Compensator Controller may be retained for connection to the Satchwell CSC Compensator Controller. It should also be noted however that the associated Drayton Theta ll EC Compensator Controller Sensors are also obsolete. These Sensors are not compatible with the Satchwell CSC range of Compensator Controllers and must also be replaced. Satchwell CSC Compensator Controllers are compatible with the following Sensors :-   STO 600 Outside Air Temperature Sensor, details of which may be viewed here. STR 600 Room Temperature Sensor.(Optional), details of which may be viewed here. STC 600 Surface Mounting Temperature Sensor, details of which may be viewed here. or alternatively :- STP 660 Immersion Temperature Sensor, details of which may be viewed here. plus DWA 0005 Immersion Temperature Sensor Pocket, details of which may be viewed here.

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 Satchwell "M 1301" Actuator forming part of combined Actuator / 3-port Valve Body assembly requires replacement. Product Line Field Devices Environment Stand alone Satchwell “M 1301” Actuator forming part of combined Actuator / 3-port Valve Body assembly M 1301 Actuator 3-port Valve Body Cause Obsolescence of Satchwell "M 1301" forming part of combined Actuator / 3-port Valve Body assembly. Resolution There is no direct replacement for the "M 1301" Actuator and as a result both the "M 1301" Actuator and the 3-port Valve Body to which it is connected will also require replacement.  Replace Satchwell “M 1301” combined Actuator & 3-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 1301” combined Actuator & 3-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. It is possible that the "M 1301" 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 b3 devices to EcoStruxure. Product Line EcoStruxure Building Operation Environment Building Operation Workstation b3 BACnet Cause List the methods of adding b3 devices to EcoStruxure Building Operation Resolution The following information can be found in the EcoStruxure Building Operation - Technical Reference Guide. Use the guide relevant to the release of EBO installed.   Discovering b3 BACnet Devices with the Device Discovery View Using the Device Discovery view to search deployed Automation Servers for b3 BACnet devices. For more information, see section "b3 BACnet Device Overview". To discover b3 BACnet devices with the Device Discovery view In WorkStation, click the Device Discovery view. In the System Tree pane, click the Automation Server to be searched. In Select device type, click on BACnet devices. Select the b3 BACnet device you want in the Device result pane. Map a device by dragging that device from the Device result area and dropping it in the System Tree pane. When prompted, copy the device only or copy the device and all of its children.   Learning b3 BACnet Devices b3 BACnet devices van be learned and to automatically assign the node IDs and initiate communication with devices on the MS/TP network. Tip: It is possible to learn b3 devices when the b3 devices and the Automation Server functioning as the BACnet interface are connected and online. If the b3 devices are not physically connected to the network, it is also possible to manually create and configure the devices offline in Workstation. For more information, see section  "b3 BACnet Devices. To learn b3 BACnet devices In WorkStation, in the System Tree pane, select the MSTP Network In WorkStation, on the Actions menu, click b3 devices and Learn When the b3 BACnet devices are learned, click Close If necessary, perform a download operation to eliminate any old points and programs stored on the b3 BACnet device.

Issue What is pneumatic actuator spring range shift and how can it be eliminated? Product Line Field Devices Environment Pneumatic Actuator Cause Spring range shift is an inherent feature of all spring return pneumatic actuators without positive positioners. The nominal published spring range of a pneumatic actuator without a positive positioner is the air pressure required to fully stroke the actuator WITH NO EXTERNAL LOAD. In the extend direction against an opposing load as provided by a damper or a valve, the supply air pressure must be increased above the spring range of the actuator to overcome the spring and the opposing force. In the retract direction against an opposing load as provided by a damper or a valve, the supply air pressure must be decreased below the spring range of the actuator so that the spring can overcome the air pressure and the opposing force. Under constant load conditions, the range of the actuator is offset by the amount of air pressure required to provide close-off of the damper or the valve. Resolution When is "Spring Range Shift" a concern? It is a concern when two or more pneumatic controlled devices should be sequenced from one pneumatic signal without an overlap. An example would be a normally open heating valve and a normally closed cooling valve being sequenced from a direct acting thermostat, In this example the spring range of the normally open valve will shift upward and the normally closed valve will shift downward which means the two valves may overlap. Another area of concern is that pneumatic control signal provides proper pressure span to operate the control device and provide "tight" close-off of damper or valve. Examples of limited pressure change would be: pneumatic controllers maximum output which is limited by main air pressure; the low pressure output capability of a pneumatic controller; and electronic to pressure transducer which can have a limited output such as 3 to 15 psig.   What can be done to overcome "Spring Range Shift" when sequencing devices? Sequencing can be accomplished in a pneumatic system by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment (2378-501) or controllers with separate outputs for each actuator. Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning. This is the ideal way to provide precision sequencing, since variable loading on the actuator will not effect the sequencing. Biased start ratio relays may be used to provide a method of sequencing by amplifying or shifting the pneumatic signal. For applications involving sequencing a pressure to electric (P.E.) switch with a pneumatic actuator, the P.E. can often be adjusted to operate outside the operating range of the actuator. Sometimes larger actuators will help the sequencing problem. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper and therefore reduces control signal change required to control the actuator. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, adjusting the start points can help prevent sequencing problems. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Sequencing problems can be eliminated by providing controllers with separate outputs for each actuator and do the sequencing in the controller. What can be done to increase the close-off of a damper or valve actuator due to limited or insufficient pneumatic control pressure to the control device? Proper control and close-off of the control device can be accomplished by selecting actuators with appropriate spring ranges, utilizing positive positioners (AK-42309-500 or N800-0555) or ratio relays with bias adjustment ( 2378-501). Positive positioners on damper and valve actuators provide the versatility of start point and span adjustment plus the availability of full pneumatic power for positioning (0 to main air pressure to the actuator). Biased start ratio relay provide a method of amplifying or shifting the pneumatic signal. Selecting larger actuators will increase close-off pressure. Using full actuator stroke to rotate the damper less than 90 degrees increases the force delivered to the damper. Rotating the damper 60 degrees usually provides almost full flow through the damper. If the actuator has an adjustable start point, proper adjustment of the start points will increase close-off. Normally open valves or dampers should have start point adjusted to the minimum and normally closed adjusted to the maximum. Provide electronic to pneumatic transducers with sufficient input span to obtain maximum or sufficient pneumatic output.

Issue When attempting to enable .NET Framework 3.5 on Windows using the DISM command mentioned in the WebReport installation guide, the attempt fails with error 1910 Command: dism /online /enable-feature /featurename:NetFX3 /all /Source:e:\sources\sxs /LimitAccess Deployment Image Servicing and Management tool Version: 10.0.14393.0 Image Version: 10.0.14393.0 Error: 1910 The object exporter specified was not found. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log Product Line EcoStruxure Building Operation Environment WebReports Cause The Windows Modules Intaller service is not operating correctly, and has to be restarted. The service is however protected, so this can not be done through the services control panel. Resolution Kill "TrustedInstaller.exe" from the Windows task manager (CTRL+SHIFT+ESC) Start the "Windows Modules Installer" service from Windows services (Start->Run->services.msc) Try again, either using the command or the SBO Reports Preparation tool.

Issue How to show raw card data of a badged card in Security Expert. Product Line EcoStruxure Security Expert Environment Security Expert Custom Card Format Cause Need to configure a custom card format and need to see the raw bit string to determine this. Resolution Displaying a cards raw data is a function that can be set in the Reader expander. 1. Confirm that the Display Card Data When Invalid option is enabled on the Reader tab under Misc Options. Misc options Display Card Detail When Invalid: When enabled, the reader expander will display the actual card data received from the reader when the card number is not known. This can be used to interface with custom third party applications that require their own processing of card information. This option is enabled by default and can be used to add card data to a user when operating Security Expert. When disabled the reader will display the card number not found message. 2. Next, set the Reader format on the Reader tab under Configuration to Any bit (raw). any bit raw 3. Now when badging a card at this reader port it should populate two events. One for the Card Number Raw Data and another for the Facility Code Raw Data.   Example: Read Card Number Raw Data: 46160846 Read Facility Code Raw Data: 436207616 Put the facility code into a Programmer Calculator to convert from Decimal to Binary. This is a 32-bit number. 00011010000000000000000000000000 Of the 32 bit number take the first 8 Binary digits (in the example this is 0001 1010) and convert this back to decimal. 00011010 bin = 26 dec What you should see in the decimal field is the bit length the card uses. Now in the Reader Format, it’s an experiment to find out which of the Bit options would correspond to the cards. (In the example above you would need to look through the 26 bit options.)

Issue The Drayton Theta YBM2 Valve Body / Actuator assembly is to be replaced. Environment Replacement Drayton Actuator Valve YBM2 Cause The Drayton Theta YBM2 Valve Body / Actuator assembly is obsolete. Resolution OVERVIEW The Drayton Theta YBM2 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 YBM2 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 YBM2 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 YBM2 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.   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 YBM2 Valve / Actuator assembly only will need to be replaced, while any associated Controller and Sensors may be retained.

Issue Device ID / Device Instance of SE8000 series BACnet controllers Duplicate BACnet Network Address alarms How to have 254 SSL Room Controllers on an Automation Server (AS) as shown in the SBO Automation Server and SE7000 and SE8000 - Architectural Guidelines Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment Automation Server Enterprise Server SE8000 Room Controller BACnet Cause There can be confusion from the difference in naming between SmartStruxure Lite(SSL) Room Controller(RC), SmartStruxure Building Operation and even Niagara(JACE). Bacnet Instance number in SSL = Object ID in SmartStruxure Building Operation COM Address in SSL = MAC Address in SmartStruxure Building Operation Resolution On the AS, considered is the Object ID of the two Comm Ports (as with all object IDs) they need to be unique across the system. A common ID is 1001 for CommA and 1002 for CommB of the first AS, then on the second AS CommA 2001, CommB 2002 etc. The key thing with BACnet is that every object (point, device, program, port etc) must have a unique Object ID. The SE8000 uses the Com Address referred to as the BACnet MAC Address in the AS. This, as detailed in BACnet COM Address of Room Controller SE7000 and SE8000, is the address range on just that one MS/TP bus. 1 – 127 are valid addresses, the AS (or bus master) will be address 0. If a second AS is on the same system this could use 83001 – 83127 for CommA, 84001 – 84127 CommB etc. Also SE8000 uses the BACnet Instance number which is called the BACnet Object ID in the AS. (This is the ID which must be unique across the whole system) So if you have the 2 ports used on one AS all 254 devices must have unique ID’s. When changing the Comm address in the SSL SE8000 to any value between 1 and 127, the Instance number will change as well. For example Comm address 9 would result in an Instance number of 83009. These will cover 127 stats that will go on CommA, and result in Instance numbers between 83001 and 83127. Any value above 127 will keep the Instance number unchanged. For CommB however, a site would need to change the Instance number manually. For example the first RC connected to CommB would be the 128th and would default to address 83127. So it is required to manually change the Instance number to 1083001 (up to 1083127). This defines unique Comm Addresses for ComB on the remaining 127 RC. When using an Automation Server (AS) you can find the Object ID and MAC address for devices on MSTP by using WorkStation and going to AS > System > Hardware > BACnet devices > Network_xxxx. A screen shot is below with the added columns Status, System Status, Object ID, and MAC address. In this first example, b3 controllers use the Object ID or Device ID of their serial numbers so each b3 is unique across the network. B3 controllers with serial numbers greater than 4194302 (the maximum allowed Object ID in BACnet) will be assigned a Device Object ID using a hashing algorithm to ensure it is unique. From an SE8000 series RC, BACnet network set-up screen shows when BACnet is detected in models. Select desired parameter and use up or down arrow to set parameter to desired value. The default BACnet instance number is generated by the model number and COM address of the controller. For example, The instance number of a SE8300A5B00 with a COM address of 57 is generated as "83057." The default instance number appears first. To change the instance number, use number pad and press Accept and Save. Below is a screenshot of the WorkStation logged into an AS, with the BACnet Interface and the MSTP network. The added columns show the Object ID and MAC address. Below is a screen shot of the WorkStation logged into the AS, with the System > Hardware Devices > Network_xxxx. The added columns show the Object ID and MAC address.  The screen shot below is the AS > BACnet Interface > MSTP Network > Configuration Settings.

Issue Replacement I/NET Controller NICAD Battery info., I/Net Batteries Product Line TAC INET Environment All I/NET controllers Cause Controller battery has failed, because the battery on the controller is over 5 years old   Resolution The 3 pin version Battery is used for the NPR2000 and the DPU48K (MIP Board) -- part number 3/V80H-SLF (Note this battery has to be order from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The 7910, 7920, 7930 7780 & 7940 use the 2 pin version -- part number 3/V80H-LPC (Note this battery has to be ordered from an outside Vendor and not Schneider Electric). Click here to view a PDF on this part. The battery used on the 7700, 7716, 7718, 7728, 7720, 7928, 7793, 7798B, & 7798C (and like controllers) is the Dallas/INET part number 801288-07. This also can be ordered from the Rockford order entry using 01-2100-545 (Old CSI P/N 801288-07). This battery also has an outside Vendor source from Power-Sonic P/N - PCBM-3.6 Click here to view a PDF on this part. For battery testing process see How to test the NiCAD Battery on a Controller

Issue How to configure Custom 37-Bit as well as Infinity 37-Bit Card Format Product Line Access Expert Environment Access Expert Server 2012 and Above Version 2 Version 3 Hosted  Premise Cause When configuring Custom 37-Bit as well as Infinity 37-Bit Card Formats, the settings are different based on the Facility Code, Card Length and Card Formats. The HEX code generated in Live Monitoring can be deciphered to get the correct set of values required to make this work for your application. If you are unable to do so, please contact PSS and open a ticket so that they can help. Resolution The following settings on the screen shots show how to configure Custom, HID Formats and Infinity 37-Bit Formats, please pay attention to the one that will work for your specific application: Open and log on to the respective Access Expert Instance Select the tab Access Configuration to create a new Card Format Name the format accordingly in the description field, this can be used for Infinity 37-Bit if so desired Add the card range by clicking on the page Icon on the Number Range There is a Standard, HID Managed 37-Bit (not Infinity 37) in the drop down in the Card Format Presets This can be used by default but if you have a Custom 37-Bit Format and the Facility Code is known, however the Start Bit and Length will be different. An Infinity 3 Bit Format will use the Parity Bits Create the new format per the screen shots and configure accordingly. Once complete, click on Save or Save and Close, reboot the controller.

Issue “IP_ADD_MEMBERSHIP failed” appears in the Application Director output during reboot of the Jace and in the Station Discovery on the Niagara Network after a failed discovery attempt Product Line TAC IA Series Environment ENC 520, 410, Jace 6E, 645, 700, 8000 controllers using G3/AX. The second Ethernet interface only applies to the Jace 6E, 700, 645 and 8000 Cause Incorrect or no default gateway assigned in the TCP/IP Configuration or Interface 2 is enabled and set for DCHP with no DHCP server available to that interface. See the notes on the illustration for possible configuration faults. Resolution Make certain you have a valid IPV4 or IPV6 (schema dependent) Gateway entered for the Interface 1 IP configurations. If set to DHCP, ensure there is a DCHP server available on the interface. Disable all unused interfaces and IPV6 if not applicable. If there are problems accessing or configuring the interfaces, you may need to use the System Shell of the ENC/Jace and correct the configurations there. Need to correct invalid IP address or subnet mask entered into an ENC or JACE

Issue Changing the default port numbers for the Fox, Platform Daemon and HTTP ports in I/A Series G3 Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server / Enterprise Network Controller Cause There is a need to change the default port numbers of the Fox, Platform and HTTP ports used in I/A Series G3. Below are the descriptions of the ports usage and their default port numbers: TCP port 1911 (Fox port) Default port for a station's Fox Service used for Workbench to station and station to station communications TCP port 80 (HTTP port) Default port for a station's Web Service used in browser access (Hx, Wb) TCP port 80, 3011 (HTTP and Platform Daemon ports) Default ports for Workbench Platform connection Resolution The default ports for the Fox and HTTP ports can be changed during the process of creating a new station. Follow the following procedures if the ports need to be changed after the station has been created. To change the Fox port: In Workbench, open the station. Expand 'Config' > 'Drivers'. Open the Property Sheet of the NiagaraNetwork. Expand the 'Fox Service' and you can change the port number from the default of 1911. To change the HTTP: In Workbench, open the station. Expand 'Config' > 'Services'. Open the Property Sheet of the WebService and you can change the Http Port number from the default of 80. To change the Platform Daemon port: In Workbench, open the host's Platform. In the Platform view, go to the Platform Administration. In the Platform Administration view, click on the 'Change HTTP Port' button to change the default port.

Issue Is JSON supported in a web service environment? Product Line EcoStruxure Building Operation Environment Web Services JSON StruxureWare Building Operation Cause Many third party application only communicate JSON. Resolution JSON is not a supported format in StruxureWare Building Operation as an HTTP response in Generic Consume. Only Simple XML Web Service and SOAP Web Service are supported. It must be an XML document. There is a tool developed on the Community to automatically convert the JSON response from a Web Service to XML, and though it is not officially supported by PSS, it has proven to be a valid work around. Refer to SBO - Web Service through a Proxy, JSON and Image conversion.

Issue Building Operation Server backup set is incompatible for restore. "Importing Backup Set" "Backup set is of a different server type" Product Line EcoStruxure Building Operation Environment Automation server (AS) Enterprise server (ES)  Cause The backup set is for a different server type (version). Determine the server type from the .xbk file to determine which server version will allow a restore. Resolution The quickest method is to run the following tool SBO xbk Analyzer - Communities (se.com) and open the backup (xbk).  It will identify the  File name Controller Type Version / Serial Number Time and type of backup.  i.e., Contents. Config only, Events and Trends, etc. And much more.  See the link above or the Help topic on the tool for further information   Alternative methods are provided below:    The backup set contains information in the compressed .xbk file that can be retrieved this way ... Make a copy of the backup set as a precaution for safety reasons On the copy, for AS change the file extension from .xbk to .zip. For ES change to .tar Use a tool such as 7zip to decompress the file Look for a file by the name x.x.x.xxxx.serverrevision (i.e. 1.3.0.4602.serverrevision) This is the revision that the backup set was created at.    The Backup set can only be restored into a server running this revision.   Look for a file by the name xxxxxxxx-xxxxxx.backuptime This is the date/time when the backup set was created.   Look for a file by the name Automation/Enterprise.servertype This indicates whether the backup set is for AS or ES   Look for a file by the name xxxxxxxxxxxxx.servername This is the name of the server when the backup set was created     Version 1.5 and above There is a file by the name TDxxxxxxxxx.serverserialnr This is the Serial Number of the server.  

Issue When attempting to start the Enterprise Server, the user receives the following error message: "Windows could not start the Building Operation Enterprise Server service on Local Computer: Error 216: 0xd8" Product Line EcoStruxure Building Operation Environment Microsoft Windows Building Operation Enterprise Server Building Operation Enterprise Central Cause Windows error 216: 0xd8 means "The version of %1 is not compatible with the version you're running. Check your computer's system information to see whether you need an x86 (32-bit) or x64 (64-bit) version of the program, and then contact the software publisher." It is likely that this error is being received due to the EBO Enterprise Server/Central being installed on a 32-bit Windows Operating System. Resolution Beginning in EBO 2.0 it is no longer supported for the Enterprise Server to run on a 32-bit Operating System. Reference the Enterprise Server Specification Sheet for the appropriate product version you are using to find the list of supported Operating Systems. The Enterprise Server/Central should then be installed on one of the supported 64-bit Operating Systems.

Issue Having inconsistent results installing PCT on various host platforms. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause Having difficulty installing PCT successfully. Resolution PCT "Server Mode" installation Sign in and add the computer to the domain Download and install the PCT Server software with an Administrator account Select the “Server” Setup Type Select the hardware Ethernet Connection for the network adapter Allow the Virtual Box installer to complete Reboot the computer Disable Windows Firewall as needed, or add the required firewall rules to allow connections to the PCT If desired, download and install the EBO License Administrator, and any required versions of EBO Workstation and Server Packages (1.9, 2.x, 3.x). Individual User Laptop Setup Download and install the EBO License Administrator, and any required versions of EBO Workstation (1.9, 2.x, 3.x) Download and install the PCT Client software Individual User Laptop Usage Open the PCT client and connect to the desired PCT server Enter the IP address of the PCT server machine to connect once, or click the “Setup for use with remote server” link to adjust the properties of the PCT client to always connect to the same PCT server Once connected to the PCT server, install all the desired Server Packages for the first use Create a new project, or open an existing project If the project’s servers are not running, start them Once the required servers are running, open Workstation to develop the project   For the purpose of testing the procedures described above, following hardware was used.   OPTIPLEX 7060 Micro XCTO Intel vPro Technology Enabled Dell Data Protection Threat Defense Subscription, 3 Years US Order Standard BIOS - Fastboot - Auto Asset Report Thermal Pad 2 512GB PCIe NVMe Class 40 Solid State Drive 32GB 2X16GB DDR4 2666MHz Non-ECC Shipping Label for DAO Intel Core i7-8700 (6 Cores/12MB/12T/up to 4.6GHz/65W); supports Windows 10/Linux TPM Enabled CMS Software not included MOD,PLCMT,QSG,7060,MFF,DAO1 OS-Windows Media Not Included SW for 7060 with Win10 OS No Integrated Stand option OptiPlex 7060 Micro with 130W up to 87% efficient adapter No Wireless LAN Card No Anti-Virus Software Desktop MFF BTO Standard Shipment No Intel Responsive No Additional Hard Drive Intel Unite Software Not Included Safety/Environment and Regulatory Guide (English/French Multi-language) No Productivity Software No AutoPilot Win 10 Pro 64 English, French, Spanish Ship Material for OptiPlex Micro Form Factor 130W AC Adapter Regulatory LBL for 130W adapter (65W CPU Chassis) No CompuTrace No UPC Label US Power Cord 8th Gen Intel Core i7 vPro processor label No Option Included No FGA Energy Star Dell Developed Recovery Environment Waves Maxx Audio Dell Client System Update (Updates latest Dell Recommended BIOS, Drivers, Firmware and Apps) Dell(TM) Digital Delivery Cirrus Client SupportAssist Not selected in this configuration NO ADAPTER No Cove Black Dell MS116 Wired Mouse Black Dell KB216 Wired Multi-Media Keyboard English No PCIe add-in card 5 Screw for SSD/DDPE ProSupport for Dell Data Protection Threat Defense, 3 Years ProSupport Plus: 7x24 Technical Support, 3 Years ProSupport Plus: Next Business Day Onsite 3 Years ProSupport Plus: Keep Your Hard Drive, 3 Years ProSupport Plus: Accidental Damage Service, 3 Years Dell Limited Hardware Warranty Plus Service

Issue When logging into the web server of a Xenta controller using Mozilla Firefox 4 an error message is shown stating that the website is using an invalid security certificate.  When logging into Xenta server using Firefox 4 a certificate error is displayed as displayed below: The complete error screen reads as follows: This Connection is Untrusted You have asked Firefox to connect securely to 192.168.1.152, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site's identity can't be verified. What Should I Do? If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn't continue. Get me out of here! Technical Details (IP Address of Xenta) uses an invalid security certificate. The certificate is not trusted because it is self-signed. The certificate is only valid for (IP Address of Xenta) (Error code: sec_error_ca_cert_invalid) I Understand the Risks If you understand what's going on, you can tell Firefox to start trusting this site's identification. Even if you trust the site, this error could mean that someone is tampering with your connection. Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification. Add Exception... How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Mozilla Firefox 4 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Firefox 4) cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution There are two possible resolutions: Install the self-signed certificate using the following steps: Expand the "I Understand the Risks" bullet then click the "Add Exception" button. Firefox will automatically retrieve the certificate from the Xenta server. Make sure to check "Permanently store this exception" and then click "Confirm Security Exception" The certificate is now installed and the warning screen will no longer show up when logging into the server. It may be necessary to restart Firefox for the changes to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Firefox is uninstalled then reinstalled. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate. Purchase a certificate issued by a Certificate Authority (CA): These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. Please see TAC Xenta Server - TAC Networks - Technical Manual for more information. See "There is a problem with this website's security certificate." when logging in to Xenta web server using Internet Explorer 8 for information on installing certificates into Internet Explorer.

Issue Xenta OP menu items: Status, Sub menu, Week chart, Holiday chart, Alarm, Access Code, Edit Access Code, Date and Time, Daylight Saving have defined Access Levels: Low Level Medium Level High Level Accessing the medium or high-level menu items requires a password. What is the default password and how can they be changed? What if the passwords have been lost? Product Line TAC Vista Environment Menta Xenta Controllers Xenta OP Cause Accessing the medium or high-level menu items requires a password. Resolution The default password for accessing medium level menu items is: 1111 The default password for accessing high-level menu items is: 2222 These can be changed via the Xenta OP only provided the "Edit Access Code" menu item is present in the OP Tree. Downloading the controller may reset the access level passwords back to the default.

Issue The object information received from a MicroNet and IAC controller is based on a request for information from the Xenta. If the local area network receives too many requests, the system will not operate as quickly as expected. It is important to configure the objects with a realistic poll time to avoid issues with slow system response. Product Line Satchwell MicroNet Environment Xenta 500 Xenta 700 Satchwell MicroNet Cause Slow graphic, alarm, updates Resolution Updated June 2019 The MicroNet 50 series range MN350, 450, 550, 650 LCD and Touchscreen have been withdrawn from sale. The IAC 420, 600 and Touchscreen have now also been withdrawn from sale. No direct replacement is offered. Further information on these changes can be found in PA-00495 - Notice of Withdrawal - Satchwell Sigma and PA-00528 - End of Commercialization - Satchwell Sigma. ---------------------------------------------------------------------------------------------------------------------------------------------------------- Network Architecture The size of a MicroNet/Satchnet network within XBuilder is not limited. It is quite possible to have 80 Unifact Pro controllers directly connected on an NCP RS485 network; ARCNET and Satchnet networks with routers can be much larger than this. With such large networks, to achieve acceptable system performance, the number of signals requested and their poll rate must be considered when engineering the Xenta 555. Note that Satchnet networks run four times slower than MicroNet NCP networks. Bandwidth and Performance  Because both MicroNet and Satchnet networks are polled, there is a limited bandwidth available in which to obtain all signal data. This means that it is necessary for the Xenta 555 to request each programmed signal (point) in turn from each controller. There are many factors which deter-mine the performance of a network, however it is generally accepted that certain signal parameters should update more frequently than others. The Xenta 555 has a special dynamic poll scheme that is inherent in the controller and needs no configuration. The polling of any signal depends on the signal type and its poll frequency. Priority is given to signals with the fastest poll rate; therefore some mea-sure of control can be applied to the prioritization of signals. The most important signals should be configured with the fastest poll rate. In the event that a particular signal is referenced more than once, for example, in an alarm, log and web page, that signal appears in the poll scheme once only and is polled at the fastest rate (that is, the fastest of the alarm rate, log rate or web page rate). Typically, the order of engineering priority should be: 1 Alarms 2 Web pages 3 Logs Tip Connection objects should be kept to a minimum because each connection comprises a read signal and a write signal (that is, two operations). Performance example Consider a Xenta 555 ARCNET or NCP network with three web clients showing three web pages (two alarm pages and one values page with 50 signals). The Xenta 555 configuration comprises a total of 480 signals: . 100 alarm signals set with a scan time of four seconds. . 300 logs at a logging interval of one hour. . 30 connection objects at a period of 10 seconds. 50 point signals on a values page with a fixed refresh time of 10 seconds. In this network, the signals will arrive in the alarm pages typically within 60 seconds. Connection objects and signals in values pages will update within 60 seconds. The Xenta 555 polling algorithm computes the optimum poll rate for each signal, therefore if the sum of the poll frequencies exceeds the available bandwidth at any particular time, the lower frequency polls will be delayed. This has the effect of spreading the polls out over the available bandwidth and therefore optimizing performance. Signals on graphics pages and values pages are only polled when the page is being displayed in a web browser, however when a signal is required for logging, alarming or for a connection object, the signals are continuously polled at the configured poll time Web Page Updates Some examples of expected polling rates follow: - In addition to MicroNet network updates, web pages are updated at regularly intervals and this should be considered when analyzing the over-all performance; ten seconds should be considered typical for a web page update. However, polling performance is affected by the number of web clients and the number of web pages. If each web client simultaneously requests a different web page, each with a set of signals not currently being polled (for example, alarms), then the number of polled signals will increase substantially and therefore slow down the rate of web page updates. For this reason it is recommended that the number of web clients is restricted to three for a typical Xenta 555 network as described in the example given earlier. Due to a slightly enhanced Native Communications Protocol (NCP) and Attached Resource Computer Network (ARCnet)  employed by the 50 series controller a small difference between the 100 series and 50 series controller Packets/Min can be seen, these are indicated below. Xenta555 - MNMI NCP Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 526 Packets/Min MN650 567 Packets/Min Xenta555 - MNMI ARCnet Polling 50 Objects 10 Polls/Sec 426 to 595 Packets/Min MN620 484 Packets/Min MN650 495 Packets/Min Xenta555 - SNP 1200 Polling 50 Objects 2.5 Polls/Sec 169 to 174 Packets/Min Xenta555 - SNP 4800 Polling 50 Objects 7.5 Polls/Sec 398 Packets/Min These times are the averages found during testing, these figures will be affected by the following: - 1. The amount of controllers on the LAN (The Xenta 555/731 carries out some background polling an each controller for online and null output status). 2. The controller type has a small bearing on the polling rate per second. 3. Quality of the communications wiring.(poor wiring or incorrect cable specification can cause errors and re-tries) 4. Quality of the controller wiring, particularly with ARCnet installations. (Unscreened inputs ETC can result in noise reaching communications cable causing errors). 5. With the Xenta 731 particularly a high level of Menta programs ETC can cause time delays if the Xenta processor struggles to process all the information in good time. Further information can be found in the TAC Xenta 555 Supplement Manual.