ua1zbe
/
aprs-python
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Removed unnecessary comments

This commit is contained in:
Joerg Schultze-Lutter 2021-09-09 23:13:24 +02:00
parent 93b0101305
commit 35cd062348
1 changed files with 0 additions and 76 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

76
tests/test_old_new_replyack_format.py
View File

@ -6,82 +6,6 @@ logging.basicConfig(
) )
logger = logging.getLogger(__name__) logger = logging.getLogger(__name__)
"""
Have a look at the incoming APRS message and check if it
contains a message no which does not follow the APRS
standard (see aprs101.pdf chapter 14)
but rather follow the new format
http://www.aprs.org/aprs11/replyacks.txt
The following assumptions apply when handling APRS messages in general:
Option 1: no message ID present:
send no ACK
outgoing messages have no msg number attachment
Example data exchange 1:
DF1JSL-4>APRS,TCPIP*,qAC,T2PRT::WXBOT :94043
WXBOT>APRS,qAS,KI6WJP::DF1JSL-4 :Mountain View CA. Today,Sunny High 60
Example data exchange 2:
DF1JSL-4>APRS,TCPIP*,qAC,T2SPAIN::EMAIL-2 :jsl24469@gmail.com Hallo
EMAIL-2>APJIE4,TCPIP*,qAC,AE5PL-JF::DF1JSL-4 :Email sent to jsl24469@gmail.com
Option 2: old message number format is present: (example: msg{12345)
Send ack with message number from original message (ack12345)
All outgoing messages have trailing msg number ( {abcde ); can be numeric or
slphanumeric counter. See aprs101.pdf chapter 14
Example data exchange 1:
DF1JSL-4>APRS,TCPIP*,qAC,T2SP::EMAIL-2 :jsl24469@gmail.com Hallo{12345
EMAIL-2>APJIE4,TCPIP*,qAC,AE5PL-JF::DF1JSL-4 :ack12345
EMAIL-2>APJIE4,TCPIP*,qAC,AE5PL-JF::DF1JSL-4 :Email sent to jsl24469@gmail.com{891
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::EMAIL-2 :ack891
Example data exchange 2:
DF1JSL-4>APRS,TCPIP*,qAC,T2CSNGRAD::EMAIL-2 :jsl24469@gmail.com{ABCDE
EMAIL-2>APJIE4,TCPIP*,qAC,AE5PL-JF::DF1JSL-4 :ackABCDE
EMAIL-2>APJIE4,TCPIP*,qAC,AE5PL-JF::DF1JSL-4 :Email sent to jsl24469@gmail.com{893
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::EMAIL-2 :ack893
Option 3: new messages with message ID but without trailing retry msg ids: msg{AB}
Do NOT send extra ack
All outgoing messages have 2-character msg id, followed by message ID from original message
Example:
User sends message "Hello{AB}" to MPAD
MPAD responds "Message content line 1{DE}AB" to user
MPAD responds "Message content line 2{DF}AB" to user
AB -> original message
DE, DF -> message IDs generated by MPAD
Example data exchange 1:
DF1JSL-4>APRS,TCPIP*,qAC,T2NUERNBG::WXBOT :99801{AB}
WXBOT>APRS,qAS,KI6WJP::DF1JSL-4 :Lemon Creek AK. Today,Scattered Rain/Snow and Patchy Fog 50% High 4{QL}AB
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::WXBOT :ackQL}AB
WXBOT>APRS,qAS,KI6WJP::DF1JSL-4 :0{QM}AB
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::WXBOT :ackQM}AB
Example data exchange 2:
DF1JSL-4>APRS,TCPIP*,qAC,T2SPAIN::EMAIL-2 :jsl24469@gmail.com Hallo{AB}
EMAIL-2>APJIE4,TCPIP*,qAC,AE5PL-JF::DF1JSL-4 :Email sent to jsl24469@gmail.com{OQ}AB
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::EMAIL-2 :ackOQ}AB
Option 4: new messages with message ID and with trailing retry msg ids: msg{AB}CD
We don't handle retries - therefore, apply option #3 for processing these
the "CD" part gets omitted and is not used
Example data exchange 1:
DF1JSL-4>APRS,TCPIP*,qAC,T2CZECH::WXBOT :99801{LM}AA
WXBOT>APRS,qAS,KI6WJP::DF1JSL-4 :Lemon Creek AK. Today,Scattered Rain/Snow and Patchy Fog 50% High 4{QP}LM
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::WXBOT :ackQP}LM
WXBOT>APRS,qAS,KI6WJP::DF1JSL-4 :0{QQ}LM
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::WXBOT :ackQQ}LM
Example data exchange 2:
DF1JSL-4>APRS,TCPIP*,qAC,T2SP::EMAIL-2 :jsl24469@gmail.com Welt{DE}FG
EMAIL-2>APJIE4,TCPIP*,qAC,AE5PL-JF::DF1JSL-4 :Email sent to jsl24469@gmail.com{OS}DE
DF1JSL-4>APOSB,TCPIP*,qAS,DF1JSL::EMAIL-2 :ackOS}DE
"""
if __name__ == "__main__": if __name__ == "__main__":