HiSky protocol - HCP100S HCP100 out of sync

could you post the ini for the hcp100s with devo 7e

Any news from James? I have V922 and also HCP100S out of sync problem still not solved. I have also issues with the flysky protocol and V912 - strange servo movement. Interesting is that V911 is flying well.

Daryoon, have you modded your HCP100S somehow? My Hisky helis are not usable with Devo 10. I tried almost everything without success.

hi
i have my hcp100s up and flying with the devo 7e.I modified the ini and it flys verry well now.
name=HiSky HCP100S
mixermode=Advanced
icon=HCP100.BMP
[radio]
protocol=HiSky
num_channels=6
fixed_id=44128
tx_power=150mW

[channel1]
reverse=1
max=100
scalar=70
scalar-=70
min=-100
template=complex
[mixer]
src=AIL
dest=Ch1
scalar=55
curvetype=7point
points=-35,-40,-25,0,33,70,100

[channel2]
reverse=1
max=100
scalar=80
min=-100
template=complex
[mixer]
src=ELE
dest=Ch2
scalar=65
curvetype=7point
points=-35,-40,-25,0,33,70,100

[channel3]
scalar-=100
template=complex
[mixer]
src=THR
dest=Ch3
switch=FMODE0
curvetype=9point
points=-100,-75,-50,-25,0,25,50,75,100
[mixer]
src=AIL
dest=Ch3
switch=FMODE1
scalar=60
usetrim=0
curvetype=fixed
[mixer]
src=AIL
dest=Ch3
switch=FMODE1
scalar=90
usetrim=0
curvetype=fixed
smooth=1
[mixer]
src=AIL
dest=Ch3
switch=HOLD0
scalar=-100
usetrim=0
curvetype=fixed

[channel4]
max=100
scalar=80
min=-100
template=complex
[mixer]
src=RUD
dest=Ch4

[channel5]
template=complex
[mixer]
src=AIL
dest=Ch5
switch=HOLD0
scalar=-100
usetrim=0
curvetype=fixed
[mixer]
src=AIL
dest=Ch5
switch=HOLD1
usetrim=0
curvetype=fixed

[channel6]
reverse=1
max=100
scalar=28
scalar-=20
min=-100
template=complex
[mixer]
src=THR
dest=Ch6
switch=FMODE0
scalar=60
usetrim=0
curvetype=7point
points=-15,-10,-5,0,20,40,60
[mixer]
src=THR
dest=Ch6
switch=FMODE1
usetrim=0
curvetype=5point
points=-100,-50,0,50,100
[mixer]
src=THR
dest=Ch6
switch=HOLD1
usetrim=0
curvetype=5point
points=-100,-50,0,50,100
[mixer]
src=THR
dest=Ch6
switch=HOLD0
usetrim=0
curvetype=5point
points=-100,-50,0,50,100

[trim1]
src=LEFT_V
pos=TRIMLV+
neg=TRIMLV-
[trim2]
src=RIGHT_V
pos=TRIMRV+
neg=TRIMRV-
[trim3]
src=LEFT_H
pos=TRIMLH+
neg=TRIMLH-
[trim4]
src=RIGHT_H
pos=TRIMRH+
neg=TRIMRH-
[timer1]
type=countdown
src=Ch3
resetsrc=HOLD1
time=300
[timer2]
type=permanent
src=Ch3
val=3606194
[safety]
Auto=min
[gui-128x64]
V-trim=59,10,1
H-trim=5,59,3
V-trim=65,10,2
H-trim=74,59,4
Small-box=2,22,Ch3
Small-box=2,31,Ch2
Small-box=2,40,Ch6
Model=75,20
Battery=102,1
Toggle=4,11,72,0,0,None
Toggle=22,11,0,193,0,FMODE
Toggle=31,11,0,71,0,None
Toggle=40,11,0,0,0,None
TxPower=102,7
quickpage1=Telemetry monitor

Also dont forget that you have to fit the nrf24l01+ module to your transmitter and update the firmware to activate the module.

Burys wrote: Daryoon, have you modded your HCP100S somehow? My Hisky helis are not usable with Devo 10. I tried almost everything without success.

No. I am using it with my Devo 7e with the stock HCP100s.

It looks like the Devo 7e is working well with hisky protocol but Devo 10 not. Is it possible? Yesterday I tried again my old V922. I choosed 150mW output power, binded and flied 3 batteries. There were few motor drop-outs, once servo frozen, happily without crash. It is not related to the distance nor battery voltage. Now I see you use 5 digits fixed ID. I'll try it also today.

hi
i dont have the devo 10 so cant try it myself but if you send me your ini i can check it out for you.

Yesterday I tried again V922 with 5 digits fixed ID, power 150mW, binded and everything worked well! I flew only 1 battery but without any problem! wow... Unfortunately I haven't more time to test it more, but now I have good hope. Today I'll try HCP100S.

hi
im glad its working for you now .Good flying.

Burys wrote: Yesterday I tried again V922 with 5 digits fixed ID, power 150mW, binded and everything worked well! I flew only 1 battery but without any problem! wow... Unfortunately I haven't more time to test it more, but now I have good hope. Today I'll try HCP100S.

Hisky protocol never has any issue with my V922. I only use 30mW to save the battery of my radio.

It does not work very well with my new HCP100 and HCP100S.

How about your HCP100s? Seems some lucky ones still can fly with no issue, wish you are one of them. Though I am not - I can fly it in normal mode, if the servo sticks for a while, I still can recover after the control resumes. But in 3D flying, lost control pretty much = crash!

do you use the devo 7e and if so have you tried the ini above because it works for mee withought any problems with my hcp100s.

Hi all, finally I solved all issues! Both my HCP100S and V922 are flying very well. The problem was probably in bad binding. Now I use 5 digits fixed ID and 150mW power. I tried to fly as far as I can see the helicopter and without any problems. Now I have more than 30 minutes flied flawlessly. The HCP100S is suprisingly powerfull, I like it.

I also have no problemen.
The hcp100s flies really good.

pmc and Burys, glad to hear you can fly without problems.

My case is different, without touch the sticks, only shaking my 7E radio very hard can trigger the servo sticky and left side LED blinks. Tried all kinds of bindings, not not help.

Not likely the INI file issue.

Thanks for your input.

hi
try for hisky fixed id 44128
and for v977 fixed id 134566
this works for me the best.

If shaking the radio invokes the problem. I would double check your NRF24L01 installation. Possibly a cold solder or something like it. (No offense intended)

Not the HW problem. The same module controls V977 without any issue.

I have three models V922, HCP100, HCP100S. Here is the list of all combinations:

7E + 24L01 V977 OK
7E + 24L01 V922 OK
7E + 24L01 100S Sticky servo
7E + 24L01 100 shudders

V922 radio is OK for all three models

Shaking 7E near the chopper cause dramatically radiation strength changes. If the two algorithm is not match well, the link may be interrupted, and cannot back in a short time.

The list shows that no failure of any individual items.

can you post your ini file for the hcp100 and 100s and ill check it for you