Issue Configuration of multiple BACnet BBMD's over several subnets Product Line Andover Continuum, EcoStruxure Building Operation Environment Bacnet BBMD Cause Bacnet Broadcast communication through IP router Resolution Configuration of multiple BBMD's over several subnets: INCORRECT METHOD For example if there are 4 subnets on the same B/IP (BACnet IP Network): Subnet 1: Workstation setup as a BBMD with an entry in the Broadcast Distribution Table for each BCX Subnet 2: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 3: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. Subnet 4: BCX setup as a BBMD with an entry in the Broadcast Distribution Table for itself and the Workstations BBMD Only. The BCX's do not reference any points from each other. Since there is no data sharing between the BBMD's, one might think that in each BCX's Broadcast Distribution Table that there would only be a need to add one entry for the Workstations BBMD. Sounds like with this setup we'll reduce traffic by only adding the one entry in each BCX's BBMD Broadcast Distribution Table. The above scenario could in fact slow down a network and cause unnecessary traffic.   The supported method is that every BBMD on a B/IP network have the same routing tables(better known as the Broadcast Distribution Table) as in the below configuration. CORRECT METHOD For example there are 4 subnets on the same B/IP (BACnet IP Network). Subnet 1: WS BBMD with an entry in the Broadcast Distribution Table for itself and all BCX's setup as BBMD on the same B/IP. Subnet 2: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 3: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. Subnet 4: BBMD with an entry for all BBMD's(including self) in the Broadcast Distribution Table on the same B/IP. The entry below can be found in the BACnet Standards 2004:   J.4.3 BBMD Concept Each IP subnet that is part of a B/IP network comprised of two or more subnets shall have one, and only one, BBMD. Each BBMD shall possess a table called a Broadcast Distribution Table (BDT) which shall be the same in every BBMD in a given B/IP network.

Issue PCT does not run properly following installation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) 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. Cause Certain environmental settings may need to be adjusted in order to successfully install PCT. These settings are not described in the Project Configuration Reference Guide. Resolution If you have issues successfully running PCT after installation, check the following items: Enable Virtual Hardware Acceleration in BIOS Use this tool to check if virtual hardware acceleration is already enabled on your PC: Intel: https://www-ssl.intel.com/content/www/us/en/support/processors/processor-utilities-and-programs/intel-processor-identification-utility.html AMD: https://support.amd.com/en-us/search/utilities?k=virtualization Disable all Ethernet Adapters except the one in use (Only applies to Server Mode): It may be necessary to check Windows Device Manager for hidden network adapters Disable the Windows firewall Disable Anti-Virus Software A true local account may be needed to install and/or run PCT due to Group Policy or other factors. Use Run as Administrator for both installing and running PCT Note: You can right-click the PCT icon, open properties, select the “Compatibility” tab, and check the box “Run this program as an administrator” Test PCT by opening up the software application, creating a project, creating a server, and opening it up in WorkStation If PCT opens and works then enable Windows firewall and Anti-Virus program. - User may need to allow PCT in Windows firewall and PCT utilize port 9091 as default. - User may need to add exceptions within Anti-Virus software settings. We recommend installing Microsoft Fix 50410 to prefer IPv4 over IPv6. This software can be found here: - https://support.microsoft.com/en-us/kb/929852 - Choose the following download: Prefer IPv4 over IPv6 in prefix policies.

Issue How to filter in a listview AlarmEvent based on the EventNotification Environment Continuum Cause Continuum pre 1.91 did not allow filter in a listview AlarmEvent, based on the EventNotification Resolution See Continuum CyberStation Release Notes Version 1.91(Downloadable here) Fixed Problems 4.007 Cannot filter an AlarmEvent table based on the EventNotification using the query wizard (21101) Find another way to filter or upgrade your version of Continuum.

