Issue Niagara R2 Enterprise Server stations may experience slow startup or performance issues due to excessive historical alarms stored in the database. Users need methods to remove alarm history or the alarm file to restore normal operation. Product Line TAC IA Series Environment Niagara R2 Enterprise Server Cause Accumulation of alarms and logged data in the station’s database increases boot time and impacts performance. The alarm archive file and associated historical data can grow significantly over time. Resolution There are two main approaches to clear alarms and logged data: Method 1: Delete the APP Folder (Complete Removal) This method removes all archived data, including alarms, logs, and events. Steps: Stop the Niagara Service: Open Control Panel → Administrative Tools → Services. Locate Niagara, right-click, and select Stop. Delete the APP Folder: Navigate to: C:\Niagara\stations\[station name]\app Delete the app folder. Restart the Niagara Service: Return to Services, right-click Niagara, and select Start. Result: The station will recreate the APP folder and Cloudscape structure on restart. All archived data, including alarms, will be cleared. Method 2: Use SQL Queries via appdb/queryForm Servlet (Selective Removal) This method allows targeted deletion of alarm history without removing all logged data. Steps: Open a browser and navigate to: http://[ipaddress]/appdb/queryForm Enter and execute the SQL query: delete from event.eventhistory Repeat for other tables if needed (refer to SQL_Tutorial\QueryExamples_10_6_04.pdf for examples). Note: This process may take time depending on database size.

Issue The NW8000 Optimal Start-Stop (OSS) block in EcoStruxure Building Operation (EBO) shows “Abnormal Input” status even when configuration appears correct. Bound parameters display valid values, but the object status remains abnormal. Product Line EcoStruxure Building Operation Environment Building Operation Server NW8000 OSS objects available for use outside NW8000 interface from EBO 2022 onward. Cause Incorrect Input Configuration: Both Heat Enable and Cool Enable inputs are set to ON (true) simultaneously, forcing conflicting modes. Missing Bindings: Required bindings to the Value and TimeToNextTransition properties of the digital schedule are not configured. Parameter Mismatch: Heat/Cool changeover temperatures and PreStart/PreStop tables must use correct values for the measurement system used (Fahrenheit/Celcius). Digital Schedule Misconfiguration: OSS relies on the TimeToNextTransition value from the referenced Digital Schedule. If the schedule has no events within the next 8 days, the schedule outputs a “maximum” value (millions of minutes until year 2106), causing OSS to enter Abnormal Input. Resolution Correct OSS Inputs: Set Heat Enable and Cool Enable to Null for normal operation. If forcing mode is required, only one input should be ON at a time. Both ON = Abnormal Input. Verify Bindings: Bind OSS block to: Digital Schedule → Value Digital Schedule → TimeToNextTransition Ensure schedule outputs correct ON/OFF states. Configure Digital Schedule Properly: Include an accurate weekly schedule and exceptions. Ensure at least one event exists within the next 8 days. Refer to: Adding a Weekly Event Adding a Date Exception Event Adding a Date Range Exception Event Adding a Calculated Exception Event Check Parameters: Heat/Cool changeover temps (OA values) must use correct values for the measurement system used (Fahrenheit/Celcius). PreStart/PreStop table range must match the measurement system used. Heat and Cool Enable Truth Table Heat Enable Cool Enable Actions EMPTY / NOT ACTIVE EMPTY / NOT ACTIVE Use Heat/Cool Changeover Temperatures OFF OFF No Heating or Cooling Pre-start or Pre-stop EMPTY / NOT ACTIVE OFF No Heating or Cooling Pre-start or Pre-stop OFF EMPTY / NOT ACTIVE No Heating or Cooling Pre-start or Pre-stop ON OFF / EMPTY / NOT ACTIVE Enable Heating for Start. Use Heat Start/Stop Tables OFF / EMPTY / NOT ACTIVE ON Enable Cooling for Start. Use Cool Start/Stop Tables ON ON Outputs set to ABNORMAL INPUT

Issue The following error appears in the Niagara R2 UNC Standard Output Window: Duplicate Server Sessions – kill [Station Name] Product Line TAC IA Series Environment Niagara R2 Cause This error typically occurs when another station running on the Enterprise Server has the same name as the UNC station. Running multiple stations with duplicate names creates conflicts in session handling. Resolution Verify Station Names Ensure that each station running on the Enterprise Server has a unique name. Stop Duplicate Station Use the Admin Tool to stop the station on the Enterprise Server that shares the same name as the UNC station. Best Practice Avoid running multiple stations on the same Enterprise Server unless absolutely necessary. Under normal circumstances, only one station should be active to prevent conflicts.

