Building Automation Knowledge Base

Issue Some of the Continuum attributes in b3/i2 objects are not listed for binding in Script, one such example is the ElecValue of an input object, in Continuum, the difference between the Value attribute and ElecValue attribute is the former is the software value while the latter is the actual value read from the sensor. Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Cause For reasons that are beyond the scope of this article, not all Continuum properties have been included for binding in Script   For example, the list of bindable properties for a b3 Analog Input is missing the ElecValue property as can be seen below   Resolution In a b3 Script or Infinet Script Program, there is a way to access any property (attribute as they are known in Continuum) of an object by simply referencing the property's name right after a binding variable to the object's value   Consider the situation that can be seen in the screen capture below...     Due to some strange failure the software contains an incorrect value for the input, but accessing the input's electrical value from a b3 Script program reveals the sensor is reading the room temperature correctly.   Below, screen capture of how this is accomplished in b3/i2 Script program     NOTES "theInput" is bound to the value of the "RoomTemperature" input. "theInElecValue" is bound for output to an AnalogValue in the b3 where the program will place the electrical value of the input We access the property by adding its Continuum attribute name right after the variable bound to the input's value, you will need to know the exact Continuum name of an object's attribute in order to access it this way. This works for any attribute that is accessible by Plain English in Continuum including the PriorityArray of b3 commandable objects.

Issue After upgrading Remote Alarm Manager 1.2 to 2.0 none of the settings site specific configuration is carried over and Remote Alarm Manager can't detect the license. Environment Sigma 4 Remote Alarm Manager 2.0 Cause The site has upgraded Remote Alarm Manager through several iterations over time, versions of Remote Alarm Manager prior to version 1.001 stored site configuration data with the source system data. For example in the C:\Sigma\Data\Remote Alarm Manager\ folder, current versions typically store the data by default in:- For Windows XP - C:\Documents and Settings\All Users\Application Data\Schneider Electric\Remote Alarm Manager. For later operating systems - C:\ProgramData\Schneider Electric\Remote Alarm Manager. Resolution There are two possible ways to resolve the issue:- After installation of the software run the Computer Configuration utility (this runs by default) and deselect (uncheck) the Windows Common Application Data checkbox on the "Data Location" tab and enter the path to the current Remote Alarm Manager data location. After Installing the software and running the Computer Configuration utility copy the setup.mdb and log.mdb files from the current location to the default location used by the software:- For Windows XP - C:\Documents and Settings\All Users\Application Data\Schneider Electric\Remote Alarm Manager. For later operating systems - C:\ProgramData\Schneider Electric\Remote Alarm Manager.

Issue An XLSX report is created using a triggered Notification in EBO. When the report should be opened in Excel an error appear "Excel cannot open the file ..." and the report can not be opened. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Excel for Microsoft 365, Excel 2021, Excel 2019, Excel 2016, Excel 2013 Office for business Cause Formatting cells on your worksheet can make the right information easy to see at a glance, but formatting cells that aren't been used (especially entire rows and columns) can cause your workbook's file size to grow quickly. This can slow down not just Excel, but the overall performance of your computer when you have an excessively formatted worksheet open. Excessive formatting can also cause printing problems in Excel. Resolution Use the Clean Excess Cell Formatting command, available on Excel's Inquire tab in Microsoft Office 365 and Office Professional Plus 2013. Important: You may want to make a backup copy of your file before cleaning the excess cell formatting because there are certain cases where this process may make your file increase in size, and there is no way to undo the change. If you don't see the Inquire tab in Excel, do the following to enable the Inquire add-in: Click File > Options > Add-Ins. Make sure COM Add-ins is selected in the Manage box, and click Go.   In the COM Add-Ins box, check Inquire, and then click OK. The Inquire tab should now be visible in the ribbon.   To remove the excess formatting in the current worksheet, do the following: On the Inquire tab, click Clean Excess Cell Formatting. Choose whether to clean only the active worksheet or all worksheets. After excess formatting has been cleared, click Yes to save changes to the sheets or No to cancel. See Microsoft support topic:  Clean excess cell formatting on a worksheet 

