grove-linux-driver VS urf_lib

https://www.seeedstudio.com looks pretty interesting to me because of the built in battery charge circuit.

A common source for Jetson is https://www.seeedstudio.com

I was sent a new XIAO BLE Sense device by https://www.seeedstudio.com/ so decided I would figure out how to manage communication. It was quite a project, since the Enhanced ShockBurst protocol has to be implemented in software. I have a few things to figure out, but the library is mostly functional, I'm looking for input on issues etc. and or improvements to make. It has been tested with the complete RF24 communication stack, although the RF24Network and higher libs need modifications to work with this library.

https://www.seeedstudio.com expensive compared to original, but not huge

Our friends at Seeed Studio send us some boards! We will work together to make them compatible with Luos technology and build great projects using Seeed Studio and Luos.

SeeedStudio

This post contains links to sample code that you can use with the FarmBeats for students kit, available from Seeed Studios.

Of significant stuff I wrote an nRF52 "core" (not Arduino core, it's for using with arm-gcc and makefiles) with necessary functions to feel comfortable there: https://github.com/ultimaterobotics/urf_lib - apart from simpler stuff like timers, uart, radio handlers and star protocol, I also made a custom implementation of BLE peripheral device (4.2-ish, hadn't implemented everything from 4.2, only parts I needed - that indeed was terribly complicated, if Nordic had their softdevice open sourced, I wouldn't do that). Since then I've added there fast ADC, PWM, SPI with DMA, persistent storage parts but those are not yet published.

You may want to check the library I made some time ago: https://github.com/ultimaterobotics/urf_lib (radio related stuff is in urf_radio.c, .h files)- I hadn't implemented there methods with external setting of length and packet ID (both are intended to be handled outside of the library) - but if something doesn't work as intended in your case, you can trace an example of sending from nRF52 to nRF24 here https://github.com/ultimaterobotics/uMyo_v2 , in file main.c preparation of the packet is handled with prepare_data_packet32(), which is later sent via a single call of rf_send(data_packet, data_packet[1])

I in fact wrote a library for nrf52 family that, among other things, handles my own RF protocol (https://github.com/ultimaterobotics/urf_lib although no documentation yet) - I'm using star architecture, one central node talking to multiple peripherals at close to realtime schedule - communication cycle time is <2 ms per connected device, variable payload up to 250 useful bytes, no in-built acks or retransmits. That's because I had the need for such pattern in multiple projects I worked on.