Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
Options
  • My Knowledge Base Contributions
  • Subscribe
  • Bookmark
  • Invite a Friend
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
Labels
Top Labels
  • Alphabetical
  • Andover Continuum 2,209
  • TAC Vista 2,045
  • EcoStruxure Building Operation 1,840
  • TAC IA Series 1,823
  • TAC INET 1,458
  • Field Devices 721
  • Satchwell BAS & Sigma 474
  • EcoStruxure Security Expert 329
  • Satchwell MicroNet 252
  • EcoStruxure Building Expert 228
  • EcoStruxure Access Expert 148
  • CCTV 53
  • Project Configuration Tool 46
  • EcoStruxure Building Activate 13
  • EcoStruxure Building Advisor 12
  • ESMI Fire Detection 6
  • Automated Engineering Tool 4
  • EcoStruxure Building Data Platform 3
  • EcoStruxure Workplace Advisor 1
  • EcoStruxure for Retail - IMP 1
  • Previous
  • 1 of 2
  • Next
Top Contributors
  • Product_Support
    Product_Support
  • DavidFisher
    DavidFisher
  • Cody_Failinger
    Cody_Failinger
See More Contributors
Related Products
Thumbnail of EcoStruxure™ Building Operation
Schneider Electric
EcoStruxure™ Building Operation
4
Thumbnail of SmartX IP Controllers
Schneider Electric
SmartX IP Controllers
1
Thumbnail of EcoStruxure™ Building Advisor
Schneider Electric
EcoStruxure™ Building Advisor
1

Related Forums

  • Intelligent Devices Forum

Previous Next

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite

Building Automation Knowledge Base

Sort by:
Helpfulness
  • Date
  • Views
  • Likes
  • Helpfulness
Options
  • Subscribe
  • Bookmark
  • Invite a Friend
  • « Previous
    • 1
    • …
    • 45
    • 46
    • 47
    • …
    • 507
  • Next »

Cannot Ping, FTP or Telnet into Controller

Issue When trying to connect to a Controller via FTP or Telnet the connection is failing even with known working usernames and passwords. Cannot ping controller after upgrade to 4.3.x Product Line EcoStruxure Security Expert Environment SP-C-Web SP-C SP-ACX SP-AC1 Cause When connecting with FTP via an application such as Filezilla the error 'Bad username/password' is returned. Via Telnet the error is simply 'Logon Incorrect' and the connection once again fails to complete    Resolution FTP and Telnet have been intentionally disabled on the Controllers for Cyber Security purposes and will not be possible to use from firmware version 2.08.1234.  Please see firmware release notes version 2.08.1234. As mentioned in the Controller firmware release notes version 2.08.1018, Ping is disabled by default and can be re-enabled via Controller Commands: EnablePing = true
View full article
Admiral David_Kendrick Admiral
‎2020-10-07 03:57 AM

Last Updated: Sisko GavinHe Sisko ‎2023-09-13 08:26 AM

Labels:
  • EcoStruxure Security Expert
1517 Views

Enterprise Network Server BTL Certification

Issue Enterprise Network Server BTL Certification Environment I/A Series G3 3.6.35 BACnet Advanced Operator Workstation (B-AWS) I/A Series G3 3.6.35 BACnet Operator Workstation (B-OWS) Cause The PIC statements for the I/A Series G3 Enterprise Network Server for BACnet Advanced Operator Workstation and BACnet Operator Workstation is available from Schneider Electric. However, they are not listed on the BTL website under Schneider Electric.  Resolution Schneider Electric is focused on maintaining BTL listings for servers and controllers that are an active part of the SmartStruxure solution. There are no plans to add or renew BTL listings for products that are only supported by TAC I/A Series systems at this time. Existing listings that don't apply to SmartStruxure solution will remain on the BTL website until they expire. Schneider Electric product BTL listing can be found here.
View full article
Picard Product_Support
‎2018-09-07 11:37 AM

Labels:
  • TAC IA Series
2034 Views

Controller status not updating in "View All Hardware" window

