| |
PA2AGA > HDDIG 01.01.00 04:10l 242 Lines 7715 Bytes #-9631 (0) @ EU
BID : HD_99_324C
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/324C
Path: DB0AAB<DB0PV<OE2XOM<OE5XBL<OE3XSR<OK0PBX<OK0PAD<OK0PPL<DB0RGB<DB0MAK<
DB0SON<DB0ERF<DB0SHG<DB0SM<PI8DAZ<PI8GCB<PI8WNO<PI8VAD<PI8HGL<PE1NMB<
EA7URC<PE0MAR<PI8VNW
Sent: 991231/2126Z @:PI8VNW.#ZH2.NLD.EU #:40308 [HvHolland] FBB7.00g $:HD_99_32
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA27389 ; Fri, 31 Dec 99 19:50:42 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00017365 ; Fri, 31 Dec 99 17:33:12 MET
Date: Fri, 31 Dec 99 17:19:03 MET
Message-Id: <hd_99_324C>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/324C
X-BBS-Msg-Type: B
access messages on packet? And (once I am verified that
I in fact have a license) allow sending packet messages
(sysop approval okay)? I could then read, receive and
send packet mail and posts without my having to set up
radio equipment. I would appear to be associated with
a BBS: wa2ise@xxnxxx
>.
------------------------------
Date: Fri, 24 Dec 1999 07:25:56 -0600
From: "Daniel nicholson" <dnicholson@socket.net>
Subject: Any web or telnet sites via internet access to packet?
Keep at it Dale. It is a learning curve but it is a short one!! One thing I
do hope is that there is plenty of packet activity in your area. Here it has
dropped to a few die hards <Me for one> . what kind of bugs do you have? I
am not an expert but I have been on packet for 10 years..
I will try to help if I can...
Dan
>
>Boy, I wish that were my experience. I have spent numerous DAYS trying to
get
>my system to work. I have yet to be successful at getting all the bugs out
so
>I can send and receive a message.
>
>Perhaps it's due to the fact that I have never been on any digital ham
system
>before, just voice and good 'ol CW. Anyway, I hope it's just a learning
curve
>issue. Sure is discouraging...
>
>Dale
>
>.
------------------------------
Date: Mon, 27 Dec 1999 06:28:48 GMT
From: Dale Gillilan <positivechanges.hypnosis@gte.net>
Subject: Any web or telnet sites via internet access to packet?
Thanks for the offer, Dan. I'll take you up on it.
In all honesty, I think I've covered a lot of the learning curve. I've
figured
out how to get the modem (tnc) to work, etc. My problem seems to be in
getting
the software to work. Here is what happens:
I can send the modem commands and it responds if I use the native
communication
program in my palmtop (I'm using an HP 200lx running DOS 5.x). The tnc (an
MFJ
1278) will send back "data." I put it in quotes, because I've never figured
out
exactly what I'm listening to (fax, Pactor, Amtor, RTTY, etc.), so I'm always
just guessing at what mode to put the tnc in. As a result, I never get any
really readable info.
Anyway, back to my symptoms. I've tried running Baycom (1.5 and 1.7) and
MFJCom
and MultiCom (MFJ). They totally hang up my pc when I send a command to the
tnc.... I've recently tried the trial version of XPCom. It seems to be
working
ok so far (again, I don't know what I'm listening too, but at least it's not
hanging the system). However, I need to be able to get fax, etc. as well as
messages.
I live on a sailboat and will be cruising off shore with my family soon, so
having the full capability of my tnc is very important for me (it could even
be
a matter of safety and survival).
I would appreciate ANY suggestions you might have.
Thanks,
Dale
Daniel nicholson wrote:
> Keep at it Dale. It is a learning curve but it is a short one!! One thing I
> do hope is that there is plenty of packet activity in your area. Here it has
> dropped to a few die hards <Me for one> . what kind of bugs do you have? I
> am not an expert but I have been on packet for 10 years..
> I will try to help if I can...
>
> Dan
>
> >
> >Boy, I wish that were my experience. I have spent numerous DAYS trying to
> get
> >my system to work. I have yet to be successful at getting all the bugs out
> so
> >I can send and receive a message.
> >
> >Perhaps it's due to the fact that I have never been on any digital ham
> system
> >before, just voice and good 'ol CW. Anyway, I hope it's just a learning
> curve
> >issue. Sure is discouraging...
> >
> >Dale
> >
>.
------------------------------
Date: Sat, 18 Dec 1999 15:06:06 -0500
From: "Rob" <NoEmail@NoWay.com>
Subject: Connecting sound card to Computer
I heard that it is NOT a good idea to connect both channels (Left and Right)
of the sound card's line output to the Rig's mic input. It might cause
distortion. (On the other hand, I heard it doesn't matter whether the rig's
speaker output is connected to both channels of the sound card's line input
or mic input).
Is this true? Will there be distortion?
I also heard if you just used a mono plug for the sound card's line output
(or speaker output), it will short out one of the channels and may cause
distortion. It is best to use a stereo plug and only use one of the
channels. Is this good advice?
73's
Rob
VA2FB
>.
------------------------------
Date: Tue, 21 Dec 1999 13:35:37 -0500
From: Bob Lewis <aa4pb@erols.com>
Subject: Connecting sound card to Computer
> BUT I heard it is a different story for the MIC input.
> I was told that the mic jack on a sound card is a MONO
> circuit but uses a STEREO JACK with one channel carrying
> the audio and the other carrying a DC voltage for the mic.
> It was suggested that I use a STEREO connector and ONLY
> use the TIP which carries the audio. (AND DON'T USE the
> RING which carries the polarizing voltage).
>
> Since HAMS like me sometimes plug cables in the wrong jack
> (especially if the mic and line input jacks are beside each
> other), it sounds to me like a good idea to only use one
> channel carried in the tip (even if you PLAN to connect it to
> the line input jack where it doesn't matter)
>
> Any thoughts?
>
> Rob
If your mike is set up that way then you do want to use the tip only and
you are right, it's best to do it that way for consistancy. I don't know
of any benefit to feeding both channels.
>.
------------------------------
Date: Tue, 21 Dec 1999 14:25:15 -0500
From: "Bob Lewis" <aa4pb@erols.com>
Subject: Connecting sound card to Computer
I would guess that in most sound cards the mike bias voltage is
supplied via a large value resistor so that shorting it to ground
will not do any damage to the sound card. In most cases the drive
impedance of your receiver's audio circuit is low enough that there
won't be any problems there either. Still, it's a good practice to
*not* connect the mike tip connection.
Rob Janssen <nomail@pe1chl.demon.nl> wrote in message
news:slrn85ujcs.du5.nomail@linux.pe1chl.ampr.org...
> Rob <NoEmail@NoWay.com> wrote:
> >DO NOT USE the TIP of the connector. Leave it unconnected!
>
> >This is the best approach! If you accidentally plug this cable
into the MIC
> >jack of the sound card instead of the LINE INPUT, you will not
cause any
> >damage to your sound card! In fact, the cable will even work and
provide an
> >audio signal from the radio to your sound card!
>
> >(If you don't follow this recommendation, you MIGHT damage your
sound card.
> >It depends on whether your sound card has any short circuit
protection etc)
>
> I presume that anything that uses a (mini-)jack connector has some
form
> of short circuit protections, as these connectors routinely short
out their
> connections when plugging in/out or fondling with the connector to
find
> the spot of good ground contact.
>
> Normally there is a small regulator on the card to provide the
voltage,
> and it is short-circuit protected. It could run a little hot when
left
> shorted all the time.
>
> A better recommendation seems to always use AC-coupling on the
soundcard
> inputs, so if you use a transformer, put a (say 1uF) nonpolarized
cap
> in series. Or a resistor of sufficient value to reduce the
current,
> and small enough in relation to the input impedance. 4k7 or so.
To be continued in digest: hd_99_324D
Read previous mail | Read next mail
| |
