Hotspot mode - Apparently stuck in TX

User avatar
kd2lh
Posts: 171
Joined: Mon Dec 02, 2019 2:44 pm

Re: Hotspot mode - Apparently stuck in TX

Post by kd2lh » Sat Jan 04, 2020 7:56 pm

One more lockup.

I observed this one. No local radio was transmitting at the time, but GD77 sent a packet in to PiStar:

M: 2020-01-04 19:49:25.118 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:49:30.816 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-04 19:51:18.336 DMR Slot 2, received RF voice header from KD2LH to 9990

The last "received RF voice header" was sent in even though there was no local RF activity.

"RX_Start" is displaying "704"
"RX_Process" continues to increment.
blinking "K" is "0x1"
Q is "0x3"

After receiving this orphan voice header, the PiStar is stuck in red "TX"mode. The GD77 is not transmitting.

The first time I make a local transmission to the parrrot, it resets the PiStar interface, but doesn't forward anything to the Parrot. The second time I transmit to the parrot, it works.

here's the entire logged sequence:

M: 2020-01-04 19:49:25.118 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:49:30.816 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-04 19:51:18.336 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 19:55:18.521 DMR Slot 2, RF user has timed out
M: 2020-01-04 19:55:25.041 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 3.2 seconds, BER: 0.9%
M: 2020-01-04 19:56:02.455 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 19:56:07.011 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 4.0 seconds, BER: 1.1%
M: 2020-01-04 19:56:10.294 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:56:14.194 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 4.1 seconds, 0% packet loss, BER: 0.0%

- - - - -

Here's another lockup, just like the last one. Again, no local RF activity triggered this:

M: 2020-01-04 20:00:11.447 DMR Slot 2, received network voice header from KD2LH to TG 98977
M: 2020-01-04 20:00:12.855 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2020-01-04 20:00:12.855 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-04 20:00:12.855 0000: 05 00 4D 61 72 63 20 52 61 *..Marc Ra*
M: 2020-01-04 20:00:13.572 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2020-01-04 20:00:13.572 DMR Slot 2, Embedded Talker Alias Block 2
M: 2020-01-04 20:00:13.572 0000: 06 00 6C 65 69 67 68 20 00 *..leigh .*
M: 2020-01-04 20:00:14.298 DMR Talker Alias (Data Format 1, Received 19/19 char): 'KD2LH Marc Raleigh '
M: 2020-01-04 20:00:14.298 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-04 20:00:14.298 0000: 04 00 66 4B 44 32 4C 48 20 *..fKD2LH *
M: 2020-01-04 20:00:16.217 DMR Slot 2, received network end of voice transmission from KD2LH to TG 98977, 4.9 seconds, 2% packet loss, BER: 0.0%
M: 2020-01-04 20:47:51.199 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 20:51:51.380 DMR Slot 2, RF user has timed out

On this one, th3e GD77 display "RX_Start" was 835"
all the others were as before.
Marc

User avatar
F1RMB
Posts: 404
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Sun Jan 05, 2020 5:26 am

Hi Marc,
kd2lh wrote:
Sat Jan 04, 2020 7:56 pm
One more lockup.

I observed this one. No local radio was transmitting at the time, but GD77 sent a packet in to PiStar:

M: 2020-01-04 19:49:25.118 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:49:30.816 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-04 19:51:18.336 DMR Slot 2, received RF voice header from KD2LH to 9990

The last "received RF voice header" was sent in even though there was no local RF activity.

"RX_Start" is displaying "704"
"RX_Process" continues to increment.
blinking "K" is "0x1"
Q is "0x3"

After receiving this orphan voice header, the PiStar is stuck in red "TX"mode. The GD77 is not transmitting.

The first time I make a local transmission to the parrrot, it resets the PiStar interface, but doesn't forward anything to the Parrot. The second time I transmit to the parrot, it works.

here's the entire logged sequence:

M: 2020-01-04 19:49:25.118 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:49:30.816 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-04 19:51:18.336 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 19:55:18.521 DMR Slot 2, RF user has timed out
M: 2020-01-04 19:55:25.041 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 3.2 seconds, BER: 0.9%
M: 2020-01-04 19:56:02.455 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 19:56:07.011 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 4.0 seconds, BER: 1.1%
M: 2020-01-04 19:56:10.294 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:56:14.194 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 4.1 seconds, 0% packet loss, BER: 0.0%

- - - - -

Here's another lockup, just like the last one. Again, no local RF activity triggered this:

