Improve Linux serial port detection about cleanflight-configurator HOT 7 CLOSED

Which board? Which serial port? What else did you have connected? Did you try with nothing other than Bluetooth connected?

I had noticed something similar a few weeks ago when testing multiple serial ports with MSP on my CC3D.

from cleanflight-configurator.

Tested on Flip32+ and CC3D, both UART1 (Serial port & MainPort).

Only GPS, PPM_RX (D4F-II) and motors connected.

Will try w/o GPS and report back.

Verzonden met Windows Mail

Van: Dominic Clifton
Verzonden: ‎zaterdag‎ ‎11‎ ‎oktober‎ ‎2014 ‎19‎:‎58
Aan: cleanflight/cleanflight-configurator
CC: Ruben Raadsheer

Which board? Which serial port? What else did you have connected? Did you try with nothing other than Bluetooth connected?

I had noticed something similar a few weeks ago when testing multiple serial ports with MSP on my CC3D.

—
Reply to this email directly or view it on GitHub.

from cleanflight-configurator.

Same here with bluetooth, but it isn't detected.
I have a paired serial bluetooth.
I run:
$ sudo rfcomm connect 0
Connected /dev/rfcomm0 to 00:14:01:23:24:32 on channel 1
Press CTRL-C for hangup

I can use minicom to open the port /dev/rfcomm0, but there is not detected and there is no option to put it by hand on cleanflight configurator.

from cleanflight-configurator.

Sorry I use linux. I inspect chrome.bluetooth, but when I declare bluetooth: {} on manifest.json, bluetooth is not supported on linux.
So I tried to hardcode the device /dev/rfcomm0 on the code to treat it as a serial port. Now I can connect cleanflight-configurator to cleanflight via the bluetooth serial adapter.
Specifically I added the /dev/rfcomm0 on serial.js and it worked.

getDevices: function (callback) {
    chrome.serial.getDevices(function (devices_array) {
        var devices = [];
        devices.push('/dev/rfcomm0');
        devices_array.forEach(function (device) {
            devices.push(device.path);
        });

        callback(devices);
    });
},

Of course, this is not a fix. It would be usefull to add text area so a user can add a device that is not returned by chrome.serial.getDevices.

Thanks,
Sebastián

from cleanflight-configurator.

@sguarin What distro are you using? I use Arch Linux and cleanflight configurator detects rfcomm0 just fine on 2 machines. Auto connect even works without issue (over days if I leave it on and forget) when I run the following code:

$ sudo sh -c 'while true; do rfcomm connect rfcomm0 20:14:08:27:11:89 ; sleep 2; done'

I've noticed the data is sometimes bursty (especially when in GPS pass through mode). Perhaps it has to do with congested 2.4 GHz spectrum, but other bluetooth devices (A2DP for example) work fine in the same environment.

from cleanflight-configurator.

@sguarin any chance you can create a pull request to allow the user to specify a device?

from cleanflight-configurator.

@sguarin manual port selection is done, see latest development branch.

from cleanflight-configurator.