Issue When launching or using BAS 2800+, the message "No Logging Databases Have Been Specified" appears. Product Line Satchwell BAS & Sigma Environment Satchwell BAS 2800+ Cause A logging database has not been assigned in the BAS 2800+ Dataview configuration. This can occur when: No logging database has ever been set The registered database list is empty The existing database file has been moved, removed, or is no longer accessible Resolution Follow these steps to register and assign a BAS 2800+ logging database: Log on to the BAS 2800+ system. Open Dataview. From the menu, select File > New. Then select Data > Logging Database. In the Registered Database window: If a database is listed, select it; or If the window is empty, click Add and browse to the desired logging database file. The default file installed with the software is BAS2800.DBS. Click OK to register the database. In the Logging Database window, click OK again to assign it. The error message should no longer appear once the logging database is properly configured.

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 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 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 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.

Issue A PC is experiencing communication problems or application startup failures because one or more TCP or UDP ports are already in use. Users need a reliable method to determine which application or service is occupying specific ports. Product Line All product Lines. Environment Any Windows operating system Cause Multiple applications running on the same PC may require the same network ports. If port assignments are not managed, this can lead to TCP/UDP conflicts that affect building management software, web servers, databases, or other services. Resolution Use Microsoft TCPView to identify all active TCP and UDP ports, including the associated processes and services. Steps Download TCPView from the official Microsoft Sysinternals site: https://technet.microsoft.com/en-us/sysinternals/bb897437.aspx Extract and run TCPView.exe. The interface displays: Active TCP and UDP endpoints Process names and paths Local and remote addresses Connection states Sort or filter to identify which application is using a specific port. Close or reconfigure the conflicting application as required. TCPView documentation on the Microsoft site includes detailed usage instructions.

Issue The network interface card (NIC) on a PC is not functioning or is suspected to be faulty. 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 PC Network Interface Card (NIC) Cause A NIC may fail to operate correctly due to: Missing or incorrect network drivers Disabled network interface Physical disconnection Hardware damage Misconfigured TCP/IP protocol stack Resolution 1. Identify the Network Interface Open Command Prompt. Run: ipconfig Review the list of network interfaces and locate the NIC by its adapter name. Record the assigned IP address (if present). 2. Check Physical and Driver Status If the NIC shows as Media Disconnected, plug in a network cable and re-run ipconfig . If the NIC does not appear in the ipconfig output: Open Device Manager and confirm the NIC is listed. If missing, install or update the correct drivers. If present but disabled, go to Control Panel > Network Connections, right‑click the adapter, and select Enable. 3. Determine if the NIC Is Responding Once the NIC has a valid IP address: Open Command Prompt. Ping the NIC’s own IP address: ping <NIC_IP_Address> A functional NIC should return 4 successful replies and associated ping statistics. 4. Verify TCP/IP Stack Functionality Before pinging the NIC IP, you can check baseline TCP/IP operation: ping 127.0.0.1 This tests the local TCP/IP stack only. A successful reply indicates that the protocol stack is operational, although it does not confirm NIC functionality. 5. Determine if the NIC Is Faulty If: The NIC never appears in ipconfig , The device is not detected even with correct drivers, or The adapter cannot be enabled… …it is likely the NIC hardware is damaged and requires replacement.

