Building Automation Knowledge Base

Issue Would like the ability to disable "Ping Failed" alarms in G3 Environment Tridium Niagara G3 (AX) network controllers (ENC, JACE-645, JACE6, JACE7) Cause Network communication issues sometimes causes device to timeout on a ping request, but quickly recovers. This failure causes an unnecessary alarm to be generated. Resolution 1.  Go to the Property Sheet of the appropriate network (e.g.. Lonworks Network, Bacnet Network) 2.  Expand Monitor, and set the Alarm on Failure field to False. 3.  Click Save  

Issue I/A Series R2 station on a JACE-603/645 platform indicates ENGINE WATCHDOG TIMEOUT STACK DUMP and App Failed when attempting to start the station.  Reboot of the station fails to correct the issue.  Example startup output window for the JACE-645 shown below: Tridium Niagara Station, r2.301.535.v1 [MedPlace1] MESSAGE: ErrorLogService installed [/MedPlace1/services/ErrorLogService] {lon} Maximum londevices = 27 Start service: ControlEngineService [3] ControlEngineService Start service: UiEngineService [12] UiEngineService Start service: NotificationService [6] NotificationService Start service: LogService [5] LogService Start service: AuditLogService [2] AuditLogService Start service: ErrorLogService [4] ErrorLogService Start service: WebUiService [13] WebUiService Start service: MailService [17] MailService DEBUG: setDebug: JavaMail version 1.4.4 Start service: LonWorksService [15] LonWorksService >>> Lon Driver opened! Start service: BACnetService [14] BACnetService ENGINE WATCHDOG TIMEOUT STACK DUMP @ Tue Mar 18 15:29:19 GMT-05:00 2014 App Failed Environment I/A Series R2, I/A Series G3, JACE-603, JACE-645 Cause The issue is related to an improper implementation of the JRE files required by the R2 mail service on the embedded platform.  A JACE-603/645 will fail if the platform is commissioned for I/A Series R2 use with distribution files provided in I/A Series G3 versions 3.7.46, 3.7.106, and 3.8.37. Resolution The issue can be corrected by installing a clean distribution and commissioning the platform with I/A Series G3 version 3.6.47.

Issue In a Niagara G3 station with a BACnet MSTP integration, the following error appears in the application director output: Transaction Timed out! invokeId 223 TransactionException in poll() for BacnetDevice {Kens_RM106}:pl=PollList [Kens_RM106 device:7219 3000:13] 196608025 {160} 10 PLEs) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) DCMD_MSTP_TX_FRAME returned 11 (errno 3) .... Hundreds & hundreds more Environment Niagara G3 Cause MSTP trunk / traffic issues Resolution See the discussion about an identical issue at Niagara-Central.com.  Here is a link:  https://community.niagara-central.com/ord?portal:/discussion/DiscussionThread/11258

Issue When looking at a revision 11 MicroSmart controller point with Operator Interface (OPRIF), setpoint changes made from another location (i.e. a Niagara graphic) do not update on the screen.  However, the HVAC equipment responds properly to the setpoint change. Environment Operator Interface 11.x (OPRIF) DMS MicroSmart controller with revision 11 firmware Cause If an up-to-date backup of the controller's database exists on the host computer, OPRIF does not upload the controller.  It uses the backup and simply transmits any changes down to the controller. If a change is made from another location, like a Niagara graphic, they are not reflected on the OPRIF screen because it's looking at a database backup file. Resolution To view the setpoint change, upload the controller.

