Issue Currently, a procedure exists to do conversion of i2 to b3 and vice versa using Continuum Cyberstation and NetControllers.   However, it is much simpler to do the conversion using the RoamIO and the Infinet/BACnet Service Tools. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause This article describes an alternate and simplified conversion method to the original procedure published to convert i2 to b3. Before using this procedure, read the Conversion of Continuum devices from i2 to b3 and vice-versa in the field Knowledge Base article in its entirety for important information about converting i2/b3 controllers in the field.  Resolution IMPORTANT NOTE If the device you are converting is of model i2/b3 865/866/885 STOP First confirm that the device is NOT a -V device, this is accomplished by inspecting its version number, -V devices have a "1" embedded in the second part (after the ".") of the version number   A -v device will show the version number as follows... 3.501027 A non -v device will show the version number as follows... 3.500027   Before starting the procedure, you need the following items: The device to be converted. The serial number of the device to be converted. A RoamIO2 configured to communicate with your PC via Bluetooth and the Infinet and BACnet Service Tools A special, firmware application upgrade file for the appropriate device model as provided by Product Support A bootloader file for the appropriate device model, provided by Product Support To convert i2 field devices into b3 BACnet using RoamIO2 Contact Product Support and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (e.g. i2920toB3920B4.500077.upd) and a boot loader file (e.g. B3920BootB4.500077.upd) for each model you are converting. Connect the RoamIO2 directly to the i2 device (make sure device is disconnected from field bus) Launch the InfinetServiceToolPC.exe (attached) and click on the connect icon Once the device shows up on the tree, right click on it then select 'Uprev firmware...' Send the conversion application file provided by Product Support Once the uprev operation is complete, click the connect icon to disconnect the Infinet Service Tool from the i2 device then close the InfinetServiceTool app. Cycle power to the RoamIO2 then start the BACnet Service Tool In the BACnet Service Tool, de-select View by networks, then click the connect icon, the conversion from i2 to a b3 causes the device to default to baud 38400 and an invalid BACnet master MAC id, so upon connection the following error will be shown... Click 'Yes' to continue From the 'Tools' menu select 'Set b3 baud rate' and set it to Baud38400  From the 'Tools' menu select 'Set offline b3 MAC id' and enter the serial number of the device and a valid MAC id then click on 'Apply' If the baud and MAC id have been set successfully, the device will automatically pop up in the tree but it will only be partially online, to bring the device fully online, click the red disconnect icon on the BACnet Service Tool to disconnect from the device, wait about 30 seconds then  click the now green connect icon to reconnect the BACnet Service Tool to the device Right click on the device then select 'Update OS', send it the appropriate boot loader file provided by Product Support Once the uprev of the boot loader has completed, select the device and click on 'Cold start device' After the device re-start, click on the device in the tree and select 'Switch view', confirm the firmware and boot loader versions are correct. (you may need to do a refresh from the 'Tools' menu)

