Hotspot mode - Apparently stuck in TX

[kd2lh]

Will do. Back with updates shortly.

[kd2lh]

It's been running for a few hours. It's continuing to work, but this was logged:

M: 2020-01-03 15:20:15.708 DMR Slot 2, received network voice header from G4KXQ to TG 98977
M: 2020-01-03 15:20:16.371 DMR Talker Alias (Data Format 1, Received 6/21 char): 'G4KXQ '
M: 2020-01-03 15:20:16.371 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-03 15:20:16.371 0000: 04 00 6A 47 34 4B 58 51 20 *..jG4KXQ *
M: 2020-01-03 15:20:17.087 DMR Talker Alias (Data Format 1, Received 13/21 char): 'G4KXQ DMR ID:'
M: 2020-01-03 15:20:17.087 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-03 15:20:17.087 0000: 05 00 44 4D 52 20 49 44 3A *..DMR ID:*
M: 2020-01-03 15:20:17.803 DMR Talker Alias (Data Format 1, Received 20/21 char): 'G4KXQ DMR ID: 234613'
M: 2020-01-03 15:20:17.803 DMR Slot 2, Embedded Talker Alias Block 2
M: 2020-01-03 15:20:17.803 0000: 06 00 20 32 33 34 36 31 33 *.. 234613*
M: 2020-01-03 15:20:18.526 DMR Talker Alias (Data Format 1, Received 21/21 char): 'G4KXQ DMR ID: 2346139'
M: 2020-01-03 15:20:18.526 DMR Slot 2, Embedded Talker Alias Block 3
M: 2020-01-03 15:20:18.526 0000: 07 00 39 00 00 00 00 00 00 *..9......*
M: 2020-01-03 15:20:21.173 DMR Slot 2, received network end of voice transmission from G4KXQ to TG 98977, 5.5 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-03 16:35:30.145 DMR Slot 2, RF user 0 rejected
M: 2020-01-03 17:01:48.133 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 17:01:51.927 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 3.2 seconds, BER: 1.7%

[F1RMB]

Hi Marc,

It's been running for a few hours. It's continuing to work, but this was logged:

M: 2020-01-03 15:20:15.708 DMR Slot 2, received network voice header from G4KXQ to TG 98977
M: 2020-01-03 15:20:16.371 DMR Talker Alias (Data Format 1, Received 6/21 char): 'G4KXQ '
M: 2020-01-03 15:20:16.371 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-03 15:20:16.371 0000: 04 00 6A 47 34 4B 58 51 20 *..jG4KXQ *
M: 2020-01-03 15:20:17.087 DMR Talker Alias (Data Format 1, Received 13/21 char): 'G4KXQ DMR ID:'
M: 2020-01-03 15:20:17.087 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-03 15:20:17.087 0000: 05 00 44 4D 52 20 49 44 3A *..DMR ID:*
M: 2020-01-03 15:20:17.803 DMR Talker Alias (Data Format 1, Received 20/21 char): 'G4KXQ DMR ID: 234613'
M: 2020-01-03 15:20:17.803 DMR Slot 2, Embedded Talker Alias Block 2
M: 2020-01-03 15:20:17.803 0000: 06 00 20 32 33 34 36 31 33 *.. 234613*
M: 2020-01-03 15:20:18.526 DMR Talker Alias (Data Format 1, Received 21/21 char): 'G4KXQ DMR ID: 2346139'
M: 2020-01-03 15:20:18.526 DMR Slot 2, Embedded Talker Alias Block 3
M: 2020-01-03 15:20:18.526 0000: 07 00 39 00 00 00 00 00 00 *..9......*
M: 2020-01-03 15:20:21.173 DMR Slot 2, received network end of voice transmission from G4KXQ to TG 98977, 5.5 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-03 16:35:30.145 DMR Slot 2, RF user 0 rejected
M: 2020-01-03 17:01:48.133 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 17:01:51.927 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 3.2 seconds, BER: 1.7%

Okay. Yes, yesterday I saw that ID 0 messages.
But the good point is it doesn't lock anymore

Many thanks for the test.

Cheers.
---
Daniel

[kd2lh]

I just found it locked up again with TX red. It's been hung up for a couple of hours after the last time I transmitted to the hotspot. I don't recall this locking up at the time, but it probably coincides with the RF User timed out message.

M: 2020-01-03 20:36:50.310 DMR Slot 2, received network end of voice transmission from KB3KBD to TG 31371, 7.7 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-03 20:39:04.504 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 20:43:04.667 DMR Slot 2, RF user has timed out

