Building Automation Knowledge Base

Issue After the successful installation of Continuum 1.9x, users are receiving a DCOM Permission error when logging on to Continuum webClient. The error is intermittent. Product Line Andover Continuum Environment Microsoft Server 2008 Standard Microsoft Windows 7 Continuum 1.9x and 2.0 Continuum webClient Server Remote Desktop Cause When a remote desktop connection is made on Windows 7 or Windows 2008 Server the console occasionally gets locked. It stays locked until the local session is restored with a logon. Resolution Create a .bat file. **************************************************************************************** @echo off REM Restores session 0 to the "console".  Thus allows local machine REM to return to the service accounts desktop without being locked. REM ------------------------------------------------------ tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 0 /dest:console @%windir%\System32\tscon.exe 1 /dest:console @%windir%\System32\tscon.exe 2 /dest:console **************************************************************************************** Place this file on the desktop of the Continuum webClient Server system. When you disconnect from the remote session run this Bat file. Do not just disconnect. This must be run "As an Administrator." This will disconnect the session and restore the console.

Issue Satchwell VZF 2-Port Flanged Valve Body requires replacement. Environment Satchwell 2-Port Plug and Seat Flanged Valve Body VZF1727                                VZF 1727 VZF1777                                VZF 1777 VZF1852                                VZF 1852 VZF1902                                VZF 1902 VZF1954                                VZF 1954 Cause Obsolescence of Satchwell VZF 2-Port Flanged Valve Body Resolution A number of alternative S-E 2-Port Flanged Valve Bodies are available to replace existing Satchwell VZF 2-Port Flanged Valve Bodies. Suggestion 1 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E VG221F 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L9TVG Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the VG221F 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. Suggestion 2 Replace Satchwell VZF 2-Port Flanged Valve Body with S-E V222 2-Port Flanged Valve Body of appropriate size N.B. Existing Satchwell Actuator installed on VZF 2-Port Flanged Valve Body may be retained for installation on replacement S-E 2-Port Flanged Valve Body.  In such instances a S-E L8TV Linkage Kit will additionally be required.  Alternatively an Actuator from the S-E range of Actuators may be installed on the V222 2-Port Flanged Valve Body, in which case no additional Linkage Kit will be required. IMPORTANT NOTE It should also be noted that the face to face dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2-port Flanged Valve Body  Similarly, the centre line to bottom of third port dimensions both of the S-E VG221F and V222 2-Port Flanged Valve Bodies differ to that of the Satchwell VZF 2port Flanged Valve Body  As a result alterations to the pipework connected to the VZF 2-port Flanged Valve Body will be required. Details of the Satchwell VZF 2-port Flanged Valve Body may be viewed here. Details of the S-E VG221F 2 port Flanged Valve Body may be viewed here. Details of the S-E V222 2-port Flanged Valve Body may be viewed here. Details of the S-E L9TVG Linkage Kit may be viewed here. Details of the S-E L8TV Linkage Kit may be viewed here.

Issue Do IP settings go to defaults when flashing from 4040 to 9640? Product Line Andover Continuum Environment bCX9640 bCX4040 Cause Have a need to flash a controller from bCX4040 to bCX9640 over a remote connection access. Do not want to have to go to the site to reset IP settings.  Resolution Using CyberStation v1.93 a bCX4040 was flashed to a bCX 9640 and it did NOT lose its IP info. Notes: At the end of the upgrade an error was received: “The uprev could not communicate with the specified controller”. From the webpage it was noted that the IP address had not changed and the upgrade was successful. It did not come back online in CyberStation. From the webpage, resetting it still did not bring it back online in CyberStation. Changing the model number in CyberStation to bCX9640 (from bCX4040) to bring it back online was not an option. The flash upgrade had reset the ACCNetID to 1. The 4040 was then deleted (Bacnet side first then Infinity side) and a new 9640 was created. The proper ACCNetID was set up in the webpage and the changes committed. It was then online in CyberStation. Bottom line – IP address never changed. ACCNetID did. The controller never had to be touched during this process so remotely doing this is expected to work. This was only tested using the latest firmware and CyberStation v1.93. Of course, the best way to do this is on the bench not on a live system. Please be aware that the model flash change will cause node count and/or xdriver upgrades to be reset if they were added as post-factory-shipment upgrades (via the Repair Dept) since these upgrade UPD files are model specific. See Node or XDriver Upgrade of BCX Inf (9640) to BCX BACnet (4040) or reverse. Also see Update b3 or i2 OS, changing (converting) a controller, BACnet to Infinet or Infinet to BACnet .

