Could be the observer made a mistake or could be something silly
like you forgot your XIT was on 5 up. Never been there, done that?
---
73, Rich - W3ZJ
> -----Original Message-----
> From: owner-writelog@contesting.com
> [mailto:owner-writelog@contesting.com]On Behalf Of Jon Suehiro
> Sent: Wednesday, November 08, 2000 17:56 PM
> To: Jim Idelson; WriteLog Reflector
> Subject: Re: [WriteLog] FWD: Feature idea [out-of-band
> notification]
>
>
>
> Make sure the concept for LSB and USB included. I
> guess too many people
> never used analog type rig (remember, calibrating LSB
> and USB individually),
> and keep on transmitting in 7,150~7,153 or
> 14,347~14,350 range. (Even I
> said you are transmitting off band, they don't listen !)
>
> 73, Jon nn5t@arrl.net
>
> BTW, I received a warning letter to my operation during
> last year SS. I
> was on 7,296.5 and not splattering at all (and
> bare-hoot). My rig
> frequency reading accuracy is within 2~3Hz on 40m. Then, why ?
>
> ----- Original Message -----
> From: Jim Idelson <k1ir@designet.com>
> To: WriteLog Reflector <writelog@contesting.com>
> Sent: Wednesday, November 08, 2000 7:23 AM
> Subject: [WriteLog] FWD: Feature idea [out-of-band notification]
>
>
>
> Out-of-band notification is not a new idea. I submitted
> the following
> suggestion to Wayne almost a year ago
> ---------- Forwarded Message ----------
>
> FROM: Jim Idelson <jimi@designet.com>
> TO: Wayne Wright <w5xd@alum.mit.edu>
> DATE: Thu, 23 Dec 1999 12:17:04 -0500
>
> RE: Feature idea
>
> Hi Wayne,
>
> Here is a feature idea that I came up with based on my
> own experience:
>
> Feature: License Limits
>
> Description: Allows or inhibits tranmission and entry
> of QSOs when the
> operator
> or station is out of band limits authorized by the
> applicable license(s).
>
> Operation: WriteLog would use a file that describes
> band segments permitted
> for
> each license class in a country. [This file should be
> user-definable so you
> don't have to do the work]. As transmit frequency is
> read back from the
> radio,
> transmission is inhibited and out-of-band QSOs cannot
> be logged. A message
> in
> the message area indicates "TX frequency not
> authorized". When the operation
> is
> multi-operator, the ability to to set a licence class
> parameter for the
> station
> callsign and for each op would be great. Then, when a
> new op logs on, his
> license limits apply.
>
> Comments: This would help greatly in situations where
> there is a lot of
> "packet
> pouncng". We have seen quite a few times when a
> multiplier is worked and
> logged
> out of band. It's easy for this to happen when spots
> are coming from all
> over
> the world on a telnet connection. Working a guy simplex
> in the EU 40m phone
> band isn't hard to do! And, the DX station doesn't
> always tell you! This
> feature would also help prevent accidental
> transmissions on the DX station's
> calling frequency due to forgetting to put the radio in
> split mode. As I
> think
> about it, it would also prevent guys from yelling "
> Hey! Listen in the US
> band!" on the DX transmit freq.
>
> Another situation where this would be useful would be
> in Field Day
> operations
> where there a often many different classes of license
> operating the station.
> Many of these ops are less experienced, etc. Everyone
> would benefit from
> this
> capability - callsign holders and guest ops, too.
>
> If you like it at all, put it on somewhere your list . . .
>
> 73 and happy holidays,
>
> Jim K1IR
>
> --
> WWW: http://www.writelog.com/
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
>
>
> --
> WWW: http://www.writelog.com/
> Submissions: writelog@contesting.com
> Administrative requests: writelog-REQUEST@contesting.com
> Problems: owner-writelog@contesting.com
>
>
--
WWW: http://www.writelog.com/
Submissions: writelog@contesting.com
Administrative requests: writelog-REQUEST@contesting.com
Problems: owner-writelog@contesting.com
|