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

 


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

 


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

 


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

 


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