Go Down

Topic: Problem reading value from a Nano 33 BLE Sense (Read 68 times) previous topic - next topic


This message was also posted on the Networks sub-boards. Being a beginner with Arduino, I try my few sketches, and I am currently facing a problem when trying to read a dummy value sent through bluetooth. Here is the sketch adapted from a LED example:
Code: [Select]

#include <ArduinoBLE.h>

BLEService ledService("19B10000-E8F2-537E-4F6C-D104768A1214"); // BLE LED Service

BLEByteCharacteristic fooCharacteristic("19B10001-E8F2-537E-4F6C-D104768A1214", BLERead | BLEWrite );

const int ledPin = LED_BUILTIN; // pin to use for the LED

void setup() {
  while (!Serial);

  // set LED pin to output mode
  pinMode(ledPin, OUTPUT);

  // begin initialization
  if (!BLE.begin()) {
    Serial.println("starting BLE failed!");

    while (1);

  // set advertised local name and service UUID:

  // add the characteristic to the service

  // add service
  // start advertising

  Serial.println("BLE LED Peripheral");

void loop() {
  // listen for BLE peripherals to connect:
  BLEDevice central = BLE.central();
  float testfloat = 3.14152;
  // if a central is connected to peripheral:
  if (central) {
    Serial.print("Connected to central: ");
    // print the central's MAC address:
    // while the central is still connected to peripheral:
    while (central.connected()) {

    // when the central disconnects, print it out:
    Serial.print(F("Disconnected from central: "));

With this on the device, I can connect with  gatttool on linux.
Code: [Select]

hms@joe:~/projects/arduino$ gatttool -I
[                 ][LE]> connect fc:57:4a:cb:ea:2e
Attempting to connect to fc:57:4a:cb:ea:2e
Connection successful
[fc:57:4a:cb:ea:2e][LE]> char-read-uuid 19B10001-E8F2-537E-4F6C-D104768A1214
Error: Read characteristics by UUID failed: Attribute PDU was invalid

And so there is this error:

Code: [Select]
Error: Read characteristics by UUID failed: Attribute PDU was invalid
I can connect with LightBlue from Android, read a value, but it appears that the hex on binary value that is read does not correspond to the value that is written by the device.
What am I doing wrong here? Can it be a problem with my laptop (and me being dumb at reading the value on LightBlue)?
Thanks for yout help!

Go Up