Building Automation Knowledge Base

Issue Customers wanting to use a Barcode Reader for door access Environment Access Control site wanting to use Barcode Readers Cause Barcode Readers often are a higher  Resolution I/NET The SCU is the best you could have so that makes it easier with memory requirements and so forth. Since you have the SCU, set it up for 26-bit Wiegand (2 parity bits and 24 data bits). It would look like this: e eeeeeeee eeeeooooooooooooo o That is a 1-bit starting bit, even parity, 8-bit facility code, site number, card number, 16-bit segment, and the 1-bit ending parity (26 bits all together). That is how many data bits the reader normally takes. 26-bit Wiegand is typical and most common. The true bits are the facility code, site and card number. The beginning and end is the parity. For more information, see TCON300, beginning on page 9-59. This is the key card translations section, and may be valuable in figuring out the solution to the bar code reader. Lastly, one idea is to contact a company called RFIDeas.com. They make a bar code reader that may be a solution. If the bar code reader is outputting a card number larger than 16 digits, convert it to 26-bits of Wiegand data (it can handle up to 64-bitWiegand). If it goes over 64-bit, they have a special firmware which allows up to 254 bits of wiegand data. With the SCU, the 26-bit is the standard. Code 128 is used to barcode INET products. The Cypressworld CVX-1300 is an alternate solution for connection between the I/NET SCU and the Barcode Reader. Continuum Code 39 is used to barcode the serial number on Continuum and Pelco boards.  Most readers can auto switch between these and other code types.  

Issue When editing a personnel object an error is received "Input string was not in a correct format" using 1.82 or 1.90. Environment Webclient Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008 Cause Microsoft released .Net 2.0 SP2 which caused an issue with our code in the personnel area. Resolution The version of Continuum you are using will determine the solution you need to use. 1.82 - Uninstall .net 2.0 SP2 1.90- Install the following hotfix  Click here to download The issue was corrected in 1.91.

Issue Are any of the Schneider Electric access software products FIPS compliant? Environment FIPS compliant access control Cause New U.S. Government access control regulations. Resolution FIPS Compliance information The Federal Information Processing Standard 140-1 (FIPS 140-1) and its successor FIPS 140-2 are United States Government standards that provide a benchmark for implementing cryptographic software. They specify best practices for implementing crypto algorithms, handling key material and data buffers, and working with the operating system. Both IPSec and the Encrypting Files System (EFS) in Windows 2000, Windows Server 2003 and Windows XP use the FIPS-140-1 evaluated Kernel Mode Cryptographic Module to encrypt the traffic packet data and file contents respectively if configured appropriately with the selections of FIPS compliant algorithms. The FIPS-compliant, kernel-mode, crypto module lets organizations deploy FIPS 140-1-compliant, Internet Protocol Security (IPSec) implementations using: L2TP (Layer Two Tunneling Protocol)/IPSec VPN client and server. L2TP/IPSec tunnels for gateway-to-gateway VPN connections. IPSec tunnels for gateway-to-gateway VPN connections. IPSec-encrypted, end-to-end, network traffic between client and server, and server to server. Currently, I/NET Seven is not FIPS Compliant. There are not any plans to make I/NET Seven FIPS Compliant. The Continuum product line is FIPS Compliant. Click here for a PDF with more information. FIPS 140-2 Validation Certificate http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140crt/140crt1355.pdf Schneider Electric Continuum Network Security Module http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140sp/140sp1355.pdf

