Benutzer-Werkzeuge

Webseiten-Werkzeuge


pr430

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen Revision Vorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
pr430 [2018/04/13 12:08]
dh3wr
pr430 [2018/04/18 20:52] (aktuell)
dh3wr [Automated start of the DAPNET-Proxy]
Zeile 42: Zeile 42:
 Keep f=8n and h=n! Keep f=8n and h=n!
  
-''​serial.exe b=<Baud rate> f=<Data format> h=<​Handshake>​ w=<​Delay>​''​+<​code>​serial.exe b=<Baud rate> f=<Data format> h=<​Handshake>​ w=<​Delay>​</​code>​
   * Parameters:   * Parameters:
     * <Baud rate>: Allowed values: 1200 to 38400 Baud     * <Baud rate>: Allowed values: 1200 to 38400 Baud
Zeile 61: Zeile 61:
 change the mode of the PR430 to POCSAG mode. The software will answer a text with ''​POCSAG Mode, Mycall NO CALL, Master undefined, Mode undefined''​ change the mode of the PR430 to POCSAG mode. The software will answer a text with ''​POCSAG Mode, Mycall NO CALL, Master undefined, Mode undefined''​
  
-Now you define the callsing of the POCSAG transmitter and the master call, and the POCSAG frequency with the following commands. We are using the same call signs as in the description of th e configuration below, so please change ''​DB0ABC-7''​ and ''​DB0ABC-12''​ to your POCSAG transmitters licensed callsign!+Now you define the callsing of the POCSAG transmitter and the master call, and the POCSAG frequency with the following commands. We are using the same call signs as in the description of the configuration below, so please change ''​DB0ABC-7''​ and ''​DB0ABC-12''​ to your POCSAG transmitters licensed callsign!
  
 **Remark**: These settings are just used on the AX.25 connection. They have nothing to do with the DAPNET configuration on the DAPNET-Network. But they are necessary in the ''​DAPNET-Proxy''​ setup described below. **Remark**: These settings are just used on the AX.25 connection. They have nothing to do with the DAPNET configuration on the DAPNET-Network. But they are necessary in the ''​DAPNET-Proxy''​ setup described below.
Zeile 67: Zeile 67:
 <​code>​ <​code>​
 mgsc I:DB0ABC-7 mgsc I:DB0ABC-7
-mgsc P: DB0ABC-12+mgsc P:DB0ABC-12
 mgsc F:439987,5 mgsc F:439987,5
 </​code>​ </​code>​
Zeile 76: Zeile 76:
 The software answer with ''​POCSAG Mode, Mycall DB0ABC-7, Master DB0ABC-12 KISS''​. The frequency information is not shown in this output, but it's still active. The software answer with ''​POCSAG Mode, Mycall DB0ABC-7, Master DB0ABC-12 KISS''​. The frequency information is not shown in this output, but it's still active.
  
-''​mgsc.exe [M=<​Mode>​ I:<​CallsignTX>​ P:<​CallsignMaster>​ F:<​Frequency>​[-|--|---][A]|FO]''​+<​code>​mgsc.exe [M=<​Mode>​ I:<​CallsignTX>​ P:<​CallsignMaster>​ F:<​Frequency>​[-|--|---]|FO]</​code>​
   * Parameters:   * Parameters:
     * <​Mode>:​ 3: POCSAG Mode, 5: PC/FlexNet Mode     * <​Mode>:​ 3: POCSAG Mode, 5: PC/FlexNet Mode
     * <​CallsignTX>:​ AX.25-Callsign for this TX, [-SSID]     * <​CallsignTX>:​ AX.25-Callsign for this TX, [-SSID]
     * <​CallsignMaster>:​ AX.25-Callsign for the Master, [-SSID]     * <​CallsignMaster>:​ AX.25-Callsign for the Master, [-SSID]
-    * <​Frequency>:​ Frequency in kHz: [-|--|---][A]+    * <​Frequency>:​ Frequency in kHz, decimal limiter is '',''​
 The ''​-''​ are setting a Duplex shift, which is only used for packet radio operation and are not necessary for POCSAG operation. So this information is for completness only. The ''​-''​ are setting a Duplex shift, which is only used for packet radio operation and are not necessary for POCSAG operation. So this information is for completness only.
    
 - : 1.6 MHz TX frequency shift - : 1.6 MHz TX frequency shift
 +
 -- : 7.6 MHz TX frequency shift -- : 7.6 MHz TX frequency shift