Issue UI-8-10 module is reporting no change of state on inputs when shorted. Environment UI-8-10 Cause Setting the voltage range switch to 10V when the Reference Resistor is in the on position is an invalid configuration. Resolution Change the voltage range settings to 5v on the input.

Issue Could not start the TAC Xenta 102-AX LonWorks PlugIn, due to an Error message. Product Line EcoStruxure Building Operation. Environment EcoStruxure Building Operation Workstation. TAC Xenta 102 AX Cause EcoStruxure Building Operation does not support online PlugIns, as LNS is running in the background, without any communication port.. If selecting to Synchronize (Upload or Download) you will get an error message. Resolution Select "Skip" synchronize.

Issue The SE8000 display face shows white blocks in place of expected data points. Product Line EcoStruxure Building Operation, EcoStruxure Building Expert Environment Building Operation Workstation Building Operation Automation Server SSL SE8000 Cause Upgrading the firmware of SE8000 using the Uploader Tool may not have been completed successfully. Resolution   .  

Issue Require the Automation license option to be able to configure C-BUS integration but the option is not enabled. Product Line EcoStruxure Security Expert Environment SP-C-WEB Cause Older SP-C-WEB controllers were shipped without the Automation license enabled. Resolution SP-C-WEB controllers purchased after 4-Oct-2021 are shipped with the Automation option included with the license.   For controllers ordered before this date the option can be enabled by contacting Product Support and providing the controllers serial number.

Issue When importing Security Expert controllers into Security Expert Server using the Data Sync Service, the Register As Reader Expander address field is different from the value in the CSV file. The address field is incremented by 1. Product Line EcoStruxure Security Expert Environment Security Expert Server Security Expert Data Sync Service Cause Register As Reader Expander values in the Security Expert SQL database are stored as integers where indexing starts at 0, whereas in the Security Expert Client the same values are displayed as integers starting at 1. The Data Sync Service updates the database values directly, which is why the values differ between the CSV file and the user interface. Resolution In the CSV import file, decrement values in the Register As Reader Expander column by 1. For example: If the address in the user interface is '1', the value in the CSV file should be changed to '0'. See screenshot from Data Sync Service (left) and Security Expert Client (right) below.  

Issue Access which allows a value to be changed, also allows other changes to be made. Environment Users User accounts Cause A user account is created to have read only access, but this user must also have access to view Graphics, and on these graphics, be able to change values. How can this be achieved without allowing the user access to delete or edit these objects?   Resolution At StruxureWare Building Operation release 1.3 there are no available options that will achieve this configuration, the most appropriate configuration is to create a Workspace for the user, in which they will see only the Graphics, the user would have Read/Write access to the values they are allowed to change.

Issue EG2RL is obsolete and needs to be replaced. Environment EG2RL 5552220000 Cause Replacement of old EG2RL sensor Resolution The EG2RL was used in pairs as Average temp sensors. Each unit contains 2 SPA (1.8kOhm) sensor elements in serial, that are then connected to the other unit in parallel. No direct replacement is available.  

Issue For EBO Active Directory (Windows Domain) integration, do EBO support usage of "nested groups"?. Product Line EcoStruxure Building Operation Environment Building Operation Workstation Cause EBO are using Windows API and ask if the user is a member of a certain group.  Resolution Windows API should respond “yes” if the user is part of a group that is part of another group, which is configured in EBO. So this is up to how the Windows AD responds to the Windows API and not on the EBO side.   For more information, please see Integrating Windows Active Directory user accounts with EcoStruxure

Issue Does the JACE-6E or JACE-7 support multiple FTT-10A LON cards? Environment JACE-6E, JACE-7, LON FTT-10A Cause Application requires multiple FTT-10A LON trunks. Resolution Yes ... the JACE-6E / JACE-7can support two individual FTT-10A cards.  Purchase (2) TRD-NPB-LON (FT-10A Lon Adapter cards) and (1) ENC-DRV-LON driver.  Add one LonNetwork for each physical port.  Under each LonNetwork within the Lon Comm Config, specify the port's Device Name (e.g. LON1 and LON2).  Reference the Niagara AX Lonworks Guide for more details.

