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
Letzte Überarbeitung Beide Seiten der Revision
dapnetprotocol [2018/10/17 11:27]
df2et
dapnetprotocol [2018/10/23 09:26]
df2et
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>​ \\
dapnetprotocol.txt · Zuletzt geändert: 2018/11/15 14:44 von df2et