Building Automation Knowledge Base

Issue How to use the Continuum Report object Product Line Andover Continuum Environment CyberStation Cause Instructions are needed to use the Continuum report object Resolution CyberStation provides a graphical suite of features, called Reports, that allows you to gather, view, compare, and distribute point-object data values, locally or remotely, manually or automatically, from virtually anywhere in your Continuum system.  Using CyberStation Reports, you may collect and filter data from a multiple number of dynamic building-control data sources (including extended logs) then instantly display this data in graphical bar charts, pie charts, trend charts, or columned text charts. With reports, you can: • Display report data using one of several data formats • Display two or more reports simultaneously • Modify report configurations on the fly while viewing them • Schedule reports to run automatically at a specified time • Save a report to a file, manually and/or automatically • Email a report, manually and/or automatically • Print a report   Basic Report Example   1. Create a Report  In Continuum Explorer, right-click on a folder or device, and select New, then Report, from the popup menu.     Type in a Report name and Select the Create button   2. Source Page a. Select a Data Source from the drop-down (Tables from the database)  b. Select a Report Type - these change based on the data source c. Select a Chart Type   3. Configure Columns Click on the Configure Columns button in the middle of the Source Page   a. Select the Columns needed in the report b. Use the drop-down to select how the report will be sorted   4. Filter Tab From the Source Page, select the Filter Tab a. The Log Filter and Time Interval options allow for Time filtering b. Member Objects - Click Add to specify which Fileds/Attributes will be included on the report   5. Output Tab From the Source page select the Output Tab The settings on the Output Tab will reflect how the report appears and how it is to be viewed   For detailed instructions for standard(Not Add-On) Continuum reports, see Chapter 14 Reports in the Continuum Configuration Training Manual. This manual is not available online, it is distributed as part of the Continuum training courses.

