Building Automation Knowledge Base

Issue Does Niagara R2, G3 (AX), and N4 support IPv6?  Product Line TAC IA Series Environment I/A Series R2 I/A Series G3 (AX) I/A Series N4 Cause Network planning questions from an end customer's IT department Resolution Niagara R2 does not support IPv6 (by design). Niagara G3 version 3.5 supports IPv6 but only on Windows-based platforms like an Enterprise Network Server or a soft Jace. Niagara G3 version 3.6 added support for IPv6 in embedded platforms like the ENC-520-2 and ENC-410-1.  Hotspot JVM required.  It is not supported by the J9 platform. Niagara N4 supports IPv6

Issue The en1 network adapter is not an option for assignment when configuring an IP port Product Line TAC IA Series, EcoStruxure Building Operation Environment I/A Series N4 Jace 9000 Building Operation Multi-purpose Controller / VAV (MP-C / MP-V) Building Operation Room Controller / VAV (RP-C / RP-V) Building Operation IP-IO Cause With the switch to Linux for the Jace 9000's operating system, some functions such as sensing adapters work differently when configuring a controller station.     Resolution In N4.13, we have added a new action to find adapters when Jace's are being pre-configured offsite. Start by confirming in the TCP/IP Configuration page that the desired port is configured and enabled. Make sure that some communicating device is connected to the desired port, exhibited by the port's lights on the unit. Examples include a workbench connection, a BACnet IP device/router, or another Niagara Device. Right-click on the "Link" component under the port, and select the "Query For Adapters" option. You should now see the port in the dropdown. Note: With N4.14, using the en1 as a DHCP server is possible.  If using this with BACnet IP MP, RP or IP/IO in Space Logic controllers engineering with Niagara, this is an important consideration for network applications.

Issue User can open the database in TAC Vista Workstation, but can not run the project database with an LNS network properly when it has been copied from the project site. TAC Vista Workstation is extremely slow when the user operates it in a separate PC or laptop. Product Line TAC Vista Environment Vista 5.1.X Windows Environment LonMaker / NL220 Vista System Plug-In Cause In the user's PC or laptop, the Vista database can not find the proper LNS port which exists in the project site PC. Resolution Define the database which was copied from the project site as the active database in the "Vista Database" tab in "TAC Vista Server Setup" Run TAC Vista Server application (TACOS.exe) Run TAC Vista Workstation. Wait a while for the TAC Vista Workstation to open the database completely Right click the LNS port. Wait a while for the right-click options to appear, then click "Properties" Record the port name in TAC Vista Workstation and its "Device address" in the properties window to a TXT file and save it. Delete all text in the "Device address" in the properties window, and click "OK" to accept the change Repeat steps 4, 5, and 6 to delete all LNS ports' "Device address" After the last "Device address" has been deleted. The TAC Vista Workstation's response speed will be back to normal. If some modifications have been made to the database and need to be applied in the project (which means the database would replace the project site database), remember to restore the "Device address" name according to the TXT file before restoring on the site PC.

Issue In Niagara G3, the SNMP driver reference manual refers to three MIB files required so that the SNMP Point Manager can "discover" and "add" SNMP points as needed.  The filenames are: TridiumR3-MIB.my RFC1155-SMI.mib RFC1213-MIB.mib Where can they be found? Environment Niagara G3 Cause The three files are not easily located. Resolution The TridiumR3-MIB.my file is installed with the version of Niagara G3 installed on the host computer. The other two files (RFC1155-SMI.mib & RFC1213-MIB.mib) can be found on the World Wide Web by searching using their specific filenames. All three files are available here:  SNMP_Files_for_G3

Issue Spare parts availability for Controlli MVL56 (Forta M700) Environment Controlli MVL56 Forta M700 Cause Replacement parts   Resolution Due to the spring return design of this actuator, no spare parts are available, with the possible exception of the PCBA. Any repairs should be done by the factory for safety reasons. However, MVL56 is a Controlli product and they should be contacted directly for further details. If the M700 fails after the warranty then a new actuator is required, the MG900 SR is a lower cost alternative to the M700.

Issue Unused Members The following SNVT members are not used: nviSNVTinput is a structured SNVT and contains the unused member state! nviSNVTinput is a structured SNVT and contains the unused member value! Environment Menta SNVT inputs and outputs Any structured SNVT type. Some examples are: switch hvac_status hvac_overid muldiv obj_request obj_status Cause The pop up is a warning only informing you that the structured SNVT has unused members. If those members are not being used by the program, then it is not necessary to define them in the Menta application. Resolution There are two options to remove this warning: At the bottom left-hand corner of the warning is an option for "Don't show this dialog again." If that is checked, then it will not show warnings for any more unused members each simulation. Add SNVT inputs or outputs for the additional unused members. To do this: Add and AI or AO to the program Double click it and go to the Bind dialog Choose the same SNVT type as the other members and make the name of the SNVT the same as the other members From the Member drop-down list, define one input or output for each member of the structured SNVT.

Issue Since the V354 is obsolete, a replacement valve is requested. Environment V354 part no 7315425000 Spare stuffing box part no 0804629005 Cause Replacing obsolete valve  Resolution No replacement valve is available. Pipe work is required due to port configuration. A spare stuffing box, part no 0804629005, is available for ordering.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Issue SP-C has a valid gateway specified and it's not receiving communications Product Line EcoStruxure Security Expert Environment Security Expert Controller firmware .1248 (or higher) Security Expert 4.0.128 (or higher) Security Expert Controller w/ USB port 2.08.582 (or higher) SX-ELV-HLI-TK license to enable the integration USB to Ethernet adaptor dongle TKE Controller (American) v2r0 (only supported version) Cause It is a known issue. SP-C sends a heartbeat message to TKE but it is not being sent/received as a broadcast message. The controller still sends a heartbeat message to TKE but it is not sending it as a broadcast message with a destination of FF:FF:FF:FF:FF:FF. The gateway being valid causes it to send a Unicast message to the gateway itself (eg router) which does not pass it on to the rest of the network. (This is a known issue and has been logged with engineers). Resolution The workaround is to enable the USB Eth NIC on the SP-C and use: - The onboard NIC to connect to the Security Expert Server that requires a valid gateway to be set - The USB to ethernet adaptor (USB NIC) to connect to the TKE Network where we would set any gateway to avoid this bug Note: The USB NIC can only be configured when using OTIS elevator HLI type. The USB NIC hardcodes the required OTIS IP info to the Onboard NIC for connection to Security Expert. To enable Web UI: 1. In Security Expert, Go to Sites|Controllers|Configuration Tab. 2. Scroll down and expand the Elevator HLI section. Set Elevator HLI type to choose OTIS 3. Return to the General Tab, Scroll down and expand the Commands section and enter OTISUseUSBForMainComms = true 4. Save changes and wait for the programming to be downloaded. 5. Power cycle the SP-C. 6. Go to SP-C Web UI. The USB Eth adaptor will have the original IP. Configure both IP adresses 7. Once The NICs are configured, change the Elevator HLI type back to Thyssen Krupp, choose Cable Network type 8. Click Save and restart the SP-C.

Issue Error message in Platform Application Director; SEVERE [00:25:32 08-Feb-21 EST][sys] Cannot boot Product Line TAC IA Series Environment I/A Series N4.9 and later I/A Series N4 Enterprise Server I/A Series N4 WorkBench Cause In 4.9.1.30 and later, the JDK distributed with Niagara was upgraded to 8u271. Starting in JDK 8u261, the target Visual C++ version was changed. While the updated libraries are available in the jre/bin folder, this folder is not on the PATH for NRE binaries. This can cause Niagara to fail to launch on Windows if another copy of the Visual C++ Redistributables is not present. Resolution Install the Visual C++ 2017 Redistributables. https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads At the time of this article, Microsoft packages the 2015, 2017, & 2019 redistributables together. Select and install the x64 version.      https://aka.ms/vs/17/release/vc_redist.x64.exe    

Issue When using a STR-150 room stat with the TAC Xenta 121-FC/HP, the effective occupancy signal output defaults to the Y1 output in ZBuilder. Y1 is the only analog output on the Xenta 121-FC/HP so this creates a conflict if an analog valve is being controlled Product Line TAC Vista Environment TAC Xenta 121-FC/HP STR-150 ZBuilder Cause In order to activate the effective occupancy signal to the STR-150 room stat, the Hardwired status LED option must be selected. This can be found under the Configuration tab > Connected devices > Room unit in ZBuilder. When this is selected, it places the output on Y1 by default. Resolution In ZBuilder, it is possible to move the effective occupancy signal named "Status LED" from the default location on Y1 to K1 through K4. If a K output is used then a 5 Volt DC external power supply will be required. Place the 5 Volts DC on KC and land the mode wire from the STR-150 on one of the K outputs. It is recommended that K4 be used because it does not share a common with the other K outputs. This way K1, K2, and K3 are free to be used for other things.