Issue In Access Expert's 'View All Hardware' window, the status of controllers does not update. For example, controllers say 'Online' even though they are actually 'Offline' and vice versa. Live Monitoring window does not show disconnect/online events. Seq log shows error: Failed to Publish event.Moniker:MonikerItem {"Namespace":"MercuryServiceEvents","Nickname":"mercury:15-12-1"} Product Line Access Expert Environment Access Expert Premise Software Cause Enterprise Administrator group, under root, is missing permissions for Mercury service. Resolution Log into the Root instance, edit the Enterprise Administrator group, in the "Event Types" tab, make sure permission is granted to the Mercury Service and Mercury Commands
View full article
Captain AbeMeran Captain
‎2020-10-07 06:40 AM

Last Updated: Guinan RandyDavis Guinan ‎2020-10-07 06:43 AM

Labels:
  • EcoStruxure Access Expert
855 Views

Dual Power supply for automation server

Warning Hazard of Electric Shock: Remove all power from all devices before removing any covers or doors of the system. Disconnect power at the device and at the power source. Issue Need for a dual redundancy power supply for the Automation Server. Product Line EBO EcoStruxure Building Operation. Environment Building Operation Automation Server. Cause Understanding how to create a fail-safe power supply for an Automation Server.  Resolution To provide dual power redundancy to an Automation Server, a possible solution can be to use a Phaseo ABL4_ABL8RED24400. This will allow the connection of two 24V PSU's to be connected to the inputs. Then connect the output of the Phaseo ABL4_ABL8RED24400 to the AS's PS-24V See the attached document and diagram for more information.
View full article
Commander Chris_Asbury Commander
‎2020-10-02 08:12 AM

Last Updated: Guinan RandyDavis Guinan ‎2020-10-02 08:16 AM

Labels:
  • EcoStruxure Building Operation
5941 Views

Modbus IP Multiple Queries and Multiple Query Packets (Async) explanation

Issue Details on how Modbus IP Multiple Queries and Multiple Query Packets work Product Line EcoStruxure Building Operation Environment Building Operation SmartX Servers Modbus IP Cause Understanding of how the Modbus synchronous and asynchronous transport layers differ. Resolution By default, the Multiple queries is Disabled, this is the synchronous transport layer. To enable the asynchronous transport layer the Multiple queries must be Enabled within the Modbus TCP Network properties as shown below. Setting to "Enabled" allows multiple queries (packets) to be sent to multiple Modbus devices, thus reducing wait times.  It also enables further settings in the Modbus Device properties "Maximum concurrent queries" and "Multi-query packets".   The maximum concurrent queries and multiple-query packets as shown below are configurations for the Modbus asynchronous transport layer. The Maximum concurrent queries setting is only enabled if the "Multiple queries" is enabled in the Network Properties. When enabled, this allows the "concurrent queries" to be sent as a single packet.     Modbus Synchronous Transport Layer Each Modbus query is sent out one after the other. Before sending out the next query the transport layer waits for a specified period for the previous query. Example Poll Sequence Device No. Objects 1 2 2 1 D=Device, Q=Query, R=Reply D1 Q1 Send D1 R1 Receive  D2 Q1 Send D2 R1 Receive  D1 Q2 Send D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 3 seconds. Modbus Asynchronous Transport Layer With the asynchronous transport layer enabled, the queries are transmitted to multiple devices at the same time. The maximum number of queries that are transmitted to that one device is controlled by the “Maximum concurrent queries” setting. The “Multiple-query packet” specifies whether the queries are transmitted in one TCP frame or not. Simple Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 2 False 1 2 1 False 1 D=Device, Q=Query, R=Reply D1 Q1 Send D2 Q1 Send D1 Q2 Send D1 R1 Receive  D2 R1 Receive  D1 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 1 second Complex Example Poll Sequence Device No. Objects Multiple-query packet Maximum concurrent queries 1 10 True 5 2 4 False 2 D=Device, Q=Query, R=Reply D1 Q1, Q2, Q3, Q4, Q5 Send D2 Q1 Send D2 Q2 Send D1 R1, R2, R3, R4, R5 Receive  D2 R1 Receive  D2 R2 Receive  D1 Q6, Q7, Q8, Q9, Q10 Send D2 Q3 Send D2 Q4 Send D1 R6, R7, R8, R9, R10 Receive  D2 R1 Receive  D2 R2 Receive  If it takes 1 second for the device to reply, then this sequence would take 2 seconds   NOTES The use of this feature should be avoided before EBO v3.1, there is also a defect in EBO v3.2 that means v3.2.3.5000 should be used (minimum) Some Modbus devices do not support multiple queries or multiple query packets, so the feature should be tested on an individual basis. (Some devices may even go offline until manually reset) This feature will increase the CPU usage on the EBO server. It should be avoided on EBO Servers that are already heavily loaded This feature also has the ability to reduce the system stability, it is usually better to optimize the use of Modbus Register Groups to increase performance
View full article
Guinan RobertAndriolo Guinan
‎2020-11-11 03:47 AM

