Date   

Re: Object PHG settings

Randy Allen
 

James,

Roger that.  I am aware of the differences between AGL, MSL and HAAT.

The heights were given to me by the Trustee.  Since one of the numbers does not match where I know the antenna is AGL, I'm assuming he took that into consideration. I'll discuss it with him next time we talk.  This is my first approximation.

Right now I think the transmitted PHG circle is actually smaller than the actual coverage.  We don't have a lot of data yet as the sites have only been really advertised recently as we have been gearing up for the Red Cross Winlink drill this month.  (I'm less than 5 miles from the site and am literally line of sight to tower when I step outside of my house)

As we get in actual user reports I'll look into adjusting numbers to match actual coverage as close as possible.  And by actual user I mean a user on the ground.  I know the Digi can reach another Winlink RMS 30 miles south of here, but since both are on high towers, I'm not figuring that into our coverage area.

Hopefully the Red Cross drill will give us some additional data on the actual coverage.

Thanks

73

Randy KA0AZS


Re: Object PHG settings

Randy Allen
 

Bob,

RR.

The link that Fred posted (to a page I think you wrote) refreshed my memory and explained it perfectly.

73

Randy KA0AZS


Re: Object PHG settings

Randy Allen
 

Fred,

Thanks! That explains it all perfectly.

I think I knew that at one time but have not set up a PHG in so long I had forgotten it.

73
Randy KA0AZS


Re: Object PHG settings

James Ewen
 

Also this height is not altitude above sea level. It should match your height above average terrain (HAAT). Also if your coverage  is offset somewhat by local terrain, you might want to report a directional pattern even if your antenna pattern is omni. 

The PHG pattern drawn on the map should try to approximate the actual coverage area of your station even if the numbers don’t reflect the numerical values in your station. 

The intent is to provide those observing the output with an idea of the coverage to expect, not to brag about the exact specifications of the equipment in use. 

If your APRS client is drawing a PHG plot on the map, and you are within that area, you should be able to use the asset being described. 

Putting a huge circle on the map just because it looks more impressive doesn’t do anything to assist those who are wanting to make use of these equipment that the exaggerated circle describes. 

Fudge the numbers to make the information put in front of others as useful as possible. Those just seeing the raw numbers aren’t going to bother with trying to plot the coverage out in their heads. They will try it and see if it is reachable or not. 

James 
VE6SRV

On Tue, Nov 3, 2020 at 2:59 PM Robert Bruninga <bruninga@...> wrote:
There is only 1 digit for height.  So it uses powers of two..  Just pick the closest one.
Bob, WB4APR

On Tue, Nov 3, 2020 at 12:36 PM Fred Hillhouse <fmhillhouse@...> wrote:
Hi Randy,

Read this:
http://www.aprs.org/aprsdos-pix/phg.txt

I think you will find that your absolute heights, power, etc., may not be in the spec.  You need to pick the closest.

Fred N7FMH


-----Original Message-----
From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Randy Allen
Sent: Tuesday, November 03, 2020 12:19 PM
To: APRSISCE@groups.io
Subject: [APRSISCE] Object PHG settings

I'm setting up objects for a couple of local Winlink nodes.

Winlink inputs them to the IS stream, but I wanted them to be available
locally on RF.  Transmitting objects is simpler than attempting to set
up APRS transmitters at each location.

The objects are W6CDR-10 (Winlink RMS), W6CDR-4 (Digipeater, same radio
and antenna) and W8GCA-10.  I offset the position of W6CDR-4 digi a bit
to show as a separate station at my usual zoom (12.4 mi which shows my
whole county and parts of the surrounding counties.)

When I tried to set up the PHG for the objects, I am unable to get them
to save the settings I input (50W 330FT for CDR, 50W, 250Ft for GCA).
The only values I can get to save are the ones in the drop down boxes of
the PHG configuration screen.  So they are now set at 49W at 320FT for
CDR and 49W at 160Ft for GCA.

