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
When I run gSDK, I am unable to read parameters and obtain motor control functionality on my Zio gimbal.
I have confirmed that all firmware on the Zio is upgraded (running Gremsy Zio payload Firmware v780 Official, and SOM firmware v2.0.1). I am running gSDK on a jetson running Ubuntu 20.04.
I am directly connecting the Jetson to the gimbal control cable over USB/UART. Camera powers on and zeroes just fine.
Here is a condensed version of the output I am receiving:
OPEN PORT
Connected to /dev/ttyUSB0 with 115200 baud, 8 data bits, no parity, 1 stop bit (8N1)
START READ THREAD
Found
GOT GIMBAL SYSTEM ID: 1
START WRITE THREAD
GIMBAL_STATE_NOT_PRESENT
Request param read: VERSION_X
Request param read: VERSION_Y
Request param read: VERSION_Z
Request param read: PITCH_P
Request param read: ROLL_P
.
.
.
Gimbal parameter VERSION_X timed out
Gimbal parameter VERSION_Y timed out
Gimbal parameter VERSION_Z timed out
Gimbal parameter PITCH_P timed out
Gimbal parameter: ROLL_P timed out
.
.
.
READ SOME MESSAGES
Got message gimbal status
Gimbal's status is OFF!
Got message RAW IMU.
raw imu: time: 0, xacc:6016, yacc:-19148, zacc:-21846
.
.
.
FW Version: 0.0.0.OFFICIAL
DO NOT SUPPORT FUNCTIONS, Please check the firmware version
The text was updated successfully, but these errors were encountered:
Hello,
When I run gSDK, I am unable to read parameters and obtain motor control functionality on my Zio gimbal.
I have confirmed that all firmware on the Zio is upgraded (running Gremsy Zio payload Firmware v780 Official, and SOM firmware v2.0.1). I am running gSDK on a jetson running Ubuntu 20.04.
I am directly connecting the Jetson to the gimbal control cable over USB/UART. Camera powers on and zeroes just fine.
Here is a condensed version of the output I am receiving:
The text was updated successfully, but these errors were encountered: