-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
This is my working note.
A lot of example of 'micro:bit BLE sample' defines
const UART_TX_CHARACTERISTIC_UUID = "6e400002-b5a3-f393-e0a9-e50e24dcca9e";
const UART_RX_CHARACTERISTIC_UUID = "6e400003-b5a3-f393-e0a9-e50e24dcca9e";and micropad defines same.
But in Nordic UART document, there is a document as belows.
in this document, peer means micro:bit.
RX Characteristic (UUID: 6E400002-B5A3-F393-E0A9-E50E24DCCA9E)
The peer can send data to the device by writing to the RX Characteristic
TX Characteristic (UUID: 6E400003-B5A3-F393-E0A9-E50E24DCCA9E)
If the peer has enabled notifications for the TX Characteristic, the application can send data to the peer as notifications.
Why TX and RX is reversed?
Metadata
Metadata
Assignees
Labels
No labels