I have been following setup instructions and searched youtube and this forum for similar problems. I have the flysky connected and configured and the ESC calibration comes after I get the wires in the right order so rotors 1-4 spin in the proper direction. I’ve got flashing green on the Pixhawk and blue on both power buttons. It does not say to arm the drone but I have tried that and it won’t arm.
The battery is a 3 cell 4200mAh one and it is fully charged to 12.7 V. It reads low on this screen. I have read I may need to calibrate to get rid of this error but my mission planner has no options under “optional hardware”. I did notice that it assumed a 4 cell battery and I tried to changing it to 3 but no luck.
I admit I am a noob to drones but very familiar with software and have built robots before.
I have seen this option show up in videos but when I click on mine there are no options under optional hardware. It perplexes me . I downloaded the software straight from the site.
You would too if you were connected to the Flight Controller. At some point you must have connected to something running firmware from 2019 (V3.6.12). This is ancient. There is no point in moving forward until you update the firmware to current Stable.
Thank you dkemxr! I was disconnected at that moment and I was indeed connected before. There are so many settings here that I find things falling through the cracks. I was able to get the motors to run tonight for brief bits. Not so long before the failsafe kicked in and told me my batter was dead (even though it still reads 12.6V). I was able to get the wiring right for the directions of the rotors this way, though not through the motor test page.
I seem to be having trouble getting any setting I change to be saved except on the full parameter page (which I am nervous about changing). I tried running mission planner as admin and it didn’t help. This has complicated my attempts at calibrating the battery which it claims is at 10 V but is at 12.6 or 12.7 V.
Even when I did change the battery setting on the full parameter page to 12.6V it didn’t seem to alter the problem of the window on the data page from reading 10.00V and claiming my battery was dead. Maybe I have the wrong setting or I am going about this calibration all wrong.
Thank you Dave, I have been hesitant to update the firmware because it came flashed and the instructions warned not to update it because it can lead to problems. I wanted to exhaust all options before doing that. I’ve been following a youtube guide on this. https://www.youtube.com/watch?v=oK4EXECxUlA&t=95s
Perhaps this is an indication I must go ahead and do it.
Sure you should. You will not get much help if you stay on V3.6 It’s a bad sign that someone is selling a Flight Controller with firmware that is 7yrs old.
Most YT videos are bullshit unless they are from an Ardupilot Developer. You can follow the Arducopter Wiki or you can use the Methodic Configurator. With your level of knowledge you should use the later. But, I see you have not clicked the link yet so the saga goes on…
Those generic 2.4.8 Flight Controllers have no standard but the “Pixhawk1” firmware is usually the best place to start when updating. You will be offered a choice so pick that one. The current Stable version today is V4.6.3, that’s what you want.
Power cycle the controller and restart Mission Planner. Leave the battery disconnected. After re-connection to USB in the connection pull-down do you see something like this?