Issue Teams need authoritative Modbus references and a concise troubleshooting workflow when integrating Modbus devices with EcoStruxure Building Operation and legacy Schneider Electric BMS platforms. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, TAC IA Series, TAC Vista Environment Modbus RTU on RS-485 Modbus ASCII on RS-232 or RS-485 Modbus TCP/IP on Ethernet Cause Modbus is an open, widely adopted protocol (introduced by Modicon in 1979). Integration issues typically arise from configuration mismatches, wiring or electrical layer issues on RS-485, device capability differences in function codes and data types, register addressing offsets, scaling and endianness differences, and timing parameters such as timeouts and inter-frame delays. Resolution Use the following authoritative references and step-by-step workflow to plan, commission, and troubleshoot Modbus integrations. 1) Official specifications and where to find them The official Modbus specifications and guides are hosted on the Modbus Organization website under Technical Resources. Key documents: Modbus Application Protocol Specification V1.1b Modbus Messaging Implementation Guide V1.0b 2) Quick protocol recap Modbus data model Coils: 00001 series, 1-bit read or write Discrete Inputs: 10001 series, 1-bit read only Input Registers: 30001 series, 16-bit read only Holding Registers: 40001 series, 16-bit read or write Framings and transports Variant Transport Framing and notes RTU RS-485 Binary framing with CRC. Timing sensitive. ASCII RS-232 or RS-485 ASCII framing with LRC. Less common. TCP/IP Ethernet Encapsulated in MBAP header. No CRC at application layer. Unit ID used by gateways to target RTU slaves. Addressing basics RTU or ASCII: 1 to 247 device addresses on a bus TCP: Unit ID often 0 or 255 for a direct TCP server. Through a gateway, Unit ID maps to the RTU slave address. 3) Pre-commissioning checklist Obtain the device Modbus register map from the manufacturer. Confirm: Register ranges and function codes supported Data types and length (16-bit, 32-bit, float), endianness, any word or byte swapping conventions Scaling, units, and valid ranges Decide the transport: RTU for simple RS-485 segments with limited bandwidth TCP for Ethernet segments or when using IP-based gateways Plan RS-485 topology: Daisy chain wiring, proper termination and bias, consistent ground reference, cable type and length within RS-485 guidelines Define serial parameters uniformly for RTU or ASCII: Baud rate, parity, data bits, stop bits Define polling strategy: Group contiguous registers, set realistic poll rates and timeouts, avoid over-polling slow devices 4) EBO-specific implementation tips In EBO, create a Modbus Network and add Modbus Devices with the correct addressing: RTU or ASCII: set the slave address to match the device TCP: set the IP and port, and the Unit ID according to the gateway or device rules Configure serial link objects for RS-485 trunks: Match baud, parity, data bits, stop bits, and inter-frame timing to device requirements Point objects: Map to the correct data model (Coil, Discrete Input, Input Register, Holding Register) Apply scaling and any word or byte swaps required by the device map Performance and reliability: Start with conservative poll intervals, then tune based on device response and network load Batch contiguous register reads when possible to reduce transactions Use EBO diagnostics to check retries, timeouts, and error counters to pinpoint transport vs. application issues 5) Troubleshooting workflow Physical layer first Verify RS-485 wiring order, shield, termination at both ends, and biasing. Measure voltage levels if needed. Confirm only one master on an RS-485 segment and that devices are powered and online. Link and timing Align serial settings exactly across the segment. Adjust timeouts and minimum inter-frame delays if you see CRC errors or framing errors. Addressing and function codes Confirm slave address or Unit ID. Ensure function codes used by the BMS are supported by the device for each register range. Register mapping and data interpretation Verify base addressing convention used by the device documentation (0-based vs 1-based). Apply correct scaling and endianness. Test with a known-good register like a firmware version or a static value. Isolate with a test tool Temporarily connect a Modbus test client to validate reads and writes to target registers with known parameters. Optimize and monitor Reduce poll rate if the device is slow. Group reads and avoid unnecessary writes. Monitor retries and errors in EBO diagnostics after each change. 6) Standard Modbus Exception Codes These originate from the slave device and are defined in the Modbus Application Protocol Specification. Code Name Meaning / Typical Cause 01 Illegal Function Function code not supported by the device. Wrong register type or device limitation. 02 Illegal Data Address Register does not exist in the device map. Wrong offset or range. 03 Illegal Data Value Value out of range (e.g. write value too large). 04 Slave Device Failure Internal device error processing the request. 05 Acknowledge Device accepted request but needs long processing time. 06 Slave Device Busy Device temporarily unable to process the request. 07 Negative Acknowledge Device rejected the request. 08 Memory Parity Error Memory read problem on the device. 0A Gateway Path Unavailable Routing/gateway problem. 0B Gateway Target Failed to Respond TCP‑to‑RTU gateway could not reach the RTU slave.   7) References Modbus specifications and guides: Technical Resources on the Modbus Organization website Modbus Application Protocol Specification V1.1b Modbus Messaging Implementation Guide V1.0b Schneider Electric Community Knowledge Center Modbus Troubleshooting PDF

