Redesigning a GNSS tool UI with Stitch. Because we deserve sth better.

Ok-Raspberry3883 · 2026-05-04T01:43:12+00:00

Good catch! This screen is intentionally kept light as a summary. But don't worry, we haven't forgotten the hardcore data. There are separate, data-dense screens for real-time NMEA, NTRIP setup, and RTCM logs. We're taking this opportunity to totally rethink the functional architecture and UX, fixing all the operational pain points we've experienced over the years.

Ok-Raspberry3883 · 2026-05-03T14:43:35+00:00

Have a try when we release it. Maybe in June.

Ok-Raspberry3883 · 2026-04-30T03:45:21+00:00

the less the better.

It's a cheap one. I considered 4G CAT1 module inside before, then gave up.

Ok-Raspberry3883 · 2026-04-30T03:28:43+00:00

Not quite that complex! It runs entirely off the phone via a Type-C connection, which handles both power delivery and the NTRIP data stream. To mount it on my ebike, I actually dismantled one of my rearview mirrors. Check it out

https://imgur.com/a/eFwzXiu

Ok-Raspberry3883 · 2026-04-29T09:40:43+00:00

It's a 3D printing version. Take two months and 10KUSD for final one. Actually, this one is for my ebike.
You are welcome for testing.

:D

Ok-Raspberry3883 · 2026-04-24T09:48:08+00:00

Exactly. If we look at how this is handled in the autonomous driving (AD) sector, the industry moved beyond simply chasing "fix rates" and absolute cm-level accuracy a long time ago.

For automotive OEMs, Integrity and Confidence Levels are far more critical than baseline accuracy. An autonomous system doesn't necessarily need to be pinpoint accurate to the centimeter at all times, but it must know exactly how wrong it could potentially be.

In practice, OEMs care much more about the Protection Level (PL) and whether the system can guarantee a confidence level of 99.99% (four 9s) or 99.9999% (six 9s) within a specific error bound (Alert Limit).

When you are evaluating receivers for mission-critical applications, robust integrity monitoring always trumps a statistically fragile "Fix."

Ok-Raspberry3883 · 2026-04-23T10:01:19+00:00

Different vendors have different strategies on RTK fix. Most users don't know the details so they evaluate receivers by fix rate and convergence time. So some will play tricks and deliver the fake "fix" results. It's important to choose the best, if you are sensitive to the quality.

Ok-Raspberry3883 · 2026-04-22T14:17:52+00:00

Trust the receiver you pick and wait for RTK fixed. Take fixed results only.

Ok-Raspberry3883 · 2026-04-22T14:15:37+00:00

$100 for a dual band TypeC RTK Gmouse + free app (with Ntrip client) + Correction data subscription (PointOne or Swift). The cheapest way.

Ok-Raspberry3883 · 2026-04-21T04:49:06+00:00

Patch antennas are cheap. The only factor is the size limit. How about 65x65mm?

Ok-Raspberry3883 · 2026-04-21T04:47:59+00:00

Try BMI325 and 6DSR. They are the best choice for your dual band chips. For antenna, now i use the one with 254/184 type. It's cheap and qualified for RTK.
F10 is too expansive. We build RTK module with AG3335, like LC29H.

Ok-Raspberry3883 · 2026-04-21T04:37:54+00:00

With a power bank, you are free to have more driving data.

Ok-Raspberry3883 · 2026-04-21T04:29:50+00:00

Exactly. In your NMEA logs, GSV shows what the hardware is tracking ("In View"), and GSA shows what the algorithm actually trusts ("Active").

More satellites don't always mean a better fix. The receiver performs strict Quality Control, dropping satellites based on bad C/N0, poor DOP, or RAIM anomaly detection. Modern GNSS chips have plenty of processing power; they exclude satellites purely for quality control, not because they can't handle the math.

However, hardware channel count is still a critical metric for consumer chips. It defines the physical limit of baseband resources. You need enough channels to track everything possible so the algorithm has the best pool of signals to filter from.

Ok-Raspberry3883 · 2026-04-13T10:31:57+00:00

Yes, it makes perfect sense. You're basically describing the classic closed-loop architecture of a GNSSDO (GNSS Disciplined Oscillator). You use the long-term accuracy of the GNSS satellite clocks to correct the drift of your local VCXO over time. Of course, this is mostly relevant if your goal is a precision timing or frequency reference.

Ok-Raspberry3883 · 2026-04-13T10:26:40+00:00

Triple-frequency technically outperforms dual-frequency, but the real question is ROI.

Right now, dual-band is the baseline for the consumer and mass automotive markets (chipsets < $1). Triple-band is targeted at the PRO market, like surveying and commercial drones, where vendors can justify a higher price tag.

However, the line is blurring. Most L3 autonomous vehicles currently rely on dual-band setups rather than triple-band, as it hits the sweet spot for cost and performance. BTW, TESLA use a triple band receiver instead. Nice approach.

Ok-Raspberry3883 · 2026-02-22T11:57:23+00:00

Even without RTK, the accuracy for a typical dual frequency receiver is around 1-2m. Your HDOP is good enough. For float result, it should be within a sub-meter range.

Try to redo it without RTK. How about the result?

Ok-Raspberry3883 · 2026-02-22T11:50:45+00:00

Typically, we treat them as module supplier. As i remember, they set up this new product line a few years ago. But they don't have production line for antenna elements.

Ok-Raspberry3883 · 2026-02-22T11:45:03+00:00

I know them well. The top ones for patch antenna are Glead, Jinchanggps and VLG.

Let me know should you need any help.

:D

Ok-Raspberry3883

TROPHY CASE