I just updated my application to the build 2020/04/27 14:13 and it still crashes when I try to create a FT8 object. I get as far as selecting my ALL.TXT file, another window opens briefly then the

While working on that last informational message, I noticed that I ahd the wrong default -SSID for FT8 objects. It is now -F8 as I originally intended. Oh, and if you decide to play

Ok, for a bit of background and description of this. It exists because I was working with JT65 a few years ago and wanted a way to visualize the gridsquares of the stations I was copying.

After 20+ years with APRS, I never did understand the Mic-E's. I dug up an old message'S raw data from my rig: KF0ED-9>APY400,CHILLI*,WIDE2-1,qAR,KD0YUJ::KF0ED :test{0 Tnx fer all you do

That's a Mic-E posit. You need to send a message to see what it uses as a ToCall. Mic-E posits put part of the location data in the ToCall field. Lynn (D) - KJ4ERJ - Author of

Due to the plethora of emails I can tell this is vitally important in APRS, but can someone explain where and what this is? Thanks. Arnold, KQ6DI 1) New support for

From a -400… KC0GP-9>SYTU5S,CHILLI,RAYCO,WIDE2*,qAR,N0JVW:`y@Arr6k/`"6;}147.225MHz Toff +060_%

My 400 sent an ack back to me earlier today. Its showing APY400. KB3KBR-12 is the ssid. Greg KB3KBR Sent from my Verizon, Samsung Galaxy smartphone

Well, that didn't come out like I had planned. It was supposed to say that you've likely hit the nail on the head and I'll quit thinking about that one at least. Now we still need to

Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

The FTM-400 is in http://www.aprs.org/aprs12/mic-e-types.txt, but not http://www.aprs.org/aprs11/tocalls.txt. Can someone that has access to a known FTM-400 check the raw packets at

Greg, That is EXACTLY why I'm wrapping up loose ends on the current development release! I've done some work on MbTiles as a map storage format in APRSISMO and want to port that

Like i said APRS to-call can be configured from CPS. This is bad way, that was an example. R W dniu 2020-04-27 o 18:10, Lynn Deffenbaugh pisze: -- SINUX Ryszard

Hi Lynn, I believe that FT1D, FT2D & FT3D are intended to be base model designators, with the R signifying the model being appropriate for the American(?) market. Each of these were/are also

Hi Lynn, Before you dig into making a lot of changes, is there any chance you could take the prior version and make it the standard release (not development)? Seems like it's about

The 400 was added in previous release. My mobile is a 400 and has been working for quite a while. Greg KB3KBR Sent from my Verizon, Samsung Galaxy smartphone

Brandmeister will source any DMR radio that produces the proper GPS info, even if the radio doesn't support DMR-PRS or APRS natively. So, when Brandmeister sources a DMR-PRS packet for a Motorola

Lynn, I see no listing for the Yaesu FTM-400. The -350, yes. 73, Glenn-KF0ED

SQ9MDD-5 shows up as "App: APRSd, etc (878)" because it uses a ToCall of APD878 which at some point in the past, but apparently not in the current ToCalls was defined as: "APDxxx",

Another example of a Brandmeister sourced (DPRS) DMR xmission: “04/27/2020 11:01:07 AM-05:00: K9BVA>APBM1D,K9BVA,DMR*,qAR,K9BVA:@160105h3845.73N/09333.03W[283/000Patrick ”