Important Announcement: Community Back to Full Functionality
Dear Members, we are thrilled to announce that our Community is back to full functionality and that posts publication is now enabled again! We appreciate your patience during the last weeks. Learn more about our Community Guidelines. Thank you, Schneider Electric Community Team.
Building Automation Knowledge Base
Access this self-service resource 24/7 and post your questions or scroll through forums for answers on building automation.
When accessing http://help.sbo.schneider-electric.com you get an message saying "This topic contains privileged information" even though you should have access.
EcoStruxure Building Operation
Building Operation WebHelp
The access right associated with the credential you log in with, does not allow you to view the topic you are attempting to view.
The access right for the StruxureWare Building Operation help pages are handled by the Buildings Exchange team.
Send an email to the team regarding issues with the WebHelp platform, and include as much information as possible. It is mandatory to include which email address you log in with, and what page and/or information you are trying to access: ExchangeSupport@schneider-electric.com
In the TAC Xenta 151-D, the nvoAlarmStatus handles the test of the dampers, but the translation of the status is not documented
TAC Xenta 151-D
nvoAlarmStatusis used to report the actual status of the fire damper tests.
nvoAlarmStatus is a SNVT_state with the use of the following bits:
nvoAlarmStatus.bit0 = 1 OBJECT1_CLOSE_TIME_TOO_LONG
nvoAlarmStatus.bit1 = 1 OBJECT1_CLOSE_TIME_TOO_SHORT
nvoAlarmStatus.bit2 = 1 OBJECT1_OPEN_TIME_TOO_LONG
nvoAlarmStatus.bit3 = 1 OBJECT1_OPEN_TIME_TOO_SHORT
nvoAlarmStatus.bit4 = 1 OBJECT2_CLOSE_TIME_TOO_LONG
nvoAlarmStatus.bit5 = 1 OBJECT2_CLOSE_TIME_TOO_SHORT
nvoAlarmStatus.bit6 = 1 OBJECT2_OPEN_TIME_TOO_LONG
nvoAlarmStatus.bit7 = 1 OBJECT2_OPEN_TIME_TOO_SHORT
nvoAlarmStatus.bit8 = 1 OBJECT1_SET_CLOSE_TIME_FAILED
nvoAlarmStatus.bit9 = 1 OBJECT1_SET_SELFTEST_OK
nvoAlarmStatus.bit10 = 1 OBJECT1_SET_SELFTEST_FAILED
nvoAlarmStatus.bit11 = 1 OBJECT2_SET_CLOSE_TIME_FAILED
nvoAlarmStatus.bit12 = 1 OBJECT2_SET_SELFTEST_OK
nvoAlarmStatus.bit13 = 1 OBJECT2_SET_SELFTEST_FAILED
It is desired to configure a minimum off time, so when the compressor stops in e.g. heating mode, it will not start again before a minimum time has elapsed in the same mode.
This setting is not available in the device.
TAC Xenta 121-HP
There is no setting for minimum stop time when in the same mode, there is only a minimum stop time between modes.
As a workaround, set the "Activate at" value to something other than zero (say 10%), so that you can use the "Hysteresis" at 10%, and this way get a delay.
This way you will get a delay in the most cases, a little time before the controller reacts.
Email alarming is configured correctly but Continuum keeps crashing when alarms are sent as emails. ACCDataServices is the crashing module.
Windows Application log shows two email errors that point to an issue with Outlook.
Email, Failed to send email - SendNote in Send function failed. Result is 80070057.
Email, Failed to send email - SubmitMessage failed in CSession::SendNote, Result is 80070057
Outlook account folder is too large and does not have available space for new entries. In this case the folder was 7GB in size with emails going back eight years.
Archive Outlook account folder and truncate to free up space for new emails.
With the Personnel Import Utility, is it possible to query multiple OU containers?
Personnel Import Utility (PIU)
Need to be able to query multiple OU containers. Similar to below query.
Server Name: LDAP://test/DC=test, DC=com
(test and com are separate domains)
Unfortunately the query cannot be changed to accommodate this. Different Domains can be specified but it is not possible to go down to the OU level.
Can the Personnel Import Utility update existing Personnel only and not create new Personnel objects if they do not already exist?
Personnel Import Utility
Need to be able to only modify existing Personnel and not create new ones when performing Personnel import with the PIU.
The way the PIU handles this, to modify existing Personnel or if none exists to create a new one, is "functions as designed". There is no way to stop a new Personnel object from being created when it is unique.
Is a certain version of Technician Tool Mobile Application compatible with all versions of StruxureWare Building Operation?
EcoStruxure Building Operation
Building Operation Technician Tool
The Technician Tool will always be backwards compatible, meaning that the latest version of the tool will work with any version of SBO.
Older versions of the Technician Tool may not work with a newer version of SBO.
Please note: Mobile experience to be replaced with EcoStruxure™ Building Operation v2.0 WebStation. For further information, please refer to Notice of Withdrawal of the Building Operation Technician Tool
Always use the latest version of Technician Tool Mobile Application when possible, as that will work with all SBO versions.
When attempting to rename an Automation Server, the following error is shown:
Validation failed for property 'PrimaryPassword'. Path: '[server path]'. Type 'Password'
Cannot set property value to null because the property is not nullable.
The Automation Server has been cloned using a backup of another Automation Server, and in that process the SMTP server passwords have been set to null.
Configure a password for the primary and secondary SMTP server. It does not matter what the password is set to.
When Forcing a value from SBO, it is just overwritten by the Lua script all the time.
EcoStruxure Building Expert
By default, the MPM executes the program once every second, so if written simply like:
Output_1 = Off
the output will be turned Off every second.
Declare a few variables in the Lua script that will help you implement the logic you need, here is an example:
if changed.Override_Status and Override_Status == 1 then
ME.BO1 = Override_Value
elseif changed.Override_Status and Override_Status == 0 then
ME.BO1 = ME.BI1
Basically, an override status points will act as a "Override button", and when it is active, The output will be equal to override value specified in SBO.
Else, if it is disabled, the output will be set to what ever you currently have in your script. In the example above, the output will be equal to the input.
Upgrading Digital Sentry breaks the Video Server connection or cameras won't learn or video streams do not work
Andover Continuum, Pelco
Pelco Digital Sentry 7.9 or greater
Continuum Video Integration 1.94 SP1 up to 2.01
Windows Server 2008
Windows Server 2012
Pelco released a newer version of Control Point that is used in Digital Sentries Video Recorders 7.9 and above. This newer API is not currently supported in any version Continuum, up to version 2.01.
Available as of July 2017, install version 2.02 of Continuum, it is a full install. R&D has worked on revising the Continuum Video Integration to work with the newer versions of Control Point 7.15 and above.
The only work around prior to this to get the video Integration to function was to downgrade the Digital Sentry to Control point 7.8
Uninstall the DS ControlPoint software using Add/Remove programs (MS Windows XP) or Programs and Features (MS Windows 7).
Install: How to install the DS ControlPoint client software
Note: Upgrading the Continuum Security Key to an Endura Key will not allow the newer API to be used with a Digital Sentry with Continuum.
A copy of the latest Video Compatibility Matrix can be downloaded from the Download Center in PA-00568.
Error importing a StruxureWare Building Operation export file. Below is an example of the error.
ERROR: Import failed to commit changeset transaction with an exception. RecoverableException: /home/ci/ci-build/rb-rb-1.8.1-system/source/server/nsp_servers/csc/changesetmanager/source/ChangeSetTransaction.cpp(1442) Invalid Data Error: File_Extension_Not_Permitted (0x10048) in module Security_Manager(74). "Not permitted to store the file "htgseqintro.wmv" with the current Document Policy." - Stack
StruxureWare Building Operation 1.8
The export file contains a document file extension that is not permitted in the Document Policy Permitted File Extensions
The file extension has to be added to the Permitted File Extensions list. See Adding a File Extension to the Permitted File Extensions List on Web Help.
For the error example shown in the issue of this article, the extension wmv has to be added to the Document Policy Permitted File Extensions. list.
Controllers are unable to get online after configuration and being added to the relative instance.
Access Expert in Cloud or Premise Installations
Win 7, Win 8, Server 2012, Server 2014
There are two reason why this could happen:
The controller is not communicating with the Feenics Host Service.
Outbound Ports are being blocked.
To resolve the issues, please check the following:
The controller is not communicating with the Feenics Host Service.
The panel may have lost power or network communication.
Dip switches may be set incorrectly (Refer to the Mercury Installation Manuals for operating modes)
Network Firewall may be blocking outbound communication over port 3001 (Give our Network Tester tool a try, find it within the downloads)
Configured DNS server may be unable to resolve at the correct IP.
2. The user is unable to see events through the Feenics Event Publishing Service.
Outbound port 4502 may be blocked. (Give our Network Tester tool a try, find it within the download section)
The client has lost internet connection.
After a card is created and added to a user, card is read and the credentials are invalid and not working.
Access Expert, Server 2012 R2 and above.
There are several reasons that could cause Access Denied to occur as listed below.
To resolve the issue please follow the steps below:
Access Denied – Invalid Card Format
The intelligent controller has no configured card format which matches the number of bits sent from the credential reader.
Opening this event inside the live monitor or event history view will display the card bit length of the credential along with its hexadecimal encoding.
Access Denied – Invalid Facility Code
The intelligent controller has a card format which matches the bit length of the card, however there are no card formats which match the facility code.
Opening this event inside the live monitor or event history view will display the interpreted card numbers & facility code based off of the card format with matching bit length.
Access Denied – Card/PIN Not Found
The intelligent controller has matched the card format & facility code, but has no matching card number value.
Opening this event inside the live monitor or event history view will display the interpreted card number & facility code based off of the format with matching bit length.
When receiving this event with a card believed to have been programmed correctly, Users may issue a clear/reload cards on the controller to update the database.
Access Denied – No Door Access
The intelligent controller has acknowledged that this card has access on this intelligent controller, but not to this particular reader.
Access Denied – Door Schedule
The intelligent controller has acknowledged that this card has access to this reader, but it is outside the allowed schedule.
This event may also trigger if the interface dip switches are not configured correctly.
**Don't forget to take advantage of Mercury’s Simulated Card Read functionality to ensure that the controller is making the correct access decision.
In V3 the Card Formats needs to be added to the Controller in Order for this to work.
**If a reader produces no audible response or LED change when a credential is presented it means that either the reader is powered incorrectly, or that it cannot read the credential technology.
Access Denied NO access at the door
Win Server 2012 R2 and above
1) The cardholder does not have sufficient Access Levels assigned.
2) The Max access levels has been reached by the intelligent controller.
3) The access levels were not successfully downloaded to the controller.
To resolve this, the following steps need to be followed:
1. Ensure that the access levels contains a door group which consists of the trouble reader.
2. Check that the person has the correct access level assignment,
3. Try saving the access level again so that it is pushed to the controller.
4. If possible, issue a reboot command to the intelligent device to ensure database synchronization.
OR if the system database limit on access levels has been reached, take the following steps.
Verify the user has permissions on the Role
Go to the General Configuration
Select System Settings
Select the Hardware Tab on the bottom
Change the Max Access Level to a higher level than the default (100).
Save and Reboot the controller for the changes to take effect
The communication with TAC Xenta controllers is slow or inconsistent
EcoStruxure Building Operation
The Non group receiver timer is not properly set.
Every device has a timer called Non group receive timer. The Non group receive timer is used to make sure that a re-sent Lon package will not be treated as a new message and to determine when a receiver buffer can be released. It is used in Acknowledged, Repeated and Request/Response transactions, but not in Unacknowledged ones.
If this timer is set too low, a re-sent package, like Unacknowledged repeated message, may be treated as new messages, that will be sent on to the application.
The communication buffers will not be released until the timer has expired. If the timer is set too long, that may result in the device running out of buffers, and new messages will not be received during this time.
If a device has many SNVTs or TACNV’s being transferred there may be a need to increase the value of the Non group receiver timer. The default value for a programmable Xenta device is 768 ms.
Change the Non group receive timer of the Xenta devices.
The default value for a programmable TAC Xenta device is 768 ms. The recommended timer values are:
Number of network variables
Non group receive timer value
768 ms (default)
50 – 100
The default value for the AS and AS-P is 8,092 ms. There is no need to change that value.
Creating new user roles and knowing the access that is needed for it to become active.
Cloud or Premise Installations
Knowing what the role the user is playing would determine what selections need to be activated for them.
To achieve this the following steps need to be followed:
Open up General Configuration
Select the Roles icon
Click on the tab for New Role (everything is blank by default)
Name and configure accordingly
Check all tabs to make sure everything is Viewable and Editable
Save and close
Now this role can be selected for any user once created
Some actuator datasheets do not specify the impedance of the 0-10V control signal, this is required to determine fan out from a controller.
MB3 Range - MB3-24M, MB3-SO-24M, MB3-SC-24M
MZ20 Range - MZ20A, MZ20A-R
Information not defined on the specification sheet.
MB3 Range 0-10V control signal input impedance = 200K Ohms.
MZ20 and MVT56 Ranges 0-10V control signal input impedance = 32K Ohms.
If a Variable status alarm is setup on a BACnet point it never triggers.
Workstation V1.8.1 and earlier
The reason is that the 3 available triggers (Forced, Overridden and Offline) do not apply to the BACnet protocol.
If you open up the bindings page for a BACnet point you will see that none of the BACnet point attributes are the same as these 3 trigger statuses.
Although from the SBO side you can force a point, what actually happens is that the value becomes commanded at "Command priority 8" (by default). The BACnet protocol does not have a Forced attribute.
There is also no attribute listed for Overridden and Offline point in the BACnet standard.
Because of this the Variable Status Alarm does not apply to a BACnet point.
Why isn't the OpenLNS a full, un-limited license?
Renewing OpenLNS CT Annual Maintenance
You can renew your annual maintenance for OpenLNS Server and OpenLNS CT before they expire.
Renewing your OpenLNS and OpenLNS CT annual maintenance enables you to continue installing
software updates and upgrades. If you do not renew the products’ maintenance, you can still use the
products; however, you will not be able to upgrade it with updates or upgrades released after your
annual maintenance expired. You cannot renew your annual maintenance after it has expired. Once it
has expired, you must purchase a new activation key to be able to install any updates or upgrades
released after your maintenance expired.
To renew your annual maintenance, purchase an OpenLNS Commissioning Tool Professional
One-Year Maintenance Renewal (Echelon model number 93800) or an OpenLNS Commissioning
Tool Standard One-Year Maintenance Renewal (Echelon model number 93810). Echelon will
process your order, and your maintenance coverage will be extended so that you can continue updating
and upgrading OpenLNS and OpenLNS CT for an additional year.
If paying the annual maintenance fee, you have access to updates and upgrades.
Not paying still means that the program could be used, however it could not be updated with the latest patches.
MPM rebooting with message in the log like:
MASTER_MAN (id= 9) 361893.721> FAULT: core_watch.c:333; code:0; time:2017-02-13 15:34:25; Message:Task ID 38:Lua_User_PGs expired at 361886.5; Top Of Stack:0x000000F3 0x20D4BE7C 0x71B73B76 0x0000007A 0x00000000 0x60000013 0x60000013 0x00000000 0x2084D224 0x08080808 0x09090909 0x10101010 0x11111111 0x00000015 0x2006FD91 0x2006FD91 0x20D48D3C 0x20062159 0x00000000 0x00000000 0x20EE8248 0x20D48D3C 0x00000000 0x00000000 0x22D50000 0x00000000 0x20D1E8E4 0x000007D0 0x00000000 0x2084D238 0x00000000 0x00000000 ;
EcoStruxure Building Expert
This is an error in one of the PG object (user written Lua script) possibly an infinite loop.
Disable or delete 1 by 1 your Lua PG's to identify the PG with the issue.