Hi Christoph,
On 20/10/2023 13:52, "Christoph v. Wüllen" wrote:
> Dear Reid,
>
> I have now re-compiled the code and tested the audio input with "Audacity"
> and made progress. First my jumper settings are (viewed from the top)
>
> a b c
> x y z
>
> ---------
> ! MIC !
> ! JACK !
> ---------
>
> such that two jumpers are set that connect x-y and b-c
>
> The connection b-c is relevant for the microphone, it connects
> the tip of the 3.5mm jack to the mic input. The connection x-y
> is for PTT.
>
> I have now wired the pink (microphone) plug of the headphone as follows:
>
> Gnd(Headphone) ==> Gnd(Jack)
> Ring(Headphone) ==> Tip(Jack)
Yes, this is the way I have mine setup.
>
> I guess for the last connection it does not matter if you connect
> with the ring or the tip of the headphone since they are the same.
>
> Note it also works if you just plug in the microphone plug
> into the microphone jack, but then you loose PTT.
>
> Two changes had to be made to CWKeyerShield.cpp:
>
> --- a/libraries/teensy/CWKeyerShield/CWKeyerShield.cpp
> +++ b/libraries/teensy/CWKeyerShield/CWKeyerShield.cpp
> @@ -68,11 +68,19 @@ void CWKeyerShield::setup(void)
> wm8960->enable();
> wm8960->volume(masterlevel_actual);
> wm8960->inputSelect(0); // select and activate microphone input
> - wm8960->inputLevel(0.1F, 0.1F); // volume control for mic input (both mic and MEMS)
> + wm8960->enableMicBias(1);
> + wm8960->inputLevel(0.5F, 0.5F); // volume control for mic input (both mic and MEMS)
> }
>
> The important thing is the line with enableMicBias, otherwise the headset cannot work properly.
> Then, I adjusted the input levels (they were a little weak).
Would your binary for this work directly for Steve's board. I have no
way of directly building from source.
>
>
> I then unplugged the microphone jack, whistled into the headset mic and re-plugged it after few
> second, the recording is as follows:
>
>
>
>
>
> In the first two second, you only see signal on the right channel from the built-in
> MEMS microphone. After two seconds, when I plugged in the head-set, I get
> a signal on the left channel (mic jack) as well.
>
> The downside of all this is that there is no software API to make these settings (e.g.
> bias on/off or volume settings), so one has to recompile for a given need.
> What *is* possible to define "typical situations" and generate a hex file for these.
>
> I send a copy to the list, since this may be important.
If there are going to over 50 boards produced, it's important that we
have working software to download on to them with as much functionality
as possible.
Cheers
Reid
Gi8TME/Mi0BOT
>
> Yours
>
> Christoph DL1YCF.
>
>