Issue Continuum i2 and b3 field devices use the same hardware. With the exception of their -V models and the bCX (bCX9640/bCX4040) controller, they were not designed to have their firmware swapped from Infinet to BACnet (or BACnet to Infinet) in the field. Product Line Andover Continuum, EcoStruxure Building Operation Environment Continuum i2 Controllers (except -V) Continuum b3 Controller (except -V) Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support for assistance. Cause With the exception of the -V controllers, the devices were not designed to have their protocol (Infinet/BACnet) swapped in the field, however, due to changes in market needs R&D is now providing a method to allow the protocol to be changed in the field. Resolution IMPORTANT NOTES: If a RoamIO2 is available, it can be used to do the conversion without the need to have Continuum Cyberstation and Continuum controllers. https://community.se.com/t5/Building-Automation-Knowledge/Conversion-of-Continuum-devices-from-i2-to-b3-and-vice-versa-in/ta-p/448337    If the device you are converting is of model i2/b3 865/866/885 STOP First confirm that the device is NOT a -V device, this is accomplished by editing the device and inspecting its version number, -V devices have a "1" embedded in the second part (after the ".") of the version number   A non -v device will show the above version number as follow,,, 3.500027   To convert i2 field devices into b3 BACnet (or vice-versa) from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. Follow the procedure detailed below or as per the attached document. To swap the firmware of any non -V i2 device from one protocol to the other (in this case, from Infinet to BACnet b3), you use the following procedure.  For more information, see section 1.3 “Converting Infinet i2 Field Devices to BACnet b3 Devices from CyberStation” below. NOTE: This procedure was developed by Schneider Electric’s R&D and tested in the Product Support Services (PSS) lab.   Before starting the procedure, you need the following items: An I2 device(s) to be converted. A Continuum CyberStation with i2 device(s) configured and online. A special, conversion b3 upgrade file for the appropriate device model as provided by PSS A b3 bootloader file for the appropriate device model, provided by PSS Physical access to the device.  You need this to push its Restart switch or to access the switch or breaker where you can shut off power to the device to force a restart. A bCX4040 controller configured in CyberStation xP Expansion I/O Note If the device to be converted from i2 to b3 has any expansion modules attached, make sure the modules do not exceed the power capacity of the expansion port (180 mA), it has been observed that the b3 devices adhere more strictly to the 180 mA limit than the i2 devices, resulting in loss of operation on IO channels located on the Expansion Port if the power limit is exceeded.  See attached xP Expansion IO Datasheet for information on power consumption of each xP IO module.   1.2 Preparing the Field Bus for the i2 to b3 Device Conversion To ensure a smooth conversion, it is necessary that you reduce the traffic on the field bus as much as possible in order to provide the necessary bandwidth to the upgrade operations required for the conversion. Before starting the process with the conversion file, be sure to follow these instructions.    To prepare the field bus for the i2 to b3 device conversion Disable all the programs in all the devices residing in the field bus. Close all Continuum Workstations except the one performing the upgrade. In the Workstation performing the upgrade, close all graphics, List views, and anything else that could be polling data from the field bus. Make sure MS/TP field bus is on same baud rate as Infinet field bus, mainly 19.2K 1.3 Converting i2 Field Devices into b3 BACnet from CyberStation You can convert Infinet i2 field devices into b3 BACnet field devices by swapping the firmware of any non -V model i2 device. IMPORTANT: When using this procedure, be aware of the following guidelines: It applies ONLY to the firmware or communication protocol (Infinet or BACnet) of the device. It does not convert the control application in the device. Following conversion, the device’s memory is cleared, so you need to configure a new control application. It may result in a loss of critical data if not performed properly. Before beginning, ensure that all important data is backed up in the event of data loss or the device losing its application and becoming non-operational.  For more information, see section 1.1 “Introduction” above. To convert i2 field devices into b3 BACnet from CyberStation Contact PSS and request the conversion files for the specific model(s) you wish to convert. You will be provided with an application file (namely, i2920toB3920B4.500077.upd) and a boot loader file (namely, B3920BootB4.500077.upd). From CyberStation, edit the i2 device and record its Serial Number and Infinet id. Consult the General tab to locate this information. From the Runtime tab, perform a Reset to clear the device’s database. Upgrade the i2 device using the application file provided by PSS. Once the upgrade is complete, the i2 device stays Offline since its communication protocol has now been swapped from Infinet to BACnet. Disconnect the device from the Infinet field bus of its host master controller (for example, a CX9680 or a bCX9640). Connect it to the bCX4040 MS/TP field bus. (MAKE SURE MS/TP FIELD BUS IS RUNNING AT SAME BAUD AS INFINET FIELD BUS DEVICE WAS ON, NAMELY 19.2K BAUD) In the bCX4040, configure a b3 device using the appropriate model as well the Serial Number and ID recorded previously. NOTE: You will need to provide BACnet Device ID. Typically, it will be the same as the Serial Number. You can also use a Learn to bring the device online under the bCX4040 and automatically assign the model, id etc.  Refer to this Knowledge Base article on using the serial number for the Device ID.  Remember here to set the Comm Port for comm2. Restart the device either by power cycling or using the restart button. The device will come online under the bCX4040 as a b3 device. Perform an Update b3 OS operation to send the appropriate b3 boot loader file provided by PSS. Go to the Runtime tab, and reset the device once the update is finished. Once the device reboots and comes back online, you can confirm it has the right boot loader by looking at the device from the BACnet side. The screenshots that follow display the before and after results of the i2 to b3 conversion process. Before: After: NOTE 1 If Continuum system is not available it is also possible to convert i2 to b3 using RoamIO and EBO server using the following steps Disconnect device from field bus and connect RoamIO directly to i2 device. Use InfinetServiceTool to send the application conversion file to the i2 device. After the uprev operation is done disconnect RoamIO and cycle power to the i2 device Connect converted device (now a b3) to MSTP of AS-P or other EBO server that supports BACnet MSTP Perform a b3 learn operation to bring the device online Right click the b3 device and proveed to 'Device->Update firmware...' Navigate to appropriate boot loader file for the b3 model After uprev of boot loader is complete, cycle power to the b3 device. NOTE 2 Similar steps can be used to convert b3 device to i2 device. Make sure to use the V2 version of the b3 to i2 conversion files as it was found the original set of b3 to i2 conversion files did not work in some cases. Please note that once a b3 device has been converted to i2 using this procedure the device will ONLY accept conversion uprev files, attempt to uprev using regular uprev file will result in the following error:   This Uprev file does not match this type of controller. This applies to b3 to i2 conversion only, it does not apply to i2 to b3 conversion.

Issue Can the Continuum OPC Server be configured to run as a service to enable the application to start without a user having to log on to the relevant machine? Product Line Andover Continuum Environment Continuum OPC Server Cause Need to have OPC Server (part number: CTRL-OPC-SRVR) running without requiring a user to logon to Windows to start the application. Resolution The OPC Server can not be run as a service. It can only be run as an application which will require a user to logon to Windows and start the application.  See OPC Server further information on OPC Server.

Issue What effect does it have on a BACnet network if the Network ID – UDP setting on multiple bCX40x0 controllers on the same BACnet/IP network is set to different values? What is the Network ID–UDP setting used for, and does it need to be changed when commissioning a new BACnet Continuum controller? Product Line Andover Continuum Environment Continuum BACnet bCX4040 bCX4000 Cause BACnet/IP controllers were configured with different Network ID – UDP values while residing on the same physical IP network. Lack of understanding of the function of the BACnet Network ID – UDP (BACnet network number for the UDP/IP physical layer). Resolution Description of Network ID – UDP In a BACnet system, each network segment is assigned a unique Network ID to enable correct routing of BACnet messages between networks. The Network ID – UDP setting defines the BACnet/IP (UDP) network number on which a bCX controller resides. When a Continuum BACnet controller is created, the default Network ID – UDP value is 1. This value must be identical on all BACnet/IP devices that are required to communicate with each other on the same IP network. Effect of Mismatched Network ID – UDP Values If bCX controllers are on the same IP network but configured with different Network ID – UDP values: Controllers may still communicate intermittently. Each controller assumes it is on a different BACnet network. BACnet routing tables become inefficient or incorrect. Excessive BACnet traffic may be generated. Overall communication reliability may be reduced. Example – Incorrect Configuration Controllers on the same IP network using different UDP Network IDs: Controller UDP Network ID UDP Comm Port 1 1 2701 2 2 2702 3 3 2703 4 4 2704 5 5 2705 6 6 2706 7 7 2707 Correct Configuration If all bCX controllers are on the same BACnet/IP network, they must be configured with the same Network ID – UDP value (typically the default of 1 ) Controller UDP Network ID UDP Comm Port 1 1 2701 2 1 2702 3 1 2703 4 1 2704 5 1 2705 6 1 2706 7 1 2707 This ensures: Correct BACnet routing Reduced network traffic Reliable communication between controllers When Should the Network ID – UDP Be Changed? The Network ID – UDP should only be changed in specific scenarios, such as: An existing BACnet/IP network already operates on the same Ethernet infrastructure. Isolation of Continuum BACnet traffic from another BACnet/IP system is required. If the Network ID – UDP is changed (for example, from 1 to 2 ) All Continuum BACnet controllers that must communicate with each other must be set to the same new value. Mixed Network ID values on the same IP network are not supported.

Issue After reinstalling Continuum Cyberstation, the Sentinel (security) key is not detected by the system. Product Line  Andover Continuum  Environment Continuum Cyberstation Sentinel Security Key Cause The Sentinel driver may not be installed correctly or may have been blocked during installation, often due to antivirus interference or Windows account restrictions. Resolution Verify antivirus status Ensure antivirus software is disabled during Continuum installation. Reinstall Continuum if antivirus was active during the initial install. Reinstall the Sentinel driver Locate the driver in the Continuum installation media: \Continuum\ISSetupPrerequisites\{1F0227D8-C348-45F0-9789-1DEE3E8C5889}\ Or download the latest drivers from Software Monetization Drivers and Downloads | HASP Drivers Run the executable to reinstall the driver. If the key is still not recognized Download the SSDCleanup utility  Run SSDCleanup to fully remove existing Sentinel drivers. Reboot the PC. Reinstall the driver from: \Continuum\Install\Sentinel\SSDv7_xx.exe Test with multiple Windows accounts Some Windows profiles, even with local admin rights, may have restrictions preventing the driver from accessing the USB key.

Issue Time Synchronization in Cyberstation  Product Line Andover Continuum Environment Multiple Cyberstation workstations Workstations using Windows time services Cause Cyberstation relies on local workstation time to timestamp events and transactions. If workstation clocks are not synchronized, recorded events in the SQL database can appear out of order or duplicated in time. Resolution Cyberstation does not require synchronization to the SQL Server clock. It requires synchronization between Cyberstation workstations themselves. Use one of the following supported methods: 1. Domain‑Based Time Synchronization (Recommended) If workstations are joined to a Windows domain: Windows Time Service (W32Time) automatically syncs each workstation with the domain controller. No additional configuration needed. 2. Sync With a Network Time Server (NTS) If the system is not domain‑joined: Configure Windows to sync time with a trusted NTP server. This can be an internal corporate NTP server or a public time source. Example: time.windows.com or your facility’s NTP appliance. Windows Clock Settings allow configuration via: Date and Time → Internet Time → Change settings 3. Sync With Another Local Workstation If the site has no NTP server: Choose a primary workstation that will act as a reference time source. Point other Cyberstations to synchronize with its static IP using Windows Time Service. 4. Offline Synchronization Options If Internet or NTP access is restricted: Use third‑party USB or PCI clock devices that sync via radio signals (Atomic clock receivers). These devices feed accurate time directly into the workstation. Notes Cyberstation uses workstation system time, not server time, for event timestamps. Ensure each workstation’s time zone and DST settings are correct.

Issue A Continuum or b3 controller fails during a flash firmware upgrade with one of the following messages: Continuum: “This Uprev file does not match this type of controller.” Building Operation: “Update Failure: No b3 controller matches to update.” Product Line Andover Continuum, EcoStruxure Building Operation Environment Andover Continuum Building Operation WorkStation b3 controllers Cause The firmware file does not match the actual hardware model or variant of the controller. Common causes include: Incorrect Controller Model entered in the Device object or the offline database. Incorrect firmware file selected for the controller hardware. Variant mismatch on b3 VAV controllers: Some b3 VAV controllers come in two hardware variants: Standard (non‑V) –V VAV hardware variant Firmware compatibility is encoded in the 4th digit of the firmware version number. Firmware 4th Digit Meaning for b3 Controllers The 4th digit identifies which hardware variant the firmware supports: 0 = Standard (non‑V) version 1 = –V VAV hardware variant Example: 4.500076 → Standard, non‑V 4.501064 → VAV –V hardware variant If the firmware's variant identifier does not match the controller hardware, the upgrade will fail with the errors above. Resolution Check the physical controller label to confirm whether the unit is a standard or –V VAV hardware model. Verify the Controller Model field in the Device object matches the actual hardware model. Check the offline database for consistency if editing in offline mode. Select the firmware file that matches the correct hardware variant based on the 4th digit of the version number. Retry the uprev using the correct firmware.

