Closed mswilk67 closed 6 years ago
Sorry for the slow reply: log_fd shouldn't print anything if it's passed a 0. What happens next?
Seems to just continue on its merry way but appears as a false positive error/warning.
I'm kind of stumped. I can't see why it's getting past that point. Could you run the library in the most verbose mode and paste the log?
Sorry but the equipment for that project is no longer available to me. I believe it was being test on an RPi. Of course the RPi had other issues with the built-in Bluetooth. It would a fair amount of effort/time to setup what I had to reproduce the issues I was seeing. It wasn’t failing, just giving a message. Kind of a false positive.
Michael S. Wilk MSW Technical Services LLC michael@gotwilk.us 916-390-1800
On Sep 5, 2018, at 12:36 AM, Edward Rosten notifications@github.com wrote:
I'm kind of stumped. I can't see why it's getting past that point. Could you run the library in the most verbose mode and paste the log?
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or mute the thread.
Ah OK, thanks for letting me know. I know what you mean about the RPi: that was the original deployment platform for this library. I also found that the chip did some very unusual but technically compliant things.
In blestatemachine.cc, there's a log_fd call that prints a log message "Function not implemented" at line 296. The message can be ignored but is falsely reporting a problem. The return value for ::connect() is 0 for success and thus the macro fails and prints the message.