Closed GoogleCodeExporter closed 8 years ago
I read about issue 718. I am a newbie but it could be the same cause as 718 ...
RCX values are not stored in EEPROM.
Original comment by Gregm...@gmail.com
on 24 Aug 2012 at 3:21
I think I sould add further details:
Although the RC_Out value is changing when I give input from RC there is no
servo movement. So someone must add a servo to simulate the issue.
Original comment by Gregm...@gmail.com
on 24 Aug 2012 at 6:05
[deleted comment]
This is also on Channel 7. Also it looks like it's only apm2.
On the APM2 if I load from the MP, 2.60 and do a setup. I set the RC7_FUNCTION
to 1, I get NO output on the servo, however the MP shows output. If it is set
to 3, you will get output on the servo. I then change it back to 1 for correct
fuction. On a change of battery, same thing again. The RC7_FUNCTION is set to
1, but no output on the servo.
Next I loaded the firmware on a APM1 and it works correctly? :<
it will hold the value and after a battery change will still work.
Original comment by burtg...@gmail.com
on 28 Aug 2012 at 1:36
Ok it only affects APM2. But real strange is that CH 7 is working fine for me
in manual mode (1).I have only the problem on CH 6.
Original comment by Gregm...@gmail.com
on 28 Aug 2012 at 3:36
The results from further tests:
I use CH 6 and CH 7 in manual mode (RCX_FUNCTION 1).
If I set Channel 7 to Flap_Auto (3), Channel 6 will work fine in manual.
But if I set CH 7 to Flap (2) CH 6 doesn´t work.
I can´t understand what is going wrong.
Could someone of the developers please comment this issue?
Original comment by Gregm...@gmail.com
on 30 Aug 2012 at 9:33
Hi Greg, I'll see if I can reproduce it and get back to you
Original comment by tridg...@gmail.com
on 30 Aug 2012 at 9:48
I think the error should be fixed with rev. acc021c81993
I will do some tests in the evening
Original comment by Gregm...@gmail.com
on 2 Sep 2012 at 6:08
I crowed too soon: The issue still persist in the rev. acc021c81993 :-(
Original comment by Gregm...@gmail.com
on 3 Sep 2012 at 10:23
I've reproduced the problem, and pushed a fix ready for the next release
Original comment by tridg...@gmail.com
on 8 Sep 2012 at 5:19
Original issue reported on code.google.com by
Gregm...@gmail.com
on 23 Aug 2012 at 9:20