Setup Journey: From Unboxing to Evaluation
This page is the starting point for LEO100 setup. Follow it from top to bottom to go from an unopened box to a working evaluation of LEO100 outputs against your target application.
The process is organized into six phases. Phases 1 through 3 follow a fixed sequence. Phase 4 is organized as a decision-driven menu. Phase 5 depends on your deployment. Phase 6 focuses on selecting a production path. Relevant pages from the PpRx reference manual are linked throughout.
Phase 1. Understand the data path
Goal: before plugging anything in, build a mental model of how a GNSS signal becomes a position fix on your host computer.
Knowing the four-stage flow (antenna, RF front end, PpRx, your application) is what makes every later choice obvious instead of arbitrary. Which output to enable, where to put middleware, what to record for debugging: all become easier when the flow is clear.
You're done with Phase 1 when: you can sketch the four stages and name which LEO100 component owns each one.
Go to Information Flow Overview →Phase 2. Install the software
Goal: get PpRx and the Locus Lock GUI running on your host machine.
PpRx also requires a valid license to run. See License Management for checking out a license and understanding Customer ID vs. License ID.
You're done with Phase 2 when: pprx --version returns a real version string and the Locus Lock GUI launches.
Phase 3. Beginner Tutorials
Goal: verify the hardware, capture your first RF dataset, configure PpRx, and produce a position fix on both recorded and live data.
This is a fixed, linear sequence of four short tutorials meant to be completed in order. By the end, LEO100 stops being a box of components and becomes a working receiver on your bench.
You're done with Phase 3 when: PpRx reports a position fix on both your post-processed .bin and a live RadioLion stream.
Phase 4. Advanced Tutorials
Goal: evaluate LEO100 against the specific requirements of your deployment.
This phase is a menu, not a sequence: pick the tutorials that match your platform and skip the rest, building toward a recorded or simulated RF input flowing through PpRx into a stub of your target application.
You're done with Phase 4 when: a recorded or simulated RF input flows through PpRx and is consumed by a stub of your target application.
Go to Advanced Tutorials →Phase 5. Prototype on the real platform
Goal: move from the bench to a non-production version of your actual platform, in conditions that closely represent real operation.
This phase typically includes:
- Moving from bench evaluation to platform-level integration
- Designing interfaces and building middleware between LEO100 outputs and the target application
- Evaluating receiver performance on production hardware (RF and/or host computer)
- High-fidelity field tests in representative or challenging conditions
During this phase the PpRx reference tab becomes your primary working document. The pages you'll lean on most:
- PpRx Intro. Top of the reference section if you want to browse the full set.
- PpRx Tuning Tips. The actual knobs that move receiver performance on a real platform. This is where most of your iteration time will go.
- PpRx Display. Diagnostic readout reference, for interpreting what's happening in long field runs.
- GBX Protocol Description and GenericType Mapping. Required when middleware needs to parse PpRx output streams.
- PpRx as NTP Server. For platforms that need the host clock disciplined to GNSS time.
You're done with Phase 5 when: LEO100 runs end-to-end on your real platform hardware, in representative conditions, meeting your performance bar.
Phase 6. Choose a production path
Goal: decide how LEO100 will ship in production. Most deployments fall into one of two paths:
- Standard deployment. Use LEO100 largely off the shelf, with minor modifications or support as needed.
- Custom deployment. Engage Locus Lock to adapt and integrate PpRx for your specific platform requirements. This may include deploying PpRx on custom RF hardware, host processors, operating systems, middleware stacks, or application architectures, as well as implementing custom receiver features or interfaces.
This phase usually involves closer coordination with Locus Lock engineering to optimize the solution for your final target platform and use case. Depending on your requirements, the resulting deployment may use the complete LEO100 platform or PpRx integrated directly into your existing hardware and software ecosystem.
You're done with Phase 6 when: a production deployment path is selected and the corresponding engineering work is scoped.
After the journey
At this point, you’ve completed the evaluation and deployment planning process. The references you'll keep coming back to are all reachable from the PpRx tab in the top bar:
- PpRx Intro, Tuning Tips, Display, GBX Protocol, GenericType Mapping, NTP Server. The long-lived reference manual.
- Release Notes. Check before updating or testing new features.
- Update Software. Keeping PpRx and the GUI current.
- License Management. Checking out and verifying a PpRx license.
- FAQs and Troubleshooting. Common questions and fixes.
- Glossary. Plain-language definitions for every acronym and term used in these docs.