To feel your needs and for you to better understand the PIN code generation, we want to share with you a code exemple that is under development and will be released soon in SDK 2.5
The application is a weather station that display data on screen and send them over BLE by demonstrating PIN code generation during pairing/bond process.
Regards,
I downloaded the zip but can't find the weather station c source code inside the zip ?
Source code is located under weather_station\task4\boards\rapidiotk64f\demo_apps\task4\source.
Can you please explain what is asking for a PIN?
When your Android app doesn't recognize the Rapid iot it is still seen by others Android apps (parameters for example) but theses apps ask for a pin code. We tried unsuccessfully 0000 and 1234. Any idea what could be the right PIN code?
Hi Jean-Philippe,
We did not intend to use such pairing mode with our Out Of the Box application in conjonction with Rapid IoT studio. (PLay and Tinker phases of the experience).
The pin code you are looking for, is nevertheless generated (pseudo randomly) but not reported to user interface (nor used in our mobile app). This is because identification between phone and kit is done via EUI when using Rapid IoT Studio and via A1006 authentication chip into the kit.
You may have a use case where you want to develop your own (Android) application connecting to the kit via BLE using code developped from scratch. We are preparing code examples for which an API is called to get this code and displayed on the kit IoT.
Reading between lines, I understand you cannot (always) connect via BLE on some application generated by the Rapid IoT Studio.
Thanks
I confirm that we have been able to connect the app to the kit only one time in three days. We use a Wiko and a Kyocera. Later we intend to transmit from the kit to devices other than smartphones. What is the transmission protocol ? Will we need then the PIN code?
Hi Jean-Philippe,
We did not test specifically those phone models, but if this had worked once, there is no reason why it should stop working after one succesfull conection.
Often users are reporting connection issues because of the provisioning misuse. This is Worth a dedicated post - could be your case too.
In a nutshell:
Regarding devices other than smartphone:
Thank you for your answer.
We see the Rapid IoT with other BLE scanning app but not with NXP app and in the future we are not sure to use a smartphone to forward data to the cloud, we may use BLE/Wifi gateways (Raspberry Pi, Arduino...) therefore we will need to know the BLE transmission protocol.
For futher details on the BLE transmission protocol, please follow this link of the NXP knowledge-center. The Bluetooth® Low Energy Applications Developer’s Guide should be interting for you.
Also the Bluetooth Low Energy API reference manual
Regards
Théophile