Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: Tomi Manninen <oh2bns@sral.fi>
To: Linux Hams <linux-hams@vger.kernel.org>
Subject: Re: PTT with soundmodem
Date: Mon, 02 Feb 2004 14:19:42 +0200	[thread overview]
Message-ID: <1075724381.1263.19.camel@oh2bns.ampr.org> (raw)
In-Reply-To: <3.0.6.32.20040201220959.0079bd30@pop.telus.net>

On Sun, Feb 01, 2004 at 04:55:30PM -0500, Mike Markowski wrote:

>  I'm thiiis close to having my packet set up working in kernel 2.4.24
>  (currently unpatched).  I'm using the user space soundmodem to create
>  interface ax0 -- so I assume I don't need to do a kissattach.  When I
>  use soundmodemconfig to test the setup, I can successfully use the
>  PTT gui button to get my rig to transmit (and also have no problem
>  with PTT when using Tomi's great gMFSK!).  However, while i can
>  receive APRS packets while running xastir, when it tries to transmit,
>  soundmodem complains after the xastir info:
>  
>     Tx: fm AB3AP-0 to APX121-0 via RELAY-0,WIDE-0 UI^ pid=F0
>     =/:B7_;?z&y ab3ap@arrl.net, Avondale PA (XASTIR-Linux)
>   
>     sm[15891]: ioctl: SNDCTL_DSP_SYNC: Device or resource busy (16)
>  
>  I see the LED on my PTT interface briefly light, but not long
>  enough to activate the rig itself before the error above is
>  printed.

The SNDCTL_DSP_SYNC call is supposed to cause the driver to wait
until all samples buffered to the soundcard are actually written to
the output. This is done at the end of each transmission so that 
soundmodem knows when it can release the PTT and switch to RX.

For some reason this now fails and then PTT is released immediately.
Unfortunately the only cause for the failure I can think of, is a 
poorly written sound card driver (I could be wrong though -- what 
is your card btw?).

You could try forcing the driver to half duplex (in the IO tab in
soundmodemconfig) and see if that fixes it. That is not a good solution 
though as it can cause additional latency in tx/rx switching (bad for 
CSMA performance).

Another remedy might be trying the ALSA driver.

(And FWIW, gMFSK uses the same technique to time PTT switching,
but as latencies are not nearly as important in gMFSK, I can always
use half duplex audio IO. That tends to be fool (and poor driver) 
proof... :)

-- 
Tomi Manninen / OH2BNS / KP20ME04


  reply	other threads:[~2004-02-02 12:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-01 21:55 PTT with soundmodem Mike Markowski
2004-02-01 22:09 ` Hamish Moffatt
2004-02-02  6:09   ` Mike Fenske
2004-02-02 12:19     ` Tomi Manninen [this message]
2004-02-06  1:05       ` PTT with soundmodem - solved! Mike Markowski
2004-02-02 15:38   ` PTT with soundmodem Mike Markowski
2004-02-06 21:48     ` 2.6.[012] register_netdev kernel bug Leo Bistmans
2004-02-06 22:52       ` Jeroen Vreeken

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=1075724381.1263.19.camel@oh2bns.ampr.org \
    --to=oh2bns@sral.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox