OpenBCM V1.07b12 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL1ABS > RSGB     29.06.07 03:39l 34 Lines 1269 Bytes #999 (0) @ WW
BID : 470474ZL1ABS
Read: GUEST
Subj: Re: Latest farce (repeaters).
Path: DB0FHN<DB0NOE<DB0GAP<DB0GPP<DB0OFI<DB0PRT<DB0LHR<F6KFT<F6KFG<DB0ZDF<
      DB0LJ<DB0RES<ON0AR<ZL2BAU<ZL1AB
Sent: 070629/0126Z @:ZL1AB.#06.NZL.OC #:62618 [AUCKLAND] FBB7.00i $:470474ZL1AB
From: ZL1ABS@ZL1AB.#06.NZL.OC
To  : RSGB@WW


My opinion is that it seems to follow the "not so good attitude" of:

"If it isn't expressly stated that it is allowed, then it is FORBIDDEN".

Where I much prefer that Amateur innovation & experimentation not be
stifled. I prefer the position that:
"If it is not expressly prohibited, then it is ALLOWED".

A bit of general discussion & consultation rather than the imposition of
rules by a "few select committee members" would be a far better thing.

It seems no problem (to me) that a repeater/beacon should be allowed to
tell the time once a hour or the temperature or the battery voltage, etc
for that matter. Voice or CW or Packet type announcements should be
allowed.
I'm sure people walking in the bush, at sea, etc would welcome a
temperature report or maybe a time report (in case their watches give up).

We're doing all those things with APRS Packet, so why not an automatic
voice report?

Many unmanned stations need something to report the status back to the
owner/trustee. The report would wait until the repeater users had finished
their QSO, so it wouldn't be blocking normal working.

There is probably a rule saying that a callsign ID must be sent every so
often.

73 de Michael ZL1ABS@ZL1AB.#06.NZL.OC


Read previous mail | Read next mail


 19.05.2024 00:03:51lGo back Go up