KK 2.1 FCB to Hyperion 25A ESC issue.

I managed to get someone from Hyperion to contact me about this...finally they suggested this:
"connect only signal wires from the KK2 board to the receiver. Do not power the receiver via the KK2 board output.
Powerup the receiver separately with 5V supply i.e with a battery or BEC first. And then connect the 12V supply to the Quad.
Then try arming. This should solve your problem."​
Has anyone had to do this before, is this really the issue? If this really is a problem, wouldn't it be a common occurrence? I'll probably try this soon, when I have some time, but I'd rather not have to lug an extra battery / extra circuit around. Shout out if you've heard of this before, thanks.
 
Update! I got and connected up a naze32 board and patched through with Cleanflight. This allows for more diagnosis insight. Still having trouble getting ESCs to respond to signals through the naze32; same issue as before, different flight control board.

Anyone know which protocol a Hyperion Atlas ESC uses?

When I power the naze32 via USB (no main battery plugged-in) the ESCs beep warning tone, just quieter than when battery IS plugged-in.

Also, I notice receiver tab shows this with HK-T4A V2:
with trim at min. on throttle:
min=1042
max= 1693​
with trim at max on throttle:
min=1189
max=1840​
Was trying to do throttle calibration through naze32 with trim at min., though maybe the max value wasn't high enough to trigger calibration on ESCs. Will try doing this again using trim at max., though I am worried about keeping the min. signal at a value as high as 1189. I just think the max. should be as high as possible to try to trigger calibration through ESC.
To clarify: I did individually calibrate the ESCs using that trim value with basic setup: 1 ESC, battery, Rx throttle channel only. ESCs/Motors do respond and spin up after to corresponding throttle changes. Then in Cleanflight went to Receiver tab, noted min./max. values with that trim, then went to Configuration tab and adjusted the Cleanflight/Naze32 output for throttle to those receiver values. Went to motors tab and tried following procedure for throttle calibration through Cleanflight with all 4 ESCs connected and no acknowledgement from ESCs/motors yet. Thinking it's protocol mix-up at this point, then back to trying to solve the original problem. I've been grounded since idea of first build, with no real in-person help since early 2014 (hoping to meet up with someone soon to see). Any new ideas? Thanks, if you can.
 
So, I have found that you can adjust the signal interpreted by Cleanflight using the "set rxrange <channel_number> <min> <max>" on the CLI. This helped change my throttle signal through the naze32, as my radio setup is very minimal (cheap) and not adjustable on the front end.
Still cannot get the ESCs to calibrate through the control board...then I came across these discussions:http://forum.flitetest.com/showthre...emax-12a-blheli-esc-with-naze32-acro-rev-6-fc
http://forum.flitetest.com/showthre...emax-12a-blheli-esc-with-naze32-acro-rev-6-fc
The link above was about a person finding out the ESCs were awake (via USB power) before getting battery powered to initiate with a full-throttle signal to the ESCs...meaning they would never calibrate because they would see something besides max throttle when provided minimum power to the ESCs even though the battery wasn't plugged-in. I have noticed this on my build as well:
When plugging USB to the Naze32 to view info through Cleanflight the ESCs would emit the tone, though much quieter than if they are plugged into the battery. Confirmation that they are active before being able to even get to the motors tab in Cleanflight.
So, I thought...well I guess I need to re-route/interrupt power to these ESCs so I can get the proper signal out of the flight controller before I supply main power to the motors.

HOW TO DO THIS?

I have been given suggestions to make the ESCs on a separate BEC...I'm thinking to myself...hmm that seems excessive because I have 4 ESCs with Linear BEC circuits in them. A BEC for my BECs, I know right? Though I didn't seem to find a way around this safely. Of course that's the idea "safely". I ran across this post then:
http://fpvlab.com/forums/showthread.php?29139-Why-disconnect-redundant-power-from-esc-s-bec
I am thinking, well that's definitely a step forward...but it may be like stepping into hot lava on the safety side.

If I disconnect all the power leads going to my linear BECs is this dangerous at higher currents , or is it just so the ESC can get a better reference voltage to do it's job more accurately?
I spec.ed this build myself as a beginner...it is very possible that my calculations may have been fudged to proceed, but I am not ready to start any fires. Advice? Do other people use a BEC for the BEC ESCs? Thanks if you can. Would love to finally fly this, I feel like I'm getting so close to the real issue and this discussion would help many beginners.
 
PROBLEM NEVER SOLVED, getting new ESCs. I have confused local hobbyshop build experts with this issue and the manufacturer doesn't even know why it doesn't work, but they said not to waste time on it anymore. Thanks for the help.
 
You must log in or register to reply here.
Back
Top