Issue There is uncertainty whether the controller output between terminals V1, G, and V2 should provide a constant 24V signal or an intermittent signal when the actuator reaches the end position, and whether this behavior is configurable. Product Line TAC Vista Environment TAC Xenta 100 controller Cause The controller operates using increase/decrease control logic and does not track the exact position of the actuator between fully open and fully closed. As a result, it continues sending control pulses even when the actuator has reached its end position. Resolution The output from the TAC Xenta 100 controller to motorized valves is not a steady 24V signal. Instead, it sends intermittent pulses to incrementally open or close the actuator. This behavior is inherent to the controller design and is not configurable. Most motorized actuators are designed to handle this type of control signal and include internal mechanisms, such as limit switches or magnetic clutch, to stop movement when end positions are reached. Note: The TAC Xenta 100 is an outdated product and is no longer supported.

Issue Multiple NS errors may occur in LonMaker / LNS environments during application loading, device commissioning, or network management. These include: System Image / Application Load Errors NS #184: Neuron model mismatch when loading application NS #186: System image cannot be written NS #187: System image memory failure during upgrade NS #188: System image upgrade failed Device, Channel, and Network Errors NS #72: Device on wrong channel NS #79: Unable to determine channel when adding/registering device NS #67: Subnet limit reached NS #138: Network interface in wrong/unconfigured state LonMark Object / Network Variable Errors NS #285: LonMarkObject not dynamic NS #286: Network variable not dynamic NS #287: LonMarkObject in use (bound variables present) Product Line TAC Vista Environment LonMaker NL220 Vista LNS Cause System Image / LoadEx Related Causes Application image incompatible with the device system image (model mismatch) LoadEx invoked but system image cannot be written (e.g. not stored in flash memory) Failure writing system image due to insufficient or incorrectly located flash memory System image successfully transferred but activation/switch to new image fails Channel and Network Configuration Causes Device defined or placed on the wrong channel Device added without a channel handle and system cannot determine the correct channel Channel topology contains repeaters or bridges preventing correct channel resolution Network interface is unconfigured or in the wrong state Network subnet limit (255) has been reached LonMark Object and Network Variable Causes Attempting to perform operations on static LonMarkObjects instead of dynamic ones Attempting to perform operations on static network variables Attempting to delete LonMarkObjects that still contain bound network variables Resolution System Image / Application Load Resolutions Upgrade the device system image so it matches the application image (NS #184) Use the LoadEx method to automatically handle compatibility where supported (NS #184) If system image write fails, reattempt loading using Load or LoadEx (NS #186) If memory-related failure occurs, reload the application (device may remain applicationless) (NS #187) If upgrade fails after transfer: Retry the LoadEx method Reload the previous system image (NS #188) Channel and Network Configuration Resolutions Move devices to the correct channel in LonMaker (NS #72) Ensure the Network Interface is on the correct physical and logical channel (NS #72) Recommission devices after correcting channel placement (NS #72) Set routers to Repeater mode during commissioning, then return to configured mode (NS #72) Ensure the channel is properly configured and topology is not ambiguous (bridges/repeaters) (NS #79) Perform a cold reboot of the controller if channel cannot be determined (NS #79) Set MgmtMode to lcaMgmtModePropagateConfigUpdates (0) and recommission the interface (NS #138) Run the LNS Database Recovery Wizard when required (NS #67, NS #138) Use LonWorks Plug ‘n Play Control Panel and select the NSI NI Application where applicable (NS #67, NS #138) LonMark Object / Network Variable Resolutions Check whether objects or variables are dynamic using the IsDynamic property (NS #285, NS #286) Avoid assigning, unassigning, or deleting static objects or variables (NS #285, NS #286) Before deleting LonMarkObjects: Disconnect bound network variables Or use lcaLonMarkObjectRemoveAndDisconnectNVs (3) (NS #287)

Issue In a TAC Xenta 102‑AX controller under TAC Vista, binding nvoSpaceTemp to nviSpaceTemp does not result in the room (space) temperature value being transferred or updated as expected. Product Line TAC Vista Environment TAC Vista TAC Xenta 102-AX LonWorks network SNVT temperature bindings Cause The issue is caused by timing parameter settings for the SNVT temperature binding: SCPTmaxSendTime = 60: The sender transmits the value at least once every 60 seconds. SCPTminSendTime = 10: The value cannot be sent more frequently than every 10 seconds. SCPTmaxRcvTime = 10: If the receiver does not receive a new update within 10 seconds, it resets the value to its default. Because the receiver’s SCPTmaxRcvTime is shorter than the sender’s SCPTmaxSendTime, the receiver resets the value before the next update is sent.  Resolution Configure the receiver in Workstation so that SCPTmaxRcvTime is set longer than the sender’s SCPTmaxSendTime. This ensures the receiver does not reset the temperature value before the sender transmits the next update, preventing timing-related value loss

