Closed notpike closed 4 years ago
Excellent! I'll try to merge this this weekend.
How are you configuring the pin number of the jukebox? Does the app support a way to discover it?
Code compiles without warnings, using 4% of Flash and 1% of SRAM. I don't see anything that would hurt the stability of other apps or the system as a whole.
The pin number is set by holding the SET button, much like setting the time. Long term, I'd like a feature for finding the pin, either by sniffing packets from the bartenders remote or by scanning all 256 possibilities and breaking on success.
All in all, it looks good to merge as soon as I do a functional test in a real watch.
Confirmed with an SSB receiver that the packets are going out. As I don't have a TouchTunes box handy, we'll trust @notpike that the packets have the desired effect.
Idle current consumption when buttons are not being pressed stays at a reasonable 6µA. My testing unit measures a bit high, so it's probably lower in practice.
GoodWatch Current Consumption
0.0000064 +------------------------------------------------------------+
| + + + + |
0.0000063 |-+ AA AA AAAA AAnAAgytraAAAAxAA AAAAAA+A|
| |
| |
0.0000062 |AAA AA AAA AAAA AA AAAA AA AA +-|
| |
0.0000061 |-+ AAAA AA AA AA AAAAA AA AA AA-|
| |
| |
0.0000060 |-+ AAAA AAAA AAAA +-|
| |
0.0000059 |-+AA AA A AA A AA AA +A|
| |
| |
0.0000058 |A+ AAAA AA A AA AA AA A AA|
| + + + + |
0.0000057 +------------------------------------------------------------+
10 20 30 40 50 60
Seconds
6.088340 µA average consumption
22.484840 months of CR2016 battery life.
Active consumption is much higher, of course, at 16mA.
Hi!
Here's the tested application I wrote that emulates a wireless remote for a TouchTunes jukebox. If you have any questions or would like to see anything changed please let me know.
Thanks!