ubertooth

This is "Open Hardware" which usually means open PCB or chip schematics, so people can modify or extend the board. OpenWRT is "Open Software that runs on closed hardware". After checking a couple, Kind of seems like a lot of boards on this "open hardware" list might not actually be open hardware? Here's an example of what open hardware is supposed to be: https://github.com/greatscottgadgets/ubertooth/tree/master/h...

Your article is great, too! I've saved it along with other Bluetooth resources for reference. Way more accessible than a video, thanks for posting it. There was nothing like it when I was deep in needing to maximize throughput. The thing I really appreciated in the presentation was the visualization of how each of the options increased throughput. I also was very thankful that CoreBluetooth handles so much for us. I was able to get our firmware updates to get to 85% theoretical speeds without having to do much fiddling (besides good algorithm design). I am jealous of your lab gear, though. I got Ubertooth [0] running for sniffing, but could only successfully follow a connection event about 25-33% of the time. [0] - https://github.com/greatscottgadgets/ubertooth

I’ve only used Ubertooth [0] to sniff BLE. I was not very impressed with its ability to follow connections (it would frequently miss the connection exchange due to channel hopping). Can using multiple micro:bits at once with BTLEJack increase the success rate? Most BLE diagnostic equipment that guarantees capture of all traffic costs over $10k. [0] - https://github.com/greatscottgadgets/ubertooth

There is much better hardware out there. The Ubertooth devices can pick up BLE, and can also plug into basically any antenna you want. It's been a while since I played with it, but a few years ago my ubertooth was grabbing LAPs without difficulty. It's not a dirt-cheap device (150$ all in) but is open and available from a variety of sources. https://github.com/greatscottgadgets/ubertooth/wiki/Capturin...

This is anecdotal evidence from my own experience, so take it with a pinch of salt. I work on an open hardware project[1], I believe that we lose a significant portion of users (~50%) at each step deeper in to the development process. It seems that the steps are along the lines of: binaries - source releases - code from GitHub - updating firmware - compiling firmware - debugging hardware. I think it would be useful to have a Virtualbox image available with everything set up for cross compiling for the Pi, BBB, etc. The thought of setting up non-standard toolchains seems to put off a lot of users. I've also been working on a project[2] involving the BeagleBone Black and I saw a sharp increase in users when I began distributing an OS image with everything pre-installed. [1] https://github.com/greatscottgadgets/ubertooth [2] https://github.c