Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- pr430 [2018/04/13 11:43]
dh3wr
+++ pr430 [2018/04/18 20:38]
dh3wr [Installing the DAPNET-Proxy]
@@ Zeile 11: / Zeile 11: @@
 The firmware Version 57 can be downloaded {{ :ax25:pr430_firmware_v57.zip |here}}.
-=== SW Configuration for POCSAG operation ===
+=== Software configuration for POCSAG operation ===
+== Introduction and Overview ==
 The PR430 was delivered originally with a software which was used for packet radio operation. Therefore the likelihood is very high that if you get an PR430 that the old packet radio TNC software is installed on your PR430. The ADACOM - Fachverband für Amateur-Datenfunk provided then at a later stage another software package which allowed to convert the PR430 into an POCSAG transmitter. At the time writing his document April 2018) the ADACOM webpage www.adacom.org is not available. Therefore we provide here the information and necessary steps for this PR430 configuration:
-We have used here at DM0SAT and DB2GM an old WinXP notebook with serial interface. The interface cable used is a 1:1 cable with SUB-D9 female connector at the notebook side and a SUB-D9 male connector at the side of the PR430. We have tested the software only in the DOS box of this WinXP PC. Please give send us by E-mail to db2gm  at  darc dot de any information if it will work on other operating systems. It is also important to receive the information on which operating systems it does not work. Because it is very likely that it is only working under Win XP and older operating systems. In any case keep in mind that these are old MS-DOS files and software.
+== Hardware setup for configuration ==
+We have used here at DM0SAT and DB2GM an old WinXP notebook with serial interface. The interface cable used is a 1:1 cable with SUB-D9 female connector at the notebook side and a SUB-D9 male connector at the side of the PR430. We have tested the software only in the DOS box of this WinXP PC. Please give send us by E-mail to db2gm  at  darc dot de any information if it will work on other operating systems. It is also important to receive the information on which operating systems it does not work. Because it is very likely that it is only working under Win XP and older operating systems. In any case keep in mind that these are old MS-DOS files and software.
 You need two files ''SERIAL.EXE'' and ''MGSC.EXE''. Copy these on your PC, we did it in a subdirectory ''C:\PR430''.
 Then open with ''cmd'' a DOS box under windows.
 Power on the PR430 and connect it with the above mentioned serial interface cable to the serial interface of this PC.
+== Setting RS232 parameters ==
 Start the software ''SERIAL.EXE''.
 If the hardware connection between the PR430 and PC is not correct then you only will see a text ''Searching Modem'' and nothing else. The software continuously searches for the modem until the cable connection is correct. With Enter you can cancel this. Please also make sure that you are using a COM interface number between 1 to 6 and not higher!
 If the hardware connection is correct the software will //immediately// perform the software upgrade to the newest software version (which includes the POCSAG mode) and you will see this only once, therefore look for it! You cannot initiate the software upgrade on your own as it is performed automatically.
 You will see that the software of the PR430 will be upgraded by the following text message
 ''Updating Firmware .............OK''
-When it is finished the text message ''Baudrate 9600, Mode 8N, handshake off'' will appear.
+When it is finished the text message
+''Baudrate 9600, Mode 8N, handshake off'' will appear.
 This altogether will take approx. 20 seconds.
-If the newest software version is already installed the software will reply with the actual configured serial interface parameters, like b=19200 f=8n h=n . If you want to change the bitrate or the other parameters then you can do this with commands like ''SERIAL.EXE b=9600''. Keep f=8n and h=n!
+If the newest software version is already installed the software will reply with the actual configured serial interface parameters, like b=19200 f=8n h=n . If you want to change the bitrate or the other parameters then you can do this with commands like
-The detailed command set is described here:
+<code>SERIAL.EXE b=9600</code>
+Keep f=8n and h=n!
+<code>serial.exe b=<Baud rate> f=<Data format> h=<Handshake> w=<Delay></code>
+  * Parameters:
+    * <Baud rate>: Allowed values: 1200 to 38400 Baud
+    * <Data format>: 7/8 Bit, (n)o / (e)ven / (o)dd Parity
+    * <Handshake>: (h)ardware RTS/CTS, (s)oftware XON/XOFF, (n)one
+    * <Delay>: Delay between characters in ms.
+  * Example:
+    * serial b=19200 f=8n h = n (sets 19200 Baud, 8 Bit, No Parity, No Handshake)
+== Configure PR430 to POCSAG mode ==
 Now you will use the second software ''MGSC.EXE'' to configure the updated PR430 software.
-Start ''mgsc'' without parameters and after a fresh updated PR430 you should see the text message ''PC/Flexnet Mode''.
+Start ''mgsc'' without parameters and after a fresh updated PR430 you should see the text message
-With the command ''mgsc M=3'' 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!
+''PC/Flexnet Mode''.
+With the command
+<code>mgsc M=3</code>
+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 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.
 <code>
 mgsc I:DB0ABC-7
-mgsc P: DB0ABC-12
+mgsc P:DB0ABC-12
 mgsc F:439987,5
 </code>
-The software will answer after the third command with the text''POCSAG Mode, Mycall DB0ABC-7, Master DB0ABC-12, Linkfreq 439,987MHz FSK''
+The software will answer after the third command with the text''POCSAG Mode, Mycall DB0ABC-7, Master DB0ABC-12, Linkfreq 439,987MHz FSK''.
 Use <code>mgsc F0</code> to change the internal TNC to KISS mode.
 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.
+<code>mgsc.exe [M=<Mode> I:<CallsignTX> P:<CallsignMaster> F:<Frequency>[-|--|---]|FO]</code>
+  * Parameters:
+    * <Mode>: 3: POCSAG Mode, 5: PC/FlexNet Mode
+    * <CallsignTX>: AX.25-Callsign for this TX, [-SSID]
+    * <CallsignMaster>: AX.25-Callsign for the Master, [-SSID]
+    * <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.
+- : 1.6 MHz TX frequency shift
+-- : 7.6 MHz TX frequency shift
+- - - : 9.4 MHz TX frequency shift
+The parameters can also be given one by one running the program serveral times.
 Now your PR430 is configured correctly and you can connect it to your Raspberry PI serial interface.
@@ Zeile 114: / Zeile 162: @@
 <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.
-<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.
   * Set the master callsign to db0abc-12
@@ Zeile 153: / Zeile 201: @@
 </file>
 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:
@@ Zeile 182: / Zeile 230: @@
 cd /opt
 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
 </code>
@@ Zeile 193: / Zeile 241: @@
 Copy the example config file to that directory. Change the callsign according to your needs.
 <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>
@@ Zeile 241: / Zeile 288: @@
 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.

DAPNET DokuWiki

Benutzer-Werkzeuge

Webseiten-Werkzeuge

Unterschiede

Seiten-Werkzeuge