How To Find ADSBExchange Feed UID On Windows Systems

Locating your ADSBExchange Feed Unique Identifier (UID) on a Windows-based feeder installation requires accessing the local web interface or inspecting the specific configuration file generated by the feeder service. This 32-character hexadecimal string is essential for linking your hardware data stream to your personal account on the ADSBExchange portal, ensuring your site statistics and aircraft tracking data are correctly attributed to your contributor profile.

Pre-Operation Requirements and Environment Preparation

Before attempting to retrieve your Feed UID, ensure your Windows host is actively running a data feeder service, such as the standard ADSBExchange feeder client or a compatible dump1090-fa fork configured for Windows via WSL or native binary executables. The UID is not merely a local setting but a persistent token generated during the initial handshake between your local receiver software and the ADSBExchange central servers.

• Essential Software Requirements:
• Access to a modern web browser (Chrome, Firefox, or Edge) with local network connectivity to the feeder machine.
• A functional dump1090 or readsb instance configured to pipe data to the ADSBExchange feed client.
• Administrative privileges on the Windows machine to access hidden configuration directories or system logs.
• Stable internet connection to ensure the feeder has successfully completed its initial registration and heartbeat transmission.
• Estimated time to locate: Under 5 minutes for experienced users; 10 minutes if log inspection is required.

Systematic Identification of the ADSBExchange Feed UID

Step 1: Navigating the Local Web Interface

The most reliable method to retrieve your UID involves querying the local status page generated by your feeder software. If your feeder is configured correctly, it maintains a web interface that displays the health of the connection and, often, the unique identity credentials assigned to the node. Open your web browser and navigate to the IP address of your feeder machine followed by the standard port, usually port 8080 or 8754. Look for a section titled Statistics, Connection Status, or Configuration. If the page displays your UID, copy it immediately and store it in a secure location.

Pro-Tip: If you are running multiple feeders on your network, use an IP scanner tool to ensure you are accessing the specific machine hosting the ADSBExchange client, as multiple instances can lead to conflicting data reports.

Step 2: Extracting the UID from Configuration Files

If the web interface does not explicitly list the UID, you must inspect the configuration file generated by the installer. On Windows installations, these are typically stored in the directory where the feeder binary resides or within the system’s AppData folder. Search for a file typically named adsbexchange.conf or similar, often located in the main feeder installation folder. Open this file using a plain text editor like Notepad or Notepad++. Inside the text, look for a variable labeled FEEDER_UID or simply UID. This string represents the hardware-locked ID associated with your specific installation.

Step 3: Inspecting System Logs for Initialization Data

If the configuration file is empty or missing the UID entry, the data may be trapped in the system log files created during the startup of the feeder service. Navigate to the log directory, which is usually located within the same folder structure as your executable binary. Open the latest log file—often labeled with the current date or as service.log—and search for the term UUID or Unique ID. During the initial startup phase, the feeder will log the registration process with the ADSBExchange servers. Once the handshake is complete, the log will display the successfully registered UID.

Warning: Never share your Feed UID in public forums or with third-party tracking applications, as this key allows others to claim your data contribution as their own, effectively hijacking your account’s site history and statistics.

Technical Configuration Parameters and Comparison

The following table outlines the common locations and methods for verifying your ADSBExchange data status and identifying the underlying credentials associated with your contribution hardware.

Common Failure Scenarios and Resolution Procedures

When the UID is not immediately apparent, it is usually due to a lack of proper initialization or a failure in the communication layer between the local feeder and the central server.

• Feeder Failing to Register:
  
  
  • Root Cause: Your local firewall is blocking outgoing traffic on the ports required for the ADSBExchange handshake.
  • Actionable Fix: Ensure that the feeder application is whitelisted in Windows Defender and that no tertiary antivirus software is intercepting the outbound TCP/UDP stream to the feed ingestion servers.
• Configuration File Missing or Corrupt:
  
  
  • Root Cause: The initial installation process failed to complete, or the feeder was forced to close during the registration handshake.
  • Actionable Fix: Delete the existing configuration file and perform a clean restart of the feeder service to force the application to re-run the registration script and generate a new, valid UID.
• UID Discrepancies Across Platforms:
  
  
  • Root Cause: Running multiple instances of feeder software on the same network using the same local configuration files.
  • Actionable Fix: Assign a unique hardware identifier to each feeder instance and ensure that each node maintains its own independent configuration file within its respective installation directory.

Frequently Asked Questions

Can I find my UID if my feeder is currently offline?

Yes, the UID is stored locally in your configuration file even if the feeder is not actively transmitting. You can retrieve it by manually opening the configuration file in a text editor, provided the initial installation and registration were successful before the service went offline.

What should I do if my UID does not show up on my ADSBExchange account page?

This often indicates that your local feeder is not successfully authenticating with the servers. Verify your network settings, check for blocked ports, and ensure that your feeder software is the most current version, as older versions may use deprecated authentication protocols.

Is the Feed UID the same as the receiver serial number?

No, the Feed UID is a server-side generated string assigned to your software installation instance, whereas the serial number is a hardware-specific identifier for your SDR dongle. Do not confuse these two, as they serve entirely different purposes in the tracking ecosystem.

Is it safe to move the Feed UID to a new Windows machine?

You can migrate the UID to a new installation by copying the configuration file, but you must ensure the original machine is permanently decommissioned. Operating two instances with the exact same UID will cause erratic data reporting and potential suspension of your feeder account for duplicate stream interference.

Optimize Your Flight Tracking Precision

Ensuring your ADSBExchange feed is correctly mapped with the proper UID is the first step toward high-fidelity participation in the global aircraft tracking community. Monitor your performance metrics regularly on the contributor dashboard to verify that your hardware is delivering consistent, high-quality signal data.