Last Updated: Sisko DavidChild Sisko ‎2022-03-23 08:30 AM

Labels:
  • EcoStruxure Building Operation
2991 Views

Unable to connect to detected RPCs using the Engage app

Issue Unable to connect to the detected RPCs using Engage app v1.2.1 or later and RPC 3.02.01 Product Line EcoStruxure Building Operation Environment Building Operation Room Controller (RPC) (all types) v3.02.01 Building Operation Engage Application Cause EFR32 BLE chip needs to be upgraded to fw3.01.00.00012 but looking at the device report you see there is a Failure to upgrade EFR32 error. Resolution From workstation open the control panel and select the Firmware upgrade view. Right-click the RPC from the list of available SmartX controllers > Device> Upgrade Firmware>Select Device Firmware Select 3.01.02.00046 Firmware package Wait for the RPC to fully upgrade and return to an online state before going to the next step. This may take 6 to 9 mins which is normal. Right-click the RPC from the list of available SmartX controllers > Device> Upgrade Firmware>Select Device Firmware Select 3.02.01.00247 Firmware package Wait for the RPC to fully upgrade and return to an online state before going to the next step. This may take 6 to 9 mins which is normal Once the RPC is online Right Click the RPC > Device> Download All Objects If not upgraded in this order, the Bluetooth Chip isn't correctly upgraded and will fail.    
View full article
Commander JonGreen Commander
‎2020-10-02 10:36 AM

on ‎2020-10-02 10:36 AM

Labels:
  • EcoStruxure Building Operation
1571 Views

License Administrator fails install on uninstall process

Issue License Administrator fails install with an "Uninstall failed, installer cannot continue" error Product Line EcoStruxure Building Operation Environment Building Operation License Administrator Cause Building Operation uses Flexera (Revenera) Software Technology for licensing. Other Schneider-Electric products may also use this technology for their licensing. Resolution Check to see if the site has other software programs/products using the Flexera (Revenera) Software Technology. Other Schneider Electric offers such as Unity Pro - IEC Programming Software for Modicon PAC, Power Monitoring Expert & TAC Vista as well as third party programs also use Flexera (Revenera) for their licensing. During installation of the Building Operation License Administrator the dialog below is shown: The default behavior of the Building Operation License Administrator installation program is to install both Building Operation License Administrator and a new local license server instance. If the default behavior is accepted, the installation program will attempt to uninstall any previously installed local license servers. If the Building Operation License Administrator installation program  does not have sufficient access rights to uninstall the license server previously installed by another product a "Failed to install Building Operation License Administrator" error will occur.   Multiple products can share a single Flexnet License server instance. If there is an existing Flexnet install then the License Server checkbox should be unchecked during installation of the Building Operation License Administrator This leaves the existing local license server installed by the other product intact, while still allowing Building Operation License Administrator to run. The license server used by Building Operation License Administrator can easily be changed by the user on the License Server Address tab in Building Operation License Administrator, if necessary.  
View full article
Picard Product_Support
‎2018-09-06 10:05 AM

Last Updated: Administrator CraigEl Administrator ‎2023-09-21 04:47 PM

Labels:
  • EcoStruxure Building Operation
2023 Views

EH Series Humidity Sensors

Issue The specifications and setup details of the EH series humidity sensors. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, TAC IA Series, TAC INET, TAC Vista Environment Humidity Sensor Cause The EH Series Room, Duct and Outside humidity sensors are a universal Relative Humidity transmitter that can be powered with either a +15 to 36 Vdc or 24 Vac supply voltage. The EH series sensors are designed with a field selectable 4-20 mA, 0-5 Vdc, or 0-10 Vdc output signal that is equivalent to 0 to 100% RH. The EH Series is used in building automation system, humidity chambers, and OEM applications and is compatible with Vista, Continuum, I/Net, I/A, and SmartStruxure systems. Resolution EH Series Humidity Sensors Click the below links to look at the documentation for these sensors including the dip switch settings. EH Series Humidity Sensor Data Sheet EH Series Humidity Sensor Installation and Operation Instructions Old EH Series Humidity Model For information on the older style of dip switches (models with two separate sets of dip switches), see the document below. Old EH Series Humidity Sensor Installation and Operation Instructions
View full article
Picard Product_Support
‎2018-09-06 10:02 AM

Last Updated: Commander JonGreen Commander ‎2022-02-28 11:54 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
  • Field Devices
  • TAC IA Series
  • TAC INET
  • TAC Vista
8925 Views

A Door configured with Magstrike status as Door Status re-locks after 2s even when Door Strike Time is set to 10s.

Issue A Door configured with Magstrike status as Door Status re-locks after 2s  even when Door Strike Time is set to 10s. Environment Continuum Access Control Cause The Door output will relock after the Door Strike Time or when the Door is opened. Since you are using the mag lock status as the Door status (not the preferred method), then as soon as the Door is unlocked, the mag lock is de-energized which turns off the Door Status which then relocks the Door 1s later. Resolution You need to monitor the actual physical status of the Door to indicate when it has physically opened and shut. Either that or remove the input from the Door object by setting the Door Status channel to 0. This should allow the Door to stay open the DoorStrikeTime. You can also use a PE program to get around not having a DoorStatus that monitors the actual Door. This post on the Community discusses this and has some good comments about using this type of Door control with the maglock status instead of a true Door Status switch and is worth a read. Below is an example Plain English program that can help monitor the Door for ValidAccess then hold the Door unlocked for the DoorStrikeTime. 1: If Door1 ValidAccess is On then Goto 2 If Door1 ExitRequest is On then Goto 2 2: Door1 = UnLocked If TS > Door1 DoorStrikeTime then Goto 3 ' wait for DoorStrikeTime 3: Door1 = Locked Goto 1
View full article
Picard Product_Support
‎2018-09-11 05:50 PM

Last Updated: Administrator CraigEl Administrator ‎2022-08-08 09:00 PM

Labels:
  • Andover Continuum
1983 Views

Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate with SmartStruxure

Issue Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate with EBO Script programming Product Line EcoStruxure Building Operation Environment b3 Infinet Building Operation Server Script Programming Cause Some attributes used within Continuum PE programs on b3/i2 controllers are no longer appropriate or cannot be used with EBO Resolution An example of this would be the ElecValue attribute for an input or output. This can be used within the Conversion field of an input but cannot be used within a Script Program or Script Function. The Continuum example PE program for an STR502 or STR504 includes the line "If STR5xx ElecValue <= 0 then Return Upper" The correct result can be obtained within SmartStruxure by dropping the "ElecValue", so "If STR5xx <= 0 then Return Upper" Then ensure the STR5xx analog input is a Voltage type with no conversion configured. Note: The ElecValue keyword can still be used in the Conversion line of an Analog Inputs (e.g. for Counter input scaling). Some other Attributes not supported in Script Programming are: Size LogType
View full article
Picard Product_Support
‎2018-09-06 10:00 AM

Last Updated: Administrator CraigEl Administrator ‎2023-09-11 01:45 AM

Labels:
  • Andover Continuum
  • EcoStruxure Building Operation
1788 Views

Cannot bring b3 controllers online after replacing BCX controller.

Issue After replacing the BCX controller cannot bring b3 controllers online. Environment Node Count BCX4040 b3 Cause BCX was enabled for only 8 MSTP nodes. Resolution Replaced BCX with a 127 node BCX.
View full article
Picard Product_Support
‎2018-09-06 09:59 AM