Issue Explanation of how Domain Name System (DNS) works and what occurs when a hostname cannot be resolved in a building automation environment. 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 TCP/IP networks supporting Building Management Systems (BMS) Cause Users may require an understanding of how DNS functions, how hostnames are translated into IP addresses, and what causes DNS lookup failures in automation networks. Resolution How DNS Works DNS is a hierarchical, distributed naming service that translates human‑readable domain names into numerical IP addresses required for network communication. There is no single central database; instead, DNS information is spread across multiple DNS servers arranged in a global hierarchy. When a client queries a hostname: The resolver checks local DNS cache If not found, it queries the configured DNS server That server may consult other DNS servers up the hierarchy The process continues until an authoritative answer is found The returned IP address is used for communication Example: www.example.com → 198.105.232.4 This translation is required because while domain names are easier for users to remember, underlying systems communicate using IP addresses. What Happens When a Name Cannot Be Resolved If DNS cannot successfully translate a hostname, the failure results in one of the following conditions: 1. NXDOMAIN – Non-Existent Domain Occurs when DNS determines that the name does not exist anywhere in the DNS hierarchy. Outcome: Client receives "Host not found" or "Domain does not exist" Communication using that hostname fails immediately 2. SERVFAIL – DNS Server Error Occurs when DNS servers are reachable but unable to respond correctly, often due to: Server misconfiguration Firewall blocking Server outage Outcome: Lookup retries occur Client eventually times out Applications may experience slow response or delays 3. Timeout – No Response Occurs when DNS servers are unreachable or do not answer. Outcome: Resolver waits for retry intervals Secondary DNS may be queried Final result is a timeout error Impact in Building Automation Systems Failure to resolve hostnames can result in: Automation Servers failing to reach the Enterprise Server Cloud services (EBO cloud connectors, remote notifications, licensing endpoints) becoming unreachable Time sync failure when using NTP via FQDN Email notification failures when using the server's hostname name such as smtp.gmail.com BACnet, Modbus TCP, or integration gateways failing if hostname references are used WebStation or client logins slowing due to DNS lookup delays Proper DNS configuration is essential for reliable communication across all Schneider Electric Building Management platforms.

Issue When using CIDR or subnet masks that include non‑255 values, it is not always obvious which IP addresses are valid within a subnet. Users need guidance on calculating the valid IP address range, including how to perform the calculation manually. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Device Administrator Building Commissioning Tool Any system using IPv4 subnets with masks that include values other than 255 Cause Subnet masks define which bits of an IPv4 address represent the network portion and which represent the host portion. When masks include values such as 128, 192, 224, 240, 248, 252, or 254, determining the correct IP range is less intuitive. This often results in invalid IP assignments or misconfiguration during commissioning. Resolution Users can determine valid IP address ranges either by using an online subnet calculator or by performing a manual calculation. Both methods are described below. 1. Understanding Subnet Masks A subnet mask marks the network bits with 1s and host bits with 0s. Example: 255.255.255.0 Binary: 11111111.11111111.11111111.00000000 This corresponds to /24, meaning 24 bits define the network. Valid decimal values for subnet mask octets are derived from binary boundaries: Decimal Binary 0 00000000 128 10000000 192 11000000 224 11100000 240 11110000 248 11111000 252 11111100 254 11111110 255 11111111 Any subnet mask containing one of these non‑255 values requires a block‑size calculation. 2. Manual Calculation Method The following steps allow you to calculate the network address, broadcast address, and usable IP range without a subnet calculator. Example IP Address: 192.168.10.55 Subnet Mask: 255.255.255.240 (/28) Step 1. Determine the block size Use the last non‑255 octet of the subnet mask: Block size = 256 – mask_octet Block size = 256 – 240 = 16 This means each subnet increments in steps of 16: 0–15 16–31 32–47 48–63 64–79 ... 240–255 Step 2. Identify the block containing the IP The IP’s last octet is 55, which falls into the block: 48–63 Step 3. Network address Start of the block: 192.168.10.48 Step 4. Broadcast address End of the block: 192.168.10.63 Step 5. Usable host range All addresses between network and broadcast: 192.168.10.49 – 192.168.10.62 This manual method works for any subnet mask. 3. Using Online Subnet Calculators Although the manual method is precise, online tools speed up the process and reduce the chance of error, especially when dealing with large networks or multiple subnets. Recommended tools: Online IP CIDR / VLSM Supernet Calculator IP Subnet Calculator Steps: Enter an IP address within the network. Enter the subnet mask or CIDR prefix. The tool will display the network address, broadcast address, and usable range. Mobile subnet calculator apps are also available for Android, iOS, and Windows.

Issue How to confirm whether a PC’s RS‑232 serial communication port is functioning correctly by performing a loopback test in a terminal emulator. Product Line Andover Continuum, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Building Operation Environment Windows PC RS‑232 serial ports (DB9) Terminal emulator (HyperTerminal or equivalent) Cause Communication failures over RS‑232 can result from: Faulty or damaged COM ports Incorrect or incompatible wiring/cables Misconfigured port parameters USB‑to‑Serial adapter issues Incorrect TX/RX pin identification A loopback test verifies that transmitted data (TX) is properly received (RX), confirming basic port integrity. Resolution 1. Prepare the Loopback Connection Short the TX and RX pins on the DB9 connector: Pin 2: RX Pin 3: TX Ensure the correct gender and pin orientation when identifying pin numbers.                  Male DB9 (Left) and Female DB9 (right)   2. Open a Terminal Emulator HyperTerminal Launch HyperTerminal. If prompted for modem installation, select No. Create a new connection and choose Direct to COMx (your target port). Set Flow control = None. In Settings → ASCII Setup, enable Echo typed characters locally. Open the connection. PuTTY (Recommended Alternative) Open PuTTY. Select Serial in the left panel. Configure: Serial line = COMx Speed = 9600 (or match device requirements) Flow control = None Start the session. 3. Perform the Loopback Test Type characters in the terminal window: Expected (Port OK): Characters appear twice One echoed locally One returned from the RX‑TX short If characters appear only once: The COM port is not receiving transmitted data. 4. Troubleshooting If Test Fails Possible causes: Faulty or damaged COM port Incorrect DB9 wiring TX/RX pins not correctly shorted Defective USB‑to‑Serial converter Incorrect COM port assignment in Windows If using USB‑to‑Serial, reassign the adapter to a preferred COM port if needed.

Issue Echelon Node Utility does not natively recognize Loytec NIC‑USB network interfaces, requiring additional steps or tools to use the NIC‑USB with Node Utility operations. Product Line EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC Vista Environment Microsoft Windows 7 32-bit Echelon Node Utility 2.04 Echelon OpenLDV 4.0 Loytec NIC-USB network interface Loytec NIC driver version 4.1.3 Cause Echelon Node Utility relies on Echelon-compatible interface paths. Loytec NIC‑USB interfaces do not automatically register in a way Node Utility can use, so either registry information must be referenced manually or the NIC must be configured to present as LON1. Resolution There are three ways to run Node Utility with a Loytec NIC‑USB network interface. Option 1 — Use NodeUtil Launcher (Recommended) A community-developed tool scans the Windows registry and automatically identifies compatible interfaces. Note: Schneider Electric Product Support does not provide support for NodeUtil Launcher. For assistance, contact the developer. Option 2 — Manual Registry Method Open LConfig and verify the NIC‑USB under the USB tab. Open regedit and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\LonWorks\DeviceDrivers Identify the entry containing _LDV, representing the Loytec interface path. Open a Command Prompt, navigate to the Node Utility directory, and run Node Utility using: nodeutil -D"" Insert the correct device path inside the quotes. Option 3 — Configure NIC‑USB as LON1 Open LConfig, verify the NIC‑USB under USB Select Advanced. Enable LON1 Support for device and choose the correct NIC‑USB. Reboot Windows to apply changes. Run Node Utility from the command line. It should now launch using the NIC‑USB as LON1.

