Issue How can thousands of unacknowledged alarms and exceptions be deleted quickly in SIGNAL? Environment SIGNAL (all versions) Cause Months of unacknowledged alarms and exceptions were allowed to accumulate. Resolution The files containing all the alarms and exceptions are located in the SIGNAL\ALARM and SIGNAL\EXCEPT folders respectively. Shutdown SIGNAL (all programs).  In the ALARM folder, delete the alarm_a.dat, alarm_u.dat, and alarm_l.num files. In the EXCEPT folder, delete the excep_a.dat, except_u.dat, and excep_l.num files. Reboot the computer.

Issue   A site has multiple locations in its instance. The goal is to restrict objects for a User in other locations by using permissions and tags which allow certain objects only for the local instance. The User also requires access to Event History, Live Monitoring and Floor plans.   After setting User permissions for specific objects, the object permissions work as expected, however clicking on Event History, Live Monitoring or a Floor plan shows: 'An error has occurred in the Live monitoring document while trying to execute initialize' Or Access Expert will show one of the following errors depending on which event object was selected: 'An error has occurred in the Event History document while trying to execute initialize' 'An error has occurred in the Floor Plan document while trying to execute initialize'   Product Line EcoStruxure Access Expert Environment Access Expert V3 Hosted Cause Event-level permissions function differently than object-level permissions Resolution User permissions set up with tags to restrict access to other locations will work as expected with objects like hardware, but these restrictions will not work with event objects.   The options to accomplish this are: 1. Buy an enterprise license and divide up the sites with their own instance. Each location should be represented by a shared instance with its controllers configured. Those controllers will publish their event to only their instances which can be controlled using permissions. This is the preferred method.   2. Allow ALL Type permissions for the hardware and event objects to be accessed. Using this method allows the event objects to work, but allows Users from other locations to access the hardware.   Event-level objects use an entirely different mechanism than regular objects. The technology under the hood requires that an enterprise license be used to accomplish event-level permission restrictions.

Issue The status of a Lon binding states locked.  How can it be changed to bound?    Environment R2, WorkPlace Pro Cause Binding is locked. This can be done at the time the node is learned or a network variable can be locked on the property sheet of the node. Resolution The Network Variable bound to the link will have to be unlocked to change the link to bound. Open the device property sheet that’s associated to the locked link Select the device tab and LonProps tab. Select and expanded the Snvt that’s associated with the locked link Unselect “Locked” and click Apply. Open LonDeviceManager under LonWorkService Highlight the device and select UpLoad Check boxes: “Upload binding info”, “Add links” and “Upload config data” and click Apply - DO NOT check “Lock existing bindings”   The link status now read bound.

Issue How long will a UNC-520 hold the date & time if AC power and the backup battery are disconnected? How long will a UNC-520 hold the date & time if AC power is disconnected but the backup battery remains connected? Environment UNC-520 Universal Network Controller Cause UNC-520 provide real-time clock and need to maintain the information during power failures. Resolution Approximately one hour. This is done by a 1200 µF 10 Vdc capacitor that backs up the real-time clock chip. Over one month.

Issue Why do the Architectural Guidelines specify a maximum of 1500 Extended Trend Logs in Automation Servers, whereas such a limitation did not exist with the Continuum Net Controllers, like the NetController II.   Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause EcoStruxure Building Operation's architectural guidelines specify a limit of 1500 Extended Trend Logs for the Automation Servers (AS-P/AS-B). Sites transitioning from Andover Continuum to EcoStruxure Building Operation need to understand the architectural differences that necessitate this limit. Resolution The architectural differences between Continuum and EcoStruxure Building Operation means that it is crucial that Extended Trend Logs are managed effectively to ensure ensuring optimal system performance.   In Continuum: Controller Role: Controllers do not participate in Extended Trend Log functionality beyond sending data from intrinsic logs upon request from Cyberstations. Log Management: Extended Trend Logs reside at and are managed by Cyberstations. Load Distribution: Multiple Cyberstations, configured to collaborate, maintain the Extended Trend Logs, minimizing the load on controllers.     This design puts very little load on the controllers when it comes to Extended Trend Log functionality.   In EcoStruxure Building Operation: Distributed Database Architecture: Extended Trend Logs are managed by the AS-P/AS-B servers. Server Load: The server performs tasks typically handled by multiple Cyberstations in Continuum, which often run on more powerful PC hardware. Performance Management: To prevent Extended Trend Log servicing from overwhelming the Automation Server's resources (CPU, memory), a limit of 1500 logs is enforced. Exceeding this limit can degrade server performance and potentially cause reboots due to critical memory usage.  This can be seen in the following example trace log entry: Nov 30 15:39:58 PSS-AS02 memcritsv[1011]: Memory usage critical!    

Issue Replacement required for obsolete product. Environment SPD160 004700180 SPD360 004700360 Cause Replacement for obsolete product. Resolution SPD160 is replaced by SPD360. For more information ad details, please see the data sheet for each product.

Issue What is the supported DC voltage on Xenta controllers? Environment Xenta controllers Cause DC Voltage is available for power. Resolution The table below list the supported Voltage DC specifications for Xenta controllers For more information check Data sheets for Xenta controllers located on The Exchange.   Xenta Controller Volt DC Support 411 19-40Vdc 421 21.6-40Vdc 451 21.6-40Vdc 471 19-40Vdc 491 19-40Vdc 400 Series 19-40Vdc 300 Series 19-40Vdc 200 Series 19-40Vdc 500 Series 19-40Vdc 700 Series 19-40Vdc 900Series 19-40Vdc 101 No Vdc Support 102 No Vdc Support 103 No Vdc Support 104 No Vdc Support 120 series No Vdc Support

Issue What is the switching level resistance for a digital input to be seen as 1 in a Xenta 411/412 I/O modules Environment Xenta 411/12 Cause Integrating third party devices with Xenta 411/412 I/O modules. Resolution The switching level resistance for a digital input to be seen as 1 in a Xenta 411/12 is around 2000ohm

Issue The Enterprise Network Server is licensed for 3 subordinates but when trying to add one it faults with the message "exceeded device limit of three"? Environment G3 Enterprise Network Sever Cause If stations had been added to the Niagara Network in the Enterprise Network Server and then deleted the subordinate count in the license does not reset. Resolution Restart the station and the subordinate count in the license will be reset to the correct number and allow the addition of more stations if the limit has not been reached.

Issue How do I reset the view of the System Plug-In  to the original look. Environment System Plug-In Cause They folder pane has been modified and now the default layout is required. Resolution A reset to default will be required to get the original settings These steps will reset the view to default Open the System Plug-In Under the file menu select Default Settings A message will appear that "The command requires a restart to take effect." Shut down the System Plug-In Restart the System Plug-In  with the original default setting is applied

Issue With the same time interval as the trend log, the traffic on the LonWorks network increases for a short period. This can be seen by a spike in the LPA log when viewing the bandwidth. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Lonworks Cause The LonWorks traffic increases with the same time interval as the trend log. Resolution To ensure we could log values in the trend log from a LonWorks device, a subscription is set up about 30 seconds before the value should be logged. After the value is logged, the subscription is removed until the next log interval. A good solution to flatten a spike caused by this issue is to stagger the times of the LonWorks trend logs. This will ensure the subscription for all the logs do not happen at the same time.

Issue When using Project Configuration Tool (PCT) in Server mode and connecting from a remote PCT client, it is not possible to transfer backups or exports. The transfer gets stuck, and a complete reboot is required to start using the project again. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause In the "Settings for Project Configuration Tool" the Notification and Listening port defaults to 0. Port 0 means that PCT will ask the OS for an available port. But if network policies prevent PCT from communicating using that port, PCT cannot detect that.  Resolution In "Settings for Project Configuration Tool" Change the port number for the Notification port and Listening port to a port that is available to use.

Issue Xenta 102-B nviManOverride allows for flow or percentage overrides. But since this controller is intended to be used along with a Belimo flow controller/actuator, how do these modes of operation differ? Environment Xenta 102-B Cause Flow control is not actually an option for this controller. Flow values will be interpreted as desired percentages of airflow. Resolution nviManOverride.state = HVO_PERCENT, nviManOverride.percent = 35% The controller fixes the Airflow output (Y1) at 35% (3.5V) nviManOverride.state= HVO_FLOW_VALUE All of the flow values are actually being treated as percentages ... there is no way to set it to a desired flow. (nviManOverride.flow X nciNomFlow / 100) is limited to 0-100% and sent to the Airflow output (Y1). Emergency Override can override these setting, as can setting the controller to slave mode (the overrides would have to be performed on the master controller in that setting). The way to release these states is to set the nviManOverride.state to any value other than HVO_PERCENT or HVO_FLOW_VALUE. Those are the only two values accounted for in the logic.

Issue The setpoint values are displayed briefly and then change to 621.X on the Proview display? Environment All LON proview installations. Cause This occurs when the setpoints are being written into network variable inputs (nvi).  The nvi's default to using the receive heartbeat and will fallback to default after the timeout occurs.  Proview does not perform a send heartbeat function as the connection is an nv update and not an actual binding. The receive heartbeat mechanism in the MNL controllers cause the nvi values to fallback to NA upon heartbeat timeout. Resolution The heartbeat can be disabled for the setpoint nvi, however nvi values are stored in RAM (not EEPROM) and will return to default upon a controller power cycle.  The best solution is to use network configuration inputs (nci) for setpoint displays on the Proview.  These do not have the heartbeat issue and the values are maintained in EEPROM so they are not lost following a controller power cycle.

Issue  Temporary groups can't get a PM time, only AM Environment I/NET Cause The time are using US settings AM/PM on for example a European PC Windows don't use AM/PM Resolution Enter Control Panel and choose Regional and Language Settings On first tab click Customize Choose tab "Time"  Set AM and PM symbol to AM and PM Click OK Restart I/NET IO server and try again.

Issue ZBuilder will not open on certain commissioned Xenta 121s in Lonmaker. It will open on others in the same network. Environment ZBuilder LonMaker Cause Incorrect or corrupted configuration parameters prevent the ZBuilder plug-in from opening on specific Xenta 121s. Resolution Right-click on the device in LonMaker and choose Browse Take a screen capture of the various settings that will need to be re-entered Re-commission the Xenta 121 controller with default values (this will erase any configurations that have been made) ZBuilder will now work correctly. Re-enter any previously configured parameters

Issue Only one of the readers on a 7920 DPU works Environment 7920 DPU Cause If you have defined one door in the DPU 7920, and the door’s Exit Reader parameter is set to anything other than "NO," then the second reader port automatically becomes the exit reader. Resolution If you have defined two doors in a DPU 7920, neither door can have an Exit Reader defined.

Issue Can the MNL controllers be powered by DC voltage? Environment MNL controllers DC voltage input Cause Using DC voltage is not recommended or supported. Resolution The MNL controllers are not specified for DC operation and all agency approvals were submitted using a power source of 24 VAC 50/60 Hz.

Issue How to create a local String Variable in a Xenta 731. Data Type String is not allowed in this node. When trying to set data type to string. Environment TAC Xbuilder Cause The datatype string can only be used for SNVT str_asc and signals connected to SNVTs of this type. Resolution To get a String signal you have to use snvt_str_asc.

Issue There is a need to identify the Ports and URLs which must be open through the customer's firewall and network security for EcoStruxure Building Activate Product Line EcoStruxure Building Activate Environment EcoStruxure Building Activate Flex Server EcoStruxure Building Activate Partner Portal Cause To ensure the Flex Server operates correctly, specific URLs must be whitelisted within the customer's firewall and network security settings. Resolution Below is the list of URLs which must be open through a site's firewall/network: Domain Name Protocol Description telemetry.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Used for sending IoT Sensor Data streams. mender.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Used to download firmware update. emqx.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Used for communication of Flex-Server with Schneider Electric cloud services such as configuration, data, or alarms. openvpn.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Allows Schneider Electric to remotely access the Flex- Server through VPN. timesync.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Time server allows the Flex- Server clock to remain synchronized. router.ecostruxure-buildingactivate. se.app HTTPS (TCP port 443) Allows the Flex-Server to download linux updates   Note: For the list of URLs to be whitelisted for the India Portal, please refer to Required list of URLs/Ports to be whitelisted under firewall/network for EcoStruxure Building Activate (India Only)