---- : 9.4 MHz TX frequency shift 
-A: Use AFSK 1200 baud mode, if not given use FSK 9600 Baud mode 
- 
-    * FO: Set to KISS MODE 
-  * Example: 
-    * mgsc M=3 I:db0xyz-7 P:db0xyz-12 F:438350-- 
  
 +- - - : 9.4 MHz TX frequency shift
  
 The parameters can also be given one by one running the program serveral times. The parameters can also be given one by one running the program serveral times.
Zeile 166: Zeile 162:
 <​code>​sudo kissattach /​dev/​ttyUSB0 ax0</​code>​ <​code>​sudo kissattach /​dev/​ttyUSB0 ax0</​code>​
  
-If you type now <​code>​ifconfig</​config> you should see a network device with name **ax0**.+If you type now <​code>​ifconfig</​code> you should see a network device with name **ax0**.
  
 Try to connect via KISS and AX.25 to your PR430 or RPC. Try to connect via KISS and AX.25 to your PR430 or RPC.
-<​code>​axcall -s db0abc ax0 db0abc-7</​code>​+<​code>​axcall -s db0abc-12 ax0 db0abc-7</​code>​
 You should see the command line interface of the POCSAG software running on your PR430 or RPC. If not done already, now it's the time to do (and store**(!)**) some settings on the PR430. You should see the command line interface of the POCSAG software running on your PR430 or RPC. If not done already, now it's the time to do (and store**(!)**) some settings on the PR430.
   * Set the master callsign to db0abc-12   * Set the master callsign to db0abc-12
Zeile 205: Zeile 201:
 </​file>​ </​file>​
 Restart the xinetd daemon with Restart the xinetd daemon with
-<​code>​sudo ​sytemctl ​restart xinetd.service</​code>​+<​code>​sudo ​systemctl ​restart xinetd.service</​code>​
  
 Try if the connection and conversion is working: Try if the connection and conversion is working:
Zeile 234: Zeile 230:
 cd /opt cd /opt
 sudo git clone https://​github.com/​rwth-afu/​raspager-proxy.git sudo git clone https://​github.com/​rwth-afu/​raspager-proxy.git
-chown -R pi /​opt/​raspager-proxy+sudo chown -R pi /​opt/​raspager-proxy
 cd /​opt/​raspager-proxy cd /​opt/​raspager-proxy
 </​code>​ </​code>​
Zeile 245: Zeile 241:
 Copy the example config file to that directory. Change the callsign according to your needs. ​ Copy the example config file to that directory. Change the callsign according to your needs. ​
 <​code>​ <​code>​
-cp /​opt/​raspager-proxy/​example.properties +cp /​opt/​raspager-proxy/​example.properties /​opt/​raspager-proxy/​config/​db0abc.properties
-/​opt/​raspager-proxy/​config/​db0abc.properties+
 </​code>​ </​code>​
  
Zeile 293: Zeile 288:
  
 In a second SSH session or terminal, you can watch the AX.25 traffic on ''​ax0''​ with In a second SSH session or terminal, you can watch the AX.25 traffic on ''​ax0''​ with
-<​code>​axlisten -axp ax0</​code>​+<​code>​axlisten -ap ax0</​code>​
 If you are familiar with AX.25, this will give a good hints for debugging. If you are familiar with AX.25, this will give a good hints for debugging.
  
Zeile 316: Zeile 311:
 ExecStopPost=-/​usr/​bin/​killall kissattach ExecStopPost=-/​usr/​bin/​killall kissattach
 WorkingDirectory=/​opt/​raspager-proxy/​config WorkingDirectory=/​opt/​raspager-proxy/​config
-ExecStart=/​bin/​bash -c "/​usr/​sbin/​kissattach /​dev/​ttyUSB0 ax0 && /​usr/​bin/​java -Ddapnet.proxy.rest.port=8080 -jar ../​target/​dapnet-proxy-1.1.1-SNAPSHOT-jar-with-dependencies.jar ​db2gm.properties"​+ExecStart=/​bin/​bash -c "/​usr/​sbin/​kissattach /​dev/​ttyUSB0 ax0 && /​usr/​bin/​java -Ddapnet.proxy.rest.port=8080 -jar ../​target/​dapnet-proxy-1.1.1-SNAPSHOT-jar-with-dependencies.jar ​db0abc.properties"​
 StandardOutput=null StandardOutput=null
 StandardError=null StandardError=null
pr430.1523614101.txt.gz · Zuletzt geändert: 2018/04/13 12:08 von dh3wr