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.
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.
