Building Automation Knowledge Base

Issue When adding MNL controller in Workstation for Projects, it will show up an error: Object type is not supported. Environment SmartStruxure 1.5 Workstation for Project PCS MNL controller Cause When using the Project Configuration Server, you cannot create MNL LonWorks devices and applications. Accordingly, the WorkPlace Tech Editor option does not display in the Control Panel. Resolution MNL LonWorks devices can be added in an Enterprise Server or Automation Server after deploying a project to one of these servers.

Issue A site physical access is configured as follows... Upon arriving at the site, the employee must check-in at a gate where a main biometric reader at a VIRTUAL door is configured with entry/exit readers for Check-in and Check-out. This 'Registration' reader is not controlling access to any physical door, the Registration door in Continuum has zero for door relay channel but IT IS configured with entry/exit readers so the Continuum access control panel can detect the check-in/check-out transactions. Once the employee has checked in, he can continue on to the building where he must then present his physical access credentials at a physical door to gain access into the building. The site requirement is that the employee can not be given access to the building until they have checked-in at the Registration reader at the gate, also, access to the building must be removed upon the employee checking-out at the gate when leaving the site. The doors in the buildings are configured with entry reader ONLY, so entry/egress anti-passback cannot be used. Product Line Andover Continuum Environment CyberStation ACX2 NC2 NC1 9702 Cause Documentation Resolution Since this must be done on a per employee basis, an InfinityNumeric is created per employee and assigned as the area schedule in the personnel object for the areas that are in the building. A specific convention is used for the name of the numerics (Key_XXXXX) where XXXXX is the card number assigned to the employee. A PE program monitors the registration door at the gate, when en employee arrives and checks-in the program finds the appropriate employee key numeric and turns it ON to grant access to the areas in the building, conversely, when the employee leaves, the program finds the right key and turns it to OFF to deny access. PROGRAM SAMPLE IMPORTANT: PE PROGRAM IS PROVIDED HERE AS PROOF OF CONCEPT ONLY AND IS NOT INTENDED TO BE TAKEN AS A COMPLETE TESTED SOLUTION. 'This program controls access to the building on a per employee basis 'The area schedule numeric for the employee is turned ON when the employee 'reports at the entrance reader (GIVE EMPLOYEE THE KEY) and OFF when the 'employee reports his departure at the exit reader. (TAKE THE KEY FROM THE EMPLOYEE) 'ASSUMPTIONS '1. All cards have the same site code 'AUTO START 'LOOPING Numeric Direction, DEBUG String theKey Line INIT DEBUG = 1 'SET THIS TO 1 FOR DEBUG HELP Goto WAIT_FOR_ACCESS Line WAIT_FOR_ACCESS theKey = "Key_" 'RESET KEY NAME 'WAIT FOR A VALID ACCESS AT THE LOBBY If Lobby ValidAccess then Goto GET_DIRECTION Line GET_DIRECTION 'DETERMINE IF ENTRY OR EGRESS If Lobby TimeEntered > Lobby TimeExited then Goto ENTRY Else Goto EXIT Line ENTRY theKey = theKey ; Lobby EntryLastCard 'FIND THE KEY FOR THIS CARD getname(theKey) = On 'GIVE THE EMPLOYEE THE KEY Goto WAIT_FOR_ACCESS Line EXIT theKey = theKey ; Lobby ExitLastCard 'FIND THE KEY FOR THIS CARD getname(theKey) = Off 'TAKE THE KEY FROM THE EMPLOYEE, NO KEY NO ACCESS Goto WAIT_FOR_ACCESS Line E If DEBUG then Print "Hit the error line" to Debug_STR If TS > 0 then Goto WAIT_FOR_ACCESS

Issue When trying to upgrade a database to version 1.5 or 1.6 the upgrade fails Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause There can be various reasons for the upgrade failing. At this moment there are two known issues: Issue with specific LonWorks devices such as the T-Stat T7300 Too complex or long list of email addresses in notification objects Resolution Solution for issue 1: Issue with specific LonWorks devices such as the T-Stat T7300 Contact Product Support and ask for hotfix 1.5.0.4801 Solution for issue 2: Too complex or long list of email addresses in notification objects Make a search for all email address objects searching for "EmailAddress" - You can import this search object to do it. Copy all rows to this Excel sheet Check the "Count" column - it counts the characters in the "Property value" column. There's no exact max character count as it also depends on complexity of the addresses, but a good indicator is if the count is over 270. In SmartStruxure, delete the content of the objects having more than 270 characters. Carry out the upgrade (if the upgrade fails, go back to step 3 and delete the content of all objects where the count is 260) After upgrading copy the property content from the Excel sheet back to SmartStruxure

