Issue How to decode BACnet errors when they are encountered in the following products. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause Documentation is unavailable for these errors when reviewing log files against any captures.  Resolution The error in log files is composed of two fields, BACnetErrorClass and BACnetErrorCode. The BACnet Error Class (BEC) field is made of the high 16 bits and the BACnet Error Code (BE) of the low 16 bits.  0x800 indicates the error class and error code are in Hexidecimal format. Error Class 0x8001, when remove 0x800, 1 decodes to Object Error Code 001f decodes to Unknown Object Therefore, the error code is Object_Unknown Object, where the device indicates it has no knowledge of the object, either it does not exist or the device does not have the expected program/database installed. For b3, it could be memory was wiped on power failure and needs to be reloaded. It could mean the expected application needs to be downloaded for other devices.   The following are a subset of BACnet errors defined in the specification. If you have questions or encounter ones not listed, please contact Product Support Services.   Error Class List High 16 bits of Error. See BACnet spec clause 18. May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Code List Low 16 bits of Error. See BACnet spec clause 18. Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Common BACnet errors you may see: Error Code Translation Notes 0x8000001e Device + timeout likely something is offline 0x8001001f Object + unknown object likely b3/AS memory was wiped in power fail 0x80020020 Property + unknown property   0x80020025 Property + value out of range likely writing 0 to a multistate object 0x80020028 Property + write access denied   0x8002002c Property + not cov property trying to subscribe to non COV object (i.e. schedule) 0x8002002e Property + invalid configuration data likely configured a change-of-value alarm on non-analog 0x80030000 Resources + out of memory   0x80050007 Services + inconsistent parameters   0x80050019 Services + operational problem   0x8005001D Services + service request denied   0x8005002B Services + COV subscription failed (0x5002B may show, not including the 0x800)   In Wireshark, using the display filter bacapp.type == 5 one will see errors dissected in the APDU packets in Decimal format. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

