Hi,

thanks for you reply!
I understand that the Bluetooth chip is not 100% reliable, and that RobotC cannot fix that. However, there is definitely something in my program that is very likely to trigger a bug, and I would like to find it...

I no longer have a fixed timeout of 100 ms: I fixed that, as explained here. The only timeouts I still have are...

• 1 second for Bluetooth to finish actions, and
• 1 second for the confirmation to arrive.

The first timeout has never been hit (I play soundException if it happens), and the second timeout only controls weather the user sees "OK" or "no reponse". Confirmations that arrive after the timeout are automatically purged ("old ACK deleted"), so the timeout should not influence the actual communication in any way.

More ideas?

Thanks,
- Felix