Issue When diagnosing application hangs, crashes, sluggish system behaviour, or installation issues, Product Support may request Windows Event Logs. While the export process is similar across Windows versions, Windows 11 introduces changes to Security log permissions and some Application and Services log channels, which may affect the ability to export or forward specific logs. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Security Expert, EcoStruxure Access Expert Environment Windows Operating Systems Cause Windows Event Logs capture critical diagnostic information across Application, System, and Security categories. These logs provide insight into system state, application behavior, and security‑related events. Although Windows 11 retains the same log categories found in earlier versions, Microsoft has modified the access rights and forwarding behavior of certain logs, particularly the Security and Windows Defender Operational channels. This means some logs may not export or forward as they did in Windows 10, even when GPOs and permissions appear correct. Resolution 1. Opening Event Viewer Event Viewer can be opened using any of the following methods: Press Windows + R, type eventvwr, press Enter Search for Event Viewer from the Start menu Open Control Panel → Windows Tools → Event Viewer 2. Logs Required by Product Support Support generally requires the following logs: Application Security System (Located under Windows Logs) If the case involves Security Expert: Security Expert logs located under Applications and Services Logs → Schneider Electric → Security Expert 3. Exporting Logs For each log: Select the log Go to the Action menu Select Save All Events As Choose a filename and save location On non‑English systems, ensure Display information for these languages includes English (United States) 4. Windows 11–Specific Considerations 4.1 Security Log Behavior Changes Windows 11 introduces changes to how the Security log applies access permissions. After upgrading from Windows 10, users may see: Security logs failing to forward to collectors Permissions appearing correct in policy but not being applied Inconsistent behavior when checking effective channel permissions These issues are due to changes in how Windows 11 enforces access to protected channels and are not caused by misconfiguration. 4.2 Application and Services Logs (e.g., Windows Defender) Certain logs in Windows 11 may not export or forward as expected. For example: Some logs, such as Sysmon, continue to function normally Others, such as Windows Defender Operational logs, may fail to forward or export even with correct SDDL and GPO settings Windows 11 applies additional restrictions on some channels that did not exist in Windows 10. 4.3 Event Forwarding Configuration Is Still the Same The underlying steps for configuring Windows Event Forwarding (WEF) remain unchanged in Windows 11: Enabling the Windows Event Collector service Configuring WinRM Using source‑initiated or collector‑initiated subscriptions Only the behavior of certain logs has changed, not the event forwarding mechanism.

Issue A site requires more than one temperature sensor to be connected to a single controller input, with the goal of producing an averaged temperature value. Only one physical input is available. Product Line Andover Continuum, Field Devices, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista Environment Building automation controllers and field devices that support resistive temperature sensor inputs. Cause Incorrect sensor type or wiring configuration may be used when attempting to connect multiple sensors to one input. Averaging requires a specific number of matched resistive sensors and proper series–parallel wiring. Resolution Use four (4) identical resistive temperature sensors of the same type (for example PT1000 or 10k NTC depending on the controller specification). For applications where two physical sensing locations are required, install two sensors per location (adjacent or within one housing) so the total sensor count equals four. Wire the sensors in the required series–parallel configuration as shown in the diagram below to produce correct averaging across the single input. This ensures the input sees the correct combined resistance and provides an accurate averaged temperature reading.

