I should have also mentioned that when doing the PHG0000 from a
radio, you need to transmit the beacon containing the text in
range of an IGate to get it through the APRS-IS to aprs.fi.
Checking the raw packets of the station that transmitted the
packet should be sufficient to ensure that at least one has been
delivered. aprs.fi's Decoded view is also quite informative to
ensure that it interpreted your intent correctly.
It appears that you actually DID get the PHG0000 entered into a
radio correctly, but aprs.fi's parser didn't parse it.
2021-02-04 17:19:52
EST: W3KIT>SYPR8P,KV3B-2*,WIDE1*,WIDE2-1,qAR,W4KEL-12:`iZNl!z0\`"5&}PHG0000_%
type:
location
format:
mice
srccallsign:
W3KIT
dstcallsign:
SYPR8P
latitude:
39.046666666667 °
longitude:
-77.041666666667 °
course:
194 °
speed: 0
km/h
altitude:
106 m
symboltable:
\
symbolcode:
0
mbits:
111
posresolution:
18.52 m
posambiguity:
0
comment:
`PHG0000_%
But when you did it from APRSIS32, it got the PHG extracted
correctly.
2021-02-04 17:55:22
EST: W3KIT>APWW11,KV3B-2,WIDE2*,qAR,WB2IFS-10:@225520h/:eml;#%W- sTPHG0000
type:
location
format:
compressed
srccallsign:
W3KIT
dstcallsign:
APWW11
latitude:
39.046864745384 °
longitude:
-77.04128360889 °
symboltable:
/
symbolcode:
-
messaging:
1
posresolution:
0.291 m
phg:
0000
timestamp:
1612479320 - 2021-02-04 17:55:20 EST
So it seems that where the radio put the comment caused aprs.fi's
parser to see a leading ` which caused it to not "see" the PHG0000
for what it was intended to be.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
PS. In the future, please state exactly
callsign-SSIDs when asking for help. It took me a while to
translate "one of my generic SSID" to W3KIT with no (actually -0)
SSID to find the actual station you were trying to fix.
On 2/5/2021 9:20 AM, Lynn Deffenbaugh
wrote:
Different radios call it different things, and unfortunately I
believe some radios call the Mic-E "status" field their
"comment".
But I believe that every APRS-capable radio has somewhere that
you can enter free-form text to be included with your position
beacon and that's exactly where the PGH00000 would have gone to
clear out aprs.fi's memory.
There is nothing "special" about APRSIS32's "comment" text,
it's all in the label given.
I don't have any Yaesu APRS radios, but in my Kenwood D74,
there's a "Position Comment" (menu 502) which is NOT it (that's
the Mic-E select-a-status from a list including things like
Enroute, In Service, Returning, and so forth) and "Status Text"
(Menu 503) which is where you can pre-configure up to 5
different free-form texts and select one to be included on
beacons.
Lynn (D) - KJ4ERJ - Author of APRSISCE
for Windows Mobile and Win32
PS. It looks like Yaesu does something
similar to the D74. I've attached 3 pages from the Yaesu APRS
manual where it describes the required free-form comment text.
On 2/5/2021 5:19 AM, Komkit Listisard
via groups.io wrote:
Lynn,
What is the different between APRSIS32 "comment" text comparing
to another radios with beacon status or comment text? I have
tried to rid of an unwanted PHG by using the radios (FT2D, FT3D,
FTM-100 and FTM-400 - I could not find the way to enter PHG0000
to clear it.
I have to fired up APRSIS32 and edited the SSID to the SSID that
I want to clear the PHG and that was the only way that worked.
Is the "comment" field a special field that ordinary APRS radio
does not have and only existed with APRSIS32?
73, Kit W3KIT
