Building Automation Knowledge Base

Issue Performing a firmware upgrade on a reader expander module via the SP-C's web page will fail with the message: "Error - The module failed to restart in boot mode" Firmware update failure Product Line EcoStruxure Security Expert Environment SP-C, SP-RDM2, SP-MRDM2. Cause Cause 1 There was an intermittent communications fault hindering the update process. Cause 2 There are Smart Card Readers connected to the reader expander module, which are set to RS485 communication. This appears to be causing RS485 communication issues between the SP-C and the reader expander which is hindering the firmware upgrade process. Resolution For Cause 1 Run the module upgrade process again. For Cause 2 Physically remove all connected RS485 Smart Card Readers from the reader expander module being upgraded. Run the module upgrade process again. Once the reader expander firmware has been successfully upgraded, reconnect all Readers.

Issue Backing up b3 controllers to flash. Environment BACnet b3 controllers Backup to Flash Cause B3 Backup to Flash does not operate as expected. Resolution The b3 controller Backup to Flash operates as follows; System variables that indicate the status of Flash / Backup. StatusBackup – Indicates if backup is needed, has been done, or is in progress. StatusFlash - Indicates that the flash is empty, valid or has failed. LastBackup – Indicates the time and data of the last backup.   Backup to Flash Operation. Downloading a controller will clear the flash memory. Resetting a controller will clear the flash memory. A download to a controller which fails, will clear the flash memory. Setting the controller "RestartMode" variable to Cool Start, will reload the controller from flash memory on power up, assuming there is a valid backup available..   Downloading a single object to the controller does not clear the flash memory.

   

Issue TAC EGWP 120 is obsolete and needs be replaced. Product Line Field Devices Environment 5122781000 TAC EGWP 120 5123106010 STP100-150 Cause Obsolete product needs replacement. Resolution TAC EGWP 120 (5122781000) is replaced by STP100-150 (5123106010)

Issue Where can information for Berger Lahr be found, as they do not appear to be Buildings Business products. Product Line Field Devices Environment Non Buildings Business Products Berger Lahr Industrial Drives, Motors and Actuators. Cause Berger Lahr is not a Buildings Business product. Resolution Email: info@schneider-electric-motion.com Webpage: Berger Lahr   Brushless DC Drives Brushless DC drive systems are an economical solution for many motion tasks. With compact and powerful motors and matching drives, they offer a wide range of options for appliances in industrial automation. Brushless DC drives are available in two versions: BLP14 with CANopen fieldbus interface and BLV14 with analog interface (5V or 10V). Both open-loop and closed-loop operation is possible. The motors are available in two sizes: BDM 4: with flange size 42mm, in two lengths with nominal power from 56W to 95W and nominal torque from 0.13Nm to 0.22Nm BDM 7: with flange size 66mm, in four lengths with nominal power from 120W to 370W and nominal torque from 0.24Nm to 0.8Nm Actuators Actuators position flaps, valves, or sliders with great precision. The compact actuator housing contains a motor, a gearbox and a control unit. Three different types of actuators are available to respond to your specific positioning challenge: STE = electronic actuator STA = actuator with cams and relay STM = actuator with cams Tin Can Motors Tin can motors are robust, energy-efficient and work with great precision. The motors can be operated without additional control electronics with 50Hz or 60Hz alternating mains voltage. Our comprehensive range provides the right motor to meet your specific requirements. These motors are available as 2-phase stepper motors or as synchronous motors and can be used for HVAC actuators, medical devices, pumps, and a wide range of other mechanical devices.

