How To Find Your ADS-B Exchange Feed UID On Windows Systems
Locating your ADS-B Exchange feed unique identifier (UID) on a Windows-based feeder system is a critical administrative task for maintaining data continuity and verifying your feeder’s status within the global network. By accessing the localized feed configuration file or the feeder’s internal web interface, you can retrieve your specific hexadecimal identifier to ensure accurate reporting and device synchronization with the ADS-B Exchange data aggregator.
Prerequisites and Local Environment Preparation
Before attempting to retrieve your feed UID, ensure your local environment is configured for ADS-B data ingestion. Most Windows-based feeders run via virtualization (such as a Linux subsystem or a VirtualBox VM) or through specific Windows-native binaries like RTL1090 or modesmixer2. Understanding the architecture of your current installation is vital, as the UID is either stored in a configuration file within your virtualized environment or embedded in the startup parameters of your command-line interface.
- Hardware Requirements: An RTL-SDR dongle, antenna, and a stable USB connection to your Windows host machine.
- Software Requirements: A functional installation of your chosen feeder software (e.g., ADSBExchange Custom Image, dump1090-fa, or readsb).
- Access Level: Administrator privileges on the host Windows machine to modify or view configuration files.
- Network Standards: Static IP assignment for your feeder device is highly recommended to prevent UID handshake failures during router reboots.
- Estimated Duration: 10 to 15 minutes of manual verification.
Procedural Workflow for UID Retrieval
Step 1: Identifying the Feeder Runtime Environment
The first step in finding your UID is determining whether your feed is running natively or through a container. If you are using the official ADS-B Exchange script via Windows Subsystem for Linux (WSL), the UID is typically stored in a hidden configuration file located in the user directory. Open your terminal interface and confirm that your feeder process is currently active. If the process is inactive, the UID may be temporarily unavailable until the service initializes, as some modern feeder scripts generate the UID upon the initial handshake with the ADS-B Exchange registration server.
Step 2: Accessing Configuration Files via the Command Interface
Navigate to the directory where your ADS-B feeder software is installed. If you are using the standard installation path, this is often found within your user folder or the specific drive root directory. Look for a file named adsbexchange-feed.conf or a similar variation containing the term settings. You can open these files using standard text editing applications like Notepad or specialized text editors like Notepad++ to avoid formatting corruption. Scan the file for the field labeled feeder_uid or uuid.
Pro-Tip: Do not confuse your latitude and longitude coordinates with the UID string. The UID is an alphanumeric sequence, typically 16 to 32 characters in length, while coordinates are numerical decimals.
Step 3: Utilizing the Local Web Interface
If you cannot locate a physical configuration file, the most reliable method is to access the feeder’s internal dashboard via a web browser. Most modern feeders broadcast a local web interface on port 8080 or port 80. Enter your machine's local IP address followed by the port number into your browser. Once the dashboard loads, navigate to the Settings or Status tab. The UID is often displayed prominently under the Feeder Status or Connection Details section. This interface acts as the primary source of truth for the data currently being transmitted to the ADS-B Exchange servers.
Step 4: Verifying the UID Against the Server Registration
Once you have retrieved the string, verify it by cross-referencing it with the registration email you received when you first set up your feed. If you have lost this information, you can use the ADS-B Exchange My Feed page to verify which UID is currently associated with your registered receiver location. Input the string into the verification field provided on the portal to confirm that your feeder is successfully pushing data to the correct profile.
How to Disable the News Feed in Widgets of Windows 11 (Easy Steps)
Technical Parameters and Configuration Comparisons
The following table summarizes the different methods for identifying your feeder details based on the software environment you have deployed on your Windows machine.
| Method | Access Point | Ease of Use | Reliability |
|---|---|---|---|
| Configuration File | /etc/adsbexchange/ or root folder | Moderate | High |
| Web Dashboard | Localhost:8080 | High | Very High |
| Command Prompt | Status logs or startup flags | Low | Moderate |
| Registration Portal | ADS-B Exchange website | Moderate | Absolute |
Common Troubleshooting for Feed UID Identification
Even with the correct steps, you may encounter obstacles during the retrieval process. Addressing these quickly ensures your station maintains its uptime and data contribution metrics.
- Root Cause: File Permission Restrictions: If you are unable to view the configuration file in your Windows folder, it is likely due to the file being flagged as a system-protected item.
- Actionable Fix: Right-click the file, select Properties, and ensure that your user account has Read permissions. If using WSL, ensure you are running the terminal as an Administrator to bypass permission blocks.
- Root Cause: Web Interface Not Responding: If you cannot connect to the feeder dashboard, the internal web server service may have crashed.
- Actionable Fix: Restart your feeder service via the Windows Services manager or by restarting your virtual machine/WSL instance. Once the service reboots, wait three minutes before attempting to refresh the web interface.
- Root Cause: UID Mismatch/Reset: A software update might have forced a reset of the feeder configuration, resulting in a new UID.
- Actionable Fix: Check your logs for an "Auth failure" or "Invalid UID" warning. If this occurs, you must update your ADS-B Exchange account profile with the new UID generated in your local config file.
Frequently Asked Questions
Is the UID the same as my RTL-SDR serial number?
No, the UID is a unique identifier generated by the ADS-B Exchange software to associate your specific data feed with your account. Your RTL-SDR serial number is a hardware identifier used by Windows to manage the USB device driver, which is entirely separate from your network feeder identity.
Can I change my UID manually?
While you can edit the UID string in your local configuration file, doing so will disconnect your feed from the ADS-B Exchange server, as the server expects the previously registered UID. Only change the UID if you are setting up a new station or have been instructed to do so by technical support.
Does the UID change if I move my antenna?
No, the UID is tied to the software instance and your user account, not the physical location of your hardware. You can move your antenna or change your altitude settings without affecting your UID, provided the software remains installed and the configuration file is preserved.
What should I do if my UID is publicly exposed?
The UID is used to authenticate your feed, but it is not a high-security credential. However, to prevent others from hijacking your feed statistics, keep your UID private. If you believe it has been compromised, you can generate a new UID by deleting the current configuration file and re-running the setup script.
Secure Your Data Feeder Connectivity
Maintaining an accurate UID configuration is essential for maximizing your station's uptime and contributing high-quality data to the global aviation community. Regularly audit your configuration settings to ensure your feeder remains synchronized with ADS-B Exchange and provides reliable tracking coverage in your region.
