Example of documentation issues: 4.5 V pad, how much current can it supply? Which one will bring down the board if overloaded, 4.5 V or 5 V supply line? Speedybee is much more explicit.
Those topics are from the PX4 forum and one is very specifically for PX4.
I literally just plugged a Matek H7 board into my computer, installed QGC, and it connected automatically. I then downloaded a log file of several MB using both QGC and Mission Planner without issue.
Your criticism is without merit.
Strange. I can not make it connect to QCG. On MP, MP detects two Serial ports, and it connects, but with QCG, I can select only one port, and that gives me an error when I try to connect. In a minut I will chekc the error to post it here.
I get Could not create Port. Access Denied
MP shows two ports, in my case 28 and 29 anc I connect to 29
When I try to edit comm settings in QCG, only 28 appears as available, and when trying to connect, I get that error.
See this post by @Eosbandi regarding com port numbering. This has nothing to do with ArduPilot or Matek and everything to do with how the host PC detected the boardās ports. The fix is outlined there.
OK. I will check it, but the point is Speedybee connected out of the box to both, QCG and MP. With Matek, I figured out immediately how to connect to MP, but not with QCG.
In the end, no matter how good hardware is, if it is not working properly, then maybe an inferior, but more stable board is a better choice?
Now, believe me, I am not going back to Speedybee, because of the LUA scripts, I have several projects in my head (like directional antenna on the copter side, which is extremely easy to imlement with LUA), so F405 defintively is out of quesiton for me.
But for practicing ACRO mode in 5 inch copter I would stick with Speedybee. I really was fed up with having to extracting the memory card with tweezersā¦
Oh, and the SD card holder of the Matek is very narrow and much more difficult to insert the card than the longer holder of Speedybee, by the way.
Given the exceptionally large quantity of issues raised here about Speedybee hardware, I have a hard time accepting that conclusion.
I had only one issue with Speedybee, it was the ADC pinout of Airspeed and RSSI, and my feeling is that there is some problem with Ardupilot, because at the very beginning I have setup INAV, and RSSI was working. After I switched to Ardupilot I was not able to make it work, and I tried to find the problem, in vain (spent 3 hours, tried all the other pins in the AP setup, and I suspect that the HW definition is wrong).
There was a report that RSSI and Airspeed are swapped, but I think that the problem goes deeper.
And I still do not know why MP does not allow to download well log files (bigger log files, 50 ā¦200 MB) from Matek but does so from Speedybee. I thought that the MP bug was resolved, but it seems only partially.
Iām not seeing that. Downloaded logs from Matek boards today with MP.
Why did this make itās way into this thread?
Thanks Yuri! I was able to download 700 MB in 20 minutes through QCG now. Last time I tried to download a 160 MB file through MP, it took 1.5 hours to tell me that MP is stuck!
Try updating MP to latest beta as well.
I did 3 days ago, same thing. 1382 build 1.3.9169.6147
Small files and ftp for scripts work fine.
Speedybee sadly does not make H7 flight controllers yet and i donāt know when they will, sadly theyāre not very receptive to consumer feedback. What are some recommended ābang for your buckā H743 flight controllers in the same range?
Boards from Matek or Holybro (Kakuteās). TBS has a new board that looks interesting. Full featured and the price is right.
None of these are $35 boards so donāt bother if that is your price point.
As someone who made the choice to get a lot of these same hardware for my first build and introduction into the realm of FPV/Quad Copters etc and autopilot software. This has taught me quite a lot about tuning, constructing and matching the correct hardware to start from scratch. If you are serious about going beyond FPV racing/freestyle this kit is the go to. Cheap replacement parts and you will continually break stuff while gaining a ton of knowledge and understanding. I have a spare pixhawk for 5 years that i never even used yet, the original one has taken so many hits and crashes and still ticking. The wiki for Ardupilot is only understood after watching tons of YouTube videos and reading over and over each time seeing things you missed. Beginners need that frustration to really decide if this is something for them to continue with or not. Rather than get top notch equipment you donāt understand the basics of their operation and even worst damaging property or even endangering life. Pixhawk 2.4.8 is still fully supported and operates very well. What I suggest however, is you stay away from EOL equipment thatās no longer supported. That said, Ardupilot 4.0.7 is a rock solid release that you can stick with to understand and learn. The mission should be knowledge before glory.
Begginers donāt need frustration. They need clear guidance to achieve best tune. Task which is made significantly harder if they use poor quality, obsolete or counterfeit components.
If you can get a genuine one or at least one compliant with the original electrical documentation, clone manufacturers are known to omit components of the power system and use subpar sensors. Then it is an acceptable choice if you get appropriate cables as it uses different connectors and you understand limitations of F411 based flight controllers.
Ardupilot 4.0.7 is almost 5 years old, there where a lot of changes since then including PID, IO and Failsafe reworks that increased performance and safety. The documentation provided in Mission Planner and other GCS are geared for up to date firmware meaning that descriptions of parameters may be inaccurate or cover features unavailable for old firmware. Using 5 years old firmware version is setting yourself for worse outcome from the beginning.
For most users the mission is to get a well flying craft. Using outdated, subpar or counterfeit components, firmware or software has significant negative affect on the desired outcome compromising safety and performance. Increasing likelihood of accidents.