Issue How to capture clear, reproducible steps for troubleshooting or documenting user actions when supporting Building Management Systems Product Line Andover Continuum, EcoStruxure Building Operation, EcoStruxure Access Expert, EcoStruxure Security Expert, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Windows 7 Windows 10 Windows Server 2008, 2012, 2016 Windows 11 (including versions where PSR is deprecated Cause PSR has historically been used to record screenshots and step-by-step annotated actions to assist support teams in reproducing issues. Microsoft has deprecated PSR in Windows 11 and is transitioning users to more modern built-in tools. PSR remains available in older Windows versions, but is being phased out and will be removed in future releases. Resolution Using PSR on Windows 7, Windows 10, Server OS, and early Windows 11 Open the Start Menu. Type PSR and launch Problem Steps Recorder. Select Start Record. Perform the actions to reproduce the problem. Select Stop Record. Save the generated .zip file. The archive contains an .mht file that can be opened in any browser. The report includes sequential screenshots and a text log of user interactions. PSR continues to function on Windows versions prior to the February 2024 Windows 11 update, even though it displays a deprecation banner on newer builds. Windows 11 and Later: PSR Deprecation and Recommended Alternatives Microsoft introduced a deprecation banner in February 2024. PSR is still present but no longer updated, and will be fully removed in a future Windows release. For BMS support workflows, where clarity and reproducibility are important, the recommended alternatives are: 1. Snipping Tool (Windows 11 built‑in) A modern, integrated tool with screen recording capability introduced in 2023. Allows selection of a specific region to record Produces lightweight MP4 recordings Suitable for capturing short, clear reproduction sequences Ships with Windows 11; can also be downloaded from the Microsoft Store 2. Microsoft Clipchamp A built-in Windows 11 video editor that also includes screen recording. Enables recording of entire screen or application windows Useful for longer or more complex demonstrations Included with Windows 11 or available via the Microsoft Store

Issue Windows event logs, product logs, or error dialog boxes display error codes in decimal or hexadecimal form, but the meaning of these codes is unclear. Product Line Andover Continuum, Satchwell BAS & Sigma, Satchwell MicroNet, TAC IA Series, TAC INET, TAC Vista, EcoStruxure Building Operation, EcoStruxure Security Expert Environment Microsoft Windows Cause Windows uses a standardised set of error codes defined in system header files (for example WinError.h). These appear as hexadecimal values such as 0x00000001 or decimal values such as -214000000 . This formatting makes the codes difficult to interpret without translation. Resolution Microsoft Error Lookup Tool (ERRLOOK / ERR) – Recommended Use Microsoft’s official, up‑to‑date resources instead of the old spreadsheet for decoding Windows error codes. The latest version of the Microsoft Error Lookup Tool provides lookups for Windows system error codes using built-in header files. ➡ Download (Official Microsoft) Microsoft Error Lookup Tool https://www.microsoft.com/en-us/download/details.aspx?id=100432 System Error Code Reference (Microsoft Learn) Authoritative listing of Windows system error codes as defined in WinError.h. Includes code ranges 0–499 and links to full listings. ➡ System Error Codes (0–499) https://learn.microsoft.com/en-us/windows/win32/debug/system-error-codes--0-499- Windows Update–specific Error Codes If the error originates from Windows Update, use Microsoft’s dedicated error code reference (Windows 10 and Windows 11). ➡ Windows Update Error Code Reference https://learn.microsoft.com/en-us/windows/deployment/update/windows-update-error-reference Format Identification Guidance Error codes beginning with 0x are hexadecimal Error codes shown as integers are in decimal format

Issue A power meter specification sheet indicates that the device provides KYZ pulse outputs, and clarification is required on what a KYZ pulse output is and how it is used. Product Line All Product Lines Environment Utility meters or power meters equipped with KYZ pulse output relays Cause Some meter datasheets reference KYZ pulses without defining the term, leading to uncertainty about the electrical function and integration method. Resolution A KYZ pulse output is a pulse-generating mechanism commonly used in electrical metering to represent energy consumption. Key points: Definition KYZ refers to the terminal designations of a Form C relay (SPDT) used in metering applications. K – Common terminal Y – Normally Open (NO) contact Z – Normally Closed (NC) contact How it works The relay switches state (Y closes and Z opens, or vice versa) to generate a clean, isolated pulse. Each transition typically represents a fixed quantity of energy (e.g., 1 Wh, 1 kWh, or similar), depending on the meter configuration. Because the output is relay-based, it provides: Electrical isolation Compatibility with a wide range of low-voltage pulse-counting inputs Noise immunity suitable for utility metering environments Typical use cases Integration with Building Management Systems (BMS) Pulse-counting energy loggers SCADA systems requiring an electrical pulse input Revenue or sub‑metering applications This pulse mechanism allows downstream systems to accurately count energy usage without needing direct access to the meter’s internal measurement circuitry.

Issue How to locate the MAC (Media Access Control) address, also known as the Physical Address, on a Windows computer. Product Line Andover Continuum, EcoStruxure Building Operation, Satchwell BAS & Sigma, Satchwell MicroNet, AC IA Series, TAC INET, TAC Vista Environment All Windows‑based computers used with Schneider Electric Building Management Systems. Cause A MAC address may be required for licensing operations, DHCP reservations, BMS device identification, troubleshooting network communications, or verifying unique hardware identifiers. A MAC address is a 48‑bit hardware identifier displayed as six pairs of hexadecimal characters, such as: 00-1A-2B-3C-4D-5E Structure First 3 octets: Vendor OUI (Organizationally Unique Identifier) Last 3 octets: Unique device portion assigned by the manufacturer Key Bit Indicators LSB of first octet: 0 = Unicast 1 = Multicast Second LSB: 0 = Globally unique (factory-set) 1 = Locally administered (overridden or virtual NIC) Common Format Examples Windows: 00-1A-2B-3C-4D-5E Linux/macOS: 00:1A:2B:3C:4D:5E Cisco: 001A.2B3C.4D5E Resolution Open the Windows Start menu. Select Run or press Windows Key + R. Type cmd and press Enter. In the Command Prompt window, type: ipconfig /all Identify the active network adapter (Ethernet or Wi‑Fi). Locate Physical Address — this is the MAC address. Example Below is a typical  ipconfig /all result with the MAC addresses highlighted. Windows IP Configuration Host Name . . . . . . . . . . . . : WIN10-TEST-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : localdomain Ethernet adapter Ethernet: Connection-specific DNS Suffix . : localdomain Description . . . . . . . . . . . : Intel(R) Ethernet Connection I219-LM Physical Address. . . . . . . . . : 𝟬𝟬-𝟭𝗔-𝟮𝗕-𝟯𝗖-𝟰𝗗-𝟱𝗘 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 192.168.1.25(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, 19 February 2026 3:42:18 PM Lease Expires . . . . . . . . . . : Thursday, 20 February 2026 3:42:19 PM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.10 DNS Servers . . . . . . . . . . . : 192.168.1.10 8.8.8.8 NetBIOS over Tcpip. . . . . . . . : Enabled Wireless LAN adapter Wi-Fi: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 8260 Physical Address. . . . . . . . . : 𝟯𝟰-𝗔𝗕-𝟴𝟵-𝟰𝗙-𝟮𝟮-𝟭𝟭 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Bluetooth Network Connection: Media State . . . . . . . . . . . : Media disconnected Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network) Physical Address. . . . . . . . . : 𝟴𝟴-𝟱𝗔-𝗙𝗘-𝟭𝟭-𝟮𝟮-𝟯𝟯 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes