<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://hampager.de/dokuwiki/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://hampager.de/dokuwiki/feed.php">
        <title>DAPNET DokuWiki</title>
        <description></description>
        <link>https://hampager.de/dokuwiki/</link>
        <image rdf:resource="https://hampager.de/dokuwiki/lib/tpl/dokuwiki/images/favicon.ico" />
       <dc:date>2026-05-14T22:49:30+0200</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=9k6"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=a2d"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=alphapocdescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=alphapocwatchdescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=apollo924description"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=aprs2dapnet"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=ax25"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=birdydescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=birdyslimdescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=blogoverview"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=bnetza"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=brandmeistergateway"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetapideletenondsgvo"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetapioverview"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetapisendcall"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetapisendrubricl"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetapisetidentificationaddress"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetfrq"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetinfluxdb2rubric"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetnodeconnectionratelimit"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetnodeinstall"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetnodeshamnet"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetnodesinternet"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetoverview"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetpresentations"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetprotocol"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dapnetproxy"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=dmrplusgateway"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=emergencybroadcast"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=faq"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=ft8500"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=gm360"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=hammessengergateway"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=metar_messages"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=mmdvm"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=monitoringnagios"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=monitoringunipager"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=nagiosnotification"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=nagiosnotificationunipager"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=netsed"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=openspot2"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=openspot3"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=openwebrx"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=pager_comparison"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=pr430"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=primodescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=procedurebuypagingrx"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=procedurenewrubric"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=procedurenewtx"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=procedurenewusecase"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=procedurenewuser"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=queueunipager"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=quixdescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=raspager"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=raspagerc9000"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=rubric"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=rubricactivationother"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=rubricactivationskyper"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=rubricgeneral"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=rubricnumber"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=salt-minion"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=skyperdescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=start"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=swissphonedescription"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=telmi"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=translationinfo"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=transmittergroupgeneral"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=transmittergroupspecial"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=txident"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=umbauten"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=unipager"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=unipagerenglish"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=unipagerled"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=unipagernextion"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=unipagersend"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecasecivil"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecaseclubnews"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecasecwident"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecasedxcluster"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecaseodl"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecasepacketradio"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecaseqthtemp"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecasetelegrambot"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecaseweather"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usecasewinlink"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=usercasepegel"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=uvk5"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=version2_overview"/>
                <rdf:li rdf:resource="https://hampager.de/dokuwiki/doku.php?id=w8008description"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://hampager.de/dokuwiki/lib/tpl/dokuwiki/images/favicon.ico">
        <title>DAPNET DokuWiki</title>
        <link>https://hampager.de/dokuwiki/</link>
        <url>https://hampager.de/dokuwiki/lib/tpl/dokuwiki/images/favicon.ico</url>
    </image>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=9k6">
        <dc:format>text/html</dc:format>
        <dc:date>2022-09-13T13:37:00+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>9k6</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=9k6</link>
        <description>Funkrufsender als SDR - SDRPager

Überblick

Die Amateurfunkgruppe an der RWTH Aachen hat einen SDR Sender für Funkrufsignale nach dem Protokoll POCSAG entwickelt. Dieser benötigt nur einen Raspberry Pi oder einen x86 Rechner. Dieser erzeugt über die Soundkarte das Signal, welches auf einen 9k6 fähigen Sender gegeben werden kann.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=a2d">
        <dc:format>text/html</dc:format>
        <dc:date>2023-09-06T20:46:47+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>a2d</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=a2d</link>
        <description>APRS to DAPNET gateway (2)

This user-friendly Debian application called 'a2d' facilitates the transmission of APRS messages to DAPNET. Initially, NY3W has created this application for personal use, but has the believe it has the potential to benefit the broader DAPNET community as well.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=alphapocdescription">
        <dc:format>text/html</dc:format>
        <dc:date>2025-09-13T18:28:45+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>alphapocdescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=alphapocdescription</link>
        <description>Alphapoc 602R

WARNING

Programming software version 3.22 has a bug that limits ALL text messages received by the pager to 45 characters. Fixed in Version 3.24, see parameter TEXT LENGTH.

Overview

The Alphapoc is a portable paging receiver for POCSAG. It is available at</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=alphapocwatchdescription">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-09T15:48:51+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>alphapocwatchdescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=alphapocwatchdescription</link>
        <description>Alphapoc 801W

Overview

This Alphapoc is quite similar to the 602R, both in construction and in internal structure. Most of the user interface is the same as the 602, and it can be programmed with the same software, and the same programming dongle. 

[Image of Alphapoc 801W, next to the 602 and a Swissphone pager. ]

3D Printed Clip</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=apollo924description">
        <dc:format>text/html</dc:format>
        <dc:date>2023-12-09T02:56:20+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>apollo924description</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=apollo924description</link>
        <description>Apollo 924

Overview

The Apollo 924 is a compact, front-panel programmable POCSAG pager manufactured in Taiwan by the Gold Apollo Co. The display is backlit and supports 4 lines of text which can be zoomed in to two lines. It is available in UHF and VHF; the most recent version supports up to 8 addresses.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=aprs2dapnet">
        <dc:format>text/html</dc:format>
        <dc:date>2019-04-23T15:01:23+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>aprs2dapnet</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=aprs2dapnet</link>
        <description>APRS2DAPNET-Gateway

