From: chuck gelm <chuck@gelm.net>
To: alexandre.chappaz@data-tools.com
Cc: linux-hams@vger.kernel.org, "André HONIG" <andre@data-tools.com>
Subject: Re: kenwood radio & numeric data
Date: Tue, 12 Oct 2004 12:05:24 -0400 [thread overview]
Message-ID: <416C00C4.3060002@gelm.net> (raw)
In-Reply-To: <200410121714.52100.alexandre.chappaz@data-tools.com>
chappaz alexandre wrote:
>Hi guy
>
>I've got a new question for U if you've got time to thing of it.....I wrote
>yesterday to get informations about the Kenwood tm700... radio & Tnc.... Well
>I think I wont manage to achieve what I want using the internal TNC......
>That's why I write again to ask if anyone could give a little help for
>choosing a nice modem (either hardware or software with a sound card) to
>transmit numeric data over radio with the smallest delay possible....... The
>"packet radio" protocol limits the use I want to have because the goal for me
>would be to have a constant data stream over the radio. So if someone knows
>what kind of material i should use it would be really helpful.....
>
>Thanks a lot
>
>Alex
>
>
Hi, Alex:
I have questions also. Your goal seems to be:
"have a constant data stream over the radio".
I do not think that it matters that the data is numeric or other.
Why do you use radio?
Why do you use Amateur Radio?
Why do you use AX.25?
Would 802.11b ( 11 Mbps ) be close enough to 'constant' ?
The closest thing I am aware of that supports 'constant data stream',
or at least constant small delay, is ATM.
If you want 'constant', you need 'full duplex'.
i.e. You need full duplex radios. Perhaps a
'dual bander' capable of full duplex would suit your goal.
Regards, Chuck
next prev parent reply other threads:[~2004-10-12 16:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 15:14 kenwood radio & numeric data chappaz alexandre
2004-10-12 15:31 ` Dennis Boone
2004-10-12 16:05 ` chuck gelm [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-12 19:14 Morgan.Wemanis
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=416C00C4.3060002@gelm.net \
--to=chuck@gelm.net \
--cc=alexandre.chappaz@data-tools.com \
--cc=andre@data-tools.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox