Date   

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

 


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

rdisney007@...
 

Unsubscribe


On Mon, Apr 27, 2020, 03:25 Ryszard Labus via groups.io <r.labus=sinux.com.pl@groups.io> wrote:

What i am doing wrong?

I cant see FT-3D as recognized?

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


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

Steven Joerger
 

On 4/26/2020 11:15 PM, Lynn Deffenbaugh wrote:
Yes, you read the subject correctly.  There's a new development version of APRSIS32 on the web!  Just check About and it should be available for download, assuming that you're configured for the Development release (see PS).
So, what's new you ask?  Well, here's what I could determine I've done since the last release.
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.
My APRSIS32 application is crashing when I attempt to add a FT8/JS8Call object. I am running the version "Built 2020/04/27 08:11".

Is there someplace I can post the dmp/dmz files that are created for review?

Thanks,
Steve N4TQU


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

Glenn O'Connor
 

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)

Fred Hillhouse
 

Dashes may be going away?

R appears to be constant.

 

For reference:

 

https://www.yaesu.com/?cmd=DisplayProducts&DivisionID=65&ProdCatID=111

 

I searched for APRS on the Yaesu site. It returns a more extensive list than what is in the current line up.

 

 

 

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

 

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

 




Avast logo

This email has been checked for viruses by Avast antivirus software.
www.avast.com



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

Lynn Deffenbaugh
 

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)

Lynn Deffenbaugh
 

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)

Dennis Griffin
 

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)

Ryszard Labus
 

It works well now.

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?

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


Updated ToCalls & Mic-E (Dev 2020/04/27 08:11)

Lynn Deffenbaugh
 

Just pushed out another new development version that fully catches up with the current ToCall and Mic-E definitions from:

http://www.aprs.org/aprs11/tocalls.txt

http://www.aprs.org/aprs12/mic-e-types.txt

The View / Platforms / Yaesu now shows 40 FT3Ds on my full feed APRSIS32 instance.

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


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

Lynn Deffenbaugh
 

From http://www.aprs.org/aprs11/tocalls.txt

In APRS, the AX.25  Destination address is not used for packet 
routing as is normally done in AX.25.  So APRS uses it for two 
things.  The initial APxxxx is used as a group identifier to make 
APRS packets instanantly recognizable on shared channels.  Most 
applicaitons ignore all non APRS packets.  The remaining 4 xxxx
bytes of the field are available to indicate the software version 
number or application.
The AX.25 Destination address is also referred to as the ToCall.  In a humanly-readable (aka TNC-2) APRS packets, this is the characters immediately following the > after the initial source (or originating) callsign-SSID.  Note that for Mic-E compressed packets, the ToCall carries some of the location information bits and not the software identification.

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

On 4/27/2020 8:22 AM, Glenn O'Connor wrote:
What exactly doess the "To" signify, Lynn? The type of equipment used?

Glenn-KF0ED

On Mon, Apr 27, 2020, 07:15 Lynn Deffenbaugh <kj4erj@...> wrote:
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?

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


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

Glenn O'Connor
 

What exactly doess the "To" signify, Lynn? The type of equipment used?

Glenn-KF0ED


On Mon, Apr 27, 2020, 07:15 Lynn Deffenbaugh <kj4erj@...> wrote:
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?

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


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

Lynn Deffenbaugh
 

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?

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


Re: Password

Rob Giuliano
 

Passcode for W8KTM is 8846

This passcode will work for any -SSID (http://aprsisce.wikidot.com/doc:ssids) you choose to use.
Because it is actually the APRS-IS network passcode, it should also work with other APRS-IS client software.

73 de
Robert Giuliano
KB8RCO



On Monday, April 27, 2020, 1:48:33 AM EDT, Jason Means <jsmeans76@...> wrote:


Would like a password for APRS IS

Thanks

Jason Means 
W8KTM

--
Jason Means
1506 Byng Dr.
S. Charleston, WV 25303
(304) 561-7939
MSSL, BSOL, LMT
W8KTM 


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

Ryszard Labus
 

What i am doing wrong?

I cant see FT-3D as recognized?

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


Password

Jason Means
 

Would like a password for APRS IS

Thanks

Jason Means 
W8KTM

--
Jason Means
1506 Byng Dr.
S. Charleston, WV 25303
(304) 561-7939
MSSL, BSOL, LMT
W8KTM 


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

Lynn Deffenbaugh
 

Yes, you read the subject correctly.  There's a new development version of APRSIS32 on the web!  Just check About and it should be available for download, assuming that you're configured for the Development release (see PS).

So, what's new you ask?  Well, here's what I could determine I've done since the last release.

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.

2) Better file detection logic for file-based objects.  This includes the new JS8Call and FT8 objects as well as the previous JT65 and weather station objects.

3) Support for "Hashes".  These are similar to !shriek!s, but are delimited by a single preceding #, as in #JS8 or #EVENT.  More details on this to follow at some later date.

4) Driving GPX overlays now supports multiple segments in a single file.

5) Messages are now gated from the APRS-IS to RF even if the source station has been copied inside a third-party packet.  It seems that some Direwolf gates are taking source messages and gating them to RF as third-party packets which was causing a receiving APRSIS32 IGate to no longer gate messages from that station since it was presumably already on RF.

6) Battery current telemetry is now transmitted in 10s of mA to keep the value in the valid range of 0..255.  Definitions were updated accordingly.

7) If too many stations were known, some popup menu items would select the wrong action.  This has been (hopefully) corrected.  I think the limit was something like > 30,000 known stations.

8) MBTiles database storage for map tiles is there, but not well documented nor exposed to the user at this point.  I've got more work to do here, especially on expiration and refresh so more to come.

9) Tile server URLs are no longer limited to 128 characters. They can now go up to 260 (MAX_PATH in C).

10) KISS (aka AX.25) callsigns are now limited to A..Z and 0..9. Invalid characters are simply removed from the transmitted callsign, so beware!

11) The ToCall was updated from APWW10 to APWW11 (finally!).

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

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

PS.  So, your About box says that you're running the general release from 2012?  Follow the instructions at the following link to re-configure for development releases.

http://aprsisce.wikidot.com/doc:development-version


Re: aprsis32 and fldig kiss interface

Lynn Deffenbaugh
 

It's actually just "winfldigi" or https://groups.io/g/winfldigi


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

On 4/24/2020 5:40 PM, John Rabold wrote:
Miguel, in case it helps, Dave Freese W1HKJ is the software developer of fldigi and the other applications in the NBEMS suite. He and fldigi users support fldigi in the groups.io group named "nbems". He also supports the Windows version of the NBEMS applications in the groups.io group named "Win-FLDIGI".

John / KS6M


Re: aprsis32 and fldig kiss interface

John Rabold
 

Miguel, in case it helps, Dave Freese W1HKJ is the software developer of fldigi and the other applications in the NBEMS suite. He and fldigi users support fldigi in the groups.io group named "nbems". He also supports the Windows version of the NBEMS applications in the groups.io group named "Win-FLDIGI".

John / KS6M

1441 - 1460 of 35661