开云体育

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

开云体育

Extra decoders are set in the Modem config tab in the Add Rx n pairs box.

These are not needed on FM. On SSB tuning has to be within about 30Hz for packets to decode successfully. This amounts to a TX to RX accuracy of around 2 parts per million on 20 Meters. Modern rigs are usually that stable, but do not always have that accuracy. So QtSM can add extra decoders tuned +- 30 Hz from the nominal. I find two pairs (a total of 5 decodes) is usually enough for normal HF operation. Each extra pair adds to the cpu load so if you are running several modems on a relatively slow platform like a Pi 3 you may need to check that you aren't overloading the cpu.

QtSM reports the success of each decode in the form [--+++]. This shows that the top 3 decodes were successful, suggesting the station was around 30 Hz high. If all stations appear either low or high it may mean you are a bit off frequency. If you see stations that are always? on the edge (eg [----+] than maybe you need more decodes (or to persuade the other station to move a bit!)

73,
John



On 18/05/2023 23:28, Matthew 2E0SIP wrote:

Hi Red,

Thanks for the debugging tips.

?

Make sure you’re only running 1 extra pair of decoders per port on QtSoundModem if running on SSB

I'm not sure where this is configured? I've not enabled any.

Make sure IL2P isn’t enabled as well as FX25 on a single port.

IL2P is disabled on both sides (QTSM and the NinoTNC)

?

Try fiddling with the extending the TXDelay in normal AX25 mode.

I set it to 500ms to rule out any issues and it didn't help.?

?

I've attached the WAVs. Both are the string "Hello" sent 3 times.

?

Thanks

Matthew

2E0SIP

?

?

?



Re: Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

开云体育

Hi Matthew.

Both recordings sound the same and look the same on Audacity, and both decode on both the original Soundmodem and QtSM.

The packet is too short to be send as fx25, so I'd expect them to be the same.

I'll do some more tests here with longer packets and see if I can reproduce your problem

73,
John


On 19/05/2023 00:49, Matthew 2E0SIP wrote:

I grabbed the audio out the back of the receiving radio and attached them to this message. There's no drop outs so I guess they were a result of trying to be clever and using audio loop backs for the recording.

Hopefully these are a bit more useful.

Thanks

Matthew



Re: Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

Good stuff,

Can you record the same test output from Direwolf?

Cheers
Red


Re: Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

I grabbed the audio out the back of the receiving radio and attached them to this message. There's no drop outs so I guess they were a result of trying to be clever and using audio loop backs for the recording.

Hopefully these are a bit more useful.

Thanks

Matthew


Re: Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

I've just listened back to those and there's some drop outs in the audio I missed first time.

They were recorded with QTSM outputting to a loopback and then recorded with Audacity. I don't get the drop outs using Dire Wolf in the same configuration.

I'll try to get a recording out the back of the receiving radio tomorrow instead of messing around with loopbacks.

Thanks


Re: Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

Hi Red,

Thanks for the debugging tips.

?

Make sure you’re only running 1 extra pair of decoders per port on QtSoundModem if running on SSB

I'm not sure where this is configured? I've not enabled any.

Make sure IL2P isn’t enabled as well as FX25 on a single port.

IL2P is disabled on both sides (QTSM and the NinoTNC)

?

Try fiddling with the extending the TXDelay in normal AX25 mode.

I set it to 500ms to rule out any issues and it didn't help.?

?

I've attached the WAVs. Both are the string "Hello" sent 3 times.

?

Thanks

Matthew

2E0SIP

?

?

?


Re: Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

Matthew, for a quick tip-

Make sure you’re only running 1 extra pair of decoders per port on QtSoundModem if running on SSB. If not running SSB, set extra pairs to zero. If you have too many pairs it taxes the CPU and will cause decodes to fail.

Make sure IL2P isn’t enabled as well as FX25 on a single port.

I know several of my peers are using QtSoundModem .62 without problems on VHF, I even had someone on MultiPSK connecting in on HF before changing them to UZ7HO SoundModem and then QtSM to add IL2P.

Sounds like a weird problem, we may need to investigate further.?
Can you do some recordings of packets you’re picking up for analysis?

The NinoTNC is dip-switched as far as I know and either has IL2P or only standard AX25. It decoding FX25 packets is just the backwards compatibility working and perhaps the extended TXDelay/preamble is enabling the transmitter to open up the carrier on transmit. Try fiddling with the extending the TXDelay in normal AX25 mode.

-Red


Unable to decode QtSoundModem Beta v0.0.0.62 1200 baud AFSK

 

Hi all,

I've been setting up the latest QtSoundModem Beta and found other systems couldn't decode the packets it sent, but if I used Direwolf with the exact same hardware packets were decoded as expected. This is standard plain old 1200 baud AFSK with 1200/2200 tones.

I know some work has been done recently to add IL2P support so I thought I'd try enabling and disabling it, as well as FX.25, in case something had become "stuck". Well, sure enough with some trial and error, it turns out if I enable FX25 RX+TX the other station can decode the packets. But here's the kicker, I'm pretty sure the NinoTNC used at the other station doesn't support FX.25, so it's not the case that the FEC is improving an otherwise poor link.

With this in mind I downloaded 0.0.0.56 from??and packets are decoded out of the box without FX.25 enabled.

Has a bug been introduced in the latest beta??

Thanks
Matthew

2E0SIP


Re: BPQ APRS igate setup questions #aprs

Ken G7VJA
 

hI kk6qms
I forgot to answer your GUI question
GUI means Graphical User Interface, means you have Icons or a tab to start a program
Non GUI means you start a program via a terminal command line

regards
Ken G7VJA


Re: BPQ APRS igate setup questions #aprs

Ken G7VJA
 

In it hey day it was frowned on the use the core servers, hence the T2 server network was setup,
I ran T2ENGLAND which got it's feed from one of the core server, if mine lost the link it was switched to another Core server and so on.
will connect you to any of the other T2 network so you should not loose connection.
But times have changed since I was last involved.

73 Ken G7VJA?

On Tue, 16 May 2023, 21:28 Kk6qms, <kk6qms@...> wrote:
Yes that is easy to see- but why use tier 2 vs core servers? I'm not clear on what is a GUI vs non-GUI client as referenced (core servers seem to work fine in my cfg currently). Thx.
"
Core Servers
(GUI Clients should use Tier2 Servers, Port 14580)
Standard Ports:
23, 10152 - Full APRS Feed (Recommended APRS-IS Servers Only)
1314 - Message-only Feed
14580 - User-defined Filtered Feed (Recommended for Clients and IGates)


Re: BPQ APRS igate setup questions #aprs

 

Yes that is easy to see- but why use tier 2 vs core servers? I'm not clear on what is a GUI vs non-GUI client as referenced (core servers seem to work fine in my cfg currently). Thx.
"
Core Servers
(GUI Clients should use Tier2 Servers, Port 14580)
Standard Ports:
23, 10152 - Full APRS Feed (Recommended APRS-IS Servers Only)
1314 - Message-only Feed
14580 - User-defined Filtered Feed (Recommended for Clients and IGates)


Re: BPQ APRS igate setup questions #aprs

Ken G7VJA
 

Click on the link and scroll down to APRS2 Group,
Addresses for APRS2 severs is on the left.

74 Ken G7VJA
ex MB7UFO Igate. (22years)

On Tue, 16 May 2023, 20:44 Kk6qms, <kk6qms@...> wrote:
Re Ken's comments- not sure what to use but this defines the servers that exist-?


Re: BPQ APRS igate setup questions #aprs

 

Re Ken's comments- not sure what to use but this defines the servers that exist-?
http://www.aprs-is.net/APRSServers.aspx


Re: BPQ APRS igate setup questions #aprs

 

I found the problem- my ISP is apparently blocking things. (like, a LOT of things apparently). After I did the connect tests it dawned on my I was running a VPN on the PC so I turned it off and could no longer connect to APRS servers. I then installed the VPN on the Pi and restarted BPQ and so far have no connect errors. I have had issues with this small town WISP ISP before but was always related to port forwarding and in this case that was not a factor. I am still unclear what the problem is on their end. I appreciate all the support here and it helped jog my thinking as I went through all the steps and suggestions everyone here offered. I learned a few things as well.?
I noticed the VPN has not been able to connect normally for awhile on UDP port 8080 and has been using alt UDP port 853. (not that I even know what UDP really is etc)
John, I was always able to connect to you using BPQTermTCP as I do that from time to time to check latest BPQ version (c 1 g8bpq-9)?
Thanks again. Time to email my ISP again but unfortunately their service is poor and I may just have to run the VPN from now on. Problem with that is I cannot access BPQ (or my Allstar node) remotely via DDNS when VPN is in use.


Re: BPQ APRS igate setup questions #aprs

Ken G7VJA
 

开云体育

Hi John

Looking at the result on the message the ip address is wrong

it should be rotate.aprs2.net:14580

not aprs.net

root@kenny-XC-215:/home/kenny# telnet rotate.aprs2.net 14580
Trying 78.47.200.124...
Connected to rotate.aprs2.net.
Escape character is '^]'.
# aprsc 2.1.14-g5e22b37
# aprsc 2.1.14-g5e22b37 16 May 2023 18:26:41 GMT T2NUERNBG 78.47.200.124:14580
Connection closed by foreign host.

Ken G7VJA


On 16/05/2023 20:08, John G8BPQ wrote:

Something on the pi must be blocking the connection, as you can connect from the same lan on a pc.

Can you connect to other things on the Internet from the pi? eg telnet nottm.g8bpq.net 8011

73, John


On 16/05/2023 19:23, Kk6qms wrote:
NODEFAULTROUTE configured in IPGATEWAY section- no cfg errors on start- still no connect to APRS server.

TELNET RESULTS FOR JOHN:
APRS server connect via telnet result on Pi:

root@Pi-BPQ:/home/pi# telnet rotate.aprs.net 14580
Trying 148.251.228.231...
Trying 205.233.35.52...
Trying 45.76.98.200...
Trying 85.188.1.114...
Trying 44.52.120.40...
Trying 192.104.234.220...
Trying 204.87.183.30...
Trying 205.233.35.46...
telnet: Unable to connect to remote host: Connection timed out
root@Pi-BPQ:/home/pi#


APRS server connect via telnet result on PC (same LAN) using PuTTY:

# aprsc 2.1.14-g5e22b37
# aprsc 2.1.14-g5e22b37 16 May 2023 17:23:49 GMT FIRST 148.251.228.231:14580

CAPS/lower case suggestion not implemented I do not think that is an issue.

Thank you.


Re: BPQ APRS igate setup questions #aprs

 

开云体育

Something on the pi must be blocking the connection, as you can connect from the same lan on a pc.

Can you connect to other things on the Internet from the pi? eg telnet nottm.g8bpq.net 8011

73, John


On 16/05/2023 19:23, Kk6qms wrote:

NODEFAULTROUTE configured in IPGATEWAY section- no cfg errors on start- still no connect to APRS server.

TELNET RESULTS FOR JOHN:
APRS server connect via telnet result on Pi:

root@Pi-BPQ:/home/pi# telnet rotate.aprs.net 14580
Trying 148.251.228.231...
Trying 205.233.35.52...
Trying 45.76.98.200...
Trying 85.188.1.114...
Trying 44.52.120.40...
Trying 192.104.234.220...
Trying 204.87.183.30...
Trying 205.233.35.46...
telnet: Unable to connect to remote host: Connection timed out
root@Pi-BPQ:/home/pi#


APRS server connect via telnet result on PC (same LAN) using PuTTY:

# aprsc 2.1.14-g5e22b37
# aprsc 2.1.14-g5e22b37 16 May 2023 17:23:49 GMT FIRST 148.251.228.231:14580

CAPS/lower case suggestion not implemented I do not think that is an issue.

Thank you.


Re: BPQ APRS igate setup questions #aprs

 

On Tue, May 16, 2023 at 11:23 AM, Kk6qms wrote:
NODEFAULTROUTE configured in IPGATEWAY section- no cfg errors on start- still no connect to APRS server.

TELNET RESULTS FOR JOHN:
APRS server connect via telnet result on Pi:

root@Pi-BPQ:/home/pi# telnet rotate.aprs.net 14580
Trying 148.251.228.231...
Trying 205.233.35.52...
Trying 45.76.98.200...
Trying 85.188.1.114...
Trying 44.52.120.40...
Trying 192.104.234.220...
Trying 204.87.183.30...
Trying 205.233.35.46...
telnet: Unable to connect to remote host: Connection timed out
root@Pi-BPQ:/home/pi#


APRS server connect via telnet result on PC (same LAN) using PuTTY:

# aprsc 2.1.14-g5e22b37
# aprsc 2.1.14-g5e22b37 16 May 2023 17:23:49 GMT FIRST 148.251.228.231:14580

CAPS/lower case suggestion not implemented I do not think that is an issue.

Thank you.
Aha, there is certainly a network issue here.

Lets see output of:

traceroute rotate.aprs.net

You may also try the ‘mtr’ tool (sudo apt install mtr)

Also can you post the output of:

ip route?



Ttfn, 73
Red


Re: BPQ APRS igate setup questions #aprs

 

NODEFAULTROUTE configured in IPGATEWAY section- no cfg errors on start- still no connect to APRS server.

TELNET RESULTS FOR JOHN:
APRS server connect via telnet result on Pi:

root@Pi-BPQ:/home/pi# telnet rotate.aprs.net 14580
Trying 148.251.228.231...
Trying 205.233.35.52...
Trying 45.76.98.200...
Trying 85.188.1.114...
Trying 44.52.120.40...
Trying 192.104.234.220...
Trying 204.87.183.30...
Trying 205.233.35.46...
telnet: Unable to connect to remote host: Connection timed out
root@Pi-BPQ:/home/pi#


APRS server connect via telnet result on PC (same LAN) using PuTTY:

# aprsc 2.1.14-g5e22b37
# aprsc 2.1.14-g5e22b37 16 May 2023 17:23:49 GMT FIRST 148.251.228.231:14580

CAPS/lower case suggestion not implemented I do not think that is an issue.

Thank you.


Re: BPQ APRS igate setup questions #aprs

 

On Tue, May 16, 2023 at 12:26 AM, Kk6qms wrote:
Thank you.

"NODEFAULTROUTE" is not configured.
The ENDPORT error was just a missed line that needed to be commented out from an unused port. Error cleared there.
igate not connecting continues.
Then configure it, is what I meant :-)


Re: BPQ APRS igate setup questions #aprs

 

开云体育

Can you try this from the Linux command line?

telnet rotate.aprs.net 14580

I get this:

Trying 192.104.234.220...
Connected to rotate.aprs.net.
Escape character is '^]'.
# aprsc 2.1.14-g5e22b37

You may get a reason for the failure if it doesn't connect.

You may need to install telnet? first -? sudo apt install telnet

73,
John



On 16/05/2023 08:38, Kk6qms wrote:

Also I noticed in my IPGATEWAY cfg there were references to old local ip addresses. I corrected those (44ENCAP and TAP lines specifically) and only change I see is that an? "APRS Igate connect failed" message appears right after starting bpq rather than quite a bit after as before. Not sure if IPGATEWAY is involved in mail but that has always worked as well as chat even w incorrect ip entries.

?