Closed Burzo closed 10 months ago
@Burzo I have tagged Charles here and shared the Gdrive with his reports/docs, maybe they have the BLE requirements?
I think one of my documents links to the definition of the Nordic UART Service (NUS). This includes the 128 bit UUIDs for their Service and Characteristics.
My personal approach would be to start with these, so our app begins by looking out for devices advertising the NUS.
Then when comfortable, change the UUIDs to something else in both the device and the app. This could either by changing say one byte of the NUS UUIDs, or creating entirely new random 128 bit value for the Service. Then the Characteristic UUID would be the same as the Service UUID except for one byte ( follow the pattern used by the NUS UUIDs).
Assuming you start withe the Nordic NUS example for the nRF52832 development board, I think the binary for that is provided in the SDK so no compilation is needed.
When you change the UUIDs you will have to find the file that defines these and make a replacement then recompile and reprogram the board.
However this will not be easy for the WW120. For that reason I would advise sticking with the NUS UUIDs for as long as possible.
Closing this since we're continuing discussion in https://github.com/wildlifeai/wildlife-watcher-mobile-app/issues/10.
I require the service and the characteristics UUID and any other additional information that may be needed to establish a stable connection with the BLE chip.
@victor-wildlife This is something that will need to be provided by Charles, but I can't seem to tag him in the project.