I didn't see it on aprs.fi under your callsign.? What SSID did you send it with?
?? I looked at -6 which said it was Direwolf, but packets in "raw"
The MOST important things about the infocmd is the first character in the field.
If you just start with text and the? first letter is A-S you should see this error.
Most of the toolkit examples start with a perl script that has "T#" and then the sequential number for telemetry data, then add more text.? The "T" indcates Telemetry, so it does not start with A-S.
If you aren't starting with a perl script, then you python script has to account for that.
Since your CBEACON doresn't appear to provide a position report, just the comment, I would consider this a status, the very first character should be a '>'
Robert Giuliano KB8RCO
On Thursday, March 23, 2023 at 02:42:36 PM EDT, David Ranch <direwolf-groupsio@...> wrote:
Hello Craig,
I've been experimenting using CBEACON to send the
output from a python file (at present this is simply text saying
"test").? The beacon triggers ok and seems to contain the required
text content but I see an error in Direwolf - "Unknown APRS Data
Type Indicator "A",..."??
Can you share your python script?? Are you sure you're not sending
formatting strings like a /n, etc?
I see from the APRS101 that types of A-S are marked as
"do not use".? ?I'm wondering if this is an issue with my script,
or is it the way CBEACON is set up?? ?For info, my CBEACON reads
as follows - CBEACON sendto=0 delay=1 every=0:30 via=WIDE1-1
infocmd="/usr/local/bin/test.py"
