MKW36 CONNECT the third ble APP

zhangxiwe — Wed, 17 Feb 2021 02:44:40 GMT

We now use NXP kinetisBLE ToolBox_6.app to connect and communicate with our devices, but using our own APP communication will prompt you to start connecting as shown in the figure-& gt; connection success-" connection disconnected, I don't know why? My device uses the same UUID ： as kinetisBleToolBox : uuid_service_wireless_uart, 0xE0, 0x1C, 0x4B, 0x5E, 0x1E, 0xEB, 0xA1, 0x5C, 0xEE, 0xF4, 0x5E, 0xBA, 0x00, 0x01, 0xFF, 0x01

DEBUG mes

Thank you!

Re: MKW36 CONNECT the third ble APP

Sebastian_Del_Rio — Thu, 25 Feb 2021 23:04:31 GMT

Hi Zhang, I hope you're doing well!

Could you please confirm if the correct custom wireless UART UUID is successfully added to your other device?

If that is correctly added, then the disconnection routine can be removed from the Wireless UART, however, this is not recommended, as it helps in disconnecting if the characteristic is not being properly recognized on the connected device.

The disconnection from the device is triggered when the service discovery for the wireless uart service fails. The function called is:

(void)Gap_Disconnect(peerDeviceId);

In the mAppServiceDisc_c event of the BleApp_StateMachineHandler function in the wireless_uart.c source file.

Please let me know if you need any more information.

Best regards,

Sebastian

topic Re: MKW36 CONNECT the third ble APP in Wireless MCU

MKW36 CONNECT the third ble APP

Re: MKW36 CONNECT the third ble APP