Have you done a run time with a 1S lipo on this setup yet? I'd be jittery if the radio calls for 5V and you try to run it with something less even though you say there is a 3.3V regulator on the 3DR board. Is your GPS 3.3V?
Guy tried a 1S cell on an EggFinder and the thing choked by the time it was launched. Yeah, I know that's a different device but powering something differently than what's marked can lead to an unpleasant surprise.
Ahhh, I see with the program, OTG or B/T.
Other problem I see is you won't be able to track with this as the enabling Mock GPS location means your local GPS is subverted and the incoming stream is presumed your local position. Yes you will be able to see where it went, you can
take the lat/long and apply it to another application but won't be able to live track/navigate all in one app.
Shoot, the only way to live track then with the "GPS Rocket Locator" program would be to convert the receiver with a USB board like described above so the incoming strings could be used as the "rocket". I don't know if
GPS Rocket Locator can use an OTG connected source. Anyone know an answer that that? Kurt
To respond to your first point: It is my understanding that said "Guy" was in a bit of a hurry to push his L3, and either failed to calculate or miscalculated his tracker power requirements and used an insufficient battery capacity,therefore consuming what power was available while waiting on the pad. Correct me if I am wrong.
This type of error, however, could have been avoided with a little bit of math and an understanding of device power consumption. I have provided the data sheets for the two power-hungry transmitter components in a previous entry. Power requirements can be directly calculated with the information contained within the data sheets. This error is relatively simple to avoid as long as you do the math and ensure you supply the components with sufficient power (voltage and amp draw) to run the duration of your estimated pad, flight, and recovery times.
Personally, tracking is tantamount to proper flight computing/events execution, as I spend far too much time building them. My projects are not expendable. I take time and pay attention to detail on every one of them and want them back regardless of their condition, hence my motivation to piece together a low-cost, reliable, small form-factor, commercially available system with off the shelf crap (not smart enough to design my own stuff like Eggtimer).
As for your second point: I'm not sure what "this" is when you refer to mock locations. GNSS Commander does not require mock location. I know you value "live tracking", but I'm not sure how you define that. All GPS systems are live tracking. If what you mean is an application that plots a path from your position to the rocket (which I presume is the case), then I guess some just aren't happy without luxury in life.
To me, I could care less about a plot because I know how to read maps and orient myself using them. Realistically, how often would one follow the exact path anyway? In fact, I would posit that an application that simply plots a path from "A" to "B" without displaying coordinates or some other means of data logging would be dangerous to the cause. What if your receiver/phone/tablet/whatever failed? What if the battery died and you lost connection and were unable to regain a signal while replacing the battery, or any number of other failures were to occur?
Having and displaying a log of coordinates removes this dilemma, as I can apply them to any number of means to process them and eventually find my vehicle.
Finally, to your third point, I was unable to use OTG with "Rocket Locator".