Jürgen, DL8MA, provides a gateway, which sends direct APRS messages to a related DAPNET-pager. This service is up to now experimental and each entry has to be manually edited by Jürgen (he needs your APRS-ID, your aprs.fi-API-key from</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=ax25">
        <dc:format>text/html</dc:format>
        <dc:date>2018-02-27T11:08:38+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ax25</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=ax25</link>
        <description>Connecting old Packet-Radio only transmitters via AX.25

There are several reasons why one would like to connect an old AX.25 Packet-Radio only Transmitter to the DAPNET:

	*  No possibility to change the hardware due to restrictions or motivation
	*</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=birdydescription">
        <dc:format>text/html</dc:format>
        <dc:date>2019-01-27T17:05:13+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>birdydescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=birdydescription</link>
        <description>TPL Birdy

[TPL birdy, courtesy DL8MA]
TPL birdy, courtesy DL8MA

The TPL Birdy is produced by &lt;https://tplsystemes.com&gt; and was originally designed for usage in French fire departments, therefore they are waterproof (IP67) and robust.

The current version is the Birdy WPs r2 with 128 RICs, each with 4 subaddresses. The older model has only 8 RICs, but the battery lasts with that model for months. Disadvantage of the birdy: Storage for only 20 Messages (each 256 characters).</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=birdyslimdescription">
        <dc:format>text/html</dc:format>
        <dc:date>2019-07-09T20:10:01+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>birdyslimdescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=birdyslimdescription</link>
        <description>TPL birdy slim (IOT)

Still in developement

&lt;https://www.criticalcomms.com.au/content/public-safety/hot-product/tpl-syst-mes-birdy-slim-v2-iot-pager-707746366&gt;

„Normal“ version: &lt;http://shop-radiocom.dk/shop/tpl-birdy-slim-1764p.html&gt; and &lt;https://notrufnoe.com/produkt/pager-birdy-slim/&gt; (german)

Front:



Back:



Main screen:



Received message:



QRGs:



Radios:



Menu Info:



Photos courtesy de DO1PPS</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=blogoverview">
        <dc:format>text/html</dc:format>
        <dc:date>2018-06-05T11:52:16+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>blogoverview</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=blogoverview</link>
        <description></description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=bnetza">
        <dc:format>text/html</dc:format>
        <dc:date>2020-03-10T21:10:05+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>bnetza</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=bnetza</link>
        <description>Template for automated amateur radio stations according to §13 of AFuV

For the application of new DAPNET transmitters, we provide a template of the from avabilable by Bundesnetzargentur here.

Check if your desired callsign is not used yet: Rufzeichenliste.

Page 1:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=brandmeistergateway">
        <dc:format>text/html</dc:format>
        <dc:date>2021-01-25T17:27:42+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>brandmeistergateway</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=brandmeistergateway</link>
        <description>Since January 2017 it has been possible to send messages via the Brandmeister DMR network to the DAPNET. 

Handling: You have to send a message to the Brandmeister-POCSAG-gateway with the private contact 262994.

The content of the message has to be structed as follows:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetapideletenondsgvo">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:10:29+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetapideletenondsgvo</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetapideletenondsgvo</link>
        <description>Just for documentation:


#!/usr/bin/python
import MySQLdb
import requests
from requests.auth import HTTPBasicAuth
import time
import sys

login = 'username'
passwd = 'password'
url = 'http://dapnet.db0sda.hamnet.radio:8080/users'

db = MySQLdb.connect(host=&quot;localhost&quot;,
                     user=&quot;username&quot;,
                     passwd=&quot;password&quot;,
                     db=&quot;dapnet&quot;)

cur = db.cursor()

cur.execute(&quot;SELECT name FROM dapnet.users where dsgvo_accepted='0'&quot;)

for row in cur.fetchall():…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetapioverview">
        <dc:format>text/html</dc:format>
        <dc:date>2018-01-08T11:15:41+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetapioverview</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetapioverview</link>
        <description>Overview of DAPNET REST-API

Until further improvment of this page, please refere to the description on GitHub.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetapisendcall">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:06:25+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetapisendcall</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetapisendcall</link>
        <description>Send individual call via REST-API

Example for curl from linux console

HAMNET


curl -H &quot;Content-Type: application/json&quot; -X POST -u yourcallsign:yourpassword -d '{ &quot;text&quot;: &quot;this is the message&quot;, &quot;callSignNames&quot;: [&quot;destinationcallsign&quot;], &quot;transmitterGroupNames&quot;: [&quot;txgroup&quot;], &quot;emergency&quot;: false }' http://dapnet.db0sda.hamnet.radio:8080/calls</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetapisendrubricl">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:08:42+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetapisendrubricl</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetapisendrubricl</link>
        <description>Send rubric content via REST-API

Example for curl from linux console

HAMNET


curl -H &quot;Content-Type: application/json&quot; -X POST -u yourcallsign:yourpassword -d '{ &quot;rubricName&quot;: &quot;rubric&quot;, &quot;text&quot;: &quot;this is the message&quot; }' http://dapnet.db0sda.hamnet.radio:8080/news</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetapisetidentificationaddress">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:10:45+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetapisetidentificationaddress</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetapisetidentificationaddress</link>
        <description>Set all identificationAddress

By means of this script in python the identificationAddresses of all transmitters can be set to determined value (e.g. 8). It's for information / documentatin only and not necessary for normal user interactions. 


import sys
import time
import json
import requests
from requests.auth import HTTPBasicAuth
 
login = 'callsign'
passwd = 'passwd'
url = 'http://dapnet.db0sda.hamnet.radio:8080/transmitters'
identificationAddress = 8 
 
r = requests.get(url, auth=(login, …</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetfrq">
        <dc:format>text/html</dc:format>
        <dc:date>2024-01-08T23:36:35+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetfrq</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetfrq</link>
        <description>The most used and preferred frequency is 439.9875 MHz but due to some legal restrictions in some countries other frequencies are used (marked in red).
 Country  2m  70cm  Remarks  Austria   438.025   according to bandplan 439.930 would also be possible</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetinfluxdb2rubric">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:10:10+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetinfluxdb2rubric</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetinfluxdb2rubric</link>
        <description>InfluxDB to Rubric Content

DB0NS is solar powered only. The data from the solar charger is placed into a influxdb instance in order to display it with Grafana. In addition, the most critical data is also sent periodically into a rubric.

The Python-Code was adapted from Philipp DL7FL:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetnodeconnectionratelimit">
        <dc:format>text/html</dc:format>
        <dc:date>2018-06-26T20:59:21+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetnodeconnectionratelimit</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetnodeconnectionratelimit</link>
        <description>Connection Rate Limiting

Introduction

We see at the moment one UniPager installation with version 0.6.0, that is constantly trying to connect to the DAPNET Node at dapnet.afu.rwth-aachen.de:43434 . In this old version of UniPager, the connect process was not inhibited if no configuration like callsign and auth key was provided after installation. So we are dealing here with a lonely Linux maschine, who's owner has forgotten that she/he installed UniPager and that it is causing 3 log lines ever…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetnodeinstall">
        <dc:format>text/html</dc:format>
        <dc:date>2018-10-23T09:22:32+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetnodeinstall</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetnodeinstall</link>
        <description>Installation procedure for new DAPNET node


ATTENTION: Due to serious problems of the current version of DAPNET-CORE we do not accept any new cores. A new version overcoming this issues is in progress. If you want to run your own core, please wait for the new version being released!</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetnodeshamnet">
        <dc:format>text/html</dc:format>
        <dc:date>2022-09-13T13:55:50+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetnodeshamnet</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetnodeshamnet</link>
        <description>List of HAMNET DAPNET Servers

	*  db0ffl 	44.149.167.37
	*  db0rhb 	44.149.59.201
	*  db0sda 	44.149.166.27
	*  db0sda2 	44.149.166.164
	*  db0sda3 	44.149.166.196
	*  db0sda4 	44.149.166.70
	*  db0vvs 	44.149.57.136
	*  di0han 	44.225.64.12

List and status:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetnodesinternet">
        <dc:format>text/html</dc:format>
        <dc:date>2019-07-24T21:39:16+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetnodesinternet</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetnodesinternet</link>
        <description>List of Internet DAPNET Servers

	*  dapnet.afu.rwth-aachen.de (137.226.79.100)
	*  db0dbn.ig-funk-siebengebirge.de (79.207.110.174) 

Not connected to the two servers above (own network with apprx. 100 participants)

	*  node1.dapnet-italia.it (37.59.188.8)</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetoverview">
        <dc:format>text/html</dc:format>
        <dc:date>2022-08-19T12:43:53+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetoverview</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetoverview</link>
        <description>DAPNET Overview

Das DAPNET ist ein von Funkamateuren betriebenes Funkmeldesystem. Es besteht aus einem dezentralen Verbund von Servern und daran angeschlossenen Sendern. Das Netz wird von freiwilligen Funkamateuren aufgebaut und betrieben. Anwendungen sind persönliche Funkrufe, allgemeine Amateurfunk-Nachrichten in verschiedenen Kategorien, Warnungen vor Unwetterlagen und zivilen Katastrophenfällen. Es gibt eine Vielzahl an kommerziell erwerbbaren Meldern zu erschwinglichen Preisen. Diese haben…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetpresentations">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-12T10:26:15+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetpresentations</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetpresentations</link>
        <description>Presentations and Publications

63. UKW Tagung Weinheim, Germany

DAPNET: Aktuelle Entwicklungen und Ausblick auf die nächste Version

[Paper]
[Presentation]</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetprotocol">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-15T14:44:51+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetprotocol</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetprotocol</link>
        <description>Protocol for Connection of Transmitters

Connection for transmitters is based on a simple cleartext TCP protocol . A tcpdump of a connection is shown below. Comments are inserted in italic where applicable. 

Red color denotes what is sent to the master.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dapnetproxy">
        <dc:format>text/html</dc:format>
        <dc:date>2018-01-08T13:21:40+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dapnetproxy</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dapnetproxy</link>
        <description>DAPNET-Proxy to make old AX.25 transmitters compatible with DAPNET

Background

In the former Funkrufmaster-Network the connection to the transmitter was established by the Funkrufmaster sofware. So the client was listening on its AX.25 interface for a connect from the master.
Using IP as the main protocol to connect transmitters and the DAPNET-Nodes, this direction of connection establishment was inverted. Incoming connections are in some cases a problem with IP: Think of transmitters connected…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=dmrplusgateway">
        <dc:format>text/html</dc:format>
        <dc:date>2020-04-03T15:32:38+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>dmrplusgateway</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=dmrplusgateway</link>
        <description>Since August 2018 it is possible to send messages via a (DMRplus-)IPSC2-repeater/hotspot to the DAPNET.

Handling: You have to send a message to talkgroup 9066 (be aware: NOT private Call!).

The content of the message has to be structured as followed:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=emergencybroadcast">
        <dc:format>text/html</dc:format>
        <dc:date>2022-09-10T20:20:01+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>emergencybroadcast</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=emergencybroadcast</link>
        <description>Emergency Broadcast

We are currently working on a way to notify large groups of receivers in a distict area.

Background

Many receivers from commercial applications have pre-programmed RICs for batch notifications. So far we have identified
 Hardware</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=faq">
        <dc:format>text/html</dc:format>
        <dc:date>2023-08-01T15:07:24+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>faq</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=faq</link>
        <description>Frequently Asked Questions

FIXME

I do not have an account. How do I get one?

Look here

Where do I get a registration for my Skyper or other receiver?

Look here

Why can't I use my DMR ID as RIC?

The maximum value for a RIC is limited to 2^21 = 2097152. Thus for example German DMR IDs (262xxxx/263xxxx) are out of range. Due to this we have to derive a RIC from that. For example cutting the first digit or replacing single digits with 0. 
As long as it is not already taken by someone else you…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=ft8500">
        <dc:format>text/html</dc:format>
        <dc:date>2020-11-09T14:16:12+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>ft8500</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=ft8500</link>
        <description>9k6 Transceiver with Yaesu FT-8500

Introduction

What is needed for the usage of a 9k6 transceiver

	*  Yaesu FT-8500
	*  Raspberry Pi (no matter what model, How-To is based on a RPi 3B+)
	*  A RJ45 LAN Cable
	*  A miniDIN 6pin Plug
	*  A 3.5mm stereo plug</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=gm360">
        <dc:format>text/html</dc:format>
        <dc:date>2020-10-25T16:03:58+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>gm360</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=gm360</link>
        <description>DAPNET Transceiver with Motorola GM360

Introduction

What is needed for the usage of a Motorola GM360 transceiver

	*  Motorola GM360 UHF
	*  Raspberry Pi (no matter what model, How-To is based on a RPi 3B+)
	*  An original Motorola accessory connector. Alternatively a 20 or 16 pin Dupont connector</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=hammessengergateway">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-07T23:26:27+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hammessengergateway</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=hammessengergateway</link>
        <description>Since Version 1.6.0 of the HAMMessenger, a messenger Client for the HAMNET (Highspeed Amateurradio Multimedia NETwork), it is possible to send a message to (selected) users of the DAPNET:



The HAMMessenger is available at &lt;http://news.ampr.at/?page_id=462&gt;</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=metar_messages">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-13T21:49:41+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>metar_messages</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=metar_messages</link>
        <description>METAR via DAPNET

It is possible to send METAR messages via DAPNET on a regional level.  
These messages are distributed through rubric ID 63.  
The label for the corresponding rubric is metar-[country]-[region].  

If you do NOT have a Nec 21/a (‘Skyper’), you can still receive these messages by programming</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=mmdvm">
        <dc:format>text/html</dc:format>
        <dc:date>2025-09-13T18:23:27+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>mmdvm</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=mmdvm</link>
        <description>MMDVM, MMDVM_HS_HAT, MMDVM_DUAL_HAT with Pi-Star (Pi*) or WPSD

What do I need?

Hardware

	*  MMDVM (modem with external analog radios) OR
	*  MMDVM_HS_Hat OR
	*  MMDVM_DUAL_HAT

with Firmware &gt;= 1.4.1

Software

	*  Pi-Star &gt;= 3.4.16 OR
	*  WPSD OR</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=monitoringnagios">
        <dc:format>text/html</dc:format>
        <dc:date>2018-02-27T11:27:43+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>monitoringnagios</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=monitoringnagios</link>
        <description>Monitoring of Unipager Transmitters on DAPNET-Node

Die Überwachung der Sender ist über die REST-API sehr einfach möglich. Wir benutzen Nagios, daher wird hier der Weg entsprechend beschrieben. Zunächst ist das Plugin check_http_json zu installieren.

Dann ist in commands.cfg</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=monitoringunipager">
        <dc:format>text/html</dc:format>
        <dc:date>2019-09-26T16:37:07+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>monitoringunipager</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=monitoringunipager</link>
        <description>Monitoring of Unipager Transmitters on the Unipager itself

Overview

There are three variantes of Nagios plugins available.

	*  Solution with JSON Status output of Unipager directly (since Version 1.0.0)
	*  Websocket based with C++ programm
	*  Websocket based with Python programm</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=nagiosnotification">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:11:14+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>nagiosnotification</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=nagiosnotification</link>
        <description>Notification to Pager from Nagios via DAPNET-Core

By default, Nagios can send emails to registered contact. Fortunately, there is also a contact property names pager which can be used very conveniently. Two things have to be added to your nagios config in order to receive the Nagios notifications via DAPNET.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=nagiosnotificationunipager">
        <dc:format>text/html</dc:format>
        <dc:date>2018-04-05T17:15:13+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>nagiosnotificationunipager</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=nagiosnotificationunipager</link>
        <description>Notification to Pager from Nagios via UniPager

There is a possibility to send notification to a pager via the DAPNET-Core. Look here. However, if in case of a failure the DAPNET-Core is not reachable, you may want to send a paging call directly via your unipager.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=netsed">
        <dc:format>text/html</dc:format>
        <dc:date>2020-05-12T11:25:35+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>netsed</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=netsed</link>
        <description>netsed Proxy

This is a quick (and dirty) way to ignore RICs without changing the software, just inserting a simple proxy in the middle.

	*  Install „wildcard netsed“ (&lt;https://github.com/xlab/netsed&gt;)
	*  Add the following line to /etc/rc.local :

sudo netsed tcp 43434 dapnet.afu.rwth-aachen.de 43434 's/:C8:3:%*%0a/:0:3:A%0a/i' 's/:D0:3:%*%0a/:0:3:B%0a/i' 's/:D8:3:%*%0a/:0:3:C%0a/i' 's/:E0:3:%*%0a/:0:3:D%0a/i' 's/:11A8:3:%*%0a/:0:3:X%0a/i' &amp;</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=openspot2">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-23T12:56:41+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>openspot2</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=openspot2</link>
        <description>SharkRF openSPOT2

The openSPOT2 is a standalone digital radio internet gateway (hotspot) designed mainly for amateur radio. You can talk with others on digital radio networks by using an openSPOT2, Wi-Fi internet access, and your radio.



Product page:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=openspot3">
        <dc:format>text/html</dc:format>
        <dc:date>2019-12-26T16:23:05+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>openspot3</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=openspot3</link>
        <description>SharkRF openSPOT3

The openSPOT3 is a standalone digital radio internet gateway (hotspot) designed mainly for amateur radio. You can talk with others on digital radio networks by using an openSPOT3, Wi-Fi internet access, and your radio.



Product page:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=openwebrx">
        <dc:format>text/html</dc:format>
        <dc:date>2020-06-04T15:28:13+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>openwebrx</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=openwebrx</link>
        <description>Not really a pager, but POCSAG: With the web-based SDR receiver OpenWebRX decoding of POCSAG signals is possible, see &lt;https://www.openwebrx.de/&gt;</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=pager_comparison">
        <dc:format>text/html</dc:format>
        <dc:date>2024-08-12T10:23:41+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>pager_comparison</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=pager_comparison</link>
        <description>Comparsion of Pagers
 Name  Picture  RICs/CapCodes  Time Sync  Skyper  [ Skyper ]  1 hardcoded; 1 group RIC (2504) 
text messages on subRIC 3/D  via group RIC  Primo / e*Cityruf  [ Primo ]  1 hardcoded 4 subRICs  n/a  QUIX     AlphaPOC  [ AlphaPoc 602R X4 ]  8 programmable (4 subRICs each) 
text messages on subRIC 3/D  via OTA RICs 216/224</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=pr430">
        <dc:format>text/html</dc:format>
        <dc:date>2018-04-18T20:52:37+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>pr430</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=pr430</link>
        <description>PR430 or RPC with KISS-Interface

Overview

PR430

The PR430 transceiver is a data transceiver originally designed as a radio for 9600 baud Packet Radio. There is an alternative firmware available to transfer the hardware into a POCSAG transmitter.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=primodescription">
        <dc:format>text/html</dc:format>
        <dc:date>2022-01-11T18:09:49+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>primodescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=primodescription</link>
        <description>Primo



These pagers were available in the former POCSAG net by Deutsche Telekom AG and later by e*cityruf. The HF part of the receiver is identical to Skypers. The modification for 439.9875 MHz is thus the same. The shortcome is that the display is much smaller and there is no built-in function for setting time and date automatically. In addition the date only allows years up to (20)13 starting from (19)94 to be set. This has to be done by hand and is lost on longer absence of battery power.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=procedurebuypagingrx">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-11T14:17:16+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>procedurebuypagingrx</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=procedurebuypagingrx</link>
        <description>First possibility: Search online at eBay for an old Skyper etc. and adapt it for HAM-frequencies. Be aware, that there are pagers with different frequency ranges (e.g. also for 2m).

Second possibility: Cheap programable pagers are distributed by AlphaPoc, e.g. the</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=procedurenewrubric">
        <dc:format>text/html</dc:format>
        <dc:date>2018-10-18T22:47:47+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>procedurenewrubric</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=procedurenewrubric</link>
        <description>What to do if I want to add a new rubric?

Just browse to https://support.hampager.de/open.php in our ticket system and file a new ticket. Select General Question and fill in the form. Explain what you want to do and what type of support from the DAPNET team you need. You should also give us information about the transmitter-groups you want to serve the rubric to and maybe if you want to regionalise it (for example like APRS-WX).</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=procedurenewtx">
        <dc:format>text/html</dc:format>
        <dc:date>2018-02-19T16:40:34+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>procedurenewtx</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=procedurenewtx</link>
        <description>What to do if I want to add a transmitter?

Just browse to https://support.hampager.de/open.php in our ticket system and file a new ticket. Select New DAPNET Transmitter and fill in the form. At the bottom, fill out all the required data, so the system can process your request. Feel free to write us in the comment section all you want to say.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=procedurenewusecase">
        <dc:format>text/html</dc:format>
        <dc:date>2018-01-17T19:43:00+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>procedurenewusecase</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=procedurenewusecase</link>
        <description>What to do if I want to add a new use case?

Just browse to https://support.hampager.de/open.php in our ticket system and file a new ticket. Select General Question and fill in the form. Explain what you want to do and what type of support from the DAPNET team you need.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=procedurenewuser">
        <dc:format>text/html</dc:format>
        <dc:date>2025-02-27T20:30:43+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>procedurenewuser</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=procedurenewuser</link>
        <description>What to do if I want to get a new user account?

Just browse to https://support.hampager.de/open.php in our ticket system and file a new ticket. In case you have a pager with a fix RIC or you want to use your DMR ID as RIC please select New DAPNET account with RIC and fill in the form. At the bottom, fill in your RIC, so the system can process your request.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=queueunipager">
        <dc:format>text/html</dc:format>
        <dc:date>2019-08-11T12:22:16+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>queueunipager</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=queueunipager</link>
        <description>Message Queues on unipager and pi-star

The TX led on your unipager/pi_hat is not blinking but working all the time? Maybe too many messages are waiting to be delivered and the queue is filling up.

Learn here how to check the queue (for unipager and pi-star/DAPNETGateway) and how to empty it.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=quixdescription">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-12T18:05:58+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>quixdescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=quixdescription</link>
        <description>Up to now Quix Pagers like the Quix Ultra are not supported by DAPNET.

The model Quix News2 (MemoExpress) can be used for DAPNET. 2 RICs, frame-based programming. No individual programming-password.

There are plannings to add support for Quix in DAPNET V2.0.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=raspager">
        <dc:format>text/html</dc:format>
        <dc:date>2018-03-13T21:42:46+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>raspager</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=raspager</link>
        <description>RasPager - Simple low-power Transmitter

Einleitung

Die Abdeckung durch Funkrufsender in Deutschland ist nach einem Aufschwung im letzten Jahrzehnt immer noch stark lückenhaft. Grund dafür ist unter anderem die mangelhafte Verfügbarkeit an Sendern, welche das POCSAG Signal ausstrahlen können. Auf der UKW-Tagung 2012 wurde ein Funkrufsender basierend auf Software Defined Radio vorgestellt</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=raspagerc9000">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:13:10+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>raspagerc9000</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=raspagerc9000</link>
        <description>Modification of Ericsson C9000



Background

Einleitung

Die Ericsson C9000 Paging Sender wurden in den 90er Jahren bis ca. 2002 an über 200 Standorten für Amateurfunk umgebaut. Nötig war neben einer Zusatzplatine, welche die nicht angeschlossene Endstufe simulierte, eine Schaltung, um die POSAG Signal zu erzeugen. Dazu gab es zunächst die RPC Karte (ein Europakarten großer Rechner mit diskreter CPU, RAM, ROM, EEPROM usw.) Der AATiS e.V. hat dann eine Variante herausgebracht, die auf einem mitt…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=rubric">
        <dc:format>text/html</dc:format>
        <dc:date>2018-01-07T13:46:32+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rubric</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=rubric</link>
        <description>Rubrics

Hier kann man sich zu den Rubriken auslassen</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=rubricactivationother">
        <dc:format>text/html</dc:format>
        <dc:date>2018-10-08T18:42:37+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rubricactivationother</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=rubricactivationother</link>
        <description>Rubric activation for other receivers (e.g. AlphaPOC)

For non-Skyper receivers, the rubric's content is also sent to special RICs. Every new entry of a rubric is transmitted to the RIC 1000+&lt;RUBRIC-NUMBER&gt;

Example: Rubric number 31 is RIC 1031. Add this RIC to your receiver in order to receive the content of the rubric as personal call on your non-Skyper receiver</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=rubricactivationskyper">
        <dc:format>text/html</dc:format>
        <dc:date>2020-05-29T22:45:22+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rubricactivationskyper</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=rubricactivationskyper</link>
        <description>Rubric activation for skyper receivers

Due to the system design of the former commercial paging system, the rubrics (except for the first three ones) have to be unlocked before you can access them. This is also called „Skyper rubrics activation“</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=rubricgeneral">
        <dc:format>text/html</dc:format>
        <dc:date>2025-03-25T19:00:19+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rubricgeneral</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=rubricgeneral</link>
        <description>General Information about rubrics

Rubrics are the „newsletter“ part of the DAPNET.

Personal calls are bound to one call sign, while rubrics are broadcasted to all pagers, which have „subscribed“ them.

Possible content: News, weather, alerts and so on.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=rubricnumber">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-14T22:09:46+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rubricnumber</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=rubricnumber</link>
        <description>Rubric Number Assignment

If you want to create a skyper-rubric, please contact us via ticket system (&lt;https://support.hampager.de&gt;) by opening a „General Question“-ticket. 

With this ticket, we need following information:

	*  describe your idea, what you want to do with the rubric</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=salt-minion">
        <dc:format>text/html</dc:format>
        <dc:date>2018-04-01T13:37:23+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>salt-minion</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=salt-minion</link>
        <description>Salt-Minion

Die RWTH-Amateurfunkgruppe betreibt zur automatischen Konfiguration von Servern mit Hilfe der Software Salt einen Salt-Master, der aus dem HAMNET unter config.db0sda.ampr.org und aus dem Internet unter config.afu.rwth-aachen.de erreichbar ist.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=skyperdescription">
        <dc:format>text/html</dc:format>
        <dc:date>2023-05-08T20:58:11+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>skyperdescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=skyperdescription</link>
        <description>Skyper



These pagers normally come with a (more or less) hard-coded RIC. It can be found on a small label on the rear side. It is not the „Skyper Nr.“  but the second part of the „ID Nr.“ and consists of seven digits of which the last four are underlined (have been used as a PIN in the commercial Skyper service).</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=start">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-13T21:53:37+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=start</link>
        <description>DAPNET DokuWiki

The DAPNET (Decentralized Amateur Paging Network) is a network operated by amateur radio enthusiasts. It is the new and further developed version of the FunkrufMaster. It consists of a decentral server cluster feeding paging data to distributed transmitters.
The most used frequency is 439.9875</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=swissphonedescription">
        <dc:format>text/html</dc:format>
        <dc:date>2019-02-21T14:35:34+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>swissphonedescription</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=swissphonedescription</link>
        <description>Swissphone



Swissphone ist ein Schweizer Hersteller von Alarmierungstechnik für BOS und kommerzielle Anwender, mit einer Niederlassung im Südwesten Deutschlands. Die Geräte aus diesem Hause sind üblicherweise hochwertig und hochpreisig, und in Zusammenarbeit mit der Zielgruppe entwickelt und optimiert worden. Reparaturen sind möglich und meist auch sinnvoll, Ersatzteile werden über lange Zeit bereitgehalten.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=telmi">
        <dc:format>text/html</dc:format>
        <dc:date>2023-02-13T10:47:43+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>telmi</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=telmi</link>
        <description>The former German Pager Network Telmi used Motorola pagers like the Motorola Memo Express or LX2. 

MemoExpress: 2RICs framebased programming, DOS-Software
LX2: 4 RIC non-framebased programming. Maildrop is possible, DOS Software

Some Telmi pagers could be used for Dapnet, but you would have to change the crystal, do a calibration with the three-circuit helix filter and mixer. Finally the telmi pager would support only personal calls.
Some LX2 HF-Boards have non-adjustible components (capacitor…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=translationinfo">
        <dc:format>text/html</dc:format>
        <dc:date>2018-04-12T12:46:03+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>translationinfo</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=translationinfo</link>
        <description>Translation of user interfaces

If you want the user interface to be presented in your favorite language, feel free to help us translate the texts. You can join the community easily by using this link https://poeditor.com/join/project/a4fVmB7IPr. Please review already existing translations or add a new language.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=transmittergroupgeneral">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-03T12:39:03+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>transmittergroupgeneral</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=transmittergroupgeneral</link>
        <description>General Information about Transmitter Groups

Introduction

In order not to have to send information across the entire network, the destination country or the destination region can be determined by specifying transmitter groups.

Naming Scheme

The transmitter groups are assigned geographically according to the following scheme:</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=transmittergroupspecial">
        <dc:format>text/html</dc:format>
        <dc:date>2020-11-15T18:59:39+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>transmittergroupspecial</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=transmittergroupspecial</link>
        <description>Special Transmitter Groups

There are special transmitter groups on DAPNET which are explained below.

Dxcluster

This special transmitter group is designed to enable their members to transmit DX Cluster messages into rubrics. The reason why not all transmitters are member of this group by default is that some sysops of transmitters prefere to keep their bandwidth for other content to be transmitted with minimum delay. A possible solution is implementing a priority system in the queuing of the D…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=txident">
        <dc:format>text/html</dc:format>
        <dc:date>2018-09-06T23:06:20+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>txident</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=txident</link>
        <description>Transmitter Identification Messages

Every transmitter sends out its own callsign every 10 minutes. In many countries it is a regulation that transmitters need to beacon their callsigns periodically. This call is broadcasted to RIC 8. So if you are interested to recieve this messages program RIC 8 to your pager.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=umbauten">
        <dc:format>text/html</dc:format>
        <dc:date>2021-01-13T09:11:54+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>umbauten</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=umbauten</link>
        <description>Modification of Scall, Quix or TelMi

Here are some (old) files which describe the modification of pagers like Scall, Quix or TelMi. The files are in German.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=unipager">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:15:05+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>unipager</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=unipager</link>
        <description>UniPager

english Version here

Einleitung und Motivation

Bisher wurden von der Amateurfunkgruppe an der RWTH Aachen verschiedene Software-Varianten entwickelt, die jeweils einen Raspager, einen SDRPager oder einen RasPagerC9000 ansprechen konnten. Nachteil war, dass die Software ein lauffähiges X11 brauchte, um die</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=unipagerenglish">
        <dc:format>text/html</dc:format>
        <dc:date>2026-01-30T14:14:06+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>unipagerenglish</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=unipagerenglish</link>
        <description>UniPager

Intro

Thomas Gatzweiler, DL2IC, wrote in rust a software, which allows to use unipager on all hardware variants and also provides a webinterface.

Installation

You can choose between two methods: The first one uses a script provided by the DAPNET-crew (</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=unipagerled">
        <dc:format>text/html</dc:format>
        <dc:date>2018-01-15T00:59:45+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>unipagerled</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=unipagerled</link>
        <description>Status LED controlled by UniPager

Für die Anzeige der Stati

	*  Programm läuft
	*  Programm ist mit DAPNET-Core verbunden
	*  Programm sendet

wird unter https://github.com/rwth-afu/UniPagerLED ein Zusatzprgramm beschrieben, welches sich mit der Websocket-Schnittstelle verbindet und entsprechend GPIO-Pins setzt.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=unipagernextion">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-12T21:27:41+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>unipagernextion</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=unipagernextion</link>
        <description>Nextion Touch Display for UniPager

Every project nowadays reaches for nice user interface. The display models from the company Nextion are quite famous due to their price and capabilities. The connection is made by a 3.3 V UART interface, either by a USB-TTL 3.3 V adapter or via the RasPi's onboard UART, if not already used. The software is written in Python can can be found here.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=unipagersend">
        <dc:format>text/html</dc:format>
        <dc:date>2018-04-05T16:57:53+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>unipagersend</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=unipagersend</link>
        <description>Send messages directly from command line with UniPager

If you want to send messages directly from the command line (e.g. from Nagios) to the Unipager, you can use a simple Python script.
It is available here: https://github.com/dh3wr/UniPager-SendWebsocket. Use the version unipager_send.py, if you want a flexible solution with command line arguments.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecasecivil">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-11T14:49:41+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecasecivil</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecasecivil</link>
        <description>Implementation of Civil Warnings (Mowas) from German BKK to DAPNET, see &lt;https://github.com/DecentralizedAmateurPagingNetwork/Civilwarnings&gt;</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecaseclubnews">
        <dc:format>text/html</dc:format>
        <dc:date>2019-04-16T16:56:58+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecaseclubnews</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecaseclubnews</link>
        <description>Club-News

Within RIC 1028 (rubric „Club-News“ on Skyper) we provide the headlines of RSS-Feeds of different homepages related to Amateur Radio.

Actually we provide news from following sources:
 Label       Name        URL         DARCDeutscher Amateur Radio Club e.V.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecasecwident">
        <dc:format>text/html</dc:format>
        <dc:date>2022-01-04T08:49:16+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecasecwident</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecasecwident</link>
        <description>Here is a simple way to Unipager-Audio transmit your callsign announcement, as required by law in many countries.

First, create a .wav file with the desired announcement. It can be CW or speech, on your choice:

	*  To create a CW .wav file visit: &lt;http://www.meridianoutpost.com/resources/etools/calculators/calculator-morse-code.php&gt;</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecasedxcluster">
        <dc:format>text/html</dc:format>
        <dc:date>2025-08-08T22:12:38+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecasedxcluster</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecasedxcluster</link>
        <description>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

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 …</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecaseodl">
        <dc:format>text/html</dc:format>
        <dc:date>2018-05-12T15:52:55+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecaseodl</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecaseodl</link>
        <description>Local Dose Rate

There are two scripts serving local dose rates of radio active contamination for the DAPNET.

Public measurements

Michael, DG5MM has written an interface to translate the public information of Bundesamt fuer Strahlenschutz (German federal agency for protection against radiation) into a DAPNET rubric called ODL. He picked several QTH throughout Germany randomly, values are broadcast every 6 hours (because online resource is only updated 4 times a day either). If you'd like to ha…</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecasepacketradio">
        <dc:format>text/html</dc:format>
        <dc:date>2018-03-13T15:10:38+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecasepacketradio</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecasepacketradio</link>
        <description>Packet Radio Mailbox Notification

The notification about new arrived mails in a packet radio mailboxes is being adapted to DAPNET at the moment. Have a look at https://github.com/DecentralizedAmateurPagingNetwork/packetradio and help us if you want/can.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecaseqthtemp">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-03T14:42:18+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecaseqthtemp</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecaseqthtemp</link>
        <description>It might be interesting to get also weather data from the own repeater QTH (parallel to the great APRS-WX rubric 1080). This page describes the periodically sending of a temperature file to DAPNET, generated with a raspberry pi and a temper1f sensor.

Please take this proposal as blueprint for own purposes, therefor the process is kept simple without any if-loops and so on. Useless use of cat intended</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecasetelegrambot">
        <dc:format>text/html</dc:format>
        <dc:date>2018-11-03T15:16:20+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecasetelegrambot</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecasetelegrambot</link>
        <description>HF is HF and 439,9875 is 439,9875 – but in the (rare ;-)) case you have no POCSAG transmitter next to you, you can use the telegram bot at DB0USD (&lt;https://db0usd.ralsu.de/wordpress/index.php/2018/09/13/13-09-2018-telegram-bot-fuer-dapnet/&gt;):

DB0USD works as a „virtual pager“ and forwards messages from the DAPNET to telegram (it fetches the messages via the DAPNET log). Experimental and not the same as a „real“ HF pager.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecaseweather">
        <dc:format>text/html</dc:format>
        <dc:date>2021-03-10T20:54:57+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecaseweather</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecaseweather</link>
        <description>Weather-Warnings and WX-Messages

We implemented actually two external services to fetch information on weather and weather-warnings. You'll find further information on the detail-pages to the mentioned rubrics below:

	*  APRS-WX
	*  DWD-Alerts
	*  NWS Alerts</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usecasewinlink">
        <dc:format>text/html</dc:format>
        <dc:date>2018-03-13T21:38:55+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usecasewinlink</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usecasewinlink</link>
        <description>WinLink-Mails -&gt; Funkruf (WinLink2Funkruf)

Das Script prüft im Maileingang von PAT (ein browserbasierender WinLink-Mail-Client) nach, ob neue Mails eingegangen sind. Bei einer neuen Mail wird aus der Absenderadresse und dem Betreff der WinLink-Mail ein Funkruf erstellt und dieser über das DAPNET an einen dort registrierten Funkrufempfänger ausgesendet.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=usercasepegel">
        <dc:format>text/html</dc:format>
        <dc:date>2019-01-16T21:46:22+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>usercasepegel</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=usercasepegel</link>
        <description>Water Levels of rivers (in Germany)

On RIC 61 the water levels of some rivers in Germany are announced each hour.

The data is fetched from &lt;https://www.pegelonline.wsv.de/webservices/rest-api/v2/stations/&gt;

If a river in your region (Bundesland) is missing: Search in the above listing for a Level measurement Station and contact Kim, DG9VH via the support ticket System for an add. Please submit Bundesland, name of the river, level station Name.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=uvk5">
        <dc:format>text/html</dc:format>
        <dc:date>2025-05-18T21:45:51+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>uvk5</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=uvk5</link>
        <description>Using a UV-K5 as a POCSAG Transmitter

TL;DR: you definitely need a modified firmware, you can download it here and flash it on Chrome/Chromium using this tool. Set the RX modulation to „DIGI“, bandwidth to „WIDE“. A hardware mod might be required, your mileage may vary. For more details, keep on reading.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=version2_overview">
        <dc:format>text/html</dc:format>
        <dc:date>2018-12-10T12:30:23+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>version2_overview</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=version2_overview</link>
        <description>Development of Version 2

The version 2 is under development at the moment. It's a complete rewrite and reorganisation of the core from DAPNET-Core 1. The main changes are going for docker-based microservices, using CouchDB as distributed database and RabbitMQ for the transmitter connections.</description>
    </item>
    <item rdf:about="https://hampager.de/dokuwiki/doku.php?id=w8008description">
        <dc:format>text/html</dc:format>
        <dc:date>2019-03-27T16:07:02+0200</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>w8008description</title>
        <link>https://hampager.de/dokuwiki/doku.php?id=w8008description</link>
        <description>WEX W8008

The W8008 is a product of the chinese company &lt;http://www.wex.com.hk&gt;. A variation of it is offered by &lt;https://alphapoc-europe.de&gt; as AlphaPoc 606R (but the firmware has some differences).



Specifications

	*  different frequency ranges (usable for DAPNET: 438-442 MHz)
	*  can handle up to 19 messages</description>
    </item>
</rdf:RDF>
