search

sylvandb / gruvin9x

Automatically exported from code.google.com/p/gruvin9x
0 stars 0 forks source link

Possible PPM_OUT (IN?) issue with long beeps #22

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

See here: http://www.rcgroups.com/forums/showpost.php?p=17666813&postcount=5365

Fix

A fix was written. See here: 
http://www.rcgroups.com/forums/showpost.php?p=17710737&postcount=5399

--- Suggest using a scope to watch PPM out while messing about with various 
beep causes to confirm fault in gruvin9x or not. Fix as required.

Notice of this possible fault from: Bertrand, via the discussion group. Thanks 
mate.

Original issue reported on code.google.com by gru...@gmail.com on 18 Mar 2011 at 5:07

GoogleCodeExporter commented 8 years ago 
I will provide you a fix with a make option for those who prefer a hardware mod 
(will save some extra bytes!)

Original comment by bson...@gmail.com on 18 Mar 2011 at 10:51

GoogleCodeExporter commented 8 years ago 
Hi Bryan,
Attached is the diff file.
I have modified the option BEEPER so that it can take values BUZZER || 
BUZZER_MOD || SPEAKER.
Tested OK on my turnigy 9x + simulator!
Regards,
Bertrand

Original comment by bson...@gmail.com on 18 Mar 2011 at 8:12

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks. If it's a bug that stuffs things up, it doesn't need to be an
optional fix, and I'll most likely just put the permanent fix into main code
base.

Meanwhile, I'll save the DIFF for later on when I hopefully get some time to
work on the project again. I've been very, very busy with other work lately.

Bryan.

Original comment by gru...@gmail.com on 21 Mar 2011 at 12:27

GoogleCodeExporter commented 8 years ago

Original comment by gru...@gmail.com on 21 Jun 2011 at 10:39

GoogleCodeExporter commented 8 years ago 
What was the hardware mod to fix this? I'm still really unclear as to how the 
problem came about in the first place. How could turning the beeper on possibly 
have any affect on the Sim_Ctrl output? Huh?

I need to understand this, so as to know if the V4 board could possibly suffer 
the same fault -- or if we can get rid of some unneeded patch code for V4. 
Thanks.

There is no 4066 switch on the V4 board -- but the PPM_PUT heading to the 
trainer jack can still be turned off by software control (and is for PPM_IN 
use.)

Original comment by gru...@gmail.com on 23 Sep 2011 at 2:00

GoogleCodeExporter commented 8 years ago 
The discussion between Mike / coro and me (bertrand35) is here:
http://www.rcgroups.com/forums/showthread.php?t=1266162&page=360#post17708366

The hardware bug is described by Mike:
"Coro, I'm guessing a bit here, but it looks to me that the SIMCONTROL line is 
switched depending on the source of power (internal or external). The source 
detection is done by a high input impedance (150K) circuit that is on the same 
connector as the buzzer output. There may be some electrical noise pickup when 
the buzzer is sounding that affects this circuit. If this is the case, then a 
capacitor, of say 100nF, could be tried across the 100K resistor R136 (on the 
circuit I have!) to filter out the noise."

Original comment by bson...@gmail.com on 23 Sep 2011 at 8:19

GoogleCodeExporter commented 8 years ago 
Right! Got it now. I was oblivious to all this when it first came out and took 
no action. But Cam must have read that post and has already added the 0.1uF 
cap. Good.

Therefore, the V4 board can be considered to have the hardware mod done. Whew.

I'll retire this issue again and modify the code to behave like BUZZER_MOD 
(where relevant) for the V4 board.

Original comment by gru...@gmail.com on 23 Sep 2011 at 10:25