Issue Users are unable to authenticate to SQL Server using SQL Authentication, including the sa account, after successfully changing the password. Login attempts continue to fail even though the new password is correct. Environment Microsoft SQL Server 2012 to 2022 SQL Server Management Studio (all currently supported versions) Systems where Remember Password was previously enabled in SSMS Cause SSMS may store login credentials in Windows Credential Manager when the Remember Password option is selected. If the password is later changed, SSMS may continue to submit the cached password instead of the manually entered new one. This leads to repeated login failures even when the correct password is typed. Cached credentials can also remain on the workstation, unexpectedly granting access to privileged accounts. Risks of Using Remember Password in SSMS Cached credentials become outdated and override new passwords, causing login issues. Credentials stored on shared or semi‑secure machines may allow unintended access to SQL Server. Users may unknowingly authenticate with privileged accounts such as sa if credentials auto‑fill. Cached entries persist across logoffs, reboots, and profile changes, creating long‑term exposure. Troubleshooting becomes difficult when SSMS silently submits incorrect stored credentials. For these reasons, it is recommended to avoid selecting Remember Password, especially for privileged SQL accounts. Resolution 1. Clear the Remember Password Option in SSMS Open SQL Server Management Studio. On the login screen, uncheck Remember Password. Re-enter the username and new password. Attempt to log in. If login continues to fail, cached credentials in Windows Credential Manager must be removed. 2. Remove Stored SQL Credentials from Windows Credential Manager Step 1 – Open Windows Credential Manager Access it using any of the following: Press Windows key, type Credential Manager, and select it Or navigate through: Control Panel > User Accounts > Credential Manager Step 2 – Locate Stored SQL Credentials Check the following sections: Windows Credentials Generic Credentials Look for stored entries related to your SQL Server, such as: The server hostname SQL instance name MSSQLSvc entries IP addresses used by SQL Server Examples: MSSQLSvc/myserver.domain.local:1433 myserver.domain.local TCP:192.168.X.X Step 3 – Remove Cached Credentials For each related entry: Expand the entry using the arrow. Select Remove. Confirm deletion. Repeat for all SQL-related credentials. Step 4 – Retry Logging Into SSMS Reopen SSMS. Ensure Remember Password is unchecked. Enter the username and new password again. Attempt the login. This forces SSMS to use fresh credentials instead of cached values.

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 After running BACnet device discovery in EcoStruxure Building Operation (EBO) or Andover Continuum, third‑party devices may appear with only a BACnet MAC address shown. The actual IPv4 address and UDP port of the device are unknown and need to be determined. Product Line Andover Continuum, EcoStruxure Building Operation, Field Devices, EcoStruxure Building Expert Environment Building Operation Server (ES, AS-P, AS-B) Continuum CyberStation, BACnet Operator Workstation SmartStruxure Lite Multi‑Purpose Manager (MPM) BACnet networks that include BACnet/IP, BACnet MS/TP, and BACnet/SC Cause In EBO and Continuum, a BACnet device is identified by a Network Number and a MAC address, but the meaning of the MAC address depends on the data link. BACnet/IP: MAC is the concatenation of IPv4 address (4 bytes) and UDP port (2 bytes) in hex. BACnet MS/TP: MAC is a single numeric address (0 to 127 for masters, 0 to 254 for slaves). BACnet/SC: Uses a 6‑octet Virtual MAC (VMAC) in EUI‑48 form that is randomly generated. It is not an IP and cannot be decoded to an IP address. In SmartStruxure Lite MPM contexts, the displayed “Device MAC” may encode Network Number and Device ID in hex, which is different from BACnet/IP MAC and does not contain an IP or port. Resolution A. Decode BACnet/IP MAC to IPv4 and Port (EBO and Continuum) Open the device properties in EBO or Continuum and locate the BACnet MAC address (hex string, often 12 hex characters if no delimiters). Split the MAC into 6 bytes: first 4 bytes are the IP, last 2 bytes are the UDP port. Convert each IP byte from hex to decimal to form the IPv4 address. Convert the last 2 bytes from hex to decimal to get the UDP port. Default BACnet/IP port is 0xBAC0 = 47808 unless configured otherwise. Example: 0A9F1ACFBAC0 → 0A 9F 1A CF and BA C0 IP = 0A 9F 1A CF → 10.159.26.207 Port = BA C0 → 47808 Excel helper formulas If the MAC is a contiguous hex string in A1 (no spaces or colons): =HEX2DEC(LEFT(A1,2))&"."&HEX2DEC(MID(A1,3,2))&"."&HEX2DEC(MID(A1,5,2))&"."&HEX2DEC(MID(A1,7,2))&":"&HEX2DEC(RIGHT(A1,LEN(A1)-8)) Zero‑padded version for sorting: =TEXT(HEX2DEC(LEFT(A1,2)),"000")&"."&TEXT(HEX2DEC(MID(A1,3,2)),"000")&"."&TEXT(HEX2DEC(MID(A1,5,2)),"000")&"."&TEXT(HEX2DEC(MID(A1,7,2)),"000")&":"&TEXT(HEX2DEC(RIGHT(A1,LEN(A1)-8)),"00000") If the MAC includes delimiters (for example C0:A8:01:05:BA:C0 or C0 A8 01 05 BA C0 ), normalize first and reference the cleaned cell: =SUBSTITUTE(SUBSTITUTE(UPPER(A1),":","")," ","")​ Use the result of the above as the input to the decode formulas. B. Interpret MAC on BACnet MS/TP MAC is a single numeric node address. Range: 0 to 127 for masters, 0 to 254 for slaves. There is no IP to derive. Use the MS/TP address and the network number for routing or troubleshooting. C. Understand BACnet/SC VMAC BACnet/SC devices use a random EUI‑48 VMAC to identify nodes on the Secure Connect topology. VMAC is not an IP and cannot be converted to an IP address. IP details are determined by the SC hubs and transport layer. D. SmartStruxure Lite MPM “Device MAC” format In MPM contexts, the “Device MAC” may be shown as: [ yy xx bb aa 00 00 ] yy xx = Network Number in hex (high‑byte first) bb aa = Device ID in hex (high‑byte first) 00 00 = padding Example: 7B 00 67 00 00 00 Network Number = 0x7B00 = 123 Device ID = 0x6700 = 103 This format does not encode an IP address or UDP port. E. Validation tips After decoding, verify by pinging the IP or using a BACnet browser to read the device object over BACnet/IP at the derived port. If communication still fails, confirm whether the device is actually BACnet/IP versus MS/TP or BACnet/SC, and check for custom port settings.

