I will have to try faking some incoming telemetry, but that will be difficult without an RF digipeater.
Can just pass telemetry packets to aprslib.parse(str(frame)) to test, as long as…
Currently logging everything to aprs_api.log. Adding to db would depend on what the error is.
Logging errors is not working correctly. These show up in the screen -r output, but not in the log file:
Spec seems pretty clear, and seems to match what aprslib is doing. I just need to insert the subpacket into the db, not the original one.
THI…Subpackets need to go into the database right, but I need to make sure of how APRS says they are to be used.
Frame could not be parsed. is an overarching log message I added for failure and includes everything from parsing to DB insertion. It's not very helpful.
- this code needs to be restructure…
I took this far down the wrong path, and I think my observation in the last post is correct. At #38, I am adding log messages to track exactly what packets are causing the code to fail and I will…
Example with a single quote? Can it be escaped?
N0CBV-2>APNU3B,KB0UGF-3,WIDE2-1:!4636.05NS09641.52W#PHG7230W2 MNn Wolverton 932'
https://stackoverflow.com/questions/3151146/replace-the-single-q…
Now seeing this?
Parsed ok.
Frame could not be parsed.
Deployed code is a bit ahead what is in the repo right now.
Same thing happening this morning. Breaking in between "Parsed ok" and when I attempt to log the
Also need to think about what…
Was fooling around with packages earlier and ran into this again. Had to reinstall stuff in right order, but first delete some things.
>~/.local/lib/python3.7/site-packages $ rm -R…Started 11:50, seems to have quit/hung ~14:27 CST.
Seems hung after this. Packets came in after this, but nothing in log.