Issue BACnet/IP controllers are not configured in RSTP Mode by default, therefore must be configured during installation. Having RSTP Mode disabled by default allows one to connect BACnet/IP controllers to any switch, even with port security configured to detect BPDU packets and disable the port. Product Line EcoStruxure Building Operation, TAC IA Series Environment Multi-purpose Controller (MP-C) Multi-purpose VAV (MP-V) Room Controller IP-IO I/A Series N4 Jace8000 SmartX IP Driver for Niagara Cause RSTP protocol requires that controllers, switches, and network architecture are configured to ensure the protocol will operate as expected.  Resolution Setting RSTP Mode for BACnet/IP Controllers ALL devices in the RSTP loop MUST BE IN RSTP MODE to function properly. This is not a huge issue because during startup you can unplug 2nd side of the loop and it will function properly in a daisy chain. Ensure the SmartX Controllers are configured correctly Configuring BACnet/IP Controller Device Settings A factory or network reset returns the RSTP setting to Disabled. Important: Whenever you make changes to RSTP the controller MUST be restarted. If you fail to perform this restart, the BACnet/IP controller will continue communicating using its previous RSTP settings. 'Activate IP Changes' does not affect RSTP mode. Ensure the switch is configured properly per Configuring RSTP on a Managed Switch for SmartX IP Controllers Bridge Priority = 4096 Hello Time = 2 sec Max Age = 40  (40 is the maximum value allowed by the protocol. Default is 20) Forward Delay = 21 sec Change Bridge Priority by adding 4096 as switches get further away from AS. (8192, 12288, 16384, 20480, 24576, 28672) DO NOT set the priority as 32768 or higher because that is the built-in Bridge Priority of BACnet/IP Controllers. Configure the Root Bridge Switch (closest to Automation Server) settings first Then configure the additional Switches in order of increasing Bridge Priority. Plug in 2nd side of the RSTP Loop If all devices stay online, then it is working properly. Now test line breaks or controllers that are powered off. If all devices go offline and/or the switch LED is flashing rapidly, then go to RSTP Troubleshooting. Managed Switch Troubleshooting Ensure the switch is IEEE 802.1D - 2004 capable. BACnet/IP Controller Networking Term Definitions RSTP Ring mentions the Rapid Spanning Tree Protocol is specified in IEEE 802.1D - 2004. Ensure the firmware is up-to-date by contacting the vendor or manufacturer or downloading it from its website. Ensure ports not participating in RSTP are configured as Edge Port, Admin port, or have STP disabled. Nomenclature for those settings on your specific managed switch may vary so consult the documentation or contact the vendor or manufacturer to assist with configuration. Adding BACnet/IP controllers to site-managed switches, work with Local IT to add these devices to their network. They will need to work with their switch vendor/manufacturer/support group to ensure the configuration of those switches because it could be more complex than changing the minimum recommended four settings above. Also, since RSTP Protocol is limited to Max Age = 40 (hops including site switches and BACnet/IP controllers), there may be limits on the size of each loop based on their site switch network configuration and architecture.   RSTP Troubleshooting Check each BACnet/IP Controller -> Diagnostics -> Device Report to confirm in RSTP Mode MANUAL CHECKOUT Double-click MP - Diagnostics Files - Device Report It will open in the default text editor Review the Device Settings section near the bottom. In firmware 1.00.0x, the report should report RSTP Mode: Enable In firmware 2.00.0x or higher, RSTP: Enabled and RSTP Status: Operational If it reports disabled, then perform Setting RSTP Mode for BACnet IP Controllers Step 1 until RSTP is working properly. USE SEARCH & EVENTS EBO 2.x MP Device IP and Settings.xml for EBO 2.0 as it only includes MP controllers EBO 3.x SmartX Device IP and Settings.xml for EBO 3.x or higher Import attached search USE RSTP STATUS GRAPHIC IN WEBSTATION MUST BE EBO 3.1 or higher which includes ClientAPI support Fusion Fridays - Session 07 ​​​​ The start of the video shows the graphics page in use RSTP Status.zip is downloaded via the link below the video. Extract the TGML and drop it on the AS to import. The suggestion is to store TGML directly under the AS to help with navigation in Webstation. bind Network to the BACnet/IP network with the BACnet/IP Controllers. (You may need a second TGML page if BACnet/IP controllers are on Primary and Secondary IP) Run from web browser via WebStation because utilizes ClientAPI KNOWN ISSUES Factory Reset or controller replacement should leave one ethernet cable unplugged until configured for RSTP per these articles: Replace a BACnet/IP Controller in an RSTP Ring Network Workflow and MP Controller Reset Modes If BACnet/IP Controller Device Report OR RSTP Graphic reports RSTP Status: Changes Pending instead of RSTP Status: Operational, disable RSTP Mode, restart, re-enable RSTP Mode, restart, and check again. If Firmware 3.02.01 is installed, please upgrade to 3.02.02. SmartX is now SpaceLogic.

Issue Many LonWorks network installation problems can be avoided if the appropriate network design rules are followed when the network is being designed. Product Line TAC IA Series, TAC Vista, Satchwell Sigma Environment I/A Series MicroNet (LON) Controllers Satchwell Sigma MicroNet series LON Controllers Vista Xenta Controllers Cause The I/A Series MicroNet System Engineering Guide (F-26507) was written as a resource of information for the installation of the I/A Series MNL-100, 200 & VAV controllers as well as the Sigma MicroNet 440 and 620 controllers.  The Resolution, below, is a summary of the LON design rules presented in this document. Resolution FTT-10 LON network wiring must be installed using Echelon-approved wire.  The most common type of wire used is described as Category 4  cable.  This wire is normally unshielded stranded twisted-pair 22AWG (0.65mm).  An example of this wire is the W221P or W222P series cable from Connect-Air International (http://www.connect-air.com).  This type of cable is normally available both in plenum rated and non-plenum rated types.  Consult the job specifications to determine if plenum-rated or shielded cable is required. The LON network can be wired using "Free Topology" or "Bus Topology" wiring segments.   1.  BUS Topology Guidelines BUS Topology LonWorks wiring extends from device to device (daisy chain format) with no branches or stubs. A LON-TERM-2 terminator must be installed at each end of the LON bus. When using standard Category 4 LON cable with the recommended terminators, the bus may be up to 4593 feet (1400 meters) in length. When extending LON wire to the MN-Sx sensor base in a bus topology network, the sensor base must be wired as part of the daisy chain and not as a stub connection. 2. FREE Topology Guidelines Free Topology imposes essentially no restrictions on the layout of the network -- some controllers may be wired point to point and others branching from a common point.  The free-topology LON network must be terminated at one point with a LON-TERM-1 terminator. When using standard Category 4 LON cable, the total wire length in a free topology LON network may not exceed 1641 feet (500 meters).  In addition, the longest wire path between any two controllers on a free topology LON network may not exceed 1312 feet (400 meters). 3. Common LON Network Wiring Guidelines LON wiring can not be part of an active bundled telephone trunk even if the telephone trunk is wired with Category 4 wire. Shielded Category 4 wire may be used in high EMI/RFI environments.  The shield must be wired continuously and grounded through a 470 Kohm resistor at one end. LON wiring must not be bundled with or housed in the same conduit as controller I/O and power wiring.  4. LonWorks Network Wiring and Addressing Guidelines When the number of controllers on a LonWorks network exceeds 60, the network must be split into segments with not more than 64 controllers or devices per segment using LonWorks Repeaters or Routers.  When counting the controllers and devices on a LonWorks network segment, a LonWorks Network Interface Device and the repeater itself must be included in the device count in each segment. In a LonWorks network containing repeaters or routers, each LonWorks network segment must be properly terminated, as described above. Domain / Subnet / Node addressing is used when configuring the LON controllers. A LonWorks Subnet consists of a series of LonWorks controllers all configured within the same LON Subnet number. A single LonWorks Subnet can have a maximum of 127 device and controller Node addresses.  This Node address count includes the LonWorks Network Interface, all controllers on the subnet, and repeater and/or router node addresses.  An allowance is typically made for additional addresses to be used by LonWorks tools connected to the Subnet.

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 Recovering non-functioning Jace 8000 caused by image corruption Product Line TAC IA Series Environment Jace 8000 Cause Improper management of the files on the Micro SD card of the Jace 8000, power brownouts, and other issues have been known to cause corruption of the installed "Golden Image" of the Jace Resolution Download and review the Product Announcement to determine which image should be used on your Jace based on the software to be installed and the Micro SD card version: PADV-IA-22-0001, JACE 8000 Hardware Changes Soon To Be In Effect   Download and select the image and tools for completing the process detailed in the video: I/A Series Niagara JACE 8000 Images and Raw Copy Utility - Installation Software   

Issue Is the new PSI / XPSI rev 4.1 compatible with Windows XP and Vista? Environment PSI / XPSI rev 4.1 Windows XP and Vista Cause Install PSI / XPSI rev 4.1 in a Windows XP or Vista Operating System (OS) Resolution The new PSI / XPSI rev 4.1 is compatible with Windows XP and Vista. Download PSI rev 4.1 from The Exchange. The zip file includes an installer and a READ.ME file that includes Release Notes and Installation Instructions. Note that the Patton Electronics RS-232 / RS-485 converter that has been widely used with the earlier versions of PSI (3.13) will not work with the new PSI / XPSI rev 4.1.  The B&B Electronics model USOPTL4 USB converter has been successfully tested with PSI / XPSI rev 4.1. Other recommended converters are listed in the Release Notes.

Issue In WorkPlace Tech, monitor tags can not be placed into the open application. They disappear and there is no error message. Product Line TAC IA Series Environment WorkPlace Tech Cause A layer being turned off in error and need to configure the layer setting to Visible. Resolution Below are steps to resolve the issue: Close WorkPlace Tech. Using Windows Explorer locate the VSD file, right click it, and clear the read-only and archive flags.   Open the drawing in Visio. Select "Customize" from the "Tools" drop-down menu. Highlight "Menu Bar" on the Toolbars tab of the Customize window and pick "Reset". Close the Customize window. Select "Drawing Explorer Window" from the "View" dropdown.   Expand Foreground Pages - Device Definition - Layers. Right-click RealTimes and enable Visible.   Close the "Drawing Explorer Window". Save and close the file. Insert monitor tags will now work.

Issue What versions of Visio are required for WorkPlace Tech? Product Line TAC IA Series Environment WorkPlace Tech Microsoft Office Visio (32-bit version only) Cause Software requirement - Microsoft Office Visio must be installed on the computer before beginning the installation of WorkPlace Tech. Resolution Below is a list of the WorkPlace Tech revisions and compatible Microsoft Visio versions.  The "Pro" versions are not required.  The "standard" versions of Microsoft Visio are typically recommended.  Only the 32-bit versions of Visio are supported. WPT Visio 3.1 Visio 5 Technical Plus 3.2 2000 SP1 4.0 2000 SP1, 2002 SP1 5.0 2002 SP1, 2003 SP1 5.1 2002 SP1, 2003 SP1 5.2 2002 SP2, 2003 SP1 or SP2 5.3 2002 SP2, 2003 SP1 or SP2 5.4 2002 SP2, 2003 SP1 or SP2 5.5 2002 SP2, 2003 SP1 or SP2 5.6 2002 SP2, 2003 SP1 or SP2 5.7 2003 SP3, 2007 SP1 5.8.0 to 5.8.5 ** 2003 SP3, 2007 SP1 or SP2, 2010 SP1 5.8.6 2007 SP1 or SP2, 2010 SP1 5.8.7 2007 SP3, 2010 SP2 5.9.1 to 5.9.4 2010 SP2, 2013 SP1, 2016 5.10.0 to 5.10.4 2016, 2019, Office (Visio) 365 Subscription Plans ** Microsoft Office Visio 2003 with Service Pack 3 (officially supported for WorkPlace Tech 5.8.0 and 5.8.1, no known issues with 5.8.2 through 5.8.5)

Issue In MNB-1000 (Plant Controller) firmware Revision 1.50E, the Spanning Tree Protocol is Disabled, by default. All previous versions were shipped with the Spanning Tree Protocol enabled. Product Line TAC IA Series Environment I/A Series MNB-1000 (Plant Controller), firmware Revision 1.50E, and later. Cause In some cases where multiple BACnet routers (eg, MNB-1000, UNC, ENC, etc) were installed on the same BACnet-IP internetwork, having the Spanning Tree Protocol enabled in the MNB-1000 would allow a "router loop". Resolution Be aware that in MNB-1000s with firmware Revision 1.50E and later, the Spanning Tree protocol is disabled, by default. Click here to see the Release Notes for firmware Revision 1.50E . It is always recommended the highest firmware version available for the MNB-1000 be used.  Many issues have been addressed for better functionality.

Issue Temperature Sensor Resistance Charts Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Temperature Sensors Cause Temperature (°C) to Resistance Charts (ohms). Upgrading the site BMS, but retaining the existing sensors and the sensor resistance values are not known. Resolution The resistance of a sensor at a specific temperature can be downloaded below, there are a number of tables collated from different sources for a number of Schneider Electric sensors and other BMS suppliers.   In EBO, the thermistor selection in the IO module or controller does not represent the thermistor bead type, an example is the Continuum Type I in EBO, but the bead is a Type 3,. For further information regarding this see the KB article  Thermistor type selection in EBO.   The document All Sensors covers the following:   Satchwell T range is now known as STR600, STP660, STD600, STO600 10K3A1 with shunt Drayton DC1000, DC1100 30K6A1 is now known as STR600D, STP600D, STO600D Andover 10K4A1 TAC Inc. Vista 1.8KA1 I/A series 10K3A1 with 11K shunt INET 10K2A1 (10k Dale) BALCO 1000 ohm RTD   Older Satchwell ranges: Satchwell DW1204, DW1305, DWS1202 Satchwell DO Satchwell DD/DR Other manufacturers included: Allerton 3K3A1 Ambiflex 2012, Honeywell Aquatrol, Jel/Thorn, Trend, York 10K3A1 Schlumberger (air) 5K3A1 Schlumberger (immersion) 100K6A1 Automatrix, York, Sibe 10K4A1 Honeywell 20K6A Landis & Gyr PT100A, PT1000A   Further information regarding the INET, IA and Balco, the document Thermistor Types Tables (Veris Industries) is available.   Further information for the Continuum ACC Temp 10K Type 3 also known as 10K4A1, the document Thermistor Temp Resist Chart (Precon Thermistors) is available.   TC900 series TC900 RS-03 sensor chart   For I/A Series Controllers (MNL/MNB) Compatible sensors that have a built-in 11k shunt resistor include the TS-5711-850 TS-57011-850 TS-57031-850 TSMN-90110-850 Series Any sensor that matches resistance to temperature curve for a 10K Thermistor Type G (U.S. Sensor), Type 9 (Dale/Vishay) or Type III (ACI Series AH) can be used with the I/A Series MNL and I/A Series MNB series controllers, provided that a 11k ± 0.1% 1/8 watt resistor is wired in parallel with the sensor. The input has a range of -10 to 135 °F (-23.3 to 57.2 °C) with an accuracy of ±1% of span. Temperature / Resistance Reference Values Temperature Deg F (Deg C) Resistance Resistance Incl. 11k Shunt 32 (0) 25490 8,012 68 (20) 12,260 5,798 75 (25) 10,000 5,238 104 (40) 5,592 3,707 140 (60) 2,760 2,206 The full temperature/resistance table for the US Sensor 10K Thermistor R-T Curve Type G sensor. Please note that the controller may not be able to use the full temperature range shown in the table.  

Issue The Niagara 4 JACE's platform daemon fails to start making it impossible to login and configure using Workbench tools such as the Commissioning Wizard or Dist File Installer. The error within the serial shell typically indicates ... /proc/boot/ksh: niagarad: cannot execute - No such file or directory. Product Line TAC IA Series Environment Niagara 4 JACE-603 JACE-645 JACE-600E JACE 8000 Cause This can occur as a result of an Incorrect or failed upgrade or improper downgrade without first installing a clean distribution. Resolution Requirements - You will need the following to complete the recovery steps: A terminal emulator such as PuTTY A SFTP client such as FileZilla Serial-Shell cable for your JACE hardware model (specified in the .PDFs below) The Niagara 4 Clean Dist file for your JACE hardware A zip file utility such as 7-Zip The hardware and startup documentation for your JACE model (provided with Niagara 4 installer) Obtain recovery files from the Niagara 4 Clean Dist File for the matching hardware: The clean dist files can be found in your Niagara4 $system_home directory, or in your Niagara 4 image files under the cleanDist directory or in the overlay\cleanDist directory. Open the .dist file for your JACE's platform using a zip utility like 7-Zip and extract the zip/n4clean.tar.gz file. Also, extract the dev/shmem/n4-xxx.image file, where xxx will be different, depending on the JACE's platform type. JACE 300 ... qnx-jace-n4-npm3xx-etfs2048-clean.dist JACE 600 ... qnx-jace-n4-npm6xx-etfs2048-clean.dist JACE 600E ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 603 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 645 ... qnx-jace-n4-npm6e-etfs2048-clean.dist JACE 700 ... qnx-jace-n4-javelina_booke-etfs2048-clean.dist JACE 8000 ... qnx-jace-n4-titan-am335x-clean.dist Make a Serial Connection to the JACE The .PDFs in the N4 documentation set describe how to make a serial connection to a JACE in the "system shell" section(s) of each document. Once connected, the controller will boot and display the "login:" prompt.  Enter your Platform credentials. After login, either a "#" or "$" shell prompt or configuration menu similar to the following is shown.   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011     dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255         inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------     1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot     L.  Logout     Enter choice:   System Shell -------------------------------------------------------------------------   hostid: [unique to your JACE]   serial number: [unique to your JACE]   build version: 4.1.25.1.2   build date: built on 2015-10-07 19:04:59   system time: Thu Jan 14 16:33:18 UTC 2016   niagara daemon port: 3011   dm0:  inet 192.168.1.140 netmask 0xffffff00 broadcast 192.168.1.255             inet6 fe80::5272:24ff:fe9c:55ba%dm0 prefixlen 64 scopeid 0x2   dm1: -------------------------------------------------------------------------   1.  Update System Time   2.  Update Network Settings   3.  Ping Host   4.  Enable/Disable SSH/SFTP   5.  Change Current User Password   6.  Change System Passphrase   7.  Enable Front Panel USB   8.  Configure WIFI   9.  Reboot   L.  Logout   Enter choice: Verify correct system time and update as needed The RTC time may not be correct if the unit has been unpowered for longer than the on-board capacitor backup period. Using menu ... the first item in the menu list allows you to Update System Time.  The current date/time is displayed. Enter the new date/time in the form YYYYMMDDhhmm[.SS].  Note that entering the seconds is optional. For example: 201801111420 for 11-Jan-2018 at 8:20am UTC or 8:20am CST. Enable SFPT The Secure FTP service is not enabled by default on a JACE.  Enable the SFPT from the menu above or the shell prompt (if required). Using menu ... the fourth item in the menu list allows you to enable SSH/SFTP.  Enable it now, using port 22. Once enabled, enter another choice, "sh" (without quotes).  This will give you the "#" or "$" prompt that you need. If you could not enable from the menu in the step above, manually start by issuing the command tsudo syssh_sshcfg at the shell prompt.   If the command fails, issue the syssh_sshcfg command.  If the command fails again, enter the following ... $ cd /sys/bin ... then enter $ ./syssh_sshcfg ... then enter Transfer the n4clean.tar.gz and OS Image Files using SFTP Client Using an SFTP client such as FileZilla, transfer the n4clean.tar.gz file previously extracted for the platform from the clean dist file to the JACE's /zip directory. If the transfer fails with a permissions error, issue the command tsudo chmod 777 /zip at the shell prompt and try it again. Next, transfer the .image file you extracted from the clean dist file to the JACE's /dev/shmem directory. Run osupdate From the login menu prompt, type sh.  This will exit the menu system and enter the shell mode.  At the "#" or "$" shell prompt, issue the command osupdate.  After a short delay, the shell prompt will return. Reboot the JACE Finally, reboot the JACE.  This can be done by issuing the command shutdown hf 0 at the shell prompt.  When the JACE restarts, the unit will automatically process the clean dist file.

Issue Understanding and Troubleshooting Modbus Product Line EcoStruxure Building Operation, TAC IA Series, Other  Environment All Modbus environments. Cause Modicon first introduced Modbus in 1979. Modbus is an open standard,and it is the most widely used in the industrial environment. Modbus is publicly available and,due to its simplicity, many manufacturers use Modbus as a solution for integration in their own products. Many commercial products and systems support the Modbus RTU and Modbus TCP protocols. For further information, visit the Modbus website at http://www.modbus.org. Resolution For a brief understanding on Modbus and how to troubleshoot Modbus, refer to the Modbus Troubleshooting PDF

Issue Niagara 4.9 (or later) sometimes has a new Host ID that differs from the Host IDs of other versions of Niagara that were installed on the same host PC Product Line TAC IA Series Environment I/A Series N4 Enterprise Server Cause Niagara 4.9 and later, are only available in a 64-bit version. The older Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions. Resolution If the older versions are Niagara 4.3 or lower, you may need to update the older versions, as per the following document… I/A Series G3 and N4 Eliminating multiple HostID on a single PC  Niagara 4.9 (or later) is only available in a 64-bit version.  The other Niagara versions installed on the host PC are probably 32-bit versions, which will always have Host IDs different from 64-bit versions.  In this case, the host PC will require one of the following Un-installing the 32-bit versions and re-installing 64-bit equivalents One license, to be "transferred" to a different Host ID when necessary Multiple licenses, one for each unique Host ID.

Issue N4 software installation stops because; azul-zre-compact3-qnx7-arm tridium-qnx7-n4-titan-am335x software is missing Product Line TAC IA Series Environment I/A Series N4 Jace 8000 Cause A valid license including the features that meet the dependencies is not installed. Resolution Install a valid license containing the jre8J8000Azul, jre8Qnz7Zulu and qnx7, jreQnx7Zulu features before attempting to commission the Jace 8000

Issue There are BACnet/IP devices on several different IP subnets. Each subnet has one BACnet/IP device setup as a BBMD, however when doing a discover, no BACnet/IP devices from the different subnets are not being discovered. Environment Niagara G3, ENC-520 Cause Setting up the BBMD in the ENC-520 is as simple as Changing its “Ip Device Property Type” from its default of “standard” to “Bbmd”. Once the ENC is configured as a BBMD device, then the BBMD’s required Broadcast Distribution Table (BDT) is automatically created. The ENC’s BDT includes its own IP address and Broadcast Distribution Mask (BDM), as well as the IP address and BDM of all other BBMD devices on the other IP subnets. The BDT allows for manual editing. We have found in some cases that the BDMs were being confused with the IP address subnet mask. The BDMs were being changed to reflect devices’ IP address subnet mask, which were something other that the standard BDM of 255.255.255.255. BBMD devices’ BDM must be set to 255.255.255.255. Resolution The Broadcast Distribution Mask must be set to “255.255.255.255” for each BACnet /IP Address listed in the ENC’s Broadcast Distribution Table. This is also true for other BACnet/IP devices configured as BBMDs on the other subnets. 1. Expand the ENC’s BACnetNetwork 2. Expand Bacnet Comm and then expand Network 3. Expand Ip Port and then expand Link 4. Expand the Broadcast Distribution Table 5. Expand any devices listed and set their Broadcast Distribution Mask to 255.255.255.255 for any one not listed as such. Save changes. Try and discover again.  

Issue Checking if a port is open Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Field Devices, Pelco, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment TCP/IP Communication Command Prompt Telnet Command Cause Suspect certain network ports are blocked and need to verify Resolution It is possible to check if a port is open in a network by issuing the Telnet command. Note:- Telnet operates using the TCP protocol. UDP connectivity cannot be tested using Telnet. If a port is open, a blank screen will be seen after issuing the command: telnet [domainname or ip] [port] where [domainname or ip] is the domain name or IP address of the server being checked [port] is the port number the server application is listening on For example: telnet 192.168.0.20 9001 (to a closed port would display a connect failed message)   telnet 192.168.0.20 9003 (to an open port would display a blank screen)   To exit the Telnet session, type Ctrl + ] and then type "quit".   For how to enable Telnet in Windows 7 please see Enable Telnet Client on a Windows 7 PC

