Building Automation Knowledge Base

Issue If only Cyberstation was installed, but Webclient is needed will installing Webclient over the top work? Product Line Andover Continuum Environment Webclient Windows XP Windows 7 Windows Server 2003 Windows Server 2008 Cause At times a Webclient install is needed but a Cyberstation installation was done. Resolution Trying to install over the top will not install the needed web components. The recommended installation of Webclient when Cyberstation has been installed first is as follows: Uninstall Cyberstation Reboot Install Webclient Run the following command after the install to re-register .NET framework with IIS. C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i​

Issue I/A Series G3 Workbench License Manager build 3.8.37 will not automatically import from the License Server even when the connection to the Internet is active.  The result is the display of the Request License dialog box that provides the host ID and email information for Schneider Electric. Product Line TAC IA Series Environment I/A Series G3 Workbench 3.8.37 Cause The issue is related to a setting within the brand.properties file included with the 3.8.37 install.  This setting enables or disables the online license server request function within Workbench.  The setting was inadvertently set to disabled (false). Resolution The issue can be easily resolved by changing the setting by one of the two methods shown below. Method 1 - Replace existing brand.properties file with an updated version Close Workbench Download the following zip file with the updated brand.properties file > brand.properties Use the Windows Explorer and navigate to the lib directory under the niagara-3.8.37 directory Extract the updated file from the zip and replace the existing brand.properties file Method 2 - Manually edit the brand.properties file Close Workbench Use the Windows Explorer and navigate to the lib directory under the niagara-3.8.37 directory. Open brand.properties using a text editor such as Notepad Carefully edit the following line changing the false to true:      license.onlineRequest=false ... update to license.onlineRequest=true Save the file Workbench will now import licenses from the license server.

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 How to determine which MNL controllers (profile and version number) are integrated to a Niagara R2 or G3 station. Environment Niagara R2 lonSiebe jar file Cause Quick reference Resolution Use the LonWorks Device Manager and cross-reference the listed MNL controllers to the table below: siebe                         MNLRF103                             SIEBE                          80:0:16:50:14:4:4:1      siebe                         MNLRF2                                  SIEBE                          80:0:16:50:14:4:4:2  (version 2)    siebe                         MNLRF3                                  SIEBE                           80:0:16:50:14:4:4:3   (version 3) siebe                         MNLRH103                             SIEBE                           80:0:16:50:33:4:4:1      siebe                         MNLRH2                                  SIEBE                           80:0:16:50:33:4:4:2     (version 2) siebe                         MNLRH3                                  SIEBE                           80:0:16:50:33:4:4:3      (version 3) siebe                         MNLRR103                             SIEBE                           80:0:16:50:1e:4:4:1      siebe                         MNLRR2                                  SIEBE                           80:0:16:50:1e:4:4:2    (version 2)  siebe                         MNLRR3                                  SIEBE                           80:0:16:50:1e:4:4:3      (version 3) siebe                         MNLRS1                                  SIEBE                           80:0:16:50:1e:4:4:10     (satellite 1) siebe                         MNLRS2                                  SIEBE                           80:0:16:50:1e:4:4:11     (satellite 2) siebe                         MNLRS3                                  SIEBE                           80:0:16:50:1e:4:4:12     (satellite 3) siebe                         MNLRS4                                  SIEBE                           80:0:16:50:1e:4:4:13     (satellite 4) siebe                         MNLRV2                                  SIEBE                           80:0:16:50:a:4:4:9       (version 2) siebe                         MNLRV3                                  SIEBE                           80:0:16:50:a:4:4:a       (version 3) siebe                         MNOTPVA3                             SIEBE                           80:0:16:50:a:4:4:8       siebe                         SiebePEC                               SIEBE                           80:0:16:50:1e:4:4:0      

Issue When commissioning or decommissioning devices in LonMaker you get a message that your request has been placed in the transaction queue. Environment LonMaker LNS Cause You usually see this message if LonMaker is trying to update devices in the background and the devices are offline or can't be reached. Resolution To see if this message is due because LonMaker is trying to update devices in the background, please try to set the Update Interval property to 0. This can be done in LonMaker by going to the LonMaker menu->Network properties->Timing.  Setting the UpdateInterval to 0 will prevent LonMaker to update devices in the background. Please note that this setting is not usually recommended. If the message disappears once the UpdateInterval is set to 0, it means that devices need to be updated to match the database. If the delay is long, it can be because there are a lot of devices that needs updating and/or LonMaker can not communicate with them. Make sure all devices configured and commissioned are online and available.

