Hotspot mode - Apparently stuck in TX

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

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Thu Jan 02, 2020 4:28 pm

kd2lh wrote:
Thu Jan 02, 2020 4:01 pm
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.
Just to be sure, your Pi-Star is configured as Simplex, and RXOffset & TXOffset are set to zero, right ?

Cheers.
---
Daniel

User avatar
KU4ZD
Posts: 127
Joined: Sat Nov 16, 2019 2:47 pm
Location: Council Bluffs, Iowa
Contact:

Re: Hotspot mode - Apparently stuck in TX

Post by KU4ZD » Thu Jan 02, 2020 5:45 pm

I just tried BlueDV on Android and I agree, at least on Brandmeister
it doesnt seem to have the same problem but the Android is a older
version than the beta on my pc and I was using the TGIF network on my pc
F1RMB wrote:
Thu Jan 02, 2020 3:58 pm
F1RMB wrote:
Thu Jan 02, 2020 3:56 pm
KU4ZD wrote:
Thu Jan 02, 2020 3:53 pm
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

Just grabbed last heard on BM
Screenshot at 2020-01-02 17-02-57.png

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

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Thu Jan 02, 2020 6:01 pm

Hi Mike,
KU4ZD wrote:
Thu Jan 02, 2020 5:45 pm
I just tried BlueDV on Android and I agree, at least on Brandmeister
it doesnt seem to have the same problem but the Android is a older
version than the beta on my pc and I was using the TGIF network on my pc
F1RMB wrote:
Thu Jan 02, 2020 3:58 pm
F1RMB wrote:
Thu Jan 02, 2020 3:56 pm


Stangely, BlueDV on Android doesn't have this problem...
Screenshot at 2020-01-02 16-57-17.png

Just grabbed last heard on BM
Screenshot at 2020-01-02 17-02-57.png
Okay, I'll try to test the Windows beta. About TGIF, can you send me (by PM) how to connect, etc, to that network ?

Cheers.
---
Daniel

User avatar
YT5HOK
Posts: 213
Joined: Sat Nov 16, 2019 11:36 am
Location: Belgrade, KN04FR

Re: Hotspot mode - Apparently stuck in TX

Post by YT5HOK » Thu Jan 02, 2020 7:43 pm

It's been only three hours, but its looking good. Running GD77 hotspot on MMDVMHost.exe on PC.

Code: Select all

I: 2020-01-02 17:33:28.996 This software is for use on amateur radio networks only,
I: 2020-01-02 17:33:28.996 it is to be used for educational purposes only. Its use on
I: 2020-01-02 17:33:28.997 commercial networks is strictly prohibited.
I: 2020-01-02 17:33:28.997 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-01-02 17:33:28.997 MMDVMHost-20190131 is starting
M: 2020-01-02 17:33:28.997 Built 07:59:39 Nov 13 2019 (GitID #0b9c1b1)
I: 2020-01-02 17:33:28.997 General Parameters
I: 2020-01-02 17:33:28.997     Callsign: YT5HOK
I: 2020-01-02 17:33:28.997     Id: 2200183
I: 2020-01-02 17:33:28.997     Duplex: no
I: 2020-01-02 17:33:28.997     Timeout: 600s
I: 2020-01-02 17:33:28.997     D-Star: disabled
I: 2020-01-02 17:33:28.997     DMR: enabled
I: 2020-01-02 17:33:28.997     YSF: disabled
I: 2020-01-02 17:33:28.997     P25: disabled
I: 2020-01-02 17:33:28.997     NXDN: disabled
I: 2020-01-02 17:33:28.998     POCSAG: disabled
I: 2020-01-02 17:33:28.998 Modem Parameters
I: 2020-01-02 17:33:28.998     Port: \\.\COM3
I: 2020-01-02 17:33:28.998     Protocol: uart
I: 2020-01-02 17:33:28.998     RX Invert: no
I: 2020-01-02 17:33:28.998     TX Invert: yes
I: 2020-01-02 17:33:28.998     PTT Invert: no
I: 2020-01-02 17:33:28.998     TX Delay: 100ms
I: 2020-01-02 17:33:28.998     RX Offset: 0Hz
I: 2020-01-02 17:33:28.999     TX Offset: 0Hz
I: 2020-01-02 17:33:28.999     RX DC Offset: 0
I: 2020-01-02 17:33:28.999     TX DC Offset: 0
I: 2020-01-02 17:33:28.999     RF Level: 100.0%
I: 2020-01-02 17:33:28.999     DMR Delay: 0 (0.0ms)
I: 2020-01-02 17:33:28.999     RX Level: 50.0%
I: 2020-01-02 17:33:28.999     CW Id TX Level: 50.0%
I: 2020-01-02 17:33:28.999     D-Star TX Level: 50.0%
I: 2020-01-02 17:33:28.999     DMR TX Level: 50.0%
I: 2020-01-02 17:33:28.999     YSF TX Level: 50.0%
I: 2020-01-02 17:33:28.999     P25 TX Level: 50.0%
I: 2020-01-02 17:33:29.000     NXDN TX Level: 50.0%
I: 2020-01-02 17:33:29.000     POCSAG TX Level: 50.0%
I: 2020-01-02 17:33:29.000     RX Frequency: 434500000Hz (434500000Hz)
I: 2020-01-02 17:33:29.000     TX Frequency: 434500000Hz (434500000Hz)
M: 2020-01-02 17:33:29.000 Opening the MMDVM
I: 2020-01-02 17:33:31.027 MMDVM protocol version: 1, description: OpenGD77 Hotspot v0.0.72 GitID #869df60
I: 2020-01-02 17:33:31.080 Display Parameters
I: 2020-01-02 17:33:31.080     Type: None
W: 2020-01-02 17:33:31.080 No valid display found, disabling
I: 2020-01-02 17:33:31.081 DMR Network Parameters
I: 2020-01-02 17:33:31.081     Address: 80.250.21.206
I: 2020-01-02 17:33:31.081     Port: 62031
I: 2020-01-02 17:33:31.081     Local: random
I: 2020-01-02 17:33:31.082     Jitter: 300ms
I: 2020-01-02 17:33:31.082     Slot 1: disabled
I: 2020-01-02 17:33:31.082     Slot 2: enabled
I: 2020-01-02 17:33:31.082     Mode Hang: 3s
I: 2020-01-02 17:33:31.086 Info Parameters
I: 2020-01-02 17:33:31.086     Callsign: YT5HOK
I: 2020-01-02 17:33:31.087     RX Frequency: 434500000Hz
I: 2020-01-02 17:33:31.087     TX Frequency: 434500000Hz
I: 2020-01-02 17:33:31.087     Power: 1W
I: 2020-01-02 17:33:31.087     Latitude: 44.795200deg N
I: 2020-01-02 17:33:31.088     Longitude: 20.426300deg E
I: 2020-01-02 17:33:31.088     Height: 0m
I: 2020-01-02 17:33:31.089     Location: "Belgrade, KN04"
I: 2020-01-02 17:33:31.090     Description: "OpenGD77"
I: 2020-01-02 17:33:31.092     URL: "https://www.qrz.com/db/yt5hok/"
M: 2020-01-02 17:33:31.093 DMR, Opening DMR Network
I: 2020-01-02 17:33:31.094 RSSI
I: 2020-01-02 17:33:31.095     Mapping File: RSSI.dat
I: 2020-01-02 17:33:31.104 Loaded 14 RSSI data mapping points from RSSI.dat
I: 2020-01-02 17:33:31.108 DMR Id Lookups
I: 2020-01-02 17:33:31.109     File: DMRIds.dat
I: 2020-01-02 17:33:31.110     Reload: 24 hours
I: 2020-01-02 17:33:31.233 Loaded 148841 Ids to the DMR callsign lookup table
I: 2020-01-02 17:33:31.233 DMR RF Parameters
I: 2020-01-02 17:33:31.238     Id: 2200183
I: 2020-01-02 17:33:31.240     Color Code: 1
I: 2020-01-02 17:33:31.244     Self Only: no
I: 2020-01-02 17:33:31.245     Embedded LC Only: no
I: 2020-01-02 17:33:31.239 Started the DMR Id lookup reload thread
I: 2020-01-02 17:33:31.245     Dump Talker Alias Data: yes
I: 2020-01-02 17:33:31.247     Prefixes: 0
I: 2020-01-02 17:33:31.248     Call Hang: 3s
I: 2020-01-02 17:33:31.248     TX Hang: 3s
I: 2020-01-02 17:33:31.251     Mode Hang: 10s
M: 2020-01-02 17:33:31.254 MMDVMHost-20190131 is running
D: 2020-01-02 17:33:41.671 DMR, Sending authorisation
D: 2020-01-02 17:33:41.711 DMR, Sending configuration
M: 2020-01-02 17:33:41.760 DMR, Logged into the master successfully
D: 2020-01-02 18:55:34.437 FindWithName =YT2FA ZARKO
M: 2020-01-02 18:55:34.437 DMR Slot 2, received network voice header from YT2FA to TG 220
M: 2020-01-02 18:55:34.989 DMR Talker Alias (Data Format 1, Received 6/21 char): 'YT2FA '
M: 2020-01-02 18:55:34.989 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 18:55:34.990 0000:  04 00 6A 59 54 32 46 41 20                         *..jYT2FA *
M: 2020-01-02 18:55:35.111 DMR Slot 2, received network end of voice transmission, 0.8 seconds, 0% packet loss, BER: 0.1%
M: 2020-01-02 18:55:39.810 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 18:55:40.877 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:14:40.647 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:14:55.438 DMR Slot 2, RF user 0 rejected
D: 2020-01-02 19:14:55.439 FindWithName =YT5HOK MARKO
M: 2020-01-02 19:14:55.441 DMR Slot 2, received network voice header from YT5HOK to TG 220011
M: 2020-01-02 19:14:56.188 DMR Talker Alias (Data Format 1, Received 6/12 char): 'YT5HOK'
M: 2020-01-02 19:14:56.188 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:14:56.190 0000:  04 00 58 59 54 35 48 4F 4B                         *..XYT5HOK*
M: 2020-01-02 19:14:56.923 DMR Talker Alias (Data Format 1, Received 12/12 char): 'YT5HOK Marko'
M: 2020-01-02 19:14:56.923 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:14:56.925 0000:  05 00 20 4D 61 72 6B 6F 00                         *.. Marko.*
M: 2020-01-02 19:14:58.470 DMR Slot 2, received network end of voice transmission, 3.0 seconds, 0% packet loss, BER: 0.0%
D: 2020-01-02 19:23:32.356 FindWithName =YU4DHM DAMIR
M: 2020-01-02 19:23:32.356 DMR Slot 2, received network voice header from YU4DHM to TG 220
M: 2020-01-02 19:23:33.057 DMR Talker Alias (Data Format 1, Received 6/22 char): 'YU4DHM'
M: 2020-01-02 19:23:33.057 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:23:33.073 0000:  04 00 6C 59 55 34 44 48 4D                         *..lYU4DHM*
M: 2020-01-02 19:23:33.770 DMR Talker Alias (Data Format 1, Received 13/22 char): 'YU4DHM DMR ID'
M: 2020-01-02 19:23:33.770 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:23:33.772 0000:  05 00 20 44 4D 52 20 49 44                         *.. DMR ID*
M: 2020-01-02 19:23:34.236 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 3% packet loss, BER: 0.0%
M: 2020-01-02 19:23:34.930 DMR Slot 2, received RF voice header from YU4DHM to TG 220
M: 2020-01-02 19:23:36.823 DMR Slot 2, received RF end of voice transmission, 0.0 seconds, BER: 0.0%
M: 2020-01-02 19:23:37.791 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:23:38.313 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:23:38.580 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:23:39.094 DMR Slot 2, RF user 0 rejected
D: 2020-01-02 19:27:43.076 Preamble CSBK
D: 2020-01-02 19:27:43.076 0000:  BD 00 C0 07 00 00 DC 21 92 A3 24 1C                *.......!..$.*
M: 2020-01-02 19:27:43.092 DMR Slot 2, received network Data Preamble CSBK (7 to follow) from YU7PXH to TG 220
D: 2020-01-02 19:27:43.133 Preamble CSBK
D: 2020-01-02 19:27:43.133 0000:  BD 00 C0 06 00 00 DC 21 92 A3 9C 7D                *.......!...}*
M: 2020-01-02 19:27:43.136 DMR Slot 2, received network Data Preamble CSBK (6 to follow) from YU7PXH to TG 220
D: 2020-01-02 19:27:43.220 DMR, Unconfirmed Data Header
D: 2020-01-02 19:27:43.220 0000:  82 4A 00 00 DC 21 92 A3 85 00 9F 28                *.J...!.....(*
M: 2020-01-02 19:27:43.222 DMR Slot 2, received network data header from YU7PXH to TG 220, 5 blocks
M: 2020-01-02 19:27:43.517 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:43.569 DMR Slot 2, ended network data transmission
M: 2020-01-02 19:27:44.022 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:44.293 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:44.554 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:45.099 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:45.363 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:45.638 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.126 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.175 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.438 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.707 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.899 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.969 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:47.231 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:47.491 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:47.771 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:48.028 DMR Slot 2, RF user 0 rejected
D: 2020-01-02 19:33:11.638 FindWithName =YT5HOK MARKO
M: 2020-01-02 19:33:11.638 DMR Slot 2, received network voice header from YT5HOK to TG 220011
M: 2020-01-02 19:33:12.188 DMR Talker Alias (Data Format 1, Received 6/12 char): 'YT5HOK'
M: 2020-01-02 19:33:12.188 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:33:12.191 0000:  04 00 58 59 54 35 48 4F 4B                         *..XYT5HOK*
M: 2020-01-02 19:33:12.924 DMR Talker Alias (Data Format 1, Received 12/12 char): 'YT5HOK Marko'
M: 2020-01-02 19:33:12.924 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:33:12.926 0000:  05 00 20 4D 61 72 6B 6F 00                         *.. Marko.*
M: 2020-01-02 19:33:14.846 DMR Slot 2, received network end of voice transmission, 3.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 19:33:26.479 DMR Slot 2, received RF voice header from YT5HOK to TG 220011
D: 2020-01-02 19:33:26.553 DMR Slot 2, audio sequence no. 0, errs: 3/141 (2.1%)
D: 2020-01-02 19:33:26.618 DMR Slot 2, audio sequence no. 1, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:26.669 DMR Slot 2, audio sequence no. 2, errs: 4/141 (2.8%)
D: 2020-01-02 19:33:26.735 DMR Slot 2, audio sequence no. 3, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:26.753 DMR Slot 2, audio sequence no. 4, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:26.853 DMR Slot 2, audio sequence no. 5, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:26.920 DMR Slot 2, audio sequence no. 0, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:26.969 DMR Slot 2, audio sequence no. 1, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.019 DMR Slot 2, audio sequence no. 2, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.092 DMR Slot 2, audio sequence no. 3, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:27.151 DMR Slot 2, audio sequence no. 4, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:27.218 DMR Slot 2, audio sequence no. 5, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:27.269 DMR Slot 2, audio sequence no. 0, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:27.286 DMR Slot 2, audio sequence no. 1, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.401 DMR Slot 2, audio sequence no. 2, errs: 7/141 (5.0%)
D: 2020-01-02 19:33:27.453 DMR Slot 2, audio sequence no. 3, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:27.519 DMR Slot 2, audio sequence no. 4, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.552 DMR Slot 2, audio sequence no. 5, errs: 3/141 (2.1%)
M: 2020-01-02 19:33:27.826 DMR Slot 2, received RF end of voice transmission, 1.1 seconds, BER: 1.3%
D: 2020-01-02 19:33:35.202 FindWithName =YT5HOK MARKO
M: 2020-01-02 19:33:35.202 DMR Slot 2, received network voice header from YT5HOK to TG 220011
M: 2020-01-02 19:33:35.871 DMR Talker Alias (Data Format 1, Received 6/12 char): 'YT5HOK'
M: 2020-01-02 19:33:35.871 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:33:35.874 0000:  04 00 58 59 54 35 48 4F 4B                         *..XYT5HOK*
M: 2020-01-02 19:33:36.595 DMR Talker Alias (Data Format 1, Received 12/12 char): 'YT5HOK Marko'
M: 2020-01-02 19:33:36.595 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:33:36.597 0000:  05 00 20 4D 61 72 6B 6F 00                         *.. Marko.*
M: 2020-01-02 19:33:41.377 DMR Slot 2, received network end of voice transmission, 6.2 seconds, 0% packet loss, BER: 0.0%
By the log, it should have been stuck many times, but didn't. Nothing indicated on the display it might have been stuck and it always received transmission incoming from the net and transmitted to HT. I'm using another hotspot and another HT to monitor and initiate traffic.
Didn't yet try running GD77 hotspot on Raspberry Pi 3A+, which I use too for testing. I didn't ever try BlueDV, but I have it, if you need me to try.

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

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Thu Jan 02, 2020 8:07 pm

Hi Marko,
YT5HOK wrote:
Thu Jan 02, 2020 7:43 pm
It's been only three hours, but its looking good. Running GD77 hotspot on MMDVMHost.exe on PC.

Code: Select all

I: 2020-01-02 17:33:28.996 This software is for use on amateur radio networks only,
I: 2020-01-02 17:33:28.996 it is to be used for educational purposes only. Its use on
I: 2020-01-02 17:33:28.997 commercial networks is strictly prohibited.
I: 2020-01-02 17:33:28.997 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-01-02 17:33:28.997 MMDVMHost-20190131 is starting
M: 2020-01-02 17:33:28.997 Built 07:59:39 Nov 13 2019 (GitID #0b9c1b1)
I: 2020-01-02 17:33:28.997 General Parameters
I: 2020-01-02 17:33:28.997     Callsign: YT5HOK
I: 2020-01-02 17:33:28.997     Id: 2200183
I: 2020-01-02 17:33:28.997     Duplex: no
I: 2020-01-02 17:33:28.997     Timeout: 600s
I: 2020-01-02 17:33:28.997     D-Star: disabled
I: 2020-01-02 17:33:28.997     DMR: enabled
I: 2020-01-02 17:33:28.997     YSF: disabled
I: 2020-01-02 17:33:28.997     P25: disabled
I: 2020-01-02 17:33:28.997     NXDN: disabled
I: 2020-01-02 17:33:28.998     POCSAG: disabled
I: 2020-01-02 17:33:28.998 Modem Parameters
I: 2020-01-02 17:33:28.998     Port: \\.\COM3
I: 2020-01-02 17:33:28.998     Protocol: uart
I: 2020-01-02 17:33:28.998     RX Invert: no
I: 2020-01-02 17:33:28.998     TX Invert: yes
I: 2020-01-02 17:33:28.998     PTT Invert: no
I: 2020-01-02 17:33:28.998     TX Delay: 100ms
I: 2020-01-02 17:33:28.998     RX Offset: 0Hz
I: 2020-01-02 17:33:28.999     TX Offset: 0Hz
I: 2020-01-02 17:33:28.999     RX DC Offset: 0
I: 2020-01-02 17:33:28.999     TX DC Offset: 0
I: 2020-01-02 17:33:28.999     RF Level: 100.0%
I: 2020-01-02 17:33:28.999     DMR Delay: 0 (0.0ms)
I: 2020-01-02 17:33:28.999     RX Level: 50.0%
I: 2020-01-02 17:33:28.999     CW Id TX Level: 50.0%
I: 2020-01-02 17:33:28.999     D-Star TX Level: 50.0%
I: 2020-01-02 17:33:28.999     DMR TX Level: 50.0%
I: 2020-01-02 17:33:28.999     YSF TX Level: 50.0%
I: 2020-01-02 17:33:28.999     P25 TX Level: 50.0%
I: 2020-01-02 17:33:29.000     NXDN TX Level: 50.0%
I: 2020-01-02 17:33:29.000     POCSAG TX Level: 50.0%
I: 2020-01-02 17:33:29.000     RX Frequency: 434500000Hz (434500000Hz)
I: 2020-01-02 17:33:29.000     TX Frequency: 434500000Hz (434500000Hz)
M: 2020-01-02 17:33:29.000 Opening the MMDVM
I: 2020-01-02 17:33:31.027 MMDVM protocol version: 1, description: OpenGD77 Hotspot v0.0.72 GitID #869df60
I: 2020-01-02 17:33:31.080 Display Parameters
I: 2020-01-02 17:33:31.080     Type: None
W: 2020-01-02 17:33:31.080 No valid display found, disabling
I: 2020-01-02 17:33:31.081 DMR Network Parameters
I: 2020-01-02 17:33:31.081     Address: 80.250.21.206
I: 2020-01-02 17:33:31.081     Port: 62031
I: 2020-01-02 17:33:31.081     Local: random
I: 2020-01-02 17:33:31.082     Jitter: 300ms
I: 2020-01-02 17:33:31.082     Slot 1: disabled
I: 2020-01-02 17:33:31.082     Slot 2: enabled
I: 2020-01-02 17:33:31.082     Mode Hang: 3s
I: 2020-01-02 17:33:31.086 Info Parameters
I: 2020-01-02 17:33:31.086     Callsign: YT5HOK
I: 2020-01-02 17:33:31.087     RX Frequency: 434500000Hz
I: 2020-01-02 17:33:31.087     TX Frequency: 434500000Hz
I: 2020-01-02 17:33:31.087     Power: 1W
I: 2020-01-02 17:33:31.087     Latitude: 44.795200deg N
I: 2020-01-02 17:33:31.088     Longitude: 20.426300deg E
I: 2020-01-02 17:33:31.088     Height: 0m
I: 2020-01-02 17:33:31.089     Location: "Belgrade, KN04"
I: 2020-01-02 17:33:31.090     Description: "OpenGD77"
I: 2020-01-02 17:33:31.092     URL: "https://www.qrz.com/db/yt5hok/"
M: 2020-01-02 17:33:31.093 DMR, Opening DMR Network
I: 2020-01-02 17:33:31.094 RSSI
I: 2020-01-02 17:33:31.095     Mapping File: RSSI.dat
I: 2020-01-02 17:33:31.104 Loaded 14 RSSI data mapping points from RSSI.dat
I: 2020-01-02 17:33:31.108 DMR Id Lookups
I: 2020-01-02 17:33:31.109     File: DMRIds.dat
I: 2020-01-02 17:33:31.110     Reload: 24 hours
I: 2020-01-02 17:33:31.233 Loaded 148841 Ids to the DMR callsign lookup table
I: 2020-01-02 17:33:31.233 DMR RF Parameters
I: 2020-01-02 17:33:31.238     Id: 2200183
I: 2020-01-02 17:33:31.240     Color Code: 1
I: 2020-01-02 17:33:31.244     Self Only: no
I: 2020-01-02 17:33:31.245     Embedded LC Only: no
I: 2020-01-02 17:33:31.239 Started the DMR Id lookup reload thread
I: 2020-01-02 17:33:31.245     Dump Talker Alias Data: yes
I: 2020-01-02 17:33:31.247     Prefixes: 0
I: 2020-01-02 17:33:31.248     Call Hang: 3s
I: 2020-01-02 17:33:31.248     TX Hang: 3s
I: 2020-01-02 17:33:31.251     Mode Hang: 10s
M: 2020-01-02 17:33:31.254 MMDVMHost-20190131 is running
D: 2020-01-02 17:33:41.671 DMR, Sending authorisation
D: 2020-01-02 17:33:41.711 DMR, Sending configuration
M: 2020-01-02 17:33:41.760 DMR, Logged into the master successfully
D: 2020-01-02 18:55:34.437 FindWithName =YT2FA ZARKO
M: 2020-01-02 18:55:34.437 DMR Slot 2, received network voice header from YT2FA to TG 220
M: 2020-01-02 18:55:34.989 DMR Talker Alias (Data Format 1, Received 6/21 char): 'YT2FA '
M: 2020-01-02 18:55:34.989 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 18:55:34.990 0000:  04 00 6A 59 54 32 46 41 20                         *..jYT2FA *
M: 2020-01-02 18:55:35.111 DMR Slot 2, received network end of voice transmission, 0.8 seconds, 0% packet loss, BER: 0.1%
M: 2020-01-02 18:55:39.810 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 18:55:40.877 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:14:40.647 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:14:55.438 DMR Slot 2, RF user 0 rejected
D: 2020-01-02 19:14:55.439 FindWithName =YT5HOK MARKO
M: 2020-01-02 19:14:55.441 DMR Slot 2, received network voice header from YT5HOK to TG 220011
M: 2020-01-02 19:14:56.188 DMR Talker Alias (Data Format 1, Received 6/12 char): 'YT5HOK'
M: 2020-01-02 19:14:56.188 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:14:56.190 0000:  04 00 58 59 54 35 48 4F 4B                         *..XYT5HOK*
M: 2020-01-02 19:14:56.923 DMR Talker Alias (Data Format 1, Received 12/12 char): 'YT5HOK Marko'
M: 2020-01-02 19:14:56.923 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:14:56.925 0000:  05 00 20 4D 61 72 6B 6F 00                         *.. Marko.*
M: 2020-01-02 19:14:58.470 DMR Slot 2, received network end of voice transmission, 3.0 seconds, 0% packet loss, BER: 0.0%
D: 2020-01-02 19:23:32.356 FindWithName =YU4DHM DAMIR
M: 2020-01-02 19:23:32.356 DMR Slot 2, received network voice header from YU4DHM to TG 220
M: 2020-01-02 19:23:33.057 DMR Talker Alias (Data Format 1, Received 6/22 char): 'YU4DHM'
M: 2020-01-02 19:23:33.057 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:23:33.073 0000:  04 00 6C 59 55 34 44 48 4D                         *..lYU4DHM*
M: 2020-01-02 19:23:33.770 DMR Talker Alias (Data Format 1, Received 13/22 char): 'YU4DHM DMR ID'
M: 2020-01-02 19:23:33.770 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:23:33.772 0000:  05 00 20 44 4D 52 20 49 44                         *.. DMR ID*
M: 2020-01-02 19:23:34.236 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 3% packet loss, BER: 0.0%
M: 2020-01-02 19:23:34.930 DMR Slot 2, received RF voice header from YU4DHM to TG 220
M: 2020-01-02 19:23:36.823 DMR Slot 2, received RF end of voice transmission, 0.0 seconds, BER: 0.0%
M: 2020-01-02 19:23:37.791 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:23:38.313 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:23:38.580 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:23:39.094 DMR Slot 2, RF user 0 rejected
D: 2020-01-02 19:27:43.076 Preamble CSBK
D: 2020-01-02 19:27:43.076 0000:  BD 00 C0 07 00 00 DC 21 92 A3 24 1C                *.......!..$.*
M: 2020-01-02 19:27:43.092 DMR Slot 2, received network Data Preamble CSBK (7 to follow) from YU7PXH to TG 220
D: 2020-01-02 19:27:43.133 Preamble CSBK
D: 2020-01-02 19:27:43.133 0000:  BD 00 C0 06 00 00 DC 21 92 A3 9C 7D                *.......!...}*
M: 2020-01-02 19:27:43.136 DMR Slot 2, received network Data Preamble CSBK (6 to follow) from YU7PXH to TG 220
D: 2020-01-02 19:27:43.220 DMR, Unconfirmed Data Header
D: 2020-01-02 19:27:43.220 0000:  82 4A 00 00 DC 21 92 A3 85 00 9F 28                *.J...!.....(*
M: 2020-01-02 19:27:43.222 DMR Slot 2, received network data header from YU7PXH to TG 220, 5 blocks
M: 2020-01-02 19:27:43.517 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:43.569 DMR Slot 2, ended network data transmission
M: 2020-01-02 19:27:44.022 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:44.293 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:44.554 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:45.099 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:45.363 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:45.638 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.126 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.175 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.438 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.707 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.899 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:46.969 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:47.231 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:47.491 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:47.771 DMR Slot 2, RF user 0 rejected
M: 2020-01-02 19:27:48.028 DMR Slot 2, RF user 0 rejected
D: 2020-01-02 19:33:11.638 FindWithName =YT5HOK MARKO
M: 2020-01-02 19:33:11.638 DMR Slot 2, received network voice header from YT5HOK to TG 220011
M: 2020-01-02 19:33:12.188 DMR Talker Alias (Data Format 1, Received 6/12 char): 'YT5HOK'
M: 2020-01-02 19:33:12.188 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:33:12.191 0000:  04 00 58 59 54 35 48 4F 4B                         *..XYT5HOK*
M: 2020-01-02 19:33:12.924 DMR Talker Alias (Data Format 1, Received 12/12 char): 'YT5HOK Marko'
M: 2020-01-02 19:33:12.924 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:33:12.926 0000:  05 00 20 4D 61 72 6B 6F 00                         *.. Marko.*
M: 2020-01-02 19:33:14.846 DMR Slot 2, received network end of voice transmission, 3.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 19:33:26.479 DMR Slot 2, received RF voice header from YT5HOK to TG 220011
D: 2020-01-02 19:33:26.553 DMR Slot 2, audio sequence no. 0, errs: 3/141 (2.1%)
D: 2020-01-02 19:33:26.618 DMR Slot 2, audio sequence no. 1, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:26.669 DMR Slot 2, audio sequence no. 2, errs: 4/141 (2.8%)
D: 2020-01-02 19:33:26.735 DMR Slot 2, audio sequence no. 3, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:26.753 DMR Slot 2, audio sequence no. 4, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:26.853 DMR Slot 2, audio sequence no. 5, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:26.920 DMR Slot 2, audio sequence no. 0, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:26.969 DMR Slot 2, audio sequence no. 1, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.019 DMR Slot 2, audio sequence no. 2, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.092 DMR Slot 2, audio sequence no. 3, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:27.151 DMR Slot 2, audio sequence no. 4, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:27.218 DMR Slot 2, audio sequence no. 5, errs: 0/141 (0.0%)
D: 2020-01-02 19:33:27.269 DMR Slot 2, audio sequence no. 0, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:27.286 DMR Slot 2, audio sequence no. 1, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.401 DMR Slot 2, audio sequence no. 2, errs: 7/141 (5.0%)
D: 2020-01-02 19:33:27.453 DMR Slot 2, audio sequence no. 3, errs: 2/141 (1.4%)
D: 2020-01-02 19:33:27.519 DMR Slot 2, audio sequence no. 4, errs: 1/141 (0.7%)
D: 2020-01-02 19:33:27.552 DMR Slot 2, audio sequence no. 5, errs: 3/141 (2.1%)
M: 2020-01-02 19:33:27.826 DMR Slot 2, received RF end of voice transmission, 1.1 seconds, BER: 1.3%
D: 2020-01-02 19:33:35.202 FindWithName =YT5HOK MARKO
M: 2020-01-02 19:33:35.202 DMR Slot 2, received network voice header from YT5HOK to TG 220011
M: 2020-01-02 19:33:35.871 DMR Talker Alias (Data Format 1, Received 6/12 char): 'YT5HOK'
M: 2020-01-02 19:33:35.871 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 19:33:35.874 0000:  04 00 58 59 54 35 48 4F 4B                         *..XYT5HOK*
M: 2020-01-02 19:33:36.595 DMR Talker Alias (Data Format 1, Received 12/12 char): 'YT5HOK Marko'
M: 2020-01-02 19:33:36.595 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 19:33:36.597 0000:  05 00 20 4D 61 72 6B 6F 00                         *.. Marko.*
M: 2020-01-02 19:33:41.377 DMR Slot 2, received network end of voice transmission, 6.2 seconds, 0% packet loss, BER: 0.0%
By the log, it should have been stuck many times, but didn't. Nothing indicated on the display it might have been stuck and it always received transmission incoming from the net and transmitted to HT. I'm using another hotspot and another HT to monitor and initiate traffic.
Didn't yet try running GD77 hotspot on Raspberry Pi 3A+, which I use too for testing. I didn't ever try BlueDV, but I have it, if you need me to try.
Okay, thank you for the test. I've been running it on a Pi-3 A+ for ~6h without any problem, but mostly on RX.

Cheers.
---
Daniel

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

Re: Hotspot mode - Apparently stuck in TX

Post by kd2lh » Thu Jan 02, 2020 9:45 pm

My PiStar is configured Simplex. I DO use a frequency offset (-150hz). It's a Pi Zero W running 4.1.6 PiStar with updates. It's configured for slot 2.

in the past, I've seen the missed packet happen in other sequences including when the voice data is coming from Brandmeister as well as from the local receiver.

VK3KYY
Posts: 7478
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: Hotspot mode - Apparently stuck in TX

Post by VK3KYY » Thu Jan 02, 2020 10:01 pm

kd2lh wrote:
Thu Jan 02, 2020 9:45 pm
My PiStar is configured Simplex. I DO use a frequency offset (-150hz). It's a Pi Zero W running 4.1.6 PiStar with updates. It's configured for slot 2.

in the past, I've seen the missed packet happen in other sequences including when the voice data is coming from Brandmeister as well as from the local receiver.
Not this this is the cause of the problem. But you should not need to use an offset. Those values are only in PiStar because the JumboSpot etc hardware is not very accurate and needs to be turned to match the HT its communicating with.

For the OpenGD77 Hotspot, the GD-77 is calibrated in the factory (By TYT), and the main reference frequency clock generator is normally very accurate.

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

Re: Hotspot mode - Apparently stuck in TX

Post by kd2lh » Thu Jan 02, 2020 10:06 pm

VK3KYY wrote:
Thu Jan 02, 2020 10:01 pm
kd2lh wrote:
Thu Jan 02, 2020 9:45 pm
My PiStar is configured Simplex. I DO use a frequency offset (-150hz). It's a Pi Zero W running 4.1.6 PiStar with updates. It's configured for slot 2.

in the past, I've seen the missed packet happen in other sequences including when the voice data is coming from Brandmeister as well as from the local receiver.
Not this this is the cause of the problem. But you should not need to use an offset. Those values are only in PiStar because the JumboSpot etc hardware is not very accurate and needs to be turned to match the HT its communicating with.

For the OpenGD77 Hotspot, the GD-77 is calibrated in the factory (By TYT), and the main reference frequency clock generator is normally very accurate.
Ok... Is the GD77 hardware applying AFC automatically, and just reporting the amount as BER? I'll pull the offsets, but always see a higher BER reported on receive when it's set to zero. i'm using TYT and Motorola XPR7550e radios with it.

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

Re: Hotspot mode - Apparently stuck in TX

Post by kd2lh » Thu Jan 02, 2020 10:15 pm

Had another one occur. This time I wasn't here to manually reset it and it timed out in PiStar.

M: 2020-01-02 21:08:57.504 0000: 04 00 58 4B 52 34 41 44 20 *..XKR4AD *
M: 2020-01-02 21:08:57.979 DMR Slot 2, received network end of voice transmission from KR4AD to TG 3100, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 21:09:39.572 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-02 21:13:39.712 DMR Slot 2, RF user has timed out

Dashboard shows it's stuck in transmit, even though the radio itself is not transmitting. Nothing further is read from the radio by PiStar.

Over an hour later, I transmitted locally, and this transmission's "end of voice transmission" got PiStar going again. It worked with both a groupid call and a parrot call.

I've also seen it drop voice packets right after it's received the "talker alias":

M: 2020-01-02 22:22:03.770 DMR Slot 2, received network end of voice transmission from N3FVP to TG 3100, 3.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 22:22:08.588 DMR Slot 2, received network voice header from KD4UYR to TG 3100
M: 2020-01-02 22:22:09.201 DMR Talker Alias (Data Format 1, Received 6/14 char): 'KD4UYR'
M: 2020-01-02 22:22:09.201 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 22:22:09.202 0000: 04 00 5C 4B 44 34 55 59 52 *..\KD4UYR*
M: 2020-01-02 22:22:09.937 DMR Talker Alias (Data Format 1, Received 13/14 char): 'KD4UYR Kevin '
M: 2020-01-02 22:22:09.937 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 22:22:09.937 0000: 05 00 20 4B 65 76 69 6E 20 *.. Kevin *
M: 2020-01-02 22:22:10.657 DMR Talker Alias (Data Format 1, Received 14/14 char): 'KD4UYR Kevin C'
M: 2020-01-02 22:22:10.657 DMR Slot 2, Embedded Talker Alias Block 2
M: 2020-01-02 22:22:10.657 0000: 06 00 43 00 00 00 00 00 00 *..C......*

This leaves PiStar in the "TX" red state, and the GD77 stops transmission locally. This remains locked up until I reboot.

Here's one more where a local transmission times out with no "end of voice" signal coming in from the GD77 to PiSTar:

M: 2020-01-02 22:37:19.432 DMR Slot 2, received network end of voice transmission from K2CJP to TG 3100, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 22:37:19.503 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-02 22:41:19.703 DMR Slot 2, RF user has timed out

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

Re: Hotspot mode - Apparently stuck in TX

Post by F1RMB » Fri Jan 03, 2020 1:31 pm

Hi,
kd2lh wrote:
Thu Jan 02, 2020 10:15 pm
Had another one occur. This time I wasn't here to manually reset it and it timed out in PiStar.

M: 2020-01-02 21:08:57.504 0000: 04 00 58 4B 52 34 41 44 20 *..XKR4AD *
M: 2020-01-02 21:08:57.979 DMR Slot 2, received network end of voice transmission from KR4AD to TG 3100, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 21:09:39.572 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2020-01-02 21:13:39.712 DMR Slot 2, RF user has timed out

Dashboard shows it's stuck in transmit, even though the radio itself is not transmitting. Nothing further is read from the radio by PiStar.

Over an hour later, I transmitted locally, and this transmission's "end of voice transmission" got PiStar going again. It worked with both a groupid call and a parrot call.

I've also seen it drop voice packets right after it's received the "talker alias":

M: 2020-01-02 22:22:03.770 DMR Slot 2, received network end of voice transmission from N3FVP to TG 3100, 3.4 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 22:22:08.588 DMR Slot 2, received network voice header from KD4UYR to TG 3100
M: 2020-01-02 22:22:09.201 DMR Talker Alias (Data Format 1, Received 6/14 char): 'KD4UYR'
M: 2020-01-02 22:22:09.201 DMR Slot 2, Embedded Talker Alias Header
M: 2020-01-02 22:22:09.202 0000: 04 00 5C 4B 44 34 55 59 52 *..\KD4UYR*
M: 2020-01-02 22:22:09.937 DMR Talker Alias (Data Format 1, Received 13/14 char): 'KD4UYR Kevin '
M: 2020-01-02 22:22:09.937 DMR Slot 2, Embedded Talker Alias Block 1
M: 2020-01-02 22:22:09.937 0000: 05 00 20 4B 65 76 69 6E 20 *.. Kevin *
M: 2020-01-02 22:22:10.657 DMR Talker Alias (Data Format 1, Received 14/14 char): 'KD4UYR Kevin C'
M: 2020-01-02 22:22:10.657 DMR Slot 2, Embedded Talker Alias Block 2
M: 2020-01-02 22:22:10.657 0000: 06 00 43 00 00 00 00 00 00 *..C......*

This leaves PiStar in the "TX" red state, and the GD77 stops transmission locally. This remains locked up until I reboot.

Here's one more where a local transmission times out with no "end of voice" signal coming in from the GD77 to PiSTar:

M: 2020-01-02 22:37:19.432 DMR Slot 2, received network end of voice transmission from K2CJP to TG 3100, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-02 22:37:19.503 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2020-01-02 22:41:19.703 DMR Slot 2, RF user has timed out
Can you check this one (same restrictions as yesterday: unchecked with lastest Windows BlueDV beta, hotspot screen full of uninteresting text ;-) ).

Cheers.

EDIT: firmware deleted, a new build is available.

Post Reply