Issue BACnet tuning policies improperly applied can cause BACnet network problems Product Line TAC IA Series Environment I/A Series G3 ENC I/A Series AX / N4 Jace Cause Configuration parameters in the BACnet tuning policies can initiate high polling rates, force high volumes of writes, reads, and apply confirmed COV to BACnet proxies in the Jace / ENC. Resolution The following video will help us, Configure the "DefaultPolicy" as well as creating additional tuning policies for BACnet proxies   Apply tuning policies to regulate BACnet network utilization

Issue There may be a situation where the External Interface File (XIF) needs to be extracted out of the controller in order to properly set up the controller in a building automation system.  Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment External Interface File (XIF) NodeUtil Loytec XIF Builder Cause These tools will help with the extraction of an XIF file. An XIF file is used to create a Niagara R2 shadow object, a Niagara G3 LMNL file, LonWorks device template, and a SmartStruxure device template.  Resolution The device manufacturer should provide an XIF, and in most cases, a DRF kit as well. The XIF provided by the manufacturer of the controller should be used first but if issues arise it may be required to extract the file from the controller. There are a number of tools available that will create an XIF, but the DRF kit cannot be created by any tool and must be supplied by the manufacturer. This MUST be provided along with the device. The list below covers some of the tools which are available. NodeUtil                          (header: bad,           NVs: ok,                      DMA/File-SCPTs are omitted) Vista's XIF-builder           (header: bad,           NVs: almost ok..,       DMA/File-SCPTs are omitted)  Loytec plugIn                  (does a perfect XIF from a device using Loytec's stack)   NodeUtil is available from the Echelon website (free registration is required) - The NodeUtilLauncher package attached makes it easy to use NodeUtil with Loytec interfaces. Loytec XIF Builder is available from the Loytec website (free registration is required) Using Lonmaker and the XIF Builder. Using NL220 and the XIF Builder. If the uploaded XIF still contains some detailed prompted error, refer to Error displayed when importing a device XIF into SmartStruxure.