Issue Enhanced and Standard Alarm Delivery Explained Product Line Andover Continuum Environment Cyberstation Cause Information on the difference between Enhanced Alarm Delivery and Standard Alarm Delivery feature. Resolution Standard Alarm Delivery:   Prior to Continuum 1.7, alarms were delivered from the controller to each workstation on the network as long as a  Cyberstation is online (from the controller's perspective) AND if the Cyberstation is a recipient of the alarm or not.   The first workstation which receives the alarm logs it to the SQL database. The alarm is broadcast and if for some reason it doesn't get logged there is no guarantee it will be delivered to any Cyberstastion. It gets broadcast once.   Enhanced Alarm Delivery: The alarm engine was changed so that alarms could be delivered to Workstations that were temporarily offline. To accomplish this Continuum implemented Microsoft Message Queuing (MSMQ).   The controllers generate alarms based on criteria set up in alarm enrollments. These are logged in the database by the first workstation that receives the alarm which then hands it off to MSMQ for delivery to all workstations in the recipient list. The controller still sends the alarms to all online workstations. If a workstation is offline, alarms are stored in an outgoing MSMQ queue that will be delivered once the Cyberstation is back online.   Acc.App.AlarmServer.exe (Alarm Delivery Server) is the process that handles alarms and hands them off to MSMQ which is handled by the Windows Message Queuing service.   To view MSMQ queues, go to [Windows Control Panel>Security Settings]> Administrative Tools> Computer Management> Services and Applications> Message Queuing   Enabling Enhanced Alarm Delivery when upgrading or with a new install This is accomplished by leaving the default checkbox for Enhanced Alarm Delivery selected in the database initialization step on a new install or when upgrading to a version greater than 1.7x. MSMQ will then be installed as part of the Cyberstation installation or upgrade.   Note: If the Enhanced Alarm Logging checkbox is not checked initially, the Enhanced Alarm Delivery checkbox may become unselectable. See Installing Continuum Database for the First Time on a Multi-User LAN System in the Installation Guide   Enabling enhanced alarm delivery in a system that doesn’t have the checkbox selectable 1. Manually Install MSMQ Start> Run> type cmd then click OK (to open a command prompt) At the DOS prompt type cd\ then enter (places the cursor at the root) cd \program files\continuum\install then enter Type cscript MSMQInstall.js then enter (Windows component wizard Installs MSMQ) When the script is finished, one of the lines will indicate that MSMQ started successfully Type exit 2. Updating the database Note: Ensure you have a recent database backup before the next step Run Database Initialization Select Server if LAN or Stand Alone accordingly Select Enhanced Alarm Delivery checkbox Select update existing database and then click continue Restart all Cyberstations (If ALL aren't restarted, the system can still be in mixed mode)   3. LAN installation  Manually install MSMQ on each Cyberstation according to the instructions above (step 1). MSMQ will now be used for guaranteed alarm delivery.     Caution: Make sure that all Cyberststations in the database are restarted after Enhanced Alarm Delivery was selected and the DB Update performed!    Not restarting a Cyberstation puts the system at risk of using workstations with both types of alarm delivery (PSS may refer to this as MIXED MODE).   If all but one of the Cyberstations gets restarted and a Continuum User changes the alarm delivery mode and then a Cyberstation gets restarted later, the system  will be in mixed mode.   Uninstalling MSMQ Uninstalling MSMQ on a workstation (if needed at some point) Go to Control Panel> Add/Remove Windows Components> Deselect Message Queuing Say Yes to the warning message Reboot Also, check the following: Add a column to the alarm list view check the loggingWSId and see if the alarms are being delivered to another workstation that is no longer used. If it is no longer needed delete that Workstation which should correct this issue.

Issue Setting up camera motion detected or camera image lost camera events to trigger an Output or Output Group. Product Line EcoStruxure Security Expert Environment Security Expert Video Integration Cause Through various Video Integrations, Security Expert is able to use camera events (such as camera motion detected) to popup a camera window when those events are seen. However, camera events are not associated with an Input or Door and therefore Security Expert is not able to trigger Outputs or Output Groups directly from these camera events.  Resolution Camera events are not able to be used to trigger Outputs or Output Groups in Security Expert. If this is a requirement, contact local solution category management to have this setup as a new feature. 

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. Issue Operator password for SP-C-WEB has been lost and unable to login to the controller. Product Line EcoStruxure Security Expert Environment SP-C-WEB Cause The SP-C-WEB operator passwords are unable to be recovered. Resolution Default the controller using the jumper to bridge reader port 2 [1] Figure 1. Connecting Wire Link Once the controller is back online set the default admin password. Then restore a previous backup of the sites database containing the site configuration Figure 2. Restoring Database Backup  When the backup is restored the operators are not overwritten so the one you just setup during the commissioning can be used to login to the SP-C-WEB.   [1] SP-C-WEB Security Purpose Web Enabled Controller Installation Manual

Issue Can the damper feedback function be calculated using Plain English based on the drive time of the damper? Product Line Andover Continuum Environment Continuum i2866-V Controller Continuum b3866-V Controller Cause For this controller application, information about the vav damper position is required.   Resolution Only the i2866-v and the b3866-v provide integrated damper feedback.    When using other controller models such as the i2865 or the b3865, an approximation of the damper position can be calculated by adding the damper pulse value to the drive time.   Whenever the damper output is driven to the closed position, a pulse equal to the full damper drive time should be sent to the output and the damper position is reset to 0%.   Whenever the damper output is driven to the fully open position, a pulse equal to the full damper drive time is sent to the output and the damper position is reset to 100%.   Because this method of calculating the position of the damper is only an approximation, it should not be used for critical applications. 

Issue Content Types are not working correctly. A Content Type that was just created appears under the ES but not under the AS in which it was created in. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Building Operation Automation Server Premium Building Operation Software 1.9 or greater Cause Problems with or changes to the network configuration are affecting both the function and the lead shadow relationship of Content Types. Resolution   The following video will help us, Understand the Lead/Shadow aspects of Content Types Diagnosis and correct possible issues regarding the Lead/Shadow Online help topic for further information is also available here: Content Types (se.com)  

Issue How to perform the activation of an embedded demo license Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Cause The embedded demo License is a temporary license used for demonstration purposes, training, site engineering, when waiting on a permanent license order, or license support. This license file has a .Bin extension and can be downloaded from the EcoStruxure Exchange (ecoxpert.se.com) and is valid for a limited time (3 months). Resolution This video will demonstrate where to download, and how to activate an embedded demo license on an Automation Server using the Device Administrator.

Issue MQTT data points are no longer published to MQTT broker with "MQTT - Buffer overflow" alarm. System alarm: Buffer overflow - Not all MQTT messages have been sent Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause Long MQTT queue can be caused by, too many variables define in MQTT data groups, fast publishing, i.e. low interval or low delta value, Low CPU and RAM resources, or slow network. Resolution Once MQTT Buffer overflow alarm is generated, the below configuration shall be checked: Data points interval value, if the interval is enabled, make sure it is not a very low interval. Data points delta value, for event driven, make it is not very low value, especially for fast changing variables. Review the network performance. Make sure that the EBO server has sufficient CPU and RAM resources, and check Architectural guidelines for the effect of the Number of MQTT Data Points on the CPU Load. For Automation Server, the system memory usage should never exceed 80% and CPU usage should stay below 60%.

Issue There is no fully detailed explanation of how to install an SSL Certificate from an External CA Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Cause When trying to install an SSL certificate from an external CA can fail Resolution Configure a DNS name for the AS/ES (This prevents the certificate from being locked down to a specific IP. I.E. Configure an A record for "AS_Name".com Purchase SSL Cert through a 3rd party, or use your organization's internal CA/ root CA Download and install OpenSSL or can use OpenSSL installed with EBO  Run Command Prompt as an administrator Use command "cd c:\program files\OpenSSL-Win64\bin Use OpenSSL to generate a CSR in order to obtain the certificate from the 3rd party openssl req -new -newkey rsa:2048 -nodes -keyout EcoStruxure.key -out EcoStruxure.csr Follow the prompts to fill out the information for the CSR Supply CSR, other certificate contact information, and a means of validating the request to the 3rd party CA Verify identity with CA (this may not be necessary if you use your company's internal CA/ root CA Receive host and intermediate CA certificates from 3rd party CA Make sure the CRT/CER files are in the C:\Program Files\OpenSSL-Win64\bin directory of Windows Explorer Use OpenSSL to convert the CRT or CER files into PEM files, as PEM is the only format EBO will accept openssl x509 -in certFileName.cer -outform PEM -out convertedCertFileName.pem Use OpenSSL to convert the private key file generated at step 6 from .key to .prv openssl rsa -inform pem -in filename.key -out filename.prv Run WorkStation as administrator In WorkStation, Control Panel > Certificates click on the server you are trying to add the cert to, either an AS or ES. Click on Manage Certificates > Add Existing  Put in a name for the certificate (it can be anything you'd like) Click the ellipsis next to host, intermediate, and private to add the appropriate PEM files and click ok  Select the newly added certificate from the drop-down and save the changes to activate Warm start the server After this process is completed, verify that connection to WebStation via HTTPS shows a secure connection/trusted certificate.

Issue In EBO BACnet device discovery, how is the BACnet MAC address defined? Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Enterprise Server Cause A BACnet device is uniquely identified by a network number and a MAC address. Resolution BACnet MS/TP A BACnet MS/TP device supports device MAC addresses in the range 0-127 for masters and 0-254 for slaves. Device MAC addresses are often configured using DIP switches or a configuration tool.   BACnet/IP MAC addresses for BACnet/IP devices are a combination of the IP address and BACnet/IP UDP Port expressed in hexadecimal notation. For example, if a BACnet/IP device is configured with an IP address of 192.168.1.5 and a UDP port of 47808 then:   IP address expressed in hexadecimal is 192 = C0, 168 = A8, 1 = 01, 5 = 05 UDP port expressed in hexadecimal is 47808 = BAC0   Therefore the MAC address will be, C0:A8:01:05:BA:C0   BACnet/SC BACnet/SC nodes are identified by their 6-octet virtual MAC (VMAC) address in form of a IEEE EUI-48 identifier which is randomly generated. A BACnet/SC device attempts to resolve its own VMAC in the network. If it detects another device is already using this VMAC, it will generate a new Random-48 VMAC address and try again.

Issue How do you see what authentication settings Security Expert was installed with? Product Line EcoStruxure Security Expert Environment Client/Server Authentication Cause When installing the Security Expert Client/Server three authentication settings for the Client to Server connection can be specified: To connect to the Security Expert Server using additional software, such as Data Sync or SOAP, the current authentication is needed so the additional software authentication can be set the same.  However, if this was not recorded at installation the only way to be 100% sure is to remove and reinstall. Resolution Navigate to the existing Security Expert installation folder:    C:\Program Files (x86)\Schneider Electric\Security Expert   Depending on the installed components there will be a file called either: SecurityExpertSV.exe.config - where only the Server component is installed SecurityExpert.exe.config - where only the Workstation component is installed Note: both files will be available if the Server and Workstation are installed on the same machine   Either file can be used.  Open the file using a text editor such as Notepad to find the current Security Settings used in the original installation. In the example below the authentication setting used was TLS 1.2 As illustrated in the image above the information is between the <netTcpBinding> tags.  The image below illustrates the settings for the three possible authentication types.  Look for the <security> tags to identify the authentication used:  

Issue The Data Sync Service Configuration Tool is showing an error when attempting to connect to the Security Expert Data Service. Failed to find operator where UserName = 'admin'. Exception: Access is denied Failed to find operator Product Line EcoStruxure Security Expert Environment Security Expert Data Sync Service Configuration Tool Cause The Authentication mode used by Security Expert is different from that used by SOAP. The Authentication mode selected during the installation of both software packages must be the same. Authentication mode Resolution Reinstall Security Expert or confirm the Authentication mode selected when it was installed. Consult the article Determining Security Expert authentication settings after installation. Reinstall Security Expert SOAP with the same Authentication mode used when Security Expert was installed.

Issue Continuum Graphics (Pinpoint): How do point updates take place and how can I change the update interval and polling speed? Is it different for BACnet points? Product Line Andover Continuum Environment Pinpoint Graphics Bacnet Cause How do point updates take place and how can I change the update interval and polling speed? Resolution In Cyberstation V1.71 and greater, the graphics polling engine was significantly changed. Prior to this change, the Pinpoint application would poll the points within its graphic file directly. If several graphics were open, each graphic would perform its own polling, This engine also applied to Web.client. Each control on the graphic had a separate selection where you could set the polling rate on a per-point basis on the miscellaneous tab of each control. This was the only method to adjust the point polling interval. The main reason for the graphic engine change was for Web.Client graphics. Slow networks, multiple browsers accessing the same graphics, and slow browser machines could make Web.Client graphics unacceptably slow.   The current method to get data into graphics involves a separate graphics polling engine per workstation. When one or more graphics are opened on a workstation or a Web.Client IIS server, the graphics register the points into the polling engine on that workstation. The polling engine then begins updating the values and sends the data to the Pinpoint/web.pinpoint clients. After initially sending all the data values to the graphic, it then only sends the data that has changed since the last update in an XML document format. If several graphics are requesting the same point values, the data is only polled once for all the Pinpoint clients on that workstation or Web.Client. Efficiency was also achieved by registering the points in the polling engine which allowed the polling engine to decrease the number of data requests by 50% to retrieve the same data.   There are now additional settings to adjust the polling rates in a graphic. #11 General preferences "Time interval between requests" This is a global setting and affects all workstations. By default, all polled points which are in the polling queue are sequentially updated at a continuous rate with a default delay between requests of 30 milliseconds. It is often recommended to set this to 100ms (Additional considerations below  under Multiple Cyberstation graphics performance)   General Preferences are accessed by Right Clicking on the Continuum icon in the Windows system tray and selecting General Preferences     There are also a pair of settings in the workstation preferences: #24 Pinpoint active polling rate #25 Pinpoint inactive polling rate These settings are for each workstation individually and do not affect the polling rates of the polling engine, but merely determine how often the graphic requests data updates from the polling engine based on whether a panel is or is not the active window. Typically these settings can be left at their defaults R&D has indicated that #24 is not used as Pinpoint always uses the inactive polling rate whether the window is active or not. Therefore, adjust #25 "Pinpoint inactive polling rate".  It is recommended to set this to keep this at the default of 250ms.   Cyberstation Preferences are accessed by Right Clicking on one of the Cyberstations while logged into Continuum and selecting Edit   Multiple Cyberstation graphics performance Several workstations may be configured to display graphics that are pointing to the same controllers and the controllers being polled may be on a large Infinet or MSTP network. In this case, the controllers could be overwhelmed by simultaneous data requests from the different workstations, slowing down controller scans, the whole field bus and overall system performance. R&D indicates that when multiple Cyberstation Graphics are used there is some randomness as to how the polling requests are accomplished. If graphic or system performance is an issue, it is suggested that another 30 Milliseconds is added to the general preferences "Time interval between requests" (#11) and then measure system performance and add additional time if needed up to 500ms.   When using this setting it is necessary to consider how many Cybersations would be running simultaneous graphics. For example:4 workstations polling graphics simultaneously with "x" number of points in it for 1 Netcontroller could have about 20 requests per second (determined via Wireshark capture at the NC NIC) 30 ms per X 4 Cyber =120ms added In this case, the recommendation was to set the "Time interval between requests" value to 250ms for performance   Note: Individual millisecond settings in each point do not effect polling for the point. They are not used.   BACnet points Bacnet points can be managed differently. Continuum BACnet points can either be polled the same way that Standard continuum points are polled or by using a COV. Standard polling is done by using the point objects from the "Infinity" side of the object tree. If you want to use COV for the point updates which is much more efficient, you should use the "BACnet Points" in the graphic, from the BACnet side of the object tree. The polling engine will then subscribe for COV updates to the respective controllers. When the graphic is closed the polling engine will unsubscribe the COVs. Third-Party BACnet controllers have an additional method to adjust the poll frequency. If the third-party BACnet controller supports COV subscriptions, Cyberstation will subscribe to these points as COV's like the Continuum BACnet controllers however, if the devices do not support COV's their points will be polled. Since many third-party BACnet controllers cannot withstand frequent data requests, there are two additional settings on the BACnet device object editor. The settings are on the Details tab on third-party BACnet controllers only. 1. Max # of Async requests The max # Async requests specify how many requests we should send before we get a reply to the data request, or how many requests can I queue. Typically this should be set to 1. 2. Request interval in ms  The request interval setting will depend on the device. Does it use Ethernet or MSTP network architecture? Are you running "Enhanced MSTP"? How many third-party devices are on the mstp network that cannot run enhanced MSTP? Typically it would be safe to set this in the 1000 to 5000 ms range based on desired data update rates and the controller's capability to handle the polling.

Issue Information needed for Integrating Access Expert BACnet objects into Continuum and EBO Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted EcoStruxure Building Operation Andover Continuum BACNet Cause BACnet objects from Access Expert may show in Andover Continuum, but will not function. An integration using EcoStruxure Building Operation is needed. Resolution BACnet objects from Access Expert may show in Continuum when a BACnet discovery is done, but they will not function.  An integration using EBO with a SmartConnector is required to use Access Expert BACnet objects. Further details on the EcoStruxure Access Expert Smartconnector are available from the Exchange Marketplace.  

Issue Examples of Permissions for specific actions needed for Access Expert Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause How to configure permissions in Access Expert for specific actions Resolution Permissions - Examples (User Groups)   Overview The Permission model in Keep is based on granular permissions at the API level. To review the Permissions basics, visit the User Group page. This article will break down permissions by the desired action within the Keep by Feenics application. *Note: The API level permissions mean that once permissions are set up in the windows client, they apply to the web client and mobile client.    Permissions Options The 5 options on individual permissions are listed below.   Create Read Update Delete Publish To ‘save’ a new object. To view existing objects. Once the object is created, changes can be made. To remove objects. Allows events related to the object to be published in the system. Example: publishing a pulse reader command requires the ability to Publish on that reader. Examples The examples listed below are showing the minimum requirements to do the action listed. To be able to do multiple actions, combine the listed permissions. How to log in to Instance Instance – Read   View Event History Event Message - Read    View Live Monitoring Event Message - Read   Acknowledge Events This permission group allows a user to view Live Monitor and Event History, open the Alarm, Acknowledge the Alarm, view the Person image associated with the alarm, and attach images to the alarm. Instance - Read Event Message – Read and Update Image - Read Person - Read Unlock Door Instance - Read User - Publish Controller - Read and Publish Downstream - Read and Publish Reader - Read and Publish Event Types: Mercury Commands - Unlock *Note: To Change the action allowed, simply change the Mercury Command allowed.   Update Reader Modes This permission group allows a user to view Live Monitor and Event History, open and modify reader modes. Instance - Read Event Message – Read Reader - Read, Update, Publish Add and Remove Linking Schedule - Read and Publish Add and Remove Linking Trigger - Read, Update, and Publish Add and Remove Linking on all object types. Procedure - Read, Update, and Publish Add and Remove Linking Downstream - Read and Publish Controller - Read and Publish Add and Remove Linking   To Add and Remove Favourites All Types - Add and Remove in Linking Column Add Widgets Keep Object - Read and Update Print Badges Badge type - Read Badge type field - Read (Note:If you are only allowing tagged badges, the badge type field must not have a tag associated). Image - Read Person - Read *Note: If the user needs to assign the badge type, then the "Add" column in the Linking section for Badge types must be selected on the Person permission.   To Play Sounds Image - Read Generic - Read Run "Access Request Report" (Reports on a persons access granted and denied events that day on ALL or specified  readers.) Instance - Read Person - Read Reader - Read Event Message - Read Access Rights for Person Report" or "Reader" Instance - Read Person - Read Reader - Read Event Message - Read Access levels - Read To view "Local Area's" Instance - Read Area - Read Controller - Read Person - Read To Add Admin HID Origo Mobile Credentials Advanced Actions "OrigoAdmin" Other permissions required will be dependent on other actions required for the user To View Elevator Floor Status Reader - Read Floor - Read   To Assign Elevator Floors to a Reader Reader - Read Floor - Read, Link Elevator Reader (add to add and remove to remove) Allow modifying objects with a specific Tag All Types – Read, Linking - Add, remove All Types - Read, Update, Delete, Publish, Linking - Add and Remove, Tags - specific desired tag Events - Desires Mercury/Bosch Commands Specify the desired tag in the Tags column. This permission group does not allow the group to ADD new objects simply modify or delete existing objecting with the specific tag.   Related articles:   Group Permissions  https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-User-Group-Permissions/ta-p/411404   Event History and Live Monitoring Site Permissions https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-Error-in-Live-Monitoring-document-while-trying-to/ta-p/411434  

  Issue Information needed to work with Access Expert Custom Forms Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Access Expert Custom Form configuration Resolution Custom Forms Overview Forms can be designed and applied to maintain additional people & reader information outside of traditional documentation or notes. Unlimited customer forms/fields can be added to the system and associated with a person or reader. The layout of the forms can be built to accommodate customer needs and can even be segmented. A good practice is to group additional information into common groupings such as Car Information, Health Information or Department Information. This type of approach will make the data entry easier. Information captured in a Custom Form can also be searched on and reported on. Once a custom form is created it will be available for use from either the person menu or the reader menu. Custom fields can then be utilized for applications such as customizing people reports, capturing additional information about employees, doing system searches as well as badge designing.   New Custom Form To start creating a custom form: Select the ‘General Configuration’ Select "Custom Forms”. Click “Add Custom Form”. Choose which editor the form will apply Enter the name of the Custom Form in the Application Name. (OPTIONAL) Choose the casing for the form. This is only important when leveraging the API or LDAP integration. Click “Save” or “Save & Close”. Below is an example of a Custom Form that has been created. The header, fields, titles, and placement of information on the form is customizable by clicking, dragging and dropping. The initial series of editors that support the creation of the form are across the top of the screen. Add Text Box – Adds a free form text box. Add Combo Box – Adds a free form text box that allows for multiple pre-selected entries from a picklist. Add Date Time – Adds a time and date entry box. Add CheckBox – Adds a checkmark box. Add Group Box – Adds a split box where the top section can be used as a title then other fields can be added. Add Header – Adds a header field that can be used for a single line title. Group Box When one of the box types is added to the form, the Properties section can be used to apply additional information and modify the data as it resides in the box. Every Content field that is added to a Custom Form must have a name. In this example, we will add a Group Box to capture information about an employee. Clicking the ‘Add Group Box’ provided the initial field. The title was applied by clicking the blank box and adding the name in the Properties editor under Content. This information can also be positioned to the left, center, stretched or to the right. The overall box can be enlarged by clicking the perimeter and then dragging to the desired size. Text Box Additional fields of information can be added to the Group Box by clicking on the desired data field type and it is applied to the Group Box. To ensure the new field is added inside the perimeter of the Group Box make sure to click inside the Group Box prior to selecting the data field. The new field can be dragged into the Group Box if it is added outside the group box. Once the field is added to the Group Box the Properties editor will allow the same type of modifications to be made. Once the new blank field is added you can click into the Header field under Content to apply a descriptive name. This same process can be repeated to add as many fields as needed.   Combo Box A Combo Box is added to a Custom Form just like the other box types. With a Combo Box, the Properties editor will display a new field called Items. Clicking the “…” will allow the operator to add the information that will be available when data entry is being performed. The completed form will look like this from the custom data menu on the cardholder.

  Issue Information needed for using Mercury downstream controllers with Access Expert Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause List of Mercury downstream controller and configuration information Resolution Mercury Downstreams    Overview Mercury controllers are an open architecture controller made by Mercury Security. Access Expert supports the series 2 and series 3 SIO boards.   Controller Equivalent    Features FN-RIM1 MR50 Single-card reader interface panel and supports Wiegand, clock and data, magnetic stripe, F2F, Supervised F2F, OSDP, keypad, and biometrics reader technologies. FN-RIM2 MR52 The MR52 is a dual-card reader interface panel. Each unit can connect two card readers, eight general-purpose input monitor points and six control relays to any Mercury EP series intelligent controller. FN-16IN MR16IN The  MR16IN interface panel can support 16 general-purpose input circuits and two dedicated programmable relay outputs. FN-16OUT MR16OUT The MR16OUT interface panel provides 16 general-purpose outputs as Form C relay contacts. FN-MR51e MR51e The MR51e is a single-door, network-ready interface panel.     Adding Downstreams to Access Expert Disconnect the power supply from the downstream and the controller. Set the RS485 jumper to the 2 wire position. Wire the RS485 communication from the downstream to the controller. Downstream Controller TR+ CLK/Data1 TR- DAT/Data0 GND GND Apply power to the downstream and the controller. In Access Expert, from the top bar menu (located at the top left corner of the screen) click on the ‘View All Hardware’ button to open the 'Hardware tree'. In the 'Hardware Tree', double click on the controller or right-click and select ‘Open’ top open the controller page. Alternatively, click on the 'Hardware Provisioning' tab (located a the top of the screen) to open the menu. Click on the 'Controllers' icon(located to the left of the 'Hardware Provisioning' menu to open the 'Controllers' page). Double click or right-click and select 'Open' on the controller, to open that controllers 'Controller Configuration' page. Click on the ‘Add downstream’ button (located at the top of the controller page) to add a downstream. From the drop-down menu, select the appropriate downstream model. Enter a unique ‘Display Name’ for the downstream. Set the ‘Panel Address’ of the downstream. Example: To set devices address to 3, DIP switch 1 and 3 must be ON and 2,3 and 4 OFF and 'Panel Address' in Access Xpert must be set to 3. The DIP switches on the downstream must match the ‘Panel Address’ in the 'Downstream Configuration' page. Note: DIP switches 1 through 5 sets the device address of the downstream and is binary. DIP switch 1 = 1, DIP switch 2 = 2, DIP switch 3 = 4, DIP switch 4 = 8, DIP switch 5 = 16 Confirm that DIP switch 6 and 7 are in the ON position to enable for 38.400BPS communication. Leave DIP switch 8 in the OFF position. Click on the ‘Save’ button (located at the bottom of the page) to apply changes to the downstream.   Downstreams are added to Access Expert from the Controller page. When adding a downstream, you will need to select the downstream type from the drop-down list. If the downstream you are trying to add does not match one of the types listed, it is either not supported on that port or not supported by that controller.     Downstream Addressing Chart     Common Issues Issue                                             Solution The EP/LP1501 has no SIO port The EP/LP1501 uses the CLK and DATA on Reader 1 to communicate to downstreams. This means that if you are leveraging a downstream device, the EP/LP1501 only supports 1 onboard reader. My MR52 is toggling on and offline. The MR52 has a conflicting address with another downstream. Confirm your dipswitches are set to the correct address. Addressing is done on dipswitch 1-5 and baud rate is set on dipswitch 6 and 7 (suggested both on). Dipswitch 8 should always be off. J3 - The jumper for 2 wire and 4 wire RS-485 also needs to be set. By default is set to 2 and should not need changing but this does happen. J5 is the Termination jumper that needs to be set on the last unit in the series. My MR51e is programmed for Static IP but won't connect Check the dip switches on the board. Make sure the dip switches are set back to static IP mode after programming. Check to make sure the static IP address programmed in is valid. Make sure the Downstream can be seen by the controller. My downstream will not come online but my other downstream did. If you have a Mercury downstream on the same port as an Engage Gateway, the Mercury downstream will not be able to come online. Engage Gateway's and Mercury downstreams cannot share a port. Confirm the addressing on your downstream is correct.  My downstream device says "Timeout" This is due to incorrect addressing or incorrect baud rate set on the downstream. Dipswitches 1-5 set the address in a binary fashion and dipswitches 6 and 7 set the baud rate. We suggest leaving both 6 and 7 on. My downstream device says it is in "loader mode" and will not leave that mode Follow the steps below to correct the loader mode: Remove Power from the controller and downstreams Disconnect all downstreams from the controller Bulk Erase the controller. Once the controller is powered back on, reconnect the downstream that is in loader mode only. Reboot the controller.

  Issue List of Mercury Controller Types and Features Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Mercury Controller Types and features to use with Access Expert Resolution Overview Mercury controllers are an open architecture controller made by Mercury Security. Feenics currently supports the LP series boards, the series 2 and series 3 MR SIO series boards.   Mercury Controllers   Equivalent Features FN-C1501 EP1501 The EP1501 is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 240,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Readers 1 SIO bus (note: connects via Reader Port 1) FN-C3202 EP1502 The EP1502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings. 240,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Reader Ports 1 SIO bus FN-C3200 EP2500 The EP2500 is an intelligent controller for managing up to 64 doors/openings. 600,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 SIO Buses FN-C4502 EP4502 The EP4502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings and complies with the BACnet standard. 2,000,000 Cardholders 50,000 Transaction buffer 32 Access Levels per cardholder 2 Onboard Readers 2 SIO Buses FN-LP1501 LP1501 The LP1501 is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 240,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 130 inputs and 130 Outputs 2 Onboard Readers 1 SIO bus (note: connects via Reader Port 1) FN-LP3202 LP1502 The LP1502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings. 240,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 520 inputs and 516 Outputs 2 Onboard Reader Ports 1 SIO bus FN-LP3200 LP2500 The LP2500 is an intelligent controller for managing up to 64 doors/openings. 600,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 1024 inputs and 1024 Outputs 2 SIO Buses FN-LP4502 LP4502 The EP4502 is an intelligent controller for controlling two connected doors and managing up to 64 doors/openings and complies with the BACnet standard. 2,000,000 Cardholders 50,000 Transaction buffer 255 Access Levels per cardholder Supports up to 1024 inputs and 1024 Outputs 2 Onboard Readers 2 SIO Buses FN-M5-IC M5-IC An intelligent control device for the replacement of the Casi PX, PXN and PXNplus CPU controller. The single controller supports up to 64 readers across multiple enclosures. 128 Access Levels per cardholder FN-M5-ICS M5-ICS A multi-device interface panel that is a direct retrofit of Software House’s Pro GCM module. A 64 reader capacity 600,000 Cardholders Mercury - PW6K1IC Prowatch 6000  The PW6K1IC is an intelligent controller that is expandable up to 8 downstream SIO controllers and up to 16 MR51e network-ready door controllers (for a total of 17 doors/openings). 15,000 Cardholders 10,000 Transaction buffer 32 Access Levels per cardholder   EP Controllers - End of Life  Feenics used to support the EP Series controllers, however, they have been replaced with the LP series. Related article - Updating Mercury Firmware https://community.se.com/t5/Building-Automation-Knowledge/Access-Expert-Updating-Firmware-on-an-SSC-or-Mercury-Controller/ta-p/410961  

Issue Metasys® N2 Integration to SBO Product Line EcoStruxure Building Operation Environment Struxureware Building Operation Metasys N2 Cause This Quick Start Guide will assist the Schneider Electric branch or dealer installation team with the basic steps to bring the virtual BACnet devices emulated by the S4 Open: BACnet-N2 Router into the SmartStruxure environment as part of a Johnson Controls Metasys® N2 integration into SBO. This document is not intended to be a full tutorial or user manual for either the S4 Open: BACnet N2 Router or the SmartStruxure system. Refer to the manufacturer’s documentation for each of these systems for detailed information. S4 documentation, the complete Device Template library, and support utilities can be found on the support CD delivered with your S4 Open appliance. Please contact the S4 group for any questions on this process.  Resolution Step 1:   Follow the installation instructions provided with the S4 Open: BACnet-N2 Router to discover and publish the N2 devices in the Metasys® installation to BACnet IP. All operations in SmartStruxure will be against these emulated BACnet IP devices each representing the underlying N2 device. Investigate before you integrate! Validate the N2 bus to make sure that it is electrically in spec and that all N2 devices are working properly before starting the integration process. Assign a unique BACnet virtual network number to each S4 Open: BACnet-N2 Router. N2 devices connected to this S4 Open appliance are published as emulated BACnet IP devices under that network. The Configure Wizard in the S4 Open Management Console will assist you with generating a unique BACnet Device ID for each N2 device. Point instance numbers are included as attributes in our Device Templates for all application-specific controllers. Either of these can be manually overridden in the S4 Open Management Console to meet unique requirements. The S4 Metasys® Configuration File Conversion Utility can be downloaded from the S4 Group web site and will assist you in creating custom Device Templates for DX-9100 devices or application-specific controllers. You will need the corresponding .DMO or .PRN files as input to this utility. A detailed understanding of Metasys® N2 devices, the Metasys® system, and the associated configuration and commissioning utilities are necessary to support successful integrations. If you don’t have this expertise in-house, The S4 Group can recommend a consultant to assist you. NOTE: We highly recommend that you attend a two-day S4 Boot Camp to make sure that you have all the skills necessary to install and configure the S4 Open: BACnet-N2 Router. Step 2: Bring up the SmartStruxure BACnet discovery tab and select BACnet devices. In this example, you can see that the S4 Open BACnet-N2 Router was defined in Network 1 and the N2 devices are in Network 122. The other device in Network 1 in this example is a JCI NAE. The best practice is to assign the S4 Open: BACnet-N2 Router to the BACnet network that you are using as your BACnet backbone. As with any BACnet device, the BACnet-N2 Router must be assigned a unique BACnet device ID. Step 3: Expand the navigation pane to expose the BACnet Interface / IP Network folder. Then select and drag the N2 devices from the Device Discovery tab to the IP Network folder. SmartStruxure will tell you that an Upload is required. Respond OK. Step 4: Navigate to the IP Network folder, select the properties page for each device, and request an Upload operation. This will bring the device properties and point list for each N2 device into SmartStruxure. SmartStruxure will respond with the following confirmation as each upload is completed. Step 5: When the Upload process is completed for all N2 devices and the S4 Open: BACnet-N2 Router, you can continue your SmartStruxure installation process as you would for any BACnet device. Note that there will be no points published under the S4 Open: BACnet-N2 Router itself but you will be able to confirm the Operational Status of the system from SmartStruxure. The Schneider Electric support organization will supply pre-sales engineering support and first-level technical support for the Metasys® N2 to SBO integration solution. The S4 Group will be available to provide 2nd level support to these integration projects.  

Warning   Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue Using sensors, other than the D?T range in a Sigma controller Product Line Satchwell Sigma Environment Sigma Release 4_05-SEB (Build 3_43_18) Sigma Release 4_05-SP2 (Build 3_42_48) Sigma Release 4_06 (Build 3_44_14) Sigma Release 4_06 SP1 (Build 3_44_16) Sigma Release 4_07 (Build 3_45_48) Sigma Release 4_07-SP1 (Build 3_45_51) Sigma Release 4_07-SP2 (Build 3_45_58) Sigma Release 4_08 (Build 3_46_57) Cause Using 10k Type 2 and type 3 Thermistor causes hardware alarm Resolution The lookup value for a Sigma resistance input is calculated as a percentage of a 2 volt signal (that's what is measured at the A/D convertor). If using a sensor other than a standard D?T range sensor, a calculation needs to made, to obtain the value to be entered in the input column (a % of 2 volts) of the look up table.   The calculation is as follows: - ( 10^6 * R1 )      /4000 ( 14700 + R1 ) Where R1 = resistance of the input 14700 =resistor on AI card The circuit shown below is a typical example of an AI channel for a resistance input.     It is suggested to put a 10K resistor in parallel therefore, the resulting circuit resistance can never be higher than 10K.   Attached is information for both the 10K type 2 and 10K type 3 sensors. Column C is the raw sensor resistance. Column D is the controller input resistance with a 10K shunt resistor connected. Column E and F example of the look up table.