Issue How can it be determined which LonWorks Program IDs are supported by the Niagara R2 system? Product Line TAC IA Series Environment Niagara R2 LonWorks Cause Users need to identify supported LonWorks Program IDs for integration and compatibility checks within Niagara R2. Resolution Create a Test Station Install a test station on the localhost that includes: LonWorks Service LonWorks Network container LocalLonDevice Access Lon Utilities Manager Open the test station in WorkPlace Pro. Right-click on the LonWorks Service and select Lon Utilities Manager. Run Program ID Report Select LocalLonDevice. Choose Command of Reports and Sub-command of programids. Execute the command to generate a listing of all Program IDs for shadow objects in the local tridiumx library (lonDevices container). Save and Search Save the report as a text file. Import into Excel for easy searching and filtering. Update When Needed Re-run the report whenever a new Lon JAR file is added or an existing Lon JAR file is updated.

Issue Clarification on linking rules within the Niagara R2 platform and restrictions when linking objects between stations. Product Line TAC IA Series Environment Niagara R2 platform Cause Users need guidance on correct linking practices to ensure proper functionality and avoid unsupported link types. Resolution General Linking Rules Properties must share the same data species for a valid link. A link connects one object's output to another object's input. The Link Editor enforces these rules during selection. Exceptions for Gx Objects Gx objects (e.g., GxText) have only inputs and can link to internal configuration properties or most outputs. These links are UI links, not part of control logic, and are used for interface display. Multiplicity Rules One-to-many: Multiple inputs can link to a single output. Many-to-one: Only allowed for priorityArray or triggerType inputs (or certain Lon properties). External Link Restrictions (Between Stations) Links between prioritizedOutputs and priorityArray inputs are not permitted. Links involving triggerType data species are disallowed. GxText objects cannot link to internal properties of another object externally (only inputs/outputs are available).

Issue Duplicate LON device node numbers detected in a Niagara R2 UNC station, preventing successful commissioning of controllers. Product Line TAC IA Series Environment Niagara R2 UNC station LonWorks Service Workplace Pro Cause When a LON device is relocated from one site to another, it may retain its previously configured subnet and node number. If these values match an existing device in the new installation, a duplicate address conflict occurs during commissioning. Resolution Follow these steps to resolve duplicate node numbers: Open Lon Device Manager from the right-click menu of the LonWorks Service. Click Find to list all LON controllers under the UNC. An error message will indicate duplicate subnet and node numbers. Right-click one of the devices with the duplicate address. If no menu appears, try another device with the same subnet and node number. Select Properties → General tab → Engineering tab. In Node State, choose Unknown. Change the NodeID to a unique value not currently in use. Click Apply to save changes. Return to the Device List screen and reselect the modified device. Click Commission and verify the Neuron ID in the pop-up window. Click Apply and wait for commissioning to complete. Repeat steps 3–10 for any additional devices with duplicate addresses.

Issue How to calculate and display Mean Kinetic Temperature (MKT) for a temperature sensor in EcoStruxure Building Operation (EBO). Product Line EcoStruxure Building Operation Environment EBO version 3.2 or later (required for Log Processing Trend Log functionality) Trend logs available for temperature sensors Customer requirement: MKT based on hourly averages or 30-minute intervals over a 24-hour period Cause Mean Kinetic Temperature (MKT) is a derived temperature that represents the cumulative thermal stress experienced by a product over time. Unlike a simple average, MKT gives greater weight to higher temperatures because chemical degradation accelerates exponentially with temperature (based on the Arrhenius equation). Why it matters: Used in pharmaceutical, food, and logistics industries for stability studies and cold chain monitoring. Sensitive to temperature spikes—short excursions at high temperatures significantly increase MKT. Recognized by FDA, EMA, and ICH guidelines for stability and excursion analysis. Formula for equal time intervals: ​ Where: TK​ = Mean Kinetic Temperature (Kelvin) ΔH = Activation energy (~83.14472 kJ/mol for pharmaceuticals) R = Gas constant (0.008314472 kJ/mol·K) T1,T2,…Tn​ = Temperatures in Kelvin n = Number of readings EcoStruxure Building Operation does not have a native MKT function, so it must be implemented using custom calculations in Log Processing Trend Logs. Resolution Use three Log Processing Trend Logs to compute MKT from trend logs: Step 1: Prepare Hourly Average Temperature Create a Log Processing Trend Log named HourTemp. Period Interval: 1 hour Calculation Type: Average Input: Temperature trend log Persist Data: False Step 2: Calculate Denominator for MKT Formula Create a second Log Processing Trend Log named MKTdenom. Period Interval: 1 hour Calculation Type: Average Input: Reference HourTemp log Log Unit: Celsius → Target Unit: Kelvin Custom Calculation: var dH := 83.14472; // Activation energy (kJ mol^-1) var R := 0.008314472; // Gas constant (kJ mol^-1 K^-1) exp(-dH / (R * @(HourTemp))) // Temp in Kelvin Step 3: Compute Final MKT Create a third Log Processing Trend Log named MKT. Period Interval: 1 day Calculation Type: Summary Input: Reference MKTdenom Custom Calculation: var dH := 83.14472; var R := 0.008314472; ((dH / R) / (-log(@(MKTdenom)/@(MKTdenom:Count)))) - 273.15 This converts back to Celsius. For Fahrenheit: (((dH / R) / (-log(@(MKTdenom)/@(MKTdenom:Count)))) - 273.15) * (9/5) + 32 Important Note You may have to adjust the substitution code based on what you have named your log references. Ensure the variable names in the formula match your Log Processing Trend Log names. Additional Notes Ensure @(MKTdenom:Count) matches the number of samples per day. Adjust constants if customer specifications differ. Set the unit on the final Log Processing Trend Log (°C or °F). You can alarm on MKT values or display them in dashboards and trend charts.

Issue Users encounter problems assigning entitlement licenses to AS-B and AS-P controllers in EcoStruxure Building Operation (EBO) 2022 (v4.0) and later using Device Administrator. Common symptoms include: Entitlement assignment fails for AS-B/AS-P. Assignment option is greyed out. Entitlement added but no license product appears. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium (AS-P) Building Operation Automation Server Bundled (AS-B) Building Operation Device Administrator (DA) Cause Starting with EBO 2022, Schneider Electric introduced a scalable licensing model that decouples hardware and software: Hardware is sold at a lower price. Sites purchase license bundles sized for their needs (Standalone, Standard, Enhanced, Full). Impact: Pre-2022 AS-P/AS-B models included most software capabilities and require upgrade SKUs when moving to EBO 2022 or later. Post-2022 Secure Boot AS-P and Scalable AS-B models require new entitlement bundles and support flexible licensing. Secure Boot adds cryptographic firmware validation. Resolution Verify Hardware Model AS-B: SXWASBXXX10001 → Requires upgrade bundle license. SXWASBXXHP10001 → Compatible with EBO 2022 and later bundle. AS-P: SXWASPXXX1000X → Requires upgrade bundle license. SXWASPSBX10001 → Compatible with EBO 2022 and later bundle. Check EBO Version For EBO 2022 and later, confirm entitlement compatibility. Assign Correct License Use upgrade license for older controllers. Activate via Device Administrator with internet access. Confirm Assignment After activation, assignment option should be enabled. If “No license product available” appears, verify entitlement type. Reference: Part Number Summary and Hardware-Software Compatibility Matrix. License Compatibility by Hardware Model Hardware Model EBO Min Version License Type Notes AS-P (SXWASPXXX1000X) 1.7.1 Upgrade Bundle Non-secure boot, pre-2022 hardware AS-P Secure Boot (SXWASPSBX10001) 2022 New Entitlement Bundle Standard, Enhanced, Full bundles AS-B (SXWASBXXX10001) 1.8.1 Upgrade Bundle Older AS-B models require upgrade AS-B Scalable (SXWASBXXHP10001) 2022 New Entitlement Bundle Standard or Full bundles  

  Issue A License Violation alarm is triggered without displaying a License Violation banner. Alarm reactivates after acknowledgment, approximately every 10 minutes.   Device Administrator also shows a license violation in "License status," when all servers show no violation. Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Enterprise Central Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Potential communication issue, possibly related to return path or port configuration. An incorrect ES port may be in use, which could be contributing to the issue. The Communication Tab [Communication View] and Server List in xbk Analyzer show only the ES, indicating limited server visibility. Resolution Verify Communication Path Ensure the ES is defined as using the same ports across all servers. Confirm that the ports are correctly configured and open on all relevant servers. Review the Communication Tab [Communication View] and Server List Check that all expected servers are listed and actively communicating. If only the ES is visible, investigate potential network or configuration issues. See article for additional information: Updating a Enterprise Server IP Address - Schneider Electric Community Check AS Logs Log in to the Automation Servers to identify any communication errors. These errors may not be visible from the ES alone. Next Steps If the above steps do not resolve the issue or the root cause remains unclear: Refer to the article for possible communication-related troubleshooting options: Enterprise Server and Automation Server Bindings show Unresolved - Schneider Electric Community Refer to the article for additional license troubleshooting options: Troubleshooting EBO license violation issues - Schneider Electric Community Contact your local support organization for further assistance.

Issue The OnSite Stat Controller can read temperature values, but the system does not control outputs. The SS light on the Site Stat Controller Interface is not flashing. Product Line Andover Continuum Environment Andover Continuum Stat Controller Cause A field wiring error occurred. The temperature sensor was incorrectly wired with x1 and x2 terminations reversed. Resolution Verify the wiring of the temperature sensor. Ensure x1 and x2 terminations are correctly connected. Once corrected, the controller resumes normal operation and the SS light flashes as expected.  

Issue Users upgrading from older Continuum versions (e.g., v1.62) need to confirm whether LCX898 and ACX781 Infinet controllers are still supported in the latest version (v2.03). Product Line Andover Continuum Environment  CyberStation Continuum versions 1.62 through 2.03 LCX898 and ACX781 Infinet controllers Cause The controllers are either in limited production or no longer manufactured, raising concerns about compatibility during system upgrades. Resolution LCX898 and ACX781 controllers are supported in all CyberStation versions from v1.62 to v2.03. No chip change or hardware modification is required for compatibility. Ensure proper configuration and testing after upgrade to maintain system stability.

Issue When communication is lost to an AC1 module, doors lock down even if they were previously unlocked by schedule. Product Line Andover Continuum Environment AC1 modules Cause The AC1 module is designed to fail to a secure position when communication is lost, ensuring security during network or controller failures. Resolution This behavior is intentional for security purposes. When communication is lost, AC1 modules automatically lock doors to maintain a secure environment. To prevent unexpected lockouts, ensure redundant communication paths or monitor module connectivity.

Issue Older sites still have ACX781 controllers installed, but the cabinet keys are missing. Users want to know if replacement keys can be ordered. Product Line Andover Continuum Environment ACX781 Cabinet Enclosure Cause The ACX781 controller was discontinued in 2007, and the stock of cabinet lock/key assemblies has been depleted. Resolution Replacement cabinet keys for ACX781 controllers are no longer available. If access is required, consider replacing the cabinet lock with a standard lock assembly from a local hardware supplier. For long-term support, plan to upgrade to current-generation controllers.

Issue Automation Servers in an EcoStruxure Building Operation (EBO) system are unexpectedly changing their time. Investigation shows that a third-party BACnet IP device is sending BACnet Time Sync messages, causing the time drift. Product Line EcoStruxure Building Operation Environment EcoStruxure Building Operation BACnet IP Cause A third-party BACnet device is broadcasting BACnet Time Synchronization messages on the IP network. By default, older EBO versions honor these messages, resulting in unintended time changes. Resolution Option 1: Modify Third-Party Device Configuration If possible, disable BACnet Time Sync on the third-party device. This is the most direct solution but depends on vendor capabilities. Option 2: Upgrade EBO From EBO 5.0.3.16010 (CP15) onward, AS-P controllers ignore BACnet Time Sync by default. This behavior is first included in: EBO 5.0.3.16010 (CP15) EBO 6.0.4.6003 (CP4) EBO 7.0.2 release To re-enable honoring BACnet Time Sync (if required): Configure a service_blacklist Add the following to the file to enable the time sync: <blacklist> <global> <enable-execute-time-sync/> </global> </blacklist>

Issue Confusion exists around which MicroNet controllers are supported in EcoStruxure Building Operation (EBO), especially during upgrades to EBO 7. The term “MicroNet” covers multiple product families with different protocols and support timelines. Product Line EcoStruxure Building Operation, TAC IA Series, Satchwell MicroNet Environment EcoStruxure Building Operation (EBO) MicroNet 2000 (NW8000) I/A MicroNet (MNL and MNB) Satchwell MicroNet Cause The term “MicroNet” can refer to multiple unique product ranges. In EBO documentation, MicroNet typically refers to Satchwell MicroNet, the European range of controllers using NCP, ARCnet, or LON protocol, which are not supported from EBO v4.0 onward. Other MicroNet families (MicroNet 2000 and I/A MicroNet) have different support histories. Resolution Refer to the table below for family types, lifecycle dates, and EBO support history: Family Protocol Introduced Withdrawn EBO Support History MicroNet 2000 (Barber Colman) MNet under ASD Late 1980s 2011 Supported up to EBO v3.2 Not supported in EBO 4.x–6.x Reintroduced in v7.0 I/A MicroNet – MNL Series LonWorks ~1998 2023 Supported in all SBO/EBO versions I/A MicroNet – MNB Series BACnet ~2003 2023 Supported in all SBO/EBO versions Satchwell MicroNet NCP / ARCnet / LON ~1998 2013 Supported up to EBO v3.2 Not supported from EBO v4.0 onward Additional Notes: MicroNet 2000 support was reintroduced in EBO 7 after being dropped in EBO 4–6. I/A MicroNet (MNL and MNB) support has never been removed from EBO. Satchwell MicroNet is unsupported from EBO v4 onward.

Issue During an Automation Server upgrade using Device Administrator, you may see warnings or errors in the Conversion Log. Errors block the upgrade process. Warnings allow the upgrade to complete, but may indicate invalid values or bindings. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS-P, AS-B Building Operation Enterprise Server Building Operation Device Administrator Conversion Log Cause Starting with EBO v1.4, new binding rules were introduced: Public Numeric/Signal bindings removed Multiple bindings per point prohibited (only the first remains) Bindings to Local-Node NVIs dropped Older configurations that violate these rules trigger warnings or errors in the Conversion Log. Resolution Run the Device Administrator upgrade. Instructions on how to perform the Automation Server upgrade and how to obtain the Conversion Log, see: SmartX Server System Upgrade Workflow - EcoStruxure WebHelp  Opening the Conversion Log - EcoStruxure WebHelp Export and review the Conversion Log: The file paths given in the Conversion Log entries will direct you to the location of the unresolved or invalid reference. Depending on the type of entry it is, it may require further action to correct the problem.   Type of entries found in the Conversion Log WARNING: ERROR: Invalid_Property_Reference (destination) (source) Explanation: Either rule 1 or 3 has been broken. If a public numeric/signal is bound programmatically to another object then it violates rule number 1. The public numeric/signal in the program must be changed to an input or output before upgrading the database. If the destination of the binding is an NVI in the Local Node then it violates rule number 3. A change to the configuration of the local node must be implemented before performing the upgrade. In many cases the substitution of an NVO for the NVI will address this issue. Explanation: This binding should not have been allowed in SmartStruxure version 1.3. In the StruxureWare Building Operation Technical Reference Guide, you will find on page 2107 that BACnet priority 6 is reserved for future use. This binding needs to be made to a different priority. WARNING: ERROR: Object_Does_Not_Exist (object). Explanation: The object that the reference is trying to bind to does not exist. In other cases the binding was already broken in the source database so it will remain broken in the target database. The binding fix can be addressed before or after the upgrade. WARNING: Property (property) bound to (property), so binding to (property) is dropped. Multiple bindings are not allowed in SmartStruxure version 1.4 and above. Explanation: The object is being written to by multiple objects and/or programs. This violates rule number 2 and is no longer accepted. After the upgrade, only one of the bindings will be left connected and all others will be dropped. This will require changes to be made to the configuration to maintain the same operation. Note: In some cases this warning can occur due to a default value of a configuration object that is mistakenly interpreted as a duplicate binding. The binding is in fact preserved by the upgrade and no further action is required. WARNING: Discarding incomplete binding for (object) -unknown source. Explanation: Due to a version 1.3 defect, the source version configuration database contains an incomplete binding error. This is not a problem but it may be a sign that someone intended for the property to be bound to something but failed to do so. Therefore, the configuration should be examined after the upgrade has been completed to insure that everything is okay. No information has been lost in the upgrade but check the configuration to rule out any errors in the source version database. WARNING: Property (property) in (object) is Unit configured but is not configurable in the new. Explanation: This property has a selected unit configured in the source version database, while in the target version configuring the unit of this property is no longer possible/meaningful. These errors should be investigated to insure that there has been no negative impact on the operation. Generally this error will not be a problem and will require no further action. WARNING: Property REF in (object) is not defined in the new system, skip REF. Explanation: The REF property prior to version 1.4 held a back-reference to an object or property that was referring to the property at hand. Starting in version 1.4 and on, the back-references are handled by other means and are no longer represented in the configuration database. This information can not be upgraded but this is not a problem and no further action is required. WARNING: Invalid value for (property) in the object, (object). The default value has been applied. Explanation: The value seen in the source version is invalid or can not be found; therefore the upgrade process sets it back to the default value. No further actions needs to be taken. WARNING: The declared instance (instance) is obsolete but contains non-default data which has been discarded. Explanation: If the instance is a SavedUserTokens or System/Remote Server warning then the warning can be ignored. No further action is required. WARNING: Property (property) in (source) is not an acceptable property type and is not configured. Explanation: This has to do with the lead reference for shadow Alarm Control Panels that cannot be properly upgraded due to changes to the type of system in version 1.4. There is logic in place that automatically sets the lead reference to the ES again. This is a warning that can be ignored. Explanation: There have been changes made to the type of system. This change prevents the hidden SynchSource property of the Time Zone setting in the source version of the database from being upgraded automatically. If the lead reference was set for Time Zone in the source database, this may have been erased and will have to be done again after the upgrade. This should be followed up manually. Explanation: The new referencing scheme expects all references to be relative so if there is a full binding path it is perceived as an error. This is not an issue and requires no action. Explanation: MatchedDevice is a hidden property that can not be seen. This warning refers to old items that have not been cleaned out. This warning can be ignored. Note: Also keep in mind that the upgrade process considers any empty link "not an acceptable Property". This error can be ignored, no changes need to be made. INFORMATION: Property "Value" in (location) is Unit configured but is not configurable, default unit is used. Explanation: This property has a configured unit that is no longer allowed to be configured in the target database, a fixed default value is used. This is unlikely to cause a problem, no further action needs to be taken.  