Issue How to configure the Network 8000 Interface for ASD overrides Part 1 of 2 Product Line EcoStruxure Building Operation Environment Building Operation Automation Server (All) I/A Network 8000 ASD controllers Cause Requirements and configuration specifics for ASD controller override in the Network 8000 interface Resolution

Issue On a new JACE-8000, or on one in which the clean-dist or factory restore procedure has been applied, the JACE can be pinged but, you cannot connect to the platform, and the system time's year shows as 2020 or greater.   The following symptomatic messages can be observed in the serial shell via the debug port:  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  ERROR [01:26:53 01-Jan-2037] [tid = 1] niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  sysmon: niagarad is no longer running  The following symptomatic messages appear in the system logs:  Jan 01 01:26:53 2 11111 0 niagarad: policy file verification failed. Policy files may have been tampered with. Cause is: [/opt/niagara/security/policy/java.security failed signing verification]  Jan 01 01:26:53 2 11111 0 niagarad: throwable occurred while initializing daemon (java.lang.SecurityException), can not continue  Jan 01 01:26:53 2 11111 4 sysmon: niagarad no longer running Product Line TAC IA Series. Environment I/A Series Jace-8000 Cause This issue is encountered when the RTC clock's date is Wednesday, December 30, 2020, or later.  Resolution Use the debug port to connect to the system shell with PuTTY. See the System Shell section of the JACE-8000 Install and Startup Guide Set the system clock to a date before the year 2020, and then commission the JACE with 4.2 or newer.  The issue is corrected within the fix for the following issue, addressed in Niagara 4.2.36.10:   NCCB-19628: Code signing timestamps checked improperly, verification will fail Jan 1, 2021    We will continue to see the issue on new JACE-8000 as they ship with a 4.1 daemon. This may also occur on a JACE-8000 on which the clean-dist or factory restore procedure has been applied.

