The goal of the Eggfinder was to build an economical GPS rocket recovery device that was relatively simple to use, and didn't require the user to futz around with programming the GPS module. The uBlox units are more flexible, there is no doubt about that. They are also significantly more expensive than the Maestro Wireless unit, are not as readily available, and wouldn't do what I wanted to do right out of the box. The A2235H GPS module that's in the Eggfinder has its firmware in ROM, so it can't be messed up, but the corollary is that there are a limited number of "programming options" available for it. Out of the package it does what I needed it to do: stream NMEA serial data at 9600 baud. The only thing that I would really think about changing is to have it omit the $GPGSV records since I don't use them and they take up bandwidth, but it's more of an annoyance than an actual problem.
I think that BRB & Altus Metrum should be glad that the Eggfinder is doing well, because as Chuck inferred it's going to be a "gateway drug" into telemetry for many users. I've already had some people inquiring about the Eggfinder being a general-purpose telemetry platform; it ain't gonna happen, folks. There are plenty of other options, so I really wouldn't be bringing anything to the party. If you need more range, BRB & Altus Metrum may be a better choice; if you want a ton of telemetry options, Altus Metrum has you covered.
Whaddya mean Cris? Don't use $GPGSV? :rant::wink: One can download the Android Program "Bluetooth GPS" and certainly monitor that data:
https://play.google.com/store/apps/details?id=googoo.android.btgps&hl=en
$GPGSV
GPS Satellites in view
eg. $GPGSV,3,1,11,03,03,111,00,04,15,270,00,06,01,010,00,13,06,292,00*74
$GPGSV,3,2,11,14,25,170,00,16,57,208,39,18,67,296,40,19,40,246,00*74
$GPGSV,3,3,11,22,42,067,42,24,14,311,43,27,05,244,00,,,,*4D
$GPGSV,1,1,13,02,02,213,,03,-3,000,,11,00,121,,14,13,172,05*67
1 = Total number of messages of this type in this cycle
2 = Message number
3 = Total number of SVs in view
4 = SV PRN number
5 = Elevation in degrees, 90 maximum
6 = Azimuth, degrees from true north, 000 to 359
7 = SNR, 00-99 dB (null when not tracking)
8-11 = Information about second SV, same as field 4-7
12-15= Information about third SV, same as field 4-7
16-19= Information about fourth SV, same as field 4-7
All's I do is pair the HC-06 from the EF receiver (LCD or the blind receiver), fire up the B/T GPS program and click on HC-06. What that does is subvert the internal GPS of my Nexus 7 Flo (no cell phone inside) and it will allow me or anyone to see exactly what is coming out of the EggFinder and what satellites it's using and the relative accuracy. This messaging stuff I don't know anything about but can get an idea what's going on "inside" the EF remotely while on the pad.
When done, I just disconnect the HC-06 from the program, shut it down and fire up GPS rocket locator to get my two tracking points and a datum line to follow. One could use the "Bluetooth GPS" program by itself as it gives a dashboard with lat/long and one could transfer the info to a handheld mapping GPS. That would entail the use of three devices though. I have a small box I painted the inside flat black to suppress the glare of the sun and I can hold it with one hand containing the N7 and an EF receiver. That way I have a one handed tracking station that is readable under most conditions. Substitute a Ham radio H/T and a Mobilnkd TNC for the EggFinder receiver and one has an APRS tracker for the Ham band with APRSDroid. Kurt :gavel: