| |
ZL3AI > APRDIG 10.06.04 10:23l 738 Lines 27296 Bytes #999 (0) @ WW
BID : 3419-ZL3AI
Read: GUEST
Subj: TAPR Digest, Jun 04, 3/8
Path: DB0FHN<DB0FOR<DB0MRW<OK0PPL<DB0RES<ON0AR<ZL2BAU<ZL2BAU<ZL3VML
Sent: 040610/0800Z @:ZL3VML.#80.NZL.OC #:25588 [Chch-NZ] FBB7.00i $:3419-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To : APRDIG@WW
Subject: Re: Solar tetroon Sky Diamond 6 aloft right now!
From: Doug Bade <doug@clecom.com>
Date: Fri, 04 Jun 2004 11:55:45 -0400
X-Message-Number: 44
Yes,
144.39 IS a shared freq, but that has little to do with a shared
network, and or the rules used to implement that sharing... put out
whatever you want on 144.39, We do not need to pass it anywhere....locally
you can do as you please, do not expect the rest of us to bend just because
you say we have to share... it does not work that way...The network is not
required to share anything.... your PTT switch is yours to do as you
please, but a dedicated network has no requirement to appease you...
Doug KB8GVQ
At 11:16 AM 6/4/2004, you wrote:
><The bottom line is this data is not APRS, and in my opinion
>does not belong on the APRS frequency.>
>
>Ah, Steve? What is this "APRS frequency" ? The Great White Father who sits
>in Washington doesn't say there is any frequency assigned to the exclusive
>use of APRS. APRS is supposed to be *sharing* a frequency for experimental
>purposes.
----------------------------------------------------------------------
Subject: 30 Meter Policing needed.
From: "Scott Weis" <kb2ear@kb2ear.net>
Date: Fri, 4 Jun 2004 11:55:55 -0400
X-Message-Number: 45
Hello all,
Last night was a very good night for 30 meter propagation, I was watching it
all with my KAM XL and MixW. I did however see some problems. Anyone who
runs a station on this band needs to take a look at their stations and make
sure we are all on the same frequency. I was seeing stations on both sides
of the center of 10.149.3. Some by quite a lot. I even saw 1 station
transmitting outside the 30m band. I have found the MixW software waterfall
display quite useful in finding all of this. We should all check to make
sure our mark and space are being transmitted on 10.149.2 and 10.149.4. Here
is something I found that may be helpful.
Packet TNCs output two tones that represent a mark and space. The HF tones
are 200 Hz apart (VHF 1000 Hz) regardless of the actual tones the TNC uses.
Each TNC manufacturer may use different tone frequencies. For example:
TNC HF LOW TONE (Hz) HIGH TONE (Hz) CENTER (Hz)
MFJ 1600 1800 1700
PK-232 2110 2310 2210
KAM 1600 1800 1700
KAM XL 2125 2295 2210
KAM 98 2125 2295 2210
PACOMM 1600 1800 1700
The method for calculating the desired DIAL frequency (freq) is:
ASSIGNED FREQ = LSB DIAL FREQ - CENTER FREQ (TNC)
ASSIGNED FREQ = USB DIAL FREQ + CENTER FREQ (TNC)
So for APRS of 30 meters.. Assigned Freq is: 10.149.3
For a 1700 Hz center using LSB the freq would be 10.151.0 and USB would be
10.147.6.
For a 2210 Hz center using LSB the freq would be 10.151.51 and USB would be
10.147.09.
So could we try to all get on the same frequency so we have one network on
30m please??
Thanks and 73
Scott KB2EAR
----------------------------------------------------------------------
Subject: APRS and PIDS
From: Earl Needham <needhame1@plateautel.net>
Date: Fri, 04 Jun 2004 10:01:35 -0700
X-Message-Number: 46
At 08:16 AM 6/4/2004, KC2MMi wrote:
><The bottom line is this data is not APRS, and in my opinion
>does not belong on the APRS frequency.>
>
>Ah, Steve? What is this "APRS frequency" ? The Great White Father who sits
>in Washington doesn't say there is any frequency assigned to the exclusive
>use of APRS. APRS is supposed to be *sharing* a frequency for experimental
>purposes.
I thought that was the statement for 145.79, before the Great QSY. I
thought the Great QSY was to get us out of the way of the sats, on our own
frequency, and away from other users. APRS is no longer experimental, in
my opinion.
Earl
Earl Needham, KD5XB, Clovis, New Mexico DM84jk
SETI@Home: 11589WU/7.52yrs
----------------------------------------------------------------------
Subject: Re: TNC vs PID -was- Re: Solar tetroon Sky Diamond 6 aloft right now!
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 09:05:57 -0700
X-Message-Number: 47
>So, how does the TNC know which PID to accept and which to reject?
According to the KPC-3+ manual, the PID filter option filters all but 0xF0,
which should be exactly what we need to avoid problems on those stations not
running KISS.
Can someone verify if this is problem with TNC-2 clones, and if they have a
PID filter option?
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond - signal loss????
From: "Jason Rausch" <ke4nyv@hamhud.net>
Date: Fri, 4 Jun 2004 11:4:17
X-Message-Number: 48
I'm sorry Bob, but maybe I mis-understood what you are asking. But, I
never asked anyone to change anything. The HamHUD II handles 99% of the
daily packets just fine. It just when the OpenTrac packets from the
balloon started comming in, it would cause the Hud to got nuts and lock up.
And I'll say this again they were comming in every 3 or 4, got to be very
fustrating. Its a matter of the packet having somthing bad in it,
somthing, dare-I-say, not to spec?
With all due respects to the OpenTrac crew, if their packets are not up to
snuff, then they need to change that. I was going to say I wasn't taking
sides, but I guess my previous comment just forced me too. I am ALL FOR
home brewing and developing. Thats why youw ill find the "Build APRS"
slogan on my website several places. That is the exact philosophy that
turned me onto projects like: HamHUD, TinyTrak, PeekPack, PICPAC , APRS
Touch Tone and so on and so on.
Sorry if there was some kind of mis-understanding on my comments.
I will say one thing about this group, its a very un-forgiving group. If
you slip up, you'll get lynched.
Jason KE4NYV
www.ke4nyv.com
RPC Electronics
www.ke4nyv.com/rpc
----------------------------------------------------------------------
Subject: Re: Modes and Frequencies
From: "Bill Vodall" <wa7nwp@jnos.org>
Date: Fri, 4 Jun 2004 09:14:29 -0700
X-Message-Number: 49
>>144.39 is not exclusively APRS any more then the
>>other frequencies are exclusively non-APRS.
>
>Really? Do the people that built the network realize that?
>Are such uses welcome?
We are the people that built the network.
>>There are times when it's reasonable to use the other
>>modes on 144.39 just as there are even more uses
>>for APRS on the other frequencies.
>
>The difference in those halves of that sentence are about
>100 to one. It is ludicrous for you to make such a claim.
Not at all. In many ways I'm following up on your ideas and suggestions.
Techniques like "voice" on 144.39, using APRS station ID's on BBS and
personal mail boxes on all other packet channels. We use Connected Mode
on 144.39 to admin remote digipeaters. We use TCP/IP to get in and tweak
remote servers. It's all good magic that makes things work better.
>>Our systems have to be tolerant of all alien packets.
>
>Yes, BUT IT IS COMMON KNOWLEDGE FOR THE
>LAST 26 YEARS THAT TNC's dont all consistently
>implement the AX.25 protocol!
Then they are junk and need to be sent to the museum. Any and I mean ANY
system that locks up or misbehaves when it receives an unexpected packet is
broken and needs to be fixed or removed from service.
>Please do not plan on using non APRS protocols on the
>national APRS channel.
Sorry. If a Netrom/TCP/OpenTRAK/RadioMirror sneaks in one way or another
and an APRS (or any other) application breaks. That application needs to
be fixed.
Besides, I plan to use APRS protocols and applications on some local packet
channels and the same applies. The applications all have to be tolerant of
others packets.
The "old" scheme of segregating modes and frequencies in Amateur Radio is
obsolete just as it is in other frequency management arenas. This is the
era of smart - cognitive - radio systems. Holding to modes and channels
is holding back progress...
Bill - WA7NWP
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond - signal loss????
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 09:13:19 -0700
X-Message-Number: 50
>And why in this gentlemens service called Amateur Radio
>does someone think he can transmit packets that are
>NOT compatible with the present use of a national channel,
>and then insist that all 20,000 existing users have to
>CHANGE their receivers to ignore him?
Please, demonstrate the incompatibility you speak of. The packets sent
yesterday were seen by hundreds of APRS stations. We've had one report of
a possible HamHud II problem (it's yet to be proven to be OpenTRAC
related), and a parsing problem on FindU that could be fixed in minutes if
Steve chose to.
Scott
N1VG
----------------------------------------------------------------------
Subject: Sky Diamond 6 landing site prediction
From: "Rochte, Robert" <rrochte@gpacademy.org>
Date: Fri, 4 Jun 2004 12:03:54 -0400
X-Message-Number: 51
Based on all available data, I believe that the balloon is somewhere in
Fayette County, Pennsylvania. More specifically, it is probably just south
of the midpoint of a line drawn from South Connellsville to Normalville.
Since the GPS likely powered off during descent, the tracker will not be
transmitting at all. The radio and Opentracker are likely powered up right
now but sitting idle.
If anyone is in that general area and would like to take a look sometime
over the weekend, I would greatly appreciate it!
73,
Robert
KC8UCH
--
Robert Rochte
Director of Technology
The Grosse Pointe Academy
171 Lake Shore Road
Grosse Pointe Farms, MI 48236
Tel. +1 313-886-1221 x155
FAX +1 313-886-1418
www.gpacademy.org
----------------------------------------------------------------------
Subject: RE: How about making OpenTrak part of APRS SPEC?
From: Jeff King <jeff@aerodata.net>
Date: Fri, 04 Jun 2004 11:39:09 -0500 (CDT)
X-Message-Number: 52
Quoting AE5PL Lists <HamLists@ametx.com>:
>This is not a matter of NIH, but a matter of trying to modify the spec
>to incorporate a completely different protocol.
I understand that. But how does one do this? That is what the "NIH" was about.
>>Without change and progress, APRS will eventually die.
>
>Ah, the mantra of all on this SIG who don't get what they want. APRS
>is not dying.
Ahh... but I used the word eventually. Here we are, 5 years after the SPEC was
adopted, and things are static. 20 years from now, will you rs out of phase
>>with reality here.
>
>But it DOESNT as was just clearly demonstrated and
>has been KNOWN for the last 22 years.
But what was clearly demostrated? Did you have a problem with your station? So
far, as of this reading, two individials have reported a problem, both using
homebrew software that is easily fixed.
Facts Bob, not wives tales.
All you and a few others are fanning the flames of fear and distrust. It serves
no purpose at all. Lets hear some actual facts from folks, OK?
>It has to be understood. Some people just
>cannot understand common sense and the Amateur
>Radio environment where most hams just want to
>use the equipment they have rather than having to
>have it obsoleted every time a new hacker comes
>along...
Common sense to me is dealing with facts. What equipment is obsoleted? Not
what you heard from a friend, but facts.
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond 6 aloft right now!
From: "Curt, WE7U" <archer@eskimo.com>
Date: Fri, 4 Jun 2004 09:52:27 -0700 (PDT)
X-Message-Number: 55
On Thu, 3 Jun 2004, Wes Johnston wrote:
>kpc3plus manual says:
>
>PID {ON | OFF}
>default OFF
>When OFF, only those packets with a protocol ID of $F0 (pure AX.25) are
>displayed. When ON, all packets are displayed. Some of the information in
>non-AX.25 packets (for example: TCP/IP, NET/ROM or TheNet) can cause some
>computers to lock up. Net/Rom, TheNet and G8BPQ nodes have a PID of $CF,
>TCP/IP uses $CC and $CD, and standard AX.25 is $F0.
I'm tweaking the tnc-startup.kpc3 file in Xastir so that it sets "PID off".
Any idea whether the KAM uses the same parameter?
--
Curt, WE7U 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!"
----------------------------------------------------------------------
Subject: Worthy???
From: "Brian Riley (maillist)" <n1bq_list@wulfden.org>
Date: Fri, 04 Jun 2004 12:52:19 -0400
X-Message-Number: 56
YES and NO - for the most part they are minor issues and strictly speaking
not worthy of all this hoopla, but it has been my experience over the
beaucoup years I have been involved with the APRS_SIG that, at the very
least, anytime we have one of these grand melees we all come away with a
better understanding of this, at times, unwieldy beast. Further, out of
these passion driven exchanges we generally have sown seeds for a half dozen
new ideas or upgrades over the next six months.
We are all here for the same reason, there are many different 'takes' on it,
hence the confrontations, but in the end we will all benefit ... So let's
all chill, put down the cudgels, and take a deep breath or two before going
on.
--
Cheers ... 73 de brian, n1bq, underhill center, vt, usa
On 6/4/04 11:48 AM, "Scott Miller" <scott@opentrac.org> wrote:
>These are very MINOR issues, not worthy of the massive debate that's been
>going on here for the last 24 hours. The two can coexist with very little
>difficulty.
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond 6 aloft right now!
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 10:04:22 -0700
X-Message-Number: 57
> 144.39 IS a shared freq, but that has little to do with a shared
>network, and or the rules used to implement that sharing... put out
>whatever you want on 144.39, We do not need to pass it anywhere....locally
No one's asking for changes in the APRS network itself. Fortunately, the
digipeaters actually implement AX.25 properly and have no trouble carrying
any type of traffic you throw at them.
Scott
N1VG
----------------------------------------------------------------------
Subject: OPENtrack incompatibilities
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Fri, 04 Jun 2004 13:13:25 -0400
X-Message-Number: 58
>>>"Scott Miller" <scott@opentrac.org> 6/3/04 5:40:35 PM >>>
>... the OpenTRAC packet provides a much greater range
>and resolution (-10,000 to 157,772 meters in centimeter
>increments, if memory serves.)
Why does a balloon need centimeter accuracy, especially when a GPS can
hardly do 10 meters altitude accuracy? I still don't see anything that
OPEN track can do that cannot be done in APRS with backwards compatibility
to the existing users?
Sure it has the advantage of 20:20 hindsight to make an extensible protocol
that is easy for newbee programmers, but that does not justify
incompatibilty with all existing users. Especially when the APRS protocol
allows for any kind of special format that anyone wants to introduce.
Bob
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond - signal loss????
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 10:21:45 -0700
X-Message-Number: 59
>fustrating. Its a matter of the packet having somthing bad in it,
>somthing, dare-I-say, not to spec?
The question is, which packets were causing it? OpenTRAC packets use PID
0x77 and should be ignored by APRS devices. I'll be happy to take a look at
the HH2 source code and see if that's been overlooked, but the APRS spec
itself says that APRS packets will use a PID of 0xF0. And it's not just an
OpenTRAC thing, it's an AX.25 compatibility issue. If you're not looking at
the PID and accidentally QSY to a non-APRS packet channel, you're going to
have problems.
It's also entirely possible the APRS packets were causing problems. The
packets the balloon was sending yesterday were rather long and included
timestamp, position, course and speed, altitude, an email address in the
comment, and temperature and voltage telemetry in the comment as well.
Could be the HH2's APRS parser had trouble with something in that mess.
Plus, it was sending back-to-back packets. Could be the HH2's packet
buffering isn't up to the job.
I'm waiting for membership approval in the HamHUD group. As soon as I get
that, I'll do what I can to help.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Worthy???
From: "Curt, WE7U" <archer@eskimo.com>
Date: Fri, 4 Jun 2004 10:25:40 -0700 (PDT)
X-Message-Number: 60
On Fri, 4 Jun 2004, Brian Riley (maillist) wrote:
> YES and NO - for the most part they are minor issues and strictly speaking
>not worthy of all this hoopla, but it has been my experience over the
>beaucoup years I have been involved with the APRS_SIG that, at the very
>least, anytime we have one of these grand melees we all come away with a
>better understanding of this, at times, unwieldy beast. Further, out of
>these passion driven exchanges we generally have sown seeds for a half dozen
>new ideas or upgrades over the next six months.
Just this morning I've committed changes to the KPC3 and the KAM startup
files for Xastir.
If there are similar parameters for other TNC's, I'd like to hear about
them.
--
Curt, WE7U 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!"
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond - signal loss????
From: "Curt, WE7U" <archer@eskimo.com>
Date: Fri, 4 Jun 2004 10:23:29 -0700 (PDT)
X-Message-Number: 61
On Fri, 4 Jun 2004, Jason Rausch wrote:
>With all due respects to the OpenTrac crew, if their packets are not up to
>snuff, then they need to change that.
I expect that if the HamHud II code is not up to snuff, that they need to
change that.
Really, I've been at this from both perspectives over the years. As a user
of proprietary code, at the mercy of whatever they put in there, and as one
of the developers of an APRS client package. A killer packet (what I call
it), need to be handled by the software. Period. I've handled quite a few
of them, spending a great deal of time capturing them and then finding out
which part of the code was deficient. Every one that I managed to capture
ended up being fixed within a few hours at most.
You have the advantage of the HamHud software being easily upgraded, with
several active developers. Use that advantage.
--
Curt, WE7U 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!"
----------------------------------------------------------------------
Subject: RE: How about making OpenTrak part of APRS SPEC?
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Fri, 4 Jun 2004 12:28:29 -0500
X-Message-Number: 62
>-----Original Message-----
>From: Jeff King
>Posted At: Friday, June 04, 2004 11:52 AM
>Subject: [aprssig] RE: How about making OpenTrak part of APRS SPEC?
>
>Quoting AE5PL Lists <HamLists@ametx.com>:
>
>>This is not a matter of NIH, but a matter of trying to modify the spec
>>to incorporate a completely different protocol.
>
>Iunderstand that. But how does one do this? That is what the "NIH" was about.
I am saying we don't.
>Pete, like it or not, there has to be a mechnism for change
>in APRS. It has to be fair, and the cards must not be
>stacked. In theory, on paper, we have that.
No problem with that Jeff, but incorporating changes to the APRS protocol
and incorporating a completely different protocol are two very different
things. I am saying that OpenTrak is a completely different protocol and
therefore should be handled outside of the APRS spec (and, IMO, outside of
this SIG).
>But what is your solution here? How can Scott work to get
>OperTrak within the APRS system, or are you saying all
>development was frozen in 1999?
Scott made the decision to not work within the APRS system when he began
designing the OpenTrak protocol. It was his decision, not anyone else's.
>>I encourage the OpenTrak developers to continue their trek, but let's
>>quit trying to merge the OpenTrak protocol with the APRS protocol,
>>either in the specification or on the air. It is counterproductive to
>>both.
>
>OK, then why is that? We have had quite a few people that
>have said things like this, but so far, only two have
>provided real factual data about two problems, both easily fixed.
Quite simply put, it is a different protocol. It is not compatible with
the APRS protocol. It has no commonality with the APRS protocol other than
to use AX.25 as a transport.
I don't see where that is "easily fixed".
73,
Pete Loveall AE5PL
mailto:pete@ae5pl.net
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond 6 aloft right now!
From: Doug Bade <dbade@clecom.com>
Date: Fri, 04 Jun 2004 13:34:44 -0400
X-Message-Number: 63
That is not totally true.... The trashed packets into the APRS-IS stream
came from somewhere, are you trying to say all the digi's and I gates
worked correctly??? I doubt it.... there are many non-KPC3+ digi's and
I-Gates out in the network. Are they all supposed to change to kpc3+ or
Kiss mode with computers just to comply with your packets???
Doug KB8GVQ
At 01:04 PM 6/4/2004, Scott Miller wrote:
>> 144.39 IS a shared freq, but that has little to do with a shared
>>network, and or the rules used to implement that sharing... put out
>
>No one's asking for changes in the APRS network itself. Fortunately, the
>digipeaters actually implement AX.25 properly and have no trouble carrying
>any type of traffic you throw at them.
>
>Scott
>N1VG
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond 6 aloft right now!
From: "Robert Bruninga" <bruninga@usna.edu>
Date: Fri, 04 Jun 2004 13:34:24 -0400
X-Message-Number: 64
>>>gregg@skymaster.cytetech.com 6/4/04 10:30:54 AM >>>
>Humm, use 100,000 existing TNCs to further enhance
>the abilities of packet based telemetery systems, or ask
>the community to purchase another 100,000 TNCS,
>radios, antennas tower space, cans etc to support this
>effort on a new frequency with a comparable infrastructure?
>
>Seems to me that the right answer is to fix the cheapest
>to fix problem, and that is the TNCs and the software...
Ill make a deal with you. You can transmit OPEN track on the APRS channel
**WHEN** you have accomplished your objective of getting everyone to
replace all of their TNC's. and all Kenwood users to abandon their
radios...
In the mean time, be a gentleman and keep it off of the national APRS
channel which is composed of 20,000 existing users who dont like to see
their data corrupted by incompatible protocols.
Or use put the OPENtrack centimeter resolution into an APRS spec compliant
experimental packet if it is so important.
Fair enough.
Bob
----------------------------------------------------------------------
Subject: Re: Sky Diamond 6 landing site prediction
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 10:36:08 -0700
X-Message-Number: 65
>Since the GPS likely powered off during descent, the tracker will not be
>transmitting at all. The radio and Opentracker are likely powered up right
>now but sitting idle.
Time to start writing a fallback CWID mode, I guess. I think it's already
on my to-do list.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Worthy???
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 10:35:09 -0700
X-Message-Number: 66
>We are all here for the same reason, there are many different 'takes' on it,
>hence the confrontations, but in the end we will all benefit ... So let's
>all chill, put down the cudgels, and take a deep breath or two before going
>on.
And remember, "It's only a hobby!" =]
Thanks Brian, people do tend to get way too worked up over this stuff.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond 6 aloft right now!
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 10:38:10 -0700
X-Message-Number: 67
>I'm tweaking the tnc-startup.kpc3 file in Xastir so that it sets
>"PID off".
I'll suggest the same to the APRSD folks, if that application is still being
maintained.
Scott
N1VG
----------------------------------------------------------------------
Subject: Re: Solar tetroon Sky Diamond 6 aloft right now!
From: "Curt, WE7U" <archer@eskimo.com>
Date: Fri, 4 Jun 2004 10:41:49 -0700 (PDT)
X-Message-Number: 68
On Fri, 4 Jun 2004, Scott Miller wrote:
>>I'm tweaking the tnc-startup.kpc3 file in Xastir so that it sets
>>"PID off".
>
>I'll suggest the same to the APRSD folks, if that application is still being
>maintained.
Looks like "PID off" is the correct command for KPC-3's and KAM's.
Paccomm: "PIDCHECK". I don't know yet whether it should be on or off.
TAPR2: "MNOAX25". Don't know what state this should be in either.
Others? Anyone with Paccomm or TAPR2 docs that can look up the description
so we can get the clients tweaked?
--
Curt, WE7U 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!"
----------------------------------------------------------------------
Subject: Re: OPENtrack incompatibilities
From: "Scott Miller" <scott@opentrac.org>
Date: Fri, 4 Jun 2004 10:47:52 -0700
X-Message-Number: 69
>Why does a balloon need centimeter accuracy, especially when
>a GPS can hardly do 10 meters altitude accuracy? I still don't
It doesn't. Why do it that way? Because 16 bits wasn't enough. 24 might
be too much, but it's better to align the value on a byte boundary than to
require more elaborate parsing. And someone might actually be able to make
use of it at some point. If Burt Rutan wants to connect a tracker to
SpaceShipOne's inertial navigation system, we're set. =]
>Especially when the APRS protocol allows for any kind of
>special format that anyone wants to introduce.
I'm pretty sure I've posted some examples of OpenTRAC target applications
before, and I'm not going to go into that again right now. I'll try to put
together a presentation on what we're trying to accomplish and why it's not
worth trying to shoehorn into the APRS protocol.
Scott
N1VG
----------------------------------------------------------------------
Read previous mail | Read next mail
| |
