Handle telemetry #32

Open
opened 2023-06-26 11:55:41 -05:00 by W1CDN · 4 comments
Owner

This example is is->rf (for some reason), but the packets from W0RFP-1 seem to have been picked up earlier this morning.

image

Might be an issue connecting to direwolf?
image

Hooked up again:
image

This example is is->rf (for some reason), but the packets from W0RFP-1 seem to have been picked up earlier this morning. ![image](/attachments/09856fd2-3ddf-42a0-8650-05b7f1628383) Might be an issue connecting to direwolf? ![image](/attachments/300c519c-cb63-4710-ab8d-4f11ad693154) Hooked up again: ![image](/attachments/a14bd70b-0b30-4c23-959c-0d0b8feee002)
Author
Owner

OK, testing with HT indicates that regular packets are working fine, but telemetry isn't quite. I will have to try faking some incoming telemetry, but that will be difficult without an RF digipeater.

OK, testing with HT indicates that regular packets are working fine, but telemetry isn't quite. I will have to try faking some incoming telemetry, but that will be difficult without an RF digipeater.

image
image

![image](/attachments/64232be1-8acd-4c54-8382-a0968c0c3862) ![image](/attachments/9d6b1fd7-3c0e-4abc-93bb-1d380efbfa78)

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 that's where the errors are.

> 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 that's where the errors are.
Author
Owner

Certain telemetry seems to be an issue in aprslib itself:

2023-12-14 09:32:33,808 - New packet, trying to parse
2023-12-14 09:32:33,810 - K0RQ-1>APDW16,KB0UGF-3,WIDE1,WIDE2-1:}W0RFP-1>APMI06,TCPIP,K0RQ-1*:T#221,188,017,008,068,130,00000000
2023-12-14 09:32:33,811 - Parsing: K0RQ-1>APDW16,KB0UGF-3,WIDE1,WIDE2-1:}W0RFP-1>APMI06,TCPIP,K0RQ-1*:T#221,188,017,008,068,130,00000000
2023-12-14 09:32:33,814 - Packet is third-party
2023-12-14 09:32:33,815 - Parsing: W0RFP-1>APMI06,TCPIP,K0RQ-1*:T#221,188,017,008,068,130,00000000
2023-12-14 09:32:33,817 - Error with aprslib:
Traceback (most recent call last):
  File "kiss_and_db.py", line 68, in main
    a = aprslib.parse(str(frame))
  File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 134, in parse
    _try_toparse_body(packet_type, body, parsed)
  File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 167, in _try_toparse_body
    body, result = parse_thirdparty(body)
  File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/thirdparty.py", line 15, in parse_thirdparty
    subpacket = parse(body)
  File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 134, in parse
    _try_toparse_body(packet_type, body, parsed)
  File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 162, in _try_toparse_body
    raise UnknownFormat("Format is not supported: '{}' {}".format(packet_type, unsupported_formats[packet_type]))
aprslib.exceptions.UnknownFormat: Format is not supported: 'T' telemetry report
Certain telemetry seems to be an issue in `aprslib` itself: ``` 2023-12-14 09:32:33,808 - New packet, trying to parse 2023-12-14 09:32:33,810 - K0RQ-1>APDW16,KB0UGF-3,WIDE1,WIDE2-1:}W0RFP-1>APMI06,TCPIP,K0RQ-1*:T#221,188,017,008,068,130,00000000 2023-12-14 09:32:33,811 - Parsing: K0RQ-1>APDW16,KB0UGF-3,WIDE1,WIDE2-1:}W0RFP-1>APMI06,TCPIP,K0RQ-1*:T#221,188,017,008,068,130,00000000 2023-12-14 09:32:33,814 - Packet is third-party 2023-12-14 09:32:33,815 - Parsing: W0RFP-1>APMI06,TCPIP,K0RQ-1*:T#221,188,017,008,068,130,00000000 2023-12-14 09:32:33,817 - Error with aprslib: Traceback (most recent call last): File "kiss_and_db.py", line 68, in main a = aprslib.parse(str(frame)) File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 134, in parse _try_toparse_body(packet_type, body, parsed) File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 167, in _try_toparse_body body, result = parse_thirdparty(body) File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/thirdparty.py", line 15, in parse_thirdparty subpacket = parse(body) File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 134, in parse _try_toparse_body(packet_type, body, parsed) File "/home/pi/.local/lib/python3.7/site-packages/aprslib/parsing/__init__.py", line 162, in _try_toparse_body raise UnknownFormat("Format is not supported: '{}' {}".format(packet_type, unsupported_formats[packet_type])) aprslib.exceptions.UnknownFormat: Format is not supported: 'T' telemetry report ```
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: W1CDN/aprs_tool#32
No description provided.