OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   27.02.04 19:49l 286 Lines 9429 Bytes #999 (0) @ WW
BID : 2912-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 25, 1/6
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<EB2BJX<KD7HAH<WA7V<VK7AX<ZL2BAU<
      ZL3VML
Sent: 040227/1323Z @:ZL3VML.#80.NZL.OC #:19954 [Chch-NZ] FBB7.00i $:2912-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

TAPR APRS Special Interest Group Digest for Wednesday, February 25, 2004.

1. Re: Uncompressed vs Compressed formats
2. Destination Addresses
3. Re: FW: APRS Client Survey
4. Re: FW: APRS Client Survey
5. Re: FW: APRS Client Survey
6. Re: FW: APRS Client Survey
7. Compiled Data from APRSWORLD
8. Re: Destination Addresses
9. Re: FW: APRS Client Survey
10. RE: Destination Addresses
11. Re: FW: APRS Client Survey
12. Re: Destination Addresses
13. Re: house beacon location
14. Survey was Re: Uncompressed vs Compressed formats
15. Re: house beacon location... client software.
16. Re: AGWTracker
17. Re: Destination Addresses
18. Re: Wider paths than Wide2-2
19. XML and findu
20. RE: APRS Client Survey
21. Re: Uncompressed vs Compressed formats
22. RE: Spam:XML and findu
23. DIGIpeater TOCALL Standard please
24. Re: APRS Client Survey
25. Re: Uncompressed vs Compressed formats
26. Re: APRS Client Survey
27. Re: Destination Addresses
28. APRS Destination Holes
29. Re: APRS Destination Holes
30. Re: APRS Client Survey
31. Re: Uncompressed vs Compressed formats
32. Re: FW: APRS Client Survey
33. Re: DIGIpeater TOCALL Standard please
34. Re: Uncompressed vs Compressed formats
35. Re: DIGIpeater TOCALL Standard please
36. Re: DIGIpeater TOCALL Standard please
37. APRS37, etc.
38. Re: DIGIpeater TOCALL Standard please
39. Re: DIGIpeater TOCALL Standard please
40. Re: Uncompressed vs Compressed formats
41. Re: DIGIpeater TOCALL Standard please
42. Re: DIGIpeater TOCALL Standard please
43. Re: DIGIpeater TOCALL Standard please
44. GPS Question
45. Re: Destination Addresses
46. Re: Destination Addresses
47. Re: FW: APRS Client Survey
48. Oncore problems....still
49. Anyone use APRSPoint?
50. Re: Canadian topo maps done!
51. Re: Canadian topo maps done!
52. GPS from Vaisala radiosonde

----------------------------------------------------------------------

Subject: Re: Uncompressed vs Compressed formats
From: "Scott Miller" <scott@3xf.com>
Date: Tue, 24 Feb 2004 20:55:39 -0800
X-Message-Number: 1

I want a copy of that t-shirt too.  =]  In an 8-bit microcontroller, you
ain't doin' squat with a 32-bit value in 1 instruction!

I got my encoder working.  The first compile had me in Iran.  Almost got it
on the first try.  Here's the code that builds the compressed position:

  base91(1073741824L - lastfix.latitude, lastfix.aprs_position);
  base91(1073741824L + (lastfix.longitude >> 1), lastfix.aprs_position+4);

And the function itself:

// Converts semicircles to Base 91 units (must be properly biased first)
char *base91(long semi, char *s) {
	// (2^31 / 180) / 380926 semicircles per Base 91 unit
	const unsigned long b91val[4] = {23601572L, 259358L, 2851L, 32L};
	char c;

	for (c=0; c<4; c++) {
		s[c] = '!';
		while (semi >= b91val[c]) {
			semi -= b91val[c];
			s[c]++;
		}
	}
	return (s);
}

The function takes 191 bytes of code, and the calls to it take 59 bytes, for
a total of 250 bytes of code.  Haven't made any attempt to optimize it yet.
Of course, there'll also be the overhead of identifying which format to use
and all that.

Unfortunately that's more program space than I had left.  I had to comment
out a block of telemetry code to get it to fit.  So now begins the
hand-optimizing and ugly hacks to make everything fit.  =]

Scott
N1VG

-----Original Message-----

>That should take 1 line of assembler

Can I put that expression on a T-Shirt? You must be related to a boss I once
worked for  :-0

----------------------------------------------------------------------

Subject: Destination Addresses
From: "Christensen, Eric" <CHRISTENSENE@MAIL.ECU.EDU>
Date: Wed, 25 Feb 2004 00:00:54 -0500
X-Message-Number: 2

Does this list agree with everyone?  Any additions?

