betaflight-configurator-android icon indicating copy to clipboard operation
betaflight-configurator-android copied to clipboard

No device found when connecting by OTG cable

Open weixingsun opened this issue 7 years ago • 4 comments

Hi, I got an error msg "No device found!" when doing the first try on my FC of OmnibusF3. I can get everything works properly in SpeedyBee, which I downloaded from googleplay. Would you please tell me what can I do to fix this problem? Thanks

weixingsun avatar Jul 09 '18 13:07 weixingsun

My current thought is to write a chrome.serial plugin and use the https://github.com/felHR85/UsbSerial library for Android

The 'No device found' would be due to the current USB library not finding a suitable device, you could try specifying vid and pid in the requestPermissions() call of merges/android/js/serial.js

For example:

requestPermissions: function(success, error) {
		serial.requestPermission({vid: '1d50', pid: '607d'}, success, function(message) {
				// Fallback to default serial ports
				serial.requestPermission(success, error);
		});
},

Reference: https://github.com/xseignard/cordovarduino#your-device-is-not-yet-known

cmengler avatar Jul 10 '18 02:07 cmengler

Thanks for your quick reply, I had fixed this issue by using {vid:'483', pid:'5740'} for my F3 controller, but I don't know if this ID pair break your FC, do you think any way to make an id_pair table for compatibility ?

weixingsun avatar Jul 10 '18 11:07 weixingsun

Good point, I'm not sure if specifying the VID/PID will cause it to break for other USB devices -- I'll take a further look into the source to determine if that's the case.

Otherwise, the alternative will be to fork the Cordova USB serial plugin and add 483/5740 to the device list.

cmengler avatar Jul 12 '18 02:07 cmengler