Labels:
  • Andover Continuum
1047 Views

Basic Modbus RTU configuration to read a register from PM800 Power Meter.

Issue Basic Modbus RTU configuration to read a register from PM800 Power Meter. Product Line EcoStruxure Building Operation Environment Automation Server Modbus RTU PM800 Power Meter Cause Integrate power meters to a Building Operation front end for the user to view data and trend logs. Resolution Here are the steps to Configure a ModBus RTU interface in Building Operation to read the Line Voltage register from a PM800 Power Meter. (Assuming meter has already been properly wired to one of the serial ports on the AS) Create the Modbus Interface, in this case a Modbus Master Network.   Link the interface to a serial port in the AS in the Port Reference field, in this example to RTU device is wired to RS485-COMB   2. Under the interface create the RTU device. In this example the device id is 11, enter the appropriate id for the device. Once the device object is saved, the status should show 'Online' unless there is a communications issue. This is provided you have the online poll interval set. If this is disabled the device will stay offline until a Modbus register is polled and a valid response is received.    You can confirm that Building Operation is able to correctly detect the communications status of the device by disconnecting it from the commport and observing the status change to 'Offline', upon re-connection the status should once again display 'Online'   3. Under the device create a Modbus Point of type AnalogInput to get the value of the Line Voltage from the device. According to the documentation for the PM800 the register holding the line voltage is Function Code 3  and register  1124 The value of the point should now correspond to the line voltage in this case 125 volts.
View full article
Picard Product_Support
‎2018-09-07 08:48 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-30 06:38 AM

Labels:
  • EcoStruxure Building Operation
4376 Views

How to calculate storage used by Extended Trend Logs

Issue A site is required to store Extended Trend Log historical data for an extended period of time, in order to make sure the system has enough capacity for all the data  it is necessary to calculate the storage needed ahead of time Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Workstation Cause Understanding the storage requirements for long term trend storage Resolution Formula to calculate the storage capacity needed for Extended Trend Log data. Storage in bytes (S)  = Number Of Records (N) x 70 bytes. EXAMPLE: Consider a trend log of 1000 records with a 10-minute interval, if the requirement is to keep 5 years of data, how much storage capacity will be required? The number of records would (N)  be... 6 records per hour times 24 hours per day times 365 days per year*** times 5 years (*** leap years must be taken into account) N =  6 X 24 X 365 X 5 = 262800 bytes This equates to: S = N X 70 S = 262800 X 70 S = 18396000 bytes or approximately 18 megabytes   Note - The calculations above are for the native SQLite database used by EBO. There are two alternatives to using the ES database for long-term trend storage. Report Server - See the WebReports Database Usage Calculator Knowledge base article for storage calculations External Log Storage is possible from EBO v3.0 using TimescaleDB database - The EBO External Log Storage Installer tool from the community provides a databases size estimator located under the Tools menu item
View full article
Picard Product_Support
‎2018-09-06 09:59 AM

Last Updated: Guinan RobertAndriolo Guinan ‎2022-01-11 05:07 PM

Labels:
  • EcoStruxure Building Operation
4738 Views

Frequency used on SmartStruxure Lite SE7000 controller Zigbee communication

