Naze32 (rev6) via Cleanflight to Hyperion Atlas ESC communication issue

Sflemdog

Member
Hello, all. I originally posted with issues on my first build (never flew) and the problem seems to have changed quite a bit...it's an interesting progression if you'd like to follow it, check my other post. BUT the progress has lead to setup changes that would constitute a new posting creation, here it is:

I have a naze32, rev6...apparently I got one of the early ones that didn't have a diode on the power circuit of the board from the USB source. After soldering in-line a schottky diode from my power distribution board's 5V regulator to the ESC rail on the naze32 rev6, I then went to do the ESC calibration via the motors tab in Cleanflight without the battery connected yet. I slid the master up to max (2000) and plugged the battery in. No noise from ESCs/motors. I've tried to improve the setup thinking it was a power distribution issue, but now I cannot seem to get these ESCs to calibrate through the naze32 (had similar issue with KK board before). These are Hyperion Atlas 25A LBEC ESCs. I don't have any of the BECs power (red) wires connected to the ESC rail on the naze32 anymore as they seemed to produce much more needed heat than I wanted...plus, like I said, my power distribution board has a 5V source built in, so I just connect it to the 6th ESC spot on my naze32 for powering later.

To confirm, these ESCs calibrate and spin up the motors when connected to basic setup of: battery, Rx(with signal from Tx), ESC, and motor. All of them do just fine with the basic setup, individually.

Has anyone used Hyperion Atlas ESCs with the naze32? Is there something particular they are looking for to initiate the calibration sequence? I have a very cheap radio with 4 channel outputs, reverse switches, and manual trims...no screen, not fancy at all. I had to use the CLI to adjust the throttle output in Cleanflight so it reads 1000 and 2000 at min stick and max stick respectively. Is there something I'm missing? Please don't suggest for me to go buy something to fix the issue...it makes no sense for me to upgrade my setup if it's never flown...it has to be possible for me to get this setup in the air before I even consider upgrading again. Please check signature for build info (build #1.5). Thanks if you have any ideas.Quadcopter wiring diagram2.jpg
 
You cannot calibrate esc's through a naze32 it has no blheli passthrough. You will have to buy an ftdi or Ardluino & do em 1 by 1.apparently the rev5 has but not rev6. F1 Boards are no longer supported by cleanflight or betaflight. So the next update will not fit on the chips on F1 boards.
 
Oh you will need a 6 channel radio.
Aileron
Elevon
Throttle
Yaw
Arm switch
Mode switch
Although the arm can be done by sticks
You will Deffo need 5 channels at least.
 
I have a naze32, rev6...apparently I got one of the early ones that didn't have a diode on the power circuit of the board from the USB source. After soldering in-line a schottky diode from my power distribution board's 5V regulator to the ESC rail on the naze32 rev6,
A USB source will output 5.00+/- 0.25V.

After soldering in-line a schottky diode from my power distribution board's 5V regulator to the ESC rail on the naze32 rev6,
That doesn't make sense, the diode will drop the PDB's 5V by about .7V. So basically you're effectively at ~4.3V. Going by your diagram the Naze is powering your RX, from HK's listing.

https://hobbyking.com/media/file/463814362X160989X33.txt
Operating Voltage: 5V - 7.4V
Oh you will need a 6 channel radio.
Although the arm can be done by sticks
You will Deffo need 5 channels at least
Although that makes sense, in Cleanflight isn't the default mode Acro? The OP just wants to fly, he can always go into CF and choose one of the leveling modes, he just won't be able to change modes with his TX.
 
You cannot calibrate esc's through a naze32 it has no blheli passthrough. You will have to buy an ftdi or Ardluino & do em 1 by 1.apparently the rev5 has but not rev6. F1 Boards are no longer supported by cleanflight or betaflight. So the next update will not fit on the chips on F1 boards.

Really? I see all over the internet about people using the motors tab to do this? Maybe there's a misunderstanding about what I mean. If you use the motors tab without the battery plugged in (idea is ESCs aren't booted yet), you can get the board to output max pulse width signal, then plug in the battery with that signal going to the ESCs. When they boot, they see that max signal and should go into throttle calibration. Does this make sense?

Oh you will need a 6 channel radio. ...
I really just want to attempt to have the entire build run, for now...I don't need any of the other features usually connected to the auxiliary switches for now. I can attempt acro. and take it slowly from there. I can arm, and other things, using sticks.

That doesn't make sense, the diode will drop the PDB's 5V by about .7V. So basically you're effectively at ~4.3V. Going by your diagram the Naze is powering your RX, from HK's listing.
The naze is powering my RX, but I think you might be thinking the diode is going backwards...unless I drew it in the diagram incorrectly, sorry. The diagram should show the setup without the USB power supplied, and with the battery connected. Imagine during the calibration process...This should all be right, except when I went to power with just USB (not battery yet) and no diode, the naze32 was actually routing power from the USB to the PDB and then to the ESCs...I am glad nothing got damaged by this, but somehow the ESCs were actually booted and beeping on just the backwards power from the USB (if I had gotten the motors spinning without realize what was happening, could have actually done damage to my pc). Hence the need for the diode:
See this post.
 
Sorry I got myself mixed up a bit. Early hours here. Was just thinking the rev6 didn't have the passthrough for reflashing. Still a stoopid one though.
But I think acro mode is the only default mode available, if you don't pick any in the tab. Best to go with acro from the start like I didn't.
 
I went to local hobby shop to consult expert builder, he was surprised to find the FCs were not communicating properly with a basic PWM communication ESC.
I was even told by Hyperion tech not to waste my time on this anymore, after about a month of back-and-forth. Not sure why STILL, but my recommendation is that, if you happen to get your hands on some Hyperion Atlas ESCs, do not use them with flight control boards as they do not operate well with the interruption in signal. Maybe they work find for airplane setups, but not for multi-rotors. Thanks all.
p.s. Ordered an Emax Bullet BLHeli 30A OPTO ESC to try with my setup before buying 3 more.
 
Back
Top