Issue After 2000 backups an attempt to perform a backup to flash results in the error 'Flash backup for this controller has been disabled.' Product Line EcoStruxure Building Operation, Andover Continuum Environment b3 controller i2 controller Cause Flash memory has a limited write count; Controllers implement a flash circuit breaker that trips after 2000 backup operations in order to protect the flash device from damage. Resolution (Applies to all b3 and i2 controllers) EcoStruxure Building Operation In EBO, a command has been added that will re-enable backup to flash after the circuit breaker has been tripped (2000 backups) From Workstation, in the object tree, right-click the i2/b3 device. From the context menu select, DEVICE->ENABLE BACKUP TO FLASH     Andover Continuum From CyberStation command line set the ACCStatusBackup system variable of the device to ACCBackupEnable. NOTE: The flash circuit breaker CANNOT be reset from Script/Plain English.  This is by design as it was deemed too risky to allow resetting it programmatically.  A poorly written program could very quickly cause damage to the flash device.

Issue Current transducers require an additional external resistor fitting to a Universal input to read the current flow, what resistor and input point settings are required? Product Line Andover Continuum Environment All controller with Universal Inputs (both 5V and 10V). 4-20 mA Cause There is a requirement to define the resistor value to be connected across the input, also the settings for the upper and lower voltage in the input point configuration. Resolution Download the attached Current Inputs.PDF file, although this was originally written for Infinity controllers it is fully applicable for i2 and b3 controllers. Controllers like the i2/b3920, i2/b3810 have 10V inputs other i2/b3 controllers have 5.12V inputs, check the product datasheet specification if you are unsure. The file details the value of the resistor to use in the circuit and the upper and lower voltage settings to enter in the Auto Conversion box in the input point, these will correspond to the sensor reading at 0mA and 20mA, or 4mA and 20mA depending on your sensor output. For controllers that allow the pull up resistor to be switched out, ensure that it is in circuit for these setting to work correctly. The UI-8-10-10V I/O Modules should be set to 0-5V input with the reference resistor On, then setup as per all other 5.12V input controllers. Note: The part numbers listed for the resistors are no longer available through Order Entry and should be sourced from your local stockist. Link to file: Current Input ISM.pdf   Suitable component resistors: For 10V inputs: RS 165-472 For 5V inputs: RS 165-185 0

Issue Includes PSI Error Messages and Device Error Messages Environment PSI Microzone II Network 8000 Cause Quick reference Resolution The error codes are listed in the PSI MicroZone II Operator's Manual.  The full document is available here:  F-23058. Just the error codes are available here:  Pages 59-61.

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 Unable to discover BACnet devices from a BACnet interface, discover broadcast address and/or devices are offline after changing IP Address on AS or ES. Bacnet devices are offline after a power cycle or loss of IP connection at the AS or ES. Product Line EcoStruxure Building Operation Environment StruxureWare Building Operations site using devices configured with BACnet Cause Broadcasting on wrong network from either the Automation Server or the Enterprise Server can be a problem. In the example below an AS is broadcasting for a BACnet device (in this case a MNB Controller). In the IP Network for the BACnet Interface, check your settings for Broadcast Address. The key is to ensure your BACnet broadcast address is in the correct range.   In this first screen capture, we have a BACnet network interface using the IP Network with a red failure to communicate indicator on the MNB. In this example, the broadcast is on 192.168.1.255 Resolution The computer being used as well as the BACnet devices we want to discover and use are in the following IP network and settings: Changing the broadcast address to match what the BACnet network is using resolves the issue (BBMD and BBDT from Enterprise Server or Automation Server). Lastly, choose to discover devices For subnet calculations and how to setup your subnet addresses, several recommended calculator are SuperNet Online or SubnetMask a downloadable program from Solar Winds.  When the IP Network broadcast address is set incorrectly, a Wireshark capture may reveal that no WHO-IS message is sent out from the SmartStruxure server when a device discovery is attempted. When in doubt as to whether the 'IP Broadcast Address' is correct, a simple test is to set the IP Broadcast address to 255.255.255.255, doing so will instruct the SmartStruxure server to broadcast on ALL subnets, if the problem was caused by an incorrect broadcast address it will be resolved but care must be taken not to leave the default address set to 255.255.255.255 as this will cause unnecessary traffic on all sub-nets, instead, review your calculations for what the appropriate broadcast address should be and set it appropriately. Key Concept: The AS will retain the Broadcast address, and if moved to a new Subnet, the old Broadcast address must be updated. One can do either of the following:  Edit the IP Broadcast Address Setting  Delete the BACnet Interface and recreate in the new Subnet

