| |
ZL3AI > APRDIG 19.09.06 22:11l 109 Lines 4024 Bytes #999 (0) @ WW
BID : D9GIS0HHA01D
Read: GUEST
Subj: [APRSSIG] Vol 26 #30, 3/3
Path: DB0FHN<DB0RGB<DB0MRW<DK0WUE<DB0RES<TU5EX<F3KT<IW2OAZ<IS0HHA
Sent: 060913/1810z @:IS0HHA.ISAR.ITA.EU [OpenBCM] OBcm1.06
From: ZL3AI @ IS0HHA.ISAR.ITA.EU (Tony)
To: APRDIG @ WW
X-Info: Sent with login password
R:060913/1746Z @:IS0HHA.ISAR.ITA.EU #:26342 [27509] FBB7.01.35 alpha
R:060831/0810z @:IW2OAZ.ILOM.ITA.EU $:8692-ZL3AI
R:060831/0808z @:ON0AR.#AN.BEL.EU $:8692-ZL3AI
R:060831/0705Z @:ZL2BAU.#87.NZL.OC #:1265 [Waimate] $:8692-ZL3AI
From: ZL3AI@ZL2BAU.#87.NZL.OC
To : APRDIG@WW
Message: 20
Date: Tue, 29 Aug 2006 08:35:00 -0700 (PDT)
From: Tim Smith <rt_smith_at_yahoo.com>
Subject: Re: [aprssig] Homebrew transmitter
The channel-busy debate is indeed a sticky one. The question to buy or
build is really a no-brainer in my opinion. There are plentiful sources of
surplus HT's, amateur mobiles, convertable commercial rigs that are well
suited for tracker or fixed operations. I bought several IC2A's on ebay
for very low prices which can give you up to a couple of watts with a good
receiver (and is frequency agile). Even the higher power mobile rigs
(relatively small too) go for relatively short money. The best part is,
they all do their part in channel management by observing the golden rule
of "listen before you transmit".
Not having a channel busy indicator serves really only two negatives. One
is that you may trash another posit as well as your own not being
successful. In a busy metro area, you're doomed for failure.
73,
Tim - N1TI
------------------------------
Message: 21
Date: Tue, 29 Aug 2006 12:04:14 -0400
From: "Stephen Brown Jr" <stephen.brown75_at_gmail.com>
Subject: Re: [aprssig] Homebrew transmitter
Ok on the channel busy thing, makes perfect sense now that I think about it.
But in the case of an open tracker, which is encode only, does it know when
or when not to transmit, in the case of the channel being busy for example?
------------------------------
Message: 22
Date: Tue, 29 Aug 2006 09:08:27 -0700 (PDT)
From: "Curt, WE7U" <archer_at_eskimo.com>
Subject: Re: [aprssig] Homebrew transmitter
On Tue, 29 Aug 2006, Stephen Brown Jr wrote:
>Ok on the channel busy thing, makes perfect sense now that I think about it.
>But in the case of an open tracker, which is encode only, does it know when
>or when not to transmit, in the case of the channel being busy for example?
OpenTracker1 has a noise sense, similar to a TinyTrak unit.
OpenTracker2 has full receive capability so can do more yet.
I have my OT1 in the Jeep tied to the speaker out of the mobile rig.
When the squelch opens it won't transmit.
The OT2 will be able to run open-squelch all the time, making one less
adjustment that can screw up my tracker.
--
Curt, WE7U. APRS Client Comparisons: http://www.eskimo.com/~archer
"Lotto: A tax on people who are bad at math." -- unknown
"Windows: Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me: I picked the coordinate system!"
------------------------------
Message: 23
Date: Tue, 29 Aug 2006 09:18:10 -0700
From: "VE7GDH" <ve7gdh_at_rac.ca>
Subject: Re: [aprssig] Homebrew transmitter
Stephen N1VLV wrote...
>Ok on the channel busy thing, makes perfect sense now that I think
>about it. But in the case of an open tracker, which is encode only,
>does it know when or when not to transmit, in the case of the channel
>being busy for example?
Devices like the OpenTracker and TinyTrak don't decode received data,
but they do listen for a signal and hold off transmitting while there is a
signal present. I would say go for your project, but make it a homebrew
transceiver instead of just a transmitter - unless it is in the sub-Watt
range. Either way, you will have more success if you listen before
transmitting. There will always be perfect doubles, but at least you can
get your end to hold off when you know for sure there is already someone
transmitting.
73 es cul - Keith VE7GDH
--
"I may be lost, but I know exactly where I am!"
------------------------------
aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
End of aprssig Digest, Vol 26, Issue 30
Read previous mail | Read next mail
| |
