ahh, sorry, I got the timestamps wrong. The set of TECS_LAND_THR was after the watchdog (at 1:44:18 in my timezone). The watchdog was at 1:41:43.
Yup, same situation today. we are at number 3…
I’ve ordered a production MatekH743 for testing. I only have a pre-production board which doesn’t have the same baro setup (so can’t run our releases).
I was wondering why the hwdef doesn’t mention the DPS310 baro (which I believe is what the board is equipped with), and no backend code exists for this baro?
it uses the DPS280 driver, which works the same as the DPS310
I’ve now received my production H743-Wing, and I’ve set it in a loop loading missions to try to reproduce the issue.
Meanwhile, I am still interested in getting more logs showing this issue. I have one so far that points at the storage code, but more logs may help me narrow it down if I can’t reproduce it myself.
Which issue are you talking about exactly? The WDT reboot or the FC hanging on startup?
I am interested in both. There are a few things we need to determine:
- are these issues only on specific boards, or on all boards (ie. why can’t I reproduce?)
- is it related to peripherals connected? Or related to history of writes to flash storage?
As you seem to be able to reproduce, can you try to strip back to the smallest set of attached cables that can reproduce the issue. Ideally just USB, nothing else connected. The idea is to make it easier for me to try and reproduce.
Note that the two issues may be one issue. For example, if it is getting a hard fault and it sometimes happens during startup and sometimes after startup then it would explain both issues. We don’t enable the watchdog timer until after startup completes, so a fault during startup will cause the startup symptoms you describe.
If we can’t find a way to transfer the issue to me to I can reproduce it then I may need to ask you to send the board to either myself or @sampson to look at. In that case I’d be happy to pay for a new board for you.
If you can find a way to reproduce then I’d also like to know if it happens on our latest builds from ArduPilot firmware : /Plane/latest/MatekH743
@tridge when it happened on my board and the last time it did it just fell for about 3 meters, I solved the issue by saving params to sdcard. it’s been fine now since the summer, no issues. I’ll try and find the logs.
Don’t know if it’s any help but thought i would let you know. It’s a custom h743 board.
As the problem occurs randomly, I can not reproduce it whenever I want. The only thing I can say for shure is, that after it hangs up, it does not boot unless I reset it using another firmware (copter instead of plane)
I can try the following:
- Flash the latest dev firmware (it also occured with 4.1.0dev from mid november, something like the 14th)
- Enable logging during disarmed state
- Unplug everything but USB and SD and let it run for a few days (occasionally replugging and rebooting, hoping that the issue is captuerd on dataflash and telemetry logs.
Anything to add/to do differently? as the isse happend about 2 weeks apart each time, it does not do so very frequently…
So, reproduced once again:
- Latest Firmware, disarmed logging enabled, no devices connected (only sd and USB)
- Running for about a day (Log file 2.4GB)
- no abnormal msgs on missionplanners messages tab- USB unplugged
- USB replugged, no connection possible (mission planner error)
- USB replugged agian, still no connection possible. Melody and Green LED hanging.
- connected OLED, USB replugged, OLED reads INIT in the top line forever
Logfiles:
https://168.119.233.154/nextcloud/index.php/s/3ToQbDGC2f5mbyK
https://168.119.233.154/nextcloud/index.php/s/K64PGffnPq69MED
https://168.119.233.154/nextcloud/index.php/s/aXaBeeH8stE7BDN
Similar problem with Matek H743-WING
- changed telemetry hardware form SIK to ESP8266
- forgot to change the baudrate for SERIAL3
- connected USB, while rover still powerd by battery
- changed telemetry baudrate im Mission Planner, saved
- made a preflight reboot, rover still powered by battery and USB
- rover is now in watchdog reboot loop
- disconnect battery and USB power
- rover hangs on boot
- can’t flash rover over mission planner. Had to flash the hex+bl with betaflight configurator
But I’m not sure, if the board has a problem.
ICM20602 AccelY gets an offset of about -400 after a while, but movement seems to be detected.I deactivated IMU0 for now. The remaining MPU6000 is good enough for a rover.
Matek H743 slim, last Arduplane from master.
Exactly same problem.
Connected Matek m8q CAN, DJI Airunit, arspeed sensor connected to m8q can.
Matek H743 Mini with the latest Fw, has happened today on the field (already once before with the latest stable). Plugged in the battery, 2x 3 beep startup noise, but then the last 2 ESC beeps were missing. MAVLink and SLCAN are showing up in the device manager but no connection is possible with Mission Planner. The TX doesn’t show any telemetry data too.
@Simon_Exner is going to send me his board so I have a board that can reproduce the problem. I wasn’t able to reproduce on my board
1 Like
Bonjour, avant toutes choses, je vous félicite pour votre travail et votre dévouement sur ce site. Je suis actuellement sur un 1er projet d’un avion VTOL, et j’ai acheté un FC “Matek H743” . J’ai plusieurs problèmes avec ce FC, et en particuliers : Connexion impossible avec Mission Planner . Mais faibles compétences, m’empêche de vous aider, mais je suivrai avec grand intérêt vos échanges techniques. Cordialement.
Do you think this is related to the H7 FRAM fix you did in master?
I have at least two data-points that indicate this is fixed by https://github.com/ArduPilot/ardupilot/pull/16434
Thank you for the confirmation.
The board from Simon has now arrived!
Similar problem with Matek H743-WING. With version 4.09 stable.
After a few successful flights, the FC no longer boots. It is also no longer found on the PC via USB. Has to burn the firmware again. This is the third time this happens.