Issue Search widget graphics can't find graphic pages created under child servers.    Product Line EcoStruxure Building Operation Environment Building Operation Webstation Cause Currently, in EBO 2023, the dynamic search widget will only find graphic pages created on the server the user is logged into on WebStation. The dashboard search widget is not related to the native EBO search object and cannot search child servers. Resolution EBO 2024 (V6) or higher: From 6.0.1 it is possible to include TGML widgets from sub servers (all servers must have EBO version 6.0.1). Note that this functionality is only supported when you use HTTPS as the protocol between the servers, which is the default protocol in 6.0.1.   EBO 2023 (V5) or lower: If graphic pages are located under child servers, they need to be added to the dashboard manually.  Refer to: Adding a Graphic to a Dashboard

Issue Do not know the card information such as card type, card number and site code.  Environment  CX99xx , CX 9680 , ACX57xx , ACX7xx. Cause Need to know the card information that is to be used and need to configure the door for the card to be used.  Resolution Set the door configuration to Site + Card mode. Open the Access EventView and swipe the card to the reader of the door. Verify the card information from Access EventView.

Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Issue 7798C stops communicating after BIN file download Is the 7798C supported in the older versions of I/NET Seven (1.14 and below). How to reset the 7798C hardware (i.e. place into boot mode) if no communication is possible with the 7798C    Product Line TAC I/NET Environment I/NET Seven 1.14 and lower I/SITE LAN 7798C Cause I/NET revision 1.14 and lower does not support 7798C and can mistakenly be assumed by the I/NET Host software as a 7798B.  If a software restore is completed to the 7798C with these revisions, it disables the device from communicating via the Controller LAN and disables any communication via the serial port with the Hand Held Console (HHC) software.   Resolution If you have downloaded the incorrect BIN file (i.e. 7798) to the 7798C, the handheld console software will not work, and hence, the device can not be placed back into a boot state, allowing the correct BIN file to be restored to the 7798C.  If the serial port is still configured/enabled for direct connection via the onboard TAP, this is the easiest solution to try a software restore to blank out 7798C with the correct BIN file. If either of these options are not available, the following steps can be performed very carefully directly on the hardware: Very Important:  Make sure you turn OFF the power to the 7798C unit. If you fail to remove power, this process could damage the board.  If unsure, please contact Product Support On the top edge of the board is the EPROM, and just below are two RAM chips. Between the EPROM and the two RAM chips are two mustard-colored capacitors (Labeled C2 & C3) If you short across each Capacitor, one at a time, this will take the device to boot. If you still have issues with the device, sending the 7798C in for repair is recommended. Once the device is communicating again, the correct firmware can be restored to the 7798C. At this point, you should be using I/NET Seven revision 1.17 or above.

Issue What port is used for the I/A Series G3/N4 LON and Serial tunnel clients and can it be changed? Product Line TAC IA Series Environment I/A Series G3/N4 Enterprise Server I/A Series G3 ENC I/A Series Jace 8000 Cause Requires port change due to routing or firewall conditions. Resolution By default, the G3/N4 Tunnel Service utilizes TCP port 9973. The port used for tunneling can be configured by modifying the Server Port within the tunnel service properties. Example: Configuring the Lon tunnel server In the palette sidebar, open the lontunnel palette. Open the ENC/JACE station and expand its Services folder. If no TunnelService exists, paste one from the palette into the Services folder. If a TunnelService does exist, go to the next step. Note: Only one TunnelService is needed in a station's services, and it can hold multiple tunnel components (both LonTunnel and (serialTunnel). The TunnelService in the lontunnel module is identical to the TunnelService in the (serial) tunnel module. From the palette, paste a LonTunnel under the station's TunnelService The station should now have a TunnelService and a child LonTunnel component. Configure the properties and modify the TunnelService server port if required. Note: If the ENC/JACE has multiple LON ports (and corresponding LonNetworks), the same number of LonTunnel components can be copied under the TunnelService. Each LonTunnel component can then be associated with a particular LonNetwork (by its LONn device name). For any station user that needs to Lon tunnel, make sure the user has admin write permissions for the LonTunnel(s). Example: Configuring the serial tunnel server In the palette sidebar, open the tunnel palette. Open the ENC/JACE station and expand its Services folder. If no TunnelService exists, paste one from the palette into the Services folder. If a TunnelService does exist, go to the next step. Note: Only one TunnelService is needed in a station's services, and it can hold multiple tunnel components (both LonTunnel and (serialTunnel). The TunnelService in the lontunnel module is identical to the TunnelService in the (serial) tunnel module. From the palette, paste a SerialTunnel under the station's TunnelService. The station should now have a TunnelService and a child SerialTunnel component. In the SerialTunnel's property sheet, expand the "Serial Port Config container." Enter the COMn "Port Name" used by the target driver network, and specify other parameters as defined in the network's configuration. If the ENC/JACE has multiple serial-type driver networks (and corresponding COM ports), the same number of SerialTunnel components can be copied under the TunnelService. Each SerialTunnel component can be associated with a particular network (by its COMn port name) and set the other parameters accordingly. For any station user that needs to the serial tunnel, make sure the user has admin write permissions for the SerialTunnel(s).