Issue Scheduled event reports exported to PDF are using the US date time format not the local systems date time format. Report settings   In the below example the Windows system, and Security Expert, were both setup for Australia regional settings with a date format of dd/mm/yyyy. The automatic scheduled reports exported to PDF were showing the US date format mm/dd/yyyy. Report export before   Product Line EcoStruxure Security Expert Environment Security Expert event reports Cause The local Windows system date settings for Welcome screen and New user accounts are incorrect. Resolution In Windows navigate to Control Panel\Region Click on Change date, time, or number formats. A new window (Region) will pop up. Click the Administrative tab Click Copy settings... Enable the following options if not enabled already. Under Copy your current settings to tick Welcome screen and system accounts and New user accounts as shown in the image below. This will copy the Current users format over to the Welcome screen and New user accounts sections. Date format settings After making the above changes the PDF reports generated now show the correct date format of dd/mm/yyyy. Report export after

Issue The Xenta 7xx from factory it has the default IP address 192.168.255.2, which also is stated in the manual. But when you run the “format” command on a Xenta 7XX, you will get IP address 172.22.1.5. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 527 NPR, 555, 701, 711, 721, 731, 901, 911, 913 Cause The format command will wipe all memory from the Xenta Server. Its IP address will need to be reset, system program will need to be reloaded, and XBuilder project will need to be redownloaded. Resolution The Xenta from factory has the default IP address 192.168.255.2 subnet mask 255.255.255.0 After the “format” command it will have IP address 172.22.1.5 subnet mask 255.255.255.0 See IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for instructions on setting the IP address to the desired address.

Issue There is no complete end-to-end guide on how to test SNMP alarms in EcoStruxure Building Operation (EBO). Existing documentation only covers creating SNMP alarms, not validating their functionality. Product Line EcoStruxure Building Operation Environment SNMP Notifications Cause Documentation provides steps for creating SNMP alarms but lacks instructions for testing and verifying alarm notifications. For general information regarding SNMP traps, refer to the following Web Help links: SNMP Notification Distribution Method Create Notification Wizard - Configure SNMP Page Resolution Follow these steps to test SNMP alarms in EBO: Install MIB Browser Download and install MIB Browser from iReasoning. Load Building Operation MIB File Download the Building Operation MIB file. In MIB Browser, go to File → Load MIBs, and select the Building Operation MIB file. Create and Trigger an Alarm in EBO Configure a simple alarm on a digital point in EBO. Ensure the alarm can be triggered manually for testing. Configure SNMP Notification in EBO Create an SNMP notification with the following settings: Address: SNMP manager IP (use localhost if manager is local). User Name: SNMP manager user credentials. In Filter Settings, select Normal and Alarm states. Add condition: Source server = * . Important: Open the SNMP notification object (double-click or press Enter) to access filter settings. Viewing properties alone will not display filters. Enable Trap Receiver in MIB Browser Navigate to Tools → Trap Receiver in MIB Browser. Trigger the Alarm Activate the alarm in EBO. Verify that the SNMP trap appears in the MIB Browser’s Trap Receiver window.

Issue The following Popup window is displayed when attempting to open WorkPlace Tech. WPTech Unable to load WorkPlace Tech Ribbon for Visio. There was a problem loading the WorkPlace Tech Fluent Ribbon for Visio, therefore, it will be unavailable. Product Line TAC IA Series Environment Visio 2010, 2013, 2016, and 2019 WorkPlace Tech Tool release 5.8 or later Cause If Visio crashes when a third-party ribbon bar function is in use, Visio may lockout that ribbon bar, believing that something on that ribbon bar caused Visio to crash.  In this case, a menu function, selected from the WorkPlace Tech (WPT) ribbon bar was being processed at the time Visio crashed, therefore Visio locked out the WorkPlace Tech ribbon bar. This is a system protection mechanism built into the ribbon bar handler in all Microsoft Office applications including Visio.   Resolution To re-enable the WorkPlace Tech ribbon bar, perform the following steps: Open Visio.  NOTE: Open Visio, not WorkPlace Tech. Select Options from the File menu. From the menu in the Visio Options window, select Add-ins At the bottom of the window, you will see a field that says 'Manage:' with a selection box after it, select 'Disabled Items' and then click the [Go] button. In the 'Disabled Items' window, select 'WorkPlaceTech.VisioRibbon' then click the [Enable] button. Close the open Visio windows and sub-windows. After closing Visio, the WorkPlace Tech ribbon bar will be available in WorkPlace Tech.  

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 Using access card types not natively supported by Continuum system Product Line Andover Continuum Environment CyberStation CX9900/9940 CX9702 CX9680 ACX5740/5720 ACX701 ACX781 Cause Continuum has built in support for the most widely used Wiegand card types, occasionally a site might be using a card type for which Continuum has not built in support. In such cases the system must be configured using custom card functionality. Resolution Setting Up a Custom Wiegand Format A custom format must be used when the card format is not one of the standard pre-defined formats. Only one custom format can be used in an ACX7xx controller and NC1(CX99xx), NC2(CX968x) using AC1 modules, up to four custom formats can be used with the ACX57xx and NC1/NC2 using AC1Plus modules. In each ACX700 and ACX780/781, NC1, NC2, ACX57xx create an InfinityNumeric point called AccessFormat (use this spelling exactly!). During the creation process, attach a manual array (log) with 22 entries to the point. If using more than one custom card definitions create InfinityNumeric points called AccessFormat2, AccessFormat3 and AccessFormat4 Create the following InfinityProgram in each controller. The program should be type FallThru, and AutoStart. This program basically saves you from having to set each array value individually for each controller. The program, once created, can be copied to all other access controllers that need it. In the following example the AccessFormat array is setup to allow the system to read the HID Corporate 1000, 35 bit card. Program Name: SetCustCrdArray FlowType: FallThru AutoStart: True Code: Set AccessFormat[1] to 35 ‘overall number of bits Set AccessFormat[2] to 0 ‘control mask Set AccessFormat[3] to 0 ‘ manufacturer’s code Set AccessFormat[4] to 0 ‘ start bit of man. Code (first bit is 0, not 1) Set AccessFormat[5] to 0 ‘ end bit of man. code Set AccessFormat[6] to 2 ‘ start bit of site code (NOTE: If the card has no site code set this field to 0) Set AccessFormat[7] to 13 ‘ end bit of site code (NOTE: If the card has no site code set this field to 0) Set AccessFormat[8] to 14 ‘ start bit of card number Set AccessFormat[9] to 33 ‘ end bit of card number Set AccessFormat[10] to 0 ‘ odd parity mask, first 16 bits Set AccessFormat[11] to 0 ‘ odd parity, next 16 Set AccessFormat[12] to 0 ‘ odd parity, next 16 Set AccessFormat[13] to 0 ‘ odd parity, next 16 Set AccessFormat[14] to 0 ‘ even parity, first 16 Set AccessFormat[15] to 0 ‘ even parity, next 16 Set AccessFormat[16] to 0 ‘ even parity, next 16 Set AccessFormat[17] to 0 ‘ even parity, next 16 Set AccessFormat[18] to 0 ‘ card number multiplier Set AccessFormat[19] to 0 ‘ card number divisor Set AccessFormat[20] to 0 ‘ start bit of issue code Set AccessFormat[21] to 0 ‘ end bit of issue code Set AccessFormat[22] to 0 ‘ decimal shift of issue code​   In each Door Configuration, select the Custom Wiegand card type. Other card types may also be selected. For each Personnel, select the Custom Wiegand card type, and enter the correct card number and site code. If the card is not working, check the Event Log and determine the cause. For Invalid Card Parity errors, set all the parity masks to 0 and try again. For proximity cards, the parity check may be eliminated with little consequence. NOTE: In controllers that support the HID Corporate 1000, 35 bit card natively (NC2 – CX968x and ACX2 – ACX57xx) the AccessFormat numeric is internally used by the system, any other custom card definitions must use AccessFormat2 – AccessFormat4 Control mask Some Wiegand cards are encoded with the bits in one or more fields reversed and/or complemented. It is then necessary to operate on the fields when decoding the data in order to obtain the correct data. In the AccessFormat array a control field is provided to configure the system so that the bits in a field in the access card data can be reversed and/or complemented. The control mask is located at AccessFormat[2] Control Mask The bits of the control mask are used by the parsing routine in the controller to reverse or complement selected fields. Setting the appropriate bit to a 1 will enable the special action: Example: To reverse the bits in the site code field set AccessFormat[2] = 8 Parity mask calculation The table below shows the card format information provided by the manufacturer of a 32 bit Wiegand card. From the information provided by the manufacturer we can deduct the flowing about the format of the data on the card: The card data is comprised of the following 3 fields A = Customer Code B = Facility Code C = Card Number Bits 0 through 16 make up the even parity field. (The ‘X’ indicates that the bit is part of the even parity field) Bits 15 through 31 make up the odd parity field. Note the overlap in the fields (bits 15 and 16 are members of both the even and odd parity fields), this is common as the fields are arbitrarily assigned by the card manufacturers. Armed with the information provided by the manufactures we can calculate the parity mask which Continuum will need to use in order to perform the necessary parity check upon receipt of the card data transmitted by the card reader. First, calculate the EVEN parity mask. To better illustrate how the calculation is done we have added a new row to our table, in this row we are going to enter the even parity mask as a binary number. What we do is write a 1 (one) in each bit that is a member of the even parity field and a 0 (zero) for bits that are not part of the even parity field. The second step is to divide the bits that make up the field into groups of 4 which will make it easier to convert the binary number in the previous row to a hexadecimal number. The even parity mask for this card is 0xFFFF8000 It should now be obvious how Continuum uses the mask when checking for even parity. Upon receipt of the card data transmitted from the reader, Continuum applies the mask to the full 32 bit stream of data received, (a logical AND operation is performed) the mask acts like a filer that allows only the set bits in the even parity field to pass through, now all Continuum has to do is count the bits that passed through the filter and make sure the count is an even number, if the count is not an even number Continuum sends a parity error. The Odd parity mask is calculated using the same procedure. Here is an example for the calculation of the parity masks for a 35 bit card A = Company ID Code B = Card Number P= EVEN PARITY Even Parity Mask 0x76DB (30427) 0x6DB6 (28086) 0xC000 (49152) 0x0000 (0) P = ODD PARITY Odd Parity Mask 0x6DB6 (28086) 0xDB6D (56173) 0xA000 (40960) 0x0000 (0) After calculating the parity masks you enter the decimal numbers into the appropriate fields in the AccessFormat array. S = Site Code C = Card Number P= EVEN PARITY Even Parity Mask 0xFFFF (65535) 0XE000 (57344) 0x0000 (0) 0x0000 (0) P = ODD PARITY Odd Parity Mask 0xFFFF (65535) 0xFFFF (65535) 0xF000 (61440) 0x0000 (0) IMPORTANT: If a custom card is configured with a bit count that is the same as the bit count of one of the cards that are supported natively, the parity masks MUST be entered in the AccessFormat array in order for the controller to be able to parse the custom card correctly, if not parity masks information is entered, the controller will generate an 'Invalid attempt, bad parity' event when the custom card is presented at the reader.

