I'm excited that you have been making progess and that you have a connection!
I'm glad that it was as simple as changing the security setting.
Regarding the 2-digit versus 4-digit numbers for the L2CAP PSM codes (0019 and 0017 versus 19 and 17):
My experience has been that the iWrap command language simply interprets whatever numbers you give it and turns them into the correct numeric values under the hood. I know that the docs say the digit format is "XXXX" for those number, but then, if you look at their own examples of how the code is used, they use two digits for those numbers in all their examples.
I'm not clear on how they decide about the difference between hex numbers and decimal numbers. I think that their interpreter expects certain parameters to be either hex or decimal depending on what the parameter is "supposed to be" and does the conversion with the assumption that you used the correct format.
Regarding the reset button needing to be pushed "some" of the time, that was the initial thing that I experienced and talked about a few days ago. I like your idea of using a GPIO pin on the arduino to handle it (probably via another voltage divider I'm guessin), should that truly become necessary.
However the reset button thing stopped being a problem for me once I realized something:
- When I am powering the whole assembly purely via the Arduino USB debug cable, then the BlueGiga chip isn't always getting enough power for it to fully wake up automatically, so it's dark sometimes. Pressing its reset button usually wakes it up at that time, but it's kinda getting less juice than I would want it to get.
- On the other hand, if I power the Bluetooth board assembly via 5v obtains from empeg's power indirectly through the tuner connector and then through that Pololu power supply, then it always (at least for me) seems to get enough juice to fully power up.
- Empeg doesn't supply power to the tuner connector when asleep, so make sure the empeg is not asleep.
So my procedure for powering things up is:
- If I'm not debugging it, unplug the debug cable and just get the power from the Empeg's 12v power through the Pololu.
- If I am debugging it, connect the Arduino debug cable first so that the computer correctly detects the presence of the USB port, then immediately after that, apply power to the empeg.
- Make sure the empeg is not asleep.
I'm excited to learn what changes you're making for a Hijack release today. I hope that it's simply not doing the deduplication, because I'm pretty sure that's going to be the best solution. By the way, here are the two bugs I get because I'm having to work with the deduplication:
https://github.com/tfabris/BlueGigaEmpeg/issues/10https://github.com/tfabris/BlueGigaEmpeg/issues/9I'm also considering a change to the logging. Let me know what you think of this:
https://github.com/tfabris/BlueGigaEmpeg/issues/11
Previous Topic
Index
