Point One Navigation, a member of the ST Partner Program, will showcase an updated version of its demo at the AutoSens tradeshow, opening on June 9 in Detroit. Building on what the company showed at CES 2026 last January, Point One Navigation will present a precise positioning system with real-time kinetic and inertial engines fully integrated into the ST demo car. The Point One Navigation TeseoVI-based solution runs in the vehicle in real time. Let us explore how Point One Navigation arrived at this point, how it began using ST technologies, and the lessons the company learned along the way.
How it started?
Learning to ship fast
Interestingly, Point One Navigation shared that they started their ST journey years ago with TeseoV modules featuring an STM32H7 MCU and ST inertial sensors. It allowed them to work on their positioning engine, learn how to use our GNSS receiver, and collaborate with partners who would integrate these modules into their designs. Put simply, it was about shipping a solution that would work for established leaders. Too often, teams get bogged down trying to do too much, too quickly, and too early. By working with modules with ST devices, Point One Navigation gained the expertise it needed to grow strategically and meaningfully.
Mastering feature development
By working on real-time kinematics and dead reckoning on a TeseoV and an STM32H7, Point One Navigation learned to use the ST platform more effectively. For instance, it understood the importance of running its application in a tightly coupled solution, but also that it had limits around the amount of information it could process at once. Real-time kinematic uses GNSS signals and local data points to provide precise location estimates. However, that requires the ability to process more data than a traditional GNSS positioning system and to compute these data points in real time. Similarly, the dead reckoning system relies on sensor data to fill in for incomplete or absent satellite information.
Evolving from module to bespoke solutions
Emboldened by this experience, Point One Navigation decided its solution would benefit greatly from the quad-band capability of the TeseoVI and could be further optimized by working at the chip level rather than the module level. Put simply, the demo shown at CES 2026 of their Atlas Duo standalone reference system stood on the shoulders of years of experience with previous ST devices and solved the limitations encountered previously. That’s why the company was able to obtain results previously available only on systems that cost multiple times more and offer unique features, such as the ability for RTK and inertial engines to talk to each other.
How’s it going?
Learning to fail early
One lesson Point One Navigation learned as they evolved from TeseoV modules to bespoke TeseoVI systems is the importance of failing early. Indeed, the company was successful because it rapidly discovered what worked and what didn’t, allowing it to offer solutions for modules and then unique features in its Atlas Duo application. Similarly, its engineers recommend that customers quickly identify the edge cases that could prevent them from obtaining accurate positioning data. Will a truck drive through an area with little to no coverage? Will assets use containers that could block signals? By failing early, and learning from it, engineers can ship a more robust solution in the long term.
Understanding what customers are not saying
Another lesson Point One Navigation shared with the ST Blog is its ability to understand its customers’ needs, especially what they are not saying out loud. For instance, one client was using a positioning system sold by a competitor with very mixed results. Point One Navigation realized that the system had been built for cars but was used on a drone that required altitude information. By shipping early and building strong expertise with ST devices, Point One Navigation not only came up with Atlas Duo but also developed a way to fully understand what their customers really needed, rather than relying on haphazard assumptions.
Creating object lessons
Finally, a third lesson is that proof of concepts are object lessons. Point One Navigation shared that, by using a TeseoVI, an ST MPU or MCU, and ST sensors, the proof-of-concept serves to educate the customer rather than being a disposable design. In fact, the company explained that most of the time, its teams simply get a development kit from ST, attach it to a Raspberry Pi, and send the whole thing to a customer who only needs to run a few lines of code to see what it can do. The proof of concept thus becomes a tool for managing expectations and teaching customers to understand what they truly need.