Issue ES does not start. In the error log, the following errors are present: nsp.util.SQLite SQLite: Error. Error code: 778 nsp.util.SQLite SQLITE: Unrecoverable error. Will exit(1).' Product Line EcoStruxure Building Operation Environment Enterprise server Cause If the hard drive is damaged or full, the Enterprise Server will not be able to write data to the disk and the error log will contain error 778. This error means: (778) SQLITE_IOERR_WRITE The SQLITE_IOERR_WRITE error code is an extended error code for SQLITE_IOERR indicating an I/O error in the VFS layer while trying to write into a file on disk. This error might result from a hardware malfunction or because a filesystem came unmounted while the file was open. This error should not occur if the filesystem is full as there is a separate error code (SQLITE_FULL) for that purpose. Resolution Change the hard drive or clear out some data depending on what the issue is.

Issue Sigma 4.08 - Sigma server does not start, and an error message may be produced. Environment Sigma 4.08 Build 3.46.57 SigmsSvr.exe Cause Upgraded to Sigma 4.08 from Sigma 4.04 and the Sigma service SigmaSvr.exe would not run. Resolution This issue is caused by a valid licensing method not being available on the Sigma server. Sigma 4.08 (Build 3.46.57) can be licensed by one of the following methods; A valid Sigma dongle. A copy of StruxureWare Building Operation license Administrator software and valid license has been installed.

Issue Where can I download SmartStruxure V1.5 software and manuals? Product Line EcoStruxure Building Operation Environment SBO version 1.50 software Cause Download location required. Resolution The following link is to all documents and software associated with V1.50 release. Or go to The Exchange Download Center and search on the tag: relsbov1.5 (short for: Release SBO V1.5).

Issue Creating a StruxureWare Saved Search which functions as an Inet Off Normal Point Summary Environment StruxureWare Building Operation Workstation Cause This tool can be used for troubleshooting and as an example of how to use the search features found in StruxureWare Resolution In StruxureWare, click on the Magnifier Icon next to the search field to open the Advanced Search Window Set the Search field to an asterisk " * " Set "In folder" to the I/NET Interface Uncheck the Include properties option Click on the ellipsis next to "Include types" Select INET Point Click on the Ellipsis next to Conditions Add conditions so that the search will show when Alarm is true OR Test is True OR Manual is True OR Old Data is True OR Alarm Acknowledge is False As an option, you can include offline items as well. Click on the Save Search Criteria Icon Name the Search and choose a destination folder You can now perform the same search with one click from the System tree.

Issue When trying to connect to a Sigma system from SmartStruxure an "Unable to load SigXmlExport.dll" error message is displayed. Product Line EcoStruxure Building Operation, Satchwell Sigma Environment SmartStruxure Enterprise Server version 1.5 Sigma 4.08 Cause The Sigma to StruxureWare Support files have not been installed to the Sigma installation. Resolution Download the Sigma To StruxureWare Building Operation Support Program from the Exchange Download Center. This additional software allows a Sigma Release 4.08 installation to respond to data import requests from SBO 1.5 and takes Release 4.08 to Build 3.46.66 On the existing Sigma 4.08 Sigma server PC, run SigmaSBOSupportSetup.exe and install the software to completion. There is no need to stop Sigma clients or the server.

Issue Security Expert refers to both Accommodation and Booking features in its Client which would suggest that it is currently capable of handling the Booking/Accommodation of Users as well as controlling their Access, but this is not the case. Product Line Security Expert Environment Security Expert Cause Security Expert has an Accommodation Tab in the User Menu of the Client, which seems to suggest that Rooms can be booked in the system. A Booking System option is also found in the Licensing Menu, which would suggest that Booking features can be enabled upon request. Resolution Both the Accommodation and Booking features are not currently activated however have been included in the GUI and license structure for potential 'future development'. There are no dates for when this will occur.

