You endup on this pages because you heard this "Dirthy beacon" on 144.475 Mhz or you just make a mistake and you don't know what is going on here. It doesn't matter just click your back button and you are back to your Gooooogle dady !
For all other VHF freaks: YES! this is what you heard on 144.475. Hm, now you are thinking, well it sounds better than it looks, but who cares.

Of course, this is just a testing configuration running in my shack. The actual becon message is not correct and You may be confused with the beacon message but this is the reality:
Ok, now here should be a data, but now it's 04:00 AM and ZZZZzzzz time.
Of course, this page is under heavy construction, so see you soon.
18.02.2006. Revision 1.
So here we are, 01:30 PM, after intial test and beacon reports it is time to post some basic info:

Call sign:
Present loc:
Beacon message:

144.475 Mhz
JN75BB  260m asl
360 mW
6el. DK7ZB yagi QTF 020'
VVV 9A4QV/B JN74BX WWW.RKP.HR/9A4QV (carier 30sec)

Beacon is running in the experimental mode and location for tunning purposes, the frequency will be changed later on according to beacon band map to minimise interference with other beacons running in the region.
So this is the ugly and dirthy beacon, what are you probably looking is the small perforated PCB with chip on it. This is the masterwork of IK0WRB, great idea and performance of Beacon keyer with PIC 16F84 can be found here:
Further ideas:

- keying the 2nd transistor is not the best idea, causing small chirp and unstability in frequency
- much better will be to key the 3rd transistor
For all sugestions fell free to contact me on:
First DX cluster reports:

1037  iv3dxw   144475.0   9A4QV/B   in JN75BB 360mW qtf 20
1044  9a3ge   144475.0   9A4QV/B   59...PLUS