Issue A TGML graphic generates a script alert such as: TypeError: Cannot call method "getAttribute" of null (cmd#xx) TypeError: Cannot call method "setAttribute" of null (cmd#xx) The error may occur when the graphic loads, when a bound value updates, or when a user interacts with the graphic (for example, mouse click). Product Line TAC Vista, EcoStruxure Building Operation Environment TGML Graphic Cause The error is caused by a TGML JavaScript attempting to execute a method on a null object reference. Most commonly, this occurs when: A TGML component has been deleted or renamed, but one or more scripts elsewhere in the graphic still reference the original object. A script calls a method such as getAttribute() or setAttribute() on an object that does not exist at runtime. In some environments, scripts may also encounter transient null values during initial graphic load. In these cases, bound values may briefly evaluate to null, causing method calls or value conversions to fail even though the graphic later operates normally. This behavior has been observed more frequently during first-load timing conditions rather than as a persistent configuration error. Resolution Follow these steps to identify and correct the offending script, prioritizing validation of object references: Determine when the error occurs On initial graphic load When a bound value changes On user interaction Once only or repeatedly This helps narrow down the script responsible for the error. Isolate the faulty TGML script Save the graphic under a new name. Incrementally remove sections of the graphic until the error no longer appears. The removed section contains the script referencing a null object. Identify the exact failure point Use the cmd# number in the error message to locate the script line. Open the Script Editor using the “…” button next to the script Content attribute. Navigate to the indicated line and identify which object or method is referenced in the error message. Correct invalid object references Verify that all objects referenced in the script still exist and are correctly named. Update the script to reference valid objects, or restore or rename deleted components as required. Confirm that method parameters are valid and reference existing TGML elements. Handle potential null values defensively If the error occurs during value retrieval or string conversion, review any use of toString() on bound values. Improved stability is often seen by converting values using safe type coercion (for example, concatenation with an empty string) to avoid exceptions when values are temporarily null during graphic load. Investigate bound point types and data sources, particularly remote or multistate values, if null behavior is observed intermittently.

Issue The License Setup utility changes configuration values without user interaction. After being modified, the license configuration unexpectedly reverts to a previous state, causing licensed features to appear missing or inactive. Product Line TAC Vista Environment TAC Vista 5.1.9 Cause The root cause is currently unknown. Under normal operation, the TAC Vista Server should write specific values to the registry when a license is added; however, these values may be overwritten, or insufficient Windows permissions may prevent them from being set correctly. Resolution Close all Schneider Electric applications that may access the license. Ensure you are logged in with local administrator privileges. Open License Setup and verify that only the intended license is configured. Remove or relocate any old or unused license files from the system. Apply the desired license settings and restart the workstation. Reopen License Setup to confirm the configuration persists.

Issue How can a minimum compressor off time be configured on a TAC Xenta 121-HP so the compressor does not restart immediately after stopping in the same operating mode (heating or cooling)? Product Line TAC Vista, EcoStruxure Building Operation Environment TAC Xenta 121-HP Cause The TAC Xenta 121-HP does not provide a native parameter for enforcing a minimum compressor off time within the same mode (heating-to-heating or cooling-to-cooling). The controller only supports a minimum stop time between different modes (heating ↔ cooling), not repeated starts in the same mode. Resolution A true minimum off-time timer cannot be configured directly. However, a functional delay can be achieved using hysteresis settings as a workaround. Workaround Configuration Set the “Activate at” value to a non-zero value (for example, 10%). Configure Hysteresis to approximately the same value (for example, 10%). Result The compressor will require a larger control deviation before restarting. This effectively introduces a delay between compressor cycles in most operating conditions. While not time-based, this method reduces short cycling and rapid restarts. ⚠️ Note: This workaround does not guarantee a fixed minimum off time. The delay depends on temperature dynamics and system response.

Issue Customers question why OpenLNS CT is not provided as a full, unlimited license and what functionality is affected when annual maintenance expires. Product Line TAC Vista, EcoStruxure Building Operation Environment OpenLNS OpenLNS CT Cause OpenLNS and OpenLNS CT are licensed with time-bound annual maintenance. This maintenance entitlement controls access to: Software updates Software upgrades released during the active maintenance period Once annual maintenance expires: The software continues to operate with its currently installed version. No new updates or upgrades can be installed that were released after the expiration date. Annual maintenance cannot be renewed retroactively after it has expired. If maintenance is allowed to lapse, a new activation key is required to regain access to updates and upgrades. Resolution To maintain access to updates and upgrades, renew annual maintenance before the expiration date. Renewal Options Purchase one of the following one-year maintenance renewal products: OpenLNS Commissioning Tool Professional – One-Year Maintenance Renewal OpenLNS Commissioning Tool Standard – One-Year Maintenance Renewal Note Alternatives: Note that Echelon has largely transitioned these tools to IzoT CT 4.1 and IzoT Net Server, which are the newer versions of the OpenLNS technology, designed for both classic LON and LonTalk/IP channels Schneider no longer supports or sells OpenLNS or IzoT; however, IzoT products remain available through EnOcean

Issue After running the TAC Vista Conversion Tool, TAC Xenta I/O modules that were configured as LonWorks units in TAC Vista are imported into EcoStruxure Building Operation (EBO) as Xenta I/O modules belonging to a Xenta Base unit, communicating as SlaveSpeak devices rather than LonWorks devices.. Product Line EcoStruxure Building Operation, TAC Vista Environment Vista Server TAC Vista Conversion tool Xenta Xenta I/O-modules Cause In a standard TAC Vista architecture, Xenta I/O modules are typically located on the same subnet as the Xenta Base unit and communicate using SlaveSpeak.   In some installations, a Xenta I/O module may be installed on a different subnet from the Xenta Base unit. In this scenario, the I/O module can be added in Vista as a LonWorks unit, communicating with the Xenta Base unit via LonWorks bindings (SNVTs).   The TAC Vista Conversion Tool does not support this non‑standard configuration. During conversion, it assumes that all Xenta I/O modules are directly connected to a Xenta Base unit on the same subnet, and therefore always converts them as SlaveSpeak devices, regardless of their original LonWorks configuration in Vista. Resolution This behavior is expected when using the TAC Vista Conversion Tool. After conversion to EcoStruxure Building Operation: Identify Xenta I/O modules that were originally configured as LonWorks units in TAC Vista. Manually recreate the required LonWorks bindings between the Xenta I/O modules and the Xenta Base unit in EBO. Validate point communication and functionality after rebuilding the bindings. The conversion tool does not preserve or translate the original LonWorks binding configuration, so manual reconfiguration is required.

Issue How to configure the LonWorks Network Interfaces application to communicate over IP‑852 with a Loytec L‑IP router when using the Echelon driver. Product Line TAC Vista Environment LNS Turbo / LonMaker Turbo LonWorks Network Interfaces Loytec L‑IP (single or multi-port) Vista systems using Echelon IP‑852 driver Cause The default or incomplete configuration of the LonWorks Network Interfaces application or the L‑IP device prevents proper IP‑852 communication. A clear step-by-step procedure is required to ensure the HOST PC, IP‑852 channel, and L‑IP configuration server are aligned. Resolution Preferred Driver Information It is preferable to use Loytec’s own IP‑852 driver, since: It is fully supported by Loytec It is the only driver supported in Building Operation It typically provides improved interoperability and ease of configuration However, it is still possible to use the Echelon driver by following the procedure below. To learn more about L‑IP operation and differences between the two drivers, refer to: Loytec L‑IP 101 video L-IP Users Manual 1. Verify IP Addresses Confirm the IP address of the HOST PC running LNS. Confirm or update the L‑IP IP address to match the network segment. Default L‑IP IP is 192.168.1.254 (refer to L‑IP manual, page 20). 2. Confirm L‑IP Configuration Server Role In single‑router systems, designate the L‑IP as the configuration server. In multi‑router systems, only one L‑IP must have the configuration server enabled. See the L‑IP manual, page 52. 3. Configure LonWorks Network Interfaces Open LonWorks Interfaces from Windows Control Panel. Select the IP‑852 tab. Add a new Network Interface: • Connection name (for example IP) • Set HOST PC IP • Port remains at 1628 • Channel Timing: LAN Save and verify the interface appears. 4. Run a Communication Test Click Test. Enable Set Configuration Server Address. Enter the L‑IP IP address. Set return port to 1629. Start the test. A successful message confirms communication; otherwise continue to L‑IP configuration. 5. Configure the Loytec L‑IP Router Access the L‑IP web interface (for example: http://10.159.5.39 ). Click Config in the menu tree. Login: • Older units: Administrator / admin • Newer units: admin / loytec4u Under EIA‑852 Server: • Config Server Status: Enabled (only on one router) • Config Server Port: 1629 Under EIA‑852 Channel List: • Confirm the L‑IP device is present • Add the HOST PC: IP + port 1628 • Save and use Recontact Repeat the communication test in LonWorks Interfaces after saving changes. 6. Result The L‑IP router will now communicate correctly with the LonWorks Network Interfaces application over IP‑852 using the Echelon driver. The LNS/LonMaker or NL220 workstation will be able to use the L‑IP as its IP‑852 network interface.

Issue Technicians need accurate resistance‑to‑temperature references for legacy and current sensors during BMS upgrades or service. Field users typically know the system in use rather than the thermistor bead type, which makes it difficult to pick the correct resistance table. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment HVAC and BMS installations using NTC thermistors or RTDs Retrofit projects where existing field sensors are retained EBO controllers and I/O modules that require correct thermistor curve selection for accurate engineering units Cause If the controller is configured with a thermistor curve that does not match the actual sensor element, the temperature reading will be offset or incorrect. Lack of documentation for legacy sensors or mixed‑vendor estates makes curve identification difficult. Note:  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. Resolution Use the mapping guide below to start from the product range you are servicing, then identify the thermistor or RTD curve, and finally open the correct attachment/table to obtain R–T values. Attachments available All sensors.pdf – multi‑vendor thermistor and RTD tables including 1.8K A1, 2.2K3A1, 3K3A1, 5K3A1, 10K3A1, 10K4A1, 20K6A, 30K6A1, 100K6A1, PT100A, PT1000A, Satchwell T‑range, DD/DR, DO. USSensorTypeG.pdf – complete R–T curve for US Sensor 10K “Curve G” Thermistor types‑tables.pdf – comparative tables for 2.2k, 3k, 10K Type II, Type III, Dale, US “G”, 20k, 100k, plus RTDs. Thermistortempresistchart.pdf – PreCon Type II, Type III, Type IV, Model 3 (10k), Model 42 (20k). RS‑03 NTC10K (3950) chart.pdf – generic NTC10K B=3950 curve. 1k Balco.pdf – 1 kΩ Balco RTD chart. A. Product range to thermistor curve mapping Schneider Electric legacy families System / Family Typical sensor family in field Thermistor or RTD curve to use Open this table Andover Continuum ACC Temp, legacy room and duct sensors 10K4A1 (NTC 10k class as listed; reference points: 25 °C (77 °F), 40 °C (104 °F)) All sensors.pdf → 10K4A1 table TAC Vista Vista 1.8K A1 sensors 1.8K A1 curve (reference points often shown around 25 °C (77 °F), 50 °C (122 °F)) All sensors.pdf → 1.8K A1 table TAC INET INET 10K2A1 (Dale) 10K Dale / Type 9 class (e.g., 25 °C (77 °F) = 10 kΩ) All sensors.pdf → 10K2A1 table; Thermistor types‑tables.pdf for Dale column TAC I/A Series (MNL/MNB) Commonly paired with US Sensor “Type G” elements with 11k ± 0.1% 1/8 watt resistor wired in parallel with the sensor US Sensor 10K “Curve G” (e.g., 25 °C (77 °F) = 10 kΩ (5,238Ω with shunt ; 40 °C (104 °F) ≈ 5.592 kΩ (3,707Ω with shunt) USSensorTypeG.pdf   TS‑57XX‑85X / TS‑67XX‑85X 10K Thermistor with 11K Shunt Resistance Table Satchwell MicroNet or Sigma Satchwell T‑range, DD/DR, DO sensors Use the dataset for the specific Satchwell family (e.g., tables include 0 °C (32 °F), 25 °C (77 °F), 50 °C (122 °F) points) All sensors.pdf → Satchwell T‑range, DD/DR, DO tables Field Devices TC900 RS03 Generic NTC10K elements (use 25 °C (77 °F) = 10 kΩ; 0 °C (32 °F) ≈ 31.77 kΩ) RS-03 NTC10K (3950) chart.pdf   Other common manufacturer mappings Vendor / Product Thermistor curve Open this table Honeywell Aquatrol, Trend, Ambiflex, York 10K3A1 (e.g., 25 °C (77 °F) = 10 kΩ; 50 °C (122 °F) ≈ 3.601 kΩ) All sensors.pdf → 10K3A1 table Allerton 3K3A1 (check typical points like 25 °C (77 °F), 50 °C (122 °F)) All sensors.pdf → 3K3A1 table Ambiflex 2040 2.2K3A1 All sensors.pdf → 2.2K3A1 table Honeywell 20K6A NTC 20k (e.g., 0 °C (32 °F) ≈ 70.204 kΩ; 25 °C (77 °F) = 20 kΩ) All sensors.pdf → 20K6A table Drayton DC1000 / DC1100 30K6A1 (e.g., 0 °C (32 °F) ≈ 105.305 kΩ; 25 °C (77 °F) = 30 kΩ) All sensors.pdf → 30K6A1 table Schlumberger (air) 5K3A1 All sensors.pdf → 5K3A1 table Schlumberger (immersion) 100K6A1 All sensors.pdf → 100K6A1 table   Generic curves frequently seen on retrofits Curve When you might see it Open this table NTC 10k, B=3950 Generic NTC10K elements in third‑party or OEM sensors (use 25 °C (77 °F) = 10 kΩ; 0 °C (32 °F) ≈ 31.77 kΩ as spot checks) RS‑03 NTC10K (3950) chart.pdf US Sensor 10K “Curve G” Many commercial 10k sensors and I/A Series integrations (25 °C (77 °F) = 10 kΩ; 40 °C (104 °F) ≈ 5.592 kΩ) USSensorTypeG.pdf PreCon 10k (Model 3) PreCon‑sourced 10k elements at 77 °F (25 °C (77 °F) = 10 kΩ) Thermistortempresistchart.pdf → Model 3 [Thermistor...esistchart | PDF] PreCon 20k (Model 42) PreCon‑sourced 20k elements (25 °C (77 °F) = 20 kΩ) Thermistortempresistchart.pdf → Model 42 PreCon Type II / Type III / Type IV 2252 Ω, 3k, and 100k families (77 °F reference; common checks at 25 °C (77 °F)) Thermistortempresistchart.pdf 1 kΩ Balco RTD Legacy RTD elements in some estates (e.g., 20 °C (68 °F) ≈ 997 Ω) 1k Balco.pdf    RTD sensors RTD Open this table PT100A All sensors.pdf → PT100A table PT1000A (common checks at 0 °C (32 °F), 25 °C (77 °F)) All sensors.pdf → PT1000A table   B. Quick verification points for spot‑checks Use these values to sanity‑check field readings after selecting the correct curve. US Sensor 10K “Curve G”: 25 °C (77 °F) = 10,000 Ω; 40 °C (104 °F) ≈ 5,592 Ω.  10K4A1: 25 °C (77 °F) = 10,000 Ω; 40 °C (104 °F) ≈ 5,594 Ω. 10K3A1: 25 °C (77 °F) = 10,000 Ω; 50 °C (122 °F) ≈ 3,601 Ω. 20K6A: 0 °C (32 °F) ≈ 70,204 Ω; 25 °C (77 °F) = 20,000 Ω. 30K6A1: 0 °C (32 °F) ≈ 105,305 Ω; 25 °C (77 °F) = 30,000 Ω. PT100A: 0 °C (32 °F) ≈ 100.8 Ω. 1 kΩ Balco: 20 °C (68 °F) ≈ 997 Ω. NTC 10k B=3950: 25 °C (77 °F) = 10,000 Ω; 0 °C (32 °F) ≈ 31.77 kΩ.  PreCon Model 3 (10k): 25 °C (77 °F) = 10,000 Ω. C. Technician workflow Identify the system on site and open the corresponding row in the mapping table. Note the thermistor or RTD curve indicated. Open the attachment listed and use the R–T table to configure the controller and validate readings.

Issue How to request an evaluation license for TAC Vista. Product Line TAC Vista Environment TAC Vista 5 Cause Starting 1 September 2025, TAC Vista evaluation licenses are no longer publicly available. Only Schneider Electric employees may request them. EcoXpert partners must request evaluation licenses through their Schneider Electric representative. Resolution TAC Vista Evaluation Licenses are available upon request: EcoXperts should contact their country or regional Customer Care Center to request an evaluation license. Schneider Electric employees can request an Evaluation License using the support@Schneider portal: Open a case in the Digital Offer Sales & Provisioning App Request portal. Complete the form with the following selections: What is your request related to? → Digital Supply Chain – Request Environment → Production Offer → TAC VISTA SESA ID → SESA ID of the Schneider Electric employee submitting the request Type of Request → Create Type of Create Request → Demo license creation Country → Country of the requester Business justification → Reason the evaluation license is needed Submit the ticket. The system handles the request automatically and sends the license via email. The ticket closes automatically upon completion.

Issue A technician or user needs to identify the IP address configuration of a Windows workstation. This is commonly required during troubleshooting, commissioning, or connecting to BMS servers and controllers. Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Operation, EcoStruxure Security Expert, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Windows Operating Systems (Windows 95 through Windows 11) Cause The IP address, subnet mask, or gateway of the PC must be confirmed to ensure correct network communication with building automation devices. Typical scenarios include: Unable to connect to Automation Server BACnet or Modbus devices not discovered PC on the wrong subnet DHCP not functioning Verifying network configuration for onsite support Resolution The following methods show how to retrieve IP information across different Windows versions. 1. Windows 7, 8, 10, 11 (Modern Operating Systems) Command Prompt Method Open Command Prompt: Press Windows Key + R, type cmd , press Enter Or search for “Command Prompt” Run: ipconfig Sample Output Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix : corp.local IPv4 Address. . . . . . . . . . : 192.168.10.45 Subnet Mask . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . : 192.168.10.1​ Full Details To view additional fields such as DHCP server, DNS, and adapter description: ipconfig /all Sample Output Windows IP Configuration Host Name . . . . . . . . . . . : TECHSUPPORT-PC Primary Dns Suffix . . . . . . : corp.local Node Type . . . . . . . . . . . : Hybrid Ethernet adapter Ethernet: Description . . . . . . . . . . : Intel(R) Ethernet Connection I219-LM Physical Address. . . . . . . . : B4-2E-99-01-34-AB DHCP Enabled. . . . . . . . . . : Yes IPv4 Address. . . . . . . . . . : 192.168.10.45(Preferred) Subnet Mask . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . : 192.168.10.1 DHCP Server . . . . . . . . . . : 192.168.10.5 DNS Servers . . . . . . . . . . : 192.168.10.20 192.168.10.21   Graphical Method (Modern Windows) Go to Settings > Network & Internet Select Ethernet or Wi‑Fi Choose the active network View IP settings (IPv4) This section shows IP address, subnet, gateway, DNS, and DHCP/static status. 2. Windows 2000, XP, Vista These systems use the same commands as modern Windows versions: ipconfig ipconfig /all Outputs are similar but may lack newer fields (e.g., IPv6). 3. Windows 95, 98, ME Use the legacy tool WINIPCFG. Go to: Start > Run Type: winipcfg Select the correct adapter from the drop‑down list. Sample Output Windows IP Configuration Adapter Address: 00-80-C8-FB-3E-21 IP Address: 192.168.1.15 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.1.1 DHCP Server: 192.168.1.5 DNS Servers: 192.168.1.20   Additional Troubleshooting Notes for BMS Engineers If the PC displays a 169.254.x.x address, it is not communicating with a DHCP server. For direct connection to an Automation Server: Set the PC to a static IP in the same range as the AS (default AS IP is typically DHCP or user-defined). Verify only the required adapter is enabled (multiple adapters can cause routing conflicts). USB-to-Ethernet adapters often appear with different names—verify you are checking the correct interface.

Issue When troubleshooting LonWorks devices, configuration parameters (SCPTs and UCPTs) stored inside the FILE section of a XIF file can be difficult to interpret. The FILE template and value blocks contain encoded definitions that determine how device configuration data is stored and retrieved. Without understanding this structure, diagnosing NCI-related issues becomes challenging.   For information regarding NCI's that are not part of a FILE definition, refer to Understanding the NVVAL part of a XIF file Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment LonWorks Networks XIF files containing FILE template and FILE value sections Devices where configuration parameters (CPTs) are part of a FILE block rather than NVVAL Cause Certain configuration parameters (SCPT/UCPT values) are stored in the FILE section of a XIF file. FILE template 0 2 "1.1;" "2,23.24.25.26.27.28.29.30.31.32.33.34.35.36.37.41.42.43.45.46,0\x80,49,2;" "1,1,0\x80,60,12;" "1,1,0\x80,52,2;" "2,0.2.3.5.6.7.8.9.10.16.17.18.19.20.21,0\x80,48,2;" "1,0,0\x80,17,31;" "1,1,0\x80,34,2;" "1,1,0\x80,23,2;" "1,1,0\xA4,169,1;" "1,1,4\x80,3,8;" "1,1,4\x80,5,17;" "1,1,3\x80,1,2;" "1,1,4\x80,4,9;" "1,1,4\xA4,13,1;" "1,1,4\xA4,14,1;" "1,1,4\xA4,15,1;" "1,1,4\xA4,16,1;" "1,1,4\xA4,17,1;" "1,1,4\x80,18,1;" "1,1,0\x80,42,2;" "1,1,0\x80,36,2;" "1,1,0\x80,193,2;" "1,1,4\x80,8,2;" "1,0,3\x80,2,2;" "1,0,0\x84,165,1;" "1,0,0\xA4,166,1;" "1,1,6\xA4,2,8;" FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, 0x09, 0xFB, 0x0B, 0x80, 0x08, 0x77, 0x07, 0x98, 0x06, 0x13, 0x00, 0x02, 0x23, 0x28, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x78, 0x7F, 0xFF, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x80, 0x80, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0xFF, 0xFF, 0x7F, 0xFF, 0x7F, 0xFF, 0x13, 0x88, 0x00, 0x00, 0x02, 0x0B, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00 This section can appear cryptic because: CPT definitions use multi-field encodings. Flags (e.g. device-specific, read-only, manufacturing-only) are encoded as hex. Byte offsets and lengths are defined indirectly via the template. Vector lengths must be interpreted via combined fields. The value block is a raw byte array that must be decoded using the template. These factors make interpreting configuration values difficult without a breakdown of the template format. Resolution The FILE section contains two parts that work together: FILE template and FILE value. 1. FILE Template (Structure Definition) The FILE template defines how each CPT is stored. Example: "1,1,0\x80,60,12;" Each entry follows the format: "A,B,C\xDD,E,F,G;" Field meanings A – Ownership 0 device 1 function block 2 network variable B – Function block or variable index C – Type selector 0 SCPT 3,4,5,6 UCPT DD – Handling flags (bitfield) a: Always 1 c: Device-specific d: Manufacturing-only e: Reset required after change f: Read-only g: Device must be offline to write h: FB must be disabled to write E – CPT index F – CPT byte length G – Optional vector multiplier Example interpretation: "1,1,0\x80,60,12;" CPT belongs to FB 1 Standard CPT (SCPT) No special flags set (0x80) Index 60 → SCPTsetPnts (based on SNVT_temp_setpt) Length 12 bytes 2. FILE Value (Encoded Data Block) The FILE value section contains the raw bytes for all CPTs defined in the template. Example: FILE value 1 1 116 0x0B, 0xB8, 0x09, 0x1D, ... First two numbers identify a value section. The optional length (116 bytes) should match total CPT byte requirements. Each CPT’s data must be decoded using: Its offset (from template sequence) Length (field F × optional G) SNVT/SCPT resolution rules Example decoding: CPT entry: "2,23.24...45.46,0\x80,49,2;" Refers to SNVT_time_sec (index 49). First two bytes: 0x0B 0xB8 = 101110111000 (binary) = 3000 decimal → 300.0 seconds. Example: SCPTsetPnts (12 bytes) "1,1,0\x80,60,12;" SNVT_temp_setpt values decoded: Bytes Decimal Adjusted Member 09 1D 2333 23.33 occupied_cool 09 FB 2555 25.55 standby_cool 0B 80 2944 29.44 unoccupied_cool 08 77 2167 21.67 occupied_heat 07 98 1944 19.44 standby_heat 06 13 1555 15.55 unoccupied_heat Troubleshooting Tips Verify the total byte length in FILE value matches all template-defined CPT lengths. Confirm SCPT/UCPT index maps to correct SNVT type. If TAC Vista cannot import CPTs linked to NVs, update entries: "2,..." → "1,1,..."

Issue Guidance is required on correct installation, configuration, and usage of Wireshark to capture and analyse Ethernet or BACnet communications for diagnosing Building Management System (BMS) issues. Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Security Expert Environment Ethernet networks BACnet IP or BACnet MS/TP IP‑connected BMS controllers Packet capture and protocol analysis using Wireshark Cause Network or protocol issues require packet-level inspection to diagnose device behaviour, communication failures, timing issues, protocol errors, or unexpected traffic patterns. Resolution 1. Downloading and Installing Wireshark Download the latest version from: https://www.wireshark.org If using a zipped installer, extract and run the executable. Follow the installer prompts to complete installation. 2. Rules and Best Practices for Capturing Network Traffic 2.1 WHERE to Capture (Critical for Accuracy) Capture traffic as close as possible to the device exhibiting the issue. If the issue is at a controller, capture directly on that controller’s port (IP or MS/TP). If analysing interactions between multiple devices (Enterprise Server, Automation Server, JACE, HVAC plant), capture at the device performing the BACnet client/server role. Placement matters; think of it like placing a microphone in the correct location to capture the right sound. 2.2 HOW to Capture Ethernet / IP captures Use one of the following: Network Tap (e.g. SharkTap,) Managed Switch with Port Mirroring enabled (see How to Configure a NETGEAR Prosafe Plus Switch for Mirroring.) Avoid: Unmanaged switches Managed switches without mirroring These will filter unicast traffic, preventing Wireshark from seeing controller‑to‑device communications. Port mirroring configuration must: Mirror all inbound and outbound traffic for the controller interface Apply zero filtering BACnet MS/TP captures To capture MS/TP: Use a RS‑485 adapter Connect directly to the MS/TP trunk Ensure correct polarity and bus loading Refer to Capture BACnet MS/TP Traffic 2.3 WHAT to Look For When Capturing Verify you can see: Broadcast packets Packets to and from the target device’s IP address Use filters such as: bacnet bacapp bvlc ip.addr == <device_IP> 2.4 WHEN to Capture Start capturing before the issue occurs. If waiting for an intermittent condition (e.g. generator test, network reconvergence, power cycle), use: Capture ring buffer Continuous rolling captures Document: Exact times events occurred Steps used to reproduce Any observed symptoms This allows correlation between traces and known events. Reference: Wireshark Capture Ring Buffer 3. Preparing Before Analysis To ensure meaningful analysis, collect the following: 3.1 System Documentation Network architecture diagrams Switches and routers involved VLANs, port configuration, any LACP/RSTP involvement IP addresses and MAC addresses for all relevant devices BACnet device instance IDs, object types, object IDs 3.2 Event and Operations Data Process steps or operations performed (with timestamps) What was happening at the moment of failure or anomaly Any manual actions triggered by the operator 3.3 Protocol Understanding Issues may originate at lower OSI layers than expected. Be familiar with: ARP DHCP NTP SNMP SMTP RSTP UDP / TCP BACnet (IP + MS/TP) BACnet Behaviour to Consider COV subscription renewal on device restart Typical COV notification frequency (no more than ~4/min per object) Time Sync timing (EBO and Continuum: hourly, at xx:38) Write-on-change behaviours Decoding BACnet errors 4. Capturing Traffic with Wireshark Open Wireshark Select Capture → Interfaces Identify the correct NIC (via IP address or packet counter) Click Start Reproduce or wait for the issue Click Capture → Stop Save capture via File → Save As 5. Starting Analysis in Wireshark 5.1 Validate the Capture Check Statistics → Capture File Properties (Confirm time window covers the incident) Check Analyze → Expert Information (Warnings, malformed packets, error counters) 5.2 Apply Appropriate Filters Examples: bacnet bvlc bacapp.service == readproperty eth.addr == <MAC> ip.addr == <IP> For BACnet, refer to the Wireshark Profiles: BACnet EBO forum post 5.3 Analyse Against the Problem Statement Compare packet activity to expected behaviour Examine frequencies (COV, Time Sync, I-Am, Who-Is) Identify delays, retries, rejected messages, or malformed frames Correlate timestamps with known events

Issue Technicians may spend unnecessary time completing database checkouts or troubleshooting LonWorks networks when using Newron NL220 without leveraging its full set of tools, shortcuts, and efficiencies. Product Line TAC Vista Environment Newron NL220 LNS-based LonWorks networks Cause NL220 provides several built-in tools such as database search filters, hotkeys, device template functions, and automated browsing options. If these capabilities are not used, field engineers may take longer to locate devices, validate network variables, update templates, or troubleshoot communication issues. Resolution Use the following NL220 functions and shortcuts to improve productivity: 1. Database Searching NL220 supports wildcard searching to quickly locate nodes or variables: Name* searches for names beginning with specified text *Name searches for names ending with specified text *Name* searches inside full strings Name finds exact matches The search toolbar at the top of the NL220 window provides fast access to these filters. The buttons found on this toolbar are defined below. 2. General Toolbar Tools The general toolbar includes shortcuts for navigation, browsing, and template-based operations. Key features include: Automatic browser function for viewing selected NVs Quick access to device templates, subsystems, and network views 3. Automatic Browse Configuration To enable auto-browse: Open the Templates tab. Select a device template (for example, 102-AX). In the NVs tab, check the Browse column for required network variables. Open the Subsystem tab. Click Automatic Browse on a controller using the modified template. NL220 will automatically populate a browse window showing only the selected NVs. 4. Filter Toolbar The filter toolbar allows targeted viewing of: Commissioned or uncommissioned nodes Specific network variable types Node/variable names or patterns This helps narrow down large system databases. 5. Network Menu Functions Right‑clicking nodes in the tree window exposes the Network menu, which includes commissioning, decommissioning, testing, and diagnostic operations. These functions streamline device-level troubleshooting. The functions of these icons are defined in the chart below. 6. Updating Network Variables After XIF Changes When modifying a device’s XIF file: Open the Templates tab Right‑click the template Select Rename variables of all application devices This renames all associated NVs to match the updated template. Important: Review SNVT bindings afterwards. Variable order may change if SNVTs were added, renamed, or removed. 7. Creating a New Device Template To add a new device: Open Templates Right‑click > New device template Enter a name and load the associated XIF file Refer to “Adding a Xenta Programmable Controller to an NL220 System” for detailed guidance. 8. Additional Resources NL220 Manual (PDF) NL220 Tutorial (PDF) Echelon LonMaker and NL220 compatibility guidance Ordering more LNS credits Ordering more Newron NL220 credits The difference between NL220I and NL220M dongles How to Rehost an NL220 Dongle to another PC LOYTEC NIC-USB in NL220 Creating LNS database in NL220 and transferring it into TAC Vista procedures outline Adding a Xenta Programmable Controller to an NL220 System Downloading new NXE or APB files using NL220

Issue Need to mirror a switch port on a NETGEAR ProSafe Plus switch to capture controller network traffic using Wireshark. Product Line Andover Continuum, EcoStruxure Access Expert, EcoStruxure Building Operation, TAC IA Series, TAC INET, TAC Vista Environment NETGEAR Prosafe Plus Switch Packet capture tools (for example: Wireshark) Cause A mirrored port is required because switches only forward traffic to the destination device’s port. A laptop connected to another port cannot see controller communications. Mirroring creates a copy of packets from the source port and sends them to a dedicated monitoring port, allowing Wireshark to capture actual controller traffic for diagnosing BACnet, Modbus, or general communication issues. This provides full visibility without interfering with network operation. Note: From EBO 2024 (V6.0) and later, AS‑P and other EBO servers include a native packet capture feature that records BACnet/IP and BACnet MS/TP messages visible to the server. This reduces the need for external port mirroring when troubleshooting BACnet traffic. Resolution Access the switch through the ProSafe Plus Utility or the web interface. Navigate to the Port Mirroring configuration page. Select the controller‑connected port as the Source (Tx/Rx/Both). Select an unused port for the laptop as the Destination. Apply and save the configuration. Connect the laptop to the destination port and begin capturing with Wireshark. Refer to the attached video or the original Area360 post for detailed instructions.

Issue Need to identify approved and supported Belden cable models suitable for LonWorks TP/FT‑10, TP/XF‑78 and TP/FT‑1250 networks when the commonly referenced Belden 8471 and 85102 are unavailable locally. Product Line EcoStruxure Building Operation, Satchwell MicroNet, TAC IA Series, TAC Vista Environment LonWorks networks (TP/FT‑10, TP/XF‑78, TP/FT‑1250) Cause Echelon’s “Junction Box and Wiring Guideline for Twisted Pair LonWorks Networks” recommends Belden 8471 and Belden 85102. These cables may not be stocked or available through local Belden offices or distributors, requiring alternative approved Belden models. Resolution Refer to Belden Technical Bulletin TB102E – “Belden Cables for LonWorks Networks” for a full list of Belden cable models qualified for LonWorks communication. Key considerations when selecting an alternative cable: Ensure the cable is listed as LonMark compliant or explicitly supported for LonWorks twisted‑pair networks. Review differences in maximum drop length and maximum total bus length, as these vary across Belden cable part numbers. Confirm that conductor type, twist rate, impedance, and capacitance meet LonWorks TP/FT‑10 or TP/XF‑78 requirements per project design.

Issue HyperTerminal is no longer included with Windows operating systems starting from Windows Vista, preventing users from using the tool for serial communication, controller configuration, or troubleshooting. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows Vista Windows 7 Windows 8/8.1 Windows 10 Windows 11 Cause Microsoft removed HyperTerminal from Windows Vista and later versions. As a result, the application is no longer available natively on modern operating systems. Resolution Install Original Windows XP HyperTerminal Files Download the provided HyperTerminal.zip containing: hypertrm.exe hypertrm.dll Extract the files to a local directory. Launch HyperTerminal via hypertrm.exe. For cable and communication settings, see: Connecting a serial cable to a Xenta 5/7/9xx controller. Manual Copy from XP Installation or CD Alternatively: hypertrm.exe can be copied from C:\Program Files\Windows NT hypertrm.dll can be copied from C:\Windows\System32 Both files are also located in the i386 directory on a Windows XP installation CD. Modern Alternatives to HyperTerminal PuTTY (Recommended Free Alternative) PuTTY is a widely used open-source terminal emulator that supports serial, SSH, and Telnet connections. It is lightweight, portable, and reliable for connecting to BMS controllers via COM ports. Recognized as a top free alternative to HyperTerminal. Also listed as the leading open-source replacement. Use Cases: Connecting to automation controllers via serial console BACnet/Modbus/Field device commissioning Troubleshooting serial communication Other Modern Alternatives Tera Term Open-source terminal emulator commonly used for serial console access. Listed among modern HyperTerminal alternatives. RealTerm Designed for capturing and debugging complex binary data streams. Considered far more capable for comms debugging than HyperTerminal. CoolTerm Simple serial terminal for embedded devices and sensor interfaces. Listed as a useful free alternative. YAT – Yet Another Terminal Engineering-grade tool supporting RS‑232/485 and TCP/IP communication. Highlighted as an open-source HyperTerminal alternative.

Issue A LonWorks controller needs to have its External Interface File (XIF) extracted to support integration into a Building Management System (BMS). The required XIF may not be available from the device manufacturer, or the provided file may be incomplete or cause issues during import. Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment LonWorks controllers External Interface File (XIF) Tools: NodeUtil Loytec XIF Builder Vista XIF Builder Cause An XIF file describes the network interface, network variables, and configuration properties of a LonWorks device. Certain integrations require a correct XIF to generate device templates such as: Niagara R2 shadow objects Niagara G3 LMNL files LonWorks device templates EcoStruxure Building Operation device templates If the manufacturer’s XIF is unavailable or contains incomplete headers, missing SCPTs, or incorrect NV definitions, it may be necessary to extract the XIF directly from the controller. Resolution Use the Manufacturer-Provided XIF First The device manufacturer should supply an XIF file and, where required, a DRF kit. The DRF kit cannot be generated using any extraction tool and must always come from the manufacturer. If Needed, Extract the XIF Using One of the Following Tools: Tool Notes NodeUtil Freely available from Echelon. Extracts NVs correctly but may produce incomplete headers and omit DMA/File SCPTs. Vista XIF Builder Similar limitations to NodeUtil. NV extraction is mostly correct, but headers and specialized SCPTs may be incomplete. Loytec XIF Builder Generates highly accurate XIF files when used with devices based on Loytec’s LonWorks stack. Considered the most reliable extraction method Accessing the Tools NodeUtil is available with free registration on the Echelon website. The provided NodeUtilLauncher package simplifies using NodeUtil with Loytec interfaces. Loytec XIF Builder requires free registration on the Loytec website. Additional Notes If the extracted XIF contains detailed errors on import into EcoStruxure Building Operation, consult the article titled “Error displayed when importing a device XIF into SmartStruxure” for troubleshooting steps. Always verify that a DRF kit accompanies the device, as it cannot be recreated.

Issue LonWorks network communication can become unreliable or fail completely when wiring and topology guidelines are not followed during installation. Many issues are preventable with correct network design. Product Line Satchwell BAS & Sigma, TAC IA Series, TAC Vista, Satchwell MicroNet, EcoStruxure Building Operation Environment I/A Series MicroNet (LON) Controllers Satchwell MicroNet LON Controllers TAC Vista TAC Xenta Controllers Cause The I/A Series MicroNet System Engineering Guide (F-26507) provides installation requirements for MNL‑100/200/VAV controllers and Satchwell MicroNet 440/620 devices. Misinterpretation or omission of these design rules leads to wiring errors, incorrect topology, improper termination, or device‑count issues that degrade network performance. Resolution Follow these FTT‑10 LONWorks design rules to ensure a stable and standards‑compliant network. 1. Approved Cable Types Use Echelon‑approved twisted‑pair cable. Most common: Category 4, unshielded, stranded twisted‑pair, 22 AWG (0.65 mm). Example: Connect-Air W221P / W222P. Use plenum‑rated or shielded versions when required by site specification. 2. Supported Topologies Bus Topology Daisy‑chain wiring, no branches or stubs. Install LON‑TERM‑2 terminators at each end of the bus. Maximum length using standard Cat 4 cable: 4593 ft (1400 m). MN‑Sx sensor bases must be in-line, not connected as stubs. Free Topology Flexible layout (stars, tees, mixed). Requires one terminator: LON‑TERM‑1. Maximum total cable length: 1641 ft (500 m). Maximum distance between any two controllers: 1312 ft (400 m). 3. Common Wiring Guidelines Do not run LON wiring in an active telephone trunk, even if Cat 4. Use shielded cable only in high EMI/RFI areas. Ground the shield at one end only through a shield terminator. Do not bundle LON wiring with controller I/O or power wiring. 4. Device Count & Segmentation Maximum 64 devices per LON segment, including: Controllers Network Interface Routers / Repeaters Split larger networks into segments using LonWorks repeaters or routers. Each segment must be terminated appropriately for its topology. 5. Addressing Guidelines LON controllers use Domain / Subnet / Node addressing. A single subnet supports up to 127 node addresses, including: Controllers Interfaces Routers / Repeaters Leave address space for commissioning tools when planning subnets.