Issue How do I locate the latest patch files (modules) for the I/A Series G3 maintenance builds (3.6.407, 3.7.108, 3.8.41) Product Line TAC IA Series Environment I/A Series G3 maintenance builds - 3.6.407, 3.7.108, and 3.8.41 Cause Various issues have been resolved in I/A Series G3 however it is difficult to locate the modules individually. Resolution The latest consolidated patch files for I/A Series G3 maintenance builds 3.6.407, 3.7.108, 3.8.41 are listed below.  The files contain updated modules and a set of release notes.  The consolidated patch files are available for download on the Buildings Download Center.  Login to the Schneider Electric EcoBuildings Exchange Extranet and enter Consolidated_Patches in the search area or the filename of the zip shown below.  Modules listed in bold have been modified or added since the previous patch. Note: This article will be updated with information to newer patch files as they become available for release. Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes bacnet3.6.407.2 baja 3.6.407.3 eibnetip 3.6.407.1 hx 3.6.407.1 mbus 3.6.407.3 ndriver 3.6.407.1             Consolidated_Patches_3.7.108.2.7_SE_02092016.zip   ...  Click here for Release Notes     Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes   Consolidated_Patches_3.7.108.2.7.1_SE_06282016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1 weather 3.7.108.1   Consolidated_Patches_3.8.41.2.9.1_SE_06282016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 weather 3.8.41.1 web 3.8.41.1           ********* Previous Release History ********* Consolidated_Patches_3.7.108.2.7_SE_02092016.zip  ...  Click here for Release Note bacnet 3.7.108.3 baja 3.7.108.3 box 3.7.108.1 eibnetip 3.7.108.2 hx 3.7.108.1 mbus 3.7.108.3 ndriver 3.7.108.1 pdf 3.7.108.1 seriesTransform 3.7.108.1       Consolidated_Patches_3.8.41.2.7_SE_02092016.zip   ...  Click here for Release Notes bacnet 3.8.41.12 baja 3.8.41.2 bajaui 3.8.41.1 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.1 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1 Consolidated_Patches_3.8.41.2.9_SE_04052016.zip   ...  Click here for Release Notes bacnet 3.8.41.13 baja 3.8.41.2 bajaui 3.8.41.2 chart 3.8.41.1 crypto 3.8.41.1 eibnetip 3.8.41.4 hx 3.8.41.1 kitControl 3.8.41.1 mbus 3.8.41.4 nAnalytics 3.8.41.6 niagaraDriver 3.8.41.1 pdf 3.8.41.2 seriesTransform 3.8.41.2 vykonPro 3.8.41.2 web 3.8.41.1   Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes Consolidated_Patches_3.6.407.2.9_SE_02092016.zip  ...  Click here for Release Notes