Building Automation Knowledge Base

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.

Issue When installing SQL server 2008 or SQL 2008 R2 to manually an instance for I/NET, Vista or Continuum, sometimes an error "Invoke or BeginInvoke cannot be called on a control until the window handle has been created" will show up. Environment SQL 2008 / SQL 2008 R2 Vista I/NET Continuum SmartStruxure Cause This issue is happening because of a behavior change in .NET that is exposing an issue with SQL Setup User Interface (UI). Resolution Generally, if you just rerun the installer, it won't hit the issue again. If this can't help, just manually create a C:\temp folder and it will work fine.

Issue When importing a file from TAC Menta into StruxureWare Building Operation Functional Block Editor, the import of the application file fails. Environment TAC Vista TAC Xenta StruxureWare Building Operation Cause The following characters are not allowed in object names in StruxureWare Building Operation. • / • " • ? • * • ~ • White space is not allowed in the beginning or the end of an objects name. • . (period) is not allowed in the beginning of an objects name. Colon (:) is not allowed either, but will automatically be replace by an underscore (_) when importing   In TAC Vista, signal names could contain the character "/". In SmartStruxure, this character is not allowed. Resolution Remove illegal characters from object names in the Function Block program.

Issue Access denied error creating ContinuumDB Environment Cyberstation SQL Server Cause Firewall blocking Resolution Ensure the firewall at both the WS and the SQL Server are not blocking the DB creation process. Turn off all aspects of McAfee or Norton Anti-Virus. In particular, McAfee On-Access Virus Scanning can cause this

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 Normally using RS-485 on an ACX 57xx requires nodes to be activated to work so ordering and price could be affected by this Environment ACX57xx Schlage PIM 400-485 Cause The Schlage PIM RS-485 unit uses RS485 for communication and it's important to know if node activation is required for the Schlage solution to work Resolution The Schlage PIM RS-485 does use RS-485 for communication, but it doesn't require node activation on the comm port. The Schlage solution uses an XDriver instead in order to communicate RS-485 to the PIM

Issue When using STR150 connected to a TAC Xenta 121-FC, the Occupancy Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC, which is the only analog output on the TAC Xenta 121-FC device. Environment TAC Xenta 121-FC STR150 Cause When using a STR150 connected to a TAC Xenta 121-FC, the Occupancy Mode indicator will be default allocated to the Y1 output on the TAC Xenta 121-FC device, which is the only analog output on the TAC Xenta 121-FC device. Resolution In ZBuilder, it is possible to move the Occupancy Mode indication from the default location at Y1 to K1-4. In this case you also need to have an external power supply with 5 Volt DC for the Occupancy Mode indicator.