HiSky protocol - HCP100S HCP100 out of sync

Recently I brought a HCP100S and a HCP100. Use HiSky protocol can bind both of them.

However, both not stable:
From time to time, HCP100S lose control for a short time (sticky servo), left side LED blinks at the same time

HCP100 has shudders in all channels occasionally - cyclic has burst movements, the tail has sudden shakes.

Tried with a radio came with a V922, it flys the HCP100 perfectly. Though cannot fly HCP100s, once linked, the servo never sticky and the LED never blinks.

I also have a V922 bought more than one year ago, it can be controlled perfectly.

It looks like the Deviation HiSky protocol may not fully compatible to HiSky protocol, TX and RX out of sync once in a while?

Unlike the new HCP100, V922 does not shudder at all with both WLtoys radio or 7E. I guess either the firmware updated or my V922 and HiSky are different in firmware versions.

Which version of Deviation are you running?

I seem to agree.

I was given an MCPX with a blown board so replaced it with a Hisky HCP100 board.
Binds ok with Deviation on 7e but servo movement moves are weird (delayed & incorrect) so will not take off.

I then purchased a brand new HCP100, once arrived binded it to the Devo 7e & again weird behaviour.

I am running Deviation 4.01

So I'm stuck with a brand new HCP100 that doesn't fly and a HCP100 board that behaves erractivally

I have an HCP100 that worked fine with the nightly builds last time I tried it, and an HCP100S which I haven't tried yet. I'll give them a shot in the next couple of days and see how they behave.

I have an HCP100 and fly it with a 7e with nightly build 4.0.1-2e82bal. No issues with servo movement at all. I bought the HCP100 April of 2014 I believe. Don't know if that matters or not. Strange that some are having issues and some aren't.

Have you tried re-binding with the tx almost touching the heli? I know HiSky has had some issues in the past with laggy servos that were resolved by following that process.

I bought my HCP100 mid January 2015, not sure if Hisky updated the firmware then.
I tried it on the Devo 7e.
Will try it on my Devo 8S sometime next week if so see if it makes any difference when I find the time.

That's a funny solution but will give that "touching Heli" rebind. Normal rebinding has made no difference

mikemacwillie wrote: Which version of Deviation are you running?

I am using default 4.01 build 92e1705. The file hisky_nrf24l01.c does not have functional changes since the V4.01 release.

Mmon77 wrote: I have an HCP100 and fly it with a 7e with nightly build 4.0.1-2e82bal. No issues with servo movement at all. I bought the HCP100 April of 2014 I believe. Don't know if that matters or not. Strange that some are having issues and some aren't.

Have you tried re-binding with the tx almost touching the heli? I know HiSky has had some issues in the past with laggy servos that were resolved by following that process.

Yes, I did re-binding very closely, that did not help.

The PCB of my old V922 seems exactly the same as my new HCP100 PCB, but my v922 never has problem.

Just tested out my HCP100, it's also working fine with the nightlies. Haven't had a chance to try the HCP100S yet.

I am also having range problem where the left led of hcp100s flashes around 15 feet away from transmitter. I did not try to fly heli bcz risky

ahmadie wrote: I am also having range problem where the left led of hcp100s flashes around 15 feet away from transmitter. I did not try to fly heli bcz risky

where is this problem? board? or deviationtx?

fox wrote:

ahmadie wrote: I am also having range problem where the left led of hcp100s flashes around 15 feet away from transmitter. I did not try to fly heli bcz risky

where is this problem? board? or deviationtx?

I am not sure. i fly my v977 heli with KN protocol with no range problems but when i try to fly hcp100s the range is short. actually only me and one other person at rcgroups reported this problem.

I am very confused:
1. TX seem no problem. Same as what you get, I can fly KN and a old V922 with HiSky protocol, no problem at all at 10mW settings.

2. Next guess is half deaf RX. However, the same 100S PCB can be controlled by the old V922 TX with no problem (no blink LED).

3. Protocol problem? HiSky protocol works fine with my old V922. It can bind 100s. The sticky servo (LED blink) is intermittent, some time can be as long as one minute without sticky problem.

4. Only left is that 100s uses different protocol from the old V922, and it is compatible to V922 controller and not Dev HiSky protocol. However, not all Dev user report the problem.

Still no clue!

You can try to change your TX id for the model in question. Also, the power during bind procedure is intentionally lowered so as to exclude accidental bind of someone else's model. It can pose a problem sometimes. Try to put the model and TX as close as possible during binding.

Hi victzh,
Glad you join the discussion!

I tried lots of things.
High and low power settings. All at almost touch range to bind. Not help.

Different hopping frequency patterns (for test, hard coded, no relation to TX ID) 20 different ones, repeat every 10, every 5, and every 4. Hope that when out of sync, the repeat patterns can get recovery sooner. Not help though.

Not sure what happens at RX side when a packet is lost. It stop hopping or continue to next frequency?

In the first case, it may need 20 * 9ms = 0.18 sec to get another packet, or pause for 0.18s

In the second case, 9ms timeing become very important. RX uses slightly shorter period?

Do you know whether V922 controller use all 20 hopping frequencies?

Wish I can access a frequency analyzer to see the transmission.

James (HiSky_Official) from RCGroups promised to send me the details of the new HiSky protocol as soon as he's back from Chinese New Year: www.rcgroups.com/forums/showpost.php?p=30783572&postcount=6599

We will know soon!

That is great!

Has anyone purchased a hcp100 anyone this year (2015) and got it all working with a Devo 8S?
If so please can you share your model's ini file.
Got my Devo 8A back now so I would like to try and see if it makes a difference or if it still behaves erratic & won't fly just as the Devo 7.
Thanks

Although I still believe there's done compatibility issues with the newer hcp100 boards.
I may be stuck with another useless hcp100 heli that won't fly

I bought my HCP100 this year and does not work with my old V922 TX.
It is the same that was reported above:

Difficult to bind it, short range, throttle and servo movement moves are weird (delayed & incorrect).

Sounds like the classic bad binding problem.

I am flying my HCP100S and all my HiSky heli with my modded Devo 7e without any problem that I can detect.