KK 2.1 FCB to Hyperion 25A ESC issue.

S

Sflemdog

Member
Howdy, (see build info in my signature, please)
Problem:
ESCs indicate ( through motors ) a constant 2 warning beep, which by the Hyperion manual should mean there is "no signal from receiver on start-up". Also, when I "arm" the Flight Control Board (FCB) to take flight, motors continue to do the constant 2 beep or are unresponsive in one case ( directly after doing throttle range setting through FCB, see later discussion * ).
(P.S.A.= I did all of this with props OFF and can still count to 10 with my hands ;) )
Background info on build / what I have already gone through:
I am a little new to this hobby, so if I am rambling about things that should seem obvious, I apologize...just want to confirm I have all things properly connected so as to resolve the issue.
Connections: I have all ESCs connected to battery, then power through serial connectors from all 4 ESCs to my FCB (in Motor Control ports 1-4). I have heard of issues with connecting power from all ESCs to FCB, but I have already tried procedures with just one motor connected (still beeps) and have read that the KK 2.1 board only takes power from motor-control port 1 when set to quadcopter mode. Then I have the receiver channel 1, with all 3 serial wires connected to the FCB and have one of the 3-wire serial connectors going to just the signal end of channels 2-4 to the FCB.
I have already bound receiver and transmitter properly with confirmation by way of receiver test screen on FCB. Also, have set trims on transmitter by way the same screen on the FCB (had to reverse throttle by way of switch on transmitter). All components on FCB "check-out" by way of FCB screen self-evaluations.
Procedures executed to zero-in on the problem:
  • Not the ESCs/wiring/motor: If eliminating the FCB from the system, by connecting the ESC straight into the receiver's throttle channel, then I can run the throttle-range-setting procedure on the ESC/motor. I did this for all 4 of the ESCs/motors, all successfully performed.
  • Not connection between receiver and FCB: If I have all 4 ESCs/motors connected to power and serial to FCB, I can power up and hold the 1 & 4 buttons on FCB to do a throttle-range-setting procedure on all 4 ESCs/motors at that same time. The ESCs indicate that this procedure is successful as well. In fact, if I continued to hold down the 1 & 4 buttons on the FCB to keep it passing the throttle signal through, I could (after setting the range and getting confirmation it was set) change the throttle and get appropriate response from all 4 motors at the same time. But, when releasing fingers from buttons 1 & 4, beep would return even when in armed mode (confirming throttle was indeed set to zero).
*I got to thinking, maybe it was falling into a fail-safe mode when having an interruption of signal...possible from power up to "safe" screen on FCB to "armed" mode. I did throttle-range-setting the same as before, but after getting a throttle response, went to zero throttle, release buttons 1&4 tried to arm the FCB as fast as possible. The result was even more mysterious as the beeping ceased while armed. When all seemed alright, in the silence, when throttling up there was no response from the motors.​
I am wondering if maybe there is an odd issue with communication between the FCB and the ESCs when going to fly. Please let me know if I have over-looked something very obvious about maybe communication speed between the two. I know it's a lot to read, but I feel it takes away the game where the first few posts back-and-forth about what the problem is actually. Thanks for reading. I hope you all can help.
 
Last edited:
Sooty from hobby king forums suggested to reprogram ESCs, said that if all beeping is not synchronized, FC will think they are not programmed. I will try that and post results.
 
