Benutzer-Werkzeuge

Webseiten-Werkzeuge


dapnetprotocol

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
dapnetprotocol [2018/10/17 11:20]
df2et
dapnetprotocol [2018/11/15 14:44] (aktuell)
df2et
Zeile 1: Zeile 1:
 ====== Protocol for Connection of Transmitters ====== ====== Protocol for Connection of Transmitters ======
  
-Connection for transmitters is based on a simple cleartext TCP protocol ((Described here: https://​www.afu.rwth-aachen.de/​images/​vortraege/​Wilke_FunkrufTX_Weinheim2012.pdf)). A tcpdump of a connection is shown below. Comments are inserted in italic where applicable. \\+Connection for transmitters is based on a simple cleartext TCP protocol ((Described here (Geman only): https://​www.afu.rwth-aachen.de/​images/​vortraege/​Wilke_FunkrufTX_Weinheim2012.pdf)). A tcpdump of a connection is shown below. Comments are inserted in italic where applicable. \\
 <color #​ed1c24>​Red color denotes what is sent to the master.</​color>​ \\ <color #​ed1c24>​Red color denotes what is sent to the master.</​color>​ \\
 <color #​7092be>​Blue color shows answers received from the master.</​color>​ <color #​7092be>​Blue color shows answers received from the master.</​color>​
Zeile 7: Zeile 7:
 ---- ----
  
-<color #​ed1c24>​[UniPager-Raspager1 v1.0.3 df2et ThisIsAReallyGoodPassword]</​color>​ \\+<color #​ed1c24>​[UniPager-Raspager1 v1.0.3 df2et ThisIsAReallyGoodAuthKey]</​color>​ \\
  
 //First you have to send the name of your software, a version string starting with "​v",​ the callsign of the transmitter and your AuthKey. Remember that this is not the user account but an account for a transmitter. // //First you have to send the name of your software, a version string starting with "​v",​ the callsign of the transmitter and your AuthKey. Remember that this is not the user account but an account for a transmitter. //
Zeile 14: Zeile 14:
  
 //The master answers with message type 2 and his time hex encoded. The next five steps were originally designed to calculate the time offset between master and slave to determine the correct time slots. In the current implementation this is not needed because clients are NTP synced. Normally the client would answer by adding his time. As a dummy "​0000"​ is used here.// //The master answers with message type 2 and his time hex encoded. The next five steps were originally designed to calculate the time offset between master and slave to determine the correct time slots. In the current implementation this is not needed because clients are NTP synced. Normally the client would answer by adding his time. As a dummy "​0000"​ is used here.//
 +
 +//If login fails due to invalid credentials or the transmitter not being registered you will receive a message of type 7 and a string containing details about why the login failed. This could look as follows://
 +
 +<color #​7092be>​7 Invalid credentials</​color>​ \\
 +
 +//But let's continue as normal... :-) //
  
 <color #​ed1c24>​2:​6116:​0000</​color>​ \\ <color #​ed1c24>​2:​6116:​0000</​color>​ \\
Zeile 59: Zeile 65:
 //This is the first call. The master sent "#​00"​ which we have to confirm by increasing by one -> "#:01 +". The rest of the line is as follows (values separated by a ":"​):​ // //This is the first call. The master sent "#​00"​ which we have to confirm by increasing by one -> "#:01 +". The rest of the line is as follows (values separated by a ":"​):​ //
   * ''​6''​ //is the message type. 6 is a text message transmission and 5 is a time sync message (see further below for an example).//   * ''​6''​ //is the message type. 6 is a text message transmission and 5 is a time sync message (see further below for an example).//
-  * ''​1''​ //is blabla//+  * ''​1''​ //indicates the POCSAG tranmission speed to use ( 1 = 1200 bit/s).//
   * ''​3EC''​ //is the RIC/CAP code that the message is intended for. It is the hexadecimal representation of the decimal value  1004 in this case.//   * ''​3EC''​ //is the RIC/CAP code that the message is intended for. It is the hexadecimal representation of the decimal value  1004 in this case.//
   * ''​3''​ //is the function bit or sub RIC that the message is addressed to.//   * ''​3''​ //is the function bit or sub RIC that the message is addressed to.//
dapnetprotocol.1539768011.txt.gz · Zuletzt geändert: 2018/10/17 11:20 von df2et