Building Automation Knowledge Base

Issue When logging in to SmartStruxure WorkStation you get a security certificate risk warning Security Certificate Risk There were errors validating the security certificate in use. This may pose a security risk to the system. The certificate presented by this server was issued for a different server's address. How do you wish to proceed? Trust certificate or Cancel You can also get a warning when logging in through WebStation if you use the https address Warning in Google Chrome - FireFox - Internet Explorer Product Line EcoStruxure Building Operation Environment SmartStruxure version 1.6 and newer WorkStation WebStation Cause Starting in version 1.6, a new security feature has been introduced validating the ES and AS server identity based on security certificates. In order to avoid seeing this warning each time you log in, you need to apply a certificate to each server (ES, AS, ASP or ASB) - either a self-signed or an existing. Resolution This article will describe how to import or generate a certificate, and how to install the certificate through WorkStation or a browser. If you generate the certificate for an Automation Server, make sure that the time and time zone is correctly set in the Automation Server before generating the certificate. Regarding external CA certificates In step 8 below, it's shown how to generate a self-signed certificate. It might be that it's required to use an external CA certificate issued by a trusted issuer e.g. Verisign. All X509 certificates are supported. The format of the certificate must be PEM (as opposed to DER, PKCS7 or PKCS12). More about certificate types here. SBO currently only supports certificates using the PEM format which is the most common. If the external CA certificate is delivered in a container format (such as .pfx) it must be extracted before it can be used in SmartStruxure. More about extracting certificates here. Importing or generating a certificate Log in to Workstation clicking "Trust certificate" Navigate to the control panel Click on "Security Settings" Click on "Certificates" If you see a message saying that a secure communication protocol is not in use, it means that one or more AS's are communicating with the ES using the TCP port (4444) rather than https. In order to manage certificates for all servers in one operation, you need to change the communication ports. Click on "Configure communication settings" to do that. - and change the protocol to HTTPS and the port to 443 Back in the certificates settings, select one or more servers (in this example just the ES) and click "Manage Certificate" Select a certificate type to add. Unless a certificate is bought from a third party provider, select "Generate certificate" which will make a self-signed certificate. Enter a name, tick "Use IP/DNS..." and select a date when the certificate will expire as a minimum, and fill out more info if needed. Click "OK".  NOTE: Do not exceed year 2060 in the "Valid to" field, doing so will result in a certificate expired error when trying to apply the certificate. Select the certificate just created and save   Installing a certificate through Workstation Close Workstation (just logging out is not enough) Open Workstation and log in using the IP address or DNS name - never "localhost" as that name will not match the certificate. Now you will be able to tick "Always trust this certificate" as the name (IP address or DNS name) in the certificate matches the server you are logging on to. Tick the box, and click "Trust Certificate". Click "Yes" to confirm the installation of the certificate Now you will not get the security warning when logging on Installing a certificate through a browser Access the server using Internet Explorer (important) entering the https address (e.g. https://localhost) Click on "Continue to this website" Click on the "Certificate error" field next to the address bar Click on "Install certificate" Select "Trusted Root Certification Authorities" Click next and ok Close the browser Now you can use both Internet Explorer, Google Chrome and FireFox to access the server from Webstation using https and not get the warning If the certificate fails to install and be trusted properly, it might be because you need to manually select which physical storage to add it to. Refer to the following discussion

Issue How to order Continuum v2.0 to take advantage of a Software license instead of a Hardware license. Product Line Andover Continuum Environment Continuum v2.0 and above Continuum Software Licensing Cause A new site requires software licenses, not hardware security keys. Resolution For details on how to order the licensing for Continuum software key see Ordering and Activation of Software License for Continuum v2.0 Note: Purchase a new Continuum Security Key before upgrading to a keyless license. The following is taken from the above document. A new installation – Software license ordering and activation is available only as an upgrade to a hardware key. For new installations please order the USB key from the factory, upon receipt follow the steps outlined hereon for upgrading your USB license to software license. The following products can be ordered with a Software Key: WebClient Server All factory Add-On options [–E (Endura), -D (Data Exchange/Active Directory), -B (Badging), etc...] CoE Add-On options. (see Continuum 2.0 Keyless Add-on Applications FAQ V1.0.pdf for details.) The following can not support a Software Key and will require a Hardware Key (USB or Parallel port): Continuum Interface Server

Issue Site looking for a sample program to monitor the thermostat and alarm if it stops updating the temperature. Environment AS PE Script MPM EnOcean Cause Documentation Resolution Write a PE script to monitor the temperature and alarm as necessary. Click HERE for sample PE Script program.

Issue Need to know Electromagnetic Compatibility for Power Supply PS-24V Environment AS PS-24v Cause Electromagnetic Compatibility Resolution Please have a look at the attached document for Electromagnetic Compatibility test report  --Report--

Issue Boiler does not switch off. Environment DC1100 DC1400 Boiler Compensate Cause The customer has set the DC controller as shown below, the boiler does not switch off. A combined Optimiser / Compensator and the compensation is for the Boiler Only. Resolution The configuration described is classified as "Scheme F" in the data sheet - Optimisation with boiler compensation - one or two boiler control This configuration uses three sensors, the Outside, Space and Boiler Flow Header, it does not use the Compensated flow sensor. To download the complete data sheet please click HERE.

Issue When trying to upgrade a database to version 1.5 or 1.6 the upgrade fails Product Line EcoStruxure Building Operation Environment Enterprise Server Automation Server Cause There can be various reasons for the upgrade failing. At this moment there are two known issues: Issue with specific LonWorks devices such as the T-Stat T7300 Too complex or long list of email addresses in notification objects Resolution Solution for issue 1: Issue with specific LonWorks devices such as the T-Stat T7300 Contact Product Support and ask for hotfix 1.5.0.4801 Solution for issue 2: Too complex or long list of email addresses in notification objects Make a search for all email address objects searching for "EmailAddress" - You can import this search object to do it. Copy all rows to this Excel sheet Check the "Count" column - it counts the characters in the "Property value" column. There's no exact max character count as it also depends on complexity of the addresses, but a good indicator is if the count is over 270. In SmartStruxure, delete the content of the objects having more than 270 characters. Carry out the upgrade (if the upgrade fails, go back to step 3 and delete the content of all objects where the count is 260) After upgrading copy the property content from the Excel sheet back to SmartStruxure

Issue Programming an 8-Bit HID or Indala Prox/Pin Pad reader Environment I/Net Site with Access Control Cause There is a requirement to supply an 8-Bit Prox/Pin Pad reader at a site. How do I program this reader? Resolution Attached is a PDF File that guides you through the setup if this type of reader in an I/Net Seven system. Click here to download.

Issue Changing a Sigma value from a graphic. Environment Object Override Graphic Slider Cause From an imported or transitioned Satchwell Sigma graphic it is possible to override an object value, from a StruxureWare Building Operation Trackbar graphic, it is not. Resolution Sigma's objects are unusual, in that they are not writable. To change their value you have to force them, (or manually override them in Sigma terms).  This means that the standard "Trackbar" component that comes with StruxureWare Building Operation, will not work with Sigma. To manually override the Sigma object, the existing "Trackbar" can be modified to call "setForce" on the object .  This is what legacy Sigma normally does if you have a slider on a graphic, and move the slider. It sets the object to a manual override state. The standard "Trackbar" component can be changed to make it work with Sigma objects. To do this, the "setForce" line was added to the function "setCurrentValue",  setForce(fullName, true);  return setValue(fullName, value);  Note:-  As with legacy Sigma, StruxureWare Building Operation Transitioned Sigma only supports changing certain values.  For example:- You can't make a graphic change the alarm high limit. You can't make it change the configuration value "Fixed value".  The modified "Trackbar in the StruxureWare Building Operation graphic must be bound to the "Value" property, just like it would have been in legacy Sigma.  It is not valid to bind it to the configuration value. To download a copy of the modified "Trackbar", please click HERE.

Issue Existing sensor has failed (TS-5751-850).  The application involves below freezing temperatures (not outside air but a storage freezer).  Since the sensor is obsolete, what's a suggested replacement? Environment Network 8000 MicroZone II Cause Sensor failure Resolution Try the TO series sensor from Veris Industries.

Issue Installation flowchart for a network SIGNAL software installation Environment SIGNAL network version Cause Installation documentation Resolution Installation flowchart available in the Network Supplement of SIGNAL (F-25952), page 9 (pdf) or page 7 (paper)

Issue Site Access Control lockdown for the entire complex. But, also allow certain cards to override certain doors during an emergency situation. Environment I/NET site with access control Cause There is a requirement to lockdown an entire complex with a single toggle switch, but allow First Responders access to certain locked doors in the building. Resolution  There are two different Demo programs for this process One Link program (Download One Link Zip file): MCI -- 7798 DPU – SCU1284 (2 addresses) A maintained switch SPDT   Two or more Links program (Download Two Link  Zip file) MCI – 7798 Link1 MCI – 7793 Link2 – Channel “B” SCU1284 (2address) Link1 SCU1284 (2address) Link2 – On second channel A maintained switch SPDT Each of the above zip files have the following inside: Note: This would be restored to your test bench, and then configuration implemented into a production site.

Issue When using the STR-350/351 in SmartStruxure Function Block Editor some programming consideration must be made to keep the occupancy and setpoint in sync between the stat and the program. Product Line EcoStruxure Building Operation Environment Function Block Editor Workstation STR350 STR351 Cause The STR-350 does not have a configurable Bypass time setting so this must be done using Function Block programming. STR-350 also takes roughly 30 seconds to recover from a power failure. By storing the last known setpoint in a DELR block with the "backup" option set, the setpoint will be restored. Resolution Click the pictures of the Function Block macro below to download the source file. Unoccupied Bypass In order to allow for local override commands from the stat, the occupancy must be read in from the STR-350. By allowing the programmable controller to control both the schedule and the override, the stat stays in sync with the program. The Bypass button of the STR-350 will only toggle the output of the nvoOccManCmd if the input nviEffectOccup matches the current button value. Setpoint The setpoint requires a little bit of extra programming to account for a power failure. The stat will report invalid setpoints for the first 30 seconds, which will cause it to come back in an undesired state. By letting the Function Block program hold onto the last known setpoint, and write it back to the stat on power up, there is no change in the setpoint after a power loss. Looping the setpoint in/out from the stat keeps everything in sync with the program, including stat adjustments. Note: If these macros are going to be used with a STR-350/351 set in degrees Celsius; make sure to change all initial values within the setpoint range. If the initial values are outside of the setpoint range, then the setpoint will always default back to the last known value.

Issue Trying to use OPRIF to make a few programming changes to a MicroSmart controller. OPRIF is installed on a SIGNAL computer (Windows 98). With SIGNAL disabled, OPRIF is able to start and handshake with the COM port. However the Auto Answer feature is enabled by default and begins an endless loop of trying to synchronize with the modem. The looping effect prevents a proper connection to the DMS to do programming changes. How can the Auto Answer be disabled on startup of OPRIF? Product Line TAC IA Series Environment OPRIF or Operator Interface version 11.4 and higher Cause Initialization file was modified by default Resolution The readme.txt file in the DMS folder explains how to prevent Auto Answer from being enabled on startup of OPRIF. Click here to view the entire readme file. Below is the excerpt on how to disable Auto Answer: Changes to the command strings used for modem-initialization and control The default modem init-string "AT C1 E1 V1 S0=1 S7=51" has been changed. It is now "AT&C1&D2E1V1". If you or your modem don't like this string, you can now override the default. Using NOTEPAD or EDIT, create a file called MODEM.INI in the DMS directory. This file should contain a single line of ASCII, which will be your customized initialization string. The line must begin with the letters "AT", and must not contain the letters "DT". Other than this one restriction, your modem-init string can contain whatever commands your modem requires. Two separate default strings have been defined for turning auto-answer ON and OFF. These may be overridden by creating files with the appropriate names in the DMS directory. To specify a customized string to force your modem to STOP auto-answering, use NOTEPAD or EDIT to create file a called ANSWEROF.INI in the DMS directory. By default, this file would contain the single ASCII line "ATS0=0". If your modem requires a disconnect command, you could instead write a line that reads "ATH ATS0=0". The default autoanswer ON string "ATS0=1", instructs the modem to answer on the first ring. To answer on the third ring, use NOTEPAD or EDIT to create a file called ANSWERON.INI in the DMS directory. It should contain the single ASCII line "ATS0=3". SUMMARY: Description Default String Filename Comment Modem Initialize AT&C1&D2E1V1 \DMS\MODEM.INI Modified in 11.4 Auto-answer On ATS0=1 \DMS\ANSWERON.INI New in 11.4 Auto-answer Off ATS0=0 \DMS\ANSWEROF.INI New in 11.4

Issue Functional block names are shorter in XIF file, LonMaker or NL220 than the names defined in SmartStruxure Environment Automation Server Externally Managed LonWorks Network Cause LonMark defines how a xif file must be structured and written. There are especially three rules that comes into play when creating the functional blocks from an Automation Server in the externally managed LonWorks network. In the LONMARK® Device Interface File Reference Guide it states that: "If the static interface contains functional blocks, the device selfdocumentation string must be formatted as described in The LONMARK Interoperability Guidelines." In the LONMARK® Application-Layer Interoperability Guidelines it states that: "Manufacturers are free to assign any functional profile number to new non-inheriting profiles, as long as they are in the range of 20000 to 25000, inclusive; and as long as the number is unique for the program ID template and scope of the resource file set containing the functional profile." In the same document it also states that: "The device self-documentation string is a string of up to 1024 bytes (subject to device memory limits)" and also "If the name is text, it must consist of ASCII printable characters, be of no more than 16 characters in length". Due to the above mentioned rules, any functional block defined in the Automation Server will always start with a functional profile number from 20001 and up and the name of the functional block (excluding the 5 digit profile number) will not be longer than 16 characters. If the name defined in SmartStruxure is longer than 16 characters, the characters from 17 and up will be deleted. If the complete length of the self documentation string is longer than 1024 bytes, the maximum character length will be lowered by one until the complete string fits within 1024 bytes. Resolution The only way to get around this is to either make fewer functional blocks on the Local Node in SmartStruxure, or to make their names shorter.

Issue Building Expert unable to complete the loading process. The Building Expert interface will begin to load but gets stuck at a certain point and never finishes when trying to log into an MPM. Product Line EcoStruxure Building Expert Environment Building Expert SmartStruxure Lite Cause The web browser cache is full.  Resolution In order to get Building Expert to finish loading try the following tasks: Clear the cache of the web browser (To clear the cache in Firefox press CTRL-F5). Try loading Building Expert again. If clearing the web browser cache does not work then try performing a File System Format. Using the Application Note here, access the bootloader and perform a "File System Format". After this process has been completed then the firmware will need to be reloaded into the MPM.

Issue Require a Lua script for using DIM modules Environment SmartStruxure Lite Cause Using a Digital Input Module and Lua script is required to view the Inputs. Resolution For Sontay's DIM4 module download the script here. For Sontay's DIM6 module download the script here. For AXIO's DIM module download the script here. For a generic DIM module download the script here. The voltage received at the AI may need tuning. Copy and paste the text into a Lua program and create the Binary Values (BV).

Issue TRD-IO-16 and TRD-IO-34 Installation (Wiring) & Configuration Guides Environment Niagara G3 Cause Quick access Resolution These guides are also available at http://www.niagara-central.com. TRD-T-IO-16 TRD-T-IO-34

Issue You want to search for a specific LonWorks device in the database Product Line EcoStruxure Building Operation Environment Lon Cause You might have a duplicate Neuron ID Resolution Make a new search right clicking the LonWorks network and then selecting "New" > "Search" Write an asterisk (*) in the search field Click "Advanced Settings" In "Include types:" select the type you want. Either select the specific device template, or just select all device templates. In "Conditions:" enter the neuron ID or other criteria you want to search for. Now click the search button, and you should find the device you are looking for. Here is an import file with a search sample.

Issue The AX Serial Tunnel service does not initialize on a station startup: ---------- Station Starting: FRI JUL 11 14:02:45 2014 ---------- Tridium Niagara Station, r2.301.529.v1 [WFU_UNC06] MESSAGE: ErrorLogService installed [/WFU_UNC06/services/ErrorLogService] ************************************************************ ERROR: Could not init node [/WFU_UNC06/services/IbsAsdService/AxSerialTunnel] java.lang.NullPointerException at tridiumx.tunnelAx.Tunnel.doInit (bytecode 48) at tridiumx.ibsAsd.AxSerialTunnel.doInit (bytecode 84) at tridium.foundation.node.Node.init (bytecode 1) at tridium.foundation.prism.LoaderModule.initNodes (bytecode 26) at tridium.foundation.prism.Prism.initNodes (bytecode 4) at tridium.foundation.Station.startStation (bytecode 60) 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.mainTmpl (bytecode 271) at tridium.nreNre.main (bytecode 1) Product Line TAC IA Series Environment Niagara R2 (revision 522 or above) Cause The tunnelAx jar is not installed in the host UNC. The release notes for AX Tunneling in R2 do not clearly state to install the jar file in section 2.4 and 2.5 which provide install instructions; however, section 1.2 indicates the requirement of this jar file. Resolution Install the tunnelAx jar file prior to starting the install instructions in 2.4 and 2.5.

Issue On rare occasions you will get an error during the installation of Echelon OpenLNS Server on Windows 8.1 64 bit saying that the installer can't create specific registry keys. Product Line EcoStruxure Building Operation, Other, TAC Vista Environment OpenLNS Windows 8.1 64 bit Cause The user does not have permission to access those registry keys. Resolution Add the registry keys manually. Alternatively, run OpenLNS on Windows 8.1 - Registry paths.zip reg file that will add the keys. Run the installer again.