Have been trying to setup a channel for Analog APRS messaging and found a couple issues that prevent it from working.
1) When using "Add APRS System" the path doesn't get saved, at least it is gone if save to yaml.
2) If uploading to the radio the path is empty if looking in the radio settings. But also when inspecting transmitted beacons the source and destination seems to be missing. If using QDMR to download the code plug again from the radio the whole -positioning: - aprs: section is missing.
Happy to help with additional testing to fix this if needed.
PS. Was reading https://dm3mat.darc.de/qdmr/manual/ch04s04.html - 'FM APRS system extension fields' and the report flags (reportPosition, reportMicE, reportObject etc.) are a filter for incoming traffic that gets stored in the APRS Info inbox. So the naming isn't very good. Anytone should have called them receive or similar.
Have been trying to setup a channel for Analog APRS messaging and found a couple issues that prevent it from working.
1) When using "Add APRS System" the path doesn't get saved, at least it is gone if save to yaml.
2) If uploading to the radio the path is empty if looking in the radio settings. But also when inspecting transmitted beacons the source and destination seems to be missing. If using QDMR to download the code plug again from the radio the whole -positioning: - aprs: section is missing.
Happy to help with additional testing to fix this if needed.
PS. Was reading https://dm3mat.darc.de/qdmr/manual/ch04s04.html - 'FM APRS system extension fields' and the report flags (reportPosition, reportMicE, reportObject etc.) are a filter for incoming traffic that gets stored in the APRS Info inbox. So the naming isn't very good. Anytone should have called them receive or similar.
BR Daniel/SA7DAI