You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+9-215Lines changed: 9 additions & 215 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -76,230 +76,24 @@ My first test case
76
76
77
77
- Apart from minor helper methods for the connection setup and field check/retrieval, this Robot Framework library does not offer any additional keywords for exchanging data in a proper way. (Almost) every feature that the original [aprslib](https://github.com/rossengeorgiev/aprs-python) offers is supported by this Robot library - nothing more and nothing less. As aprslib does not [support the more recent replyack scheme](http://www.aprs.org/aprs11/replyacks.txt), this keyword library will also not decode these messages in a proper way and you may need to decode them manually. I was thinking about introducing a workaround to this library (the one that [mpad](https://github.com/joergschultzelutter/mpad) uses), but in the end this decoding should rather be done by aprslib itself.
78
78
79
-
- The current version of the Robot Framework does not support WHILE loops which would permit the Robot script to run endlessly (when needed). Loops can only be triggered with the help of finite FOR loops. This should be enough for testing but unless a real WHILE loop is made available for the Robot Framework, you can't build an APRS messaging server which will not terminate after a certain point in time.
79
+
- The current version of the Robot Framework does not support WHILE loops (planned for RF 5.x) which would permit the Robot script to run endlessly (when needed). Loops can only be triggered with the help of finite FOR loops. This should be enough for testing but unless a real WHILE loop is made available for the Robot Framework, you can't build an APRS messaging server which will not terminate after a certain point in time.
80
80
81
81
- The ```Receive APRS Packet``` keyword has no timeout which means that it will only return back from this code if it has found a message that is to be returned back to Robot. If you depend on timeout, you may need to amend your APRS-IS filter settings and handle the filter process in your code.
82
82
83
83
- The keyword ``Send APRS Packet`` will __not__ check whether the APRS-IS connection has been establised read-only (``N0CALL`` call sign) or read-write.
84
84
85
-
## Examples
85
+
## Robot Framework Library Examples
86
86
87
-
All examples can be downloaded from this repo.
87
+
In order to run these scripts, you need to change them and add your call sign to the script's configuration section:
88
88
89
-
### Send a single packet to APRS-IS and wait for the response
89
+
# This is your APRS-IS call sign. Replace this place holder with your personal call sign
90
+
${callsign} YOURCALLSIGN
90
91
91
-
```robotframework
92
-
# Send a single message to WXBOT, wait for a response message and display it on the console.
0 commit comments