OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   28.12.00 16:03l 168 Lines 6853 Bytes #999 (0) @ WW
BID : 35242_ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 26, 1/4
Path: DB0ABH<DB0CWS<DB0ROF<DK0MNL<DF0HMB<DB0HHW<DB0IL<OZ5BBS<OZ4PAC<OZ2DIZ<
      7M3TJZ<HA3PG<PP5BLU<PY3KW<ZL2TZE<ZL2TZE<ZL2WA<ZL2TCX<ZL2BAU<ZL3VML
Sent: 001227/0309Z @:ZL3VML.#80.NZL.OC #:51720 [Chch-NZ] FBB7.00g25 $:35242_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW


TAPR APRS Special Interest Group Digest for Tuesday, December 26, 2000.

1.  APRS Big Event needed
2. Re: APRS Big Event needed.
3. Re: 1-wire weather stations and aprsd
4. Re: aprsd 2.14 and RedHat 7
5. Re: Help for KB8ROP
6. Re: Installing Win95 on laptop WITHOUT a cdrom drive.
7. Re: Installing Win95 on laptop WITHOUT a cdrom drive.
8. Re: Installing Win95 on laptop WITHOUT a cdrom  drive.
9. Re: 10 Meter 300 baud APRS
10. Re: Installing Win95 on laptop WITHOUT a cdrom drive.
11. Re: Installing Win95 on laptop WITHOUT a cdrom drive.
12. Re: DR-135
13. APRSD questions
14. Re: [APRSSIG] Another BIG APRS Event...
15. Re: [APRSSIG] Another BIG APRS Event...
16. Re: [APRSSIG] Another BIG APRS Event...
17. TigerTrak TM-1 and Etrex
18. second.aprs.net Service Interruption

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

Subject:  APRS Big Event needed
From: Frank Ingle <73545.1210@compuserve.com>
Date: Tue, 26 Dec 2000 11:51:01 -0500
X-Message-Number: 1


----------------- Bob Bruinga said:
> >We can't wait another 4 years for the olympic tourch, but it should be
> >something of general HAM radio interst.  Does anyone know of any
> >
> >Off-shore boaters transiting the oceans?

------------------- Frank Ingle replied:
> 
> Am I missing something here?  Wouldn't this be a perfect 
> way for Navy families to keep track of their loved ones
> while on deployment?
>
 
Thanks to all who remided me that opertional security of
US Navy ships is not taken lightly, making full-time Satelite
tracking a bad idea.

Less than an hour after I sent the suggestion, it occured to 
me that most skippers I know would be very paranoid about
trackers transmitting when they werent supposed to, and 
would probably veto the whole idea in a heartbeat.

I'm still not convinced that the whole idea is bad, just the 
proposed method of implementation.  There are still some
cases where ships want their location to be known for PR
value.  Some examples might be hospital ships, ships on
goodwill tours, ships returning to home port, ships in friendly
ports with crew on liberty, ships involved in widely publicized
rescue operations etc.

Most of the other devices which divulge a ship's position or other 
data are under the active, positive control of the skipper - the horn, 
signal flags, navigation and running lights, flares, RF emissions, 
Wx observations, targeting radar, MOVREPS, deployment schedules, 
etc.  If a skipper is going to be comfortable with a tracker, he would 
need to be confident that it was under his control, too.

What if we set up a tracker that would transmit for 6 hours 
(enough for only one satellite pass - or about 4 fixes at 30 min 
intervals in the satellite window) after a button was pushed?

Additional safeguards could include software to inhibit a tranmission
if the ship's speed worked out to greater than 5 knots. (Kind of like the 
anti-scud limit). This would prevent fixes while underway, except
when being piloted into port, but allow fixes when at anchor or 
tied up.  (I'm thinking this could be done with a SW mod to a Tiny 
Track.)

The ultimate decision of whether to beacon a fix or not would rest
on the skipper's shoulder, (where it should) but he would be
assured that 1) there would be no fix unless he (or his designee)
pushed the button, 2) the tracker would provide only 1 set of fixes 
every time the button was pushed, and 3) It could not accidently 
provide fixes while underway, 4) the button would not be pushed 
unless he was convinced there was significant PR value
for the whole world to know where the ship was.

I suspect many will think this is still a bad idea, but before you
condem it, how about we wait and see whether there is anyone
in the Navy who thinks it could be useful?  If not, it will never
happen anyway.

73

Frank Ingle

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

Subject: Re: APRS Big Event needed.
From: "Gregg G. Wonderly" <gregg@skymaster.c2-tech.com>
Date: Tue, 26 Dec 2000 10:49:47 -0600
X-Message-Number: 2


>I'ts getting kinda boring watching my car sitting in the driveway...:-(
>
>No one's listening because no one is transmitting... no one is
>transmitting because no one is listening...

There are too many parameters in typical APRS setups for people to get happy 
about changing them so that they can use SUNSAT I believe.  It is time for 
APRS implementations to take a step up and provide much more powerful 
configuration management systems that would allow parameters to change based 
on anything that the APRS application can detect such as time, speed (hamhud 
does this), location, recent digi's heard etc.  Hamhud's smart beaconing (I 
have this in JeAPRS too) only lets you change beacon time frequencies.  What 
if you could change the path, the from call, the icon, the frequecy of status 
packets etc all based on the timing of external events.  Profiles should be 
available and easily selectable so that once a configuration works, the time 
spent making it work is not lost due to needing a different config.

People get a lot of flack from other operators, it seems, when they are not 
operating correctly.  We have "memory channels" in the radios now so that 
CTCSS/PL tone setups, TX/RX offsets and other operating parameters are 
preserved.  It seems like APRS needs to take the step and allow "memory 
channels" for operational setups which would allow us to easily select 
"SUNSAT", "FISHING", "RIDING", "TORCH" etc from a list of preestablished 
configs and thus be confident that we can operate correctly and effectively.

....Now I've just created more work to do in JeAPRS before I get to beta 
stage...sigh...
-----
gregg@c2-tech.com  (C2 Technologies Inc)



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

Subject: Re: 1-wire weather stations and aprsd
From: Bruno Quesnel <quesnelb@ve2.ele.etsmtl.ca>
Date: Tue, 26 Dec 2000 12:02:18 -0500
X-Message-Number: 3

Hi all and Rich,

    I'm not familiar with the way to plug the OWW into the computer, but one
thaing that might be easy to implement would be throught the UDP code.  No patch
needed to the software for now.  The only trick would be to get the data from
theproper interface (from the OWW) then use a simple perl script to format the
data
to your server.  Transmit the data both on RF and Internet or to your
convinience...

    A small script is also included in the standard distribution of APRSD for
UDPcommunication that will enable you to send to the server....

Rich Mulvey wrote:

> Hi all:
>
>    Has anyone ever tried to integrate any 1-wire weather stations with aprsd?
> I just picked up one ( a clone of the original Dallas Semiconductor 1-wire
> stations, from a Mexicam company ( http://www.aag.com.mx/weather.html ) that



Read previous mail | Read next mail


 16.11.2026 17:54:11lGo back Go up