Issue The Sigma Compact Edition previously supported specific Windows CE-based hand-held devices, including: iPAQ 114 iPAQ 214 iPAQ 2490b Dell Axim X51 These devices are now obsolete and no longer available in the market. Product Line Satchwell BAS & Sigma Environment Sigma Compact Edition Sigma WinCE Cause The rapid evolution of the PDA market has led to frequent discontinuation of supported devices. This created ongoing compatibility challenges and limited long-term support options. Resolution To address this issue and improve future compatibility, Sigma 4.05 Compact Edition shifted its support strategy. While no new hand-held devices are supported in this release, users can now utilize more widely available and sustainable alternatives such as: Mini PCs Netbooks Notebooks These devices offer greater flexibility, availability, and longevity compared to legacy PDAs. Resources Release Note – Sigma Compact Edition 4.05 User Guide – Sigma Compact Edition 4.05

Issue The ServerPack installation process does fail to complete on a new PCT installation PCT presents the following error. : 'beee::vm_module::VirtualBox::make_disk_multiattach' due to: 'VBoxManage.exe: error: Cannot change the type of medium 'C:\ProgramData\Schneider Electric EcoStruxure\Building Operation\Project Configuration Tool\external\VM\docker.vmdk' because it is attached to 1 virtual machines VBoxManage.exe: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), component MediumWrap, interface IMedium, callee IUnknown Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The VBoxHardening.Log (\\Users\John Boehmer\VirtualBox VMs\NoteTEst\Logs) is flagging dll flags that are incorrectly signed. supR3HardenedScreenImage/Imports: cache hit (VINF_SUCCESS) on \Device\HarddiskVolume3\Program Files\Oracle\VirtualBox\Qt5CoreVBox.dll [lacks WinVerifyTrust] If an attempt is made to create a virtual instance in VBox the machine fails to run with the following error. Resolution Uninstall all non-essential software applications from the host machine.  In this case, PCT was being installed on a brand new Hewlett Packard PC that had a variety of HP security software.  In some cases, other non-essential applications may need to be uninstalled as well. Once the software was uninstalled PCT was reinstalled over the top of the existing installation. Virtual machines created in VBox could then be started and PCT began to function normally.

