Building Automation Knowledge Base

Issue Backing up a GCM database in Tree Tech, but the system wasn't originally engineered using Tree Tech. Is there a documented procedure for doing so? Environment Tree Tech 3.1 or 3.2 Tree Tech Engineering Guide, F-26640-4 Network 8000 GCM-84000, GCM-86000, LNC-1000, SIM-x Cause Earlier versions of the Tree Tech Engineering Guide, F-26640, didn't include a step-by-step procedure for backing up a GCM that had not originally been engineered using Tree Tech. Resolution The latest edition, Tree Tech Engineering Guide, F-26640-4,  has been appended to include a step-by-step procedure for creating and configuring all Tree Tech components necessary for ultimately uploading a GCM database. A link to this revised edition is available through the "Help" menu:     See Appendix B, "Creating a GCM Database Backup". Topics include: 1. Creating a New Project Database 2. Adding the Equipment Segment 3. Adding the Network 8000 Object 4. Adding a GCM to the Network 5. Adding the Workstation Segment 6. Adding a Port 7. Configuring the NETWORK 8000 Network 8. Communicating with the GCM 9. Prepare for Backup (Upload) 10. Uploading the GCM Database

Issue Continuum BACnet devices not seen in Continuum Explorer Environment CyberStation Cause "Continuum Explorer\View\Show Continuum BACnet Devices As" is set to "Infinet Controllers only" Resolution "Continuum Explorer\View\Show Continuum BACnet Devices As" is set to "Infinet Controllers only" Set to "Infinet Controller and BACnet Device The slightly confusing thing is that all Non Continuum (third party) devices still appear in the Bacnet view. This is correct, as designed. See below for both examples  

Issue How do you convert MicroNet 2000 controller filenames generated by the MicroNet Controller Interface "Get Multiple" function to integrator and controller addresses? Environment MN-2000, MN-CI, MicroNet Controller Interface Cause The "Get Multiple" function is used to upload application programs from multiple MicroNet controllers under one MicroNet Integrator or a series of MicroNet Integrators.  The application programs are stored as files with the integrator and controller addresses appended to the name. Resolution When uploading files from multiple MicroNet VAV Controllers, the CI creates unique filenames for each uploaded application file by appending the integrator number and device number to the prefix entered in the Enter File Prefix window. The integrator number and device number are appended in hex format. The file shown in the illustration above was uploaded from MicroNet controller 11 under MicroNet integrator 6.

Issue After a Xenta download through the system Plugin the daylight savings mode is changed in the controller that was downloaded Environment Vista 5.x.x System Plugin Cause The time setting in the System Plugin is applied to the Xenta controller at the time of download. Resolution In the system Plugin under the TAC network pane right mouse click on the TAC network and select Configure Time Settings.   From this window set the Time zone and daylight savings mode. When finished select ok and then update the Vista database.

Issue Unable to access the "Tools" menu item to configure options in the "standalone" version of I/A Series G3 Alarm Portal Environment I/A Series G3, Alarm Portal, ENS-ALM-CON-G3 Cause The "Tools" menu item was removed in I/A Series G3 versions 3.6 and higher to prevent any user from configuring Alarm Portal options (e.g. appearance and operational behavior). Resolution Configuration of the Alarm Portal options on a "standalone" version requires a set of files to be transferred from a full Workbench version of the Alarm Portal to the standalone version. Start Workbench and select Tools - Options Configure options (e.g. Alarm Console, Alarm Portal) Close Workbench and use Windows Explorer to locate the options subfolder for the user that modified the Alarm Portal options Copy the associated options files (alarm-AlarmConsoleOptions.options and alarm-AlarmPortalOptions.options) to the standalone Alarm Portal. Place the files under the appropriate user using the same path structure in an options subfolder.  The Alarm Portal will now use the options defined.

Issue Instructions for configuring the enterprise server or automation server for custom views accessible from mobile devices. Environment SmartStruxure iPhone iPad Custom View Cause Instructions for configuring the enterprise server or automation server for custom views accessible form mobile devices. Resolution Creating custom views for iPad or iPhone is done in StruxureWare Building Operation. In Building operation right click on the server object and select New>Folder Name that folder Custom View (the folder must be named this to be recognized by the mobile device) Within the custom view folder you can drag and drop your data that you wish to have in the custom view or you can also create sub folders beneath the custom view folder. See example Below.   Once the configuration steps above are complete, login to the mobile app and click the Custom View button. Everything within the Custom View folder in the AS or ES should be displayed. * In the event these folders do not show up, please logout of the mobile application and log back in.

Issue Cant open a hyperlink because internet explorer version is to low Environment Vista Cause The hyperlink is opened with compatibility mode on please read more here 1) http://stackoverflow.com/questions/6717055/how-do-i-turn-off-compatibility-view-on-the-ie-webbrowsercontrol-in-a-winforms-a 2) http://msdn.microsoft.com/en-us/library/ee330730(v=vs.85).aspx Resolution Open regedit Go to Start > Run Enter regedit and press enter Locate the folder 32-bit OS: HKLM\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION 64-bit OS HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_BROWSER_EMULATION Right click and choose add Add a DWORD Name it "TACVistaExplorer.exe" Enter the value depending what Internet explorer you use i.e for Internet Explorer 10 enter the value 10001 Restart Vista and Tacos This is how it should look

Issue User names and passwords are not accepted by the AS's. Environment Domain Password Users Cause A new Domain was configured on the ES, this configuration was then exported, the export was then imported to each AS. Resolution Note;- By importing and exporting copies of the Domain, Domains that are not related to each other, are created, which is unlikely to be the operational intent. Exporting/Importing will duplicate user accounts etc. Having multiple accounts with the same name (potentially with different passwords) throughout the system can lead to an overly complex and un-manageable configuration. To create a new Domain configuration, carry out the following. Add the Automation Servers (AS) to the Enterprise Server (ES) in the normal way. With the Workstation connected to the ES, select "Control Panel" and "Domains"     "Add" a new Domain, giving it a suitable name, and then select the AS's that will share this Domain with the ES.       Now Create the Domain. At this stage, if the AS's are reviewed, the New Domain can be seen, (Note - Nothing is shown in the Domain folder on an AS).                           If required, you can choose to set the new Domain as the default Domain,  this is achieved by right-hand mouse clicking on the Domain and selecting the option. This must be done on each Server.                                       Confirm that the ES IP address is correct in all servers.     Finally create the User Groups, Users, and Workspaces required for this Domain. Log off the Workstation, and restart  the ES. Once the ES has restarted, log back on using the new Domain information.   Log on to an AS using the new Domain information.     

Issue Building Operation Menta Editor can normally be opened. But when editing a Function Block Program or a Xenta programmable Xenta controller in Operation Workstation, a Runtime error occurs like the following image and Menta Editor will crash. Environment Building Operation Menta Editor Building Operation Workstation 1.3sp1 Cause The reason is that the formats and language do not match in regional and language options in Windows Operation System. Resolution The selected item in the Standards and Formats of Regional Options must be matched with the selected language in Language for non-Unicode programs of Advanced in Regional and Language Options.  That is like as the red circles of the following image.

Issue Hotfix readme / report asks me to "Confirm the file versions are now build x.x.x.xxxx in explorer" - how is this done? Environment SmartStruxure Hotfix releases. Cause The 'File version' property on some files are not easily found / shown in Windows explorer, so only the 'date modified' can be used to indicate that the file has been updated.  Resolution The easiest method of confirming that files have been updated correctly by the Hotfix is to view them in Windows Explorer.  The paths for this are as shown below: For versions 1.2 and below: C:\Program Files\Schneider Electric\StruxureWare X.X\...(32-bit operating systems) C:\Program Files (x86)\Schneider Electric\StruxureWare X.X\...(64-bit operating systems) For versions 1.3 and above: C:\Program Files\Schneider Electric StruxureWare\Building Operation X.X\...(32-bit operating systems) C:\Program Files (x86)\Schneider Electric StruxureWare\Building Operation X.X\...(64-bit operating systems) Within this path are the folders containing the files for each of the applications such as the Device Administrator, Enterprise Server, Workstation, etc as shown below. For each Hotfix .EXE file that is applied you need to check each of these folders with the files detailed in the Hotfix readme / Hotfix Report provided. To confirm that these files have been updated you can either check the File version shown in the properties of the file or you can display the file version as a column in Windows Explorer. See an example of this below (This is showing Hotfix 1.2.0.2207). For the files that do not display their 'File version' property the only way to check that these have been updated is to look at the 'Date Modified' property. This date should match the date of the Hotfix application (.exe). See image below where these matching dates have been highlighted.

Issue When logging onto a client session on the WebClient server, the screen goes white and cannot logon. Environment WebClient Firewall Client WebServer Cause Firewall was restricting access to the database server. Resolution Turned off firewall on the database server.

Issue Importing a VisiSat pointslist StruxureWare reports a limit issue and suggests the import is complete. Environment StruxureWare Building Operation 1.3/1.3 SP1 Cause On one of the VisiSat points being import,  the alarm limits have been incorrectly set.   Although StruxureWare Building Operation 1.3/1.3 SP1 reports that the import completed in X minutes and X second, the import would have failed to complete due to the stated issue. Unfortunately the reported limit issue can effect 100 points or just the 1 point.  The specific point or points identity is not highlighted in the trace file.   Resolution Locate the point and check the alarm limits are entered correctly. The example below show the upper limit and lower limit are reversed. Change it so the upper limit is above the lower limit.

Issue How to display custom text and properties of an alarm in the email notification. Product Line EcoStruxure Building Operation Environment Email Notification Substitution Codes Cause There may be certain situations where a specific property of the monitored value needs to listed in the alarm email that is sent out. For example when an alarm is triggered, the value at the time the alarm state changed my need to be documented in the notification email. These are called substitution codes. Resolution The properties of the Email Notification can be set to customize the message that is sent out when an alarm changes states. As seen in the properties window of the Email Notification above, the "Subject" and "Text" can be changed to say whatever is desired. There are special codes that can also be entered into these fields to pull actual properties from the value that went into alarm. Below is a table that lists all of the Codes for the different value properties. This same information can also be found on the EcoStruxure Building Operation WebHelp. Substitution Codes for Notifications Code Description @(AcknowledgedBy) Writes the user that acknowledged the alarm. @(AcknowledgeTime) Writes the time the alarm was acknowledged. @(AckRequired) Writes an indicator if the BACnet alarm requires acknowledgement. @(AlarmState) Writes the present state of the alarm. @(AlarmText) Writes the alarm messages that is added to the alarm. @(AssignedID) Writes the unique ID of the user the alarm is assigned to. @(​AssignedState) Writes the current assigned state the alarm is in. The possible values are Unassigned, Assigned, and Accepted. @(​AssignedTo) Writes the name of the user or group that the alarm is assigned to. @(​AssignedToDomain) Writes the domain of the user or group that the alarm is assigned to. @(BACnetEventType) Writes the BACnet event type for this alarm. @(BACnetNotificationType) Writes whether the BACnet notification was an alarm or event. @(BasicEvaluationState) Writes if the alarm is active or not. @(Category) Writes the category name of the alarm. @(CommandValue) Writes the value which was commanded for a BACnet command failure alarm. @(ConfirmedNotification) Writes an indication whether a BACnet notification was issued as a confirmed or unconfirmed BACnet message. @(Count) Writes the number of times the alarm has toggled between the alarm and reset states. @(Deadband) Writes the value of the deadband used for limit checking for BACnet out of range alarms. @(DeviceName) Writes the name of the I/NET device that generated the event. @(​DisabledCause) Writes the cause of the alarm being disabled. An alarm can be disabled by User, Shunt variable, and System. If the alarm isn't configured correctly it can be disabled by System. @(ErrorLimit) Writes the difference limit that was exceeded for BACnet floating limit alarms. @(EvaluationState) Writes the present evaluation state of the alarm. For example, Upper limit alarm is displayed when the monitored value reaches the upper alarm limit. @(EventFromState) Writes the event state of the object prior to the occurrence of the alarm condition for BACnet alarms. @(CWSid) Writes the EcoStruxure Web Service identification of the alarm on the external system. @(CWSSourceId) Writes the EcoStruxure Web Service identification of the external object that generated the alarm. @(ExceededLimit) Writes the value of the limit that was exceeded for BACnet out of range alarms. @(ExceedingValue) Writes the value that exceeded a limit for BACnet out of range alarms. @(FeedbackValue) Writes the value that differs from the commanded value for a BACnet command failure alarm. @(FirstName) Writes the first name of the individual whose key/card was used at the I/NET door point. @(Hidden) Writes the visible status of an object. False is displayed when the object is shown. @(IndivNdx) Writes the individual number of the individual whose key/card was used at the I/NET door point. @(LastName) Writes the last name of the individual whose key/card was used at the I/NET door point. @(Logging) Writes whether the alarm should be logged or not. @(MessageText) Writes the text of an I/NET action or dispatch message, if there is one. @(MonitoredObject->DESCR) Writes the description property of the monitored object. @(MonitoredObject->NAME) Writes the name property of the monitored object. @(MonitoredObject->NOTE1) Writes the note 1 property of the monitored object. @(MonitoredObject->NOTE2) Writes the note 2 property of the monitored object. @(MonitoredObject->LabelText) Writes the label text of the monitored object. This requires that a MonitoredVariable is configured. @(MonitoredValue) Writes the value depending on the alarm states selected under 'Notify on transition to'. @(​MonitoredVariable) Writes the path of the monitored variable. @(NewMode) Writes the new mode of the monitored object for a BACnet change of value alarm. @(NewState) Writes the new state of the monitored object for a BACnet change of state or change of life safety alarm. @(NewValue) Writes the new value of the monitored property for a BACnet change of value alarm. @(NotificationClass) Writes the distribution information of an alarm notification within a BACnet system. @(OperationExpected) Writes the next operation requested by the monitored object for a BACnet change of life safety alarm. @(OriginalAlarmText) Writes the alarm text from the matched alarm. This substitution code is only available for Alarm Decorators. @(PossibleOperatorActions) Writes the possible actions one can perform on the record, given permissions. @(PreviousAlarmState) Writes the previous alarm state. @(Priority) Writes the current priority level of the alarm state. @(ProcessId) Writes the process identifier configured by the notification for a BACnet alarm. @(ReferencedBitString) Writes the new value of the monitored bitstring property for a BACnet change of bitstring alarm. @ (Report) Writes the name of the report connected to the notification. @(SEQNO) Writes the sequence number of the record. @(SetpointValue) Writes the value of the setpoint when the alarm condition occurred for a BACnet floating limit alarm. @(​Source) Writes the path of the source object. @(SourceName) Writes the name of the source object that generated the alarm. @(SourceObject->DESCR) Writes the description property of the source object. @(SourceObject->NAME) Writes the name property of the source object. @(SourceObject->NOTE1) Writes the note 1 property of the monitored object. @(SourceObject->NOTE2) Writes the note 2 object of the monitored object. @(​SourceServer) Writes the path to the server where the source object is located. @(StatusFlags) Writes the status flag of the object. @(SystemAlarmId) Writes the alarm ID generated by the system. @(TenantNdx) Writes the tenant number of the individual whose key/card was used at the I/NET door point. @(TimeStamp) Writes the time and date when the event was generated. @(TriggeredTimestamp) Writes the time and date of the last state transfer from normal state to alarm state. @(TYPE) Writes the record type.