Issue When were the different TAC Vista Server versions released? When was Vista Server version 4.X.X or 5.X.X released? Need a list of release dates for TAC Vista Server Need to know approximately how old a Vista site installation is Environment TAC Vista Server Cause It would be interesting to know the release date of the different Vista Server versions Resolution All the Vista release note documents are available on the The Exchange Download Center. TAC Vista 3.11 - 1998-10-21 TAC Vista 3.21 Service Pack 1 - 2000-02-04 TAC Vista 2000 Server and Workstation 3.31 Service Pack 1 - 2001-07-04 TAC Vista 2000 Server and Workstation 3.32 - 2001-09-10 TAC Vista 2000 Server and Workstation 3.33 - 2001-12-20 TAC Vista 2000 Server and Workstation 3.33 SP2 - 2002-11-15 TAC Vista IV Server/Workstation/Menta 4.01 - 2003-02-21 TAC Vista IV Server/Workstation/Menta 4.10 - 2003-10-24 TAC Vista IV Server/Workstation/Menta 4.2 - 2004-03-10 TAC Vista IV Server/Workstation/Menta 4.2.1 - 2004-04-19 TAC Vista IV Server/Workstation/Menta 4.2.2 - 2004-06-24 TAC Vista IV Server/Workstation/Menta 4.2.3 - 2004-11-30 TAC Vista IV Server/Workstation/Menta 4.2.5 - 2005-03-21 TAC Vista Server and Workstation 4.3.0 - 2005-04-29 TAC Vista Server and Workstation 4.3.0 SP1 - 2005-05-25 TAC Vista Server and Workstation 4.3.1 - 2005-07-15 TAC Vista Server and Workstation 4.3.1 SP1 - 2005-10-31 TAC Vista Server and Workstation 4.4.0 - 2005-12-16 TAC Vista Server and Workstation 4.4.1 - 2006-03-13 TAC Vista Server and Workstation 4.4.2 - 2006-05-29 TAC Vista 4.5.0 - 2006-07-05 TAC Vista 5.0.0 - 2006-11-15 TAC Vista 5.0.1 - 2007-04-26 TAC Vista 5.0.2 - 2007-09-28 (first version to support Xenta 700) TAC Vista 5.0.3 - 2008-01-21 TAC Vista 5.1.0 - 2008-06-03 TAC Vista 5.1.1 - 2008-10-27 TAC Vista 5.1.2 - 2009-04-15 TAC Vista 5.1.3 - 2009-09-24 TAC Vista 5.1.4 - 2010-03-31 TAC Vista 5.1.5 - 2011-01-25 TAC Vista 5.1.6 - 2011-07-04 TAC Vista 5.1.7 - 2012-01-03 Note: All dates are in the form [year]-[month]-[date]  

Issue Controller labelling and documentation does not describe how to connect expander modules or which modules are supported. Product Line EcoStruxure Security Expert Environment Security Expert SP-ACX SP-ACX-V2 SP-O8 SP-I16 SP-MRDM2 SP-RDM2 SP-I01 SP-IO84 SP-MI16 Cause Documentation is scheduled to be updated but due to UL certifications for some of these documents the process may take some time to complete. Resolution Expander modules are able to be connected to the SP-ACX and SP-ACX-V2 controllers. There is no restriction to the type of Expander Module, all modules are supported unless specifically stated that they are not. The Expander Module network is connected to the RS-485 port on the right-hand side of the controller just above the Digital Outputs port. This port should be labelled with N+, N-, NA, NB and is to be wired up as per the below diagram. Expander Module RS-485 port

