Fluke 287 Bluetooth Connection

[jadamroth]

Hi @dbbotkin, I have successfully communicated with my Fluke 289 over serial and everything is perfectly working.

I purchased the ir3000 FC connector to communicate with my dmm over bluetooth. I can discover my device, read the services and characteristics using the bleak python library. But I'm having some issues streaming the proper data from the dmm and haven't found any documentation or forums on bluetooth communication with the fluke 287.

A couple questions:

1. have you tried communicating to the fluke dmm over bluetooth?
2. the one value that changes when scanning my dmm services/characteristics returns these bytestrings, which I've tried decoding every which way to figure out what this means but have had no success

b'\x81\x11\x00F\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
b'\x9b\x0f\x00F\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
b'\xc5\x0f\x00F\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'

I really appreciate any help you can provide.

[dbbotkin]

I have no experience in communicating with the 289 using Bluetooth, only the infrared serial connection. I am assuming that the Bluetooth connection is serial as well and that the python utility bleak has some documentation for the serial interface. If I had to guess, I would check the serial transfer speed as the 289 is not capable of high speed serial transmission. I'll give this more thought tomorrow as it's nighttime here.

[dbbotkin]

Hello Adam, “Bleak’ for Python is new to me, but I plan to find out more as I have an interest in controlling Bluetooth devices. Thanks for the reference. As to your problem, the code below is ‘regular,’ meaning it is a message, not just random bytes. And it is not ASCII, meaning there are no readable letters and numbers for you. As I’m sure you know, x00 is the ’null’ character—nothing to see there. The odd part is the ‘x00F’ as it seems out of place to have a three-byte value in an otherwise regular listing of 2-byte. The data structure in the 289 is complicated and it took a while to figure it out. What exactly are you trying to access in your 289? I was after the raw data from voltage and current measurements without all the other stuff for analysis in plotting and statistical software. Not the real-time stream—that’s easy and well documented—I wanted the data from the recordings so I could leave the 289 unattended to collect measurements. In your last sentence, you mention ‘287’; is that a typo, or are you also trying to access a Fluke 287? I look forward to helping find a solution (and trying out bleak). Cheers, Donal Donal B. Botkin 556 Shagbark St. Windsor, CA. 95492

…

On Apr 28, 2022, at 21:23, Adam Roth ***@***.***> wrote: Hi @dbbotkin <https://github.com/dbbotkin>, I have successfully communicated with my Fluke 289 over serial and everything is perfectly working. I purchased the ir3000 FC connector to communicate with my dmm over bluetooth. I can discover my device, read the services and characteristics using the bleak <https://github.com/hbldh/bleak> python library. But I'm having some issues streaming the proper data from the dmm and haven't found any documentation or forums on bluetooth communication with the fluke 287. A couple questions: have you tried communicating to the fluke dmm over bluetooth? the one value that changes when scanning my dmm services/characteristics returns these bytestrings, which I've tried decoding every which way to figure out what this means but have had no success b'\x81\x11\x00F\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' b'\x9b\x0f\x00F\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' b'\xc5\x0f\x00F\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00' I really appreciate any help you can provide. — Reply to this email directly, view it on GitHub <#1>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABV2CDGX5KMEUWBSX7GFZH3VHNBYXANCNFSM5UULGFCQ>. You are receiving this because you were mentioned.

[jadamroth]

Thank you for the quick response.

1. I used Bleak because it was the easiest and quickest for me to get setup with python3 on my mac. Not sure if it's the best bluetooth library
2. That 3 byte value really through me off and glad it wasn't just me
3. Yes, I'm using fluke 287. It was a typo, but I'm pretty confident the 287 works the same as the 289 over serial
4. When I say stream, I mean just getting the raw value and unit from the screen. I know the serial commands can retrieve a lot more data under the hood, but I just wanted to start with raw value + unit

I'm going to keep working on this, but in the meantime you can reach out to me over email as well adam@nimbuscontrols.com

[ivan-volkov-embedded]

Hi,
Regarding the issue with "\x00F" - actually it is not a "3 byte value", but rather 2 bytes: the byte \x00 (Hex 0x00, ASCII code NUL) and the byte \x46 (Hex 0x46, ASCII code "F").
Usually in the logs the printable ASCII characters are displayed as text.
So overall each byte string is exactly 16 bytes.