M: 2020-01-04 20:00:11.447 DMR Slot 2, received network voice header from KD2LH to TG 98977
M: 2020-01-04 20:00:12.855 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2020-01-04 20:00:12.855 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-04 20:00:12.855 0000: 05 00 4D 61 72 63 20 52 61 *..Marc Ra*
M: 2020-01-04 20:00:13.572 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2020-01-04 20:00:13.572 DMR Slot 2, Embedded Talker Alias Block 2
M: 2020-01-04 20:00:13.572 0000: 06 00 6C 65 69 67 68 20 00 *..leigh .*
M: 2020-01-04 20:00:14.298 DMR Talker Alias (Data Format 1, Received 19/19 char): 'KD2LH Marc Raleigh '
M: 2020-01-04 20:00:14.298 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-04 20:00:14.298 0000: 04 00 66 4B 44 32 4C 48 20 *..fKD2LH *
M: 2020-01-04 20:00:16.217 DMR Slot 2, received network end of voice transmission from KD2LH to TG 98977, 4.9 seconds, 2% packet loss, BER: 0.0%
M: 2020-01-04 20:47:51.199 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 20:51:51.380 DMR Slot 2, RF user has timed out

On this one, th3e GD77 display "RX_Start" was 835"
all the others were as before.
Marc
Okay, thanks for the userful informations. So, another timeout checking should be installed. I will try to look at this today.

Many thanks again for all the tests.

Cheers.
---
Daniel
73 de Daniel.

User avatar
F1RMB
Posts: 404
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Sun Jan 05, 2020 1:15 pm

Hi Marc,
kd2lh wrote:
Sat Jan 04, 2020 7:56 pm
One more lockup.

I observed this one. No local radio was transmitting at the time, but GD77 sent a packet in to PiStar:

M: 2020-01-04 19:49:25.118 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:49:30.816 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-04 19:51:18.336 DMR Slot 2, received RF voice header from KD2LH to 9990

The last "received RF voice header" was sent in even though there was no local RF activity.

"RX_Start" is displaying "704"
"RX_Process" continues to increment.
blinking "K" is "0x1"
Q is "0x3"

After receiving this orphan voice header, the PiStar is stuck in red "TX"mode. The GD77 is not transmitting.

The first time I make a local transmission to the parrrot, it resets the PiStar interface, but doesn't forward anything to the Parrot. The second time I transmit to the parrot, it works.

here's the entire logged sequence:

M: 2020-01-04 19:49:25.118 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:49:30.816 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-04 19:51:18.336 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 19:55:18.521 DMR Slot 2, RF user has timed out
M: 2020-01-04 19:55:25.041 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 3.2 seconds, BER: 0.9%
M: 2020-01-04 19:56:02.455 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 19:56:07.011 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 4.0 seconds, BER: 1.1%
M: 2020-01-04 19:56:10.294 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-04 19:56:14.194 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 4.1 seconds, 0% packet loss, BER: 0.0%

- - - - -

Here's another lockup, just like the last one. Again, no local RF activity triggered this:

M: 2020-01-04 20:00:11.447 DMR Slot 2, received network voice header from KD2LH to TG 98977
M: 2020-01-04 20:00:12.855 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2020-01-04 20:00:12.855 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-04 20:00:12.855 0000: 05 00 4D 61 72 63 20 52 61 *..Marc Ra*
M: 2020-01-04 20:00:13.572 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2020-01-04 20:00:13.572 DMR Slot 2, Embedded Talker Alias Block 2
M: 2020-01-04 20:00:13.572 0000: 06 00 6C 65 69 67 68 20 00 *..leigh .*
M: 2020-01-04 20:00:14.298 DMR Talker Alias (Data Format 1, Received 19/19 char): 'KD2LH Marc Raleigh '
M: 2020-01-04 20:00:14.298 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-04 20:00:14.298 0000: 04 00 66 4B 44 32 4C 48 20 *..fKD2LH *
M: 2020-01-04 20:00:16.217 DMR Slot 2, received network end of voice transmission from KD2LH to TG 98977, 4.9 seconds, 2% packet loss, BER: 0.0%
M: 2020-01-04 20:47:51.199 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-04 20:51:51.380 DMR Slot 2, RF user has timed out

On this one, th3e GD77 display "RX_Start" was 835"
all the others were as before.
Marc
Well, here is a new build. You'll find more informations displayed on the screen, so if it locks up, can you report all of them (just like you did before) ?.

Cheers, and thanks for your help.
---
Daniel
73 de Daniel.

User avatar
F1CXG
Posts: 128
Joined: Sat Nov 16, 2019 7:24 am
Location: GRENOBLE (France)

Re: Hotspot mode - Apparently stuck in TX

Post by F1CXG » Sun Jan 05, 2020 1:31 pm

Hi Daniel, even on Sundays he works! ! !
Good coding ;)
73 de Thierry ;)

User avatar
F1RMB
Posts: 404
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Sun Jan 05, 2020 1:57 pm

Hi Thierry,
F1CXG wrote:
Sun Jan 05, 2020 1:31 pm
Hi Daniel, even on Sundays he works! ! !
Good coding ;)
;)
73 de Daniel.

User avatar
kd2lh
Posts: 171
Joined: Mon Dec 02, 2019 2:44 pm

Re: Hotspot mode - Apparently stuck in TX

Post by kd2lh » Sun Jan 05, 2020 3:03 pm

Will do...

Note that these data packets are coming in from GD77 to PiStar without any local RF causing them. I'll get this loaded and running this AM.

Marc

User avatar
kd2lh
Posts: 171
Joined: Mon Dec 02, 2019 2:44 pm

Re: Hotspot mode - Apparently stuck in TX

Post by kd2lh » Sun Jan 05, 2020 3:32 pm

Here's a first interesting anomaly. No local RF activity from my DMR radio, but I saw the red receive light come on at the time this message came out:

M: 2020-01-05 15:25:33.546 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:25:42.343 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 8.6 seconds, BER: 1.8%
M: 2020-01-05 15:25:51.412 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:25:57.257 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 5.8 seconds, BER: 1.4%
M: 2020-01-05 15:26:00.536 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:26:06.244 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:26:17.739 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:26:22.545 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 4.7 seconds, BER: 1.4%
M: 2020-01-05 15:27:15.185 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:27:15.690 DMR Slot 2, RF voice transmission lost from KD2LH to TG 98977, 0.0 seconds, BER: 0.0%


Blinking "K" 0x1
Q "0x3"
Set_Status running incrementing count xxx
RX_Process very fast incrementing count 0 xxx
RX_Start 0 3 4 069
DMR_Lost 2 3 1 001

Here's a second one of these:

M: 2020-01-05 15:32:34.873 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:32:40.165 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 5.0 seconds, BER: 1.4%
M: 2020-01-05 15:32:43.414 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:32:48.405 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:42:42.666 DMR Slot 2, received network voice header from N3MAT to TG 31377
M: 2020-01-05 15:42:43.318 DMR Talker Alias (Data Format 1, Received 6/11 char): 'N3MAT '
M: 2020-01-05 15:42:43.318 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-05 15:42:43.319 0000: 04 00 56 4E 33 4D 41 54 20 *..VN3MAT *
M: 2020-01-05 15:42:43.560 DMR Slot 2, received network end of voice transmission from N3MAT to TG 31377, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:44:40.425 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:44:40.678 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 0.0 seconds, BER: 0.0%


GD77 display:
blinking K 0x1
Q 0x3
Set_Status incrementing 000 to 255
RX_Process 0 fast incrementing 0 255
RX_Start 0 3 4 230
DMR_Lost 2 3 1 002

Note that the next time I transmit to the GD77, nothing is forwarded to Brandmeister. The second time I transmit to the GD77, it is forwarded (in this example, a parrot call to private id 9990).

Here's what was logged:

M: 2020-01-05 15:42:43.319 0000: 04 00 56 4E 33 4D 41 54 20 *..VN3MAT *
M: 2020-01-05 15:42:43.560 DMR Slot 2, received network end of voice transmission from N3MAT to TG 31377, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:44:40.425 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:44:40.678 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 0.0 seconds, BER: 0.0%
M: 2020-01-05 15:54:30.596 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.183 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.720 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.778 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.078 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.105 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.440 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.498 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.801 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.861 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.117 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.217 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.518 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.576 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.870 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.939 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.239 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.299 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.600 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.626 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.958 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.017 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.316 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.382 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:56.083 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:54:58.872 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 2.5 seconds, BER: 1.3%
M: 2020-01-05 15:55:02.120 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:55:04.589 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 2.6 seconds, 4% packet loss, BER: 0.0%

User avatar
F1RMB
Posts: 404
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Sun Jan 05, 2020 4:11 pm

kd2lh wrote:
Sun Jan 05, 2020 3:32 pm
Here's a first interesting anomaly. No local RF activity from my DMR radio, but I saw the red receive light come on at the time this message came out:

M: 2020-01-05 15:25:33.546 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:25:42.343 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 8.6 seconds, BER: 1.8%
M: 2020-01-05 15:25:51.412 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:25:57.257 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 5.8 seconds, BER: 1.4%
M: 2020-01-05 15:26:00.536 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:26:06.244 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:26:17.739 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:26:22.545 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 4.7 seconds, BER: 1.4%
M: 2020-01-05 15:27:15.185 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:27:15.690 DMR Slot 2, RF voice transmission lost from KD2LH to TG 98977, 0.0 seconds, BER: 0.0%


Blinking "K" 0x1
Q "0x3"
Set_Status running incrementing count xxx
RX_Process very fast incrementing count 0 xxx
RX_Start 0 3 4 069
DMR_Lost 2 3 1 001
Here I see few xmit of few seconds. The last one started, and the hotspot didn't received any data for too long and trigger the transmission loss event (according to the log + the DMR_Lost x x x 001 on screen).
kd2lh wrote:
Sun Jan 05, 2020 3:32 pm
Here's a second one of these:

M: 2020-01-05 15:32:34.873 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:32:40.165 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 5.0 seconds, BER: 1.4%
M: 2020-01-05 15:32:43.414 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:32:48.405 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:42:42.666 DMR Slot 2, received network voice header from N3MAT to TG 31377
M: 2020-01-05 15:42:43.318 DMR Talker Alias (Data Format 1, Received 6/11 char): 'N3MAT '
M: 2020-01-05 15:42:43.318 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-05 15:42:43.319 0000: 04 00 56 4E 33 4D 41 54 20 *..VN3MAT *
M: 2020-01-05 15:42:43.560 DMR Slot 2, received network end of voice transmission from N3MAT to TG 31377, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:44:40.425 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:44:40.678 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 0.0 seconds, BER: 0.0%


GD77 display:
blinking K 0x1
Q 0x3
Set_Status incrementing 000 to 255
RX_Process 0 fast incrementing 0 255
RX_Start 0 3 4 230
DMR_Lost 2 3 1 002
Same, a gap of 253ms without data (or less), probably.

kd2lh wrote:
Sun Jan 05, 2020 3:32 pm

Note that the next time I transmit to the GD77, nothing is forwarded to Brandmeister. The second time I transmit to the GD77, it is forwarded (in this example, a parrot call to private id 9990).

Here's what was logged:

M: 2020-01-05 15:42:43.319 0000: 04 00 56 4E 33 4D 41 54 20 *..VN3MAT *
M: 2020-01-05 15:42:43.560 DMR Slot 2, received network end of voice transmission from N3MAT to TG 31377, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:44:40.425 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:44:40.678 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 0.0 seconds, BER: 0.0%
M: 2020-01-05 15:54:30.596 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.183 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.720 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.778 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.078 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.105 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.440 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.498 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.801 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.861 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.117 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.217 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.518 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.576 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.870 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.939 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.239 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.299 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.600 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.626 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.958 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.017 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.316 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.382 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:56.083 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:54:58.872 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 2.5 seconds, BER: 1.3%
M: 2020-01-05 15:55:02.120 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:55:04.589 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 2.6 seconds, 4% packet loss, BER: 0.0%
Yeah, again DMR Lost event. Hmmm, maybe I need to increase the timeout value.
BTW, what is the transceiver you're using, and is your MMDVMHost config file has TXOffset and RXOffset set to 0 ?
Extra question, if you're using a GD-77 as transceiver, do you run the latest firmware ?

Thanks for all the informations, that's really useful.
---
Daniel
73 de Daniel.

User avatar
F1RMB
Posts: 404
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France
Contact:

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Sun Jan 05, 2020 4:14 pm

F1RMB wrote:
Sun Jan 05, 2020 4:11 pm
kd2lh wrote:
Sun Jan 05, 2020 3:32 pm
Here's a first interesting anomaly. No local RF activity from my DMR radio, but I saw the red receive light come on at the time this message came out:

M: 2020-01-05 15:25:33.546 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:25:42.343 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 8.6 seconds, BER: 1.8%
M: 2020-01-05 15:25:51.412 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:25:57.257 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 5.8 seconds, BER: 1.4%
M: 2020-01-05 15:26:00.536 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:26:06.244 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:26:17.739 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:26:22.545 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 4.7 seconds, BER: 1.4%
M: 2020-01-05 15:27:15.185 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-05 15:27:15.690 DMR Slot 2, RF voice transmission lost from KD2LH to TG 98977, 0.0 seconds, BER: 0.0%


