4.3.2 / 4.3.3 / 4.3.4 Beta Feedback

[KA1PIT]

On the dashboard I did a, configuration -> Expert -> MMDVMHost -> NextionDriver. The port box I changed from modem to /dev/ttyUSB0. applied
changes and rebooted. Bingo, the nextion screen is back up and working. I let it run for about an hour and just rebooted it and the screen came
back up and is working. Now I shut the pistar down and pulled the power. Plugged it back in and powered it up and the screen is working!

thank you
scott

[VE3RD]

I am running a Pi Zero W with 4.3.4
Any change I make in Pi-star expert mode mmdvmHost, whether I hit the Apply Changes or the Enter Key will, stop MMDVMHost and I have to manually restart it

my pi-3b and pi-4b are fine

[W1TG]

Jonathan (G4KLX) has added some more changes in MMDVMHost that might (please help us testing) cure the remaining issues in MMDVMHost with D-Star. Those of you running 4.3.4, please update and give it a go and see if you get any more of those issues.

Pi-Star: 4.3.4 / Dashboard: 20250424
MMDVMHost: 20250422_PS4 git #3bb600e
Platform: Raspberry Pi 4 Model B Rev 1.5
Modem: DVMEGA HR3.26

This version of MMDVMHost seems to have more problems than the prior. Here's what I've experienced in one QSO:
1. Receiving audio trails off and stops randomly.
2. On keyup to tx - Signal isn't decoded and conveyed to the reflector (no dashboard indicators)
Tailing the log yields: M: 2025-04-25 11:04:25.285 D-Star, received RF late entry from W1TG /52AN to CQCQCQ
Second attempt usually goes through
3. Another example - with different log results:
M: 2025-04-25 11:06:57.419 D-Star, received RF header from W1TG /52AN to CQCQCQ
Unkey, second or third attempt usually goes through
4. Example of rx audio trailing off and dashboard indicators show still in tx. I keyed to reply and the dashboard indicators returned to normal.
Logs recorded for this event:

2025-04-25 11:20:38: DPlus header - My: AA1HO /ART Your: CQCQCQ Rpt1: AA1HO D Rpt2: REF050 C Flags: 00 00 00 (75.147.26.195:20001)
M: 2025-04-25 11:20:38.134 D-Star, received network header from AA1HO /ART to CQCQCQ via REF050 C
<SNIPPED SLOW DATA TEXT>
M: 2025-04-25 11:23:58.280 Mode set to Idle
<OBSERVED = Received audio stopped and dashboard displayed as though it was receiving>

<ACTION = Keyed down to transmit>
M: 2025-04-25 11:24:07.721 D-Star, received RF header from W1TG /52AN to CQCQCQ
M: 2025-04-25 11:24:07.721 Mode set to D-Star

M: 2025-04-25 11:24:07.877 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:24:07.965 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-25 11:24:14.335 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 7.0 seconds, BER: 0.0%
M: 2025-04-25 11:24:19.553 D-Star, network watchdog has expired, 221.1 seconds, 2% packet loss, BER: 0.0%

I appreciate the efforts to work this out!
Tom - W1TG

[VA3UV]

Jonathan (G4KLX) has added some more changes in MMDVMHost that might (please help us testing) cure the remaining issues in MMDVMHost with D-Star. Those of you running 4.3.4, please update and give it a go and see if you get any more of those issues.

Pi-Star: 4.3.4 / Dashboard: 20250424
MMDVMHost: 20250422_PS4 git #3bb600e
Platform: Raspberry Pi 4 Model B Rev 1.5
Modem: DVMEGA HR3.26

This version of MMDVMHost seems to have more problems than the prior. Here's what I've experienced in one QSO:
1. Receiving audio trails off and stops randomly.
2. On keyup to tx - Signal isn't decoded and conveyed to the reflector (no dashboard indicators)
Tailing the log yields: M: 2025-04-25 11:04:25.285 D-Star, received RF late entry from W1TG /52AN to CQCQCQ
Second attempt usually goes through
3. Another example - with different log results:
M: 2025-04-25 11:06:57.419 D-Star, received RF header from W1TG /52AN to CQCQCQ
Unkey, second or third attempt usually goes through
4. Example of rx audio trailing off and dashboard indicators show still in tx. I keyed to reply and the dashboard indicators returned to normal.
Logs recorded for this event:

2025-04-25 11:20:38: DPlus header - My: AA1HO /ART Your: CQCQCQ Rpt1: AA1HO D Rpt2: REF050 C Flags: 00 00 00 (75.147.26.195:20001)
M: 2025-04-25 11:20:38.134 D-Star, received network header from AA1HO /ART to CQCQCQ via REF050 C
<SNIPPED SLOW DATA TEXT>
M: 2025-04-25 11:23:58.280 Mode set to Idle
<OBSERVED = Received audio stopped and dashboard displayed as though it was receiving>