Issue Doing a R2 to G3 oBIX integration.  The alarms in the R2 station have been successfully imported into the G3 station.  However, they are as 'normal' in the G3 Alarm Console when they are actually in alarm.  How can they be configured to change color? Environment Niagara G3 oBIX integrations (any version) Cause R2 native alarms are NOT oBIX 'Stateful Alarms', meaning there is no defined 'lifecycle' of an alarm event (unlike native G3 alarms). As a result, R2 imported alarms appear as "normal" (green alarm bell) source state events when routed to the G3 Alarm Console. Resolution Add native G3 alarming proxies to provide the red color of an alarm.

Issue Viewing Script time from the editor can show incorrect time Product Line EcoStruxure Building Operation Environment Building Operation Automation Server, AS, ASP, ASB, AS Classic Building Operation Enterprise Server Building Operation WorkStation Script Program Editor Cause Scripts use Local Server time, but the Clients like Script Editor or WorkStation expecting a server to be UTC. The result is that during Daylight Saving Time, the time seen in the script editor may appear an hour out. Resolution During debugging of Times or Dates or DateTime Values, it is helpful to "Print" the Datetime to a string as this will show actual time being used rather than the Clients interpretation of the time (See script below).The client will take the Server time as UTC and apply offsets to achieve its "Local" time, which can give an incorrect time. The UTCOffset property can be used to correct for time zones but there is no DST(Daylight Saving Time) offset available until v4.0.

Issue Getting LON messages TException E_QUEUE_FULL {LonAsyncRequest} in the standard output window. Environment R2, Niagara, Lon Service Cause If also in the message there is a line that includes: "lonextras.control.PollSnvtTempSetptCmd.execute" these messages are being caused by the use of the special object from the LonExtras jar called PollSnvtTempSetptCmd.  Resolution When the station is booting up the PollSnvtTempSetptCmd object  will begin its polling function before the station has finished rebooting causing the queue to fill up before the station starts.  There is an object in the LonWorks jar - Conversion container called SnvtTempSetptCmd that will perform the same function as the PollSnvtTempSetptCmd except it does not poll which is not necessary in most cases.  Replace all PollSnvtTempSetptCmd objects in the station with the SnvtTempSetptCmd object.

Issue Is the MZ20B suitable for use in an On/Off application? Environment MZ20B 230V: 8455003000 MZ20B 24V: 8455001000 Cause Depending on control signal type and construction, some actuators are better suited for On/Off applications. Resolution Yes, the MZ20B can be used in an On/Off application. For connection details and more, please see the MZ20B data sheet. 

Issue Since the ZS106 is obsolete, a replacement is requested. Environment ZS106 - 007309220 STR106 - 004600500 Cause Replacement for obsolete product. Resolution The STR106 wall module, part no 004600500, is replacing the obsolete zone sensor ZS106.

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 With no CyberStation or network controller available, need to load application programs into controller. Environment RoamIO2 Cause This item is not in the documentation. Resolution The RoamIO2 does not have the ability to load a dump file into a controller.

Issue Logs in the UNC are not archiving to the Enterprise Server Environment I/A Series R2 Universal Network Controller (UNC) and Enterprise Server Cause The UNC station and the Enterprise Server station have their LogService 'archiveMode' property set to 'archive_disabled'.  Resolution Change the LogService 'archiveMode' in both the UNC station and the Enterprise Server station.  1. Set the UNC station's LogService 'archiveMode' to 'archive_remote'. The 'archiveAddress' property should have 'Supervisor' checked.  2. Set the Enterprise Server station's LogService 'archiveMode' to 'archive_local'. (The “archive_local” selection is valid only if the station is running the DatabaseService) The following have to be also correct in order for log archiving to happen: AddressBook entries should be properly setup in the Enterprise Server and UNC stations. Refer to Page 1-15 and 1-16 of the Niagara Standard Programming Reference for further information.  Supervisor checkbox in the UNC's LogService 'archiveAddress' property should be checked. In the Niagara Log Object properties, the 'archiveSetup' property should have 'nearFull' or 'daily' checked. It is recommended that both of these be checked.