Issue Does the MNB-1000-15 Remote I/O Module supports pulse inputs? Environment I/A Series MNB-1000-15 Remote I/O Module Cause How to use the MNB-1000-15 remote I/O module universal inputs to read pulse inputs. Resolution Standard pulse input is supported on the MNB-1000-15 universal inputs (UI1 to UI6).  Minimum Rate 1 pulse per 4 minutes   Maximum Rate 1 pulse per second Minimum Rate 1 pulse per 4 minutes. Maximum Rate 1 pulse per second.

Issue Security Expert Smartcard Readers support for DESfire EV2 Cards Product Line Security Expert Environment Security Expert Smartcard Readers DESfire EV2 Cards Cause There is a requirement to use DESfire EV2 cards in a Security Expert system. Currently, the Security Expert Smartcard Readers' specifications sheets indicate support for DESfire EV1. Resolution New Smartcard Readers with firmware v1.04 build 229 and above support DESfire EV2. Older readers' firmware can be upgraded with the new firmware. Contact your Local Country Support for details on upgrading the firmware.

Issue Manually selecting warm start on the restart variable or using a program to try to set it will not work Environment B3 SmartStruxure Continuum Cause Attempting to set the restart or accrestart system variable to work start will not work and may generate errors Resolution The b3885-V does not have an onboard battery, so the warm start option isn't available. Cool start or Cold start are the only options.  Programs that attempt to set warm start will need to be modified to do a cool start and use backup to flash.

Issue How many Vista logs can Vista 5.1.9 handle? Product Line TAC Vista Environment Vista Server 5.1.9 Cause There are no official limitations or documents on how many trend logs you can add to a Vista server. The following items listed in the resolution will assist in determining the performance of the Vista Server Resolution The following items listed are the restrictions that limit the performance of the Vista Server: The DSS writer can handle around 40 logs per second. Vista server trends are often limited by how many values per second the Lon network interface can handle. (Typically 40 for a Loytec port and 10-15 for 911 or LNS port in Vista). Size of the SQL database, 100GB for Vista trend logs is a very large SQL database. Vista can handle this provided the computer hardware is of a high-performance nature, and the SQL database and computer hard disk must have regular maintenance performed.

Issue Modem commands for the internal modem for the 9680 are needed Environment 9680 RAS Cause Troubleshooting the modem in the 9680 may require knowledge of the Microtech modem and the commands Resolution The Netcontroller II Operation and Technical Guide references "RJ Modem AT Commands Reference" in order to customize the modem initialization string Click her to download RJ Modem AT Commands Reference There is no option for changing the DTMF frequency Guide"

Issue Sometime it is hard to trace the File Equalization process, especially when issues happens. Environment I/NET File Equalization Cause There is a log file under C:\INET Seven Data\ called INetEqzConfig.log. This will record the whole process of file equalization. But it is not so accurate if I/NET shows the equalized client finished the equalization although it is not. Resolution There is a function in SQL management tool called Replication Monitor. This can monitor the current SQL replication status of all the clients, which is file equalization, on the filemaster. 1. Open SQL management tool on Filemaster, and right click on Replication to Launch Replication Monitor. 2. In the monitor, after you start the Filemaster, you will see the local SQL server. If there is no equalized client, the list will be empty. 3. If the equalized clients appear, they will show up in the list. If it shows Synchronizing, that means file equalization is working. 4. If it shows Not synchronizing, it means the file equalization doesn't start or has been finished.

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 An error message is displayed when trying to save changes to a Programmable Xenta in Menta Editor. The error message is: Tam32 Save Error Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: index (E) Error message trying to save changes in Menta Editor Product Line EcoStruxure Building Operation Environment Building Operation Workstation 3.0.2 or earlier Xenta 281 Xenta 301 Xenta 401 Cause A defect in Menta Editor causes this error to be displayed when a SNVT name in the Menta application is identical to the programmable Xenta device name.  An example of this is shown below: Resolution This problem has been fixed in Hotfix 3.0.2.2500 and the fix is included in version 3.1. For earlier versions there are two ways to resolve this problem; Either a) rename the Xenta device, or b) rename the SNVT. a) Renaming the Xenta device In Workstation right click the Xenta device and choose Rename Click OK Now you can edit the Xenta in Menta Editor without getting the error message b) Renaming the SNVT Right click the Xenta device and choose Edit In Menta Editor double click the block with the SNVT binding to edit the block Click the Bind... button to edit the binding Change the name, click OK to close the dialogs and Save the changes

