I use a high-rate GPS (10Hz) together with TrackAddict. As the GPS needs to be configured after power-up I always need to use another application first to do the necessary changes. Therefore it would be a great feature if one could enter a (hex-) string that is sent to the BT-GPS after connectng to automate this process...
Probably something like this coul dbe included in a future version..
regards!
I think we should be able to add that to our Android version, assuming it's as simple as others that I've seen... Most of the work has already been done for another situation, but there just hadn't previously been a need or request to give users direct control over this type of capability.Originally Posted by clumsy
Could you tell what brand/model of GPS you are using, what its Bluetooth device name is (ie what shows up when you go to pair with it, or go to select it in TrackAddict), and what the init string is that you'd need to send it? That will help me ensure that we're implementing the right kind of support for this, and maybe enable some automation of that as well.
I use a diy kit with with a u-blox max7-c receiver and a HC-05 Bluetooth module interconnected by uart. some example / important strings are (all in Hex):
set 10Hz navigation rate: b5 62 06 08 06 00 64 00 01 00 01 00 7a 12
set 1Hz navigation rate: b5 62 06 08 06 00 e8 03 01 00 01 00 01 39
(2 byte init, 2 byte message select, 8 byte message, 2 byte checksum)
others (like hot/coldstart, set baudrate, etc.)
thanks for your help, regards
Thanks. Our very next app update (v3.3.4) will offer a GPS "Setup" button for this on the More Options screen...
great! thanks! already any ideas on the version timeline?
My goal is to have v3.3.4 for Android released before this weekend. It's a maintenance and small features update, so there's not too much left that I need to add to it...
HI, seems to work fine (had to figure aout though how the string needs to be specified, eg. bytewise or as a whole)..... what happens when it disconnects and reconnects, does it send it again?
It should be fairly flexible in how you specify it, as long as it is a hexadecimal string... You can put spaces between the hex bytes (ie sets of 2) or not, but just don't do something weird like putting spaces between hex nybbles within a byte.
So, for example...
Valid: b5 62 06 08 06 00 64 00 01 00 01 00 7a 12
Valid: b562060806006400010001007a12
Invalid: b 5 6 2 0 6 0 8 0 6 0 0 6 4 0 0 0 1 0 0 0 1 0 0 7 a 1 2
This initialization data will be sent every time that the app makes a Bluetooth connection to the GPS. Typically, it maintains one connection when you are on any of the top-level screens (Setup, Camera Preview, Record, Sessions, etc) and certain other screens that you might adjust right before starting a session. If you go deeper, such as opening a specific session, then it will disconnect from the GPS to save battery, and will restart the connection if you go back to one of the top-level screens (at which point the init data would be sent again).
thank you... somehow the init without the spaces (second "Valid" line) did not work... however with the spaces inbetween it seems to work without issues.
this would mean, if the GPS looses power (or reception) the app reconnects and resends the init? if yes, that's perfect! thanks for implementig this..
Yes, if the GPS gets power cycled, then the Bluetooth connection should get reset as well, meaning that the init data gets sent again. Same goes for the Bluetooth going out of range, etc. Any time that the Bluetooth connection is lost, we have to close that socket and attempt to open a new one, at which point the init data will be sent.
Reply With Quote