Issue This is the description of what the Continuum Analyzer does that is also available on the service release CD. Product Line Andover Continuum Environment Continuum Analyzer Windows 7 Windows 2003 Windows Server 2008 Cause The Continuum Analyzer description and what it does is in the service release CD. Resolution The Continuum Analyzer is designed to provide installers and troubleshooters with a point of reference for discovering problem areas within their installations. The software is proactive in that it enables you to 'clean' orphaned and mismatched objects from the database, thereby recovering from a minimal amount of database corruption. Continuum Analyzer also performs a system information check and provides full reporting on all aspects of the installation, as well as alerts regarding deficiencies. This article is provided to you as a guideline and an operational reference for use of the Continuum Analyzer. It is of the utmost importance that you review the current, Continuum Cyberstation Release Notes, before using this product. This document refers to specific changes made to the operation of the Cyberstation software in its new release. Installation Requirements Continuum Cyberstation software must also be installed on the given computer, and meet its hardware and software specifications as detailed in the, Continuum Getting Started Guide. Uninstall Previous Analyzer Versions If a previous revision of Continuum Analyzer is installed on the computer, it is important to remove it before installing a newer version. This is easily accomplished using the following procedure. Close all open applications before proceeding. Select Start, then Settings, and then Control Panel. Once inside the Control Panel, select the Add/Remove Software icon and select, Continuum Analyzer. When prompted, select Yes to remove all application components, and Remove All once uninstall begins. Close the Add/Remove applet and reboot your system. You may now proceed with installation of a newer version, below. Setup Procedure Close all open applications before proceeding. Setup will begin unpacking necessary files. Older versions of Windows workstation may require system file upgrades. An alert message will display asking you to confirm this operation. You may be required to reboot your computer. If this is the case, rerun setup after the computer restarts. The installation awareness screen prompts you for the location in which the files are installed. We recommend allowing the default installation directory. (C:\Program Files\Continuum\ContinuumUtilities\Continuum_Analyzer) When you are satisfied with the location, click on the large installation icon towards the left of the dialogue box. Figure One, below, details this screen. When prompted for creation of the program group in which the Analyzer will reside, select the default, or choose an existing program group for these icons. Setup will copy the necessary files into the installation directory on the hard drive. When finished, you are prompted that setup is complete and need to click, OK to verify. Setup is complete. Operation Modes Continuum Cyberstation software allows the user to define the type of database used to house the system information. Typical system configurations rely on the implementation of Microsoft SQL Server. LAN Mode This operating mode provides the user with all available information about the system installation, including SQL parameters used on the database server. This additional information can help reconcile issues that exist within the configuration of the SQL server. Stand Alone This mode diagnoses problems and lends the equivalent information presented through SQL implementation. Password Confirmation Continuum Analyzer requires the user to enter a password before launching the GUI. The password used should match the password of the SQL account used by Continuum. If all installation defaults were followed, the password is, pyramid97. Navigating the Interface The Analyzer uses an intuitive interface to easily collect and return data from Continuum installations. The interface is broken into 5 parts; a function toolbar, system toolbar, status prompt, report explorer, and the report window. Appendix B contains a screen shot of the analyzer display. Several toolbars located throughout the graphical interface permit point and click operation of the software. Function Toolbar This toolbar is located to the upper-left hand side of the Analyzer interface. Each toolbar feature is explained below. Button descriptions will also appear When the mouse is held idle over the selected feature. Save Reports to File Activating this button saves the Main and Suspect generated report to a *.csv file at the location specified by the user. The Save dialogue box prompts the user for the report destination. This file is required for proper technical support from Andover Controls Corp. Word Wrap This button wraps each line of output data to fit within the parameters of the display window. Run Begins data collection on the system. Clean The clean button removes references to suspect objects found during the initial database screening. After the items are removed from the database, the analyzer is automatically rerun to ensure that no remaining corruption exists. System Toolbar The System Toolbar features shortcuts to many of the same features as the Function Toolbar. This feature group also contains a button to close the program and a display window that monitors the integrity of the database and indicates corruption when found. Status Prompt The analyzer status prompt displays the progress of a current session. During an active session, the status indicator bar will fill to indicate that the analyzer has completed its review of the system. It may take Analyzer several minutes to complete its system scan. The status bar is located in the center of the system toolbar. Please refer to figure four for a detail of the system toolbar and status prompt. Log Selection Windows Analyzer allows a technician to specify log collection dates independently for both the Error and Activity logs using calendar menus as detailed below. This feature is helpful in reducing the amount of time necessary for the completion of an Analyzer scan, and identifying the point at which problems first occurred. The user may choose not to report on log collection by selecting one day ahead of the present date. Report Explorer Navigation The report explorer allows navigation through each report feature in a manner akin to the windows explorer file manager found in Windows. Navigate by double clicking on the desired report folder and selecting the appropriate report from the file list. Figure Seven details the report explorer below. The root of the Analyzer’s report explorer indicates to the user the mode in which the analyzer is running (LAN Mode or Stand Alone.) Each folder displayed below the root contains a report(s) on the system. Continuum Logs These log reports display two kinds of activity. The first report, Continuum Activity, displays all system user actions on the system during the period specified in the calendar selection window. The second report, Continuum Errors, shows the continuum error log during the dates specified within the parameters of the calendar selection window. Cyberstations This report area displays each workstation’s properties as detailed by the device table, and all Plain English programs that are installed at each workstation. Database Integrity This report allows a technician the ability to quickly identify an area of data corruption within the various link tables of the Continuum database. Each of the following reports specifies the type of link verified and a numeric display of how many broken links appear within the system. Typically, broken links detected by Continuum Analyzer can be cleaned from the system, using the clean feature. The clean feature removes all references to the orphaned item. Distributions Pending and failed distributions are monitored from within this report area. Failed distributions detail the name of the object and its status. The Pending distributions monitor the type, content, and numeric statistic of distributions waiting to complete. Field Devices Field device reports detect the variable parameters for different classes of objects configured in the field. This gives the technician a holistic reference point for determining any conflicting parameters within the system. Please refer below for information regarding the content of each report. Report Name Description CommPorts Infinity Controller communication port configurations InfinityControllers CX controller parameters InfinityInfinetControllers Defined parameters for infinet devices InfinityPrograms Details programs that reside on the CX controllers IOU Modules Parameters for each IOU configured within the system Networks Network Object parameters Each field device report displays values as an enumeration from within the database. Troubleshooting with the Analyzer requires that a technician be able to correlate each reported value of an attribute to the software value that Continuum displays within the object editor. Please refer to Appendix A for a definition and value range for variables discussed in the reports. General Continuum These detail all Continuum installation parameters, providing the technician with the ability to troubleshoot any problems that might occur at the software installation level. Aspects covered in this report segment include ODBC client connector details, connection status, domain user account information, and installation path. Workstation Workstation reports provide system information on the workstation hardware and operating system configuration. These reports help clarify any Continuum software compliance issues. SQL Server SQL Configuration information is provided through two reports, Database Configuration and Server Configuration. These values are used to trace possible problems back to a server configuration variable. Summary Report The summary report issues system details that provide a quick overview of the Continuum configuration in use at a particular facility. One set of data in particular is worth discussion, as the values here can lead to problems with the workstation performance of the system. The summary includes a section labeled Windows Registry Check. If the software installation was performed correctly, registry keys will be entered in the Local Machine hive of the registry. It is possible under abnormal installation circumstances that these registry entries are placed under the Current User hive. The Analyzer retrieves these registry values and displays them as follows in figure eight. If the machine is properly configured, the values will only display once, to the right side of the definition text. This indicates their presence in the appropriate location. If the values are located on the left-hand side of the definition text, the installation did not put the appropriate values in the correct location. Suspect Objects The suspect object report details three categories of data corruption detected within the database. If data corruption is discovered, the system toolbar and the report explorer will indicate such. The first category, Suspect Objects Correctable, contains any corrupt data that the Analyzer can repair using the clean command. Suspect Objects Manual Fix details configuration issues which require manually editing the erroneous variable. The final category, Suspect Objects Uncorrectable requires the assistance of Andover Controls TSD staff to remedy the problems. Please be aware that support for these issues requires that ACC TSD staff have a copy of the Analyzer report from the system in question. Figure nine details the report explorer icon displayed when corruption is detected. It is recommended that all suspect objects are saved as a file to aid in recreating the broken link objects. The Clean button is used after the Save Suspect Objects to File button to remove the broken objects from the database. Analyzer Report This report details all areas of data collection and is saved in a *.csv format. You may save a report in one of the following ways. Saving your Analyzer Reports The Continuum Analyzer generates two reports that can be saved for review. Both reports can be saved simultaneously, or individually using the reports menu option at the top of the Analyzer window. Suspect Objects Report The suspect object report is optionally generated when data corruption is discovered. If you do not see the visual indicators that suspect objects are present in the system, then there is no report to generate. However, if corruption is present, the report must be saved. All Cyberstation Workstations Invoke the analyzer by selecting the Continuum Analyzer icon from the Start Menu. You are prompted for a password. This password is the same as the password used to access your database from the ODBC connector. Figure Ten displays the password dialog box. If Continuum was installed with the default options, the database login password is Pyramid97. You may change the start date for log collection through the calendar menu, if necessary. Select, “Run” to begin analysis. The program will run for several seconds, an active display in the system toolbar details its progress. Save the report generated by each machine. Repair Data Corruption IMPORTANT! Note that this is option is NOT always available! If the Continuum Analyzer reports that data corruption was found, a stop sign icon appears in the report explorer and a Database Integrity Failed message appears at the top of the system toolbar. Select the option button labeled, Save Suspect Objects to File. Upon completion, select the Clean option. You’ll notice that after this button is selected, the database is cleaned and the Analyzer is run a second time, to ensure there is no remaining corruption within the database. Submit Analyzer Report The Continuum Analyzer Reports should be sent to our technical support department before upgrading if uncorrectable errors were found. Schneider Electric has a technical support address designed for this purpose. The email should include the following information. Subject: / Body: Dealership name Site Name File attachments: Analyzer Reports (each workstation) File attachments: Suspect Object Reports (each workstation) This email should be sent to Product Support All workstation analyzer reports and suspect object reports should be attached to a single email. Run Analyzer before Upgrade The Analyzer must be run again prior to the upgrade installation to verify that database integrity is stable. Using the Primary Access Server, run the analyzer, save the generated reports, and clean any suspect objects if necessary. Uninstall Continuum Make a note of the workstation and database settings within the Database Initialization Program. Uninstall earlier versions of Continuum from the workstations through the Add/Remove Programs icon located in the Control Panel. Select Continuum from the menu of programs and follow the automated procedure. You must reboot after un-installing. Install Continuum Refer to the Continuum Cyberstation Getting Started Guide for installation instructions. The first workstation upgraded should use the database initialization program to UPDATE an existing database. Ensure that the server name and authentication information is entered correctly. Verify that the workstation settings are IDENTICAL to those used in the previous installation of Continuum Cyberstation. Rerun Continuum Analyzer Rerun the Continuum Analyzer to verify that data within the tables is stable, and that all workstation settings are properly configured. If database corruption is present again, we recommend contacting our Technical Support Department for further information. Appendix A Field Translation Guide The Continuum Analyzer report references the exact table and column names used within the Continuum database. This appended reference should be used when trying to correlate settings and values from the analyzer report against values within the Cyberstation software. Please direct any further inquires to our Technical Support Department. Field Name Description Typical Values Autostart autostart on/off True/False Baud Enumerated value starting with 0 for 300. Each rate of speed has its own enumerated value 0=300, 1=1200, 2=2400, 3=4800, 4=9600 and 5=19.2 Command Whether a program can execute from command line on/off DefaultBaud When a Commport is created it is assigned the default baud of 9600 which is equal to 4 0=300, 1=1200, 2=2400, 3=4800, 4=9600 and 5=19.2 DefaultMode This is the mode the CommPort is configured to use. i.e., Infinet, printer 0=Printer, 2=Command, 3=Infinet, 5=Autoset, 6=Tanknet,11=Xdriver Description Text string entered into the object description field user defined DialPrefix Standard Commport initialization settings ATDT DialSuffix Standard Commport initialization settings |013 DirectConnect User selectable checkbox definition True or False. True if checkbox is selected Filesize Size of the program file in bytes 18 FlowControl UART data stream control 0=NoFlowControl, 1=XonXoff, 2=CtsRts, 3=XonXoffCtsRts HangUpCmd Standard Commport termination request @@@+++@@@ATH0|013 InfinetID Unique Identifier assigned to infinet controllers   IOU Number reference ID attached to the current module 1-32 Location Controller to which an object is attached User Defined MaxResponse Time Maximum amount of time to wait for a response in seconds Default 5 Sec ModelName Value obtained from hardware hardware/software type and version ModemInit Modem initialization string AT&F|013@@@@@@@@@@@ATEQ1&C1&D3S1S0=1W3\J\Q3%C1&W|013 Module ID Unique module identifier; hardware encoded in each module Not user Definable NetworkID Workstation's Energy Net identification number 1-190. 1-64 are recognized by the CXs and NetController. Ids above 64 are recognized by Workstations only. NetworkUTCOffset GMT offset of the network objects User Defined in minutes Owner Name of attached controller object User Defined Parity Standard Commport entries 0 PortNum Enumerated value of commport number to which a device is attached 0=1, 1=2, 2-3, 3=4 PrimaryAccessLogger Workstation computer designated as the primary access server 0=Not Primary, 1=Primary ProbeTime Probe Frequency time between TTL pings Default 60 Sec Program ID Internal Firmware reference ID 4th digit from the left represents IOU firmware revision SecondaryAccessLogger Workstation computer designated as the secondary access server 0=Not Secondary, 1 = Secondary SendToACX Whether or not the object must be sent to the corresponding ACX controller 0/1 SendToCX Whether or not the object must be sent to the corresponding controller 0/1 SerialNum Serial number of the network controller object 527853 Shareflag Whether program is able to run on any workstation on/off State Determines whether an object is active within the system or not TRUE StopBits Commport initialization setting 0 SynchDB Whether or not the object must be synchronized with the database 0/1 TerminalType Determines Commport emulation 0=VT100, 1=VT220, 2=Wyse TimeOutValue No user definition 0 TrackCxd Changed through checkbox selection True or False. True if checkbox is selected UiName Object name in database User Defined UTCOffset Number of minutes offset from GMT User Defined in minutes VersionNum Firmware revision number Ex. 1.53x, 1.2x, 2.1x, 4.5x XDriverFile Location of and name of any Xdriver assigned to the port User Defined

Issue Can't receive "Power Factor" values from ABB's M-bus meters. Environment Xenta 913 Xenta 701 Xenta 711 Xenta 721 Xenta 731 Cause Earlier versions of X700/ X913 system software did not support M-bus manufacturer specific data that contains extra status information in the VIFE Resolution For Xenta 700, there is a hotfix for v5.1.8 that adds support for this type (also included in v5.1.9 and later) . For Xenta 913, v5.1.9 and later includes this hotfix.

Issue R2 UNC won't boot and standard output shows the following: FATAL: Cannot boot station from sns java.lang.NoClassDefFoundError: tridium/foundation/prism/Subscription Environment R2 UNC's Cause Typical of corruption to the operating system Resolution  To recover: reinstall the OS, nre and modules and then the station. 

Issue User keeps getting re-prompted for login for each station even though using virtual domain. Each station file has been edited to include the cookieDomain slot.  Also, each station’s “hosts” file has mapped every station’s IP address in the virtual domain to their hostnames. Everything seems to be configured correctly. Environment Niagara R2 Cause Host (station) names contained underscores. The hostname cannot contain underscores. Resolution The station must be renamed without underscores. Change the hostname to match the new station name.

Issue Trying to configure door on AC1 to use HID Corporate 1000 and custom card and getting error... “Can't configure HID Corp 1000 and Custom formats simultaneously on AC1 module” Environment CyberStation CX9680 Cause Since the AC1 module only supports one custom format and the HID_1000_35 requires it, the controller can not allow the user the configure a door for both HID_1000_35 and Custom at the same time. An attempt to violate the rule above shall result in the following error: “Can’t configure HID Corp 1000 and Custom formats simultaneously on AC1 module” Resolution If door is on AC1 then Custom and HIDCorp 1000 can't be selected simultaneously. Also, if the AccessFormat is present the doors cant be configured for HIDCorp1000 regardless of the module type. SOLUTIONS: Replace the AC1 with the AC1Plus. Use AccessFormat2 (or 3 or 4) for the custom cards if using AC1Plus modules