So, I reset the ESCs (all 4) with the programming card they come with. I then reset all of them to values I knew were the same (which were defaults anyway). I re-did the ESC throttle-range setting through the FC board. All went well. I tried to arm very quickly again to keep from too much of a signal interruption between the FC board and the ESCs, this time (didn't happen before). Motor 1 output responded to Tx movements as if it were flying; speed variation with stick movements besides throttle. BUT, it was only motor 1. Motors 2,3 and 4 were silent. I unplugged power, replugged power and tried to arm quickly; constant 3 tone beeping occurs same as last time, though, now confirmed to be beeping in unison.
 
I ruled out it being a faulty FC (flight control) board, as I ordered another one and the same problem persisted. I have been looking into it being something related to power distribution. These ESCs (Electronic Speed Controller) seem to fall into a fail safe mode when they don't get a response from the Rx (receiver). Though there is much discussion about this elsewhere, I am not sure personally. I can say that the way I am distributing power may be an issue, unless someone knows that it is okay. Here's how it goes: I have one 3S battery connected (split) to all 4 ESCs...then the FC is powered through the smaller signal leads from ESCs, then the Rx is powered through the FC. If you know of any issues, please comment. Thanks. (problem unresolved)
 
Hi. I was wondering if you resolved this issue. I am having the exact same problem with my KK2.1 board and Hyperion Atlas ESCs. I am at the point where I feel like buying a different set of ESCs would be the best thing to do.
 
HI guys in the transmitter what is the throttle set to some times the esc needs to see a neg value to arm , also is transmitter set up as an aero
Also make sure there is no duel rates active
 
I have tried arming the ESC through the board with the transmitters minimum throttle at 0% and at -100%. Does not make a difference, the ESC will still continuously beep the minuet I arm then unarm the KK2.1. The ESCs still don't respond to the KK2.1s inputs unless its in throttle pass through mode. Dual and exponential rates are disabled on my transmitter as well. Transmitter is set up as a simple airplane.

The ESCs respond fine when they are plugged directly into the receivers throttle channel. I set the max and min throttle positions and then they are good to go. They arm every time this way when I turn everything on. They refuse to arm however when connected to the KK2.1. They only work in the throttle pass through mode of the board which is exclusively used for ESC calibration (press and hold buttons 1 and 4 to enter this mode. Mode is exited the second you release those buttons).

These Hyperion ESCs don't seem to like the signals that the KK2.1 gives them.
 
Hi mate is strange what firmware does the KK have , it may be worth a try and put on steveis1.8s1pro (not the 1.9 as this is for the acro board) there may be a firmware problem on the code in the KK
 
Hi mate they are all the same so just get one thats in stock , do you have the acro mini kk strange why it has 1.9s1pro, thats normally on the evo,
Steveis said dont update unless you have a bad acc so it will let you fly acro
 
As far as I know I just have the normal kk2.1. I'll provide a link to the one I bought.

I fixed the problem though. I went to my local hobby store and tried out other ESCs and they worked perfectly with my set up. I ended up selling my Hyperion ones and replacing them with some Hitec 40A ESCs that worked great and were much easier to program. The Hyperion ESCs do not work with the kk2.1 board.
 
Hi Holden I think it will have the standard HK firmware , If you get the flash tool put on Steveis1.8s1pro ( not the 1.9 this is for the acro board) your be shocked how much better the quad flies , just on default settings , if you want links to flash tools etc let me know
 
Oh it's that much better? Ok ill defiantly get the flash tool then. Thanks.
Question. You keep saying for the "acro board" what do you mean by that?
Is "acro" short for acrobatic or something?

Also just so you know I'm not building a quad-copter. I'm building a dual copter, and this whole thing is for school. Goal is to make a VTOL aircraft like the V-22 Osprey.

Here is a snap shot of some of the CAD I've done on the design. Me and my team are about halfway done building it.
upload_2015-3-12_16-10-24.png

Thanks for all your help so far man. Appreciate it.
 
Hi mate yes its the acrobatics board , cant be made as tame so you really need to know how to fly
OMG osprey looks good your need a transmitter that does Vtol I think unless you can find a FCB to add this to a quadcopter board
Take a look at this they use Birds eye view to go from hover to forward flight its the control board
http://www.birdseyeview.aero/
 
Last edited:
Yea I've seen that before. Pretty cool.
I found a thread on RC forms of a build a guy did, not sure where the link is at the moment. I need to look it over again.
But yea we are going to use a separate FCB to try and get the two different modes configured.
On the thread the guy used a KK FCB along with this eagle tree guardian flight stabilizer
http://www.eagletreesystems.com/index.php?route=product/product&product_id=50

Here is the thread that lead me to choose the KK and the Eagle Tree.

http://www.rcgroups.com/forums/showthread.php?t=1814667&highlight=VTOL+Trainer+bixler

Its not a perfect build but I had to find something that works on short notice.
I am definitely going to buy the flash tool to change the firmware on my KK now.
 
Holden said:
The Hyperion ESCs do not work with the kk2.1 board.
Click to expand...
Never fixed this issue. I moved onto another build, though would love to know why this doesn't work. Any new info out there? I still have the old build, been trying to keep it from collecting dust. I bought the Hyperion stuff thinking it was of great quality...would love to actually use it. I might need to contact a local expert, but not sure where to go.

Bottom line: If someone has had this issue, how did they get over it besides just getting new ESCs? Thank you.
 
Also, did flash to v 1.17s1 Lite steveis before.

Just to review...I can do a throttle-pass through with the KK board, the ESCs respond (beep beep) to full throttle, then respond at no throttle (beep beep). While still in throttle pass through, I can spin the motors up, everything responds. The issue is when I pull my fingers off the 1 & 4 buttons on the KK board and disengage the throttle pass through: the ESCs seem to beep as if they'd lost all input, I think it beeps to sort of let you know it's not connected because after it calls out twice they seem to go into a fail-safe, where they constantly beep over and over. Arming the board will not result in any output to the motors, motors will still continue to beep over and over. Question is why they can't handle seeing a throttle input for some short duration, during SAFE mode...can't even run ACC calibration before "flight". Hopefully this sheds more light on the issue.
 
Back
Top