If you want to purchace a Naze32 we have them available in our store!
This information can be applied to any kind of race quad setup.
If you are building a VersaCopter, you can continue straight through the rest of the build with this video.
LINKS
Anyone have the PID settings for a 3-cell setup using the NAZE32 and power pack from FT? Admittedly, I don't know a lot about PID settings. Looking to get a close approximation until I learn to tune it myself. Thanks!
Yeah, I spent some time trying to get BLHeli Suite to cooperate last night. And I did find which file to use once I realized they were SiLabs and not ATMEL ESCs. But for the life of me I could not get the 12A ESCs from Power Pack E to connect to the software. I plugged them in and powered them up as directed but got nothing but errors. I read somewhere that those ESCs (at least the older ones, mine are from July) don't have a boot loader on them at all? Could that be my issue?
Anyone? I am very interested in this as well. I have a 3-cell setup, not 4.
How are people fitting there naze 32 boards in.
Im running a rev 6 acro naze32 and not having luck with oneshot either. After reading jhitesma's post above, i believe i received the older blhelis with the power E pack. I'll skip the saga ive had with my rev 6 naze32 trying to calibrate the escs(see my post in the electric multirotors section if interested)...but i ticked the checkbox to enable oneshot in baseflight and didnt really notice any difference. Then after looking at another sellers site at the Luminier oneshot esc's, i read you should also tick the enable fast pwm box for those esc's. So i did and now my emax esc's make a new short set of beeps on power up and wont respond to any inputs. Tx or baseflight inputs do nothing. So I've given up on enabling oneshot on these esc's and plan to buy some Lumenier esc's in the future.
Dont get me wrong, i really like the emax escs i purchased from Flitetest and plan to keep flying them in my Versacopter till i get some Lumeniers. Then use them in other smaller builds
Thanks jhitesma. I really appreciate and learned alot from your post. Didnt know the simon series were the old ones and mine came labled as blheli so i got the newer ones. Sweet.
[/quote]My esc's definitely needed to be calibrated. The motors would all start spinning at different throttle openings and at one point one would not stop spinning when the throttle was fully closed. After calibrating they all start spinning at the same throttle opening and my quad definitely responds better to throttle level changes in flight.
jhitesma;238196 The idea of "calibrating" ESC's individually by hooking them to a RX really is silly on a multirotor. The reason is a lot of people forget that the signal from the RX means squat to the ESC on a multi. It's the signal from the FC. And since that's setup in firmware it doesn't matter what the range is from your TX/RX the signal range is instead controlled by the min/max values programmed into the FC. So if you really MUST calibrate ESC's on a multi it really should be done through the FC and not by hooking ESC's up to your RX. However - you raise another good point. And that's the confusion caused by the term "oneshot" which is really two separate things. It's important to remember that "oneshot" was originally developed as "oneshot125" which is a far more accurate name since "oneshot" and "125" are the two things that make up the difference between traditional ESC signals and "oneshot" signals. SimonK (and TimeCop once he finally accepted this into Baseflight) use the terms "SyncPWM" and "FastPWM" which are somewhat more descriptive. The first part "SyncPWM" or "oneshot" is a change in the firmware of the flight controller and not an actual change in the ESC firmware. It syncs the PWM output to the main control loop of the FC rather than running it as it's own loop which can result in the two loops getting out of sync and introducing latency. (that's a really dumbed down description to save space/time - I've explained it in more detail in a few past posts that search should turn up.) Basically though SyncPWM/Oneshot means that your FC is updating the signal to the ESC as soon as it gets new data from the gyro instead of waiting on another loop to complete which can cause the gyro data to go stale. The second part "FastPWM" or "125" is that instead of using a 1000-2000 microsecond (microsecond (one millionth of a second) is abbreviated as "us" online because the real abbreviation "μs" is kind of hard to type :D) range for the PWM signal to the ESC instead that is divided by 8 to get a 125-250 us range. This basically means you can send up to 8 updates in the time it used to take to send 1 update resulting in faster updates sent to the ESC. [/QUOTE said:You are right, i can't agree with you anymore www.coquegsm.com