You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm connecting the gimbal to port COM2 and I'm using a usb to serial cable for my computer.
I enabled the MAVLINK control using the gTuneDesktop v1.4.5 app, my gimbal show the next in windows:
When trying the SDK in linux, I always have the problem of Lost Connection!, the port in linux is /dev/ttyUSB0:
~/gSDK/build$ ./gSDK -d /dev/ttyUSB0
OPEN PORT
Connected to /dev/ttyUSB0 with 115200 baud, 8 data bits, no parity, 1 stop bit (8N1)
START READ THREAD
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
Lost Connection!
I tried all above firmwares and not luck...
What to do?
The text was updated successfully, but these errors were encountered:
One thing you could double check is that your TX / RX lines are correct. I had an issue with a drone-code standard uart cable (6-pin) between my pixhawk4 and the gimbal until I realized the TX/RX lines were reversed on the gimbal side. I've come to expect peripherals to just plug in and work, so this one caught me off guard.
Do you have to use the UART interface of the Gremsy with a FTDI cable? Can the gSDK work using the Gremsy's usb connection?
(I'm thinking not, since I'm getting the "Lost Connection" message when I attempt to connect to /dev/USB0. There is a serial entry under /dev/serial/id so it seems that Ubuntu is recognizing it as a serial connection.)
Hi!
Using gremsy T3v3, testing firmwares:
I'm connecting the gimbal to port COM2 and I'm using a usb to serial cable for my computer.
I enabled the MAVLINK control using the gTuneDesktop v1.4.5 app, my gimbal show the next in windows:
When trying the SDK in linux, I always have the problem of
Lost Connection!
, the port in linux is/dev/ttyUSB0
:I tried all above firmwares and not luck...
What to do?
The text was updated successfully, but these errors were encountered: