SEARCH
TOOLBOX
LANGUAGES
ON0DST

ON0DST

From ON0DAS

Jump to: navigation, search

ON0DST is an FM repeater running on 145.7125Mhz with a 600Khz negative shift.
A CTCSS tone of 131.8Hz is required to operate it, and a CTCSS tone of 131.8Hz is also transmitted by the repeater. This way users can use a full CTCSS squelch system to avoid hisses and other qrm noise.

SysOps are ON8LTE and ON4BAB, with help from the technical workgroup.

Since november 2008 echolink connectivity was restored by ON8TT (hardware) and ON4SAX (software) running SvxLink on Slax Linux from an offsite location. The SvxLink node is linked to T2BELGIUM to push echolink status messages to APRS.

It is now possible to use the following Macro's to connect to Belgian repeaters through EchoLink:

D11 ON0BA
D21 ON0AN
D22 ON0KB
D23 ON0LIR
D31 ON0DST
D32 ON0DVS
D33 ON0LB
D34 ON0LN
D35 ON0RCL
D41 ON0LFE
D81 ON0FF
D82 ON0KTK
D83 ON0OST
D84 ON0VTI
D91 ON0GB
D92 ON0GRC
D93 ON0WL

Usage: Send the DTMF Tone "D" followed by the Number (eg: D33 or D91)

New Antenna + updated mast

24/03/12: Currently testing new antenna and antenna height.

New ON0DST FM

During the installation of the ON0DST D-Star repeater at the same site of the ON0DST FM repeater, we noticed that the power coming from the TX module of the repeater has dropped significantly.

Power, measured behind the duplexers, is currently around 3W. You have to keep in mind that there is still about 30m coax between the duplexers and the antenna, so the ERP is probably lower.
We are now effectively running a QRP-Repeater :)

The technical workgroup has started building a new repeater, with SVXLink onsite.
Here you can follow the current flow of things:

18/11/09: The RX tranceiver (Motorola M110) has been build into the 4U enclosure. the VK5DJ Repeater
controller has been connected to the tranceivers and the CTCSS decoder module is working after some
debugging. (it seems there are some errors in the print-layer on the PCB. (JP11, JP11, JP12 instead
of JP11, JP12, JP13 as it should be). The latest firmware has been flashed on the VK5DJ controller
and it has been configured for usage with our repeater. The repeater itself should now be ready for
operation. Next step is completing the S57NAN svxlink controller PCB, connecting it to the VK5DJ
controller and the SVXLink Alix PC.
27/10/09: RedDevil has etched the PCB for the S57NAN controller and we received all components
(thx to ON4UDO).
22/10/09 A Philips tranceiver has been build into the 4U enclosure. It will function as TX for the
repeater. Documented power is 25W. Thx to the UBA/RST for providing us with this TRX. An
additional heatsink has been mounted on the tranceiver as well as an airflowtunnel with redundant 
temperature controlled fans. We tested a TX of 90 minutes, which resulted in a temperature of 36°C
on the heatsink and a power output of 24W.
September 2009: The repeater controller VK5DJ is finished. This was actually already done since
a 'backup' repeater was planned for some time now. The controller for this backup repeater will be
used as the main controller for the new repeater. The controller from the current (old) repeater
will then be used for a backup repeater.
September 2009: A 4U 19" enclosure is being used for the repeater. We will be using the VK5DJ
controller as the main repeater controller. On the gateway port will be a S57NAN SvxLink
controller, which is connected to an Alix PC running Debian and SVXLink.
Measuring will be done of the supply voltage, as well as a detection system for 220v mains (to see
when we are running on battery). We would like to measure several other things like FWD and REF
power, and ofcourse calculate the SWR. All this data could then be dumped onto the APRS network.
An alert signal can be provided to the VK5DJ controller, which on his turn will generate a different
rogerbeep on alert. This will notify the sysops that something is wrong and they can then use
various APRS websites as a log to see what is going on.