Issue Users need access to the BACnet Protocol Implementation Conformance Statements (PICS) for Schneider Electric BACnet controllers. Product Line Andover Continuum, EcoStruxure Building Operation, TAC IA Series Environment All Schneider Electric BACnet controllers Cause Customers and support personnel may be unsure where to obtain the official BACnet PICS documents for Schneider Electric devices. Resolution BACnet Protocol Implementation Conformance Statements (PICS) for Schneider Electric controllers are available on the BACnet International website. Use the site’s device listing or certification database to locate PICS files associated with specific Schneider Electric BACnet products.

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 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 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 Guidance is required for configuring and using the encrypted LON Tunnel Client in WorkPlace Tech 5.10.4 and later when connecting to a Jace N4. Users may experience workflow changes or tunneling errors after upgrading. Product Line TAC IA Series Environment WorkPlace Tech 5.10.4 and later Click for WorkPlace Tech 5.9.4 information I/A Series N4 Jace Cause Newer versions of WorkPlace Tech introduce changes to LON tunnel connectivity, including updated encrypted communication handling and modified workflows for multi‑network tunneling. These changes may alter how users connect and how tunneling errors appear. Resolution The included video demonstrates: How to enable and apply encrypted LON tunneling on a Jace N4 Configuration of the Tunnel Client in WorkPlace Tech 5.10.4 and later Support for tunneling to multiple LON networks on a single Jace Key workflow differences compared to earlier releases Common tunneling error behaviors and how to recognize them Refer to the video for detailed configuration and troubleshooting guidance  