Issue Why are many BACnet controllers sending out Who-Is requests for a Cyberstation that is Offline and been removed from the Database? Environment Continuum BACnet Cause Even though the Cyberstation Device object has been removed from the database, there are probably still references to it in the various controllers in the field. If this Cyberstation was the recipient of BACnet alarms from these controllers then they may still have its Device ID as a delivery recipient and send out the Who-Is packets to locate this device.   Resolution There are a couple things that can be done to fix this problem, basically the reference to this device needs to be removed from every controller. Make sure to perform a global teach, this should fix up most of the routing tables. The next thing to do is to reload any and all affected controllers. (You can use Wireshark to determine which controller are sending the who is requests, see details below.)   In the attached packet capture here, you'll find details of the Who-Is packet and the NPDU layer that show the details that you will be looking for to identify the source of the packet. A filter of "bacapp && (bacapp.unconfirmed_service == 😎 && (bacapp.who_is.low_limit == 199)" was used in this example to focus on the Who-Is packets being directed to device 199.

Issue Personnel Manager lacks Access Event built in report like Personnel Editor, this article outlines a procedure for adding similar functionality to the Personnel Manager via a list view that can be invoked from a Personnel Manager's application button. Environment CyberStation Cause Add Access Event report functionality to Personnel Manager. Resolution Click here for a pdf document that outlines the procedure.

Issue An error has occurred, please try the operation again later when opening a Digital Sentry video layout on a browser PC using Webclient 1.91 Environment Digital Sentry 4.3 or 7.x Webclient 1.91 Windows XP Windows Vista Windows Server 2003 Cause There are 2 updated hotfix files necessary for video display in a browser with 1.91. Resolution Click the link below and follow the instructions for installing the DSConneX_VideoPatch contained in the file Click here to download the file

