High Packet Loss Garbled RX very clear TX

KD2HYE
Posts: 9
Joined: Wed Jan 20, 2021 5:34 pm

High Packet Loss Garbled RX very clear TX

Post by KD2HYE »

I just received my OpenSpot3 yesterday shipping was super fast from Europe to the States.

Since setting up the OpenSpot I cant hear audio clearly. In the OpenSpot console it shows loss of >30% for each transmission received on REF001C. People report they hear me very clearly.

Seeing lots of invalid seqnum errors in the logs.

My connection is stable at 1gbps with a maximum throughput of 3.5gbps at my edge router and I have made sure to open all the necessary UDP ports to the openspot.

Below is an example log from DMR connector but its the same with d-star. I ahve tried with a LTE router Wi-Fi hotspot and get the same behavior so have ruled out my home network.

Code: Select all

12:39:50 httpsrv[0]: websocket opened with token 641e2294
12:39:50 httpsrv[0]: websocket opened with token 641e2294
12:39:50 homebrew: invalid seqnum received, got 29 expected 27, missing 2 packets
12:39:51 modem-djq: emptied, closing
12:39:52 homebrew: ping sent
12:39:52 homebrew: pong received
12:39:54 nvmm: net check ok (11 ms)
12:39:54 dmrcalltracker[0]: call ended (timeout), dur 18.9s ber 0.0% loss 37.6% rssi 0
12:39:54 dstar4dmrcon: call end, timeout: 1
12:39:54 modem-djq: emptied, closing
12:39:57 batt: stat: done/100mA, 100% (new) (4084mV 30C)
12:39:57 dmrcalltracker[0]: grp voice call started, dst: 93 src: 3160840 id: 72b2988c7e28c8fe
12:39:58 homebrew: ping sent
12:39:58 dstar4dmrcon: new call, cid 72b2988c7e28c8fe
12:39:58 homebrew: pong received
12:39:58 dstar4dmrcon: call start, using src callsign KC1MMH for this call
12:39:59 homebrew: received seqnum diff 6
12:39:59 homebrew: received seqnum diff 7
12:40:00 homebrew: invalid seqnum received, got 50 expected 49, missing 1 packets
12:40:03 modem-djq: emptied, closing
12:40:03 dmrcalltracker[0]: call ended, dur 5.7s ber 0.0% loss 1.2% rssi 0
12:40:04 dstar4dmrcon: call end, timeout: 0
12:40:04 dmrcalltracker[0]: grp voice call started, dst: 93 src: 3160840 id: f894fef4ee80389e
12:40:04 homebrew: ping sent
12:40:04 homebrew: invalid seqnum received, got 4 expected 2, missing 2 packets
12:40:04 dstar4dmrcon: new call, cid f894fef4ee80389e
12:40:04 homebrew: pong received
12:40:04 dstar4dmrcon: call start, using src callsign KC1MMH for this call
12:40:05 homebrew: invalid seqnum received, got 27 expected 26, missing 1 packets
12:40:05 homebrew: invalid seqnum received, got 30 expected 29, missing 1 packets
12:40:05 homebrew: invalid seqnum received, got 37 expected 36, missing 1 packets
12:40:05 homebrew: invalid seqnum received, got 41 expected 40, missing 1 packets
12:40:05 homebrew: invalid seqnum received, got 49 expected 47, missing 2 packets
12:40:05 homebrew: invalid seqnum received, got 51 expected 50, missing 1 packets
12:40:06 homebrew: invalid seqnum received, got 56 expected 55, missing 1 packets
12:40:06 homebrew: invalid seqnum received, got 59 expected 58, missing 1 packets
12:40:09 dmrcalltracker[0]: call ended, dur 5.1s ber 0.0% loss 11.8% rssi 0
12:40:09 dstar4dmrcon: call end, timeout: 0
12:40:10 batt: stat: done/100mAhomebrew: ping sent
12:40:10 homebrew: pong received
12:40:10 modem-djq: emptied, closing
12:40:13 , 100% (new) (4092mV 30C)
12:40:16 homebrew: ping sent
12:40:16 homebrew: pong received
12:40:17 dmrcalltracker[0]: grp voice call started, dst: 93 src: 3116750 id: 80b0f6b8d47abae2
12:40:17 dstar4dmrcon: new call, cid 80b0f6b8d47abae2
12:40:17 homebrew: invalid seqnum received, got 10 expected 9, missing 1 packets
12:40:18 dstar4dmrcon: call start, using src callsign KD2MZM for this call
12:40:18 dmrcalltracker-emb [0]: decoded talker alias: KD2MZM
12:40:18 dstar4dmrcon: msg to modem change to KD2MZM
12:40:19 homebrew: invalid seqnum received, got 38 expected 37, missing 1 packets
12:40:19 homebrew: invalid seqnum received, got 41 expected 39, missing 2 packets
12:40:19 homebrew: invalid seqnum received, got 43 expected 42, missing 1 packets
12:40:19 homebrew: invalid seqnum received, got 46 expected 45, missing 1 packets
12:40:19 homebrew: invalid seqnum received, got 48 expected 47, missing 1 packets
12:40:19 homebrew: invalid seqnum received, got 50 expected 49, missing 1 packets
12:40:20 homebrew: invalid seqnum received, got 53 expected 51, missing 2 packets
12:40:20 homebrew: invalid seqnum received, got 57 expected 55, missing 2 packets
12:40:20 homebrew: invalid seqnum received, got 62 expected 60, missing 2 packets
12:40:20 homebrew: invalid seqnum received, got 64 expected 63, missing 1 packets
12:40:21 homebrew: invalid seqnum received, got 69 expected 68, missing 1 packets
12:40:21 homebrew: invalid seqnum received, got 75 expected 74, missing 1 packets
12:40:21 homebrew: invalid seqnum received, got 80 expected 79, missing 1 packets
12:40:22 homebrew: invalid seqnum received, got 88 expected 86, missing 2 packets
12:40:22 homebrew: invalid seqnum received, got 90 expected 89, missing 1 packets
12:40:22 homebrew: ping sent
12:40:22 homebrew: pong received
12:40:22 homebrew: invalid seqnum received, got 92 expected 91, missing 1 packets
12:40:22 homebrew: invalid seqnum received, got 96 expected 95, missing 1 packets
12:40:23 homebrew: invalid seqnum received, got 106 expected 104, missing 2 packets
12:40:23 homebrew: invalid seqnum received, got 111 expected 110, missing 1 packets
12:40:23 homebrew: invalid seqnum received, got 113 expected 112, missing 1 packets
12:40:23 homebrew: invalid seqnum received, got 115 expected 114, missing 1 packets
12:40:24 batt: stat: done/100mA, 100% (new) (4078mV 30C)
12:40:24 homebrew: invalid seqnum received, got 120 expected 119, missing 1 packets
12:40:24 homebrew: invalid seqnum received, got 128 expected 126, missing 2 packets
12:40:24 homebrew: invalid seqnum received, got 133 expected 132, missing 1 packets
12:40:25 homebrew: invalid seqnum received, got 137 expected 135, missing 2 packets
12:40:25 homebrew: invalid seqnum received, got 139 expected 138, missing 1 packets
12:40:25 homebrew: invalid seqnum received, got 145 expected 144, missing 1 packets
12:40:25 homebrew: invalid seqnum received, got 148 expected 146, missing 2 packets
12:40:26 homebrew: invalid seqnum received, got 154 expected 153, missing 1 packets
12:40:26 homebrew: invalid seqnum received, got 157 expected 156, missing 1 packets
12:40:26 homebrew: invalid seqnum received, got 161 expected 160, missing 1 packets
12:40:26 homebrew: invalid seqnum received, got 163 expected 162, missing 1 packets
12:40:26 homebrew: invalid seqnum received, got 166 expected 164, missing 2 packets
12:40:27 homebrew: invalid seqnum received, got 170 expected 169, missing 1 packets
12:40:27 batt: stat: done/100mA, 100% (new) (4092mV 30C)
12:40:27 homebrew: invalid seqnum received, got 181 expected 177, missing 4 packets
12:40:28 homebrew: invalid seqnum received, got 184 expected 183, missing 1 packets
12:40:28 homebrew: invalid seqnum received, got 186 expected 185, missing 1 packets
12:40:28 homebrew: ping sent
12:40:30 modem-djq: emptied, closing
12:40:31 dmrcalltracker[0]: call ended (timeout), dur 14.1s ber 0.1% loss 26.1% rssi 0
12:40:31 dstar4dmrcon: call end, timeout: 1
12:40:31 modem-djq: emptied, closing
12:40:34 homebrew: ping sent
12:40:34 homebrew: pong received
12:40:34 dmrcalltracker[0]: grp voice call started, dst: 93 src: 3160840 id: d076644c8c960244
12:40:35 dstar4dmrcon: new call, cid d076644c8c960244
12:40:36 homebrew: received seqnum diff 15
12:40:36 homebrew: invalid seqnum received, got 22 expected 19, missing 3 packets
12:40:37 homebrew: received seqnum diff 9
12:40:37 batt: stat: done/100mA, 100% (new) (4094mV 30C)
12:40:37 homebrew: invalid seqnum received, got 42 expected 41, missing 1 packets
12:40:37 dstar4dmrcon: call start, using src callsign KC1MMH for this call
12:40:37 dmrcalltracker-emb [0]: decoded talker alias: KD2MZM
12:40:37 dstar4dmrcon: msg to modem change to KD2MZM
12:40:38 homebrew: received seqnum diff 7
12:40:38 homebrew: invalid seqnum received, got 63 expected 60, missing 3 packets
12:40:38 homebrew: invalid seqnum received, got 70 expected 69, missing 1 packets
12:40:39 homebrew: invalid seqnum received, got 75 expected 74, missing 1 packets
12:40:39 homebrew: invalid seqnum received, got 79 expected 77, missing 2 packets
12:40:39 homebrew: received seqnum diff 8
12:40:40 homebrew: ping sent
12:40:41 homebrew: received seqnum diff 6
12:40:41 homebrew: invalid seqnum received, got 100 expected 99, missing 1 packets
12:40:41 modem-djq: emptied, closing
12:40:42 net-seqbuf: inserting seq:128 at:0 0/114
12:40:42 net-seqbuf: inserted invalid seq:128 cnt:2 at:0 1/114 0/128
12:40:42 net-seqbuf: seqnum 129 diff too big (max: 9)
12:40:42 homebrew: received seqnum diff 16
12:40:42 homebrew: received seqnum diff 241
12:40:42 homebrew: received seqnum diff 15
12:40:43 modem-djq: emptied, closing
12:40:45 dmrcalltracker[0]: call ended (timeout), dur 10.9s ber 0.0% loss 14.6% rssi 0
12:40:46 dstar4dmrcon: call end, timeout: 1
12:40:46 modem-djq: emptied, closing
12:40:47 batt: stat: done/100mA, 100% (new) (4092mV 30C)
12:40:47 homebrew: ping sent
12:40:53 homebrew: ping sent
12:40:53 homebrew: pong received
12:40:54 nvmm: net check
12:40:57 nvmm: net check ok (10 ms)
12:40:57 batt: stat: done/100mA, 100% (new) (4098mV 30C)
12:40:59 homebrew: ping sent
12:40:59 homebrew: pong received
12:41:05 homebrew: ping sent
12:41:05 homebrew: pong received
12:41:07 batt: stat: done/100mA, 100% (new) (4090mV 30C)
12:41:08 dmrcalltracker[0]: grp voice call started, dst: 93 src: 3116750 id: 02025ef458e88680
12:41:08 dstar4dmrcon: new call, cid 02025ef458e88680
12:41:09 dstar4dmrcon: call start, using src callsign KD2MZM for this call
12:41:09 homebrew: invalid seqnum received, got 22 expected 21, missing 1 packets
12:41:10 homebrew: invalid seqnum received, got 24 expected 23, missing 1 packets
12:41:10 homebrew: invalid seqnum received, got 27 expected 26, missing 1 packets
12:41:10 homebrew: invalid seqnum received, got 31 expected 30, missing 1 packets
12:41:10 homebrew: invalid seqnum received, got 38 expected 37, missing 1 packets
12:41:11 homebrew: invalid seqnum received, got 40 expected 39, missing 1 packets
12:41:11 homebrew: invalid seqnum received, got 42 expected 41, missing 1 packets
12:41:11 homebrew: invalid seqnum received, got 45 expected 43, missing 2 packets
12:41:11 homebrew: invalid seqnum received, got 51 expected 47, missing 4 packets
12:41:11 homebrew: ping sent
12:41:11 homebrew: pong received
12:41:11 homebrew: invalid seqnum received, got 54 expected 53, missing 1 packets
12:41:12 homebrew: invalid seqnum received, got 63 expected 61, missing 2 packets
12:41:12 homebrew: invalid seqnum received, got 66 expected 64, missing 2 packets
12:41:12 homebrew: invalid seqnum received, got 69 expected 68, missing 1 packets
12:41:12 homebrew: invalid seqnum received, got 71 expected 70, missing 1 packets
12:41:13 homebrew: invalid seqnum received, got 75 expected 73, missing 2 packets
12:41:13 homebrew: invalid seqnum received, got 83 expected 82, missing 1 packets
12:41:13 homebrew: invalid seqnum received, got 85 expected 84, missing 1 packets
12:41:14 homebrew: invalid seqnum received, got 89 expected 88, missing 1 packets
12:41:14 homebrew: invalid seqnum received, got 92 expected 91, missing 1 packets
12:41:14 dmrcalltracker-emb [0]: decoded talker alias: KD2MZM
12:41:14 dstar4dmrcon: msg to modem change to KD2MZM
12:41:14 homebrew: invalid seqnum received, got 100 expected 98, missing 2 packets
12:41:14 homebrew: invalid seqnum received, got 105 expected 103, missing 2 packets
12:41:15 homebrew: invalid seqnum received, got 109 expected 106, missing 3 packets
12:41:15 homebrew: invalid seqnum received, got 117 expected 116, missing 1 packets
12:41:15 homebrew: invalid seqnum received, got 120 expected 119, missing 1 packets
12:41:16 homebrew: invalid seqnum received, got 129 expected 128, missing 1 packets
12:41:17 modem-djq: emptied, closing
12:41:17 batt: stat: done/100mA, 100% (new) (4092mV 30C)
12:41:18 homebrew: ping sent
12:41:18 homebrew: pong received
12:41:20 dmrcalltracker[0]: call ended (timeout), dur 11.4s ber 0.0% loss 26.9% rssi 0
12:41:20 dstar4dmrcon: call end, timeout: 1
12:41:21 modem-djq: emptied, closing
12:41:24 homebrew: ping sent
12:41:27 batt: stat: done/100mA, 100% (new) (4090mV 30C)
12:41:28 net-seqbuf: inserting seq:14 at:0 0/0
12:41:28 net-seqbuf: inserted invalid seq:14 cnt:2 at:0 1/0 0/14
12:41:28 net-seqbuf: seqnum 15 diff too big (max: 9)
12:41:28 homebrew: call started based on incoming packet, dst 93 src 3160840 type prv
12:41:28 dmrcalltracker[0]: prv voice call started, dst: 93 src: 3160840 id: a8de26ac3c7252bc
12:41:28 dstar4dmrcon: new call, cid a8de26ac3c7252bc
12:41:28 homebrew: received seqnum diff 241
12:41:28 dmrcalltracker[0]: got new lc, ending call
12:41:28   old lc: dst 93 src 3160840 fid 0 flco 3 so 0
12:41:28   new lc: dst 93 src 3160840 fid 0 flco 0 so 0
12:41:28 dmrcalltracker[0]: call ended, dur 0.0s ber 0.0% loss 0.0% rssi 0
12:41:28 dmrcalltracker[0]: grp voice call started, dst: 93 src: 3160840 id: d6cc5ab42096ba00
12:41:28 homebrew: received seqnum diff 15
12:41:28 dstar4dmrcon: new call, cid d6cc5ab42096ba00
12:41:28 dstar4dmrcon: call start, using src callsign KC1MMH for this call
12:41:29 dstar4dmrcon: call end, timeout: 0
12:41:29 homebrew: invalid seqnum received, got 18 expected 16, missing 2 packets
12:41:29 modem-djq: emptied, closing
12:41:30 homebrew: invalid seqnum received, got 27 expected 25, missing 2 packets
12:41:30 homebrew: ping sent
12:41:30 homebrew: pong received
12:41:30 homebrew: invalid seqnum received, got 34 expected 31, missing 3 packets
12:41:30 dstar4dmrcon: call start, using src callsign KC1MMH for this call
12:41:32 homebrew: invalid seqnum received, got 40 expected 39, missing 1 packets
12:41:35 modem-djq: emptied, closing
12:41:35 homebrew: invalid seqnum received, got 47 expected 44, missing 3 packets
12:41:35 homebrew: received seqnum diff 7
12:41:35 homebrew: invalid seqnum received, got 64 expected 63, missing 1 packets
12:41:35 modem-djq: emptied, closing
12:41:35 homebrew: invalid seqnum received, got 82 expected 81, missing 1 packets
12:41:35 homebrew: invalid seqnum received, got 89 expected 85, missing 4 packets
12:41:35 modem-djq: emptied, closing
12:41:36 homebrew: invalid seqnum received, got 96 expected 93, missing 3 packets
12:41:36 homebrew: ping sent
12:41:36 homebrew: pong received
12:41:37 homebrew: invalid seqnum received, got 110 expected 107, missing 3 packets
12:41:37 batt: stat: done/100mA, 100% (new) (4090mV 30C)
12:41:37 homebrew: invalid seqnum received, got 112 expected 111, missing 1 packets
12:41:38 homebrew: invalid seqnum received, got 117 expected 115, missing 2 packets
12:41:38 homebrew: received seqnum diff 6
12:41:39 modem-djq: emptied, closing
12:41:39 homebrew: invalid seqnum received, got 134 expected 131, missing 3 packets
12:41:39 homebrew: invalid seqnum received, got 137 expected 136, missing 1 packets
12:41:41 homebrew: invalid seqnum received, got 161 expected 160, missing 1 packets
12:41:41 homebrew: invalid seqnum received, got 169 expected 167, missing 2 packets
12:41:42 modem-djq: emptied, closing
12:41:42 homebrew: invalid seqnum received, got 176 expected 175, missing 1 packets
12:41:42 homebrew: ping sent
12:41:42 homebrew: pong received
12:41:44 modem-djq: emptied, closing
So far my troubleshooting steps have been:
  • Try different WAN connection
  • Try different network router
  • Try factory reset device and re-setup from scratch
  • Upgraded to beta firmware

