I would like to see some sort of watch dog timer on the ConnectDevice method. Sometimes when trying to connect to a device that is not there the ConnectDevice method can take a long time and this can slow down the program if your waiting for the method to finish before continuing with the program. It would be nice to set some attribute that will limit the amount of time spent in the ConnectDevice method. Would something like this be possible? great to hear that Bluetools development will continue - I was wondering already as there have been no updates for a long time. Here are my wishes / feedback. Provided in order of importance for me - from high to low: - Overall stability: Make Bluetools work as stable and reliable as possible for continuous running. With the current version I do see intermittend failures where exceptions are not thrown for discovery finished or sends get stuck. Stability is the most important for me - everything else is second. If that would require to drop support for Widcomm-Stack I would accept that, although I would prefer to see continued support for the Widcomm stack (eventually requiring a certain level of stack version) - Stability handling large (e.g. &gt;20) discovered devices and multiple sends simultaneous. We currently do see some issues with that, although I must say that those are also related to the stack used. Widcomm seems to reliably fail if trying to send &gt;64kb files with more than