Issue Which format will emails be transmitted in? Environment SmartStruxure Cause IT departments may need to know the format of system generated emails, especially if they use an internal mail server. Resolution The email is sent with text/plain;charset=utf-8 encoding with Transfer-Encoding: quoted-printable.

Issue Sending nvoSpaceTemp to nviSpaceTemp in TAC Xenta 102-AX does not work even if we are using SCPTmaxSendTime and SCPTmaxrcvTime. Environment TAC Xenta 102-AX Cause SCPTmaxSendTime of 60 means that the value is sent at least once every 60 second. SCPTminSendTime of 10 means that you could not send more often than once every 10th second. But, SCPTmaxRcvTime of 10 means that if the device has not got a new update within 10 seconds of the latest value, the value goes back to default value.   Resolution SCPTmaxRcvTime in the receiver has to be set to at least longer than the SCPTmaxSendTime in the sender, to avoid timing issues, there the receiver resets its value before the sender sends out a new value.  

Issue The specification data sheet for the ETR803 sensor shows a supply voltage connection and controller input connection but does not provide any further details for reading the setpoint. Environment ETR803 temperature sensor with setpoint Cause ETR803 is being used for space temperature sensing and needs to be able to read the setpoint in an I/A Series controller. Resolution The ETR803 Space Temperature Sensor with setpoint adjuster is marketed as an equivalent for the TS-90250-850 and similar device. The space temperature sensor is a 10kohm type 3 thermistor with an 11kohm shunt resistor.  This space temperature sensor can be read by any of the I/A Series controllers that support the 10k thermistor with 11k shunt resistor. The setpoint adjuster is an uncalibrated Cool / Warm slider that be read by the I/A series controller as a voltage input. Note: Unlike other ETR sensors, voltage detailed below must be applied to the ETR803 setpoint (SP+ and common) for proper operation. The power source can be the 5.1VDC power from the MNL-800 or the 20VDC source, with a 4500 ohm series resistor, from the MNB-1000. For the other controllers, an AO can be configured as a 5 VDC output.  This voltage source is connected to the SP+ terminal on the ETR803. The SPST output of the ETR803 is then connected to a spare analog input on the controller. This analog input is configured to read a voltage in the range of 1.2 to 4.8 volts. Since the ETR803 setpoint slider is uncalibrated, being labeled "Cool" on the left and "Warm" on the right, the AO reading this value could be configured to read an absolute temperature range such as 50 to 90 degrees or could be configured as a +/- setpoint offset.

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 Controller locks up on configuration of the Modbus TCP-IP XDriver. Environment Continuum Controller Cause The Device Comm Status point was created as an InfinityString instead of InfinityNumeric Resolution Delete the incorrect Device Comm Status point and re-create it appropriately as an InfinityNumeric.