Issue Access Expert SEQ Log Installation Information Product Line EcoStruxure Access Expert Environment Access Expert Hosted V3 Cause The SEQ Log is a valuable troubleshooting tool to be installed separately from Access Expert Resolution Overview Access Expert utilizes a system logging application called SEQ which is used for troubleshooting and diagnostic purposes. While this service is not technically required to run any of the Feenics services, it provides valuable information when troubleshooting. Downloading SEQ The latest version can be downloaded at https://getseq.net/Download Installing SEQ Once the MSI is launched the wizard will prompt for installation as shown in the following Figures. SEQ service installation dialog Once the SEQ logs are installed, click 'Browse Seq' button to open the log in the default browser. Bookmark or Favorite It may be beneficial to set the SEQ logs as a bookmark for easy access. The example below is from Chrome. SEQ Settings Click on the 'Settings' option at the top of the page to access and change the defaults. Initially after clicking on Settings, the API keys page opens. Add an API key if required. API Keys Retention Policy From the settings page, select 'Retention' from the left-hand side menu. Once at the Retention page, click add and set the retention policy. The Access Expert/Feenics default is 21 days. This is adjustable to your needs, however, it is recommended to never go below 7 days. Note: Seq will periodically delete events covered by the policy based on their timestamp. Disk space will be reclaimed by a background compaction process and may not be available immediately. Default is ‘all events’ Example Seq Log Note: Left Click once to expand an event and click it again to shrink it Tips and Troubleshooting Ensure SEQ is installed on the PC where the Access Expert client is installed or it cannot ingest the Access Expert events. If a reinstall of SEQ is needed, manually deleting C:\ProgramData\Seq and subfolders is required after uninstalling SEQ from Windows Control Panel> Programs and Features. The SEQ uninstall does not remove the folder, subfolders and files. If the folder and files are not removed, the installation will fail. Before reinstalling SEQ, Grant the User that is running the installation full permissions to C:\ProgramData\Seq and subfolders if they do not have them. Installing SEQ using Windows Power Shell can be useful since it gives some feedback if something isn't working. Running the MSI installer within Windows doesn't give any feedback.   Command syntax:  seq service install --listen=http://localhost:5341/ -u "YourPCName\admin" -p "YourAccountPassword" Note: The username must be specified as DOMAIN\user or MACHINE\user PowerShell Install Example: SEQ Log documentation: https://docs.datalust.co/docs/getting-started https://docs.datalust.co/docs/ingestion-troubleshooting

Issue Replacement for defective controller is unable to be brought online in Security Expert. The online status is offline and last download shows as failed. controller status A review of the event server diagnostic window shows it is full of "Unencrypted event packet received" messages. event server diagnostics window Product Line EcoStruxure Security Expert Environment Security Expert Client Security Expert controller (SP-C, SP-AC1, SP-ACX) Cause The previous failed controller had been setup for encrypted communications with the Security Expert server. Since the newly installed replacement controller did not have the encryption keys to be able to decode the packets from the server it was not able to be brought online. Resolution On the controllers Configuration tab press the Disable controller encryption, then Yes to confirm. Wait for communications to be established with the controller, review the controller health status and update any modules that require it. To re-initialize encrypted communications with the controller press the Initialize controller encryption button to establish a new encryption key with the new controller. controller encryption buttons

Issue Setting the default BACnet priority levels for different applications avoids priority conflicts by normalizing which priority gets used for a specific action or within a specific application Product Line EcoStruxure Building Operation Environment Building Operation Enterprise Server Building Operation Automation Server Building Operation Automation Server Premium Building Operation Automation Server Bundled Building Operation Edge Server - Standard Cause Different EcoStruxure applications may act upon BACnet objects utilizing different BACnet priority levels. This may cause confusion and can keep the system from operating as expected. Resolution BACnet objects created with EBO (1.4 and higher) will have a default BACnet Priority of 16 unless specified otherwise. The default BACnet Priority can be changed to the customer's needs.   As a best practice, define the Default priority level prior to configuring the system. In addition, consider maintaining the same default priority level for multiple active systems at your site. For example, configure the same default priority level for the EcoStruxure Building Operation and fire protection system. In a multi-server system, you can only configure the Default priority level from the Interface Manager of the Enterprise Server. If you set a new priority level, the system propagates the change to the other automation servers in the network. Refer to: Default Priority Level (se.com) and Configuring the Default Priority Level (se.com)  

Issue RP-C-16B-230V Transformer 24Vac output Product Line EcoStruxure Building Operation Environment SmartLogic SmartX IP Controller RPC-16B-230V Cause More details about the internal transformer power supply required. Resolution The voltage regulation of the transformer is around 15%, thus if the "230Vac supply" is towards it's upper tolerance (230Vac +10%, 253Vac) the no load voltage of the "24Vac output" can be about 30Vac. If the RPC power supply is 230Vac, then the no load voltage of the 24Vac output will be around 28Vac With the 224Vac output" half loaded, the voltage is around 26.5Vac With the "24Vac output" fully loaded the voltage is around 24Vac See SpaceLogic - Hardware Reference Guide