Check the whole setup.
Support depends on the receiver, firmware, connection mode, bridge, power supply and intended workload—not a board name alone.
GNSS receiver profiles
MGW200 and MGW310 are established profiles for the licensed GeoBridge OS receiver integrations. USB and AP are distinct acquisition paths with a shared correction-data pipeline.
CE uses its own supported receiver and installation profiles. Confirm the receiver interface and firmware before choosing an image or starting migration.
Raspberry Pi bridge
GeoBridge uses a separate Raspberry Pi as the bridge. Pi 4 and Zero 2 W have tested reference deployments. Other board and OS combinations must be checked against the current image and installation requirements.
A 512 MB board does not have the same workload capacity as a larger Pi. Low-memory safeguards do not make every optional service suitable for every board. Use appropriate power, storage and data-capable USB cables.
Radio modules need radio hardware
Wingbits requires compatible ADS-B reception hardware. MastChain requires a compatible AIS receiver. Helium IoT requires supported LoRaWAN radio hardware. Antennas, regional requirements and provider onboarding are separate considerations.
Optional modules are separate workloads. Installing software alone does not make unsupported hardware compatible or guarantee provider validation or rewards.
Before deploying remotely
Complete setup and verify fresh correction data and destination delivery before moving the station to its final location. Retain an independent recovery route for changes that could affect remote access.
Contact GeoBridge with board model, receiver model, connection mode and intended networks. Do not include passwords, private keys or full license codes.