My coding is crap. The code at the core of the AVA1 & AVA2 boards was old, nasty and had some buffer overflows in it I could never track down. I’m sure the issues related to the way I was reading the NMEA data and parsing the\u00a0GPGGA, occasionally and unreproducibly\u00a0it would just give overflows usually when it was getting locks.<\/p>\n
I started the code again and with the assitance of Jcoxon’s Project EURUS code<\/a> I changed the way it gets the data from the GPS by switching to polling the GPS for its location. Its much more efficient, also I’ve put in checks and timesouts that were missing on the original code and moved everything to procedures.<\/p>\n All the complex flight status stuff has been removed and I’ve redone the temperature parts. Finally on review I’ve amended the default RTTY from ASCII-8 1 stop bit to ASCII-7 2 stop bits. Additionally I’m sending 10 nulls before commencing transmission to aid the trackers and AFC in dl-fldigi. Hopefully these changes will make a more decodable signal.<\/p>\n I’m really pleased how its worked out, in fact now I’ve procedurised everything it was a very trivial 10 minute job to amend the code to work with the RFM22B making both a RTTY and\u00a0Hellschreiber<\/a>\u00a0beacon.<\/p>\n The code for all variants is now about 10kB as opposed to the 18kB it was previously.<\/p>\n","protected":false},"excerpt":{"rendered":" My coding is crap. The code at the core of the AVA1 & AVA2 boards was old, nasty and had some buffer overflows in it I could never track down. I’m sure the issues related to the way I was …<\/p>\n