APA A-Filter, Alinco, etc
APAFxx AFilter.
APAGxx AGATE
APAXxx AFilterX.
APAHxx AHub
APB avail
APC Windows CE, etc
APD APRSd, etc
APDTxx APRStouch Tone (DTMF)
APE avail
APF avail
APG Gates, etc
APH HamHud, etc
API Icom, etc
APICQx for ICQ
APJ JavaAPRS,JeAPRS,etc
APK Kenwood, etc
APK0xx THD7's
APK1xx D700's
APL Liunx applications
APM MacAPRS, etc
APN Network nodes, digis, etc
APNU-UIdigi
APO APRSpoint
APP pocketAPRS, etc
APQ avail
APR APR8xx APRSdos,etc
APRDxx APRSdata, APRSdr
APRKxx APRStk
APRS Generic, (obsolete. Digis should use APNxxx instead)
APRXxx APRSmax
APRTLM used my MIM's and Mic-lites, etc
APS APRS+SA, etc
APT TinyTrack
APTTxx Tiny Track
APT2xx Tiny Track II
APTAxx K4ATM's tiny track
APTV for ATV/APRN and SSTV applications
APU UIview, etc
APU1xx UIview 16 bit applications
APU2xx UIview 32 bit apps
APV avail
APW WinAPRS, etc
APX Xaprs, etc
APY etc, Yeasu, etc
APZ Experimental
APZ0xx Xastir
APZPAD Smart Palm

----------------------------------------------------------------------

Subject: Re: FW: APRS Client Survey
From: Steve Dimse <k4hg@tapr.org>
Date: Wed, 25 Feb 2004 00:01:00 -0500
X-Message-Number: 3

On 2/24/04 at 11:30 PM Christensen, Eric <CHRISTENSENE@MAIL.ECU.EDU> sent:

>Steve,
>My reasoning for sending the letter to the UI-View Listserv (and other
>lists) was to get the message out to as many APRS Users as possible.  There
>are a lot of people on the UI-View list that use other programs as well.  I
>have heard many members on that list talk about Xastir, WinAPRS, etc.  I
>also encouraged others to forward that message on to other lists as to
>propagate the request as far as I can.  I am not being selective...  I am
>trying to give as many APRS users (that have e-mail) a voice.

I understand that, but again, the difficult part of statistics is getting
good data. In medical school, a project like this would result in a failing
grade, no matter how well the stats are performed and presented, as the
student completely missed the points we are trying to teach them. As I say,
business school may be trying to teach something else, but I sure hope not,
I'm counting on businesspeople to make my investments grow!

>You are also correct about the email addresses being faked.  But I would
>HOPE that no one would do that.

After living through a few hundred of "the program I use is better" threads
on this SIG over the last 10 years, I'd bet there would be more than a few
multiple voters even if you explicitly said one-person-one-vote. However,
your call for votes never said that, it said one vote per email address, so
a person isn't doing anything unethical...

>Even if you use a "random" sample of users, it still could be skewed.  The
>ONLY way to get the proper data would be to do a census of ALL the APRS
>users... But I don't have the manpower to go door-to-door.  Now, with that
>data from APRSWORLD... If someone can provide me with the key to what all of
>those destinations come from, I'll be happy to compile that data as well.
>It would be very interesting to see how that data would compare with the
>survey I am doing.  But, that data would only see stations that actually
>make it into the internet.

Again, it is important to keep in mind what you are measuring, and state
your results accordingly. This is an unscientific poll, its results cannot
be said to imply anything about the actual use of any client program. Your
result need to be stated something like "After advertising on the APRS SIG,
UI-View list (and any other places) responses from n different email
addresses were received, and the percentages are...".

Is using a sample derived from the APRS Internet system bias free? No, and
I said that from the first time I suggested it. Yet a sample based on 32000
stations is more likely to be closer to the true usage of client programs
than the few hundred you are likely to garner with a survey.

>I'm sure there are more than a few users that
>cannot access an I-Gate that are on this listserv (I am one of them).

Yet two of your stations make it to findU:

http://findu.com/cgi-bin/find.cgi?call=KF4OTN*

Steve K4HG

----------------------------------------------------------------------

Subject: Re: FW: APRS Client Survey
From: Steve Dimse <k4hg@tapr.org>
Date: Wed, 25 Feb 2004 00:02:41 -0500
X-Message-Number: 4

On 2/24/04 at 9:29 PM Earl Needham <needhame1@yucca.net> sent:

>I'm not sure if this is what Steve meant or not, but using the
>above link, I get the following result:

Close, but you would also combine the different version of the same
program, and then match the abbreviation with the client name.

Steve

----------------------------------------------------------------------

Subject: Re: FW: APRS Client Survey
From: Earl Needham <needhame1@yucca.net>
Date: Tue, 24 Feb 2004 22:04:58 -0700
X-Message-Number: 5

At 10:02 PM 2/24/2004, Steve Dimse wrote:
>On 2/24/04 at 9:29 PM Earl Needham <needhame1@yucca.net> sent:
>
>>I'm not sure if this is what Steve meant or not, but using the
>>above link, I get the following result:
>>
>Close, but you would also combine the different version of the same 
>program, and
>then match the abbreviation with the client name.
>
>Steve

That might be a problem, as I don't know what they all are!  <G>

Give me the rundown on this and I'll try to get it all going when
I get back.  In spite of the snow and all, I have to take a 25-ton milk 
shake to Dallas tomorrow...

7 3
Earl

Earl Needham, KD5XB, Clovis, New Mexico  DM84jk
KD5XB-2>APW251,PCSAT-1%:=3425.83N/10313.55W-PHG7150/WinAPRS 2.5.1 
-EARL_CLOVIS -251-<630>
SETI@Home:  11385WU/7.39yrs

----------------------------------------------------------------------



Read previous mail | Read next mail


 11.10.2026 20:03:51lGo back Go up