Not sure what else to try... my DVAP and RaspPi setup work flawlessly.... but don't have all the features of the OpenSpot.

Many thanks in advance... super excited to get this thing working.

Jim.
N1IG
Posts: 179
Joined: Thu Apr 09, 2020 7:50 pm

Re: High Packet Loss Garbled RX very clear TX

Post by N1IG »

I see a lot of loss on 001C.

I will be on 062C in case you want to try a different reflector.
KD2HYE
Posts: 9
Joined: Wed Jan 20, 2021 5:34 pm

Re: High Packet Loss Garbled RX very clear TX

Post by KD2HYE »

Thank you to N1IG I spoke with him on 062C and had the same effects. Example log output from that convo below.

At this point I have tried mobile hotspot, hardware reset, different radio and the other troubleshooting steps above and am beginning to suspect a hardware issue. Will e-mail support and respond to this thread again once I am able to ascertain what is going wrong.

Code: Select all

18:04:31 httpsrv[0]: websocket opened with token 1a881a44
18:04:31 httpsrv[0]: websocket opened with token 1a881a44
18:04:31 ref: invalid seqnum received, got 18 expected 17, missing 1 packets
18:04:31 ref: invalid seqnum received, got 2 expected 21, missing 2 packets
18:04:31 ref: invalid seqnum received, got 14 expected 13, missing 1 packets
18:04:32 ref: invalid seqnum received, got 3 expected 2, missing 1 packets
18:04:32 ref: invalid seqnum received, got 6 expected 5, missing 1 packets
18:04:32 dstarcalltracker-sd: got msg AnAnynyo  4 o  9co
18:04:32 ref: got ping, replying
18:04:32 ref: invalid seqnum received, got 14 expected 13, missing 1 packets
18:04:32 ref: invalid seqnum received, got 18 expected 17, missing 1 packets
18:04:33 dstarcalltracker-sd: got msg Anthony D74 FM19co
18:04:33 ref: got ping, replying
18:04:34 ref: got ping, replying
18:04:34 ref: got last frame
18:04:34 dstarcalltracker: call ended, dur 66.7s ber 0.0% loss 16.4% rssi 0
18:04:35 ref: call ended
18:04:35 modem-djq: emptied, closing
18:04:35 ref: got ping, replying
18:04:36 ref: got ping, replying
18:04:37 ref: got ping, replying
18:04:37 batt: stat: done/100mA, 100% (new) (4092mV 31C)
18:04:38 ref: got ping, replying
18:04:38 dstarcalltracker: got header
18:04:38 dstarcalltracker: voice call started, dst: CQCQCQ   src: KD2HYE  /     from modem: 1 id: c8605aaa28045ec4
18:04:38 nvmm-csd: ignoring special callsign CQCQCQ  
18:04:38 ref: call started
18:04:38 dstarcalltracker-sd: got msg Jim - New York City
18:04:39 ref: got ping, replying
18:04:40 ref: got ccs ping
18:04:40 ccs: sending pong
18:04:40 ref: got ping, replying
18:04:41 ref: got ping, replying
18:04:42 ref: got ping, replying
18:04:43 ref: got ping, replying
18:04:44 ref: got ping, replying
18:04:45 ref: got ping, replying
18:04:46 ref: got ping, replying
18:04:47 ref: got ping, replying
18:04:47 batt: stat: done/100mA, 100% (new) (4092mV 31C)
18:04:48 ref: got ping, replying
18:04:49 ref: got ping, replying
18:04:50 ref: got ping, replying
18:04:51 ref: got ccs ping
18:04:51 ccs: sending pong
18:04:51 ref: got ping, replying
18:04:52 ref: got ping, replying
18:04:53 ref: got ping, replying
18:04:54 ref: got ping, replying
18:04:55 ref: got ping, replying
18:04:56 ref: got ping, replying
18:04:57 ref: got ping, replying
18:04:57 batt: stat: done/100mA, 100% (new) (4092mV 31C)
18:04:58 ref: got ping, replying
18:04:59 ref: got ping, replying
18:05:00 ref: got ping, replying
18:05:01 ref: got ping, replying
18:05:02 ref: got ccs ping
18:05:02 ccs: sending pong
18:05:02 ref: got ping, replying
18:05:03 dstarcalltracker: got end sync
18:05:03 dstarcalltracker: call ended, dur 24.7s ber 0.0% loss 0.0% rssi -47
18:05:03 ref: call stopped
18:05:03 ref: got ping, replying
18:05:03 dstarpacket: sending message to modem: REF062 C/openSPOT3
18:05:03 modem-djq: emptied, closing
18:05:04 ref: got ping, replying
18:05:05 ref: got ping, replying
18:05:06 ref: got ping, replying
18:05:07 ref: got ping, replying
18:05:07 batt: stat: done/100mA, 100% (new) (4092mV 31C)
18:05:08 ref: got ping, replying
18:05:09 ref: got ping, replying
18:05:10 ref: got ping, replying
18:05:11 ref: got ping, replying
18:05:12 ref: got ping, replying
18:05:13 ref: got ccs ping
18:05:13 ccs: sending pong
18:05:13 ref: got ping, replying
18:05:14 ref: got ping, replying
18:05:15 ref: got ping, replying
18:05:16 ref: got ping, replying
18:05:17 ref: got ping, replying
18:05:17 batt: stat: done/100mA, 100% (new) (4080mV 31C)
18:05:18 ref: got ping, replying
18:05:19 ref: got ping, replying
18:05:20 ref: got ping, replying
18:05:21 ref: got ping, replying
18:05:22 ref: got ping, replying
18:05:23 ref: got ping, replying
18:05:24 ref: got ccs ping
18:05:24 ccs: sending pong
18:05:24 ref: got ping, replying
18:05:25 nvmm: net check
18:05:25 ref: got ping, replying
18:05:25 nvmm: net check ok (13 ms)
18:05:26 ref: got ping, replying
18:05:27 ref: got ping, replying
18:05:27 batt: stat: done/100mA, 100% (new) (4102mV 31C)
18:05:28 ref: got ping, replying
18:05:29 ref: got ping, replying
18:05:30 ref: got ping, replying
18:05:33 dstarcalltracker: got decoded header data from net
18:05:33 dstarcalltracker: voice call started, dst:        I src: AC3FI   /     from modem: 0 id: 50e4504264aebae8
18:05:33 nvmm-csd: ignoring special callsign        I
18:05:33 ref: new call started
18:05:33 ref: invalid seqnum received, got 4 expected 2, missing 2 packets
18:05:33 ref: invalid seqnum received, got 7 expected 6, missing 1 packets
18:05:33 ref: invalid seqnum received, got 13 expected 9, missing 4 packets
18:05:33 ref: invalid seqnum received, got 19 expected 18, missing 1 packets
18:05:33 ref: invalid seqnum received, got 1 expected 21, missing 1 packets
18:05:33 ref: invalid seqnum received, got 5 expected 4, missing 1 packets
18:05:33 ref: invalid seqnum received, got 8 expected 7, missing 1 packets
18:05:33 ref: invalid seqnum received, got 14 expected 13, missing 1 packets
18:05:33 ref: invalid seqnum received, got 17 expected 16, missing 1 packets
18:05:34 ref: got last frame
18:05:34 dstarcalltracker: call ended, dur 0.8s ber 0.0% loss 31.7% rssi 0
18:05:34 ref: call ended
18:05:34 ref: got ping, replying
18:05:34 modem-djq: emptied, closing
18:05:36 ref: got ping, replying
18:05:36 ref: got ping, replying
18:05:37 ref: got ping, replying
18:05:37 batt: stat: done/100mA, 100% (new) (4092mV 31C)
18:05:42 ref: got ping, replying
18:05:43 ref: got ping, replying
18:05:45 ref: got ping, replying
18:05:46 ref: got ccs ping
18:05:46 ccs: sending pong
18:05:46 ref: got ping, replying
18:05:47 ref: got ping, replying
18:05:47 batt: stat: done/100mA, 100% (new) (4090mV 31C)
18:05:48 ref: got ping, replying
18:05:52 ref: got ping, replying
18:05:53 ref: got ping, replying
18:05:54 ref: got ping, replying
18:05:55 ref: got ping, replying
18:05:56 ref: got ping, replying
18:05:57 ref: got ccs ping
18:05:57 ccs: sending pong
18:05:57 ref: got ping, replying
18:05:57 batt: stat: done/100mA, 100% (new) (4090mV 31C)
18:05:58 ref: got ping, replying
18:05:59 ref: got ping, replying
18:06:00 ref: got ping, replying
18:06:01 ref: got ping, replying
18:06:02 ref: got ping, replying
18:06:03 ref: got ping, replying
18:06:04 ref: got ping, replying
18:06:05 ref: got ping, replying
18:06:06 ref: got ping, replying
18:06:07 ref: got ping, replying
18:06:07 batt: stat: done/100mA, 100% (new) (4102mV 31C)
18:06:08 ref: got ccs ping
18:06:08 ccs: sending pong
18:06:08 ref: got ping, replying
18:06:09 ref: got ping, replying
18:06:10 ref: got ping, replying
18:06:11 ref: got ping, replying
18:06:12 ref: got ping, replying
18:06:13 ref: got ping, replying
18:06:14 ref: got ping, replying
18:06:15 ref: got ping, replying
18:06:16 ref: got ping, replying
18:06:17 ref: got ping, replying
18:06:17 batt: stat: done/100mA, 100% (new) (4088mV 31C)
18:06:18 ref: got ping, replying
18:06:19 ref: got ccs ping
18:06:19 ccs: sending pong
18:06:19 ref: got ping, replying
18:06:20 ref: got ping, replying
18:06:21 ref: got ping, replying
18:06:22 ref: got ping, replying
18:06:23 ref: got ping, replying
18:06:24 ref: got ping, replying
18:06:25 nvmm: net check
18:06:25 ref: got ping, replying
18:06:25 nvmm: net check ok (15 ms)
18:06:26 ref: got ping, replying
18:06:27 ref: got ping, replying
18:06:27 batt: stat: done/100mA, 100% (new) (4082mV 31C)
18:06:28 ref: got ping, replying
18:06:29 ref: got ping, replying
18:06:30 ref: got ccs ping
18:06:30 ccs: sending pong
18:06:30 ref: got ping, replying
18:06:31 ref: got ping, replying
18:06:32 ref: got ping, replying
18:06:33 ref: got ping, replying
18:06:34 ref: got ping, replying
18:06:35 ref: got ping, replying
N1IG
Posts: 179
Joined: Thu Apr 09, 2020 7:50 pm

Re: High Packet Loss Garbled RX very clear TX

Post by N1IG »

The only other thing I can think of is to check the wifi settings, as suggested by an admin:

- Make sure the Wi-Fi bandwith is set to max. 20Mhz in the Wi-Fi router (see explanation here:

https://superuser.com/questions/542191/ ... less-speed

- If it still does not work, try switching Wi-Fi channel on your Wi-Fi router. Only channels 1, 6 or 11 should be used (see explanation here:

https://www.metageek.com/training/resou ... -6-11.html
KD2HYE
Posts: 9
Joined: Wed Jan 20, 2021 5:34 pm

Re: High Packet Loss Garbled RX very clear TX

Post by KD2HYE »

Interesting,

I have not played with the radio bandwidth.

For the 2.4G AP should I set the bandwidth to VHT 20 or 40?

I had it set to 20 to minimize the chance of interference... I live in a apartment building.... but have changed to 40 now to test.

I currently have two Ubiquity HD 4x4 APs running from my Dream Machine Pro.

Code: Select all

2.4 GHz
Channel	
Auto11VHT40
Transmit Power	23 dBm / 26 dBm (EIRP)
Tx Pkts/Bytes	55,976,872 / 20.6 GB
Rx Pkts/Bytes	680,448,432 / 554 GB
Tx Retry/Dropped	0.0% / 0.0%
Rx Retry/Dropped	0.0% / 0.0%
Ch. Util. (Busy/Rx/Tx)	42% / 3% / 8%
# Users	11
# Guests	0
5 GHz
Channel	
4648,-1VHT40
Transmit Power	26 dBm / 29 dBm (EIRP)
Tx Pkts/Bytes	898,418,785 / 0.98 TB
Rx Pkts/Bytes	1,702,260,753 / 1.88 TB
Tx Retry/Dropped	2.8% / 0.0%
Rx Retry/Dropped	0.0% / 0.3%
Ch. Util. (Busy/Rx/Tx)	19% / 8% / 5%
# Users	18
# Guests	0
Cheers,

Jim.
Last edited by KD2HYE on Wed Jan 20, 2021 11:46 pm, edited 1 time in total.
N1IG
Posts: 179
Joined: Thu Apr 09, 2020 7:50 pm

Re: High Packet Loss Garbled RX very clear TX

Post by N1IG »

from the admin's posts and from what I understand the link to say, you want to set it to 20mhz. kind of counterintuitive from a bandwidth/speed perspective, but it lessens channel overlap and potential interference.

this way you can tell them that you tried that as well.
KD2HYE
Posts: 9
Joined: Wed Jan 20, 2021 5:34 pm

Re: High Packet Loss Garbled RX very clear TX

Post by KD2HYE »

Okay this is both strange and also quite exciting...

Changing the 2.4G bandwidth to 40 seems to have solved my issue... I am going to test for a little while longer to be sure... but so far very promising!
N1IG
Posts: 179
Joined: Thu Apr 09, 2020 7:50 pm

Re: High Packet Loss Garbled RX very clear TX

Post by N1IG »

I'm still on 62C if you want to test.
KD2HYE
Posts: 9
Joined: Wed Jan 20, 2021 5:34 pm

Re: High Packet Loss Garbled RX very clear TX

Post by KD2HYE »

Okay I can confirm changing the 2.4G radio bandwidth to 40 solved the issue.

So I am not sure if this is unique to Ubiquity APs but none the less I consider this resolved.

Thanks to N1IG for saving the day!!! :D :D :D :D :D :D :D
N1IG
Posts: 179
Joined: Thu Apr 09, 2020 7:50 pm

Re: High Packet Loss Garbled RX very clear TX

Post by N1IG »

Just for clarification, setting the wifi to 20Mhz did not work properly. Setting the wifi to 40Mhz appears to have corrected the problem.
Post Reply