Issue Wiring a MD10B-24 / MD20B-24 actuator to a Climatronic CXT / CXR / CSC Actuator Environment MD10B-24 MD20B-24 Actuator Climatronic CXT CXR CSC Cause The Climatronic controller switches the O volt side of the 24 volt supply, but the actuators shows that it requires 24 volts to open and close. Resolution The Satchwell range of Climatronic controllers have always switched the 0 volt side of the 24 volt supply to control the actuator position. CXT Controller - Terminals 13 and 14 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CXR Controller - Terminals 23 and 24 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. CSC Controller - Terminals 33 and 32 provide 0 volts to close or open the actuator. A permanent 24 volts is provided by terminal 37. For the complete datasheet, please click HERE. The MD10B-24 / MD20B-24 datasheet shows the wiring as follows; For the complete MD10B datasheet, please click HERE. For the complete MD20B datasheet, please click HERE. The above actuator wiring shows a 0 volt connection to the common connection (1) and a switched 24 volt connection (2 or 3). To connect the MD10B-24 / MD20B-24 actuator to any of the above controllers it will be necessary to connect the actuator as follows. Controller 24 volt  (37) to connection wire (1). Controller Open signal (14, 24 and 32) to connection wire (2). Controller Close signal (13, 23 and 33) to connection wire (3). Please note that the actuator direction can be changed by repositioning the switch on the front of the actuator.

Issue How to discover MNL Lon devices or other Lon devices in an SmartStruxure Automation Server. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Automation Server Cause Use the below instructions when you need to find all Lon devices on a Lon network. Resolution To discover a LonWorks device In WorkStation, in the System Tree pane, select the server that is connected to the device you want to discover. Click the Device Discovery view. In the Select device type box, select LonWorks. Select the Devices folder. Right click on the Devices folder and take "Scan network for devices" In the Device Discovery view, ensure that the LonWorks device is displayed in the Devices folder. This may take up to 5 seconds. Drag the discovered device to the System Tree pane: Drag to an existing device to associate it with the discovered physical device. Drag to the LonWorks network to create the device.   NOTE: You cannot drag a standard MNL LonWorks device to the System Tree pane if the discovered device is in an unconfigured state For more information, refer to the Creating and Configuring a LonWorks Network with MNL LonWorks Devices [102423].pdf document 

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 Can I take a 26 bit Wiegand Hexadecimal Card Number format and find out what the Facility Code and Card Number are? Product Line TAC INET Environment 26 bit Wiegand Hexadecimal Card Cause Need to discover the Facility Code and Card Numbers Resolution Yes you can do this. This document will show you the process on how to determine these values: 26 Bit Wiegand Format Also see Conversion from I/NET hexadecimal code to Continuum Facility/Card Number for an Excel utility to perform this conversion.