Issue The command string referenced in AN-355 for Avigilon PTZ integration with Security Expert is unclear, leading to confusion about which command should be entered. Product Line EcoStruxure Security Expert Environment EcoStruxure Security Expert Avigilon VMS Cause AN-355 documentation states that a command string must be entered into Security Expert but does not specify the exact format or value, causing ambiguity during configuration. Resolution To configure PTZ commands for Avigilon integration in Security Expert: Navigate to Monitoring > Setup > PTZ Commands. Create a New PTZ Command. Under Configuration, select the target Camera. In the Command String field, enter the Preset number programmed in Avigilon. This number corresponds to the desired preset position that will be sent to the DVR. Example: If Avigilon has presets labeled 0, 1, 2, and 3, entering 0 in the Command String will move the camera to Preset 0.

Issue Need a method for mass importing User photos for creating / updating the Users for a Security Expert site. Product Line Security Expert Environment Security Expert Security Expert Data Sync Service (SX-DB-SYNC) Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause Data Sync Service is typically used to import data from the third party system.  In this instance, a CSV file containing the data to be imported into the Security Expert database is used. The Data Sync Service is configured to monitor the folder where this CSV file is located and automatically (if configured) import the relevant data into Security Expert, creating records (including users, access levels, areas, doors, schedules, and so on) for each matched entity. Resolution The Data Sync Service can be used to map specific fields from a CSV file to fields within Security Expert. One of those fields can be the User photos. Below is a guide on how to implement this.   1. Directory Setup Before opening the Security Expert Data Sync Service, it is necessary to setup a CSV file and directory for the Data Sync Service to work with. The only requirement for now is that each image must have a unique name and that the folder housing the images must be called "Photos". Figure 1 shows an example folder structure: Note: The names of the folder, CSV file and image names are not critical. As long as the image names match what is in the CSV file.   2. CSV File A CSV file is a comma separated file with each row being a separate record and columns (fields) separated by comma's. An example CSV is shown below:   UniqueID,FirstName,LastName,AccessLevel,PIN 101,First,User,Visitor,1284 102,Second,User,Visitor,5618 Note: The UniqueID field will need to be the file name of the Users image. For the below example CSV, two images must be present in /Photos/ with the names 101.jpg and 102.jpg.   3. Security Expert Operator It is recommended that a new Security Expert Operator is added for importing from the Data Sync Service. This ensures that records that have been added / modified / deleted by the Data Sync Service can easily be identified. To proceed past the Data Target section the Show PIN numbers for Users option must be enabled in the Operator object.   4. Data Target Now that an Operator, directory and CSV have been set up, open Security Expert Data Sync Service and follow these steps: Select Security Expert from the Target System dropdown. Confirm the SOAP Server Address. If the defaults were accepted during the installation of the SOAP Service, enter http://localhost:8030/SecurityExpertSOAPService/service.svc. Enter the Username of an Operator. Enter the Password for that Operator. From the Site dropdown, select the Site that the records are to be imported to. All Sites that have been added in Security Expert will be available in the dropdown. Overwrite the Site ID during the field mapping process if the records are imported to different Sites within a single import. Note: The rest of the fields on the Configuration window are disabled until a valid Server Address, Username and Password have been entered.   5. Sync Options Set the Resynchronize Every time to a time interval over which the service should resync data. Tick the Enable Error Log checkbox to populate the Event Viewer with events that will make error solving simpler.  6. Data Mapping  Configure the records and import file with the following steps. Select Users from the Record to Sync drop-down.  In the File Directory field, enter the created folder. If importing a single file, enter the name of the file in the Import File field. If the checkbox is left unticked, all files in the File Directory will be imported. From the File Format drop-down, select Delimited. If the import file is a CSV, select {CR}{LF} as the Row and {Comma} as Column delimiters. Enable the option to Start Import At Row 2 to skip the header.    7. Field Mapping The field mapping phase allows CSV columns (Source Column) to be mapped to a record type in the Security Expert Database (Target Field). To import the example CSV, the field mapping must be configured as below. Link a Target Field and Source Column, simply select both in the interface, complete the following: Link the following [Target Field : Source Column]: ImageID : 1, First Name : 2, Last Name : 3, UserAccessLevelGroupDataData > UserAccessLevel : 4 PINNumber : 5, Select ImageID (Column 1) as the Unique Field. For UserAccesLevel, open the Advanced Data Configuration by clicking the [ … ] button. Ensure that Use This Field As The Group Data Identifier is set and Grouping Type is Singular Data. Ensure Target Field Record Type is ticked and set to Access Levels. Click Save and then Start to begin the syncing of Users. 8. Troubleshooting If troubleshooting is required, examine the following logs: All Events - In Security Expert under Monitoring > Status Page View, open the All Events view to view Data Sync Service events. Event Viewer - Open the Windows Event Viewer and navigate to Event Viewer > Applications and Services Logs > Schneider Electric Security Expert event log.

Issue Users want to configure an ACX57xx controller to use its RS-485 Infinet communication port to connect to a Netcontroller as an Infinet device, similar to older ACX781 controllers. Product Line Andover Continuum Environment ACX5720 ACX5740 Cause The ACX57xx was designed to replace and improve upon the ACX781, requiring higher bandwidth for enhanced features such as: Increased memory Faster processor Larger personnel storage Secure communications The Ethernet LAN provides this bandwidth, whereas the Infinet network would create a significant bottleneck. Resolution The RS-485 port on ACX57xx can be configured for Infinet communications only to add subnet controllers off the ACX57xx. It cannot be configured to communicate directly on the Infinet network as a slave device. For full functionality and performance, the ACX57xx must connect via Ethernet LAN.

Issue After creating an output point on an XPD02 expansion module connected to a BCX controller, the output does not function. The CPU LED on the XPD02 remains solid ON. Product Line Andover Continuum Environment XPD02 Expansion Module BCX Controller Continuum system with expansion modules Cause The XPD02 was connected to the BCX while the system was powered, which can cause communication or initialization issues. Resolution Reload the BCX controller to reinitialize communication with the XPD02.