Issue Users expect to configure I/A Series MNB‑1000 controllers or other third party BACnet devices directly through Cyberstation, but the devices do not expose setup parameters or cannot be configured from Cyberstation. Product Line TAC IA Series, Andover Continuum Environment Cyberstation BACnet networks I/A Series MNB‑1000 controllers Cause Cyberstation provides BACnet interoperability but does not support device level configuration for third party BACnet devices. Most BACnet field devices require a vendor specific configuration tool or onboard display for initial setup. The MNB‑1000 specifically requires I/A Series configuration software before Cyberstation can interact with it. Resolution Cyberstation cannot perform base configuration of third party BACnet devices. Use the manufacturer’s configuration, commissioning, or keypad interface. For I/A Series MNB‑1000 controllers, perform device setup using the I/A Series configuration tools. After the MNB‑1000 is fully configured and online, Cyberstation can read, write, and adjust points based on the device’s PIC statement.

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 Understanding how to decode BACnet error values found in EBO Trace/System Logs, Controllers, and Continuum devices when documentation for the error message is not readily available. Product Line EcoStruxure Building Operation, Andover Continuum, TAC IA Series Environment EBO Error Log Tool Continuum bCX4040 (BACnet) Continuum b3s Building Operation Multi-purpose Controller (MPC/V) Building Operation Room Controller (RPC/V) Building Operation IP-IO EBO Trace and System logs Cause BACnet error messages in logs use a combined 32‑bit value that includes: BACnetErrorClass (BEC) in the high 16 bits BACnetErrorCode (BE) in the low 16 bits Values often appear with 0x800 prefix indicating hexadecimal formatting. Without decoding, the error meaning is unclear. Example: 0x8001001F 0x10000 → Error Class = Object 0x001F → Error Code = Unknown Object Resolution Understanding the Error Structure A BACnet error value is formed as: 0x8 0 0 [ErrorClassHex] [ErrorCodeHex] High 16 bits Low 16 bits Remove the 0x800 prefix, if present. Convert high 16 bits to identify Error Class. Convert low 16 bits to identify Error Code. Common Interpretation Example Error: 0x8001001F Error Class: 1 → Object Error Code: 1F (31 decimal) → Unknown Object Meaning: Device does not recognize the object. Possible reasons include: Expected program/database not loaded Object deleted or missing b3 device memory wiped after power failure Error Classes (High 16 Bits) (From BACnet Specification Clause 18) May not include 0x8000. (Example: could be 0x5002B instead of 0x8005002B for COV subscription failed) Error Class Hex(0x800) Dec Notes device 0 0   object 1 1   property 2 2   resources 3 3   security 4 4   services 5 5   vt 6 6   proprietary     64 is the first available code for proprietary error classes client 7FFD   0x7FFD0000 Reject 7FFE   0x7FFE0000 (error code is BACnetReject) Abort 7FFF   0x7FFF0000 (error code is BACnetAbort)   Error Codes (Low 16 Bits) A subset of codes from BACnet Clause 18: Error Code Hex (0x) Dec other 0 0 authentication_failed 1 1 configuration_in_progress 2 2 device_busy 3 3 dynamic_creation_not_supported 4 4 file_access_denied 5 5 incompatible_security_levels 6 6 inconsistent_parameters 7 7 inconsistent_selection_criterion 8 8 invalid_data_type 9 9 invalid_file_access_method A 10 invalid_file_start_position B 11 invalid_operator_name C 12 invalid_parameter_data_type D 13 invalid_time_stamp E 14 key_generation_error F 15 missing_required_parameter 10 16 no_objects_of_specified_type 11 17 no_space_for_object 12 18 no_space_to_add_list_element 13 19 no_space_to_write_property 14 20 no_vt_sessions_available 15 21 property_is_not_a_list 16 22 object_deletion_not_permitted 17 23 object_identifier_already_exists 18 24 operational_problem 19 25 password_failure 1A 26 read_access_denied 1B 27 security_not_supported 1C 28 service_request_denied 1D 29 timeout 1E 30 unknown_object 1F 31 unknown_property 20 32 removed 21 33 unknown_vt_class 22 34 unknown_vt_session 23 35 unsupported_object_type 24 36 value_out_of_range 25 37 vt_session_already_closed 26 38 vt_session_termination_failure 27 39 write_access_denied 28 40 character_set_not_supported 29 41 invalid_array_index 2A 42 cov_subscription_failed 2B 43 not_cov_property 2C 44 optional_functionality_not_supported 2D 45 invalid_configuration_data 2E 46 datatype_not_supported 2F 47 duplicate_name 30 48 duplicate_object_id 31 49 property_is_not_an_array 32 50   Frequently Encountered Errors Hex Value Decoded Meaning Notes 0x8000001E Device + timeout Device offline or non‑responsive 0x8001001F Object + unknown object b3/AS memory wipe, missing database 0x80020020 Property + unknown property Invalid property reference 0x80020025 Property + value out of range Writing 0 to multi‑state object 0x80020028 Property + write access denied Permission issue 0x8002002C Property + not COV property Subscription attempted on non‑COV property 0x8002002E Property + invalid configuration data Often caused by invalid COV alarm config 0x80030000 Resources + out of memory Device resource exhaustion 0x80050007 Services + inconsistent parameters Parameter mismatch 0x80050019 Services + operational problem General service failure 0x8005001D Services + service request denied Device rejected request 0x8005002B / 0x5002B Services + COV subscription failed May appear without 0x800 prefix Wireshark Tip Use the filter: bacapp.type == 5 This displays APDU error packets with decoded Class and Error fields in decimal. In this example, the BACnet device returns an error for Device (0) and operational problem (25) when responding to a readPropertyMultiple.

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.