RAK5010 NB-IoT Tracker

Posted on
of 3
First Prev
/ 3
  • @Gordon but I am now having an issue where I am getting BLE error 0x6 and BLE error 0x8 with setScan() ? This is the same code I am running fine on nrf52832 hardware. Any thoughts ?

  • Ok. Recent commit should have fixed that - Nordic made some big changes to advertising in their SDK15

  • Looks like it's working!
    Tried to merge Nordic's long-range demo with Espruino, but no luck. Any chance of getting BLE long-range in Espruino? Would be great :)

  • Honestly, right now I'll settle with just having an nRF52840 port working reliably. It looks like adding support for long range advertisements via setScan is pretty easy, but I'm unsure about connections themselves.

    If/when there's a nRF52840-based Espruino I imagine things will improve pretty quickly, but right now it's hard to justify much development time on.

  • :( but totally understandable. Thanks!

  • Excellent news, I have loaded the latest hex and my app is running. The only thing I am noticing at the moment is that I am getting occasional UART_OVERFLOW errors with serial to the BG96 and so commands are getting corrupted

  • That's interesting - thanks! That's a tricky one. Is it more prevalent than on the nRF52832 RAK trackers? The UART code should be identical I believe.

    Perhaps it would be possible to tell the BG96 to operate at a lower baud rate?

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview

RAK5010 NB-IoT Tracker

Posted by Avatar for peruperu @peruperu