Issue Distinguishing whether an xDriver-enabled commport on a controller is set for Modbus RTU or Modbus TCP/IP. Environment CX9900, CX9940 CX9680 bCX4040 Cause How does one know if the xDriver-enabled commport on a controller is for Modbus RTU or Modbus TCP/IP? Resolution Open the controller editor and go to the Options tab. At a minimum the Modbus RTU XDriver, like all Xdrivers, requires Bit 0 for the commport be Xdriver enabled. The most common example would look like this: Xdrvr Commx: 00000001(####). In the above example x = commport number. The four digit number in parentheses indicates whether an Xdriver file is loaded into the port. If it is 0000 then no Xdriver file is loaded into the port. A number such as 4767 corresponds to "Xdriver Valid" line at the end xdriver XDR file. You can edit the XDR file with a text editor and go to the bottom to see this.   In addition to Bit 0 being enabled for the commport, the Modbus TCP/IP Xdriver requires Bit 3 to be Xdriver enabled.  A common example of this would look like this: Xdrvr Commx: 00000009(####). The 00000009 is in hexadecimal format -  converting this to an 8-bit binary number you get 00001001. The furthest right bit is Bit 0 and the 4th from the right is Bit 3. Both are set to 1 which means they are Xdriver enabled. For a further explanation see page 15 of the linked Modbus TCP/IP Xdriver User Guide.   Note: Since Bit 0 is enabled in both of the above examples, the Modbus RTU Xdriver will work on either. But only the second example will load the Modbus TCP/IP Xdriver.      

Issue What sensors can be used in Clean Rooms  What sensors can be used outdoors for temperature measurement What sensor can be used in a swimming pool What sensor would be explosive proof What color is the wall sensor and are custom colors available Environment Building Automation System such as I/NET, Vista, or Continuum at a site containing a clean room, swimming pool, or outdoors Cause Questions concerning the uses of Schneider Electric sensors in Clean Room applications Questions concerning temperature sensors for Outdoor installations Questions concerning temperature sensors for swimming pools Questions concerning explosion proof sensors* Questions concerning color and custom colors for sensors Resolution All the Schneider Electric temperature sensors found in the HVAC Sensor Catalogue as well as on iPortal provide high accuracy and can be mounted on the wall, in ducts, or in a J-Box. Appendix A provides the accuracy for each of the temperature sensors. Color: STR series wall sensors are: Front Cover: White NCS S-0500 N Core Plate: White NCS S-0500 N and Gray NCS S-2500 N Base Plate: Gray NCS S 1502-R Manufacturing in custom colors in not available. One option could possibly to have the sensors locally custom finished to meet customer's requirements. While there is not a direct cross reference to RAL colors, our engineering team has found the closest alternates. Please see the attached pdf. Clean Room: Depending on the specified limits of the clean room, the variety of sensors offered by Schneider Electric are possible solutions. Thing you may want to research are the standards required for the site. Clean rooms are a controlled environment where products are manufactured. It is a room in which the concentration of airborne particles is controlled to specified limits. Eliminating sub-micron airborne contamination is really a process of control. These contaminants are generated by people, process, facilities and equipment and must be continually removed from the air. The level to which these particles need to be removed depends upon the standards required. The most frequently used standard is the ISO 14644 Standards, which were first formed from the US Federal Standard 209E Airborne Particulate Cleanliness Classes in Cleanrooms and Clean Zones.  ISO 14644 is a document that establishes standard classes of air cleanliness for airborne particulate levels in cleanrooms and clean zones. Strict rules and procedures are followed to prevent contamination of the manufactured product. The only way to control contamination is to control the total environment. Air flow rates and direction, pressurization, temperature, humidity and specialized filtration all need to be tightly controlled. Outdoor:  Schneider Electrics selection of Outdoor Temperature Sensors are the STO100, 200, 500, & 600. These outdoor sensors are intended for outdoor wall mounting. Variants are available for Vista, I/NET, Continuum and Satchwell systems. The body has a 20mm conduit entry and the product is supplied with a conduit gland. Range -40 to +90 °C Accuracy See Appendix A: Table A, C, F in the attached HVAC Sensor Catalog.pdf Outdoor Temperature Sensor STO100 Order Code 5141100010 Part Number STO100 System Vista, Xenta Outdoor Temperature Sensor STO200 Order Code 5123246000 Part Number STO200 System I/NET Outdoor Temperature Sensor STO500 Order Code 5141104010 Part Number STO500 System Continuum Outdoor Temperature Sensor STO600 Order Code 5126060000 Part Number STO600 System Satchwell Outdoor Temperature Sensor STO600D Order Code 5126000000 Part Number STO600D System Drayton Outdoor Temperature Transmitters STO300 The STO300 transmitter is supplied as a complete unit, comprising a sensing element and an amplifier mounted in a housing which is resistant to ultraviolet light. The transmitter is intended for mounting on an outside wall, on the north side where possible. The transmitter is connected over a 2-wire cable, which serves both as power supply and signal transmission. The reading of the measured signal is made over an external load resistance. Outdoor Temperature Sensor STO300 -50/50 Order Code 006920501 Part Number STO300 -50/50 System All Note for each of these outdoor sensors, find the Description, the Order Code, Part Number, and the System it works with for the iBAS (intelligent Building Automation System) Please note the difference in Weatherproof and Outdoor. I put a lot of these outdoor sensors in at a university in Texas, and always installed in places that were a little protected. I found that under porches, up under the eves and out of the sun, or along a loading dock out of the rain and ice gave me accurate readings. Swimming Pool: In the piping system of a swimming pool is a corrosive environment with steadily harmful and gradually destructive minerals and chlorine in the water which present a challenge finding sensors able to withstand for extended periods of time. Schneider Electric makes several immersion temperature sensors. Beginning on page 12 of the above HVAC Catalogue, there is a variety of immersion sensors for the different iBMS lines.  One example is the STP660 is a Temperature Sensor for the European market, and intended for immersion mounting in pipe or the circulating systems. The stainless steel probe is a good solution but remember,  if the sensor is to be installed in pool water that contains chlorine, the best bet is to use a stainless steel pocket. I suppose it all depends on if sensor is in pipe associated with the secondary pool side of the system or the heating side of the system. If the sensor head is in an area exposed to Chlorine, then there may be an issue.  Chlorine may attack the solder connections of the wired joints inside the sensor. In the old days products from Satchwell used to produce special sensors for such applications where the wire connections were varnished in order to prevent corrosion. I think at the end of the day, our sensor would have a similar life expectancy to other devices in the plant that were no designed for use in such corrosive atmospheres. Explosion proof sensors: Schneider Electric does not manufacture explosion proof sensors. We do not partner with another manufacturer who provides such sensors. The closest is an 3rd party explosion proof enclosure with one of our available sensors. Our sensors are designed for building installations and if in extreme environments, we suggest enclosures.  

Issue The FDA requires Building Automation systems to meet their standards which are outlined in Chapter 21 CFR and FDA Part 11. Environment Vista I/NET Andover Continuum TAC I/A-series Satchwell Sigma Cause Finding documentation on Schneider Electric Building Automation Systems which comply to The Food and Drug Administration rules. Resolution Vista 21CFRPart11 support in TAC Vista 5.pdf FL-VISTA-REGIND-A4 mod RO.pdf I/NET - currently unavailable Andover Continuum With the addition of the 21 CFR Part 11 compliance pack, Continuum can meets these requirements. Satchwell Sigma SoftwareOverview.pdf Advanced Security Module.pdf Note: Validation to 21CFR Part 11 can only be performed on whole operational systems and as such, a sub-system comprising the Satchwell Sigma building management system cannot be validated in it own right. Satchwell Sigma would normally be validated as part of a whole operational system. TAC I/A Series - currently unavailable

Issue How to reset an NC2 9680 model controller Environment CX 9680, NCII, NC2 Cause While upgrading/downgrading the controller firmware, communications was lost and the controller was not able to communicate afterwards.   Resolution Reset controller and re-commission. Please click here for document on how to reset the CX9680 controller.

Issue What transport type should be used when setting up an ACX57xx, CX9702, or bCX9640? (UDP TCP Netcontroller) Environment ACX5720 ACX5740 CX9702 bCX9640 Cause What transport type should be used when setting up an ACX57xx, CX9702, or bCX9640? Resolution The definition on the transport type settings from our Technical Reference Guide states that: UDP - This controller will communicate with other controllers and Workstations primarily using the UDP protocol. TCP - This controller will communicate with other controllers and Workstations primarily using the TCP protocol. TCP/UDP - This controller will communicate with other controllers and Workstations primarily using the TCP protocol, but can also speak to controllers and Workstations that communicate primarily using the UDP protocol.   You can set the controller to use either or both transport types for communication with other devices depending on your specific network requirements. UDP is the preferred option for Continuum devices. See the Andover Continuum Network Ports document for details on what specific ports are required. Three things you need to be aware of with this: Make sure that both the transport setting in the device object and the controllers IE configuration webpage are the same. No matter what transport type you choose make sure that any network firewalls are setup to allow packets through on those ports. View this document for some reasons to use Continuum's reliability layer over UDP rather than TCP.

Issue IOU Modules power requirement Environment CX9900 CX9940 CX9980 ACC LON IOU Modules Cause Limit on AC power supply capacity. Resolution See "Maximum number of I/O modules' in the I-O System Reference Guide document.

Issue What is the maximum MSTP cable length without a repeater? Environment Bacnet BCX B3 MSTP Cause Controller was not responding as online. Resolution Below is a document that explains the Maximum Cable Length for MSTP communications without a repeater. Click HERE for document.

Issue What are the steps to reload a controller Environment CX controllers BCX controllers ACX controllers NCII NC2 CX9680 I2 controllers B3 controllers Cause Point or program not available, receiving 5121 error Resolution To reload a controller follow the steps below: In continuum explorer select Options/Send to controller options and either the middle choice or bottom choice depending how which and how many controllers to be reloaded The most common and the default is to set to the middle setting to reload only the controller selected. Now select the controller to reload and right click and select send to controller The distribution located in the icon tray can be launched from a double-click to watch the progress of the reload.

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 Are examples available to show how to write Plain English programs and create points for a Modbus RTU X Driver linked to Schneider Electric Power meters? Environment Modbus RTU X Driver Schneider Electric PM700, PM750 Power meters. Cause Requirement for some examples to see how Modbus RTU programs can be written to poll for the data in a 3rd party Modbus device. Resolution The attached example was written by an application engineer in the UK to extract data from the Schneider Electric PM700 and PM750 meters. This example provides the mapping of data for these 2 specific meters, but the polling principle utilized in the Plain English programming can be applied to any Modbus RTU interface Download file here. 

Issue The purpose of this verification checklist is to provide documentation to the Project Manager that the Site Engineer has confirmed the Continuum Security configuration. Basic Settings Access Events Reporting Alarm Event Notification and Alarm Enrollments Door Alarms Other Alarms Time Sync Video including Pelco Digital Sentry IP Camera System Administrative Tasks Other Tasks Basic Checklist Access Events Reporting Checklist Alarm Event Notification and Alarm Enrollments Checklist Door Alarm Checklist Other Alarm Checklist Time Sync Checklist Video Checklist Administrative Tasks Checklist Other Tasks Checklist Environment Continuum with Security enabled Pelco Digital Sentry IP Camera System Cause Beneficial checklist for Verification of security site settings. Resolution Please find the attached pdf document which will walk you through the Continuum Security Checklist. The first section provides step by step instructions for novice users. The second section is the actual checklist where each task should be initialed by the Site Engineer, and the whole document signed by the Site Engineer and the Project Manager. To print the Checklist section of this procedure, start printing on page 21 of the attached checklist. Please find the attached pdf document which will guide you through a Pelco Digital Sentry IP Camera System Quick-Setup

Issue Using the selection tool to select the correct meter. Environment Heat Meters Cooling Meters Cause Selecting the incorrect meter can lead to loss of water flow and increased system pressure. Resolution Selecting an appropriate Heat Meter can be achieved using the selection tool. To view or download the tool click here. For the Product Announcement click here. To view the Online version of the tool please click here. The selection of a Heat Meter requires the following information; 1 - The maximum water flow through the system. 2 - The location of the meter, (Flow or Return). 3 - The size of pipe work where Heat Meter is to be installed. 4 - The media type, heating, cooling or both. 5 - Using the selection tool is made easier by using the Auto filter drop down selection arrows. These allow you to filter the selection on a particular area, i.e. "Flow Rate" as shown below. The Heat Meter part number is established as follows; 1 - Digits 1,2 - Heating, Cooling or Combined. 2 - Digits 3,4 - Flow rate. 3 - Digits 5,6 - Body length and connections. 4 - Digit 7 - Threaded/Flanged. 5 - Digit 8 - Heat Meter location Flow / Return. 6 - Digit 9 - Communications type. 7 - Digit 10 - Display option. 8 Digits 11,12,13 - Revision. To view a warning about the under sizing of Heat Meters, please click here. New serial communication modules are now available for Modbus RTU and BACnet MS/TP interfaces.

Issue Netcontroller power supply is not working as expected. Environment NC1 NC2 CX9900 CX9680 PS120 UPS Cause Problems with Netcontroller power supply. Resolution UPS not working Replace failed 5 Amp pico fuse (located on PC board adjacent to the UPS cable connector) UPS cable or connector has failed or is defective. Insufficient UPS battery capacity is attached to the UPS connector.  UPS requires two 12 VDC batteries). UPS Batteries are not sufficiently charged or have failed. No Power to NetController 3 Amp Slow-Blow fuse has failed.  (located on PC board adjacent to 120 volt power connector). Power switch is shut off. Insufficient supply voltage. General Mode switch is in the wrong position (See manual) Click here to download the PS manual

Issue How is Continuum configured to validate FIPS 201 PIV card credentials? Environment CyberStation CX9680 ACX5740 ACX5720 Cause Questions on how to configure a Continuum physical access control system to validate FIPS 201 PIV credentials at the door. Resolution Configuring Continuum for FIPS PIV card credentials Click here for instructions on creating a custom FIPS-PIV card format Versions needed for FIPS-201