Devo 10 (v4.0.1) lag on Blade 200 SRX controls

Hi Forum,

1st of all: SORRY for my bad english! I am from germany and it is quite a while from my schooldays until today...

This is my problem I would like to discuss on this forum:

I am having a problem with my Blade 200SRX; all controls show a lag of about 2-3 tenth of a second, which leaves my Heli quite unflyable.

The same TX works perfectly fine with my Blade Nano QX and Blade MSR.

The Blade 200 SRX works perfectly with my Dx6i (no lag).

I tried rebinding the 200SRX and using another ini-file but the lag remains uneffected.

So I kindly ask for a hint leting me find the solution for this lag, since I have not got any idea about the origin of this uncommen problem (uncommon because I could not find any similar problem on the internet)

Thank you for reading so far

Regards

I to also found there was a lag........so went across to the nightly builds as I could not get switching to work I have included a model ini for this in the model section ....
You never know try it and see??
Hope this helped

If you're using DSMX, try DSM2, and vice versa. Also, make sure you've only got six channels configured on the Tx. I've never had a problem with mine, whether running 4.0.1 or the nightly builds.

Not sure about the 200SRX lag but since only the nightly-build versions will let you:
- display 9999 numbers (>255) in telemetry flightlog display
- higher framelosses and hold numbers to tweak the 200SRX setup gain numbers

I would suggest you give it a try.

We especially extended the telemetry just for 180CFX and 200SRX.

You might also want to give one of the Indigo/Vlad DSMx protocol + telemetry re-engineering test-builds for the 200SRX a try and see if it improves on your side for DSMx.

Sorry, but I do not own a 200SRX. 200QX was fine.

Have you already put up throttle >100% (yes of course this has nothing to do with a protocol / steering lag).

Greetings

Thomas

Thx for the tips so far - So the new roadmap is:

- try another ini-file
- change the protocol (dsm 2/x)
- check the number of channels defined (think it is 4 for steering plus 1 for panic + 1 for flightmode which would be exactly 6)
- flash a nightly-devo-fw

I think(!) I already made a protocol-change (dsm 2/x) but I am not sure wether I did a rebinding, so I will check that (again)

@thomas.heiss: Yes, I put up throttle to 200% (Gain 4 as far as I remebember), but I still think about another motor-pinion (12 teeth)

Hi there, the lagg-man again

1st of all: It works!!!!!

I tried another ini (model4-slot - the lagging showed at model3-slot), did the binding and "VOILA" no laggs anymore.

But the weird thing is now to come: Also the model-3-slot-ini works now WITHOUT laggs.

So it could have been just a binding issue (kind of "human error" you know ...)

Anyway: THX to all that tried to help me !

GONE FLYING ...

Hi,

no, don't fly with DSM2 which may use two channels which are near to each other (in the worst case): www.rcmodelreviews.com/dsm2flaw.shtml

You better use DSMx as true FHSS hopping system.

According to ETSI V1.8.1 it is prohibited to use 2-3 channel DSSS protocols in DE (complete EU?) starting 01/01/2015 any way.

I am using the proper DSMX-Protocol, since everything is working fine now (s.a.)