Issue  The Modbus TCP-IP XDriver can function as either a TCP Client or a TCP Server but not both at the same time. Environment Cyberstation Continuum Controllers Cause Documentation Resolution  It is the XDriver points themselves that define the mode of the driver, in every point created, Parameter 2 should be set to either “0” for Client Mode OR to “1” for Server mode. You can’t use both in one driver. ALSO, in Client mode you need to create the Remote Device Status point, one per server, but it is Parameter 2 in the points that determines the client/ Server mode. QUESTION: If the XDriver can only operate in one mode (client or server) why does each point need to be configured with the mode type? ANSWER: There is a historical reason for this, the original design envisioned the support of both client and server points simultaneously, but for reasons that are well beyond the scope of this article this was changed to support only one mode at a time.

Issue Require sample code to configure a Door for the "two man" rule, where two valid card reads are required before a door is opened. Environment Continuum Access Control ACX5720 ACX5740 Cause Require sample code to configure a Door for the "two man" rule. Resolution For this "two man" rule you would need to take control from the Door object and do this through a Plain English program. Make sure to remove the door status input from the Door and define this as an Infinity Input if you want to use it within the Door program, otherwise the door will never show a "ValidAccess" signal for the program to work as it will be waiting for someone to walk through the Door first. See below example code of one way to accomplish this.   ========== Sample Code ========== Numeric LastCard WaitForValid1:   Door1 = off     If Door1 ValidAccess is True then       LastCard = Door1 EntryLastCard       GoTo WaitForValid2     Endif WaitForValid2:   If TS > 5s then     goto WaitForValid1   else     If (Door1 ValidAccess is True) and (Door1 EntryLastCard <> LastCard) then       Door1 = on       goto TimeWait     endif   endif TimeWait:   if TS > 5s then goto WaitForValid1 ===============================  

Issue Have the ability in SBO to disable and enable the email delivery from a graphic with a simple switch Environment Automation Server (AS), Enterprise Server (ES) - all versions Cause - none - Resolution In order to enable / disable email delivery from a graphic, do the following: 1. Add a Switch component to a graphic. Save the graphic. 2. In Workstation, open the bindings window for the graphic. Bind the Status of the Email Notification to the Value of the Switch.

Issue Error updating row in the database table when manipulating object. Environment Cyberstation Cause Workstation using unsupported SQL Native Client 10.0 Resolution Use supported version of the SQL Native Client

Issue How can I/A Series G3 be configured to monitor local setpoint changes on the LON based SE7000 Series Room Controllers? Environment I/A Series G3, SE7000 Series Room Controllers Cause Setpoint values on the LON based SE7000 Series Room Controllers are maintained as a network configuration property (nciSetPts).  Local setpoint changes will not be seen at the I/A Series G3 station unless the value is polled or read. Resolution I/A Series R2 had an object (PollSnvtTempSetptCmd) in the lonextras jar that could be set to poll the nci values on a configurable time basis.  The same functionality can be setup in I/A Series G3 through the use of an interval trigger. Open the kitControl palette and expand the ControlPalette - Trigger folder Add an Interval trigger object and configure as Trigger Mode with the Interval required.  The Interval will determine how often the nciSetPts is updated (polled).  The recommendation would be 60 seconds. Right Click on the Trigger and select “Link Mark” Right Click on the SE Room Controller and display the property sheet for the device Locate and Right Click on the nciSetPts parameter.  Select Link From “Name of Your Trigger”. When the link window appears, select Fire Trigger and then select Force Read.  Select OK to complete the link. All setpoints included in the nciSetPts parameter will be updated at the time interval configured to read what has been set at the local device.