Hotspot mode - Apparently stuck in TX

[F1RMB]

Can someone who's experiencing the TX lockup can test this version ?

Please, disregard the hotspot screen, it's full of debug informations, so don't be surprised.

Cheers.

EDIT: attachment delete, as it was still locking.

[kd2lh]

Will do...

It's now running with the dashboard live log running on one browser session.

No problems in the last 20 minutes. I'll leave it running until a problem occurs, and try and capture the log and GD77 screen info.

[F1RMB]

Will do...

Thanks

[KU4ZD]

This version causes a 'misconfigured radio' error when using it with BLUEDV (latest beta version)
if I watch my transmissions on the last Heard page of the TGIF network, every time I sent to
a talk group my call will show up but then change to misconfigured radio. I went back to the last
version of the firmware and everything works fine.

Can someone who's experiencing the TX lockup can test this version ?

Please, disregard the hotspot screen, it's full of debug informations, so don't be surprised.

Cheers.

[F1RMB]

Hi,

This version causes a 'misconfigured radio' error when using it with BLUEDV (latest beta version)
if I watch my transmissions on the last Heard page of the TGIF network, every time I sent to
a talk group my call will show up but then change to misconfigured radio. I went back to the last
version of the firmware and everything works fine.

Can someone who's experiencing the TX lockup can test this version ?

Please, disregard the hotspot screen, it's full of debug informations, so don't be surprised.

Cheers.

Okay. I didn't specified I'm testing with MMDVMHost right now, didn't checked with BlueDV yet.

Thanks for the test


Cheers.
---
Daniel

[KU4ZD]

No problem, at least you know that what ever you changed created a issue with BlueDV
I have been back on the last firmware version and it is running ok again. Thanks for all your work

[F1RMB]

No problem, at least you know that what ever you changed created a issue with BlueDV
I have been back on the last firmware version and it is running ok again. Thanks for all your work

Stangely, BlueDV on Android doesn't have this problem...

[F1RMB]

No problem, at least you know that what ever you changed created a issue with BlueDV
I have been back on the last firmware version and it is running ok again. Thanks for all your work

Stangely, BlueDV on Android doesn't have this problem...

Screenshot at 2020-01-02 16-57-17.png (13.76 KiB) Viewed 4120 times

Just grabbed last heard on BM

Screenshot at 2020-01-02 17-02-57.png (22.17 KiB) Viewed 4116 times

[kd2lh]

PiStar missed an "End of Voice" packet after the local call to 3100 talkgroup:

M: 2020-01-02 15:51:54.770 DMR Slot 2, received RF voice header from KD2LH to TG 3100
<<<<<<<comment>>>>>> the end of voice transmission was not received by pi star, and the dashboard was stuck until I made a local call to 9990. When that call ended, the parrot didn't function and the following message appeared on PiStar<<<>>>:
M: 2020-01-02 15:52:58.361 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 3100, 2.9 seconds, BER: 0.9%
<<<<<<<comment>>>>>> I then made a second call to the parrot that worked properly. <<<<>>>>:
M: 2020-01-02 15:53:24.119 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-02 15:53:27.156 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 2.5 seconds, BER: 0.8%
M: 2020-01-02 15:53:30.451 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-02 15:53:32.917 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 2.6 seconds, 0% packet loss, BER: 0.0%

It only showed up (the second line) after I made a local call to a different talkgroup (9990) but was reported to PiStar as coming from TG 3100, not private call 9990. The second call to the parrot worked.

The "mmdvm_get_status" message 0x1 was on the GD77 display while it was stopped (with the call to TG3100 still shown in TX on PiStar) until the start of my next local transmission (the first to private call 9990).

It looks like PiStar MMDVMHost missed the first incoming "end of voice" transmission packet from GD77.

[F1RMB]

Hi,

PiStar missed an "End of Voice" packet after the local call to 3100 talkgroup:

M: 2020-01-02 15:51:54.770 DMR Slot 2, received RF voice header from KD2LH to TG 3100
<<<<<<<comment>>>>>> the end of voice transmission was not received by pi star, and the dashboard was stuck until I made a local call to 9990. When that call ended, the parrot didn't function and the following message appeared on PiStar<<<>>>:
M: 2020-01-02 15:52:58.361 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 3100, 2.9 seconds, BER: 0.9%
<<<<<<<comment>>>>>> I then made a second call to the parrot that worked properly. <<<<>>>>:
M: 2020-01-02 15:53:24.119 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-02 15:53:27.156 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 2.5 seconds, BER: 0.8%
M: 2020-01-02 15:53:30.451 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-02 15:53:32.917 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 2.6 seconds, 0% packet loss, BER: 0.0%

It only showed up (the second line) after I made a local call to a different talkgroup (9990) but was reported to PiStar as coming from TG 3100, not private call 9990. The second call to the parrot worked.

The "mmdvm_get_status" message 0x1 was on the GD77 display while it was stopped (with the call to TG3100 still shown in TX on PiStar) until the start of my next local transmission (the first to private call 9990).

It looks like PiStar MMDVMHost missed the first incoming "end of voice" transmission packet from GD77.

Okay, hummm, I will look at this, if I can reproduce.

Thank you for the test.

Cheers.
---
Daniel