Issue Information for replacement for the SPA1505 and SPA1506 Product Line Field devices Environment Pressure sensors Cause "PA-00167 Sensors and Input Devices New SPP930 Relative Pressure Switch" suggests SPP930 replaces SPA 1505 and SPA 1506. The link provided for the SPP930’s manufacturer’s data sheet, no longer works Resolution SPP930 Part number 004701160 replaces the SPA 1505 SPP930 Part number 004701170 replaces the SPA 1506 The site wiring should be checked, to ensure it complies with replacement switches reduced current ratings.   SPA 1505/1506 data sheet Huba Controls type 620/625 data sheet.

Issue What are the replacement battery part numbers? Product Line Andover Continuum Environment Continuum and Infinity controllers i2, b3, CX, bCX1 SCX920, LCX810, LCX800, TCX850 Cause Replacement part numbers required. Resolution All the i2/b3 controller battery types are covered on pages 48/49 of the b3 Controller Technical Reference The CX9200, CX9400, and CX9900 all use 2 off: 12V 6.5A lead acid gel cells, Part number: 01-2100-423 The Part number for the bCX1 battery is: BCX1-BAT-KIT The Part number for the ACX57xx battery is: ACX2-BAT-KIT The Part number for the NC2 battery is: NC2-BAT-KIT For the older Infinity Controllers: SCX920, LCX810, LCX800, TCX850 – ½ AA 3.6V 850mA-Hr  e.g. LS14250

Issue Customer are running an ES with version 3.2.3 sending emails through SMTP server using TLS protocol. After site is upgraded to version 4.0.3, emails are not sent and the following error is shown in the ES: "SSL routines: tls_process server_certificate:certificate verify failed. Email service failed to connect to SMTP Server." In version 6.0.3, the following error is also displayed in the ES: "error:16000069:STORE routines::unregistered scheme" Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server version 4.0.1 and later Building Operation Automation Server Premium (AS-P) version 4.0.1 and later   Cause The following is stated in the EBO version 4.0.1 release notes: "Certificate validation for SMTP When choosing TLS as encryption method (i.e. encryption of all traffic) for SMTP, then the certificate will be validated from EBO 4.0. If a corresponding CA-certificate isn’t present in the server, then a system alarm is generated. See more in “CA Certificate Management” ( also in section 2.17.5) how to import CA Certificate." Resolution In EBO version 4.0.1 and later a valid certificate needs to be installed if alarms should be sent when using TLS protocol in the communication to the SMTP server.