The block to enter the actual PHG value is greyed out. So I can't enter
PHG7500/ for CDR or PHG7400/ for GCA. (as calculated at
http://digined.pe1mew.nl/tools/phgcalculator.htm)

In this case the differences are insignificant for operations. I'm just
interested if I'm missing something.

73

Randy KA0AZS


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus












--
James
VE6SRV


Re: Object PHG settings

Robert Bruninga
 

There is only 1 digit for height.  So it uses powers of two..  Just pick the closest one.
Bob, WB4APR

On Tue, Nov 3, 2020 at 12:36 PM Fred Hillhouse <fmhillhouse@...> wrote:
Hi Randy,

Read this:
http://www.aprs.org/aprsdos-pix/phg.txt

I think you will find that your absolute heights, power, etc., may not be in the spec.  You need to pick the closest.

Fred N7FMH


-----Original Message-----
From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Randy Allen
Sent: Tuesday, November 03, 2020 12:19 PM
To: APRSISCE@groups.io
Subject: [APRSISCE] Object PHG settings

I'm setting up objects for a couple of local Winlink nodes.

Winlink inputs them to the IS stream, but I wanted them to be available
locally on RF.  Transmitting objects is simpler than attempting to set
up APRS transmitters at each location.

The objects are W6CDR-10 (Winlink RMS), W6CDR-4 (Digipeater, same radio
and antenna) and W8GCA-10.  I offset the position of W6CDR-4 digi a bit
to show as a separate station at my usual zoom (12.4 mi which shows my
whole county and parts of the surrounding counties.)

When I tried to set up the PHG for the objects, I am unable to get them
to save the settings I input (50W 330FT for CDR, 50W, 250Ft for GCA).
The only values I can get to save are the ones in the drop down boxes of
the PHG configuration screen.  So they are now set at 49W at 320FT for
CDR and 49W at 160Ft for GCA.

The block to enter the actual PHG value is greyed out. So I can't enter
PHG7500/ for CDR or PHG7400/ for GCA. (as calculated at
http://digined.pe1mew.nl/tools/phgcalculator.htm)

In this case the differences are insignificant for operations. I'm just
interested if I'm missing something.

73

Randy KA0AZS


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus













Re: Object PHG settings

Fred Hillhouse
 

Hi Randy,

Read this:
http://www.aprs.org/aprsdos-pix/phg.txt

I think you will find that your absolute heights, power, etc., may not be in the spec. You need to pick the closest.

Fred N7FMH

-----Original Message-----
From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Randy Allen
Sent: Tuesday, November 03, 2020 12:19 PM
To: APRSISCE@groups.io
Subject: [APRSISCE] Object PHG settings

I'm setting up objects for a couple of local Winlink nodes.

Winlink inputs them to the IS stream, but I wanted them to be available
locally on RF. Transmitting objects is simpler than attempting to set
up APRS transmitters at each location.

The objects are W6CDR-10 (Winlink RMS), W6CDR-4 (Digipeater, same radio
and antenna) and W8GCA-10. I offset the position of W6CDR-4 digi a bit
to show as a separate station at my usual zoom (12.4 mi which shows my
whole county and parts of the surrounding counties.)

When I tried to set up the PHG for the objects, I am unable to get them
to save the settings I input (50W 330FT for CDR, 50W, 250Ft for GCA).
The only values I can get to save are the ones in the drop down boxes of
the PHG configuration screen. So they are now set at 49W at 320FT for
CDR and 49W at 160Ft for GCA.

The block to enter the actual PHG value is greyed out. So I can't enter
PHG7500/ for CDR or PHG7400/ for GCA. (as calculated at
http://digined.pe1mew.nl/tools/phgcalculator.htm)

In this case the differences are insignificant for operations. I'm just
interested if I'm missing something.

73

Randy KA0AZS


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Object PHG settings

Randy Allen
 

I'm setting up objects for a couple of local Winlink nodes.

Winlink inputs them to the IS stream, but I wanted them to be available locally on RF.  Transmitting objects is simpler than attempting to set up APRS transmitters at each location.

The objects are W6CDR-10 (Winlink RMS), W6CDR-4 (Digipeater, same radio and antenna) and W8GCA-10.  I offset the position of W6CDR-4 digi a bit to show as a separate station at my usual zoom (12.4 mi which shows my whole county and parts of the surrounding counties.)

When I tried to set up the PHG for the objects, I am unable to get them to save the settings I input (50W 330FT for CDR, 50W, 250Ft for GCA).  The only values I can get to save are the ones in the drop down boxes of the PHG configuration screen.  So they are now set at 49W at 320FT for CDR and 49W at 160Ft for GCA.

The block to enter the actual PHG value is greyed out. So I can't enter PHG7500/ for CDR or PHG7400/ for GCA. (as calculated at http://digined.pe1mew.nl/tools/phgcalculator.htm)

In this case the differences are insignificant for operations. I'm just interested if I'm missing something.

73

Randy KA0AZS


--
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


Re: Shape files and weather info

Lynn Deffenbaugh
 

See also http://aprsisce.wikidot.com/doc:shapefiles

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


On 11/2/2020 4:47 PM, Fred Hillhouse wrote:

This will get you to the files you need.

http://wa8lmf.net/aprs/get_nws_shapefiles.htm

 

Grab the zip files, unzip and load files into APRSIS32.

 

Fred N7FMH

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Steve Black via groups.io
Sent: Monday, November 02, 2020 2:39 PM
To: APRSISCE@groups.io
Subject: [APRSISCE] Shape files and weather info

 

I have had APRSIS#@ running for years on my station computer. Well I go a new computer and reloaded many old programs back onto the new one. I can't remember how to add the shape files or where to get them from. I looked at the wiki but its kind of dated. Is there a step by step somewhere to walk me through it again? Thanks Steve kb1chu




Avast logo

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



Re: Shape files and weather info

Fred Hillhouse
 

This will get you to the files you need.

http://wa8lmf.net/aprs/get_nws_shapefiles.htm

 

Grab the zip files, unzip and load files into APRSIS32.

 

Fred N7FMH

 

 

From: APRSISCE@groups.io [mailto:APRSISCE@groups.io] On Behalf Of Steve Black via groups.io
Sent: Monday, November 02, 2020 2:39 PM
To: APRSISCE@groups.io
Subject: [APRSISCE] Shape files and weather info

 

I have had APRSIS#@ running for years on my station computer. Well I go a new computer and reloaded many old programs back onto the new one. I can't remember how to add the shape files or where to get them from. I looked at the wiki but its kind of dated. Is there a step by step somewhere to walk me through it again? Thanks Steve kb1chu




Avast logo

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



Re: Shape files and weather info

Glenn O'Connor
 

For the county warning areas boundaries, https://www.weather.gov/gis/CWABounds.

For the public forecast zones, https://www.weather.gov/gis/PublicZones.

For coastal marine, https://www.weather.gov/gis/MarineZones.

The above are .zip files. Extract to a folder that you can reference. For example, I, from time to time, still use UIView32, which
has a specific NWS folder. My shapefiles are kept there and when I point my APRSIS32 to that folder for its use, there they are.

No fuss, no muss.

73,
Glenn-KF0ED


Shape files and weather info

Steve Black
 

I have had APRSIS#@ running for years on my station computer. Well I go a new computer and reloaded many old programs back onto the new one. I can't remember how to add the shape files or where to get them from. I looked at the wiki but its kind of dated. Is there a step by step somewhere to walk me through it again? Thanks Steve kb1chu


Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Rob Giuliano
 

Idon't want to make this too confusing, but a single instance of Direwolf does not allow 2 separate ports.

However the Nexus DR-X implementation on the Raspberry Pi allows for separating the 2 audio channels (left & right) which allows 2 instances of Direwolf to run and become separate RF connections on APRSIS32.

I sure wish Direwolf offered the AGW and KISS over IP ports on a per port basis.
It is kind of like you DIGI, outside the port settings so applies to all.

Robert Giuliano
KB8RCO



On Wednesday, October 28, 2020, 10:08:43 AM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If multiple channels come over a single port connection as is typical with the AGW protocol, then yes, APRSIS32 only supports transmitting on the "first" channel.

If the sound card TNC supplies different ports for each channel, as I believe I saw in your DireWolf configuration, then a KISS over IP connection will be able to transmit on each individually configured port in APRSIS32.  At least, I think it should work that way!  I have never configured a multi-port DireWolf to test it.

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

On 10/27/2020 10:53 PM, Rob Giuliano via groups.io wrote:
Yep.
Logging the TX now on the KISS over IP port and AGW port.
Seeing both the TX and RX from a local DIGI.

I know that with 2 channels on an AGW port APRSIS32 can only TX on the first channel.
  With my Nexus setup, I can run 2 instances of the AGW app (Direwolf or UZ7OH) and have 2 ports.

I assume the same limitation exists for KISS over IP?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 6:44:02 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

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

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

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

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

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

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Re: Fix RF/TCP message gating (Dev: 2020/10/27 14:46)

Lynn Deffenbaugh
 

But unless you actually modified the code, it still probably doesn't handle acking properly.

The auto-reply was causing the looping, but the improper ack was/is causing excessive retries when a SATSRV request is received.

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

On 10/28/2020 11:43 AM, Bill Erhardt wrote:

Hi Lynn and to the gang,

 

I fixed the Loop in UISS SGATE addon and unchecked the AutoREPLY.  That was my fault on K7MT-6 my SGATE for Satellite APRS digi here in Montana.  I checked APRS dot FI and no loop since yesterday….

 

Bill K7MT

 

Sent from Mail for Windows 10

 


Re: Fix RF/TCP message gating (Dev: 2020/10/27 14:46)

Bill Erhardt
 

Hi Lynn and to the gang,

 

I fixed the Loop in UISS SGATE addon and unchecked the AutoREPLY.  That was my fault on K7MT-6 my SGATE for Satellite APRS digi here in Montana.  I checked APRS dot FI and no loop since yesterday….

 

Bill K7MT

 

Sent from Mail for Windows 10

 


Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Lynn Deffenbaugh
 

If multiple channels come over a single port connection as is typical with the AGW protocol, then yes, APRSIS32 only supports transmitting on the "first" channel.

If the sound card TNC supplies different ports for each channel, as I believe I saw in your DireWolf configuration, then a KISS over IP connection will be able to transmit on each individually configured port in APRSIS32.  At least, I think it should work that way!  I have never configured a multi-port DireWolf to test it.

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

On 10/27/2020 10:53 PM, Rob Giuliano via groups.io wrote:
Yep.
Logging the TX now on the KISS over IP port and AGW port.
Seeing both the TX and RX from a local DIGI.

I know that with 2 channels on an AGW port APRSIS32 can only TX on the first channel.
  With my Nexus setup, I can run 2 instances of the AGW app (Direwolf or UZ7OH) and have 2 ports.

I assume the same limitation exists for KISS over IP?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 6:44:02 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

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

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

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

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

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

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Rob Giuliano
 

Yep.
Logging the TX now on the KISS over IP port and AGW port.
Seeing both the TX and RX from a local DIGI.

I know that with 2 channels on an AGW port APRSIS32 can only TX on the first channel.
  With my Nexus setup, I can run 2 instances of the AGW app (Direwolf or UZ7OH) and have 2 ports.

I assume the same limitation exists for KISS over IP?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 6:44:02 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

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

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

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

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

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

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Lynn Deffenbaugh
 

If you still have the KISS over IP port configured, check for the latest development version (2020/10/27 18:38) and see if an enabled trace log shows Sent packets.  I'm not sure I put it in the right place, but hopefully I did!

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

On 10/27/2020 5:38 PM, Rob Giuliano via groups.io wrote:
Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

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

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

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

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Rob Giuliano
 

Yes, it transmits when the RF port is KISS over IP.
I have transmited on the KISS over IP port alone and heasr the packet back from a local DIGI.
I enabled all 3 ports to show that it was the only one that doesn't place the TX information in the log.
Normally, I never use both protocols to the same device. 

This started when I was having trouble with a KISS over IP port, but the logs didn't show I was transmitting.
That TNC was not "near by" the APRSIS32 instance, so I tried going back and forth between rooms.


Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 5:32:19 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

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

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

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

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Lynn Deffenbaugh
 

Possibly not by design, but probably by accident.  One of these days I need to revisit the port logging to make it more consistent.

In the meantime, sometimes the Transmit log can help, at least to determine if it is internal, -IS, RF, or both.  Not sure if you can tell from it which actual RF ports it was transmitted over.

Are you sure it actually transmitted or tried to transmit over the KISS over TCP/IP port?

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

On 10/27/2020 5:25 PM, Rob Giuliano via groups.io wrote:
So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

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

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO


Re: AGW (logs TX) vs. KISS over IP (TX not in log)

Rob Giuliano
 

So not logging the TX on teh IP port is by design?

Robert Giuliano
KB8RCO



On Tuesday, October 27, 2020, 4:56:37 PM EDT, Lynn Deffenbaugh <kj4erj@...> wrote:


Yes, Rob, every port type and transport has it's own logging style.  AGW is a TCP/IP protocol that encodes things differently than KISS.  And KISS over TCP/IP logs differently than KISS over a serial or Bluetooth port.

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

On 10/27/2020 4:19 PM, Rob Giuliano via groups.io wrote:
Another example showing the different between log using an AGW port:
WinMain:2020-10-27T20:01:59.988 Logging Enabled
Port(DW_AGW_Rt):2020-10-27T20:01:59.989 AGW:AX.25-rPort[0] AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio
Port(DW_AGW_Rt):2020-10-27T20:02:06.408 AGW:AX.25-rPort[0] N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI
Port(DW_AGW_Rt):2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]:<00 00 00 00>K<00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00>X<00 00 00 00 00 00 00 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
Port(DW_AGW_Rt):2020-10-27T20:02:15.309 AGW:AX.25-rPort[0] KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!
WinMain:2020-10-27T20:02:21.852 Logging Disabled
Port(DW_AGW_Rt):2020-10-27T20:02:27.595 AGW:AX.25-rPort[0] VE3PV>APAT51-1,VE3WRC*,CHLSEA*,WIDE2*:!4220.35N/08256.49W-210/000/A=000432Anytone 578

Compared to the KISS over IP port:
WinMain:2020-10-27T20:01:57.144 Logging Enabled
Port(DW_KISS_Rt):2020-10-27T20:01:59.989 KISS:AA8HS-1>APDW15,CHLSEA*,WIDE1*:!4141.60NS08338.40W&PHG2250Fill in Digipeater; 5 watts, 50 feet, Toledo, Ohio  (105)
Port(DW_KISS_Rt):2020-10-27T20:02:06.408 KISS:N8HKU-5>APDW15,CHLSEA*,WIDE1*,WIDE2-1:!4210.73NS08339.43W&PHG3170IGATE and Digipeater in Ypsilanti Township, MI  (77)
Port(DW_KISS_Rt):2020-10-27T20:02:15.309 KISS:KB8RCO>APWW11,CHLSEA*,WIDE2-1:@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!  (48)
WinMain:2020-10-27T20:02:20.506 Logging Disabled

All other RF ports log TX example from another RF port :
WinMain:2020-10-27T20:01:55.074 Logging Enabled
Port(TNC-X):2020-10-27T20:02:11.350 Sent[90]:<C0 00 82 A0 AE AE>bb<E0 96 84>p<A4 86 9E>`<AE 92 88 8A>d@e<03 F0>@200211h4209.34N/08346.27W-APRSIS32 XUbuntu 20.04  WINE 5.0!wY0!<C0>
WinMain:2020-10-27T20:02:19.249 Logging Disabled

TX on All 3 ports at once.  No audio into the TNC-X so DIGI'ed packet not received.
Top AGW port
   Logged TX at  2020-10-27T20:02:11.217 AGW:AX.25-xmit[124]
   Logged RX at 2020-10-27T20:02:15.309 AGW:AX.25-rPort[0]      timestamped @200211
Middle KISS IP
   Logged TX -> none
   Logged RX at  2020-10-27T20:02:15.309                                      timestamped @200211
Bottom RF serial port
   Logged TX at 2020-10-27T20:02:11.350 Sent[90]                         timestamped @200211
   Logged RX -> none    (no audio connection to a radio)


Robert Giuliano
KB8RCO

941 - 960 of 35881