Camera trigger and manual tilt pass-through?

[Max]

Also have you used that M port before? Could it just be a bad connection? Maybe try a different port (disable a motor to free a timer...)?

-Max

[hogster]

Hi Max,

Thanks for your quick reply.

I was connecting via Bluetooth but I've now repeated the test using a direct link and it produced the following on reboot – I don't know why it was different?

(CORTEX AQ) ADC init
(CORTEX AQ) ADC task started
(CORTEX AQ) Supervisor task started
(CORTEX AQ) filer: created new session [22]
(CORTEX AQ) DIMU: read calibration parameters from EEPROM
(CORTEX AQ) Battery cells: 6
(CORTEX AQ) Radio init
(CORTEX AQ) Futaba on RC port 0
(CORTEX AQ) GPS init
(CORTEX AQ) Nav init
(CORTEX AQ) Command interface init
(CORTEX AQ) Motors init
(CORTEX AQ) Control init
(CORTEX AQ) Control task started
(CORTEX AQ) Gimbal init
(CORTEX AQ) Gimbal TRIGGER control port initialized.
(CORTEX AQ) Gimbal radio PASSTHROUGH port initialized.
(CORTEX AQ) AQ S/N: 36373532-33314716-002E0032
(CORTEX AQ) Mavlink SYS ID: 206
(CORTEX AQ) SYS Clock: 168 MHz
(CORTEX AQ) 8336/8336 heap used/high water
(CORTEX AQ) Disarmed
(CORTEX AQ) Initialization complete, READY.

I've also attached a dump of the Parameters.

Many thanks again

David

PS. I will try another port to see if it's just 13 that's behaving badly.

[hogster]

Ok after some fiddling around changing the gimbal output between different ports ... it's now working on port 13, exactly as it should do! *shrugs*

Thanks for being so quick to offer your help Max – perhaps it was your good aura on the other end of the forum that fixed it for me!

Onwards and upwards!

David

[Max]

Yea sometimes over slower radio links messages coming in quick succession can get lost somewhere in the ether.

Cool, good to hear it's working! Maybe a loose solder on one of the pins? I didn't see anything wrong in the params you posted. But sure, I'll let my aura take some of the credit...

-Max

[kinderkram]

Dr. Max, do you offer faith healing now?

David, check your wiring and connectors. You dont want to be botherd by unexpected fail safe events, right.
If something "suddenly" works it might fail again all of a sudden.

[hogster]

Yes that's a good point kinderkram, it could have been a loose connection, although I'm pointing my finger of suspicion at software at the moment ... but then I'm a hardware engineer so it's always the software that's at fault

David