Topics

DigiPeating and iGate oddities here

KD7YZ Bob
 

I think I asked somebody about this. However I kenno find the wee reply.

see this Digi-Log from my View Logs Digi:
----------------------------------------------------------------

WinMain:2019-11-21T10:27:53.988 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

WinMain:2019-11-21T11:49:58.465 Digipeating WR4CV-4 (WIDE2-1) via(WIDE2-1=WIDE2*)

WinMain:2019-11-21T11:49:58.465 Original(WR4CV-4>APOT30,KD4BNQ-3,KC8SDN-5*,WIDE2-1:!3754.99N/07857.30W#!3754.97N/07857.30W#APRS+ QRT2019/05/25 WGRN Mtn@4150ft ASL)

WinMain:2019-11-21T11:49:58.466 Transmit(WR4CV-4>APOT30,KD4BNQ-3,KC8SDN-5*,KD7YZ-15*,WIDE2*:!3754.99N/07857.30W#!3754.97N/07857.30W#APRS+ QRT2019/05/25 WGRN Mtn@4150ft ASL)

WinMain:2019-11-21T11:49:58.466 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

-----------------------------------------------------------------------

I have dozens of such from my overnight test run.

I am trying to nail down a "correct" setup so I can store it as such then revert to someting that works when I (again) mess things up s I attempt to learn.

so what's with the DigiPeat Error?

I appear to have guessed right on iGate:
-------------------------------------------------------------------------
WinMain:2019-11-20T23:42:32.958 RFtoIS:[AGWPE-TELNET ]IGated AC2KU-1>SYRT7S,RS0ISS*,qAR,KD7YZ-15:'f:-l K\]=

WinMain:2019-11-20T23:42:48.249 RFtoIS:[AGWPE-TELNET ]IGated AC2KU-1>SYRT7S,RS0ISS*,qAR,KD7YZ-15:'f:-l K\]=

WinMain:2019-11-20T23:43:13.207 RFtoIS:[AGWPE-TELNET ]IGated N3FCX-4>DJFT2Z,RS0ISS*,qAR,KD7YZ-15:'g.7l n/]=

WinMain:2019-11-20T23:43:20.390 RFtoIS:[AGWPE-TELNET ]IGated AC2KU-1>SYRT7S,RS0ISS*,qAR,KD7YZ-15:'f:-l K\]=

WinMain:2019-11-21T01:15:45.017 RFtoIS:[AGWPE-TELNET ]IGated KI4AQD-14>TPSU1Y,RS0ISS*,qAR,KD7YZ-15:`{CD"53u/]"6z}HI IN THE BIG BLUE LA-Z-BOY TRUCK=

WinMain:2019-11-21T01:16:01.646 RFtoIS:[AGWPE-TELNET ]IGated RS0ISS>CQ,qAR,KD7YZ-15:>ARISS - International Space Station

WinMain:2019-11-21T02:28:54.470 RFtoIS:[KWD710(Pkt)]IGated K8RRT>SXRT8Y,WIDE1-1,qAR,KD7YZ-15:`nZdl@O-/`"65}147.270MHz T123 +060 WVAR NET TUE 8:30 147270 PL 123_%

WinMain:2019-11-21T02:32:40.790 RFtoIS:[KWD710(Pkt)]IGated KJ4SNT>APMI04,KD4BNQ-3,KC8SDN-5*,WIDE2,qAR,KD7YZ-15::KJ4SNT :BITS.11111111,Telemetry
---------------------------------------------------------------------------

EXCEPT: " [KWD710(Pkt)]IGated" is not enabled.
So how did I iGate that one?

see the screenshots.

thanks!

--
73
Bob KD7YZ
AMSAT LM #901

Lynn Deffenbaugh
 

On 11/21/2019 7:21 AM, KD7YZ Bob wrote:
WinMain:2019-11-21T02:28:54.470 RFtoIS:[KWD710(Pkt)]IGated K8RRT>SXRT8Y,WIDE1-1,qAR,KD7YZ-15:`nZdl@O-/`"65}147.270MHz T123 +060 WVAR NET TUE 8:30 147270 PL 123_%

WinMain:2019-11-21T02:32:40.790 RFtoIS:[KWD710(Pkt)]IGated KJ4SNT>APMI04,KD4BNQ-3,KC8SDN-5*,WIDE2,qAR,KD7YZ-15::KJ4SNT :BITS.11111111,Telemetry
---------------------------------------------------------------------------


EXCEPT:  " [KWD710(Pkt)]IGated"  is not enabled.
So how did I iGate that one?

see the screenshots.
On the contrary, you DO have IGating enabled on your KWD710(Pkt) port.  From your screen shot, you have both RF to IS and IS to RF enabled.

I see on the second look that you have the port itself disabled, but if that were the case, we'd have never received a packet from it, would we?  Are you sure the port was not enabled when the log was generated, but that you disabled it after capturing the logs?

If you've been creating and/or destroying ports (especially deleting ports), it may be that APRSIS32 has gotten confused about an internal index.  To be sure, please restart APRSIS32 if you ever actually delete (not just disable) a port.

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

Lynn Deffenbaugh
 

KWD710(APRS) type ports do NOT support digipeating.  This is a restriction because in that protocol, paths cannot be set to include the used (*) bit which is required for digipeating.  Only KISS and AGW type ports support digipeating because in those, the AX.25 header is fully constructed and can include the required used bit.

So, the logs you're seeing from your KWD710(APRS) port show the digipeater logic detecting a packet that it CAN digipeat, so it fully constructs the new packet, but when it passes it off to the port, the port protocol driver (KWD710(APRS) in this case) rejects it because it is a digipeat packet.  Hence the burst of logs for each digipeat-able packet.

If you use an APRS-type port to your D710 or the AGW port to the other side of the radio, the digipeat function should work, provided of course that you receive a packet that your configuration thinks should be digipeated.

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

On 11/21/2019 7:21 AM, KD7YZ Bob wrote:
I think I asked somebody about this. However I kenno find the wee reply.

see this Digi-Log from my View Logs Digi:
----------------------------------------------------------------

WinMain:2019-11-21T10:27:53.988 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

WinMain:2019-11-21T11:49:58.465 Digipeating WR4CV-4 (WIDE2-1) via(WIDE2-1=WIDE2*)

WinMain:2019-11-21T11:49:58.465 Original(WR4CV-4>APOT30,KD4BNQ-3,KC8SDN-5*,WIDE2-1:!3754.99N/07857.30W#!3754.97N/07857.30W#APRS+ QRT2019/05/25 WGRN Mtn@4150ft ASL)

WinMain:2019-11-21T11:49:58.466 Transmit(WR4CV-4>APOT30,KD4BNQ-3,KC8SDN-5*,KD7YZ-15*,WIDE2*:!3754.99N/07857.30W#!3754.97N/07857.30W#APRS+ QRT2019/05/25 WGRN Mtn@4150ft ASL)

WinMain:2019-11-21T11:49:58.466 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

-----------------------------------------------------------------------

I have dozens of such from my overnight test run.

I am trying to nail down a "correct" setup so I can store it as such then revert to someting that works when I (again) mess things up s I attempt to learn.

so what's with the DigiPeat Error?

I appear to have guessed right on iGate:
-------------------------------------------------------------------------
WinMain:2019-11-20T23:42:32.958 RFtoIS:[AGWPE-TELNET ]IGated AC2KU-1>SYRT7S,RS0ISS*,qAR,KD7YZ-15:'f:-l K\]=

WinMain:2019-11-20T23:42:48.249 RFtoIS:[AGWPE-TELNET ]IGated AC2KU-1>SYRT7S,RS0ISS*,qAR,KD7YZ-15:'f:-l K\]=

WinMain:2019-11-20T23:43:13.207 RFtoIS:[AGWPE-TELNET ]IGated N3FCX-4>DJFT2Z,RS0ISS*,qAR,KD7YZ-15:'g.7l n/]=

WinMain:2019-11-20T23:43:20.390 RFtoIS:[AGWPE-TELNET ]IGated AC2KU-1>SYRT7S,RS0ISS*,qAR,KD7YZ-15:'f:-l K\]=

WinMain:2019-11-21T01:15:45.017 RFtoIS:[AGWPE-TELNET ]IGated KI4AQD-14>TPSU1Y,RS0ISS*,qAR,KD7YZ-15:`{CD"53u/]"6z}HI IN THE BIG BLUE LA-Z-BOY TRUCK=

WinMain:2019-11-21T01:16:01.646 RFtoIS:[AGWPE-TELNET ]IGated RS0ISS>CQ,qAR,KD7YZ-15:>ARISS - International Space Station

WinMain:2019-11-21T02:28:54.470 RFtoIS:[KWD710(Pkt)]IGated K8RRT>SXRT8Y,WIDE1-1,qAR,KD7YZ-15:`nZdl@O-/`"65}147.270MHz T123 +060 WVAR NET TUE 8:30 147270 PL 123_%

WinMain:2019-11-21T02:32:40.790 RFtoIS:[KWD710(Pkt)]IGated KJ4SNT>APMI04,KD4BNQ-3,KC8SDN-5*,WIDE2,qAR,KD7YZ-15::KJ4SNT :BITS.11111111,Telemetry
---------------------------------------------------------------------------


EXCEPT:  " [KWD710(Pkt)]IGated"  is not enabled.
So how did I iGate that one?

see the screenshots.

thanks!

--
73
Bob KD7YZ
AMSAT LM #901


KD7YZ Bob
 

wow Lynn, many thanks.

I must now disable email from the list and ONLY read it here on the web-interface.

what caught my attention was that a "Reply" about [APRSISCE] Disabling APRS-IS from Rob "kb8rco=yahoo.com@groups.io" appeared via Email. yet I never sw the original post. And that made me remember that sometimes I just never get replies ... or so the email interface tells me. And I have yet to ever see your email vial the email interface .. go figure

this made me remember to try the web interface. There are a couple of guys, such as Rob, who's emails always get thru on the list. Go Figure.


Anyway, I will try you suggestion regards an APRS type port .. though I don't quite understand what you mean ... the AGW port, I use, as AGWPE defines my SignaLink soundcard which is reading off "Data" port on D710 ...and the AGW-Port accepts its input nicely. However, I have not seen anything get DigiPeated from it ...hmmm, I always have it on 145.825 to read 2m Sats ... that wouldn't get digipeated anyway.