Blinking "K" 0x1
Q "0x3"
Set_Status running incrementing count xxx
RX_Process very fast incrementing count 0 xxx
RX_Start 0 3 4 069
DMR_Lost 2 3 1 001
Here I see few xmit of few seconds. The last one started, and the hotspot didn't received any data for too long and trigger the transmission loss event (according to the log + the DMR_Lost x x x 001 on screen).
kd2lh wrote:
Sun Jan 05, 2020 3:32 pm
Here's a second one of these:

M: 2020-01-05 15:32:34.873 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:32:40.165 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 5.0 seconds, BER: 1.4%
M: 2020-01-05 15:32:43.414 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:32:48.405 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:42:42.666 DMR Slot 2, received network voice header from N3MAT to TG 31377
M: 2020-01-05 15:42:43.318 DMR Talker Alias (Data Format 1, Received 6/11 char): 'N3MAT '
M: 2020-01-05 15:42:43.318 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-05 15:42:43.319 0000: 04 00 56 4E 33 4D 41 54 20 *..VN3MAT *
M: 2020-01-05 15:42:43.560 DMR Slot 2, received network end of voice transmission from N3MAT to TG 31377, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:44:40.425 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:44:40.678 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 0.0 seconds, BER: 0.0%


GD77 display:
blinking K 0x1
Q 0x3
Set_Status incrementing 000 to 255
RX_Process 0 fast incrementing 0 255
RX_Start 0 3 4 230
DMR_Lost 2 3 1 002
Same, a gap of 253ms without data (or less), probably.

kd2lh wrote:
Sun Jan 05, 2020 3:32 pm

Note that the next time I transmit to the GD77, nothing is forwarded to Brandmeister. The second time I transmit to the GD77, it is forwarded (in this example, a parrot call to private id 9990).

Here's what was logged:

M: 2020-01-05 15:42:43.319 0000: 04 00 56 4E 33 4D 41 54 20 *..VN3MAT *
M: 2020-01-05 15:42:43.560 DMR Slot 2, received network end of voice transmission from N3MAT to TG 31377, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-05 15:44:40.425 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:44:40.678 DMR Slot 2, RF voice transmission lost from KD2LH to 9990, 0.0 seconds, BER: 0.0%
M: 2020-01-05 15:54:30.596 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.183 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.720 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:31.778 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.078 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.105 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.440 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.498 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.801 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:32.861 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.117 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.217 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.518 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.576 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.870 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:33.939 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.239 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.299 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.600 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.626 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:34.958 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.017 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.316 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:35.382 DMR Slot 2, RF user 0 rejected
M: 2020-01-05 15:54:56.083 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-05 15:54:58.872 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 2.5 seconds, BER: 1.3%
M: 2020-01-05 15:55:02.120 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2020-01-05 15:55:04.589 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 2.6 seconds, 4% packet loss, BER: 0.0%
Yeah, again DMR Lost event. Hmmm, maybe I need to increase the timeout value.
BTW, what is the transceiver you're using, and is you MMDVMHost config file has TXOffset and RXOffset set to 0 ?
Extra question, if you're using a GD-77 as transceiver, do you run the latest firmware ?

Thanks for all the informations, that's really useful.
---
Daniel
About the last case, it's because ID is equal to zero, but that's another (known) bug ;)

Here, I want to fix the TX lock-up, on Pi-Star, and timeouts issued by MMDVMHost, first (then, look at the preBeta BlueDV + TGIF problem, since I've made large changes in the code, maybe this software have some special way to implement MMDVM support).

Cheers.
---
Daniel
73 de Daniel.

User avatar
kd2lh
Posts: 171
Joined: Mon Dec 02, 2019 2:44 pm

Re: Hotspot mode - Apparently stuck in TX

Post by kd2lh » Sun Jan 05, 2020 5:03 pm

Yes - all these recent tests have the RXOffset and TXOffset at 0 (zero).

Could the incidence of all this be related to squelch setting? I have it set roughly midway. Note that I'm on a reasonably isolated frequency for hotspot operation (one that I alternately share with a JumboSpot on the same frequency). The JumboSpot never indicates any similar RF events.

Marc

Post Reply