Issue EcoStruxure Building Operation Automation Server, Enterprise Server and BACnet object names limitation Dragging converted I/NET TGML graphics into Workstation causes Workstation to crash with following message: Exception message: Object reference not set to an instance of an object. System.NullReferenceException: Object reference not set to an instance of an object. at SE.WorkStation.Base.Windows.Views.TgmlFileDropHandler.Drop(FileInfo, Path, IOperationContext, IProgressInfo) at SE.WorkStation.Base.Windows.Views.FileDropCoordinator.ExecuteDrop(Path, IList`1, IProgressInfo) at SE.WorkStation.Base.Windows.Views.<>c__DisplayClassd.b__9(IProgressInfo) at SE.WorkStation.Framework.Services.<>c__DisplayClass1.b__0(IProgressInfo) at SE.WorkStation.Framework.ProgressIndication.ProgressActionOperation`2.Run(IProgressOperationInternal, IProgressResult, IProgressOperationInfo) at SE.WorkStation.Framework.Services.ProgressItem`1.b__1a(Task) at System.Threading.Tasks.<>c__DisplayClasse`1.b__d() at System.Threading.Tasks.Task`1.InvokeFuture(Object) at System.Threading.Tasks.Task.InnerInvoke() at System.Threading.Tasks.Task.Execute()  Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The number of characters and the use of special characters in a EcoStruxure Building Operation object name and EcoStruxure Building Operation BACnet objects names Resolution Refer to the Webhelp Object Names topic for information on naming restrictions The statements in Webhelp also apply to EcoStruxure Building Operation BACnet objects unless is it a Continuum b3 object.  If you are creating a Continuum b3 object etc., the b3 object display name is limited to 16 characters consisting solely of letters, digits, and underscores (as per Continuum limitation). Basically, any objects you create for Continuum, for example, a 'BACnet Analog Input (Continuum)' will be subjected to the Continuum limitation. If you add a standard 'BACnet Analog Input' into an Automation Server or an Enterprise Server, then it is not limited by the Continuum limitation of 16 characters. The most common issue when bringing I/NET TGML converted graphics into Workstation is not checking for spaces at either the beginning or end of the converted file name.  Make sure there are no spaces (white space) before or after any characters of the file name before copying into Workstation.

Issue Where can I download the latest version of SigmaX? Product Line Other, Satchwell Sigma Environment SigmaX Cause Satchwell Sigma 4.07 release notes states that it is compatible with SigmaX version 7.0.4. On Extranet, 'Products' > 'Satchwell' > 'Sigma' > 'Downloads' > 'Utilities' only links to the download location for SigmaX 6.0.x. Resolution Sigma X version 7.0.9 is the latest version. You can download SigmaX version 7.0.9 from the Schneider download centre (1). (1) https://ecobuilding.schneider-electric.com/search#documentUUID/15c25fb4-fa6d-4cb1-8d04-3bea0a287526/SigmaX Version 7.0.9 - Support Tool This version does not require unlocking and corrects the following areas: - 1. Doctor error Doctor could incorrectly report an illegal point number value if a page reference value was over 9999. Error number 2122, 2. Doctor error Doctor could incorrectly report that page location in pointer.bin files greater than index.rex size. Error number 2152. 3. Doctor error. Doctor could incorrectly report index page segment incorrect for point mnemonic. Error number 2150. 4. Sigma View Site summary could miss valid look-up tables. 5. Sigma View Sigma view help text was not included in installer. Doctor can also ignore up to 5 specified errors if required. SigmaX supports all valid versions of Sigma from 4.05. Note: - SigmaX version 7.09 no longer needs a PCID to be unlocked. Due to this change SigmaX 7.09 no longer unlocks Sigma. To unlock Sigma, install the SBO license server/administrator, with a temporary license added, needs to be used. Click here to view the TPA-SACH-16-0012.00 which provides more information on the software licensing for Sigma. SBO license server/administrator SBO Temporary license

  Issue No more equation characters can be entered into a Function Block application Product Line EcoStruxure Buildings Operation Environment Buildings Operation WorkStation Buildings Operations Function Block Editor Cause You have exceeded the maximum number of characters allowed in a Function Block expression editor.   Resolution Expression text must have less than 500 characters. Split larger equations into two Function Blocks if needed. How to add an Expression Block  Expression Blocks 

Issue Displaying Automation Server status on a graphic page Product Line EcoStruxure Building Operation Environment Building Operation Workstation Building Operation Webstation Automation Server Cause The online / offline status of an Automation Server can be viewed in the Workstation System Tree (Servers folder). However, there is currently no 'built in' method of displaying the Automation Server status on a graphic page.  Resolution There are two possible ways to workaround this   Within TGML Bind any Automation Server attribute that is shown only when the Automation Server is online (such as DateTime) and convert the status either by TGML script or a ConvertStatus element. See the attached example.   Using a script program We can create a point in the Automation Server and use another server to monitor this point. Below is an example of using the Enterprise Server to monitor an Automation Server.  Create a value point in the Automation Server. In this example, I have created an Analog Value point and set it to a value of 88.8. This value does not really matter but I have set to this value for easier recognition. Create a value point in the Automation Server. In this example, I have created an Analog Value point and set it to a value of 88.8. This value does not really matter but I have set to this value for easier recognition 1. Create a value point in the Automation Server. In this example, an Analog Value point (named 'Status')is created and set to a value of 88.8. The value set does not matter. It has been set to 88.8 for easy recognition.    2. In the Enterprise Server, create a new Program point (named 'Monitor AS' in this example) with the following codes.  Numeric Input In1 String Output Out1 Numeric Output Out2 Out2 = In1 If In1.Offline = true then Out1 = "Offline" else Out1 = "Online"   3. Edit the binding of the Script program and bind 'In1' to the Value Point that was created in the Automation Server.    4. When the Automation Server loses connectivity to the Enterprise Server, the Out1 output of the Script program will show 'Offline'. You can then bind this to a graphic page.

Issue After moving the License server to another computer the license server address in the License Administrator is changed to the IP address of the new computer, but EBO Workstation gets a license error when trying to login to it. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause The License Administrator can be used to select which license server EBO uses. This is done by going to the License Server Address tab and entering the license server address in the License Server Address field. Note that the license server address must be preceded by an @ in order for it to work, e.g. @servab48. The License Server Address in The License Administrator is not always used when Workstation or the Enterprise server asks for a license, Resolution The request for a license is handled in the following order:   If there are licenses located locally on the machine running WorkStation/Enterprise server (activated from ASR files), those are used first. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is used. This registry key contains all license server addresses that have been successfully used to obtain a valid license previously. If this key is not empty, each server contained in the registry key value is asked for a valid license until one is obtained. This means that the license server set in License Administrator is not used in this case. If there are no licenses located locally on the machine running WorkStation/Enterprise Server, and the registry key HKEY_CURRENT_USER\Software\FLEXlm License Manager\TACLIC_LICENSE_FILE is empty, the license server set in License Administrator is used. The license server address is stored in the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Schneider Electric\StruxureWare\License Administrator\TACLIC_LICENSE_FI

Issue What is the Intel Floating point number as used in the Modbus X Driver? Product Line Andover Continuum Environment Modbus RTU X Driver Cause It is not clear how the two special floating point function codes vary. Resolution There are two different floating point data formats (248 & 245) these are both standard 32 bit floating point numbers but the data bits stored in memory (or read over the protocol) differently.   The 32 bits of Function 248 are stored as one string of bits, bit 0 through to bit 31.   For the 245 format the upper and lower words are swapped around, so it stores the data as bits 15 to 0, then bits 31 to bit 16. This format is called Intel format as it is the way Intel microprocessors handle floating point data.   Here is a link to information on floating point numbers FYI: https://en.wikipedia.org/wiki/Floating-point_arithmetic   These two formats can also be called Big Endian (Function 248), or Little Endian (Function 245). Little Endian is also known as the Intel format. Information on Endianness can be found at: https://en.wikipedia.org/wiki/Endianness

Issue If more than 3 Operators are created in Security Expert, the License page of the Thick Client will show more Licenses in use than the maximum three (3) clients provided with the standard SX-SRVR License. To see what the site is using, select About > License and scroll down to the Feature: Web Operators. As shown below, there are four web operators active out of the three (4/3) allowed. Product Line EcoStruxure Security Expert Environment Licensing Cause A Web Operator is defined as any Operator who can log onto the Security Expert Server using a browser.                           In the example shown below there are four Operators: admin 2nd Operator 3rd Operator 4th Operator The system allows each to log in successfully: The License option SX-WEB-OPR enables 'x' number of browser connections depending on customer needs and should effectively ensure that the correct number of Operators are purchased. However, the feature is currently in development and is not yet enforcing limits on the number of web operator connections.  This allows the number of connections to exceed the maximum limit (I.e.4/3) for the time being. Resolution Note: The Operator does NOT even need to be logged on for the count to register 4/3, the fact that 4 operators have been created is enough. The restriction of operators via Web Client could be enabled/enforced at any time in the next release of the software, so it is strongly advised to purchase the correct number of Licenses required at the time of installation, to prevent a loss of user connectivity going forward.

Issue Point under the Application folder of MP-x device shows error "Contains unresolved BACnet reference" Product Line EcoStruxure Building Operation Environment Building Operation Multi-purpose Controller Building Operation Multi-purpose VAV Building Operation IP-IO Cause Incomplete entry in point's BACnet priority array. The screenshot below shows the XML file obtained from exporting the point, as it can be seen, 'Priority16' is missing the 'Type' section. Resolution Perform the following steps to correct the problem: Export the point out to a file. Delete the point. Import the file created at step 1, once the point has been re-created via import the unresolved error is gone. NOTE: There is no need to make any modifications to the XML file, it can be imported as is, the system will automatically correct the incomplete entry for priority16.

Issue What is the unit load of a TC300 thermostat and what are the bias and termination requirements when used with a SmartX Server. Product Line EcoStruxure Building Operation, Field Devices Environment TC303-3A2LM TC303-3A4LM TC303-3A2DLMS TC303-3A4DLMS SmartX Server Cause Documentation does not state the RS-485 transceiver type for the TC300 range, making it unclear how many devices can exist under a SmartX servers RS-485 serial port ComA or ComB. Resolution The answers to the transceiver interface attributes below can be applied with to the Worksheet for Configuration of RS-485 Bus with generic RS-485 devices on Webhelp Q1 Failsafe Receiver The TC300 does not use an RS-485 transceiver with an integrated idle-state failsafe receiver. Q2 Data Transmission Speed TC300 thermostats manufactured from November 2018 onward can be configured to communicate at 9600 or 4800 bps. TC-300 thermostats manufactured before this date can only communicate at 4800 bps. Q4 Isolated Interface The TC300 does not provide an isolated RS-485 interface. Q6a Measured Resistance With no electrical connections to the TC300, the measured resistance between the RS-485 low-side (-) signal and the communications common is 10K ohms. Based on this the unit load of the TC300 is 1.2 (12.000/10,000) Bias requirements and number of devices If the length of the RS-485 bus is less than 150M (500ft) then Generic RS-485 Device Configuration 3 from Webhelp can be applied. Using this configuration the recommended 3300 bias resistors present a unit load of 3.6 (12,000 / 3,300). The SmartX server adds 0.5UL. The remaining node budget is calculated as: 32 - 3.6 - 0.5 = 27.9UL. Since the TC300 has a unit load of 1.2 the maximum number of devices that can be placed under each comm port using this configuration is 27.9 / 1.2 = 23.25 If the length of the RS-485 bus is greater than 150M (500ft) then Generic RS-485 Device Configuration 7 from Webhelp can be applied. Using this configuration the dual end-point bias configuration presents a unit load of 24UL (12,000 / (1,000 / 2) = 24). The SmartX server adds 0.5UL. The remaining node budget is calculated as: 32 - 24 - 0.5 = 7.5UL. Since the TC300 has a unit load of 1.2 the maximum number of devices that can be placed under each comm port using this configuration is 7.5 / 1.2 = 6.25 Also check out the SmartStruxure-RS485-Controller Unit Load Quick-Help video on the Exchange.  h

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 Services for assistance. Issue After successfully setting up KIOSK mode to automatically login in to WebStation another user wants to login through WebStation on the same PC. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation WebStation Cause The GUEST account login URL used with KIOSK mode retains the last user logged in and the WebStation menu bars have been removed so that user cannot "logout". Any subsequent attempts to access the WebStation using the same browser result in being automatically logged in under the GUEST account. Resolution The "KIOSK" link that you create will login automatically with the GUEST account as long as the GUEST account has already been created in the ES/AS. This then must set the "last credentials" in IE for that website and any subsequent connections to that server, even to the direct login URL, result in automatically being logged in with those last credentials. One of the two options below should work to disable GUEST login depending on where your ES is located. Enterprise Server on another computer or accessing an Automation Server Disconnect the Ethernet cable for the computer or disable the network port while Building Operation Workstation attempts to login returning user to the login prompt. Enterprise Server on same computer The Enterprise Server can be stopped temporarily and the next attempt to start Building Operation Workstation will result in a communication failure allowing you to modify the "Remember me on this computer" selection. To be prompted for a login: Disconnect the ES/AS with one of the options above. Then try to connect to the server page at "http:/localhost:444" (or your specific URL:Port). This results in a "this page can't be displayed" (or similar) message. Then start the service, or reconnect cable, and again attempt to connect to "http:/localhost:444". You should be presented with the login page. Do not try to open up the "KIOSK" URL or else this will again login with the GUEST account and you'll be back to square one. The next time you use the "KIOSK" URL it will automatically login with the GUEST account and this will again be used for subsequent logins until the above steps are repeated. Note1: This could result in loss of data while the Enterprise Server is stopped. Note2: Also see StruxureWare Building Operation Workstation Auto Login feature locked if encountering this issue with a Workstation.

Issue What binding methods can be used and how is the data transferred when binding objects between two b3  or Infinet controllers? Product Line EcoStruxure Building Operation Environment Automation Server, AS, ASP, ASB BACnet b3 Infinet controllers i2 Cause When binding objects between b3(infinet) devices/controllers, the type of Objects being bound will effect the properties of the binding. Resolution When binding between two Controllers, several methods can be used: Value/Point to Value/Point - The data goes via the Automation Server and the speed/rate is set in the Transfer Window, thus more bandwidth used and communication is lost if the Automation Server fails. Script to Value/Point - The data goes direct using BACnet COV subscriptions, thus less bandwidth is used. NOTE - The BACnet b3 and Infinet controllers, have no facility for direct binding of Value/Point to Value/Point, thus if a direct binding is made within the same controller, an EBO binding will be created. This will cause data packets on the MSTP or Infinet network. This should usually be avoided, as it can easily overwhelm the network. Bindings should usually be made from scripts. See Infinet under the hood for more details on Infinet setup

Issue DC1100 / DC1400 Displays two horizontal black lines when powered up. Product Line Field Device Environment DC1100 / DC1400 Discrete Controller. Cause Cold Start has not been performed. Cold Start has been performed incorrectly. Mains borne corruption has affected processor. Resolution Carry out Cold Start: Isolate Controller power supply. Press and hold down "Enter" and "Exit" buttons. Keep "Enter" and " Exit" buttons depressed while restoring power. Display should show "Self Test" and "Initiating System Variables" Release "Enter" and "Exit" buttons. Controller may then be programmed in accordance with Data Sheet instructions.   Or, if the controller is non-recoverable, the DC1100 and DC1400 units are now obsolete. However, there are several 3rd party companies offering refurbished units, these can be found by using a browser and searching e.g. DC1100 repairs.    

Issue Spare Satchwell valve gland kit & grease, reconditioned 'O' rings and lug nuts options. Satchwell packing kits, Satchwell gland kits, Satchwell stuffing glands. Product Line Field Devices Environment Satchwell valve Gland kits Packing kits Stuffing Gland Part Numbers: 0617-9-410, 0617-9-411, 0617-9-412, 0617-9-413 0618-9-210, 0618-9-510, 0618-9-511, 0618-9-512 0623-9-201 0626-9-203, 0626-9-204, 0626-9-310, 0626-9-311, 0626-9-312, 0626-9-313 0667-9-201 Cause Spare item part numbers Resolution   Valve(size) Part No Description Stock 1/2"…..1" 0626-9-313 LUG NUT AVAILABLE   0626-9-312 LUG NUT AVAILABLE   0617-9-410 RECON KIT "O" RINGS & TOOL AVAILABLE MB 1 1/4" 0617-9-411   AVAILABLE MB 1 1/2" 0617-9-412   TOOL AVAILABLE MB 2" 0617-9-413   AVAILABLE MBF 65mm 0618-9-510   AVAILABLE MBF 80mm 0618-9-511   AVAILABLE MBF 100mm 0618-9-512 RECON KIT "O" RINGS AVAILABLE MEU, FEU & VEU 0623-9-201 REPLACEMENT GLAND KIT & GREASE OBSOLETE MJF 0626-9-203 REPLACEMENT GLAND KIT & GREASE AVAILABLE MZ 1"..2" series 3       VJF       VSF 15..25mm       VZ 0.5" .. 2" series 1 & 2               MZX 0.5" .. 2" 0626-9-204 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZX 0.5" .. 2"               MZ 0.5" .. 2" series 1 0626-9-310 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZ 1" .. 2" series 1               MZF 65 .. 150mm 0626-9-311 REPLACEMENT GLAND KIT & GREASE AVAILABLE VZF 65 .. 150mm series 1               VSF 32 .. 50mm 0667-9-201 REPLACEMENT GLAND KIT & GREASE AVAILABLE VV 0618-9-210 RECONDITIONING KIT AVAILABLE Download the drawing for the MB 0617-9-410 (0.5" to 1") Download the drawing for the MBF 0618-9-511 (80mm) Download the drawing for the MZX 0626-9-204 Download the drawing for the VZ/MZ 0626-9-310

Issue There is no indication that a card has been read when being presented at a Security Expert Smart Card Reader. Product Line EcoStruxure Security Expert Environment Security Expert Security Expert Smart Card Reader (SX-DRD-??, SX-DRK-??, SX-RD-??, SX-RK-??) Cause Reader is configured but there is no LED activity or beep when a card is presented at the reader. Resolution If the Security Expert Smart Card Reader does not blink or beep, then the reader cannot read the card for one of the following reasons. Wrong technology, e.g. trying to read a 125khz card on a 13.56mhz reader will not work and vice versa The card is encoded with a proprietary format/encryption The card is encrypted and the encryption keys are not programmed into the reader (note that this is different from the above case; there are many scenarios where cards are encrypted but not proprietary and therefore if the encryption keys are programmed into the reader it can be read) If you get a single beep/short flash of the reader ports reader LED but no event/data in Security Expert it means that the reader can read the card but the format at the reader port is not able to correctly interpret the data which is why no events are being logged. Another format should be selected from the Reader Format list to suit the card type, if no suitable format exists in the list a custom format must be created.