| |
ZL3AI > APRDIG 30.03.04 16:48l 262 Lines 9360 Bytes #999 (0) @ WW
BID : 3065-ZL3AI
Read: GUEST
Subj: TAPR Digest, Mar 27, 1/1
Path: DB0FHN<DB0FOR<DB0SIF<DB0EA<DB0RES<ON0AR<EB2BJX<ED1ZAC<ZL2TZE<ZL3VML
Sent: 040330/1422Z @:ZL3VML.#80.NZL.OC #:21663 [Chch-NZ] FBB7.00i $:3065-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
TAPR APRS Special Interest Group Digest for Saturday, March 27, 2004.
1. RE: WI-SYS 7110
2. New tracker design suggestions
3. findU access
4. RE: WI-SYS 7110
5. RE: WI-SYS 7110
6. PC Maps link
7. Re: PC Maps link
8. Filter port
9. Re: New tracker design suggestions
----------------------------------------------------------------------
Subject: RE: WI-SYS 7110
From: "Scott Miller" <scott@3xf.com>
Date: Fri, 26 Mar 2004 20:48:41 -0800
X-Message-Number: 1
If $xxx for a transmit-only tracker is a good deal, I think I need to
re-evaluate my pricing structure. =] Admittedly, they've got a very
professional looking package. But an OpenTracker or TinyTrak3 will cost you
about $30, and a GPS module $60 or so. With the exception of 9600 baud
transmit, I don't see any major difference in features.
My next project's going to look a lot more like this thing. One of my main
constraints, though, is board size - to keep the cost per board down I
really need to constrain the PCB dimensions to fit the PCB house's panels.
Right now I'm working with a 3.9" by 3.15" board, which pretty much rules
out stuff like the reconfigurable jumpers. There's just no room.
Interestingly, I just came up with the same layout with the RJ45's on front
and back. Mine's got the serial ports on back, though. Still not sure
about including a 6-pin DIN.
I think I'll follow this message with a new thread to get an idea of what
people would like to see from a new, open source tracker.
Scott
N1VG
----------------------------------------------------------------------
Subject: New tracker design suggestions
From: "Scott Miller" <scott@3xf.com>
Date: Fri, 26 Mar 2004 21:28:53 -0800
X-Message-Number: 2
As mentioned here previously, I've started work on a follow-on project to
the OpenTracker, tentatively called the OmniPacket. It'll be open source,
and the target price is less than a new KPC-3+. It's intended to be used in
three primary roles:
- Standalone tracker / weather / telemetry station
- UI-Frame digipeater/router
- KISS TNC
While there's no reason it couldn't be programmed with node and mailbox
features, I don't have any interest right now in devoting that much time to
what seems to be a dying mode.
Some of the notable hardware features, as the design stands now:
- 1200 baud Bell 202 or V.23 send and receive
- DTMF encode and decode, for remote command/control functions
- Two true RS-232 ports
- Full speed USB port
- 40 MHz CPU with 60K internal, updateable FLASH memory and 4K RAM
- 32K nonvolatile FRAM
- Real-time clock
- Event counters
- LCD interface (HD44780 style, probably 16x2 or 20x2 format)
- MultiMediaCard flash socket, for at least 32 MB storage capacity
I've thought about integrating a GPS receiver like the Wi-Sys 7110 has, but
I keep coming back to the fact that you've still got to have an external
antenna connected. For many users, it's more practical to use a headless
GPS like the DigiTraveler, and you don't have to worry about signal losses
in your coax. One of the serial ports will be available on the board as a
pin header, though, so there's a convenient place to connect an internal
GPS.
I also hope to be able to provide an option to access the serial ports
through the USB port. For computers without a serial port, you'd get access
to both a TNC and your GPS or other external device without an additional
adapter. Drivers are the main issue here. Linux drivers should be fairly
easy. Windows drivers might take a while.
Some of the software/firmware features I've got planned:
- Access to serial ports through USB
- Download new firmware over the air to avoid having to visit digi site
- Load firmware and configuration from MMC for quick and easy updating
- Connect to external KISS TNCs to act as a multi-radio router
- Use the (optional) LCD to provide HamHUD-like functionality
- Generate waypoints for anti-tracker functionality
Anything you'd use a KPC-3+ for in APRS or OpenTRAC, this thing will do. I
think the hobby has been too long at the mercy of commercial manufacturers
that aren't in touch with the community and can't respond to its needs
quickly enough. Projects like the TinyTrak, TNC-X, HamHUD, Anti-Tracker,
and UIDIGI have done a lot for the hobby, and BayCom's brought some
innovation to the high speed arena, but I think there's still a niche to be
filled.
I don't think I'll be making this one available as a kit, though. It's
mostly surface mount, and hand soldering's not going to be much fun for the
average hobbyist. But thanks to the ease of automated assembly, having it
factory assembled will probably add less to the cost than what I charge now
to build an OpenTracker.
Anyway, I'm taking suggestions for features now. Firmware features of
course can always be changed later, but the hardware design's going to firm
up a lot in the near future, so now's the time to suggest hardware features.
73,
Scott
N1VG
----------------------------------------------------------------------
Subject: findU access
From: Steve Dimse <k4hg@tapr.org>
Date: Sat, 27 Mar 2004 11:00:52 -0500
X-Message-Number: 3
Since I've gotten a couple of complaints already, let me try to preempt
more email complaints by stating there is some sort of internet problem
upstream of the hosting site. As you can see from this traceroute, the
problem is somewhere between Level3 and Allegience in New York City:
traceroute to findu.com (66.78.35.146), 30 hops max, 40 byte packets
1 170.134.203.2 (170.134.203.2) 1.895ms 0.352ms 0.284ms
2 172.16.1.4 (172.16.1.4) 0.431ms 0.402ms 1.409ms
3 170.134.150.6 (170.134.150.6) 0.974ms 0.923ms 0.944ms
4 207.203.24.161 (207.203.24.161) 1.37ms 1.575ms 1.599ms
5 172.25.100.249 (172.25.100.249) 1.681ms 1.743ms 1.956ms
6 205.152.144.90 (205.152.144.90) 2.463ms 2.013ms 1.839ms
7 axr00mia-1-3-1.bellsouth.net (65.83.237.10) 1.96ms 14.78ms 49.148ms
8 pxr00mia-2-0-0.bellsouth.net (65.83.236.18) 2.159ms 2.136ms 12.19ms
9 65.57.174.1 (65.57.174.1) 21.076ms 17.729ms 17.323ms
10 so-7-0-0.mp2.miami1.level3.net (4.68.112.45) 18.455ms 17.335ms 17.385ms
11 as-3-0.bbr1.newyork1.level3.net (64.159.3.253) 88.283ms 37.584ms 37.578ms
12 ge-2-2.core1.newyork1.level3.net (64.159.17.133) 79.256ms 37.612ms 37.559ms
13 intermedia-level3-oc12.newyork1.level3.net (209.244.160.142) 70.506ms
36.996ms 44.603ms
14 jfk11-core1-s0-7-1-0.atlas.algx.net (165.117.192.93) 63.154ms * *
15 ewr10-core1-pos6-0.atlas.algx.net (165.117.50.114) 411.939ms 450.823ms
412.303ms
16 ewr10-edge1-pos6-0.atlas.algx.net (165.117.48.110) 407.706ms 409.061ms
407.139ms
17 66.78.63.34 (66.78.63.34) 435.8ms * 436.524ms
18 66.78.35.146 (66.78.35.146) 413.81ms * 408.565ms
Nothing I can do, sorry. These things tend to clear up pretty quickly though...
Steve K4HG
----------------------------------------------------------------------
Subject: RE: WI-SYS 7110
From: "WalterH" <walterh@k5wh.net>
Date: Sat, 27 Mar 2004 11:06:17 -0600
X-Message-Number: 4
A 30 meter version of this, or the Pocket Tracker would be plenty handy.
Thanks,
Walter/K5WH
----------------------------------------------------------------------
Subject: RE: WI-SYS 7110
From: "Scott Miller" <scott@3xf.com>
Date: Sat, 27 Mar 2004 09:15:36 -0800
X-Message-Number: 5
The modem chip used in my new design won't do 300 baud. However, I've
already written a software-based modulator for the OpenTracker that will.
I'm going to make sure there's a D/A path from the CPU to the audio output -
that way it'll at least be able to send at 300, and probably play back
digitized voice from the flash memory too.
Scott
----------------------------------------------------------------------
Subject: PC Maps link
From: James Smith <k9apr@sbcglobal.net>
Date: Sat, 27 Mar 2004 12:24:43 -0500
X-Message-Number: 6
The PC MAP link on the TAPR is DOA
ftp://ftp.tapr.org/aprssig/maps/PCMaps ... Who takes care of this?
--
TAPR Member
UI-Webserver http://k9apr.no-ip.org
73, James, K9APR
Chairman \ Coordinator
Tri-State APRS Working Group
http://www.tawg.org
mailto:k9apr@tawg.org
Run a APRS Website? Why not join the APRS Webring. http://www.tawg.org/join.htm
----------------------------------------------------------------------
Subject: Re: PC Maps link
From: John Ackermann N8UR <jra@febo.com>
Date: Sat, 27 Mar 2004 13:09:05 -0500
X-Message-Number: 7
James Smith wrote:
>The PC MAP link on the TAPR is DOA
>ftp://ftp.tapr.org/aprssig/maps/PCMaps ... Who takes care of this?
James, I just tried that link via web browser and it worked fine.
73,
John N8UR
jra@febo.com
----------------------------------------------------------------------
Subject: Filter port
From: Robbie WA9INF <mwrobertson@comcast.net>
Date: Sat, 27 Mar 2004 17:38:35 -0600
X-Message-Number: 8
Hi,
I have never used a Filtered Port 14580 with WinAPRS. I can not find the
proceedure so I am asking for help, please.
My first attempt to connect then send a message to SERVER with r/42/113/200
didn't seem to work..
Thanks in advance,
Robbie
----------------------------------------------------------------------
Subject: Re: New tracker design suggestions
From: Brian D Heaton <bdheaton@c4i2.com>
Date: Sat, 27 Mar 2004 23:47:55 -0500
X-Message-Number: 9
Scott,
How about a few GPIO pins and perhaps a multiplexed analog sensor input?
73/N5VFF
---
END OF DIGEST
Read previous mail | Read next mail
| |
