[Jhinta]

I have it all compiled without any error but it will not connect mij revo
is this a ubuntu 16.10 error ? cant even connect when running sudo

Code: [Select]

.........
link a3867 hasn't been detected!
MainWindow::createWorkspaces - creating workspace "HITL" took 201 ms
MainWindow::createWorkspaces - creating workspace "Firmware" took 219 ms
MainWindow::createWorkspaces - creating workspaces took 2173 ms
# devices  1
# devices  2
# devices  3
# devices  4
main - main took 3520 ms
findDevice: cannot find  "Revolution"  in device list

lsusb

Code: [Select]

Bus 002 Device 010: ID 20a0:415e Clay Logic
dmesg

Code: [Select]

[ 5826.943908] usb 2-3: USB disconnect, device number 13
[ 5827.398864] usb 2-3: new full-speed USB device number 14 using xhci_hcd
[ 5827.539899] usb 2-3: New USB device found, idVendor=20a0, idProduct=415e
[ 5827.539901] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 5827.539903] usb 2-3: Product: Revolution
[ 5827.539904] usb 2-3: Manufacturer: openpilot.org
[ 5827.539905] usb 2-3: SerialNumber: 200023001251353231323535+FW
[ 5827.540444] cdc_acm 2-3:1.0: ttyACM0: USB ACM device
[ 5827.541549] input: openpilot.org Revolution as /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3:1.2/0003:20A0:415E.000B/input/input20
[ 5827.541699] hid-generic 0003:20A0:415E.000B: input,hiddev0,hidraw1: USB HID v1.10 Joystick [openpilot.org Revolution] on usb-0000:00:14.0-3/input2

[f5soh]

Try a 'git pull' and rebuild gcs

[Jhinta]

Try a 'git pull' and rebuild gcs

working again tnx

[Jhinta]

Try a 'git pull' and rebuild gcs

could it be that windows is also affected?

Windows build will fail because of libhogweed-4-2.dll, as i understand copy.data.pro needs to be corrected  to -4.dll,
as msys2 only provides that version. then it will fully compile ,, but when opening it doesnt connect(as in it sees the hardware it shows it connected but only one green tx bar)

will full clean rebuild to make sure, ( or is libhogweed-4-2.dll installed by somthing other then nettle?)

[f5soh]

Maybe, was not tested under Windows.

Generally the "one Tx bar" comes from drivers to unload / reload:
https://librepilot.atlassian.net/wiki/display/LPDOC/Troubleshooting

[Jhinta]

Maybe, was not tested under Windows.

Generally the "one Tx bar" comes from drivers to unload / reload:
https://librepilot.atlassian.net/wiki/display/LPDOC/Troubleshooting

  tnx