Issue Search of All Forced Variables Environment StruxureWare Building Operation site Cause Desire to search of All Forced Variables without having to visit and physically look at each point. Wanting a Summary page that is not in the Reports Server, but on the AS or ES which shows which points are Forced and which are not Forced. Resolution Forced Values can be found in system tree. Example with screen shot below: ES/Servers/AS/System/Modules/RuntimeDBManager/VariableManager/Variables if you enabled the isForced column.

Issue When attempting to open a TGML page from a Xenta Server in Internet Explorer receive a Java error "Unknown error: null" Environment Xenta Server 500 / 700 series 5.03 and above. Cause The original pages in the Xbuilder project were created as OGC pages, the new pages that replaced the OGC pages are now TGML pages. This occurs when, the Xbuilder project had an OGC Graphics object that was replace with a TGML Graphics object of the same name, the Graphic page that referenced this object is what produces the JAVA Null issue Resolution There seems to be an issue with the original Graphics page that were created and referenced an OGC Graphic To solve this Delete the Graphics page in the Xbuilder project. Create a new Graphics page with the same name as the deleted one. Select the new TGML graphic object on the new page with the same name. Generate the project and download to the Xenta server.

Issue The MnFlow shadow device, in Niagara R2, comes with six objects.  What do the inputs and outputs cross-reference to down in the Micronet 2000 VAV controller? Environment Niagara R2 (ASD driver) Micronet 2000 Cause Programming Niagara objects to control setpoints in the Micronet VAV Resolution Document F-25720 lists tables illustrating what each input and output is mapped to in the Micronet VAV. MnFloEmsDi object in Niagara R2: MnFloEmsAi object in Niagara R2: MnFloDvOuts & MnFloAvOuts objects in Niagara R2:

Issue SmartStruxure and Vista 5.1.8 and later TGML editors have an option to change the grid size whereas earlier versions of TGML were hard coded at 5 pixels. Environment TGML Graphics Editor Cause Being able to change the grid size to a larger value allows for quicker and easier alignment of graphics objects. Being able to change it to a smaller value allows for more precise positioning. Resolution In the TGML Editor, find the "Show Grid" option in the main toolbar There is a small down arrow to the right of this icon that will pull down a menu for selecting the desired grid size Toggle "Show Grid" to display the grid size on the graphic work area Toggle "Snap to Grid" to turn on and off fixed positioning of items on this grid.

Issue OPC points status' shown as 'fault' and not updating after Matrikon OPC Server is restarted Environment I/A Series r2.301.529 Enterprise Server OPC Client integration to Matrikon OPC Server Cause The root cause for this issue has not been determined at this time, the following workaround currently resolve this issue.  Resolution The current workaround is to disable and then enable the OPC Server in WorkPlace Pro.  1. Right click on the OPCServer object and go to its properties. 2. Go to the Config tab. Change the serverEnable property to False and Apply. Change the serverEnable property back to True and Apply.      

Issue Dimensions for the ENCL-DOOR-PLA.  Environment DMS Cause They are not provided on the datasheet available via iPortal. Resolution Dimensions are illustrated below:

Issue Object Transfers are not working after upgrading Vista. The devices are online and the values are updated when viewed, but the values aren't transferred via the object transfer objects. Environment Vista 5.1.X that has been upgraded. Cause The vista server is in engineering mode. Resolution Go to the $System object under the TAC Vista root object in workstation and check the  Status-Operating check-box is checked.