| |
ZL3AI > APRDIG 04.11.03 15:09l 169 Lines 5926 Bytes #999 (0) @ WW
BID : 2269-ZL3AI
Read: GUEST
Subj: TAPR Digest, Nov 02, 3/3
Path: DB0FHN<DB0FOR<DB0MRW<DB0ERF<DB0FBB<DB0GOS<ON0AR<WB0TAX<SP7MGD<VK3TE<
ZL2BAU<ZL2BAU<ZL3VML
Sent: 031104/1241Z @:ZL3VML.#80.NZL.OC #:12237 [Chch-NZ] FBB7.00i $:2269-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Deluo GPS question
From: KC7ZRU <kc7zru@arrl.net>
Date: Sun, 02 Nov 2003 13:20:49 -0700
X-Message-Number: 16
John Kraus wrote:
>Does anyone know of a source for this GPS or a similar one that does not
>bundle software? I don't want to buy the Street finder package. It is a
>real shame that they don't seem to be selling the GPS plain.
Do you mean a source other than *the* source??
http://www.deluo.com/Merchant2/merchant.mv
----------------------------------------------------------------------
Subject: RE: Deluo GPS question
From: <mike@hatzakis.net>
Date: Sun, 2 Nov 2003 12:51:51 -0800
X-Message-Number: 17
I am very happy with my deluo and TTx3. Th combined package was less than
$200
----------------------------------------------------------------------
Subject: Re: Deluo GPS question
From: KC7ZRU <kc7zru@arrl.net>
Date: Sun, 02 Nov 2003 14:25:31 -0700
X-Message-Number: 18
KC7ZRU wrote:
>John Kraus wrote:
>
>>Does anyone know of a source for this GPS or a similar one that does not
>>bundle software? I don't want to buy the Street finder package. It is a
>>real shame that they don't seem to be selling the GPS plain.
>>
>
>Do you mean a source other than *the* source??
>
>http://www.deluo.com/Merchant2/merchant.mv
DOH!!
Now I get it - sorry. Yea, they do seem rather insistant on bundling
something with their recievers don't they.
73
----------------------------------------------------------------------
Subject: Re: Well, it didn't work...
From: "Spider" <spider@rivcom.net>
Date: Sun, 2 Nov 2003 16:11:23 -0700
X-Message-Number: 19
>Nice answer -- I'm taking the 9600 BPS audio from the data plug on
>the back of the '1500. Isn't that generally agreed to be discriminator output?
>
> Earl
Earl, I'd have to look at the schematic to determine that. If the pl tone
circuits mute it, then it's not raw discriminator audio and there is gate in
the way. I'd look at the print and see where this gate is and pick off the
other side of it...closer to the discriminator.
Jim
----------------------------------------------------------------------
Subject: RE: KPC3+
From: "Georgette Sampson" <georgette.sampson@cox.net>
Date: Sun, 2 Nov 2003 19:18:38 -0600
X-Message-Number: 20
>Well, the answer to that is to stop dealing with the commercial market,
>whenever possible.
It's not possible. In the day of surface-mount designs, we're talking robots
to assemble products of any sophistication, and the setup charges are quite
hefty. (I'm not talking about a PIC on a Perf).
>The open source movement fits well with the ham
>philosophy - there's a good reason Linux has had AX.25 support since the
>earliest versions.
Software yes, hardware (mostly) no. Someone still has to shell out money to
the hardware houses (they don't do open source).
>I've spent quite a bit of time developing the OpenTracker, and yet I don't
>plan to make any money from it. One of the main features that sets it apart
>from the commercial TT3 is the ability to upload new firmware in the field -
>firmware that I'll provide for free, or that you can write and upload
>yourself if you're so inclined.
It's basically a retread of ax.25 simplex digipeater with a different data
protocol, right? New baud rate? New band? How does it push the current
technology? Will it be better than a (non-open source) GPS cell phone? :-)
----------------------------------------------------------------------
Subject: Re: Well, it didn't work...
From: "Georgette Sampson" <georgette.sampson@cox.net>
Date: Sun, 2 Nov 2003 19:22:31 -0600
X-Message-Number: 21
It's a one-chip design. Probably shuts down the whole squelch section.
----- Original Message -----
>
>Earl, I'd have to look at the schematic to determine that. If the pl tone
>circuits mute it, then it's not raw discriminator audio and there is gate in
>the way. I'd look at the print and see where this gate is and pick off the
>other side of it...closer to the discriminator.
>
>Jim
----------------------------------------------------------------------
Subject: RE: KPC3+
From: "Scott Miller" <scott@3xf.com>
Date: Sun, 2 Nov 2003 19:46:13 -0800
X-Message-Number: 22
>>Well, the answer to that is to stop dealing with the commercial market,
>>whenever possible.
>It's not possible. In the day of surface-mount designs, we're talking robots
>to assemble products of any sophistication, and the setup charges are quite
>hefty. (I'm not talking about a PIC on a Perf).
That's why I said whenever possible. Often it's not. But software defined
radios let us minimize the amount of hardware that needs to be fabricated.
And I've seen some rather complex circuits reflow soldered in a toaster
oven.
>Software yes, hardware (mostly) no. Someone still has to shell out money to
>the hardware houses (they don't do open source).
Very true, though there is a growing open hardware movement.
>It's basically a retread of ax.25 simplex digipeater with a different data
protocol,
>right? New baud rate? New band? How does it push the current technology?
>Will it be better than a (non-open source) GPS cell phone? :-)
I'm the first to admit that it's nothing new. I'm not a research scientist,
and I'm not even an electrical engineer. I'm just trying to get some useful
tools out there for people to build on. Just because it doesn't push the
envelope doesn't mean it can't serve a useful purpose.
And as for the cell phone comparison, I've got a Motorola phone that runs
Qualcomm's BREW. It's got tons of memory and processing capacity, but you
know what? It doesn't do me a damn bit of good because I can't write code
for it without spending thousands on development tools and code signing
fees. And do you think what the service providers charge for SMS messages
has any relation to what it actually costs to provide the service?
Scott
N1VG
---
END OF DIGEST
Read previous mail | Read next mail
| |
