During the development process of the MC149.01 GNSS receiver, we’ve got a delegation from the company making a reference station network. Their job is to make a Hydrogen Master clock-based station with three receivers inside. For one of their receivers they chose some of the Javad lineups, other two are vacant. Therefore, they came to us to test our device and, if all is good, include it in their master-device.
Every GNSS engineer has heard of the RTKLib. It’s an open source toolkit for real-time and post-processing of the raw GNSS data. The availability of such a toolkit is somewhat of a revolution: it allowed small companies to step into the high-precision navigation market without the need for spending a lot of time and money on R&D tasks. There are, however, some limitations and drawbacks:
One of the main reasons to choose C++ over any other programming language is performance. Eventually, this is what we’re being paid for. There are several cases when we have to write multi-platform:
I’ve got a confession to make: I love standalone applications. Nothing buggers me more than getting a “DLL missing” error from an executable you’ve got from somewhere. Another problem is when an application requires some external data. Sometimes those files should be placed in relative directories alongside the executable, in the most disturbing case the paths are hardcoded.
Earlier this week we’ve had a nice chat with my colleague about an interesting task, which I’ve found quite entertaining and, most important, a nice interview topic.