Hotspot mode - Apparently stuck in TX

[W0RMT]

Follow-up: changing the RFhangtime to 5 in pi-star seems to help. No lockups (i.e. no "RF user has timed out") yet

[VK3KYY]

I think there are multiple bugs.

The TG 0 bug which I can put in a fix for.. Hopefully over the weekend when I get some free time, as its been a manic week for me with very little free time....

The other things where PiStar says the radio has stopped responding, are more difficult to fix, as I'd need to wait for the it to happen to me, with the debugger attached to the radio and running in the IDE etc.

But I left mine running for 5 hours last sunday in that configuration and had no problems

[DG1YFX]

Yeah, sometimes it happens after 5 min. Sometimes after hours. It has nothing to do with excess traffic on the TGs since I have very quiet personal TGs connected. The trick with the hangtime didn't work for me. It is indeed a nasty little bug.

73s
Jens

[kd2lh]

My guess (without better tracing) is that a buffered voice data packet inside OpenGD77 might be being sent again out of sequence to PiStar at a later (sometimes much later) time. I've seen my local RF transmission resent well after it occurred.

[DG1YFX]

Well,

if you reboot the hotspot and the GD-77, again it eventually will send a "fake" voice header. But since it has either ID nor TG this is what the log says:
"M: 2019-12-14 17:58:35.882 DMR Slot 2, RF user 0 rejected"
And it will not block. But as soon as I use RF, it will echo the voice header within the next minutes up to an hour and this will block the system until I press the PTT. I don't know, what data are GD-77 and MMDVM are exchanging in idle mode.

73s,
Jens

[ad4uu]

Hi, I have been having the TX hang issue since I started with the openGD77 about a week ago. I have had little success in getting it to not hang.
I have tried a RPI 3a and pi-0. Also pi-star 4.0 and 4.1. Currently it hangs 100 % of the time. Not usable.

When it has worked it seems to be be when I make a change to something. Example. Firmware and most recently I went from pi-star 4.1 to
4.0. It worked for about 10 minutes.

I have read through this thread and applied the recommended changes to pi-star setting,DMR and General with no success.

Overall its worked about 5 % of the time in the past week.

Thanks for your work on this issue and overall project. Pretty cool.

Dave/AD4UU

[W0RMT]

Dave/AD4UU- if you want to use the radio just as a hotspot and don't need/want the Tier 2 capabilities and latest features, you can always install the stable Tier 1 hotspot FW which works well. You can download that version here

[ad4uu]

Hello Bud, Thanks for help.

I only need tier 1. I have download and put into the radio. I was not able to connect to the hotspot with the RPI.
I found another link for another post asking for the stable version tier 1. Saw this "link.https://github.com/rogerclarkmelbourne/ ... ily_builds" from Robert.

I loaded it into the radio. As previous attempts it worked for about 30 minutes and then TX hangs. After several restarts it would
work for a transmission or 2. Now back to TX on 100 % of the time.

On the first TX hang the hotspot keys up briefly 1/2 second or so then pi-star stays in TX.
Dave/AD4UU

[W0RMT]

Hello Bud, Thanks for help.

I only need tier 1. I have download and put into the radio. I was not able to connect to the hotspot with the RPI.
I found another link for another post asking for the stable version tier 1. Saw this "link.https://github.com/rogerclarkmelbourne/ ... ily_builds" from Robert.

I loaded it into the radio. As previous attempts it worked for about 30 minutes and then TX hangs. After several restarts it would
work for a transmission or 2. Now back to TX on 100 % of the time.

On the first TX hang the hotspot keys up briefly 1/2 second or so then pi-star stays in TX.
Dave/AD4UU

Can you post the pi-star log files from when it hangs up?

[ad4uu]

Thanks Bud,

Here is the live log. I keyed up 31665. N9KFW keyed up briefly. Then when kc8usa keyed up it Hung on TX.

Starting logging, please wait...
M: 2019-12-15 17:08:46.291 DMR Slot 2, received RF voice header from AD4UU to TG 31665
M: 2019-12-15 17:08:47.494 DMR Slot 2, received RF end of voice transmission from AD4UU to TG 31665, 0.0 seconds, BER: 0.0%
M: 2019-12-15 17:10:12.432 DMR Slot 2, received network voice header from N9KFW to TG 31665
M: 2019-12-15 17:10:12.531 DMR Slot 2, received network end of voice transmission from N9KFW to TG 31665, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-15 17:11:06.576 DMR Slot 2, received network voice header from KC8USA to TG 31665

Thanks

Dave