Spectrum DM9 Modult not operable under version 133 and others.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set up DSM2 Spectrum DM9 module and AR6200 Radio with any servos connected 
to ch1.
2. Try to move ch1 stick - servo will move with delay and jitter.
3. Load original factory microcode - issue will go away.

What is the expected output? What do you see instead?
I see it will be good in your microcode to increase pause betwin channel pulses 
from 300 to 400 usec. I cannot do it myself, I hope you will.

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by server...@gmail.com on 14 Aug 2010 at 10:44

[GoogleCodeExporter]

PPM sequence values were measured and compared  for V2 original microcode and 
Th9 v 133 microcode. Spectrum DM9 module operated well while iterchannel pulse 
duration = 400 usec. 

Original comment by server...@gmail.com on 14 Aug 2010 at 10:54

[GoogleCodeExporter]

I have changed pulse duration to 400, doesn't help ! server28 suggested, last 
diff we have between your FW and original V14 is duration of frame. You have 
22.5 and original one 20. I have changed to 20 and sent version to server28. He 
has reported with duration of ppm frame 20 his module DSM2 Spectrum DM9 is 
working without any problem.

Original comment by vlad...@yahoo.com on 15 Aug 2010 at 5:45

[GoogleCodeExporter]

Changes in source code:

 was 
uint16_t rest=22500u*2;
is
 uint16_t rest=20000u*2;

Original comment by vlad...@yahoo.com on 15 Aug 2010 at 5:51

[GoogleCodeExporter]

oops
a closer look to the code showed me a litle bug in the pulse generation part.
I think, that the current duration is 22.5ms + 9*0.3ms = 25.2 ms. (forgot the 
low-pulse lengthes)
I fixed this to 22.5 ms in the next version. This has nearly the same frame 
effect of your change (rest=20000).
Has anybody measured the exact current frame duration?

Original comment by th...@t-online.de on 27 Aug 2010 at 10:46

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I measured with Proteus simulator and I can confirm in r141 pulse is 22.5ms and 
with my changes it was 22.5ms too :) Seems you are right, without changes it 
was 25.2ms

Original comment by vlad...@yahoo.com on 27 Aug 2010 at 3:37

[GoogleCodeExporter]

Original comment by th...@t-online.de on 27 Aug 2010 at 6:51

• Changed state: Fixed