Re: Chat log


James Ewen
 

Craig, 

I think I know what you are up against... In your log you show evidence of APRSISCE/32 sending a message at 13:53:16. I don't know how to read all the information in the APRSISCE/32 logs, but all the information you provided looks to be associated with that one transmission based on the timestamps.

Below you can see that packet captured in the APRS-IS logs I pulled from aprs.fi with a timestamp of 16:53:17. You can see retries as well.


2022-01-31 16:52:30 MST: KH6CP>APWW11,WIDE1-1,WIDE2-1,qAR,KH6MP-1::KE0JSB-7 :This is a test{RD}
2022-01-31 16:53:17 MST: KH6CP>APWW11,TCPIP*,qAC,T2CSNGRAD::KE0JSB-7 :Via IS{RE}
2022-01-31 16:53:49 MST: KH6CP>APWW11,TCPIP*,qAC,T2CSNGRAD::KE0JSB-7 :Via IS{RE}
2022-01-31 16:54:22 MST: KH6CP>APWW11,TCPIP*,qAC,T2CSNGRAD::KE0JSB-7 :Via IS{RE}
2022-01-31 16:55:26 MST: KH6CP>APWW11,TCPIP*,qAC,T2CSNGRAD::KE0JSB-7 :Via IS{RE}
2022-01-31 16:57:03 MST: KH6CP>APWW11,TCPIP*,qAC,T2CSNGRAD::KE0JSB-7 :Via IS{RE}

APRSISCE/32 expects that messages can be delivered 100% of the time.

If you enter three lines in your outgoing message chat box, APRSISCE/32 will send the first line until it times out. It will not send the second or third line until the first line gets an ack.

I don't have APRSISCE/32 with me now, but I believe there is a checkbox where you can override that behaviour. With the override in place, it will not need to wait for each line to get an ack if I am not mistaken.

Default behaviour is as you describe. You can try sending multiple lines of messages, but they will get jammed up in the outgoing queue until the each get an ack in sequence.

Have a look again and see if that was the source of your issue.

James
VE6SRV


On Tue, Feb 1, 2022 at 11:44 AM KH6CP Craig Paul <carcarx@...> wrote:
Thanks, James,

Yes, MP-1 is an iGate. iGates need to know who is in their RF neighborhood.
I can hear and decode (via Direwolf) what MP-1 and neighboring digis/iGates are doing.

Craig/KH6CP

On Tue, Feb 1, 2022 at 4:49 AM James Ewen <ve6srv@...> wrote:
Just a bit of clarification:

A digipeater doesn’t “register” a station. Digipeaters don’t pay any attention to the source callsign. Digipeaters keep track of packets they handle for the duration of the anti-dupe timer, but do not pay any attention to the content of the packet, including source call. The only thing digipeaters really care about in a packet is the next unused path element, and whether they support it or not. 

I haven’t looked at the logs, but your description tells me that an I-gate somewhere forwarded your message to the destination. Any susbsequent packets sent via an IS route should have been delivered. RFONLY packets may not have made the trip due to many issues related to RF path viability. 

You would need to monitor the RF network to be able to determine what is happening on the frequency, probably at a number of points to be able to try and determine what was causing the problem you are seeing. 



On Mon, Jan 31, 2022 at 17:36 KH6CP Craig Paul <carcarx@...> wrote:
Bug report:

Computer Windows 11 Intel i7, sound card modem Direwolf 1.7a, functioning WiFi connection.
1/31/22 APRSIS32 development version.

Yesterday I was testing with a station across low mountains here on Oahu. I sent KH6JUZ-3 a message and KH6MP-1 heard it (Diamond Head digi).
KH6JUZ-3 hadn't beaconed yet, so KH6MP-1 hadn't "registered" that station. I asked him to beacon and KH6MP-1 registered his station and forwarded the message.
The problem subsequently was I specified the next message to go by IS. That message and subsequent RF ones never made it out as far as I can tell.

So, I decided to recreate the environment with my wife's Kenwood TH-D74a next to the Kenwood TM-710GA.
I first sent from APRSIS32 with RF and the message was immediately received. I then switched to IS and sent the message. Nothing.
You can see (below:chat log) what I tried next. Even the next RF message never went out.

Yesterday I switched from APRSIS32 to YAAC and all RF messages went through.

Let me know of any further diagnostics/logs you might need.

Thanks!
Craig/KH6CP

---------- Forwarded message ---------
From: <carcarx@...>
Date: Mon, Jan 31, 2022 at 1:59 PM
Subject: Chat log
To: carcarx@... <carcarx@...>


