Building Automation Knowledge Base

Issue Problems adding OPC tags manually in OPC clients. The tags can be browsed successfully, but if the path to the Vista object is copied and pasted in, e.g., via excel, the object can not be found on the Vista OPC server. Environment TAC Vista 5.1.X  TAC Vista OPC Server 1.6.X 3rd party OPC client Cause To save engineering time, objects are exported from Vista to excel and imported into the OPC client. Resolution Spaces in Vista object names are saved as non-breaking spaces. This is used to avoid the words that the object name consists of getting separated. Breaking and non-breaking spaces in word documents: To restore the non-breaking space: Paste the text into Word.  Search and replace "object name" with "object^sname". Example:

Issue Which object attributes are exposed on Vista's OPC server? Environment TAC Vista OPC server 1.6.X TAC Vista Server 5.1.X Cause A user may wish to edit objects such as TAC Vista time schedules and force physical Xenta outputs from an OPC client? Resolution By default, all objects and all object attributes are exposed on the Vista OPC server. This can be controlled with authority and user settings. Example of exposed Time Schedule attributes, shown in an OPC client.     Example of Time Schedule time event string, shown in an OPC client.     Example of exposed Xenta output attributes, shown in an OPC client.

Issue java.io.EOFException    at javax.baja.xml.XParser.read(XParser.java:753)    at javax.baja.xml.XParser.parseString(XParser.java:555)    at javax.baja.xml.XParser.parseAttr(XParser.java:492)    at javax.baja.xml.XParser.parseElemStart(XParser.java:421)    at javax.baja.xml.XParser.next(XParser.java:262)    at javax.baja.xml.XParser.parseCurrent(XParser.java:146)    at javax.baja.xml.XParser.parse(XParser.java:119)    at javax.baja.xml.XParser.parse(XParser.java:102)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:77)    at javax.baja.ui.px.PxDecoder.decodeDocument(PxDecoder.java:64)    at javax.baja.workbench.px.BWbPxView.loadPx(BWbPxView.java:176)    at javax.baja.workbench.px.BWbPxView.doLoadValue(BWbPxView.java:90)    at javax.baja.workbench.BWbEditor.loadValue(BWbEditor.java:233)    at com.tridium.workbench.shell.NHyperlinkInfo.loadView(NHyperlinkInfo.java:563)    at com.tridium.workbench.shell.NHyperlinkInfo.hyperlink(NHyperlinkInfo.java:100)    at com.tridium.workbench.shell.BNiagaraWbShell.doHyperlink(BNiagaraWbShell.java:350)    at com.tridium.workbench.shell.BNiagaraWbShell.hyperlink(BNiagaraWbShell.java:316)    at com.tridium.workbench.shell.WbCommands$BackCommand.doInvoke(WbCommands.java:718)    at javax.baja.ui.Command.doInvoke(Command.java:303)   Environment G3 (Niagara) station with px files, any revision level. Cause The px file did not copy correctly. Resolution There are three possible approaches to recover from this situation, as follows: Try copying the file again.   Open the px file with a text editor. It might be possible to determine what was either not copied at all, or what might have been corrupted during the copying process. The example shown below is part of the BoilerRoom.px file from niagara-3.6.47 \ stations \ demo \ px \ plant. Lines 489 through 495 contain 'closing tags' for the Canvas Pane, Scroll Pane, Border Pane, content, and px statements that were opened at an earlier point in the px file. If one or more of these 'closing tags' were not copied, or were somehow corrupted during the copying process, the error would result .  If necessary, restore the px file from a backup.

Issue Windows Application logs may be requested by Technical Support to assist with a reported issue. Product Line All Product Lines Environment All Microsoft Windows Operating Systems Cause Unspecified cause. Resolution Press WINDOWS + R on keyboard of the Windows system that the report is to be from. The Windows key is usually located between the CTRL and ALT keys and has a picture of a flag on it. Type Eventvwr.exe and click OK Event Viewer will now start. Expand Windows Logs and then right click on Application. Click on Save All Events As... When prompted save the file as an *.evtx file to an accessible location. Email the *.evtx file to your support representative.

