Building Automation Knowledge Base

Issue In a G3 MicroSmart station, does the station point name have to match the point name in the MicroSmart controller? Environment Niagara G3 MicroSmart driver Cause Replacing a MicroSmart controller database with a copy that has identical programming (including I/O assignments) but with different point names Resolution The MicroSmart driver does not use the point name as the link between the G3 station's point and the MicroSmart controller's point. If the I/O assignment is the same, then commands will work.

Issue Migration of DMS-3500 to SmartStruxure Solution Environment DMS-3500 SmartStruxure Cause Not all products have been selected for migration to the SmartStruxure platform. Resolution None of the DMS-3500 databases or controller databases can be converted directly to SmartStruxure.  This is an unsupported migration without the use of a Niagara device to act as a gateway.

Issue How can the time in a Niagara G3 ENC or Jace be changed from a web browser? Environment Niagara G3 Cause Workbench not available Resolution It will require a change to the ENC/Jace license for Embedded Workbench. Then use Platform Services to edit the date/time. Drag Platform Services to a PX page, select Workbench View > System and Time Editor.

Issue Can the setpoints on a SE7600 Room Controller be locked out on the keypad so no one can modify it? Environment SE7600 or VT7600 room controllers Cause Design feature Resolution There are three keypad lockout levels: 0 = Full access to both occupied and unoccupied setpoints 1 = Temporary override capability for both occupied and unoccupied setpoints 2 = No access to both occupied and unoccupied setpoints Review the engineering guide specifications at www.viconics.com.

Issue Does the MNL controller line have any built-in surge protection for main AC power? Environment MNL controllers Cause Design specification Resolution No main AC power surge protection is part of the MNL controllers' design.  It will have to be externally applied.

Issue Values on graphic pages constantly showing 'down' momentarily The following message can be seen in the standard output. "duplicate server session kills" Environment I/A Series R2 Enterprise Server Cause There is another copy of the same Enterprise Server station running on the network. In this particular case, there is a another computer on the network that has been licensed as an Enterprise Server and it has a copy of the Enterprise Server station. This computer is meant as a standby computer and the Enterprise Server station should not be running.  Resolution In this particular case, there is a another computer on the network that has been licensed as an Enterprise Server and it has a copy of the Enterprise Server station. This computer is meant as a standby computer and the Enterprise Server station should not be running.  Stop the Enterprise Server station that is running on the standby computer. From the Admin Tool, connect to the localhost and right click on the Enterprise Server station. Make sure auto run is uncheck. 

Issue Niagara G3 station fails to send out emails and discards to the email with this error message: "BOutgoingAccount could not dequeue in-memory email: null" Environment Niagara G3 (AX) ENC and ENS stations (all versions) Cause After watching the output with debug turned on, the station connects to the email server and authenticates. When it tires to send out an email there is a null pointer exception and it discards the email. There is a trailing semicolon in the To Field of the EmailRecipient under Alarm Service. The email handler is looking for another email address after the last semicolon and sees a null when trying to add the last non-existent email address.   Resolution Remove the trailing semicolon.  

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 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 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 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 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.

Issue Losing VAS client connection; getting error: java.lang.outofmemoryerror: unable to create a new native thread. Environment R2 VAS 2.50 Cause Users at the client were not signing off but rather switching users causing multiple connections to VAS from the same pc.  Resolution Ensure user is logging off, not just switching users.

Issue Customer has a Jace-7 installed with two NICs.  It's installed with 3.7.106. NIC 1 (192.168.1.101) is communicating with 3 other jaces on-site with IP addresses of 192.168.1.102, 103, & 104. NIC 2  (public address) is accessed remotely with Workbench. Is there a way to access the stations (remotely) running on 192.168.1.102, 103 & 104 with fox tunneling? Environment Niagara G3 / AX Cause There is no Enterprise Server on site, just the four Jaces. Resolution Jaces cannot act as Proxy Servers so fox tunneling is not supported on anything except a server.

Issue A customer installed a critical valve with an actuator containing a potentiometer for a positional feedback connection. The potentiometer was wired into a MNL controller's input. After some calibrating, the potentiometer drives past the "0 %open" position which displays as a negative value in the AI point. Is there a way to compensate in software for this negative reading? Environment WorkPlace Tech MNL and MNB controllers Cause It can be difficult to calibrate the feedback potentiometer accurately. Resolution Add a high selector block to the output of the AI block.  Connect the AI block's output and a constant set to a value of zero. Anytime the AI block's output drops below zero, the output of the high selector will display zero.  This can then be used for other logic or for graphical display.

Issue I/A Series G3 Enterprise Network Server output window displays the following error: java.io.IOException: Negative seek offset. java.io.IOException: Negative seek offset at java.io.RandomAccessFile.seek(Native Method) at com.tridium.history.io.FileRandomAccess.seek(FileRandomAccess.java:118) at com.tridium.history.file.recstore.RecordStore.writePage(RecordStore.java:561) at com.tridium.history.file.recstore.RecordStore.newLastPage(RecordStore.java:631) at com.tridium.history.file.recstore.RecordStore.getWritePage(RecordStore.java:606) at com.tridium.history.file.recstore.RecordStore.append(RecordStore.java:222) at com.tridium.history.file.recstore.BRecordStoreHistoryTable.doAppend(BRecordStoreHistoryTable.java:175) at com.tridium.history.file.BFileHistoryTable.append(BFileHistoryTable.java:803) at com.tridium.history.db.TableHandle.append(TableHandle.java:203) at com.tridium.history.db.BLocalDbHistory.append(BLocalDbHistory.java:393) at com.tridium.driver.file.history.BDelimitedFileImport.appendToHistory(BDelimitedFileImport.java:796) at com.tridium.driver.file.history.BCsvFileImport.executeFileImport(BCsvFileImport.java:212) at javax.baja.driver.file.history.BFileHistoryImport.doExecute(BFileHistoryImport.java:90) at auto.com_tridium_driver_file_history_BExcelCsvFileImport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1217) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) at javax.baja.sys.BComponent.doInvoke(BComponent.java:1046) at javax.baja.util.Invocation.run(Invocation.java:46) at javax.baja.util.Worker.process(Worker.java:161) at javax.baja.util.Worker$Processor.run(Worker.java:134) at java.lang.Thread.run(Thread.java:619) Environment I/A Series G3 Enterprise Network Server (versions prior to 3.4.54) Cause The error indicates that a history has become too large where the source .hdb file has exceeded 2GB making the history become inaccessible.  Versions prior to 3.4.54 used a Java integer as the offset into the page file of a history and the negative seek offset error is caused by a math rollover calculating a negative number. Resolution Two options to correct: Review the current size of the audit histories, log histories and any string logs to see which one is at the 2GB limit and perform some history database maintenance to trim the size down. Upgrade to the latest maintenance build of I/A Series G3 (3.4.54 or higher) where Java long calculations are used for the offset.