Issue When schedules, reports, trend logs, loops or any calendars are loaded, Internet Explorer is rejecting the control and will not host it. IE will then throw a "Cannot Create .net Editor" error. Product Line Andover Continuum Environment .Net 4.51 Continuum webClient Server Internet Explorer Cause Microsoft has stopped allowing IE to host controls from .net 2.0 and 1.1 by default. Resolution In order for these controls you must do the following on all of your client machines: Note: Always make a copy of the registry on the machine before making any modifications Open regedit Update the .NetFramework key as follows: On an x86 Operating System Add a DWORD attribute with the name EnableIEHosting to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework Set the value to 1 On an x64 Operating System Add a DWORD attribute with the name EnableIEHosting to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework Set the value to 1 Reboot the computer At this point you should be able to start WebClient and run the .net editors without any problems. The following Microsoft Article discusses this issue: Application Compatibility in the .NET Framework.

Issue @TriggeredTimeStamp does not always report the last time an object transitioned to an off-normal state. Environment Alarms Substitution Codes Event Notifications. Cause Both the Normal and the Reset alarm states represent conditions where the alarmed object has assumed an acceptable value and is not in alarm Reset = The object has returned to a normal state but the return to normal notification has not been acknowledged. Normal = The object has returned to a normal state and the return to normal notification has been acknowledged. The TriggeredTimeStamp value is updated only when the object transitions from a Reset Alarm State to an Alarm Alarm state. The TriggeredTimeStamp value is not updated when the object transitions from an Alarm Alarm State to a Reset Alarm state. If an object goes into alarm and that alarm event is never again acknowleged, the Triggered Time Stamp will continue to reflect that initial alarm transition time regardless of how many times the object goes into and out of an alarm state. Resolution In order to get the Triggered Time Stamp to update, the notification must be acknowleged so that the alarm can return to a Normal state (rather than Alarm State = Reset) before it transitions to Alarm. 

Issue In the past there was no way to calibrate the space temperature from a STR-150 when used with a Xenta 121 FC/HP.  Environment STR-150 Xenta 104A Xenta 120 Xenta Programmables Cause Any calibration applied to the temperature of a STR-150 had to be done downstream of the stat in the controller. In the past when the STR-150 room stat was wired up to a Xenta 121 there was no way to calibrate the space temperature as the Xenta 121 FC/HP had no kind of Temp Offset in the controller. Resolution Starting with version 1.4 (released September 2013) of the STR-150, there is a calibration feature built into the stat. This feature allows the calibration to be applied before the temperature is sent down to the controller (Example: Xenta 121 controller). Below you can find out how to check the version number of the stat and how to perform the calibration. There is not a way to upgrade older versions of the STR-150 to 1.4 or greater. Checking the STR-150 version number The version number of the stat can be found as parameter P0. View version: Push the fan and bypass button simultaneously for 2 seconds to display P0. The version number will be displayed here. Using the STR-150 Calibration Feature Enter Configuration: Push the fan and bypass button simultaneously for 2 seconds to enter P0.   In P0, hold down the bypass button and push the fan button three times to enter configuration mode. Note: the wrench symbol is lit when the STR-150 is in configuration mode.   In Configuration Mode: Press the fan button repeatedly until you reach parameter F0. Note: The two digits farthest to the left on the display show the parameter, while the two digits farthest to the right show the value.   Use the increase or decrease button to adjust the value. The offset scale ranges from 0-99 which corresponds to -5.0 to +4.9 degrees. If the STR-150 is setup for degrees C, then the offset is exact. If the STR-150 is setup for degrees F, then the offset is recalculated to a corresponding value.   Exit Configuration Mode: Push the fan and bypass button simultaneously for 2 seconds or allow the idle timeout to exit configuration mode on its own.

