Servers by jDrones

Gremsy T3 pixhawk cube

(Aaron Gruenberg) #1

Anybody running this gimbal? Does mavlink actually work? I’m assuming i still need control, so aux outs, or possibly SBUS out? Its marketed as canlink, it isn’t. supposed to run mavlink, so far, no. My tarot t3diii ran fine off aux 1 and 2. i may have to try more aux ports, and a PWM encoder to the gimbal. but this is very much not as advertised…

(James Pattison) #2

@HUY_PHAM is the Gremsy guy and might be able to help.
I’ve been intending to follow up on the canbus implementation so perhaps he can update us all on that too.

(Aaron Gruenberg) #3

The cable that gremsy calls the pixhawk can cable is a serial connection. Not canbus at all. they say it works over mavlink, but all ive gotten it to read is sbus. No success from searching either. I just got SBUS out almost working on my hex carrier board, but only with the servo pins loose, if i push it down, i lose signal. Suspecting a weak solder, i’ll inspect and reflow it tomorrow. This gimbal was marketed to work, and i had FAR more success with alexmos, tarot, and storm32. feel like i wasted 1500$…

Follow up, SBUS out works great. But only after you press the magic button.

(proficnc) #4

it works great over mavlink serial, but you need to put the right firmware on the gremsy
Their Facebook page has a lot of knowledgeable people on it

(Aaron Gruenberg) #5

Confirmed via gremsy, mavlink control only partially functioning. Pan, tilt and roll control only. Since mode switch isn’t supported, other control input is required. Got SBUS out running, and full gimbal control.

But now the bird doesn’t fly.
After getting the gimbal running, on the maiden, she played turtle. Immediate flip right. Motor order went crazy.

No wiring was changed. Parameters all set for octa x. Motor out going to correct servos, Etc.

Motors are wired as documentation says.

Clockwise from front right, (motor 1).

1,3,8,4,2,6,7,5.

Motor test should occur clockwise from motor 1.

Motor test is clockwise from motor 1.

A,E,F,C,G,B,D,H.

So motors 1 and 5 are correct. The rest is craziness. I tried to wire to match the motor test, and got some form of flight. Throttle control, pitch, and roll control, but no yaw. I can hear motors spooling up, but absolutely no yaw control.

So full collection if issues currently.

Windows 10 laptop can’t flash board anymore. But can communicate through mission planner, and motor order issue.

Going to reset my laptop. I think it’s a windows side problem. I’m hopeful that a bad flash is caching somewhere.

Any other ideas?

(Norimbo) #6

Do you have working “horizon drift correction” when Gremsy T3 is connected via com 2 to telemetry port of Cube Black? I know that I have to set SERIAL_BAUD to 115 and SERIAL_PROTOCOL to 2 . What about SR parameters like SRx_POS SRx_ADSB SRx_RAW_SENS ? They will be set automatically ?

(Aaron Gruenberg) #7

I never got mavlink working. I just use sbus out. I don’t see the point of running mavlink until its complete. After swapping out some bad hardware, everything is functioning.

(Norimbo) #8

I don’t need to control gimbal by pixhawk. I just need horizon correction from pixhawk.

(Norimbo) #9

I get from Gremsy such short manual. Bu there is no info about more settings…

Gimbal connect to Pixhawk_V2.pdf (590.9 KB)