| |
IK2NBV > BEACON 13.05.99 18:14l 38 Lines 1104 Bytes #999 (0) @ WW
BID : 20521-IK2NBV
Read: GUEST
Subj: CP IK2NBV: Re: >> NO RESPECT << ??!!
Path: DB0AAB<DB0PV<DB0ISW<OE7XBB<OE6XHG<OE6XYG<9A0BBS<9A0YKZ<S50BOX<S50ATV<
S50MBL<IV3LAV<IV3AVQ<IW3EFI<IW3HHD<I3NXU<IK2QCA<I1YLM<IK1MAP<IK2HDG<
IK2NBV
Sent: 990513/1046Z @:IK2NBV.IK2HDG.ILOM.ITA.EU #:29363 TSTH143b $:20521-IK2NBV
Original from IK2NBV to ON4KLG@ON0RAT
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ START OF ORIGINAL MESSAGE ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
>Unfortunately, and especially on 14100 Khz, there is always QRM caused by
>some packet operators. Is it really so difficult to let those frequencies
>QRM free ? I am sure that it is really possible because it's simply a matter
>of " ham spirit " ! Instead of transmitting on 14099.85 Khz, why not moving
>a bit downward ?
>
Hello !
Yes it's true, but I think the problem it's of a bad beacon frequency.
It's impossible put a beacon at the middle of a packet range frequency.
So I think it's necessary a revision of bandplan, to have beacons at the
start of the band, or at the end of CW only segment.
The true problem it's this.
Packet have many problems,it's in LSB and so the frequecy counter don't give
the correct indication as a cw emission and this may cause the problems,
packet it's unattended, so it's easy to have a variation of the frequency.
So, it's a a big mistake the use of 14.100 for cw beacon.
Ciao a presto !!
Fredi IK2NBV [Manager pkt-rpt ARI Lombardia]
Read previous mail | Read next mail
| |