Issue Customer wants to know if he gets any different functionality when updating from a MNL-20RS1 to a MNL-20RS3 in terms of the LonMark profile. Likewise, what is the difference between the MNL-10RS2 and MNL-10RS4 LonMark profiles. Environment MNL-xxRS1 / MNL-xxRS3 controllers MNL-xxRS2 / MNL-xxRS4 controllers Cause LonMark Profile update was required when the hardware was revised so that we could maintain our LonMark registration status on the controllers This same change applies to the RS2 and RS4 profiles Resolution The profiles for all the standard MNL-xx series controllers (MNL-50, MNL-100, MNL-110, MNL-130, MNL-150, MNL-200 and MNL-Vxx) are documented in Appendix B of the WorkPlace Tech Tool 4.0 Engineering Guide, F-27254. Specifically, the differences in the MNL-xxRS1 and MNL-xxRS3 profiles are as follows: NV Index # 23 MNL-xxRS1: Name: nvoSECAlarm Type:SNVT_str_asc MNL-xxRS3: Name: nvoDeviceAlarm Type:SNVT_str_asc NV Index # 58 MNL-xxRS1: Name: nciSECModelNum Type:SNVT_str_asc MNL-xxRS3: Name: nvoDeviceInfo Type:SNVT_str_asc Likewise, the differences in the RS2 and RS4 profiles are as follows: NV Index # 25 MNL-xxRS2: Name: nvoSECAlarm Type:SNVT_str_asc MNL-xxRS4: Name: nvoDeviceAlarm Type:SNVT_str_asc NV Index # 60 MNL-xxRS2: Name: nciSECModelNum Type:SNVT_str_asc MNL-xxRS4: Name: nvoDeviceInfo Type:SNVT_str_asc The corresponding differences exist in the Version 2 and Version 3 profiles for the MNL-xxRFp, MNL-xxRHp, MNL-xxRRp, MNL-V1RVp, MNL-V2RVp and MNL-V3RVp controllers where "p" corresponds to the Version number 2 or 3.

Issue Can Value Transfer Settings be used to control the frequency at which a value is transferred over the Infinet bus? Product Line EcoStruxure Building Operation, Andover Continuum Environment Continuum i2 Controller Cause There is a need to control the frequency at which a value is transferred from one Infinet controller to another. Resolution Whether or not the Value Transfer Settings determine the value transfer rate depends on the type of reference used. When the Continuum to EBO transition process was developed, features and functionality were added to the Automation Server so that it would accommodate an existing controller protocol. Neither the Infinet controllers nor the Infinet protocol was substantially redesigned in order to work with Automation Servers. Infinet controllers have never had a Value Transfer Setting capability and it was not added when the Continuum Transition process was developed. The primary method of value transfer in Infinet controllers is the Import/Export tables. In order to enter a point into the Import Export table of a controller, the point has to be bound to an Infinet Script program or to an Infinity Alarm notification. You can find more information on the I/E functionality in the following Knowledge base article. Details on Continuum Import/Export (IE) System The Import/Export system is a highly efficient means of value transfer that is base value change. If you chose to bypass the Import/Export capability, the only method available to you to control the frequency at which values are transferred over the Infinet bus is to read these values via a program that incorporates some form of throttling to slow down the polling rate.

Issue Feature overview and tested platforms, operating systems, databases, and web browsers for AX/G3 version 3.8. Product Line TAC IA Series Environment Niagara AX / G3 3.8 Cause Field inquiries Resolution View the PDF files below.  They were obtained from Niagara-Central.com.  Feature Overview Test Summary Windows 8.1 is also supported (not listed in the Test Summary).

Issue Need to use a controller that has no BACnet functionality due to network security limitations on site. Environment Continuum bCX1-CR-INF (bCX9640) Cause A customer has a site with restrictive network security requirements and BACnet devices (or any other open protocol) are not allowed. Resolution The bCX9640 is an Infinet protocol controller only. This version of the bCX firmware does not have the BACnet stack installed, and there are no BACnet points able to be created in this controller. You will be fine to use this controller where BACnet support is not required or allowed.

Issue What is spacing for the screw terminal blocks of the SP-MRDM2 2 Door Mini Expander, and what do the terminal blocks look like? Product Line Security Expert Environment Security Expert 2 Door Mini Expander Cause Screw terminal block details needed for ordering spare parts. Resolution The 2 Door Mini Expander uses two different screw terminal blocks. The lower is the normal terminal with 5.08 mm pitch labelled 2EDGK, and the upper is upside down, also 5.08 mm pitch and labelled 2EDGKF. See also data on the manufacturer's website.

