In the examples, it is not documented why the packet reading code requires all GATT values to begin with the '!' character.

Especially curious is why the replyidx is reset when a second '!' character is encountered in the value. What if a '!' character is actually intended to be part of the value the master device is trying to send to the BluefruitLE?

https://github.com/adafruit/Adafruit_BluefruitLE_nRF51/blob/b80b880a62646223ba28b93301164c2134c9f4fc/examples/cplay_neopixel_picker/packetParser.cpp#L101

• Arduino board: Arduino UNO
• Arduino IDE version (found in Arduino -> About Arduino menu): 1.6.12
• Bluefruit board: BluefruitLE UART Friend
  • Nordic Chip: nRF5182
  • Firmware: 0.7.0
• Android nRF Toolbox version 1.18.4

Possible defect in heartratemonitor example sketch (as of git commit 0c841d49, but sketch was last touched f248eec9).

In short, try the nRF Connect app if the nRF Toolbox app doesn't work.

As expected:

The Bluefruit shows up under AVAILABLE DEVICES: as Bluefruit HRM, followed by the MAC address.

Not expected:

Attempting to connect fails, and the nRF toolbox gives a notification:

The device does not have required services.

Short-term solution

However, using the nRF Connect app instead does allow me to connect, and it does show the appropriate output for Body Sensor Location and an updating output for Heart Rate Measurement.

Just getting started in this, so I'm not sure whether the problem connecting to nRF Toolbox is due to incomplete information on the Bluefruit side or to a bug on the nRF Toolbox side.

Hi! I noticed several problems when using the library. I will sometimes see the library getting into infinite loops and also loosing packets. It took me a while, but I realized what the problems are (I'll also post on the Adafruit forums soon). I forked and fixed them with minimal changes in https://github.com/corbinstreehouse/Adafruit_BluefruitLE_nRF51, I also have re-write branch that does it better.

Conceptually, here are the issues:

1. Adafruit_BluefruitLE_SPI::getResponse has this while loop: while ( digitalRead(m_irq_pin) && m_rx_fifo.remaining() >= SDEP_MAX_PACKETSIZE )

The problem here is the irq pin might still be left pulled, but data isn't available..this causes problems in getPacket, where it reads the header based on it not reading SPI_IGNORED_BYTE. However, it will eventually get a non-ignored byte from the last packet, and the code:

while ( p_header->msg_type != SDEP_MSGTYPE_RESPONSE && p_header->msg_type != SDEP_MSGTYPE_ERROR )
{
  p_header->msg_type = spixfer(0xff);
}

will skip over bytes loosing data. This is the cause of packet loss.

1. getPacket needs to be rewritten to do the IRQ assertion test at its start. However, I find that on a fast processor (teensy 3.1) it will still be asserted from the last packet. This causes the header to get SPI_OVERREAD_BYTE. If we get SPI_OVERREAD_BYTE , we should wait more on the m_irq_pin.

Anyways... I'll send you a pull request that fixes this.

Enhancement request:

This API is currently already close to Arduino's Stream as is: https://www.arduino.cc/en/Reference/Stream

If it fully implemented it, we could do fun stuff like plugging it into Firmata and have the uart service pipe data back and forth.

• Arduino board: Adafruit Feather 32u4 BlueFruitLE
• Arduino IDE version (found in Arduino -> About Arduino menu): 1.6.8
• Adafruit_BluefruitLE_nRF51 version: 1.9.1
• List the steps to reproduce the problem below (if possible attach a sketch or copy the sketch code in too):

I'm using the new callbacks to handle UART RX's and GATT writes, but I am also forwarding traffic between the BlueFruit and Serial so I can talk to the module directly for debugging. (while (ble.available()){Serial.write(ble.read()} and vice-versa). When I first got it running I was getting a constant stream of "OK"s from my reads. I tracked them down to being the responses to println( F("AT+EVENTSTATUS") ); in Adafruit_BLE::update line 284. I think line 285 should be waitForOK(); instead of readline(); so that update() consumes the full result of "AT+EVENTSTATUS". I made the change locally and it seems to work, I can interact with the BLE module without a any excess OK's appearing. It shouldn't require any other changes to the code since waitForOK() puts the data in this->buffer same as readline(). I guess it does cost another BLE_BUFSIZE+1 (49) bytes of ram though.

SDEP_MAX_PACKETSIZE should really be 20. That is because the BLE spec can send up to 20 bytes at a time. This means that to send a 20 byte packet over BLE with the SPI Friend BlueFruit will take two SPI data packet send/response pairs (since the value is 16):

#define SDEP_MAX_PACKETSIZE       16 // Maximum payload per packet

This is slow and too chatty.

Hello, I'm creating my own services and characteristics using the module's AT commands. Below is a printout from when I send "AT+GATTLIST" to the module. As you can see, I've created a service 0x6900, with one "read" characteristic with a value of "hello".

ID=01,UUID=0x6900
  ID=01,UUID=0x1110,PROPERTIES=0x02,MIN_LEN=1,MAX_LEN=20,VALUE=hello

However, when I connect to the module using the Light Blue app on iOS, the characteristic's value shows up as only the first letter "h". If I change the module's value to "world," then only "w" shows up on the app.

I do not think this is the app's error, because the UART examples work just fine. I am wondering if it has to do with the MAX_LEN property not being set properly?

The following code is creating the service and characteristic. Before running these lines, I run .factoryReset() and send an ""AT+GATTCLEAR". After the following lines, I then run .reset(). Both the module's firmware and Adafruit library are up to date, and it's being run on an Arduino Uno.

// first, create the service
String serviceString = "AT+GATTADDSERVICE=";
serviceString += "UUID=0x6900";

int serviceID = BLE_print_with_reply(serviceString, 200);

// second, create the characteristic
String charString = "AT+GATTADDCHAR=";
charString += "UUID=0x1110";
charString += ", PROPERTIES=0x02"; // read only
charString += ", MIN_LEN=1";
charString += ", MAX_LEN=20";
charString += ", VALUE=hello";

int charID = BLE_print_with_reply(charString, 200);

// below is a helper function to send dynamic strings to the module
// and return the integer value sent back

int BLE_print_with_reply(String msg, int delayTime) {
  delay(delayTime); // optional delay, because it seemed to help communication
  uint32_t reply = -1;
  ble.println(msg);
  ble.sendCommandWithIntReply(F(""), &reply);
  return reply;
}

This is a port of the neopixel sketch in existing in the nRF52 library

No files where modified, only the sketch example was added

I do not have a large selection of chips, so this was only tested on a: Adafruit Feather 32u4 Bluefruit LE connected to a Adafruit NeoPixel FeatherWing

There is a spot in the code for sending an image, but the Android app doesn't have support for it (or I just couldn't find it). Although, other then the bluetooth connection, very little was changed.

Circuit Playground Arduino IDE: 1.8.5

I have some issues with the code. When I connect my Circuit Playground to the BLE module and upload the sketch through my Mac everything looks fine. I am using the bluart_datamode sketch. I can both send and receive uart data, but when I connect the Circuit Playground to an external power resource or replug the Circuit Playground to my computer, I dont receive uart data anymore. It possible to connect to the BLE through the app, but the data dont appear.

`/********************************************************************* This is an example for our nRF51822 based Bluefruit LE modules

Pick one up today in the adafruit shop!

Adafruit invests time and resources providing this open source code, please support Adafruit and open-source hardware by purchasing products from Adafruit!

MIT license, check LICENSE for more information All text above, and the splash screen below must be included in any redistribution *********************************************************************/

#include <Arduino.h> #include <SPI.h> #include "Adafruit_BLE.h" #include "Adafruit_BluefruitLE_SPI.h" #include "Adafruit_BluefruitLE_UART.h"

#include "BluefruitConfig.h"

#if SOFTWARE_SERIAL_AVAILABLE #include <SoftwareSerial.h> #endif

/*========================================================================= APPLICATION SETTINGS

    FACTORYRESET_ENABLE    Perform a factory reset when running this sketch         Enabling this will put your Bluefruit LE module in a 'known good' state and clear any config data set in previous sketches or projects, so     running this at least once is a good idea.         When deploying your project, however, you will want to disable factory reset by setting this value to 0.  If you are making changes to your     Bluefruit LE device via AT commands, and those changes aren't persisting across resets, this is the reason why.  Factory reset will erase the non-volatile memory where config data is stored, setting it back to factory default values.             Some sketches that require you to bond to a central device (HID mouse, keyboard, etc.) won't work at all with this feature enabled since the factory reset will clear all of the bonding data stored on the chip, meaning the central device won't be able to reconnect. MINIMUM_FIRMWARE_VERSION Minimum firmware version to have some new features MODE_LED_BEHAVIOUR LED activity, valid options are "DISABLE" or "MODE" or "BLEUART" or "HWUART" or "SPI" or "MANUAL" -----------------------------------------------------------------------/ #define FACTORYRESET_ENABLE 1 #define MINIMUM_FIRMWARE_VERSION "0.6.6" #define MODE_LED_BEHAVIOUR "MODE" /=========================================================================*/

// Create the bluefruit object, either software serial...uncomment these lines /* SoftwareSerial bluefruitSS = SoftwareSerial(BLUEFRUIT_SWUART_TXD_PIN, BLUEFRUIT_SWUART_RXD_PIN);

Adafruit_BluefruitLE_UART ble(bluefruitSS, BLUEFRUIT_UART_MODE_PIN, BLUEFRUIT_UART_CTS_PIN, BLUEFRUIT_UART_RTS_PIN); */

/* ...or hardware serial, which does not need the RTS/CTS pins. Uncomment this line */ Adafruit_BluefruitLE_UART ble(BLUEFRUIT_HWSERIAL_NAME, BLUEFRUIT_UART_MODE_PIN);

/* ...hardware SPI, using SCK/MOSI/MISO hardware SPI pins and then user selected CS/IRQ/RST */ //xxcAdafruit_BluefruitLE_SPI ble(BLUEFRUIT_SPI_CS, BLUEFRUIT_SPI_IRQ, BLUEFRUIT_SPI_RST);

/* ...software SPI, using SCK/MOSI/MISO user-defined SPI pins and then user selected CS/IRQ/RST */ //Adafruit_BluefruitLE_SPI ble(BLUEFRUIT_SPI_SCK, BLUEFRUIT_SPI_MISO, // BLUEFRUIT_SPI_MOSI, BLUEFRUIT_SPI_CS, // BLUEFRUIT_SPI_IRQ, BLUEFRUIT_SPI_RST);

// A small helper void error(const __FlashStringHelper*err) { Serial.println(err); while (1); }

/************************************************************************/ /*! @brief Sets up the HW an the BLE module (this function is called automatically on startup) */ /************************************************************************/ void setup(void) { while (!Serial); // required for Flora & Micro delay(500);

Serial.begin(115200); Serial.println(F("Adafruit Bluefruit Command <-> Data Mode Example")); Serial.println(F("------------------------------------------------"));

/* Initialise the module */ Serial.print(F("Initialising the Bluefruit LE module: "));

if ( !ble.begin(VERBOSE_MODE) ) { error(F("Couldn't find Bluefruit, make sure it's in CoMmanD mode & check wiring?")); } Serial.println( F("OK!") );

if ( FACTORYRESET_ENABLE ) { /* Perform a factory reset to make sure everything is in a known state */ Serial.println(F("Performing a factory reset: ")); if ( ! ble.factoryReset() ){ error(F("Couldn't factory reset")); } }

/* Disable command echo from Bluefruit */ ble.echo(false);

Serial.println("Requesting Bluefruit info:"); /* Print Bluefruit information */ ble.info();

Serial.println(F("Please use Adafruit Bluefruit LE app to connect in UART mode")); Serial.println(F("Then Enter characters to send to Bluefruit")); Serial.println();

ble.verbose(false); // debug info is a little annoying after this point!

/* Wait for connection */ while (! ble.isConnected()) { delay(500); }

Serial.println(F("******************************"));

// LED Activity command is only supported from 0.6.6 if ( ble.isVersionAtLeast(MINIMUM_FIRMWARE_VERSION) ) { // Change Mode LED Activity Serial.println(F("Change LED activity to " MODE_LED_BEHAVIOUR)); ble.sendCommandCheckOK("AT+HWModeLED=" MODE_LED_BEHAVIOUR); }

// Set module to DATA mode Serial.println( F("Switching to DATA mode!") ); ble.setMode(BLUEFRUIT_MODE_DATA);

Serial.println(F("******************************")); }

/************************************************************************/ /*! @brief Constantly poll for new command or response data */ /************************************************************************/ void loop(void) { // Check for user input char n, inputs[BUFSIZE+1]; ble.print("test"); if (Serial.available()) { n = Serial.readBytes(inputs, BUFSIZE); inputs[n] = 0; // Send characters to Bluefruit Serial.print("Sending: "); Serial.println(inputs);

// Send input data to host via Bluefruit
ble.print(inputs);

}

// Echo received data while ( ble.available() ) { int c = ble.read();

Serial.print((char)c);

// Hex output too, helps w/debugging!
Serial.print(" [0x");
if (c <= 0xF) Serial.print(F("0"));
Serial.print(c, HEX);
Serial.print("] ");

} }`

I've been working on adding support for the Feather M0 Bluefruit LE to StandardFirmataBLE. While doing so, I discovered a few issues, which are addressed by this pull request. The changes here affect only the Adafruit_BluefruitLE_SPI class.

First, when alternating between reads and writes in DATA mode, it was possible to lose received data that hadn't yet been read. For example, I was testing a scenario where the Firmata client (a Mac desktop) sent 6 bytes to the Feather. After reading the first 3 bytes, the Firmata library wrote a response. However, because Adafruit_BluefruitLE_SPI::sendPacket always empties the RX FIFO when more_data is 0, the last 3 bytes were lost. I've changed it so that the FIFO is emptied only when not in DATA mode. Also, I modified Adafruit_BluefruitLE_SPI::setMode to empty the RX FIFO when entering DATA mode, so that a previous command response isn't interpreted as incoming UART data.

Second, I was nervous about Adafruit_BluefruitLE_SPI's simulated handling of the "+++" command. Since Firmata is a binary protocol, it's possible that that sequence of bytes could be sent to the client, which would then trigger an unexpected switch to command mode and break everything. To eliminate this possibility, I added a method to disable the simulated "+++" handling. It's still enabled by default, so the behavior of existing code won't change.

Whenever I try to verify or upload any code from the adafruit bluefruitLE nrf51 I get the error

C:\Program Files (x86)\Arduino\libraries\Adafruit_BluefruitLE_nRF51\Adafruit_BLE.cpp: In member function 'int Adafruit_BLE::readBLEUart(uint8_t*, int)': C:\Program Files (x86)\Arduino\libraries\Adafruit_BluefruitLE_nRF51\Adafruit_BLE.cpp:543: error: invalid conversion from 'uint8_t*' to 'char*' C:\Program Files (x86)\Arduino\libraries\Adafruit_BluefruitLE_nRF51\Adafruit_BLE.cpp:543: error: initializing argument 1 of 'size_t Stream::readBytes(char*, size_t)'

Is this error from my end or is there a coding error?

Running the atcommand example, I am using an otherwise unmodifiedBluefruitConfig.h, with settings for a MKRZero using hardware SPI. This means that the only change I had to make was:

#define BLUEFRUIT_SPI_CS               5
#define BLUEFRUIT_SPI_IRQ              3
#define BLUEFRUIT_SPI_RST              6    // Optional but recommended, set to -1 if unused

I did make one other change, however. I have a lot of memory to work with on this board and I'm not sure how often I'll be able to check for incoming messages - and I know that they'll be on the order of 32B and coming fast. So.... I set the buffer size (BUFSIZE) to 256.

With the buffer at 160, I can send AT commands just fine. Here's ATI:

-------------------------------------
Initialising the Bluefruit LE module: OK!
Performing a factory reset: 
AT+FACTORYRESET

<- OK
ATE=0

<- OK
Requesting Bluefruit info:
----------------
BLESPIFRIEND
nRF51822 QFACA00
4A01B079A608DD56
0.6.7
0.6.7
Sep 17 2015
S110 8.0.0, 0.2
----------------
AT > ATI

<- BLESPIFRIEND
nRF51822 QFACA00
4A01B079A608DD56
0.6.7
0.6.7
Sep 17 2015
S110 8.0.0, 0.2
OK
AT >

And here it is again with a buffer of 256:

-------------------------------------
Initialising the Bluefruit LE module: OK!
Performing a factory reset: 
AT+FACTORYRESET

<- OK
ATE=0

<- OK
Requesting Bluefruit info:
----------------
BLESPIFRIEND
nRF51822 QFACA00
4A01B079A608DD56
0.6.7
0.6.7
Sep 17 2015
S110 8.0.0, 0.2
----------------
AT > Y*

<- ERROR
AT > Y*

<- ERROR
AT > Y*
...
...
...
...

(With the errors coming in, nonstop, at maybe 100/sec?)

The buffer size is the only thing I have changed between the two examples. The working version is the default 160 and the broken one is 256. Given that the MKRZero has something like 32KB of memory, I'm not running out. Strangely, setting BUFSIZE to 300 works, as does 1000. If it needs to be divisible by a specific number, BluefruitConfig.h should note this.

• Arduino board: Mega 2560

• Arduino IDE version (found in Arduino -> About Arduino menu): PlatformIO - Visual Studio Code

• List the steps to reproduce the problem below (if possible attach a sketch or copy the sketch code in too): LIST REPRO STEPS BELOW

I have firmware version 0.6.7 on my BlueFruitLE. The callbacks in the MIDI example fails due the wrong FW version.

Putting this code prior to the callbacks would help for those debugging issues.

  if ( !ble.isVersionAtLeast(MINIMUM_FIRMWARE_VERSION) )
  {
    error( F("Callback requires at least 0.7.0") );
  }

void setup(void)
{

  //while (!Serial);
  delay(500);

  Serial.begin(115200);
  Serial.println(F("BT Remote"));
  Serial.println(F("---------------------------------------"));

  /* Initialise the module */
  Serial.print(F("Initialising the Bluefruit LE module: "));

  if (!ble.begin(VERBOSE_MODE))
  {
    error(F("Couldn't find Bluefruit, make sure it's in CoMmanD mode & check wiring?"));
  }
  Serial.println(F("OK!"));

   ble.println(F("AT+BLEGETADDR"));
   ble.waitForOK();
   Serial.print(F("Done."));
}

Whatever I try I cannot get the HWAddr from the Feather 32u4. I need either that or the serial number.

With ble.println(F("AT+BLEGETADDR")); or just ble.println ("AT+BLEGETADDR"); nothing is printed in the console.

How would one implement a pairing code or password for peers? I couldn't find anything about this in the docs.

Because anyone can connect to my device now blocking any further connections from my own devices. A simple 4 digit code like some other accessories require would solve this problem.

• Arduino board: Adafruit Bluefruit Feather 32u4 BLE
• Arduino IDE version (found in Arduino -> About Arduino menu): 1.8.6

Hi, I have tried two ways in order to get a value read from the Lipo:

1. With the official docs, simply as follows:

#define VBATPIN A9
float measuredvbat = analogRead(VBATPIN);
measuredvbat *= 2; // we divided by 2, so multiply back
measuredvbat *= 3.3; // Multiply by 3.3V, our reference voltage
measuredvbat /= 1024; // convert to voltage
Serial.print("VBat: " ); Serial.println(measuredvbat);

I have read VBatt: 0

2. I've executed the code supplied with battery.ino and I've got an ERROR displayed with the Serial

What could be happening?