On Fri, Jul 21, 2017 at 06:33:38AM +0200, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: > I noted in the file gps.c of the Xastir sources two problems in the decoding > of GPS NMEA sentences: only two types of sentences are decoded $GPRMC and > $GPGGA, no checksum is tested. > GPS devices have many different preambles, just in my case $IIRMC and > $IIGGA, II stands for integrated instruments, but there are many others that > are banned from Xastir. > Moreover, a control of the checksum is not complicate and it can be added. > I ask to the developers a comment on this issue, and in the case I can offer > a proposal for modification.
If you can code it in yourself, go ahead and make a fork on GitHub, do the work on a branch, and issue a pull request. So long as it doesn't break any other use cases, we'll very likely just merge it. I don't think either Curt or I have GPS units that produce those sentences, and I don't have time to work on it myself. I can't speak for Curt, but I think he's pretty busy these days, too. If you can't do the coding yourself, this might take longer than it might seem. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m] _______________________________________________ Xastir mailing list [email protected] http://xastir.org/mailman/listinfo/xastir
