Hi, just been testing my Y6 with it's new 6000mah 4S pack and noticed the motors are getting hot. This is affecting the bottom motors more where if you touch them on the base, non rotating part, they are too hot to touch for more than a few seconds. The rest of the motor is hot but can be held without issue.
To check I did another flight with a 3S 4400mah setup and the motors were again getting hot, not as hot but the flight time was 5 mins vs 13 mins.
It's also worth noting with the 4S setup the ESCs were also getting hot, again after a 13 min test flight.
The flight itself basically consisted of a 13 minute hover in loiter mode, I was testing battery times, and consumed 5000mah. The weather for the UK was hot, 25 deg C. The Y6 is a new 2014 B version weighing 1900 grams or so, std config plus 600 gram pack, with std 10 inch props and 850 blue motors.
And finally to the question, is this normal of does something sound wrong?
The only thing I can think I haven't done is balance the props, guide for this would be handy, but I have no vibration issues looking at the data log.
Replies
I ended up cutting all ESC positive wires leaving the PM for main power and UBEC as clean backup power, so they say.
Also, the 3DR ESC's are now installed. Ha! All six motors spin and no commutation issues. Altitude Hobbies will take back the Maytechs. Why I couldn't get six good ones to work with my new configuration is puzzling; have heard Maytech ESC's are good quality.
Now to double check everything, button it up, then if we get a decent day this weekend hopefully a test flight.
Also, after the experience with GPS glitching causing major problems earlier this year, I'm really interested in getting that new GPS unit that is supposed to pick up several more satellites and lock on faster/better. A Neo 8m ??? I can't find the info the company sent to me.
BTW Doug, I installed 3.2 per Randy's "invite". Is there anything I should know to watch out fo
@DG
I ordered and am awaiting the NEO-M8N to test out. I'm hoping that the triple band antenna will provide me more satelites and less HDOPs.
As for 3.2, are you coming from 3.1.5? If so, I would suggest you wipe your Pixhawk and perform a fresh install and complete recalibration. I've been running the release candidates since v3.2 rc5 and out of a abundance of caution, wiped and installed refresh each time. It's my understanding that you may not have to do that if already using a ealier release of 3.2 but why chance it.
I think you will like the new features and functions. Oh and on a seperate note... Don't fret the lack of vertical climb speed in most modes other than Stabilized. The code is designed to damped the vertical climb rate to mitigate Z axis vibrations which could cause instability issues while climbing. You can adjust it int he Full parameter section, just would recommend it until you've flight tested all modes and understand the plus and minuses.
Also downloaded the latest Mission Planner MSI file from 3DR and uninstall the older Mission Planner before instaling this one. Some folks are confused in the Mission Planner because they are not using the latest version or in this case the BETA version.
Is this the same unit? What if any accessories/cable should I get with it (see bottom)?
http://witespyquad.gostorego.com/mini-ublox-m8n-gps-w-35x35mm-mount...
@Haygood,
This (UBLOX NEO-M8N GPS, GLONASS, Galileo, BeiDou, QZSS and SBAS receiver...) and (See Christians comment on pg47 of "ArduCopter-3.2 beta testing" Blog) are a couple writeups I could located. It's possible that the version is so new that there hasn't been many evaluations. I know I plan to evaluate and post my findings.
@DG,
It states that cables come with it. I'm going out on a limb to say that the compass will plug into IC2 expansion buss or on Pixhawk using a DF13 4-pin and the GPS will use a DF13 6-pin for it to connect to the GPS port on Pixhawk.
If you are unsure which one to select on whitespy, I would recommend contacting them before you order it.
Does anyone have a link to a good write-up of what's involved in using the NEO-M8N? I'm not finding much concrete beyond specs on it.
Two test flights with the Sunnysky 690kv motors has shown promise. For one, no more motors overheating! I've attached pics of a few log analysis printouts, the BIN file and a URL to share the video of the Y6B in hover testing.
http://youtu.be/Ds2i1POnPME
- upper image is motors 1,3, & 5
- lower image is motors 2,4, & 6
2014-11-09 15-20-26.bin
Doug,
congratulations to succesful flight. What is the weight of your Y6b during this flight? It seems to be quite heavy because it takes nearly 38 Amp @ hover.
Hi All,
Rebuild of my Y6B is complete and initial flight test were a bit rough as I need to take it up and perform a Autotune.
The good news is I was able to increase flight time by 8% and the motors I ran in a hover never showed any heating issues.
Tomorrow I plan to video it in flight and I will post my logs for all to review.
The Y6B is running Sunnysky 690kv motors with 12 x 3.8 CF propellers.
Will post more tomorrow after flight tests.
I received my new props yesterday and slapped them on. I took Hubertus Paetow’s suggestion and installed APC Thin Electric 11 x 4.5ep for upper (850kv) motors and 12 x 8e for the lower (690kv) motors.
Took it for a flight today and everything went well until an unexpected roll to the left while in Loiter mode and subsequent crash approximately 4 minutes into my flight. See attached “.bin” log. At this point I do not know what caused the crash but it wasn’t from the props. So I have to figure out what caused it to roll over.
On a separate note: log analysis shows that the combination of props lowered my over PWM on lower motors from 1675 PWM down to 1550 PWM. This is significant in that at no time did the motors hit max PWM while in Loitering as it did when I ran 10x47 upper and 11x47 lower motors. So I’m pleased to see a power and performance improvements.
On a seperate note, the upper motors were a little warmer than normal and this is probably due to going with a bit large propeller and the lower motors were ambient in temperature.
Now to figure out why the crash.
2014-10-12 14-02-23.bin
-
8
-
9
-
10
-
11
-
12
of 23 Next