Issue An error message is displayed when trying to save changes to a Programmable Xenta in Menta Editor. The error message is: Tam32 Save Error Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index (E) Error message trying to save changes in Menta Editor Product Line EcoStruxure Building Operation Environment Building Operation Workstation 3.0.2 or earlier Xenta 281 Xenta 301 Xenta 401 Cause A defect in Menta Editor causes this error to be displayed when a SNVT name in the Menta application is identical to the programmable Xenta device name.  An example of this is shown below: Resolution This problem has been fixed in Hotfix 3.0.2.2500 and the fix is included in version 3.1. For earlier versions there are two ways to resolve this problem; Either a) rename the Xenta device, or b) rename the SNVT. a) Renaming the Xenta device In Workstation right click the Xenta device and choose Rename Click OK Now you can edit the Xenta in Menta Editor without getting the error message b) Renaming the SNVT Right click the Xenta device and choose Edit In Menta Editor double click the block with the SNVT binding to edit the block Click the Bind... button to edit the binding Change the name, click OK to close the dialogs and Save the changes

Issue Most systems have an Overview Graphic of the whole building.  The user then navigates from this graphic to specific floors and rooms of interest. If the Workspace is configured incorrectly, navigating to a newly selected graphic does not work as expected. The overview graphic does not disappear and the new graphic is forced to open very small at the edge of the screen. Product Line Building Operation Enterprise Server Environment Workspaces Cause The standard Administration and Engineering Workspaces used in EBO contain a Work Area Window (WAW) which is necessary 'space' to show a selected graphic/trend/schedule If an Overview Graphic Pane is created in a Customer Workspace and this graphic takes up most of the screen, there is no space left to show the new object which the customer wishes to see Note: The Overview Graphic 'Building' is now shown in a Graphic Viewer only   When the system tries to open a new graphic, there is not space to open it in, The graphic is forced to open at the very edge of the screen and is therefore very small. Resolution General information about creating and using Graphic Panes, Work Area Windows and Panel Components can be found in the EBO webhelp, But for specific information on how to prevent a graphic opening at the edge of the screen see below.  Rather than adding a Graphic Pane to the Workspace to show the Overview Graphic add a Work Area Window (WAW) instead. Next, define the required Overview graphic as the initial path for the WAW on startup so the Overview graphic opens at user log on. Note: The Overview graphic 'Building' is now shown in the WAW rather than the Graphic Viewer. Graphics will always close themselves on navigation to the next object by default when used with a WAW (this can be changed). As soon as the user needs to navigate away from the overview page to a new graphic/schedule/trend, the system can use the WAW which will then use most of the screen as the 'space' to show it. In this case, as soon as the link to the next graphic 'Floor' is pressed, the first graphic 'Building' closes according to its default and the new object is shown in its place.

Issue Site has a personnel database with about 10K records, the site is switching to dual credentials and has configured the Personnel Manager to use HIDCorp1000 as the default for card type 2 and xxx as the default for Site Code 2. Problem is when going to change the personnel the Card Type 2 field still comes up with Infinity37 and Site Code 2 of 0 instead of the configured defaults. Environment CyberStation Cause Any existing personnel in the database will come up with Infinity37 for the card number 2 and 0 for the site code 2 as those were the values populated in the SQL database for those fields when the system was configured for only one credential. When creating NEW personnel objects the fields show the configured default values. Resolution When creating NEW personnel objects the fields show the configured default values.

Issue Unable to use Windows domain login to WebReports. Environment StruxureWare Building Operation WebReports Cause Windows domain login is not currently a feature that can be used with WebReports. Resolution The use of Windows domain login to WebReports has been entered as a future enhancement request but it is not currently assigned to a version.  UPDATE: As of EBO 2.0 the change request has NOT yet been implemented.