Issue There are missing serial ports (COM ports) when viewing the 'SerialPortService' under 'PlatformServices' in a station. Some or all COM ports will be missing. Local serial ports and/or serial ports of the attached modules do not function. Product Line TAC IA Series Environment I/A Series AX Jace 8000 Cause This could show up for several reasons. This was found during an upgrade to Niagara 4.2. It was also experienced when converting a Jace8000 running N4.2 (or lower N4 version) to AX. This can occur with a new out of the box J8000 to AX conversion if you do not first commission the Jace8000 to Niagara 4.4 or above before converting to AX. All of these problems are due to older version USBbinary files not being properly updated during commissioning. The LON option module (side-car) might stop communicating on the LON trunk due to the same binary file issue. Resolution This can be fixed via serial shell; either by direct connecting with a mini-USB cable or via ssh after it is enabled from the Platform Administration view. It is recommended that PuTTY.exe be downloaded and used as the terminal program to access the shell. The directions below are CASE-sensitive and must be entered exactly as shown. We recommend that you do not type these commands, but rather use copy-and-paste to avoid typographical errors. This is especially true of the usbSerialNumber itself -- it is case-SENSITIVE. By default, PuTTY.exe uses mouse-left-click-drag-and-highlight as an automatic shortcut for copy. Mouse-right-click is the automatic shortcut for paste. Once logged in type: Display the USB serial number(s) sh [hit enter] $ ls /etc/usb [this will display the USB serial number(s), if nothing displays see the note* at the bottom] 85091090FPGGS41 [this is an example serial number] Display the available binary files $ ls -Rp /sys/images/usb [this will display the available binary files] /sys/images/usb/applet-flash-sam4s16.bin* /sys/images/usb/vid03eb/pid2404/Tridium232-1_r03.bin* /sys/images/usb/vid03eb/pid2425/Tridium485-2_r04.bin* Note: You could also see '_r05' instead of '_r04'. If this is your result, make sure to update using the line below. /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin* The USB ports unavailable is due to the 'Tridium485-2_r04.bin' (or Tridium485-2_r05.bin) file was not written to the USB serial number file. This can be corrected by updating the USB serial number file with the correct binary file using the statement below. Make sure to replace the X in the statement with the highest number binary found in 'STEP 2' above. $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r0X.bin > /etc/usb/<usbSerialNumber> Update the binary file Using the example serial number and USB binary file found in STEP 2: $ echo /sys/images/usb/vid03eb/pid2425/Tridium485-2_r05.bin > /etc/usb/85091090FPGGS41 Make sure to use the serial number found when 'ls /etc/usb' was called. If there is more than one serial number found, write the command multiple times, once for each serial number found. Also, make sure to use the highest USB binary file number found. Currently r05 is the highest number. If '_r05' is returned as the available USB binary file, make sure to use '_r05' when updating the USB serial number. After a reboot, check the SerialPortService to confirm the ports are restored. *Note: if no usb serial number was found using ls /etc/usb another method would be to call for the slog by typing: $ sloginfo An error would have been logged here during the last startup and will display the serial number; example output: Oct 10 13:42:06 1 6 0 serusb_is_device_supported: Device 2 on bus 0 unrecognized. Using CDC-ACM Class Oct 10 13:42:07 4 11111 0 error opening /etc/usb/85091090FPGGS41 rc=-1 In addition to the symptoms listed above, the inability to communicate with the LON option module may cause the any of the following messages in the Serial Shell and/or the Platform Administration System Logs: error opening /etc/usb/<serial number here> rc=-1 U50Read returned unknown rc = 8!!! io_write failed ldvRC=7, length=<various numbers of bytes> The Station will most likely show that the LON network is up, but the LON devices are down. The device fault cause may show "unable to write" or something similar.