TL;DR: why bright idea to disable GPGSV is basically a bad idea applicable to NEO receiver series — Imagine you’re about to design some realtime (ok, near-realtime) GPS application with UBlox NEO-6M (NEO-6,7,8) receiver, and already implemented my tweaks as described earlier — boosting GPS 10x faster, and serial baudrate 12x faster. What will be your next bottleneck? $GPGSV,4,1,16,01,42,181,22,03,70,029,28,04,57,291,32,06,14,320,24*78 $GPGSV,4,2,16,07,12,205,14,09,39,272,36,11,21,193,19,14,02,060,*7E $GPGSV,4,3,16,16,11,113,,17,09,270,07,18,20,169,19,19,09,287,32*70 $GPGSV,4,4,16,22,63,089,11,23,62,307,32,26,16,085,,31,15,040,08*7E…

TLDR: yes, it’s possible via direct NEO NMEA command. — So, let’s assume you have in hands one of these multiple IoT devices equipped with U-Blox GPS receivers. These receivers are among the most popular with our Ali’ friends, and, unfortunately are the most fake’d, so check your devices. As for me now, it’s ESP32-based TTGO modules, T-Beam v.22 The…

TLDR: it’s possible using internal command, even if docs say not — As you already noticed, we are able to tweak NEO GPS receiver to increase rate of measurements, from 1sec to 0.1sec, which gives us 10x drop in latency, but also 10x times of data must be sent using default serial protocol from device. …