====== DX Cluster notification ======
One of the main use cases of DAPNET is the DX Cluster notification. Michael ON5MM/DG5MM has written an interface between a DXSpider Cluster and the DAPNET. The initial code can be found here:
[[https://github.com/DecentralizedAmateurPagingNetwork/DxClusterInterface|https://github.com/DecentralizedAmateurPagingNetwork/DxClusterInterface]]

It connects to the DX Spider Cluster ON5MM-2 (dx.on5mm.be::7300) via Telnet. FT4 and FT8 spots are excluded via textfilter and bandmap, the rest is classified by frequency and put in a broadcast queue based on its category (e.g. CW, VHF/UHF, 6m, etc.). The transmitter queues of some german DAPNET-TX are regularly observed and the script interrupts working when queues are getting to large. This prevents the whole network especially during major contests or other periods of high traffic.
For special use cases (e.g. dxspots from 40 MHz- or 70 MHz-band), individual calls to a small number of interested participants are established. If you'd like to participate, please feel free to contact ON5MM.

DX spot notifications cause high traffic. Therefore not every DAPNET TX broadcasts them, only those in the transmitter group //dxclusters//. If you see the categories on your skyper pager but do not receive any content, please talk to your sysop whether he wants to add his transmitter to the group //dxclusters//.

====== Clusterstats ======
{{ https://on5mm.be/images/dapnetstats.png }}
The graph shows the number of received spots, those which are (based on the current queue length, see above) forwarded to DAPNET and their categories.


====== Transmitterqueues ======
{{ https://on5mm.be/images/queue-day.png }}{{ https://on5mm.be/images/queue-week.png }}