I’ve written a BLE scanner and have noticed that increasing setScanTimeout only helps “capture” more distinct devices to a point. For example a setting of 6000 captures on average 8 while a setting of 12000 captures on average 6. The devices in question advertise every few seconds and only produce 1 SERVICE_DATA record for one service UUID. The devices are stationary. My particle boron is stationary. My deviceOS is 2.0.1. Other than trial and error is there a better way to know the ideal scan timeout setting?
Thanks,
Tim
Hi Tim- Since this is specific to the number and kind of devices you’re scanning for and a number of other unknowns,trial and error is the best option. Good luck!
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.