AQ arms but ESC32 using CAN remains unarmed

[DUKE40]

OK, I will try updating the FW on the ESC, will be tricky as they are now build into the Quad.
Concerning the DIMU It should be 1.1, at least it says AQ9 DIMU 1.1, got it from Jussi a few weeks ago.

[LPR]

Duke

When I connected my ESC32 the first time using CAN I had one of the motors not start. I checked the connections to the DIMU's CAN output and found that one of the connection was wrong. After switching the CAN wires all the motors worked.

Larry

[DUKE40]

Hi,

I now performed several tests to try to isolate the cause of the issue, and found it, all my wiring was correct.
But one of the ESC32 seems to have some problem, it is the one with CANID 2, as long as I do not connect it to the CAN bus all other are correctly recognized and can be armed without any problem, but as soon as I connect the ESC with CANID 2, none is recognized anymore. Very strange, even when it is connected alone it is not recognized.
I have connected it to QGC and did not found anything strange, settings can be read without problem, it can be armed through QGC without any issue, so I now have to further drill down what is wrong on that ESC.

I will check if I can flash all of them easily to the newest FW.

[DUKE40]

Hi,

I have now flashed all 4 ESC32 to R57, but the issue with one of them remains, this is what I get when it is not connected to the CAN bus:
(MAV 106) ADC init
(MAV 106) ADC task started
(MAV 106) Supervisor task started
(MAV 106) DIMU: EEprom init
(MAV 106) DIMU: Reading values from EEprom
(MAV 106) DIMU: read calibration parameters from EEPROM
(MAV 106) Battery cells: 3
(MAV 106) Radio init
(MAV 106) GrHott on RC port 0
(MAV 106) GPS init
(MAV 106) Nav init
(MAV 106) Command interface init
(MAV 106) CAN: Found 3 node type ESC
(MAV 106) Motors init
(MAV 106) Radio task started
(MAV 106) GPS task task started
(MAV 106) ESC32: CAN ID: 1, ver: 2.1.0
(MAV 106) ESC32: CAN updated 1 param(s) in flash
(MAV 106) Motors: cannot find CAN id [2]
(MAV 106) ESC32: CAN ID: 3, ver: 2.1.0
(MAV 106) ESC32: CAN ID: 4, ver: 2.1.0
(MAV 106) Control init
(MAV 106) Control task started
(MAV 106) Gimbal init
(MAV 106) Gimbal PITCH stabilization port initialized.
(MAV 106) Gimbal ROLL stabilization port initialized.
(MAV 106) Gimbal TILT control port initialized.
(MAV 106) Gimbal radio PASSTHROUGH port initialized.
(MAV 106) HoTT Telemetry init
(MAV 106) HoTT enable ESC32 monitor
(MAV 106) AQ S/N: 36373532-33314716-00320038
(MAV 106) Mavlink SYS ID: 106
(MAV 106) SYS Clock: 168 MHz
(MAV 106) 8615/8984 heap used/high water
(MAV 106) 32648 of 40960 CCM heap used
(MAV 106) Run task started
(MAV 106) AQ FW ver: 7.0 - EXPR rev416 b1794, HW ver: 6 rev1
(MAV 106) Disarmed
(MAV 106) HoTT Telemetry task started
(MAV 106) Initialization complete, READY.
(MAV 106) GPS: trying new baud rate
(MAV 106) RTC set: 2014-09-11 18:58:07 UTC


And that is what I get when it is connected:
(MAV 106) ADC init
(MAV 106) ADC task started
(MAV 106) Supervisor task started
(MAV 106) DIMU: EEprom init
(MAV 106) DIMU: Reading values from EEprom
(MAV 106) DIMU: read calibration parameters from EEPROM
(MAV 106) Battery cells: 3
(MAV 106) Radio init
(MAV 106) GrHott on RC port 0
(MAV 106) GPS init
(MAV 106) Nav init
(MAV 106) Command interface init
(MAV 106) Motors init
(MAV 106) Radio task started
(MAV 106) GPS task task started
(MAV 106) Motors: cannot find CAN id [1]
(MAV 106) Motors: cannot find CAN id [2]
(MAV 106) Motors: cannot find CAN id [3]
(MAV 106) Motors: cannot find CAN id [4]
(MAV 106) Control init
(MAV 106) Control task started
(MAV 106) Gimbal init
(MAV 106) Gimbal PITCH stabilization port initialized.
(MAV 106) Gimbal ROLL stabilization port initialized.
(MAV 106) Gimbal TILT control port initialized.
(MAV 106) Gimbal radio PASSTHROUGH port initialized.
(MAV 106) HoTT Telemetry init
(MAV 106) AQ S/N: 36373532-33314716-00320038
(MAV 106) Mavlink SYS ID: 106
(MAV 106) SYS Clock: 168 MHz
(MAV 106) 8615/8615 heap used/high water
(MAV 106) 32648 of 40960 CCM heap used
(MAV 106) Run task started
(MAV 106) AQ FW ver: 7.0 - EXPR rev416 b1794, HW ver: 6 rev1
(MAV 106) Disarmed
(MAV 106) HoTT Telemetry task started
(MAV 106) Initialization complete, READY.
(MAV 106) GPS: trying new baud rate
(MAV 106) RTC set: 2014-09-11 19:00:31 UTC

so it looks like something is wrong with this ESC, but I have no clue what it might be.
Anybody an idea what I should check, if there is anything I could check with simple means.
Would like to get my Quad airborne in latest 2 weeks.

[Jdmagoo]

Good work in tracking it down, maybe check the solder around the CAN Transceivers and capacitors. If anything i would re tin these with flux to be sure. The next step maybe replacing the CAN transceiver if you have one spare, but only guessing here

[chschmid]

[LPR]

Duke

You can set the motor mix so that the one ESC32 that is not working is controlled with PWM while the others are controlled with CAN. If the ESC32 works in PWM mode then my guess is that the small CAN chip should be replaced. I find it's not hard to remove the chip and solder a new one on. A replacement ESC32 would be easier but less interesting.

Larry.

[chschmid]

[DUKE40]

Soldering a new CAN chip is no option for my soldering skills
This would surely result in en even worth situation.
I will check then with Flyduino where I got the ESC from what can be done.

[DUKE40]

I did not want to have three ESC connected through CAN and one Through PWM, this would have made the wiring a bit more complex than expected.
I contacted FlyDuino where I had purchased the ESCs and we agreed for a replacement.
So by beginning / mid of next week I hope to be able to get the copter airborne for the first time.