In the GD77, The "Rx-Process" counter continues to increment, and "RX_Start" is "275". "K" is blinking with "0x1" after it and Q is "0x3".


The PiStar dashboard has "TX" red and stuck with a time of 15:39:04 which was my last transmission to the radio (logged +5 hours UTC).

When I transmitted again to the hotspot locally, the condition cleared up in PiStar.

M: 2020-01-03 20:39:04.504 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 20:43:04.667 DMR Slot 2, RF user has timed out
M: 2020-01-03 22:16:59.112 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 2.9 seconds, BER: 1.7%

I saved the entire log if it's useful. Marc

[kd2lh]

Happened again.

M: 2020-01-03 22:56:09.182 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 23:00:09.322 DMR Slot 2, RF user has timed out

Originally, the transmission ended normally, but a few minutes later the timeout message and the red TX stuck on the dashboard.

The 22:56:09 transmission was the last local transmit.

The GD77 display shows:
"RX_PROCESS [running incrementing number]
"RX_START 336"
blinking "K" "0x1"
"Q" "0x3"

Again, when I transmit locally, things reset and the dashboard returns to normal after the first new transmission has ended:

M: 2020-01-03 22:56:09.182 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 23:00:09.322 DMR Slot 2, RF user has timed out
M: 2020-01-04 00:01:17.053 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 6.8 seconds, BER: 1.2%
M: 2020-01-04 00:01:40.062 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-04 00:01:44.346 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 4.0 seconds, BER: 0.6%

[F1RMB]

Hi,

Happened again.

M: 2020-01-03 22:56:09.182 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 23:00:09.322 DMR Slot 2, RF user has timed out

Originally, the transmission ended normally, but a few minutes later the timeout message and the red TX stuck on the dashboard.

The 22:56:09 transmission was the last local transmit.

The GD77 display shows:
"RX_PROCESS [running incrementing number]
"RX_START 336"
blinking "K" "0x1"
"Q" "0x3"

Again, when I transmit locally, things reset and the dashboard returns to normal after the first new transmission has ended:

M: 2020-01-03 22:56:09.182 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 23:00:09.322 DMR Slot 2, RF user has timed out
M: 2020-01-04 00:01:17.053 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 6.8 seconds, BER: 1.2%
M: 2020-01-04 00:01:40.062 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-04 00:01:44.346 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 4.0 seconds, BER: 0.6%

Okay, many thanks for the tests you've made, and reporting all the informations. I will investigate this today, and probably ask you to to test it, again

Cheers.
---
Daniel

[F1RMB]

Hi Marc,

Hi,

Happened again.

M: 2020-01-03 22:56:09.182 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 23:00:09.322 DMR Slot 2, RF user has timed out

Originally, the transmission ended normally, but a few minutes later the timeout message and the red TX stuck on the dashboard.

The 22:56:09 transmission was the last local transmit.

The GD77 display shows:
"RX_PROCESS [running incrementing number]
"RX_START 336"
blinking "K" "0x1"
"Q" "0x3"

Again, when I transmit locally, things reset and the dashboard returns to normal after the first new transmission has ended:

M: 2020-01-03 22:56:09.182 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-03 23:00:09.322 DMR Slot 2, RF user has timed out
M: 2020-01-04 00:01:17.053 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 6.8 seconds, BER: 1.2%
M: 2020-01-04 00:01:40.062 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-04 00:01:44.346 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 4.0 seconds, BER: 0.6%

Okay, many thanks for the tests you've made, and reporting all the informations. I will investigate this today, and probably ask you to to test it, again

Cheers.
---
Daniel

Here is another one.

Cheers.
---
Daniel

EDIT: firmware delete, a new build is available.

[KU4ZD]

I know you are not testing for use on the BLueDV application but
just wanted to let you know the last firmware update
firmware_hs_dbg.sgl
still is causing the misconfigured radio errors
on the TGIF network using the BlueDV
just for your information
thank you for all the work you are doing

[F1RMB]

Hi Mike,

I know you are not testing for use on the BLueDV application but
just wanted to let you know the last firmware update
firmware_hs_dbg.sgl
still is causing the misconfigured radio errors
on the TGIF network using the BlueDV
just for your information
thank you for all the work you are doing

True, but BlueDV-9572-preBETA is installed in my VM, and TGIF config modification is already done.

Cheers.

[KU4ZD]

No worry, I just thought I would check. I know it is not the focus of what you are working on right now. I did gi back to the last standard release of the firmware and that does work fine.