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.