I also use LightBlue on MacOS and find it pretty useful. Unfortunately, the mac version doesn't appear to support peripheral mode.
On Android devices, I use an app from Nordic called nRF Connect. Finally, for when I really need to see exactly what's happening, I use a Mynewt device running the bletiny app. Bletiny gives you a lot of control, and with full logging enabled, you can usually determine exactly what a peer device is doing. All that said, probably the most useful BLE development tool I've used is the Ellisys sniffer. They are quite expensive, but extremely powerful. Chris On Tue, Feb 07, 2017 at 10:10:59AM -0500, David G. Simmons wrote: > As one datapoint ... > > I use LightBlue -- on MacOS and iOS for initial testing. Depending on the > app, I also make heavy use of the MyNewt Sensor Reader app for Mac OS X and > iOS, but mostly that's because I wrote them. :-) > > dg > > > On Feb 6, 2017, at 8:57 PM, Sam Lewis <[email protected]> wrote: > > > > Hi all, > > > > Apologies if this has been asked before but I searched and couldn't find > > anything. > > > > For those of you who write mynewt Bluetooth applications, what is your > > development test set up and development workflow? > > > > Do you test your Bluetooth interface by using a Bluetooth adaptor from your > > development laptop/PC? Do you write scripts or use a generic testing > > application? Do you use your smartphone to interact with the Bluetooth > > interface? Or do you have a proper test rig test up? > > > > I'm guessing that most BLE applications eventually run against a smartphone > > app but for rapid development it doesn't seem that productive if I'm having > > to constantly recompile an app to test if my BLE interface is working as > > expected. > > > > Would be very interested in hearing productive workflows that people are > > using. > > > > Sam > > -- > David G. Simmons > (919) 534-5099 > Web <https://davidgs.com/> • Blog <https://davidgs.com/davidgs_blog> • > Linkedin <http://linkedin.com/in/davidgsimmons> • Twitter > <http://twitter.com/TechEvangelist1> • GitHub <http://github.com/davidgs> > /** Message digitally signed for security and authenticity. > * If you cannot read the PGP.sig attachment, please go to > * http://www.gnupg.com/ <http://www.gnupg.com/> Secure your email!!! > * Public key available at keyserver.pgp.com <http://keyserver.pgp.com/> > **/ > ♺ This email uses 100% recycled electrons. Don't blow it by printing! > > There are only 2 hard things in computer science: Cache invalidation, naming > things, and off-by-one errors. > >
