Yep, I looked at all of the advanced APRS manuals from all of the Yaesu radios. I have RTsystem programming software for those radio as well. CUSTOM 0-6 can not be edited. Few day ago for the heck

Did you look at the PDF that I previously attached of pages 38-41 of the FT2DR APRS manual? I'm not talking about the Mic-E comments that includes the Custom options, but the actual

Lynn, Thank you for the reply. Sorry, I forgot to indicate the SSID in question. At any rate, Yaesu radios I have none of the "CUSTOM 0-6" can not be edited. I am not even sure what they were

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.

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

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,

Just put "PHG0000" without the quotes at the end of your comment text. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

http://blog.aprs.fi/2009/02/deleting-old-phg-data.html Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

OK I got a new "station heard directly by N7TTQ-9" so I believe things are working fine 100.000% and won't touch a thing. Thanks. Jeff

I got it. Thanks! It's just that my nearest gateway VA6ATA-1 used to constantly update it's "last heard" from me for a few weeks now it suddenly does not. I can see in APRSISCE that he heard me and I

Just to be clear, their directly injected packet will show up at aprs.fi via TCPIP*, but none of their RF packet receivers will get "credit" for having heard that station because those

Any time you configure an RF Port, it internally disables and re-enables the port for the new settings to get everywhere they need to go. And that means it fires the <CloseCmd>s and

ahh but I get that if they direct inject the station it won't show up on APRS.fi... ok.

Thanks, but guys like VA6ATA-1 had, in the past, reported the last heard on both ends like clockwork and now not? Now, it might be HE changed his config somehow which messed things up after 4:36 pm on

From https://aprs.fi/doc/guide/aprsfi-info-pages.html Read through that quote and I suspect that most of the packets you're copying are either a) injecting directly to the

I saw folks on the forum on the APRSIS website complain about this last year but I saw no resolution, by the way. Whatever they did/didn't do, I did.

Hi, although my raw packets are being reported by APRS.FI, and that I'm active, positions and stations that have clearly been decoded on my RF port are suddenly not being shown under "Stations heard

My bad that I didn't post it here. It's all on me, sorry man! It was more or less not entering KISS mode correctly 'cause you have to cycle power on the SCS tracker after exiting the program in

So it would only work on RF received packets going to APRSIS32 from an 'AGW device' like AGWpe, Direwolf, etc. I have only used it with Direwolf and only on very limited occasions. It did provide an

Hi Rob and thanks for reply, Yes I also use AGW PE on HF for ROBUST PACKET and UZ7HO Soundmodem for AX25 PACKET so at least I can see the heardlist this way. On VHF though I use an APRS Voyager VHF