All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Lassoff <jlassoff@gmail.com>
To: linux-hams@vger.kernel.org
Subject: Re: Soundmodem Not Decoding Real Packets
Date: Fri, 1 Jul 2005 23:56:54 +0000 (UTC)	[thread overview]
Message-ID: <loom.20050702T015133-109@post.gmane.org> (raw)
In-Reply-To: 20050701184203.2013.qmail@radagast.org

Dave Platt <dplatt <at> radagast.org> writes:

> In my experience, the user-mode soundmodem code does a very fine job of
> decoding AX.25 packets, and it does so even if the radio is operated
> "open squelch".  In fact, in many areas it is a preferred practice for
> packet nodes to be run with the receive squelch open - this allows
> the TNC or other modem to synchronize very rapidly at the beginning
> of each packet, without a long wait for the radio to detect carrier
> energy and open its squelch.  This, then, allows the nodes in the
> area to use a shorter beginning-of-packet synchronization burst, and
> increase the useful data throughput of the packet channel.
> [...]
> In your situation, I'd look at several things:
> 
> -  Audio levels, as you suggest.  Take a look at the audio coming
>    out of your radio when it's receiving a clean packet - use
>    an oscilloscope.  Check for clipping (a "flat-top" appearance)
>    in the waveform.  If you see it, turn the radio's audio-output
>    control down until it goes away.
> [...]
> Also, check the quality of the signal from the sending station.  It's
> not unusual for TNCs or soundmodems or audio interfaces or radios to
> be misadjusted, causing any of several problems:
> [...]
> My own guess is that that Thomas Sailer's soundmodem code is not
> the cause of your problem.  I've found it to be quite good indeed
> at receiving packet.

I did find out that the audio output from my radio was a bit high.
I don't have an oscilloscope to play with, so I just used audacity to see the
audio while recording it. I trimmed it down so that everything is there. I'm
still having the same problem though. I have also been trying to decode packets
off of APRS here in California on 144.390 to no avail. I also tried the decoding
process with squelch open. I'm not really sure what is going on here. I also
tried twiddling with the audio levels on my input channel in a mixer program.
Any crafty diagnostic ideas?

Jonathan (KG6THI)


  reply	other threads:[~2005-07-01 23:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01  8:01 Soundmodem Not Decoding Real Packets Jonathan Lassoff
     [not found] ` <46479.194.154.200.89.1120206709.squirrel@mail.lx2gt.lu>
2005-07-01 17:34   ` Jonathan Lassoff
2005-07-01 18:42 ` Dave Platt
2005-07-01 23:56   ` Jonathan Lassoff [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-07-02  4:09 Dave Platt
2005-07-02  4:58 ` Jonathan Lassoff
2005-07-02 19:03   ` ariel mastracchio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20050702T015133-109@post.gmane.org \
    --to=jlassoff@gmail.com \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.