¿ªÔÆÌåÓý

Re: New Setup issues


 

¿ªÔÆÌåÓý

Hi Cassie

For an FM RX channel one would expect a much higher audio level with zero received signal. ie try increase the slider to around 100% for a start. The way to adjust is on an actual signal receipt that should be logged with the audio level eg;

Digipeater RS0ISS audio level = 73(20/13)??? _|||||___
[0.3 23:24:37 UTC] VK3KAW-10>APRS,RS0ISS*,SGATE,WIDE2-1:=3621.56S/14707.30E`..

The "audio level = 73" should be between 50 and 100 or so.

I can see you already found that in your "UPDATE" email. Suggest you standardise with the pavucontrol Input Devices slider on 100% and adjust the Recording tab slider for (say) 75 on received packets. As a guide (same hardware) my slider is set to 80% for ISS.


The audio level that comes with the direwolf command line -a option, like;

ADEVICE0: Sample rate approx. 48.0 k, 0 errors, receive audio levels CH0 86, CH1 91

can be over 100 for an FM RX (ie mostly just unmuted noise) It depends on the relative deviation, bandwidth and RX design etc.


If the 9100's are adjacent/nearby/running then possibly use one as a TX source to test the other RX. The usual caution about dummy loads and/or no antenna with PTT disabled. This is also a good test bed for finding the right TXDELAY number. If you did a rig reset too the USB port audio output level (menu 56) may have changed (back) to default resulting in over or under deviation.

I think too that using a single 9100 with its monitor turned on (button 2 left/below VFO knob) will feed audio back into direwolf. ie any packet you TX will come back on RX. Handy for all kinds of tests and will also get the input level (above) in the ball park.

Also be aware that the IC9100 has 3 fixed IF FM filters, 15Khz, 10kHz and 7.0Khz (Filter 1, 2 & 3). The TX deviation however for the 2 narrower ones is then set to 2.5kHz. You probably want to only use the 15kHz filter, but keep in mind for Doppler etc situations.


Cheers Bob



On 14/1/25 08:44, cdres via groups.io wrote:

Hello Bob and thanks for the reply!

pavucontrol is showing up normal just as before:

rigctl -m 2 is working I believe:

You're probably right about the delay, I adjusted the config file to 30 instead. I also flushed the iptables rules temporarily just for testing- and low and behold... no traffic on the airways for me to try to receive. I started to wonder if someone had inadvertently changed the settings on my rigs, so I did a partial reset on both and re-configured their settings as I did previously. still, nothing. So now I'm just not sure of anything. Either everything is fine, and it's just a happenstance that our test antenna are too weak, and there isn't enough traffic to test with... or something is broken and I don't know where to start.
I've decided to leave the rig running for a bit longer today and see if anything pops up. I'll update if so.

Cassie

Join [email protected] to automatically receive all group messages.