Issue Changing readers from ABA to Wiegand and getting card not in database Environment Continuum ACX7xx ACX700 Cause When you change card readers from ABA to Wiegand on a ACX7xx controller you need to make sure you also change the switch and jumper positions also Resolution You will need to remove the cover of the ACX7xx to reveal the dip switches and the resistor like jumpers that you will need to change, please see the attached document for how to make these changes . Link

Issue Customer wants to connect MODbus meter to Comm port 4 on a Netcontroller 2 but needs to know which pins to use Environment Continuum Netcontroller 2 NC2 Cause Customer wants to know Netcontroller 2 pinouts Resolution The Netcontroller 2 has a number of different connection types including RS485, RS232, RS422 and RJ11 Please see attached document for a full list of the Netcontroller 2 pinout configurations Link

Issue WorkStation crashes when opening some TGML graphic pages following a windows update Product Line EcoStruxure Building Operation Environment Windows 7 64 bit SBO v1.6.1.5000 with KB3045171 windows update Cause Windows Security update KB3045171 can cause WorkStation to crash if some fonts have been used within the TGML graphic The example seen was using font "Dotum" Security Update for Windows 7 for x64-based Systems (KB3045171) http://support.microsoft.com/kb/3045171 If this does not resolve your issue see Graphics Editor will not open and causes a font related error. Resolution Microsoft have produced a fix for this problem (KB3065979) see https://support.microsoft.com/en-us/kb/3065979 The PC must be rebooted following this update before the problem is corrected.

Issue Who to contact for Continuum - Easy-Lobby integration support.  Environment Continuum Security Cause Unsure of who to contact for Continuum - Easy-Lobby integration support.  Resolution The Continuum - EasyLobby integration is supported directly by HID - EasyLobby.     For sales or technical support: EasyLobby support email is support@easylobby.com . U.S. support phone number 866-607-7339 (option 8). International support phone number: +1-949-732-2000, option 3, then option 8.   If you have EasyLobby sales questions, or need a quote or a web demo, please call 781-455-8558 or contact jmooradian@hidglobal.com, jmurzycki@hidglobal.com, vrowan@hidglobal.com or your HID sales rep If you need EasyLobby technical support, please contact support@easylobby.com or call the HID tech support line at 866-607-7339 and select Option 8 If you are placing an EasyLobby order, please resend it to easylobby-sales@hidglobal.com or fax it to 781-455-6766 If you have questions about the status of an order already placed, please contact Customer Service vrowan@hidglobal.com, kzarrow@hidglobal.com If you have questions about adding a feature or doing custom engineering, please contact Product Management nwahlander@hidglobal.com

Issue Need to use the Automation Server port log to view BACnet MS/TP communication Product Line EcoStruxure Building Operation Environment Building Operation Automation Server Premium Building Operation Automation Server Bundled Cause Need to capture BACnet MS/TP traffic for troubleshooting. Resolution In EBO 2024 (V6.0) and higher, there is an integrated packet capture feature available in EBO Servers with BACnet Interfaces. This feature allows users to create packet captures that record the BACnet messages that are visible to the EBO Server’s BACnet/IP and BACnet MS/TP networks. Refer to: Packet Captures in EcoStruxure Building Operation

Issue Display the Text Value for a multistate point (e.g. enumerated SNVT) instead of the numerical value in a TAC Vista Graphic page. Product Line TAC Vista Environment Vista IV OGC Graphics Editor Cause A digital presentation will display the integer value of the enumerated SNVT by default (1, 2, 3...). Many structured SNVT types use default enumerations (e.g. HVAC_HEAT, HVAC_COOL, HVAC_OFF). Rather than setting up a customer dynamic text value each time, the standard enumerations can be displayed. Resolution Add a digital presentation to the Graphic page Browse in multistate point. Check the check box "Presentation format." Now the text will be displayed instead on the numerical value. To define custom texts for use with multiple points, see Creating custom Multi-state Text definitions.