I am working on a project where a BLE113-256k is a BLE collector and a BLE113 is a BLE thermometer.
My goal is to obtain a temperature sample every 500 ms, and I've almost reached it. But after obtaining several samples, the BLE thermometer disconnects. I am using connect direct command (BGAPI by UART host control), hence I am not bonding both devices.
My question is, shall I just change my SW to reconnect after disconnection, or I should try to bond and use connect selective? Does the bonding guarantee a more reliable connection?
I will appreciate any helpful comments,
Bonding is not likely to improve the connection reliability in this case. Reconnecting after an unexpected disconnection is not a bad recovery mechanism, but there must be some other issue at play causing it in the first place. What is the "result" code that is generated in the connection_disconnected event handler? This should help tell you what the potential cause for the disconnection is.
Thanks for answering so quick, I have been working on it, but still I have some issues.
The point is that, when the BLE Slave disconnects my code is not reading UART RX because is the time that the master BLE would be sleeping. So I don't catch the disconnect event if it occurs.
1)I am wondering if there is any way to debug the BLE Slave attached to the DKBLE V1.0 without using the BGScript, as I would like to keep using the UART demo example (which works perfectly).
2) Is there any comand to request the BLE Slave to repeat old events to occur again?
3) To solve the undesired disconnection (I realize it with the BLE GUI and BLE 112 dongle), I try to reconnect with Connect Direct. But the connection is never restablished, until I reset the BLE master and I start the overall process.
Thanks for your help,