Issue An offline edit in PCS deploys successfully. When viewed in Workstation, the Automation Server is online, but all b3s are offline. Product Line EcoStruxure Building Operation Environment SmartStruxure 1.50 PCS AS 1.5 BACnet interface Cause The b3s have a BACnet Device ID which is different from that assigned to b3s in PCS. The BACnet device ID can not be modified in PCS after it has been assigned. Resolution It is best to modify the BACnet Device ID in Continuum: Use a BCX4040. Connect with b3 devices one by one or together Bring b3s online in Continuum Workstation Modify the BACnet Device ID for each b3 to the BACnet Device ID assigned in PCS Go back to SBO Workstation. b3s should be online.

Issue Trend log values from two or more M-bus meters under a Xenta Server are intermittently mixed up, also when viewing a trend log page in the Xenta Server's web interface. Values from meter 1 are (sometimes) logged in meter 2's trend log and/or vice versa. Environment Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 M-bus meter Cause When secondary addressing is used for the meters, there is an extra telegram sent from the Xenta Server before asking for the actual values/data. The M-bus meters then replies to this telegram so that the Xenta Server knows which secondary address belongs to which meter. In some cases (only seen with a few meters) these addresses seems to be intermittently mixed up and this will cause the issue described above.  Resolution Use primary addressing for the M-bus meters.

Issue Replaced a Niagara R2 UNC with a Jace-645 embedded with R2.  LON communications was stable at first but now it is intermittent.  Environment Niagara G3 - AX version 3.6.47 or higher Niagara R2 version 535 Cause The intermittent LON communications issue was identified and a supporting jar file in R2-535 needs to be upgraded. Resolution Replace the lonworks jar file with this updated version:   lonworks-2.301.535c

Issue Setting up Visual Verification to track who has gained access to a door using Access Expert Product Line Access Expert Environment Access Expert v3 Cause Verification of access is a common feature request in access control integrations. The following steps show how to enable and access this feature within the Access Expert v3 product. Resolution Open and connect to the instance with the required credentials Select the Access Control Tab and click on the Visual Verification button Click on the Assign Reader button to Add the respective readers and click OK The Visual Verification Window opens up with the readers that were selected from the previous step on the right side of the screen. Select the necessary readers that will be used for the verification.                    Once someone scans a card on any of the selected readers, their saved image will then be displayed    *Note* If this Window is closed the configuration for Visual Verification will be lost and will need to be recreated

Issue The MPM controller does not adjust the clock automatically when Daylight Saving Time (DST) period occurs. Product Line EcoStruxure Building Expert Environment SmartStruxureLite Multi-Purpose Manage Cause DST settings in the MPM are configured for North America. Canada and United States: Daylight saving time begins on the second Sunday of March and ends on the first Sunday of November Europe: Daylight saving time begins on the last Sunday of March and ends on the last Sunday of October Resolution In Firmware 2.15, DST properties can be configured in the Controller Configuration Object (CFG1) and/or configuration page. DST start and end configuration on month, week, weekday, hour and offset can be set. If using a firmware version older than 2.15, a script can be used to correct the issue. The script can be found here: Daylight_Saving_Time_DSC.lua

Issue Unable to find Schlage Xdriver file on Exchange Download Center. Product Line Continuum Environment Xdriver add-on Cause It is unclear of where to download the Schlage Xdriver for Continuum.  Resolution All Schlage Xdriver .xdr files, as well as their accompanying documentation, can be found in the Schlage Wireless Lock Resources Kit on the Schneider Electric Exchange Download Center.

Issue With revision 1.0.37 and later, folders under the instance within the navigation tree are no longer there.   Product Line Access Expert Environment V3 Hosted Cause The 1.0.37 release of the Keep software removed the folders under the instance within Folder Explorer. Resolution Use the corresponding tabs at the top of the window.  

Issue The sort order for data in Reports was changed in TAC Vista version 5.1.7. The newest data should be in the bottom, but in TAC Vista 5.17 the newest is in the top. When inserting a trend log to a report with period "Number of values" chosen, "Start/Stop Time" and "Period" works like they did in previous versions. Product Line TAC Vista Environment TAC Vista 5.1.7 Cause This is an error and have been fixed in hotfix 41 for TAC Vista 5.1.7. The sort order is correct in TAC Vista 5.1.8 and later versions. Resolution Install hotfix 41 for TAC Vista 5.1.7, or upgrade to TAC Vista 5.1.8 or later.

Issue Permissions on V3 Product Line Access Expert Environment Managing Permission settings for Individual Groups. Cause Limiting the Permission for users in accessing certain objects within the system for better management. Resolution Permissions can be configured for each user by following these steps: Open the API and connect to the respective instance with the relevant credentials Go to the General Configuration Tab Select the Groups Icon If creating a new Group, click the Add Group Button If modifying, select one from the list and double click to open it up Click on Add Permission and select the Object Type  Select the various check boxes to Grant or Deny access  Once completed then click on the Save & Close button to close the Editor

Issue SE(R)8000 series short and long messages Product Line EcoStruxure Building Expert, EcoStruxure Building Operation Environment SE8000 Series Room Controllers SER8000 Series Room Controllers Ex. Viconics branding VT8000 Series EcoStruxure Building Operation Cause Configuration of the SE(R)8000 series short and long messages Resolution The short and long messages are set via BACnet. Take note that the short and long messages do not hold when power to the SE8000 is turned off. This is because currently, the messages are stored in RAM. The workaround is to change the name (from the AS) and back again then save to get it to display on the unit again. Below is the procedure to change the short and long messages in EcoStruxure Building Operation. Short Message: The Short Message can be written to the SE8000 room controller by populating the "Location" Property with the message   Long Message: The Long Message can be written to the SE8000 room controller by populating the "Description" Property with the message The message however will not get displayed until the "Display Long Screen Message" has been activated. Optional: you can also choose the color of the long message background by changing the "Long Message Background Color".     Discrepancy on the text written to the device, and the text shown on the device In some cases when using non-English characters in the messages, the text on the SE8000 will not be rendered as expected. The issue is caused by SE8300 not conforming to BACnet standard in string encoding and decoding. The workaround is to set "BACnet string encoding" property of the device to "ISO 8859-1(Latin-1)", or other encoding the device supports. SE8300 claims to support BACnet protocol revision 10, which requires the conforming device to interpret Character Set 0 as UTF-8 string. In 1.9, SBO started to write to devices using Character Set 0 for unicode strings, but the SE8300 fails to decode it. Setting the "BACnet string encoding" to Latin-1 for the devices fixes the problem. 

Issue When opening a project in Workstation for Projects, Unkown Exception error will pop up Environment SmartStruxure 1.5 Workstation for Project PCS Cause This is a defect for SmartStruxure 1.5. When there is no Internet connection on this computer, this error will happen. Resolution This issue will be fixed in SmartStruxure 1.6. Currently the workaround is to obtain the Internet connection for this computer, at least when opening the project. It should be OK to remove the Internet connection after the project is opened.

Issue Boiler does not switch off. Environment DC1100 DC1400 Boiler Compensate Cause The customer has set the DC controller as shown below, the boiler does not switch off. A combined Optimiser / Compensator and the compensation is for the Boiler Only. Resolution The configuration described is classified as "Scheme F" in the data sheet - Optimisation with boiler compensation - one or two boiler control This configuration uses three sensors, the Outside, Space and Boiler Flow Header, it does not use the Compensated flow sensor. To download the complete data sheet please click HERE.

Issue In rare occurrences, technicians may remove the bottom terminal from the AS or I/O Baseplate so that a power supply can fit. The backplanes inside the baseplates are not all the same and this will not work. Visually determine which baseplate is for each module. Product Line EcoStruxure Building Operation Environment SmartStruxure Power Supply SmartStruxure Automation Server SmartStruxure I/O module Cause Incorrect baseplate will not work on the SmartStruxure modules. Resolution See picture for representation of Power Supply backplane, the other configuration is for Automation Server (and I/O modules). For more detailed information please see the Hardware Reference Guide.

Issue "Helix YUV Codecs (remove only)" shows up under Windows "add/remove programs" after Continuum is installed. What is this and is it part of Continuum? Product Line Andover Continuum Environment Continuum Cyberstation 2.02 and earlier Windows Cause A Continuum Cyberstation installation brings with it several additional programs in order to run properly. These can be seen in the "Add/Remove Programs" interface. These programs may remain installed even after an uninstall/upgrade of Continuum. Resolution Helix YUV Codecs is part of the Continuum installation. The installation file is "yuvcodecs-1.2.exe" located on the CD in "..\Continuum\ISSetupPrerequisites\{1D2652A6-D9B2-43ED-8009-987E762962A2}". The Codecs install is part of the SVG viewer program for WebClient graphics in Continuum 2.02 and earlier.  This was removed from the Continuum 2.03 installation. If desired, this program can be removed if it is no longer in use.