Issue After configuring a Niagara R2 station with BACnet MSTP communications, the UNC displays an error in the standard output window: "Cannot load BACnet MSTP Driver". Error details below: *************************************************************** ERROR: Cannot load BACnet MSTP Driver tridium.nre.DriverException: Not found [mstp]    at tridium.nre.Platform.installDriver (bytecode 98)    at tridium.nre.Platform.getDriver (bytecode 42)    at tridium.nre.Nre.driver (bytecode 4)    at tridiumx.bacnet.services.link.mstp.MstpLinkService.init (bytecode 3)    at tridiumx.bacnet.services.network.NetworkPort.linkInit (bytecode 14)    at tridiumx.bacnet.services.network.NetworkPort.linkStart (bytecode 😎    at tridiumx.bacnet.services.network.MultipleNetworkService.start (bytecode 29)    at tridiumx.bacnet.services.network.RouterNetworkService.start (bytecode 1)    at tridiumx.bacnet.services.BACnetService.startService (bytecode 44)    at tridium.foundation.Sys.startServices (bytecode 49)    at tridium.foundation.Station.startStation (bytecode 63)    at tridium.foundation.Sys.boot (bytecode 27)    at tridium.foundation.Sys.bootLocalSns (bytecode 17)    at tridium.tools.StationMain.bootSns (bytecode 0)    at tridium.tools.StationMain.doIt (bytecode 352)    at tridium.tools.StationMain.main (bytecode 10)    at java.lang.reflect.Method.invoke (Native Method)    at tridium.nre.Nre.mainImpl (bytecode 271)    at tridium.nre.Nre.main (bytecode 1) *************************************************************** Product Line TAC IA Series Environment Niagara R2 Cause BACnet MSTP driver does not load on a UNC reboot. Resolution Add the line illustrated below to the drivers.properties file and reboot the UNC: driver.mstp=tridium.nre.vxworks.mstp.VxWorksMstpDriver

Issue How to configure an analog input on a DMS MicroSmart controller as a contact input. Environment MSC-MPC (revision 10) and MSC-MPC-001 (revision 11) MicroSmart controllers Cause No contact inputs available on the MSC-MPC Resolution Below are illustrations and explanations on how to configure an analog input as a contact input.  

Issue How will SQL logging be affected if a trend log's parameters are changed?  Environment Vista 5.1.X Cause A customer may wish to log values from another point, eg if an energy meter has been changed, or may wish to change the frequency with which the point is logged. Resolution The simplest answer to this question is that if a change affects the log, the message "Log database will be emptied" will be displayed giving the user the opportunity to cancel the action. Depending on the type of trend log being used, the check box "Keep trend log values when changing log point" can be checked and this will allow the log point to be changed - all other parameters must remain the same. It is not possible to change the log interval without emptying the log database for the point as a number of calculations are carried out when displaying log data in a client, that require the points to be logged at a regular interval.

Issue "Couldn't parse: Illegal type:1 cannot be enum" Java error when opening a values page in an Xenta Server Environment Xenta 511 Xenta 527 Xenta 555 Xenta 913 Xenta 711 Xenta 731 Cause Underscores ( _ ) are not permitted characters in the enumeration names within the Xbuilder project. Resolution Remove the _ (underscores) from the enumeration names and redownload the project.

Issue When you attempt to create SNVT binding you the following error. The message output pane shows the following text. Environment NL220 Cause The SNVTs setup in Menta has not had the correct send or poll option set. Resolution Select the send option on the Digital/Analog output setup as a NVO SNVT from the Menta application   This will allow the change of value connection which will assist with network traffic bandwidth. If you set poll in the option on the Digital/Analog input the NVI will poll the output at the specified time set in the input regardless of a change in value. When you generate the modified Menta file the program ID will be changed so an update of NL220 and the Xenta controller is required. To do this save the modified Menta file to the hard drive, browse the updated Menta file from the configure option on the Xenta controller in the system plugin. Then update Vista and download the controller.

Issue MN-Sx, MN-SxHT sensors calibration Environment I/A Series MicroNet Sensors (MN-Sxxx series) Cause Sensor readings inaccurate Resolution 1. Calibration in WorkPlace Tech application program Calibrate the temperature and / or humidity offset in the Hardware Wizard. Enter a positive or negative offset value. For examples, -0.5 or 0.5. The WorkPlace Tech application has to be compiled and downloaded to the controller for the offset to take effect.   2. Calibration via sensor's Diagnostic Mode (only available in MN-S3xx, MN-S4xx, MN-S4xx-FCS, and MN-S5xx) To enter the sensor's Diagnostic Mode, press the Up and Down buttons simultaneously until the sensor enters the Diagnostic Mode. Press the Override button (while still in Diagnostic Mode). This will lead you to a display where you can enter an offset for sensor calibration. Allow the sensor to return to the normal display (takes about 30 seconds).

Issue In Niagara G3, a Learn Nv command on a MNL controller generates the following error: Environment Niagara G3 LON Cause Attempting to learn the new snvt profile from a controller that is already assigned a lnml file. Resolution If a LearnNv command is required on a controller already assigned a lnml file, the only way to avoid the error is to remove the lnml file assignment such that the file assignment is null. Then the LearnNv command will successfully complete. Access the Property Sheet of the LON controller and clear the 'Xml File' and Save.  The file name will be replaced with 'null'. Note:  Performing a Learn Nv on any Lon device previously using a Lon Xml file, LonComponent data from any manufacturer-defined type info is removed (lost).

Issue Presenting FIPS-PIV credential at the door results in Invalid Attempt, FIPS-PIV Credential not valid. Environment CyberStation ACX5740 CX9680 Cause Either the credential number or the Individual Credential Issue field (or both) has a value of zero. Continuum does not allow zero in the credential number for any of the supported FIPS-201 card format types (FIPS-75, FULL-FASCN etc) Continuum does not allow zero in the Individual Credential Series (ICI) field for any FIPS-201card format  type that includes the ICI field such as FULL FASCN The card may have not been programmed correctly. Resolution 1. Upgrade controller firmware. The controller FW has been updated to allow zero in the Individual Credential Series (ICI) field. Credential number ZERO remains INVALID. CX9680 version 2.100048 or greater. ACX57xx version 1.100052 or greater. 2. Use FIPS-PIV credentials that have non zero values in the credential number and the individual credential issue. OR 3. In the PIVReaderFormat system variable in the controller, configure the format specifying that the field (or fields) be ignored. **** **** IMPORTANT Be aware that ignoring a field such as the Individual Credential Issue (ICI) may result in an otherwise invalid card to be granted access. For example, if a card with ICI set to 1 is lost and replaced with a card with ICI set to 2 but with all other FASCN field identical, the controller will grant access to both cards if configured to ignore the ICI field. For example, for a reader that outputs a 200 bit FULL FASC-N card signal configure the door like this... And set the PIVReaderFormat like this SS-Agency+System+Credential+SF+SF+PI-OC-OI-POA-ES-LRC (Note the SF token instructing the controller to skip the field when performing the card validation) NOTE: When the door configuration changes the controller automatically resets PIVReaderFormat based on the value of the door's card format, to keep the value of PIVReaderFormat at the proper custom value it is necessary to create a PE program in the controller. The program should be triggered by the PIVReaderFormat system variable.

Issue Continuum installer throws a Error 1904, dll failed to register error during the installation process. Environment Continuum Error 1904 Failed to Write to Registry. Cause Virus protection is preventing the Continuum install from writing a .dll to the registry. Resolution Uninstall Continuum completely. Reinstall Continuum with all malware protection software disabled and using a Local Administrator user account. Check the compatibility matrix to ensure that the Windows OS you are using is compatible with the Cyberstation version

Issue How to create 0-10Vdc or 0/4-20mA Analogue Input on a 532 Controller Environment Analogue Input 532 Cause How to create 0-10Vdc or 0/4-20mA Analogue Input on a 532 Controller? Resolution On the 532 there are 2 rows of links. The left hand row need to be unlinked i.e. set for non-resistive. The right hand row needs to be set for AI with the middle and right hand pin linked. Next the input needs to be modified with resistors as follows: 0-10Vdc 0/4-20mA

Issue When selecting a list view, last column is always on next page Environment Release 1.2 and 1.3 Beta 3 Cause When Printing a list view, last column is always on next page.  Resolution At the moment only workaround: to add 4th "dummy" column. Then the 3 necessary columns are on the first page and the dummy is on the second.

Issue Is it possible to see a list of all the signals in the vista system that are overridden manually? Environment Vista 5.1.X Cause It is important for the customer to know which signals are manually overridden to be able to make appropriate decisions about a plants' status. Resolution There are 2 main options available: 1. Use Vista's search tool -the screen shot below shows which criteria to use. You can of course include other points in the filter. 2. Create a report and link to the signal's 'manual control' property. This option would have the advantage of being able to trigger the report via a button in TGML and that the layout can be configured according to the customer's specifications. However, it will take a bit longer to configure the report initially. -Open the report and via the Vista reports addin configure a vista link to a value as shown below.  

Issue TCP/IP ports used in Niagara G3 (AX), various drivers, features, and functions - Quick Reference Table Environment Niagara G3 all versions Cause quick online reference for the ports used in Niagara G3 Resolution

Issue Clarification regarding Vista's OPC server and OPC client functionality. Incorrect configuration can cause unexpected results and crash the system. Product Line TAC Vista Environment Vista Server Vista OPC Server Cause There is some confusion as to the usage of the OPC server object in TAC Vista workstation. Resolution TAC Vista OPC Server TAC Vista OPC Server is an add-on module to TAC Vista Server, which enables third party OPC-compliant presentation systems to interface with TAC products. All objects and signals in the TAC Vista Server database can be read and changed via the OPC Data Access interface. Vista OPC Server is implemented as a Windows service and can be started from the Computer Management console.  A license is required, but no configuration is necessary in workstation TAC Vista OPC Client The TAC Vista database has to be programmed and configured as an OPC client, using the TAC Vista OPCTool. Simply browse the available OPC servers, select the objects to be added to TAC Vista and then from the tools menu select "Create/update TAC Vista objects...". When the dialogue opens up, browse to the appropriate location and select the OPC server object to be updated. If this is a new OPC client, right-click in the dialogue and select New->Device-OPC server. The object's properties will then be set by OPC tool after clicking on the select button. !!Do not create an OPC server object in Vista and set the program ID to TACOS.OPCServices.DA.1 and the Class ID to {7EA83597-0B54-4BAF-9EE5-D30AA9EB4D6D}. This will create a loop in the system and cause unexpected behaviour. There should be no OPC server objects in Workstation if TAC Vista is the OPC server!! read and changed via the OPC Data Access interface. to interface with TAC products.

Issue Current rating of the analogue outputs is not documented Product Line Field Devices Environment TC907-3A4LAB TC907-3A4LMAB TC907-3A4DLSAB TC907-3A4DLMSAB TC907-4FMSAB TC907-3A4DPSAB TC907-3A4DPMSAB TC907-3A4DPMSA-24B TC907-4FMSA TC907-3A4LMA TC907-3A4LA TC907-3A4DPSA TC907-3A4DPMSA-24 TC907-3A4DPMSA TC907-3A4DLSA TC907-3A4DLMSA Cause The maximum current information is required for connecting controlled devices. Resolution The analogue output has a maximum output of 40mA (minimum impedance 250Ω).

Issue Link test fails when selecting graphics folder path in Pinpoint Options. Internet Explorer throws the following error when a graphic is launched.   Environment WebClient IIS Server Web Pinpoint Pinpoint Graphics Cause When specifying the location of graphics files in WebClient, the share must be a virtual drive as IIS not use a physical drive. Resolution Use the virtual drive share name when configuring the graphic file location under WebClient in Pinpoint options.