Select to expand quotedecrepit said..
Had my second sail yesterday, in cleaned prescription glasses, with our boom mounted units.
I was concentrating on alphas, on smooth water, it was fine I could read the deviation display Ok, but once I hit the small chop, it became almost impossible to read.
To make this function useful for me, I'd need the deviation numbers to be much bigger.
Is it possible for the alpha function to take over the whole screen?
It's only for the first 250m after a gybe, so shouldn't affect the other functions too much.
I know some others aren't having this problem, is it because I'm light and bounce around more?
Or just that I'm ancient and my eyes can't follow a moving screen very well?
Anyway if somebody has a solution I'd be very thankful!
The Boom mount is great but having to turn your head to view when belting down a speed run thought I'd try a unit mounted in close to forward view. Proto moulded to forearm using divinycell. GPS is always facing skyward so not like the watch. Will glass the unit and then pot will see how it performs.
Coud be better Boz, but are you having one on each arm, or just change arms depending on run.
I'm certainly right about my head moving around.
Just had a look at yesterdays' 2s run.
Blue is GW60, ignore that it has internal smoothing, but the other 3 at 10hz don't. Magenta is my head unit, green and red are the boom units. You can see the head unit is moving around much more than the others, to make matters worse it's out of phase with the boom units. So the relative movement between eyes and esp is quite large. Interesting but I guess it doesn't help much
Re above. I just realised, it's an apples and oranges situation. The head unit is set to use the portable dynamic model, both boom units use the sea model.
That could possibly be the difference in sawtooth between them?
Select to expand quoterp6conrad said..BigBoss said:
Hi Jan,
I noticed that the logo choice number does not responded correct to the logo's. Logo choice 12 should give Gaastra and Fanatic, but it displayed Fanatic and duotone.
Other issue, i want to change the timezone, but when i submitted the browser say that the 'barlenght' must be more than 1000 ( i had 500). Oke i changed it to 1000 then GPIO12_screen should be less than 1000.
The fieldchecks looks a little off ;-)
I did just checked the logos, on my browser (chrome / win10) everythings looks fine. Just the saillogo's 3 and 4 (both NP) were in reverse order. Logo 12 should display Fanatic and Duotone (board logo 1, sail logo 2).
The barlength is now limited between 1000 and 1852 meter, but I can enlarge this window from 250 - 10000 (can be handy in the Defi wind...). Timezone did work for me as it should. Only the change of the logOAO field was rather difficult, probably due to missing credits....
(sorry for the joke, i could not resist...).
Here the corrected logo list :
Hi Jan, I've flashed my units with 5.60, and but had issues with Logo_choice field in the config.txt. I've never played with this field, but decided to now. So I had to look at your code to find out what was going on. According to your code, it's parsing the config.Logo_choice field as:
"Logo_choice":,(sail logo)(board logo)
and not
"Logo_choice":,(board logo)(sail logo)
The modo operator you are using is processing the right most digit. Then you do a divide by 10, and the value in Logo_choice gets 10 base shifted to the right. Then repeat. So the digits in the Logo_choice field in the config.txt get read from right to left.
Also, what is the idea of the "if(Logo_choice > 99)" condition ?. Is this a once off test ?. If so, why is it in the for loop ?
SD_card.cpp (version 5.60):
--$-------------
.
.
210 for (int i=0;i 99){
223 logo_choice[0]=Logo_choice;
224 } else { // else default logos
225 logo_choice[i]=Logo_choice%10;//
226 Logo_choice=Logo_choice/10;
227 if(Logo_choice>0){
228 config.logo_count=i+1;
229 }
230 }
.
.
--$-------------
Select to expand quotejn1 said..rp6conrad said..BigBoss said:
Hi Jan,
I noticed that the logo choice number does not responded correct to the logo's. Logo choice 12 should give Gaastra and Fanatic, but it displayed Fanatic and duotone.
Other issue, i want to change the timezone, but when i submitted the browser say that the 'barlenght' must be more than 1000 ( i had 500). Oke i changed it to 1000 then GPIO12_screen should be less than 1000.
The fieldchecks looks a little off ;-)
I did just checked the logos, on my browser (chrome / win10) everythings looks fine. Just the saillogo's 3 and 4 (both NP) were in reverse order. Logo 12 should display Fanatic and Duotone (board logo 1, sail logo 2).
The barlength is now limited between 1000 and 1852 meter, but I can enlarge this window from 250 - 10000 (can be handy in the Defi wind...). Timezone did work for me as it should. Only the change of the logOAO field was rather difficult, probably due to missing credits.... (sorry for the joke, i could not resist...).
Here the corrected logo list :
Hi Jan, I've flashed my units with 5.60, and but had issues with Logo_choice field in the config.txt. I've never played with this field, but decided to now. So I had to look at your code to find out what was going on. According to your code, it's parsing the config.Logo_choice field as:
"Logo_choice":,(sail logo)(board logo)
and not
"Logo_choice":,(board logo)(sail logo)
The modo operator you are using is processing the right most digit. Then you do a divide by 10, and the value in Logo_choice gets 10 base shifted to the right. Then repeat. So the digits in the Logo_choice field in the config.txt get read from right to left.
Also, what is the idea of the "if(Logo_choice > 99)" condition ?. Is this a once off test ?. If so, why is it in the for loop ?
SD_card.cpp (version 5.60):
--$-------------
.
.
210 for (int i=0;i 99){
223 logo_choice[0]=Logo_choice;
224 } else { // else default logos
225 logo_choice[i]=Logo_choice%10;//
226 Logo_choice=Logo_choice/10;
227 if(Logo_choice>0){
228 config.logo_count=i+1;
229 }
230 }
.
.
--$-------------
You are right, board /sail logo choice is now inverted. Better to make 2 separat choices, one for the sail and one for the board. If you now set the value to 100, you get the big beer logo from tritondm. Select to expand quotedecrepit said..
Had my second sail yesterday, in cleaned prescription glasses, with our boom mounted units.
I was concentrating on alphas, on smooth water, it was fine I could read the deviation display Ok, but once I hit the small chop, it became almost impossible to read.
To make this function useful for me, I'd need the deviation numbers to be much bigger.
Is it possible for the alpha function to take over the whole screen?
It's only for the first 250m after a gybe, so shouldn't affect the other functions too much.
I know some others aren't having this problem, is it because I'm light and bounce around more?
Or just that I'm ancient and my eyes can't follow a moving screen very well?
Anyway if somebody has a solution I'd be very thankful!
I try to change the fonts so that the first line font is bigger, but then the second line (actual speed) has to be smaller. Now we have first line 18pt, second line 96 pt. I could make that configurable over the webserver.
Select to expand quotedecrepit said..
Re above. I just realised, it's an apples and oranges situation. The head unit is set to use the portable dynamic model, both boom units use the sea model.
That could possibly be the difference in sawtooth between them?
It's a possibility. This might not be possible (different mounts) but it might also be worth switching the roles of the units to see if it is specific to the head or the unit.
Select to expand quoterp6conrad said..jn1 said..rp6conrad said..BigBoss said:
Hi Jan,
I noticed that the logo choice number does not responded correct to the logo's. Logo choice 12 should give Gaastra and Fanatic, but it displayed Fanatic and duotone.
Other issue, i want to change the timezone, but when i submitted the browser say that the 'barlenght' must be more than 1000 ( i had 500). Oke i changed it to 1000 then GPIO12_screen should be less than 1000.
The fieldchecks looks a little off ;-)
I did just checked the logos, on my browser (chrome / win10) everythings looks fine. Just the saillogo's 3 and 4 (both NP) were in reverse order. Logo 12 should display Fanatic and Duotone (board logo 1, sail logo 2).
The barlength is now limited between 1000 and 1852 meter, but I can enlarge this window from 250 - 10000 (can be handy in the Defi wind...). Timezone did work for me as it should. Only the change of the logOAO field was rather difficult, probably due to missing credits.... (sorry for the joke, i could not resist...).
Here the corrected logo list :
Hi Jan, I've flashed my units with 5.60, and but had issues with Logo_choice field in the config.txt. I've never played with this field, but decided to now. So I had to look at your code to find out what was going on. According to your code, it's parsing the config.Logo_choice field as:
"Logo_choice":,(sail logo)(board logo)
and not
"Logo_choice":,(board logo)(sail logo)
The modo operator you are using is processing the right most digit. Then you do a divide by 10, and the value in Logo_choice gets 10 base shifted to the right. Then repeat. So the digits in the Logo_choice field in the config.txt get read from right to left.
Also, what is the idea of the "if(Logo_choice > 99)" condition ?. Is this a once off test ?. If so, why is it in the for loop ?
SD_card.cpp (version 5.60):
--$-------------
.
.
210 for (int i=0;i 99){
223 logo_choice[0]=Logo_choice;
224 } else { // else default logos
225 logo_choice[i]=Logo_choice%10;//
226 Logo_choice=Logo_choice/10;
227 if(Logo_choice>0){
228 config.logo_count=i+1;
229 }
230 }
.
.
--$-------------
You are right, board /sail logo choice is now inverted. Better to make 2 separat choices, one for the sail and one for the board. If you now set the value to 100, you get the big beer logo from tritondm. decrepit said..
Had my second sail yesterday, in cleaned prescription glasses, with our boom mounted units.
I was concentrating on alphas, on smooth water, it was fine I could read the deviation display Ok, but once I hit the small chop, it became almost impossible to read.
To make this function useful for me, I'd need the deviation numbers to be much bigger.
Is it possible for the alpha function to take over the whole screen?
It's only for the first 250m after a gybe, so shouldn't affect the other functions too much.
I know some others aren't having this problem, is it because I'm light and bounce around more?
Or just that I'm ancient and my eyes can't follow a moving screen very well?
Anyway if somebody has a solution I'd be very thankful!
I try to change the fonts so that the first line font is bigger, but then the second line (actual speed) has to be smaller. Now we have first line 18pt, second line 96 pt. I could make that configurable over the webserver.
I rarely look at actual speed when things get "interesting".
Select to expand quoterp6conrad said..
You are right, board /sail logo choice is now inverted. Better to make 2 separat choices, one for the sail and one for the board. If you now set the value to 100, you get the big beer logo from tritondm.
I reckon just leave it how it is. It doesn't matter if it's sail first or board first in my opinion. Just ensure you document it. In your instructions, you specify the config.txt file, but you've omitted the Logo_choice field in your description.
docs.google.com/document/d/1j86kj3bNMID3sHCRT7QTYyrL7IHeQnGPec1LajsDfB4/edit
Select to expand quoteK888 said..It's a possibility. This might not be possible (different mounts) but it might also be worth switching the roles of the units to see if it is specific to the head or the unit.
Good thinking but not possible. two units are specifically designed to fit on the boom. One is designed to fit on the head. But I can easily change the boom units to portable. Not so easy to change the head unit to sea. I have to remember how to drive U-center.
Select to expand quoterp6conrad said.. I try to change the fonts so that the first line font is bigger, but then the second line (actual speed) has to be smaller. Now we have first line 18pt, second line 96 pt. I could make that configurable over the webserver.
Thanks Jan, configurable sounds good.
Select to expand quoteAus501 Boz said..decrepit said..
Had my second sail yesterday, in cleaned prescription glasses, with our boom mounted units.
I was concentrating on alphas, on smooth water, it was fine I could read the deviation display Ok, but once I hit the small chop, it became almost impossible to read.
To make this function useful for me, I'd need the deviation numbers to be much bigger.
Is it possible for the alpha function to take over the whole screen?
It's only for the first 250m after a gybe, so shouldn't affect the other functions too much.
I know some others aren't having this problem, is it because I'm light and bounce around more?
Or just that I'm ancient and my eyes can't follow a moving screen very well?
Anyway if somebody has a solution I'd be very thankful!
The Boom mount is great but having to turn your head to view when belting down a speed run thought I'd try a unit mounted in close to forward view. Proto moulded to forearm using divinycell. GPS is always facing skyward so not like the watch. Will glass the unit and then pot will see how it performs.
I like the style, nice and clean. Are you not worried it will slide towards the wrist? But the same design will also work for the upper arm I guess. What do you do with the space right of the BN220? Is that empty? Easy to the usb connector and some space for the sdcard?
Select to expand quoteFreezer said..Aus501 Boz said..decrepit said..
Had my second sail yesterday, in cleaned prescription glasses, with our boom mounted units.
I was concentrating on alphas, on smooth water, it was fine I could read the deviation display Ok, but once I hit the small chop, it became almost impossible to read.
To make this function useful for me, I'd need the deviation numbers to be much bigger.
Is it possible for the alpha function to take over the whole screen?
It's only for the first 250m after a gybe, so shouldn't affect the other functions too much.
I know some others aren't having this problem, is it because I'm light and bounce around more?
Or just that I'm ancient and my eyes can't follow a moving screen very well?
Anyway if somebody has a solution I'd be very thankful!
The Boom mount is great but having to turn your head to view when belting down a speed run thought I'd try a unit mounted in close to forward view. Proto moulded to forearm using divinycell. GPS is always facing skyward so not like the watch. Will glass the unit and then pot will see how it performs.
I like the style, nice and clean. Are you not worried it will slide towards the wrist? But the same design will also work for the upper arm I guess. What do you do with the space right of the BN220? Is that empty? Easy to the usb connector and some space for the sdcard?
Will be testing if it slides, originally shaped the divinycell cell for upper arm and probably this is we're it will end doesn't take long to make the shape approx 40min. Space can be used for a number of things but for myself this is for a active piezo buzzer with gortex above the sound opening to prevent water ingress.
I currently use a sound function to indicate when I reach a particular set speed (GT31) this keeps my concentration on what's in front of me without looking at the actual speed for me it works well and motivates me to keep pushing the board speed.
I've worn my GW60, Motion LCD and Garmin 245 on my upper forearm for the last 4 years. They rarely slide down the arm and I've never lost one in a crash. I don't look at the screen in runs, except the Garmin when tracking the separation distance on the return leg of an alpha.
Select to expand quoteJohn340 said..
except the Garmin when tracking the separation distance on the return leg of an alpha.
Same here with the ESP, separation distance on the Alpha, the only thing I do currently is set over speed alarm on the GT31 which beeps every .5 sec at 38knots then I know I've got to push it with one more gust to reach 40 were I set the speed genie which gives a different sound. Having sound keeps your eyes forward if that makes sense. At the moment just mucking about with a test ESP unit.
Select to expand quoteJohn340 said..
...I don't look at the screen in runs.
Interesting. We had a few sessions in small chop (maybe 20 cm), and never looked at the screen when going for top speed. I thought that perfectly flat water might be a different story, since you have to worry less about hitting chop wrong and catapulting. That's not an issue with sound feedback.
I have used the ESP screen during nauti runs even in chop, though. I guess you get more time to look so you can pick safe spots, and I'm usually going a bit slower, too. But I'll bring the phones and head phones on our trip to WA.
Select to expand quoteboardsurfr said..John340 said..
...I don't look at the screen in runs.
Interesting. We had a few sessions in small chop (maybe 20 cm), and never looked at the screen when going for top speed. I thought that perfectly flat water might be a different story, since you have to worry less about hitting chop wrong and catapulting. That's not an issue with sound feedback.
I have used the ESP screen during nauti runs even in chop, though. I guess you get more time to look so you can pick safe spots, and I'm usually going a bit slower, too. But I'll bring the phones and head phones on our trip to WA.
Perhaps we can add a buzzer to one of the ESP32 ports to give some audible feedback. No need for phones and/or headphones.. Although there is bluetooth a well. Not sure we can provide even more sophisticated feedback though that...
Select to expand quoteFreezer said..boardsurfr said..John340 said..
...I don't look at the screen in runs.
Interesting. We had a few sessions in small chop (maybe 20 cm), and never looked at the screen when going for top speed. I thought that perfectly flat water might be a different story, since you have to worry less about hitting chop wrong and catapulting. That's not an issue with sound feedback.
I have used the ESP screen during nauti runs even in chop, though. I guess you get more time to look so you can pick safe spots, and I'm usually going a bit slower, too. But I'll bring the phones and head phones on our trip to WA.
Perhaps we can add a buzzer to one of the ESP32 ports to give some audible feedback. No need for phones and/or headphones.. Although there is bluetooth a well. Not sure we can provide even more sophisticated feedback though that...
Correct Freezer, the active Piezo buzzer is triggered when a Desired speed is reached and a 500ms delay applied to turn the buzzer on/off while at or above the set desired speed eg 38knts
When Achieved speed is reached a 250ms delay is applied while or above the Achieved Speed, this way you know you've reached the Achieved speed eg 40knts.
The buzzer is inactive if the above conditions are not met.
Two Int one for Desired speed and one for Achieved speed can be set in the Config file eg As above I set 38knots as Desired speed and 40knt as Achieved speed.
It's just the tone that is manipulated by putting a delay to give the beeping sound from the Piezo around 85-90dB.
The principal comes from the overspeed function and Speed Genie function of the GT31, setting the overspeed gives a uniform beep and the speed genie a faster beep.
Select to expand quotedecrepit said..rp6conrad said.. I try to change the fonts so that the first line font is bigger, but then the second line (actual speed) has to be smaller. Now we have first line 18pt, second line 96 pt. I could make that configurable over the webserver.
Thanks Jan, configurable sounds good.
Font size first line for the speed screen is now configurable. In the original speed-screen, you could see the last alfa, and the best alfa of the session. The same for NM, last NM and best NM. With the large fonts, this is reduced to only last Alfa and last NM.
Some other changes :
* SW5.61 First draft new open source fileformat
* Some minor changes for the webserver (triton_dm)
* Separate Board_logo and Sail_logo config
* Test with other fonts in speed screen, added "speed_large_font" to the config : Run, Alfa and NM can have a bigger font.
* Changed order config.field, 1=Auto between Run, Alfa & NM, 2=Run & NM, 3=Alfa, 4=NM, 5= Total distance, 6= 2s/10s, 7= 0.5h, 8= 1h
* Font 46pt_nr and 84pt_nr added, condensed format only digits and decimal point to save memory
* Added Github link to main menu
Select to expand quoteFreezer said..
Perhaps we can add a buzzer to one of the ESP32 ports to give some audible feedback. No need for phones and/or headphones.. Although there is bluetooth a well. Not sure we can provide even more sophisticated feedback though that...
In theory, it should be possible to add voice output over bluetooth. The Flysight GPS had voice announcements working on a pretty crappy processors (via plug, though), so it is doable without too much overhead.
But I think the number of speedsurfer who ever used voice feedback is quite small, and the great display on the ESP logger makes voice feedback less relevant, so I'm not sure it is worth much effort. If someone who is already familiar with voice feedback/speech generation and bluetooth on the ESP chip would want to give it a shot, that might be a different story.
I have been inspired by this forum to build my own hardware GPS logger and try out some new stuff based on what I think will work. It is slow progress (due to lack of time) and I have kept quiet as I don't have a working unit to share results. But happy to share when I have some results, eta is early next year. Currently the project is just bits on my desk.
On the topic of Audio feedback, my unit will have a Class D audio amplifier communicating over the I2S bus to the ESP32 running Arduino code. Bench testing has proved the audio is louder than my cell phone. Will it be loud enough in a sealed box? That remains to be tested.
My use case for the audio could be speed/alpha/NM etc announcements, but would also love to geofence (if I can code that!) some underwater obstacles so I can venture away from my local spot and be more confident of not hitting something at certain tides etc.
My back up plan for audio is ESP audio to Bluetooth earbuds or waterproof speaker.
I can stream audio (eg spotify) via bluetooth from my cell phone to the ESP32 and have it play music (not really that useful for windsurfing).
This was using drivers and examples from here: github.com/pschatzmann/ESP32-A2DP
What could be more useful is sending audio over bluetooth from the ESP32. The comments from pschatzmann on his github repository suggest the driver can work as a "A Simple Arduino Bluetooth Music Receiver and Sender for the ESP32".
FWIW I did try the music sender example but I did not have any luck in getting it going. The ESP32 could see the Bluetooth speaker and connect to it but no audio came out of the speaker. I only spent a couple of hours on it and that was near the beginning of this year, I see some updates to the Github repository have been made since then so I will have another look next time I'm coding in this area.
For those that are familiar with the Arduino environment and want to play with audio, check out the driver as it *might* be just what you want.
Be interesting to see the power consumption/processing requirements required for Bluetooth and audio processing on top of GPS function.
I use mobile phone with GPSlogit with bluetooth headphones and things go flat pretty quickly.
Select to expand quoteelmo said..
Be interesting to see the power consumption/processing requirements required for Bluetooth and audio processing on top of GPS function.
I use mobile phone with GPSlogit with bluetooth headphones and things go flat pretty quickly.
Thats interesting. I also use Logit with speed audio but I have not noticed it uses noticeably more battery when talking. I dont use BT headphones though, just hear it from the phone speaker. Perhaps the sending of the BT data chews up battery more? It took me a while to find a cheap android phone with a louder than average speaker, but now it is fine.
Just hearing my current speed in (more or less) real time is very helpful to me for Alphas,1hr and Nautical Miles. It also helps me work out my best upwind angle.
I highly recommend adding audio speed talk it to your Loggers if you can.
Select to expand quoterp6conrad said..
Font size first line for the speed screen is now configurable. In the original speed-screen, you could see the last alfa, and the best alfa of the session. The same for NM, last NM and best NM. With the large fonts, this is reduced to only last Alfa and last NM.
Some other changes :
* SW5.61 First draft new open source fileformat
* Some minor changes for the webserver (triton_dm)
* Separate Board_logo and Sail_logo config
* Test with other fonts in speed screen, added "speed_large_font" to the config : Run, Alfa and NM can have a bigger font.
* Changed order config.field, 1=Auto between Run, Alfa & NM, 2=Run & NM, 3=Alfa, 4=NM, 5= Total distance, 6= 2s/10s, 7= 0.5h, 8= 1h
* Font 46pt_nr and 84pt_nr added, condensed format only digits and decimal point to save memory
* Added Github link to main menu
Thanks for doing this, I'm looking forward to trying it without glasses!
One tiny thing, do you think it would be better to have "Gate" rather than "Wind"? We all know what it means now but "wind" could mean a number of things.
Select to expand quotesailquik said..elmo said..
Be interesting to see the power consumption/processing requirements required for Bluetooth and audio processing on top of GPS function.
I use mobile phone with GPSlogit with bluetooth headphones and things go flat pretty quickly.
Thats interesting. I also use Logit with speed audio but I have not noticed it uses noticeably more battery when talking. I dont use BT headphones though, just hear it from the phone speaker. Perhaps the sending of the BT data chews up battery more? It took me a while to find a cheap android phone with a louder than average speaker, but now it is fine.
Just hearing my current speed in (more or less) real time is very helpful to me for Alphas,1hr and Nautical Miles. It also helps me work out my best upwind angle.
I highly recommend adding audio speed talk it to your Loggers if you can.
Probably is Bluetooth related
I just uploaded 5.61 to one unit and it crashed at the first "wake up" page when it auto rebooted after the update.
At the moment it's stuck on the wake up page and won't shut down. I guess my only option is to wait for the battery to run down.
It won't connect to the computer in this state.
I'm not game to try the other.
Alby said to try charging, that worked after a while.
I'll take 5.60 and 5.61 for a drive and compare the difference with them side by side.
I think it will do the trick though, I could read it while jogging.
Just been for a drive, both displays looked the same, so checked the config file and as Jan says, it's configurable, with old display the default. You have to select "large font" for top panel.
And in our case also change from Km/h to knots. For some reason, every time you open the config file with the webserver it changes kts to Km/h, but leaves the rest of your settings alone?
Anyway enough of that. Thanks again Jan, for the very prompt change, that looks ideal now, can't wait to try it on the water.
Select to expand quoteremery said..
One tiny thing, do you think it would be better to have "Gate" rather than "Wind"? We all know what it means now but "wind" could mean a number of things.
You are right, I will change that.
About the BT audio, this should be possible, but there can be a issue with keeping up with the 10Hz datalogging. It has to be tried, but I never did something with BT / Audio. A simple buzzer is always possible.
The Freezing after a update happens me on a few occasions, but they al recover after a flat battery or a reset. My advice for sealed units : only do a update when you dont plan to use it for the next 24 hours. When it is stuck, the battery has to go flat, and then you can recharge and it will recover.
There was one occasion when the unit was "unrecoverable" due to a bad bin file : I had updated the ESP32 library to version 2.x. With this bin file, the ESP32 came always in a bootloop (on the serial output : "Panic core 1..."). But over usb, I could flash the unit again with a good bin file.
For those who compile there own bin files, I advice to do al tests with a unsealed unit !
Greetings, Jan.
Jan,
Thanks a lot mate, the bigger font looks fantastic! I think that will make big difference to my alphas.
And like hammer, my crashed unit recovered with a recharge, worth trying if the battery is fairly full.
Select to expand quoteelmo said..
Be interesting to see the power consumption/processing requirements required for Bluetooth and audio processing on top of GPS function.
I use mobile phone with GPSlogit with bluetooth headphones and things go flat pretty quickly.
Audio processing can be pretty trivial, and should not use much power when implemented in a decent way (otherwise, the Flysight would never be able to). That probably means using pre-defined files rather than text-to-speech engines, which would be overkill.
Bluetooth should also not be a large drain on power, compared to the ~ 100 mA currently needed for the GPS chip and the ESP.
When I use phones and headphones for speed announcements, the phone usually lasts through a typical 2-3 hours session without problems. Old phones and batteries could be an issue, though. The cheap phone I got 4 years in Oz was quite inferior to the ones I got in the US before, perhaps because the US companies subsidized the pay-as-you-go cheap phones more. Newer phones tend to have bigger batteries, but also bigger screens and higher weights, so they can be more of a pain to have on the arm.
I do recall quite vividly how the phone was talking sweet numbers to me almost 4 years ago in Fangyland during PB runs, following Stroppo. Hope to hear (and see) similar numbers at the same spot again soon!