Issue Which frequency is used by the Zigbee wireless communication protocol used in the SmartStruxure Lite? Product Line EcoStruxure Building Expert Environment SmartStruxure Lite SE7000 Zigbee Cause 2 different versions of Zigbee (W and P) are used, depending on generation of product. Resolution   W and P are using the same layer IEEE 802.15.4 at 2.4 GHz frequency, only the "language" is different. (they can't talk to each other) For more information and details on the different Zigbee protocols, please see: Zigbee on Wikipedia Zigbee Alliance
View full article
Picard Product_Support
‎2018-09-11 08:28 AM

Labels:
  • EcoStruxure Building Expert
1262 Views

BACnet device can't be discovered due to duplicate name

Issue BACnet device can't be discovered but instead shows up under the 'Unconfigured devices' in the server's hardware folder. Product Line EcoStruxure Building Operation Environment WorkStation Enterprise Server - ES Automation Server - AS Cause A BACnet device name must be unique. Devices with duplicate BACnet names can't be discovered. In the screen shot below a device by the name AbesbCX already exists under Network1, when performing a device discovery on Network1 a second device with the same name is found, Since StruxureWare already has a device with the same name it adds the device to the list of unconfigurable devices. NOTE: “The <<N>> means the device was discovered on a directly connected network (such as the local IP network, or a directly connected MSTP bus).  The 2 indicates it was “port” 2, (port numbers are really an internal detail) The server's Trace Log shows the following information, which includes the device's ID. The entry gives the reason as duplicate device name. Resolution 1.8.1 and above BACnet device name duplication is allowed, the duplicates will still land in the unconfigured folder and the system alarm will be generated BUT you can drag the duplicate device from the unconfigured folder to the desired network. When finished, manually delete the device from the unconfigured/non-conformant folder. Alternatively, you can also  warm start the server to force the unconfigured/non-conformant devices list to be updated. Note that the devices with duplicate names will still stay in the unconfigured/non-conformant folder until the name conflict is resolved. 1.7.2 and below A workaround is to create the device manually and specify a BACnet name during the create process. When manually creating the device you need to know the Device ID, you can get the id from the information in the trace log as shown above. SmartStruxure will send a message to the device to change its name to the specified BACnet name. The entry in the unconfigured devices folder should automatically update after a few minutes, you can also re-start the server to force the unconfigured devices list to be updated, the entry for AbesBCX should be gone now that the devices has been manually configured.
View full article
Picard Product_Support
‎2018-09-07 08:51 AM

Labels:
  • EcoStruxure Building Operation
7122 Views

Subscriptions using BACnet

Issue What is the BACnet point data refresh rate and how is the rate changed? Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation AS-P and AS-B Cause Subscriptions are the connection between the value from the BACnet Interface point to the value on the ES or AS. Resolution These subscriptions can be edited using the Binding of the value. Using 1.4, edit the configuration of the Binding as shown below: Here, the default 10 seconds interval in the Requested Transfer Rate can be changed. The default is 10 seconds. This allows changing the default interval of 10 seconds down to a minimum 100 milliseconds a maximum 24 hours:  Using 1.3: Edit the configuration of the Binding as shown below:  Here the default 10 seconds interval in the Requested Transfer Rate can be changed. The default is 10 seconds.
View full article
Picard Product_Support
‎2018-09-07 08:51 AM

Labels:
  • EcoStruxure Building Operation
2372 Views

BACnet COV subscription system COV Settings

Issue BACnet COV subscription system Product Line EcoStruxure Building Operation Environment BACnet Settings COV subscriptions v1.7 and earlier Cause A site will have a problem with the amount of traffic because of misconfigured COV Increments. The problem is that Building Operation, the  ES and AS resubscribes to values every 10 seconds and one by one. So for example: hh:mm:ss 00:00:00 Value1 00:00:10 Value2 00:00:20 Value3 00:00:30 Value4 ... 05:00:00 Value1800 If you have more than 1800 subscriptions the ES or AS is not able to do all subscriptions in 5 hours.   5 hours is used because Building Operation subscribes to the values with a lifetime of 5 hours.   Resolution BACnet COV subscription system is not influenced by the requested transfer rate in the edit bindings system (Subscriptions using BACnet). That is used in the case where the external device does not support COV, and read-property must be used instead. The design in 1.4 and 1.5 simply did not anticipate such large numbers of COV subscriptions. Workaround: 1.Exit Workstation 2. Stop the Enterprise Server Edit using notepad the server.properties file located in "C:\Program Files\Schneider Electric StruxureWare\Building Operation 1.x\Enterprise Server\etc\ Find at the bottom: # Set GenericConsume communication defaults Add the two following lines: NspServer.BACnetPlugIn.COVSubscriptionLifetime entry = 28800 NspServer.BACnetPlugIn.COVTimerPeriod entry = 5 Save your changes and close the server.properties file. This changes the default values from 5 hours to 8 hours and 10 seconds to 5 seconds. NOTE From version 1.8 the BACnet Interface manager (/Server 1/System/Interface Manager/BACnet) provides access to these settings (COV subscription lifetime (default 8 hours) and Server COV renew rate(default 5 seconds)) The settings will be controlled via the Enterprise Server if connected.
View full article
Picard Product_Support
‎2018-09-07 11:20 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-07 11:58 PM

Labels:
  • EcoStruxure Building Operation
6015 Views

Extended Trend logs stop updating on the Enterprise Server

Issue Extended Logs have stopped updating on the Enterprise Server. Product Line EcoStruxure Building Operation Environment Extended Trend Logs Cause Extended Trend logs have been set up on the site for some time and have operated correctly. Now some of them have stopped updating.  Resolution This issue can be caused by a Server backup being restored. Trend logs and Extended Trend logs are allocated sequence numbers, and if the sequence numbers do not follow the correct sequence, the Extended Trend log may not update. To confirm that this is the issue; Trend Log. Navigate to the Trend log and open it in a "Trend Log List" view. Add an additional column to show the Sequence number. Note the highest sequence number used. Extended Trend Log. Navigate to the Extended Trend log that is referencing the above Trend Log. Open it in a Extended Trend Log properties. Press and hold down the "ALT" key and click where the dot is indicated on the screen shot below, (just below the Basic tab).       This will show some more properties for the Extended Trend Log, the one you are interested in is “Last transferred sequence number”.   If the last transferred sequence number on the Extended Trend Log is higher than the Trend log’s highest sequence number, then that is why the Extended Trend Log has stopped. How can this issue be resolved? Increase the sample interval of the Trend log until it has caught up. The Extended Trend Log will only fetch new records that has a sequence number higher than the last transferred sequence number. So until the sequence has caught up, you will not see any new records in the Extended Trend Log, and only records created after you have caught up in sequence numbers will be fetched. Re-create the Extended Trend Log. The new Extended Trend Log will fetch every record the log has and continue from there, but you will lose the records the old Extended Trend Log had that the log does not have anymore. Backup / restore on the AS. The Trend log will be cleared but the Extended Trend Log will start fetching new records.    
View full article
Picard Product_Support
‎2018-09-07 08:52 AM

Last Updated: Sisko GavinHe Sisko ‎2022-11-18 05:15 AM

Labels:
  • EcoStruxure Building Operation
1964 Views

What graphics formats can be imported into a TGML graphic?

Issue What image formats are supported in a TGML graphic? Product Line EcoStruxure Building Operation Environment EcoStruxure ES, AS Vista Graphic Editor Cause Clarification of supported graphic formats required. Resolution When inserting a picture in a TGML graphic you can select the image file from the following file types: Bitmap, GIF, ICO, JPEG, Metafiles, PNG, TIFF  
View full article
Picard Product_Support
‎2018-09-07 08:53 AM

Last Updated: Captain SharlinaRe Captain ‎2022-09-07 08:33 AM

Labels:
  • EcoStruxure Building Operation
  • TAC Vista
3850 Views

Using Sysman Alert Server with EcoStruxure Building Operation

Issue Is it possible to use Sysman Alert Server with EcoStruxure Building Operation? Product Line EcoStruxure Building Operation Environment Alarms and Events Cause Customers may wish to send important alarms to duty staff via SMS. Sysman Alert Server is one way of doing this and is easy to configure.  Resolution This is possible. The following document details the setup procedure: Sysman Alert Server with StruxureWare Building Operation The configuration will depend on the setup and location of the SysMan Server, but will generally involve "Write to File" Notifications if the Enterprise Server and Sysman Servers are installed on the same PC, or Emails to the SysMan Server (from Enterprise or Automation Server) More information can be found on Sysman's website. Part Numbers: SysManSMS ALERT SERVER: 900800600 SysManSMS GSM Modem: 900800610 In the UK when ordering please use the below part numbers. SysManSMS ALERT SERVER: 802000 SysManSMS GSM Modem: 100002
View full article
Picard Product_Support
‎2018-09-11 06:17 AM

Labels:
  • EcoStruxure Building Operation
5620 Views
  • « Previous
    • 1
    • …
    • 45
    • 46
    • 47
    • …
    • 507
  • Next »
To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of