Re: Device Info Characteristics with an OLS425 and Mac OS X
Re: Device Info Characteristics with an OLS425 and Mac OS X
- Subject: Re: Device Info Characteristics with an OLS425 and Mac OS X
- From: Ringwald Matthias <email@hidden>
- Date: Tue, 18 Feb 2014 06:50:19 +0000
- Thread-topic: Device Info Characteristics with an OLS425 and Mac OS X
Hi James
To get some more information about what goes wrong, you can install the “Hardware Tools for Xcode/Mavericks” from the Apple’s developer pages. It contains the excellent PacketLogger tool to look at the actually ATT protocol data being exchanged with your peripheral. Alternatively, you could also try an air sniffer, like the one that’s part of TI’s CC2540 developer kit.
Best
Matthias
On 17.02.2014, at 20:07, James Snyder <email@hidden<mailto:email@hidden>> wrote:
Hi -
I’ve recently been working with a connectBlue OLS425 module (http://www.connectblue.com/products/bluetooth-low-energy-products/bluetooth-low-energy-modules/bluetooth-low-energy-serial-port-module-ols425ols426/) with iOS and things have gone mostly smoothly there (aside from connection interval limiting baud rate).
However, when I tried to make a port over to Mac OS X, I began noticing some issues on my MacBook Pro Retina, 13-inch, Late 2013 running 10.9.1, mainly that the device info characteristics are not being reported correctly. This happens when writing my own code for connecting to the device and also in LightBlue 1.2.
I’m expecting to see 2A24, 2A26, 2A28 & 2A29, but only get:
- Connected to device UUID: 8BB05933-69AB-41EE-A87F-475BBD39C72F Named: OLS425
- UUID 2A24 Read Value: 0x636F6E6E656374426C7565
- UUID 2A26 Read Value: 0x4F4C53343235
- UUID 2A29 Read Value: 0x636F6E6E656374426C756500
So the Model Number (2A24) shows almost the same value as Manufacturer Name (2A29) minus a null byte and Firmware revision (2A26) gives what should be in the model number field (2A24).
What’s interesting is that I can get correct values for each characteristic by using LightBlue 1.2 running on 10.9.1 in a Parallels VM on the same rMBP with the internal Bluetooth module switched to the VM (though reading values is laggy in that context):
- Connected to device UUID: 71C1FDFD-DC8D-4723-8657-2629368C0AEE Named: OLS425
- UUID 2A29 Read Value: 0x636F6E6E656374426C756500
- UUID 2A24 Read Value: 0x4F4C53343235
- UUID 2A26 Read Value: 0x312E332E30203130313337
- UUID 2A28 Read Value: 0x312E332E30203130313337
With gatttool under Linux (in a VM, same Apple internal module allocated to the VM), I get:
[ ][78:C5:E5:6D:97:14][LE]> connect 78:C5:E5:6D:97:14
[CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a29-0000-1000-8000-00805f9b34fb
handle: 0x0012 value: 63 6f 6e 6e 65 63 74 42 6c 75 65
[CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a24-0000-1000-8000-00805f9b34fb
handle: 0x0014 value: 4f 4c 53 34 32 35
[CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a26-0000-1000-8000-00805f9b34fb
handle: 0x0016 value: 31 2e 33 2e 30 20 31 30 31 33 37
[CON][78:C5:E5:6D:97:14][LE]> char-read-uuid 00002a28-0000-1000-8000-00805f9b34fb
handle: 0x0018 value: 31 2e 33 2e 30 20 31 30 31 33 37
The Linux and VM OS X results seem to be accurate, since the expected displayed values for all of these are:
0x2A29 -> Manufacturer Name -> connectBlue
0x2A24 -> Model number -> OLS425
0x2A26 -> Firmware revision -> 1.3.0 10137
0x2A28 -> Software revision -> 1.3.0 10137
Has anyone run into issues like this before on Mac OS X or know of any solutions or workarounds? One thing that seems like a bit of a clue is the order that the characteristics show up in LightBlue: 2A29, 2A24, 2A26, 2A28 when correct, 2A24, 2A26, 2A29 when incorrect.
Also, the vendor (connectBlue) tried using LightBlue 1.2 on a MacBook Air running 10.8.5 and got correct values in that context.
Best.
James Snyder
Global Satellite Engineering
Senior Engineer
(m) +1.847.644.2322
www.gsat.us<http://www.gsat.us/>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden<mailto:email@hidden>)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden