Topics

A Question about Digipeating

KD7YZ Bob
 

1:Fm N4PWH-10 To APDW15 Via KD7YZ-15,WIDE1*,WIDE2-1 <UI pid=F0 Len=57 >[08:40:46]
!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY [UISS/AGWPE]

or
( and I'd asked about this "not supported stuff earlier]

WinMain:2020-01-04T13:40:46.127 Digipeating N4PWH-10 (WIDE1-1) via(WIDE1-1=WIDE1*)
WinMain:2020-01-04T13:40:46.127 Original(N4PWH-10>APDW15,WIDE1-1,WIDE2-1:!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY)
WinMain:2020-01-04T13:40:46.127 Transmit(N4PWH-10>APDW15,KD7YZ-15*,WIDE1*,WIDE2-1:!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY)
WinMain:2020-01-04T13:40:46.127 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

The question is, why don't I see the next station that heard me DigiPeat N4PWH ?
I see a thick brownish line connection N4PWH and "ME" on the APRSIS32 map everytime he Beacons that message.
However I never see a line from "ME" to someone else who received my repeat of PWH.

There are actually two or three guys out here in Rural Appalachia, over 100 miles, on ridgelines like me, who DO include my call in their Beacon path. I have seen the brown lines and seen AGWPE-UISS Digipeat them.

I realise that technically, AGWPE->UISS caught the decode through the Signalink off the D710 Data-Port. And that UISS did the DigiPeat. So maybe no seeing I make in APRSIS32 or the D710 would make any difference.

But I thought I'd ask anyway. Any D710 users feel free to email me at mycall from ARRL. DOT argghhhh matey.

that should be obfuscated enough to belay the spam-bots, hi hi

Thanks es HNY
--
KD7YZ Bob EM88LL

Rob Giuliano
 

This should explain it better:



Quoted from that page:
"APRSISCE/32 makes use of these internal commands (TC 0, TC 1) in order to assume control of the radio so it can send packets. In doing so, APRSISCE/32 sends a number of commands to the radio, including a command to set the source callsign (MYCALL). If the TM-D710 is left in control, and APRSISCE/32 is attempting to assert control, you can end up with some interesting effects. Note that APRSISCE/32 cannot provide digipeater support in this mode because the UNPROTO … VIA … command does not support used (*) path components."

Robert Giuliano
KB8RCO



On Saturday, January 4, 2020, 9:03:45 AM EST, KD7YZ Bob <kd7yz@...> wrote:


1:Fm N4PWH-10 To APDW15 Via KD7YZ-15,WIDE1*,WIDE2-1 <UI pid=F0 Len=57 >[08:40:46]
!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY  [UISS/AGWPE]

or
( and I'd asked about this "not supported stuff earlier]

WinMain:2020-01-04T13:40:46.127 Digipeating N4PWH-10 (WIDE1-1) via(WIDE1-1=WIDE1*)
WinMain:2020-01-04T13:40:46.127 Original(N4PWH-10>APDW15,WIDE1-1,WIDE2-1:!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY)
WinMain:2020-01-04T13:40:46.127 Transmit(N4PWH-10>APDW15,KD7YZ-15*,WIDE1*,WIDE2-1:!3819.85NI08258.30W#RasPi I-Gate/Digipeater in Grayson KY)
WinMain:2020-01-04T13:40:46.127 KWD710(APRS):DigiPeating Not Supported on KWD710(APRS) Protocol Ports

The question is, why don't I see the next station that heard me DigiPeat N4PWH ?
I see a thick brownish line connection N4PWH and "ME" on the APRSIS32 map everytime he Beacons that message.
However I never see a line from "ME" to someone else who received my repeat of PWH.

There are actually two or three guys out here in Rural Appalachia, over 100 miles, on ridgelines like me, who DO include my call in their Beacon path. I have seen the brown lines and seen AGWPE-UISS Digipeat them.

I realise that technically, AGWPE->UISS caught the decode through the Signalink off the D710 Data-Port. And that UISS did the DigiPeat. So maybe no seeing I make in APRSIS32 or the D710 would make any difference.

But I thought I'd ask anyway. Any D710 users feel free to email me at mycall from ARRL.  DOT argghhhh matey.

that should be obfuscated enough to belay the spam-bots, hi hi

Thanks es HNY
--
KD7YZ Bob EM88LL


KD7YZ Bob
 

You’d mentioned this before. However I see it differently now that I have used the Com port output of my D710.

And here is a quote from there too:

By having APRSISCE/32 monitoring the COM port, it is possible to decode and display all of the information received by the TM-D710.

I never saw a way to have APRSIS32 see the D710 port directly.
So I connected my SignaLInk to the D710 data port.
SignaLInk outputs as an Rx/Tx Soundcard.

I had to use AGWPE to make a Port of the Soundcard type. As you already knew..

And THEN I had APRSIS32 make a Soundcard Port reading the AGWPE PORT.

Is this what the wiki page is alluding to? Have APRSIS32 grab the D710GA COM port through an intermediary program?

Because those few paragraphs led me to believe I must create an APRSIS32 Kenwood D710 APRS port.

Am I getting reduced functionality?

First of all, I can never seeing myself driving along anywhere whilst using my D710 in any vehicle.
Not what my initial intended purpose was.


--
--
KD7YZ Bob EM88LL

Robert Bruninga
 

First of all, I can never seeing myself driving along anywhere whilst
using my D710 in any vehicle.
Not what my initial intended purpose was.
Just in case, the callsign of the mobile MUST be different from the callsign
of the receiving station because APRS ignores its own call.

Bob

KD7YZ Bob
 

OK.
I guess I should moderate the “likelihood “ of putting it in my Farm P/U truck.
I wouldn’t say “never “..
Just that (A) no one cares where I am driving.
And (B) there are usually two working dogs in the compartment behind the driver/passenger seats where I removed the former full seats. They, fwiw, weigh 175#

They’re both curious as well as suspicious of things that don’t belong. I have had driver seats chewed to the springs when they needed to go see some threat. Some accidentally left ham gear has been marked, drugged thru mud and otherwise told to go away.

All I want to do is try to report and or work thru PSAT,S ISS and USNAP1

Since ur here. Are there any UHF APRS types of birds up there I can set my D710GA CH-B to and have meaningful packets magically appear?

Thanks for answering


--
--
KD7YZ Bob EM88LL