Date   

Re: FTM-400 ToCall was: Dev 2020/04/26 22:23

Glenn O'Connor
 

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 Lynn!

Glenn-KF0ED


Re: FTM-400 ToCall was: Dev 2020/04/26 22:23

Lynn Deffenbaugh
 

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 APRSISCE for Windows Mobile and Win32

On 4/27/2020 1:53 PM, Glenn O'Connor wrote:

 From a -400…

 

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

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Greg Depew
Sent: Monday, April 27, 2020 12:52 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] FTM-400 ToCall was: Dev 2020/04/26 22:23

 

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

 

 

 

-------- Original message --------

From: Lynn Deffenbaugh <kj4erj@...>

Date: 4/27/20 13:49 (GMT-05:00)

Subject: [APRSISCE] FTM-400 ToCall was: Dev 2020/04/26 22:23

 

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 aprs.fi and confirm what ToCall they are using for non-position packets?  Their position packets are Mic-E which is how we're identifying them.

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

On 4/27/2020 12:15 PM, Greg Depew wrote:

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

 

 

 

-------- Original message --------

From: Glenn O'Connor <ka0lnr37@...>

Date: 4/27/20 12:11 (GMT-05:00)

Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ

 

On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 


Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Arnold Harding - KQ6DI
 

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 JS8Call and FT8 log-scraping objects. This is
similar to the JT65 scraper that already existed. Simply create new
object of the appropriate type and point it to your ALL.TXT log file for
the corresponding program. Object will be created for any detected
station for which a grid square is available. These are objects local to
your instance only.


Re: FTM-400 ToCall was: Dev 2020/04/26 22:23

Glenn O'Connor
 

 From a -400…

 

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

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Greg Depew
Sent: Monday, April 27, 2020 12:52 PM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] FTM-400 ToCall was: Dev 2020/04/26 22:23

 

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

 

 

 

-------- Original message --------

From: Lynn Deffenbaugh <kj4erj@...>

Date: 4/27/20 13:49 (GMT-05:00)

Subject: [APRSISCE] FTM-400 ToCall was: Dev 2020/04/26 22:23

 

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 aprs.fi and confirm what ToCall they are using for non-position packets?  Their position packets are Mic-E which is how we're identifying them.

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

On 4/27/2020 12:15 PM, Greg Depew wrote:

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

 

 

 

-------- Original message --------

From: Glenn O'Connor <ka0lnr37@...>

Date: 4/27/20 12:11 (GMT-05:00)

Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ

 

On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 


Re: FTM-400 ToCall was: Dev 2020/04/26 22:23

Greg Depew
 

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



-------- Original message --------
From: Lynn Deffenbaugh <kj4erj@...>
Date: 4/27/20 13:49 (GMT-05:00)
To: APRSISCE@groups.io
Subject: [APRSISCE] FTM-400 ToCall was: Dev 2020/04/26 22:23

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 aprs.fi and confirm what ToCall they are using for non-position packets?  Their position packets are Mic-E which is how we're identifying them.

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

On 4/27/2020 12:15 PM, Greg Depew wrote:
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



-------- Original message --------
From: Glenn O'Connor <ka0lnr37@...>
Date: 4/27/20 12:11 (GMT-05:00)
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 


Re: Yaesu FTnD was: Dev 2020/04/26 22:23

Lynn Deffenbaugh
 

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 determine what unique (or not) ToCall these devices use when sending a non-Mic-E packet like a message or an ack (which is really just a normal APRS message with a pre-defined content).

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

On 4/27/2020 1:46 PM, Lynn Deffenbaugh wrote:



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

On 4/27/2020 12:20 PM, Dennis Griffin wrote:
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 available with a DE suffix as well as the DR suffix, and the FT1D also had an XDR suffix follow-on model.

This is similar to how Icom & Kenwood append an A or an E to many (all?) of their models to signify American or European market models.

I suspect that may be why Bob B listed only FT3D, so that any variation of that base model would be ID’d in APRS correctly.

You may recall seeing this from the TH-D74 FW update notes:

Updated item : (Version 1.08  1.09) [June 26, 2019]

The following features are updated.

1. Enables decoding of standard APRS telemetry format.(Displays telemetry packets sent from the PSAT2.)
2. Enables display of the model name "FT3D" when received an APRS position packet from the Yaesu FT3DR/E.

73 de Dennis KD7CAC
Scottsdale, AZ


On Apr 27, 2020, at 7:59 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

So maybe we got the hyphen right, but are still worng (sic)...

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:
In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

Thanks for adding it correctly, Lynn.

73 de Dennis KD7CAC
Scottsdale, AZ


On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:
Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.

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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:
12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl



Yaesu FTnD was: Dev 2020/04/26 22:23

Lynn Deffenbaugh
 



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

On 4/27/2020 12:20 PM, Dennis Griffin wrote:
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 available with a DE suffix as well as the DR suffix, and the FT1D also had an XDR suffix follow-on model.

This is similar to how Icom & Kenwood append an A or an E to many (all?) of their models to signify American or European market models.

I suspect that may be why Bob B listed only FT3D, so that any variation of that base model would be ID’d in APRS correctly.

You may recall seeing this from the TH-D74 FW update notes:

Updated item : (Version 1.08  1.09) [June 26, 2019]

The following features are updated.

1. Enables decoding of standard APRS telemetry format.(Displays telemetry packets sent from the PSAT2.)
2. Enables display of the model name "FT3D" when received an APRS position packet from the Yaesu FT3DR/E.

73 de Dennis KD7CAC
Scottsdale, AZ


On Apr 27, 2020, at 7:59 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

So maybe we got the hyphen right, but are still worng (sic)...

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:
In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

Thanks for adding it correctly, Lynn.

73 de Dennis KD7CAC
Scottsdale, AZ


On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:
Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.

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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:
12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl



FTM-400 ToCall was: Dev 2020/04/26 22:23

Lynn Deffenbaugh
 

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 aprs.fi and confirm what ToCall they are using for non-position packets?  Their position packets are Mic-E which is how we're identifying them.

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

On 4/27/2020 12:15 PM, Greg Depew wrote:
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



-------- Original message --------
From: Glenn O'Connor <ka0lnr37@...>
Date: 4/27/20 12:11 (GMT-05:00)
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 


General release was: Dev: 2020/04/26 22:23

Lynn Deffenbaugh
 

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 (complete the port, actually) into APRSISCE/32, but I want to get the current version into general release first.

Yes, a new general release is coming.  And the release notes will leave a lot to be desired unless someone would like to take all of the accumulated raw releases from Development and try to boil out the features worth mentioning for the General release update?

I can provide the raw text to any suitable victim... er volunteer!

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

On 4/27/2020 12:20 PM, Greg D wrote:
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 time, no? 

Greg  KO6TH


Greg Depew wrote:
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



-------- Original message --------
From: Glenn O'Connor <ka0lnr37@...>
Date: 4/27/20 12:11 (GMT-05:00)
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 



Re: AnyTone 868 was: Dev 2020/04/26 22:23

Ryszard Labus
 

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:

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", "APRSd, etc"

But certainly APD878 is not currently defined in the ToCall list that I can see.

 APD  APD4xx  UP4DAR platform
      APDDxx  DV-RPTR Modem and Control Center Software 
      APDFxx  Automatic DF units
      APDGxx  D-Star Gateways by G4KLX ircDDB
      APDHxx  WinDV (DUTCH*Star DV Node for Windows)
      APDInn  DIXPRS - Bela, HA5DI
      APDIGI  Used by PSAT2 to indicate the digi is ON
      APDIGI  digi ON for PSAT2 and QIKCOM-2
      APDKxx  KI4LKF g2_ircddb Dstar gateway software
      APDNOx  APRSduino by DO3SWW
      APDOxx  ON8JL Standalone DStar Node
      APDPRS  D-Star originated posits
      APDRxx  APRSdroid Android App http://aprsdroid.org/
      APDSXX  SP9UOB for dsDigi and ds-tracker
      APDTxx  APRStouch Tone (DTMF)
      APDTMF  digi off mode on QIKCOM2 and DTMF ON
      APDUxx  U2APRS by JA7UDE
      APDVxx  OE6PLD's SSTV with APRS status exchange
      APDWxx  DireWolf, WB2OSZ

But if it is configurable somewhere, it should be set to APAT81 according to the definition:

      APATxx  for Anytone. 81 for 878 HT 
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  According to http://wa8lmf.net/bruninga/aprs/tocalls.txt

 APD  APRSd,  etc
      APDTxx  APRStouch Tone (DTMF)
      APDFxx  Automatic DF units
      APDPRS  D-Star originated posits

Gotta love history revisionism...

On 4/27/2020 11:52 AM, Ryszard Labus via groups.io wrote:

Hi.

APBM1D is DPRS(DMR position) frame oryginated from Brand Meister network.
Anytone 878 can't send compressed frame. And dest call can be changed (!) from CPS
It's look like this:

2020-04-27T15:46:45.448 RF[KISS TC DIGI LOCALNET][1200] SQ9MDD-5>APD878,WIDE1-1,WIDE2-1:!5215.01N/02055.59E[000/000/A=000453145.574MHz lub SR5WZ

SQ9MDD.

W dniu 2020-04-27 o 17:38, Lynn Deffenbaugh pisze:

KF0ED-15 shows as "App: BrandMeister DMR (1D)" because if you look at the raw packet, it is using a ToCall of APBM1D, not the APATxx which is defined for Anytone.  And it is sending an "@" position packet, not a Mic-E packet, so the type code won't matter (regardless of the fact that only 878 has a type code defined).

I'm not sure I understand how an "IS only" device is coming through with a BrandMeister ToCall, but I don't know anything about DMR and/or its links to APRS.

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

On 4/27/2020 11:16 AM, Glenn O'Connor wrote:

I’ve just enabled my KF0ED-15 for my AnyTone 868. Its APRS is IS only. The 878 does RF and IS.

 

Glenn-KF0ED

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl


Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Dennis Griffin
 

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 available with a DE suffix as well as the DR suffix, and the FT1D also had an XDR suffix follow-on model.

This is similar to how Icom & Kenwood append an A or an E to many (all?) of their models to signify American or European market models.

I suspect that may be why Bob B listed only FT3D, so that any variation of that base model would be ID’d in APRS correctly.

You may recall seeing this from the TH-D74 FW update notes:

Updated item : (Version 1.08  1.09) [June 26, 2019]

The following features are updated.

1. Enables decoding of standard APRS telemetry format.(Displays telemetry packets sent from the PSAT2.)
2. Enables display of the model name "FT3D" when received an APRS position packet from the Yaesu FT3DR/E.

73 de Dennis KD7CAC
Scottsdale, AZ


On Apr 27, 2020, at 7:59 AM, Lynn Deffenbaugh <kj4erj@...> wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

So maybe we got the hyphen right, but are still worng (sic)...

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:
In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

Thanks for adding it correctly, Lynn.

73 de Dennis KD7CAC
Scottsdale, AZ


On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:
Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.

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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:
12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl



Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Greg D
 

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 time, no? 

Greg  KO6TH


Greg Depew wrote:

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



-------- Original message --------
From: Glenn O'Connor <ka0lnr37@...>
Date: 4/27/20 12:11 (GMT-05:00)
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 



Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Greg Depew
 

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



-------- Original message --------
From: Glenn O'Connor <ka0lnr37@...>
Date: 4/27/20 12:11 (GMT-05:00)
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 


Re: AnyTone 868 was: Dev 2020/04/26 22:23

Randy Love
 

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 XPR6550, for example, there's no source code for a XPR6550 as it's not an APRS device, but it will send a GPS packet to Brandmeister when properly programmed and set up correctly in BM systems.

Randy
WF5X


On Mon, Apr 27, 2020 at 12:03 PM Glenn O'Connor <ka0lnr37@...> wrote:

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

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Ryszard Labus via groups.io
Sent: Monday, April 27, 2020 10:52 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] AnyTone 868 was: Dev 2020/04/26 22:23

 

Hi.

APBM1D is DPRS(DMR position) frame oryginated from Brand Meister network.
Anytone 878 can't send compressed frame. And dest call can be changed (!) from CPS
It's look like this:

2020-04-27T15:46:45.448 RF[KISS TC DIGI LOCALNET][1200] SQ9MDD-5>APD878,WIDE1-1,WIDE2-1:!5215.01N/02055.59E[000/000/A=000453145.574MHz lub SR5WZ

SQ9MDD.

W dniu 2020-04-27 o 17:38, Lynn Deffenbaugh pisze:

KF0ED-15 shows as "App: BrandMeister DMR (1D)" because if you look at the raw packet, it is using a ToCall of APBM1D, not the APATxx which is defined for Anytone.  And it is sending an "@" position packet, not a Mic-E packet, so the type code won't matter (regardless of the fact that only 878 has a type code defined).

I'm not sure I understand how an "IS only" device is coming through with a BrandMeister ToCall, but I don't know anything about DMR and/or its links to APRS.

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

On 4/27/2020 11:16 AM, Glenn O'Connor wrote:

I’ve just enabled my KF0ED-15 for my AnyTone 868. Its APRS is IS only. The 878 does RF and IS.

 

Glenn-KF0ED

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ




On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl


Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Glenn O'Connor
 

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

 

 

73,

Glenn-KF0ED

 

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 


Re: AnyTone 868 was: Dev 2020/04/26 22:23

Lynn Deffenbaugh
 

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", "APRSd, etc"

But certainly APD878 is not currently defined in the ToCall list that I can see.

 APD  APD4xx  UP4DAR platform
      APDDxx  DV-RPTR Modem and Control Center Software 
      APDFxx  Automatic DF units
      APDGxx  D-Star Gateways by G4KLX ircDDB
      APDHxx  WinDV (DUTCH*Star DV Node for Windows)
      APDInn  DIXPRS - Bela, HA5DI
      APDIGI  Used by PSAT2 to indicate the digi is ON
      APDIGI  digi ON for PSAT2 and QIKCOM-2
      APDKxx  KI4LKF g2_ircddb Dstar gateway software
      APDNOx  APRSduino by DO3SWW
      APDOxx  ON8JL Standalone DStar Node
      APDPRS  D-Star originated posits
      APDRxx  APRSdroid Android App http://aprsdroid.org/
      APDSXX  SP9UOB for dsDigi and ds-tracker
      APDTxx  APRStouch Tone (DTMF)
      APDTMF  digi off mode on QIKCOM2 and DTMF ON
      APDUxx  U2APRS by JA7UDE
      APDVxx  OE6PLD's SSTV with APRS status exchange
      APDWxx  DireWolf, WB2OSZ

But if it is configurable somewhere, it should be set to APAT81 according to the definition:

      APATxx  for Anytone. 81 for 878 HT 
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

PS.  According to http://wa8lmf.net/bruninga/aprs/tocalls.txt

 APD  APRSd,  etc
      APDTxx  APRStouch Tone (DTMF)
      APDFxx  Automatic DF units
      APDPRS  D-Star originated posits

Gotta love history revisionism...

On 4/27/2020 11:52 AM, Ryszard Labus via groups.io wrote:

Hi.

APBM1D is DPRS(DMR position) frame oryginated from Brand Meister network.
Anytone 878 can't send compressed frame. And dest call can be changed (!) from CPS
It's look like this:

2020-04-27T15:46:45.448 RF[KISS TC DIGI LOCALNET][1200] SQ9MDD-5>APD878,WIDE1-1,WIDE2-1:!5215.01N/02055.59E[000/000/A=000453145.574MHz lub SR5WZ

SQ9MDD.

W dniu 2020-04-27 o 17:38, Lynn Deffenbaugh pisze:

KF0ED-15 shows as "App: BrandMeister DMR (1D)" because if you look at the raw packet, it is using a ToCall of APBM1D, not the APATxx which is defined for Anytone.  And it is sending an "@" position packet, not a Mic-E packet, so the type code won't matter (regardless of the fact that only 878 has a type code defined).

I'm not sure I understand how an "IS only" device is coming through with a BrandMeister ToCall, but I don't know anything about DMR and/or its links to APRS.

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

On 4/27/2020 11:16 AM, Glenn O'Connor wrote:

I’ve just enabled my KF0ED-15 for my AnyTone 868. Its APRS is IS only. The 878 does RF and IS.

 

Glenn-KF0ED

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl


Re: AnyTone 868 was: Dev 2020/04/26 22:23

Glenn O'Connor
 

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

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Ryszard Labus via groups.io
Sent: Monday, April 27, 2020 10:52 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] AnyTone 868 was: Dev 2020/04/26 22:23

 

Hi.

APBM1D is DPRS(DMR position) frame oryginated from Brand Meister network.
Anytone 878 can't send compressed frame. And dest call can be changed (!) from CPS
It's look like this:

2020-04-27T15:46:45.448 RF[KISS TC DIGI LOCALNET][1200] SQ9MDD-5>APD878,WIDE1-1,WIDE2-1:!5215.01N/02055.59E[000/000/A=000453145.574MHz lub SR5WZ

SQ9MDD.

W dniu 2020-04-27 o 17:38, Lynn Deffenbaugh pisze:

KF0ED-15 shows as "App: BrandMeister DMR (1D)" because if you look at the raw packet, it is using a ToCall of APBM1D, not the APATxx which is defined for Anytone.  And it is sending an "@" position packet, not a Mic-E packet, so the type code won't matter (regardless of the fact that only 878 has a type code defined).

I'm not sure I understand how an "IS only" device is coming through with a BrandMeister ToCall, but I don't know anything about DMR and/or its links to APRS.

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

On 4/27/2020 11:16 AM, Glenn O'Connor wrote:

I’ve just enabled my KF0ED-15 for my AnyTone 868. Its APRS is IS only. The 878 does RF and IS.

 

Glenn-KF0ED

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ




On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl


Re: AnyTone 868 was: Dev 2020/04/26 22:23

Ryszard Labus
 

Hi.

APBM1D is DPRS(DMR position) frame oryginated from Brand Meister network.
Anytone 878 can't send compressed frame. And dest call can be changed (!) from CPS
It's look like this:

2020-04-27T15:46:45.448 RF[KISS TC DIGI LOCALNET][1200] SQ9MDD-5>APD878,WIDE1-1,WIDE2-1:!5215.01N/02055.59E[000/000/A=000453145.574MHz lub SR5WZ

SQ9MDD.

W dniu 2020-04-27 o 17:38, Lynn Deffenbaugh pisze:

KF0ED-15 shows as "App: BrandMeister DMR (1D)" because if you look at the raw packet, it is using a ToCall of APBM1D, not the APATxx which is defined for Anytone.  And it is sending an "@" position packet, not a Mic-E packet, so the type code won't matter (regardless of the fact that only 878 has a type code defined).

I'm not sure I understand how an "IS only" device is coming through with a BrandMeister ToCall, but I don't know anything about DMR and/or its links to APRS.

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

On 4/27/2020 11:16 AM, Glenn O'Connor wrote:

I’ve just enabled my KF0ED-15 for my AnyTone 868. Its APRS is IS only. The 878 does RF and IS.

 

Glenn-KF0ED

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl


AnyTone 868 was: Dev 2020/04/26 22:23

Lynn Deffenbaugh
 

KF0ED-15 shows as "App: BrandMeister DMR (1D)" because if you look at the raw packet, it is using a ToCall of APBM1D, not the APATxx which is defined for Anytone.  And it is sending an "@" position packet, not a Mic-E packet, so the type code won't matter (regardless of the fact that only 878 has a type code defined).

I'm not sure I understand how an "IS only" device is coming through with a BrandMeister ToCall, but I don't know anything about DMR and/or its links to APRS.

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

On 4/27/2020 11:16 AM, Glenn O'Connor wrote:

I’ve just enabled my KF0ED-15 for my AnyTone 868. Its APRS is IS only. The 878 does RF and IS.

 

Glenn-KF0ED

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ



On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 


Re: JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

Glenn O'Connor
 

I’ll correct my recent post. I see the 868’s transmissions are covered thusly, “APBMxx  BrandMeister DMR Server for R3ABM”.

 

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Glenn O'Connor via groups.io
Sent: Monday, April 27, 2020 10:16 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

I’ve just enabled my KF0ED-15 for my AnyTone 868. Its APRS is IS only. The 878 does RF and IS.

 

Glenn-KF0ED

 

From: APRSISCE@groups.io <APRSISCE@groups.io> On Behalf Of Lynn Deffenbaugh
Sent: Monday, April 27, 2020 10:02 AM
To: APRSISCE@groups.io
Subject: Re: [APRSISCE] JS8CAll/FT8 Log Scrapers (Dev 2020/04/26 22:23)

 

Also, I just noticed that these devices are not listed in http://www.aprs.org/aprs11/tocalls.txt

Can someone that owns each of these devices send a message to anyone and check the raw packets at aprs.fi to see what ToCall they are actually using?

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

On 4/27/2020 10:59 AM, Lynn Deffenbaugh wrote:

I only mirrored what Bob had listed at http://www.aprs.org/aprs12/mic-e-types.txt

Which leads me to ask if the model number actually includes the final R as you showed but is NOT included in Bob's definitions?

 

So maybe we got the hyphen right, but are still worng (sic)...

 

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

On 4/27/2020 10:45 AM, Dennis Griffin wrote:

In case anyone is confused, Yaesu didn’t include a hyphen in the FT1DR, FT2DR & FT3DR HT model descriptors, as they have for every other transceiver model that I’m aware of since the FT-51R.

 

Thanks for adding it correctly, Lynn.

 

73 de Dennis KD7CAC
Scottsdale, AZ

 

On Apr 27, 2020, at 6:48 AM, Ryszard Labus via groups.io <r.labus@...> wrote:

 

It works well now.

<lobbcmjhfakpnhcf.png>

Really good job.
Thank You.

R.

W dniu 2020-04-27 o 14:00, Lynn Deffenbaugh pisze:

Well, because those notes were accumulated from the changes done over the past 2 years, not necessarily recently.  FT-3D will be in the next update, hopefully later today as I catch up on more stuff.


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

On 4/27/2020 4:03 AM, Ryszard Labus via groups.io wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

<hicijalgjldiggho.png>

W dniu 2020-04-27 o 05:15, Lynn Deffenbaugh pisze:

12) The recognized ToCalls and Mic-E type codes have been update per Bob's pages.

-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl
-- 
SINUX Ryszard Labus
ul. Domaniewska 47/10 02-672 Warszawa
NIP: 548-138-01-53    tel: 666385002
          r.labus@...
http://sinux.pl   http://sinux.com.pl

 

1101 - 1120 of 35339