<ACTION = Keyed down to transmit>
M: 2025-04-25 11:24:07.721 D-Star, received RF header from W1TG /52AN to CQCQCQ
M: 2025-04-25 11:24:07.721 Mode set to D-Star

M: 2025-04-25 11:24:07.877 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:24:07.965 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-25 11:24:14.335 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 7.0 seconds, BER: 0.0%
M: 2025-04-25 11:24:19.553 D-Star, network watchdog has expired, 221.1 seconds, 2% packet loss, BER: 0.0%

I appreciate the efforts to work this out!
Tom - W1TG

Hello Tom:

I have been helping Andy (and indirectly Jonathan) refine MMDVMHost to resolve these last few issues. I am curious to know whether your "RF late entry" error is occurring on a full-duplex repeater, or a simplex hotspot?

I have also seen this issue on a repeater system that I'm testing pre-deployment. I do have a slightly newer build than you, but the problem you describe occurs with the newer build too. I was beginning to think that may be my 83 / 84dB notches in the duplexer are not cutting it.

If this is on a repeater system, I'd be curious to know what your reject notch depth is, and whether you can re-test with a dummy load on the repeater RX port?


Thanks,

Ramesh, VA3UV, WA3UV, G4PNQ
(Usually found on XLX405A)

[W1TG]

Hello Tom:

I have been helping Andy (and indirectly Jonathan) refine MMDVMHost to resolve these last few issues. I am curious to know whether your "RF late entry" error is occurring on a full-duplex repeater, or a simplex hotspot?

I have also seen this issue on a repeater system that I'm testing pre-deployment. I do have a slightly newer build than you, but the problem you describe occurs with the newer build too. I was beginning to think that may be my 83 / 84dB notches in the duplexer are not cutting it.

If this is on a repeater system, I'd be curious to know what your reject notch depth is, and whether you can re-test with a dummy load on the repeater RX port?

Thanks,

Ramesh, VA3UV, WA3UV, G4PNQ
(Usually found on XLX405A)

Hi Ramesh - This is just a simplex 10mw hotspot. Sorry no help for you.

Tom - W1tg

[VA3UV]

Hello Tom:

I have been helping Andy (and indirectly Jonathan) refine MMDVMHost to resolve these last few issues. I am curious to know whether your "RF late entry" error is occurring on a full-duplex repeater, or a simplex hotspot?

I have also seen this issue on a repeater system that I'm testing pre-deployment. I do have a slightly newer build than you, but the problem you describe occurs with the newer build too. I was beginning to think that may be my 83 / 84dB notches in the duplexer are not cutting it.

If this is on a repeater system, I'd be curious to know what your reject notch depth is, and whether you can re-test with a dummy load on the repeater RX port?

Thanks,

Ramesh, VA3UV, WA3UV, G4PNQ
(Usually found on XLX405A)

Hi Ramesh - This is just a simplex 10mw hotspot. Sorry no help for you.

Tom - W1tg

HI Tom: Thanks, that is very helpful actually! - it helps in identifying that the issue is not isolated to duplex systems.. and I don't have to worry about adding extra cavities on my 2m repeater!

I'd be interesting in knowing whether others are seeing this / irrespective of simplex or duplex systems?

Thanks,

Ramesh, VA3UV, WA3UV, G4PNQ

[MW0MWZ]

M: 2025-04-25 11:20:38.134 D-Star, received network header from AA1HO /ART to CQCQCQ via REF050 C
<SNIPPED SLOW DATA TEXT>
M: 2025-04-25 11:23:58.280 Mode set to Idle

I'm actually interested in the bit that was snipped here, do you have it still?

[W1TG]

M: 2025-04-25 11:20:38.134 D-Star, received network header from AA1HO /ART to CQCQCQ via REF050 C
<SNIPPED SLOW DATA TEXT>
M: 2025-04-25 11:23:58.280 Mode set to Idle

I'm actually interested in the bit that was snipped here, do you have it still?

2025-04-25 11:20:38: DPlus header - My: AA1HO /ART Your: CQCQCQ Rpt1: AA1HO D Rpt2: REF050 C Flags: 00 00 00 (75.147.26.195:20001)
M: 2025-04-25 11:20:38.134 D-Star, received network header from AA1HO /ART to CQCQCQ via REF050 C
M: 2025-04-25 11:20:38.289 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:21:08.118 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:21:37.932 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:22:08.170 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:22:37.998 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:23:07.815 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:23:38.054 D-Star, network slow data text = "ART LOWELL MA ID51A "
M: 2025-04-25 11:23:58.280 Mode set to Idle

[W1TG]

Here's some more clips from a QSO today where I experienced issues. These were all "RF Late Entry" type events. I keyed down, the modem heard me, wrote to the logs, but didn't make it to the network. I had an OpenSpot monitoring the reflector and in all cases the late entry keydown didn't get passed to the network. Unkeying, pause, and keying a second time provided normal operation. In one case I experienced the late entry issue twice. I didn't experience any "stuck" tx in this qso.

Tom - W1TG

Pi-Star:4.3.4 / Dashboard: 20250424
MMDVMHost: 20250422_PS4 git #3bb600e
Platform: Raspberry Pi 4 Model B Rev 1.5
Modem: DVMEGA HR3.26

<ACTION = Keyed down to transmit-No Joy>
M: 2025-04-27 13:24:58.207 D-Star, received RF late entry from W1TG /52AN to CQCQCQ
M: 2025-04-27 13:25:03.612 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 5.4 seconds, BER: 0.0%

M: 2025-04-27 13:25:07.482 D-Star, received RF header from W1TG /52AN to CQCQCQ
2025-04-27 13:25:07: Repeater header - My: W1TG /52AN Your: CQCQCQ Rpt1: W1TG A Rpt2: W1TG G Flags: 00 00 00 (127.0.0.1:20011)
M: 2025-04-27 13:25:07.736 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:25:37.331 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:26:07.490 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:26:29.780 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 82.7 seconds, BER: 0.0%

<ACTION = Keyed down to transmit-No Joy>
M: 2025-04-27 13:27:36.403 D-Star, received RF late entry from W1TG /52AN to CQCQCQ
M: 2025-04-27 13:27:41.423 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 5.2 seconds, BER: 0.0%

M: 2025-04-27 13:27:44.846 D-Star, received RF header from W1TG /52AN to CQCQCQ
2025-04-27 13:27:44: Repeater header - My: W1TG /52AN Your: CQCQCQ Rpt1: W1TG A Rpt2: W1TG G Flags: 00 00 00 (127.0.0.1:20011)
M: 2025-04-27 13:27:45.085 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:27:57.383 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 12.9 seconds, BER: 0.0%

<ACTION = Keyed down to transmit-No Joy>
M: 2025-04-27 13:36:12.941 D-Star, received RF late entry from W1TG /52AN to CQCQCQ
M: 2025-04-27 13:36:18.344 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 5.4 seconds, BER: 0.0%

<ACTION = Keyed down to transmit-No Joy>
M: 2025-04-27 13:36:22.944 D-Star, received RF late entry from W1TG /52AN to CQCQCQ
M: 2025-04-27 13:36:26.112 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 3.3 seconds, BER: 0.0%

M: 2025-04-27 13:36:29.262 D-Star, received RF header from W1TG /52AN to CQCQCQ
2025-04-27 13:36:29: Repeater header - My: W1TG /52AN Your: CQCQCQ Rpt1: W1TG A Rpt2: W1TG G Flags: 00 00 00 (127.0.0.1:20011)
M: 2025-04-27 13:36:29.517 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:36:59.113 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:37:28.935 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:37:33.039 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 64.2 seconds, BER: 0.0%

2025-04-27 13:45:00: G2 header - My: W1TG /TIME Your: CQCQCQ Rpt1: W1TG G Rpt2: W1TG A Flags: 00 00 00 (127.0.0.1:56666)
M: 2025-04-27 13:45:00.414 D-Star, received network header from W1TG /TIME to CQCQCQ via REF050 C
M: 2025-04-27 13:45:01.176 D-Star, network slow data text = "It is 09:45 AM "
M: 2025-04-27 13:45:01.852 D-Star, network slow data text = "It is 09:45 AM "
M: 2025-04-27 13:45:02.698 D-Star, network slow data text = "It is 09:45 AM "
M: 2025-04-27 13:45:03.538 D-Star, network slow data text = "It is 09:45 AM "
M: 2025-04-27 13:45:04.384 D-Star, network slow data text = "It is 09:45 AM "
M: 2025-04-27 13:45:05.202 D-Star, received network end of transmission from W1TG /TIME to CQCQCQ , 4.8 seconds, 0% packet loss, BER: 0.0%

<ACTION = Keyed down to transmit-No Joy>
M: 2025-04-27 13:45:07.460 D-Star, received RF late entry from W1TG /52AN to CQCQCQ
M: 2025-04-27 13:45:12.789 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 5.5 seconds, BER: 0.0%

M: 2025-04-27 13:45:16.318 D-Star, received RF header from W1TG /52AN to CQCQCQ
2025-04-27 13:45:16: Repeater header - My: W1TG /52AN Your: CQCQCQ Rpt1: W1TG A Rpt2: W1TG G Flags: 00 00 00 (127.0.0.1:20011)
M: 2025-04-27 13:45:16.571 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:46:16.371 D-Star, RF slow data text = "TOM - HAMPTON, NH "
M: 2025-04-27 13:46:20.892 D-Star, received RF end of transmission from W1TG /52AN to CQCQCQ , 65.0 seconds, BER: 0.0%

[M0HYL]

I belong to the Radio society of Harrow and the club has reflashed the SD card to 4.3.4 from 4.1.10 but although it appears to work fine on dmr on ysf it will not change rooms when using Yaesu Ft70D any ideas to solve the problem much appreciated