RE: Blend Micro Arduino Timeout problem

David Edwin — Sat, 20 Dec 2014 16:17:38 GMT

Thanks for posting the trace. The first event that you see E3 :3, 86, 3, 8, is interpreted as a DisConnected Event with the BTLE reason code as 0x08 which means timed out. See Section 24 for the Disconnected Event. Then you start the advertising and it looks as if the advertising is started sucessfully based on the command response event E3 :3, 84, F, 0, with SUCCESS as the result code. Then looking at the next event I see E3 :3, 86, 93, 0,, I see another Disconnected Event, but this has a reason code of 0x93 which means that there was no BTLE central that connected back to this device of the time the device was advertising. I would have liked a timestamp with each of the messages when they are printed out on the PC so I can be certain that the advertisement was done for the commanded time. However at this point I can see that the phone or application that you have is not re-connecting back and that is one of the issues.

Action: Ensure that your application re-connects when there is a link loss.

The other issue is to see why did you get a E3 :3, 86, 3, 8, in the first place. This can happen if there you have moved too far away from the phone or there is other noise on the air which resulted in a disconnect. It may be interesting to see the messages that happen before the first Disconnected Event was received along with timestamps for the Serial messages.