WinMain:2022-01-31T23:53:16.930 Insert[1/2] at 84 (84) 476/512 Remaining (
13:53:16> Via IS)
WinMain:2022-01-31T23:53:16.931 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x008CFF (10)<Via IS{RE}>
WinMain:2022-01-31T23:53:16.931 Insert[1/2] at 84 (84) 476/512 Remaining (
13:53:16> Via IS)
WinMain:2022-01-31T23:53:16.932 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:53:16.932 Send IS-Only  
WinMain:2022-01-31T23:53:25.218 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x008CFF (10)<Via IS{RE}>
WinMain:2022-01-31T23:53:25.220 Insert[1/2] at 84 (84) 448/512 Remaining (
13:53:16> Via IS (*2-13:53:25))
WinMain:2022-01-31T23:53:41.378 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x008CFF (10)<Via IS{RE}>
WinMain:2022-01-31T23:53:41.379 Insert[1/2] at 84 (84) 448/512 Remaining (
13:53:16> Via IS (*3-13:53:41))
WinMain:2022-01-31T23:53:49.467 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x008CFF (10)<Via IS{RE}>
WinMain:2022-01-31T23:53:49.467 Insert[1/2] at 84 (84) 448/512 Remaining (
13:53:16> Via IS (*4-13:53:49))
WinMain:2022-01-31T23:54:18.725 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:54:18.725 Send IS-Only  
WinMain:2022-01-31T23:54:18.726 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:54:18.726 Send IS-Only  
WinMain:2022-01-31T23:54:18.924 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:54:18.924 Send  RF-Only
WinMain:2022-01-31T23:54:18.926 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:54:18.926 Send  RF-Only
WinMain:2022-01-31T23:54:21.421 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:54:21.421 Send   BOTH
WinMain:2022-01-31T23:54:21.422 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:54:21.422 Send   BOTH
WinMain:2022-01-31T23:54:21.748 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x008CFF (10)<Via IS{RE}>
WinMain:2022-01-31T23:54:21.749 Insert[1/2] at 84 (84) 448/512 Remaining (
13:53:16> Via IS (*5-13:54:21))
WinMain:2022-01-31T23:54:46.285 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x00D7FF FORCENEW (29)<Best setting transmission{RF}>
WinMain:2022-01-31T23:54:46.286 Insert[2/3] at 115 (115) 438/512 Remaining (
13:54:46> Best setting transmission)
WinMain:2022-01-31T23:55:26.283 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x008CFF (10)<Via IS{RE}>
WinMain:2022-01-31T23:55:26.284 Insert[1/3] at 84 (84) 448/512 Remaining (
13:53:16> Via IS (*6-13:55:26))
WinMain:2022-01-31T23:55:26.284 Insert[2/3] at 115 (115) 438/512 Remaining (
13:54:46> Best setting transmission)
WinMain:2022-01-31T23:57:02.765 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x9370DB (10)<Via IS{RE}>
WinMain:2022-01-31T23:57:02.767 Insert[1/3] at 84 (84) 448/512 Remaining (
13:53:16> Via IS (*6-13:57:02))
WinMain:2022-01-31T23:57:02.767 Insert[2/3] at 115 (115) 438/512 Remaining (
13:54:46> Best setting transmission)
WinMain:2022-01-31T23:57:10.792 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:57:10.792 Send   BOTH
WinMain:2022-01-31T23:57:10.793 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:57:10.793 Send   BOTH
WinMain:2022-01-31T23:57:13.757 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:57:13.757 Send IS-Only  
WinMain:2022-01-31T23:57:13.759 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:57:13.759 Send IS-Only  
WinMain:2022-01-31T23:57:14.723 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:57:14.724 Send  RF-Only
WinMain:2022-01-31T23:57:14.725 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:57:14.725 Send  RF-Only
WinMain:2022-01-31T23:57:21.463 AddToChat(KH6CP<->KE0JSB-7):Reply:0 Type:1 Color:0x00D7FF FORCENEW (14)<Another RF{RG}>
WinMain:2022-01-31T23:57:21.463 Insert[3/4] at 151 (151) 468/512 Remaining (
13:57:21> Another RF)
WinMain:2022-01-31T23:57:21.465 Checking/Fixing Send Button IS:Enabled RF:Enabled
WinMain:2022-01-31T23:57:21.465 Send  RF-Only 

--
James
VE6SRV

Join APRSISCE@groups.io to automatically receive all group messages.