Ah ok.
Thanks for tracking this down
This sounds like the same sort of problem where the screen displays TG 0.
Perhaos the HS is sending ID 0 or TG 0 to PIStar and it’s rejecting it.
Hotspot mode - Apparently stuck in TX
Re: Hotspot mode - Apparently stuck in TX
One more failure log. Communication to MMDVM from PiStar is failing. This locked up within a few minutes of starting a conversation.
Code: Select all
I: 2019-12-10 19:57:56.391 This software is for use on amateur radio networks only,
I: 2019-12-10 19:57:56.391 it is to be used for educational purposes only. Its use on
I: 2019-12-10 19:57:56.391 commercial networks is strictly prohibited.
I: 2019-12-10 19:57:56.391 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2019-12-10 19:57:56.391 MMDVMHost-20191122_Pi-Star-v4 is starting
M: 2019-12-10 19:57:56.391 Built 11:05:01 Nov 22 2019 (GitID #ed7f593)
I: 2019-12-10 19:57:56.391 General Parameters
I: 2019-12-10 19:57:56.391 Callsign: KD2LH
I: 2019-12-10 19:57:56.391 Id: 3159165
I: 2019-12-10 19:57:56.391 Duplex: no
I: 2019-12-10 19:57:56.391 Timeout: 240s
I: 2019-12-10 19:57:56.391 D-Star: disabled
I: 2019-12-10 19:57:56.391 DMR: enabled
I: 2019-12-10 19:57:56.391 YSF: disabled
I: 2019-12-10 19:57:56.391 P25: disabled
I: 2019-12-10 19:57:56.391 NXDN: disabled
I: 2019-12-10 19:57:56.391 POCSAG: disabled
I: 2019-12-10 19:57:56.391 Modem Parameters
I: 2019-12-10 19:57:56.391 Port: /dev/ttyACM0
I: 2019-12-10 19:57:56.391 Protocol: uart
I: 2019-12-10 19:57:56.391 RX Invert: no
I: 2019-12-10 19:57:56.391 TX Invert: yes
I: 2019-12-10 19:57:56.391 PTT Invert: no
I: 2019-12-10 19:57:56.391 TX Delay: 100ms
I: 2019-12-10 19:57:56.391 RX Offset: -150Hz
I: 2019-12-10 19:57:56.391 TX Offset: -150Hz
I: 2019-12-10 19:57:56.391 RX DC Offset: 0
I: 2019-12-10 19:57:56.391 TX DC Offset: 0
I: 2019-12-10 19:57:56.391 RF Level: 100.0%
I: 2019-12-10 19:57:56.391 DMR Delay: 0 (0.0ms)
I: 2019-12-10 19:57:56.391 RX Level: 50.0%
I: 2019-12-10 19:57:56.391 CW Id TX Level: 50.0%
I: 2019-12-10 19:57:56.391 D-Star TX Level: 50.0%
I: 2019-12-10 19:57:56.391 DMR TX Level: 50.0%
I: 2019-12-10 19:57:56.391 YSF TX Level: 50.0%
I: 2019-12-10 19:57:56.391 P25 TX Level: 50.0%
I: 2019-12-10 19:57:56.391 NXDN TX Level: 50.0%
I: 2019-12-10 19:57:56.392 POCSAG TX Level: 50.0%
I: 2019-12-10 19:57:56.392 RX Frequency: 438600000Hz (438599850Hz)
I: 2019-12-10 19:57:56.392 TX Frequency: 438600000Hz (438599850Hz)
M: 2019-12-10 19:57:56.392 Opening the MMDVM
I: 2019-12-10 19:57:58.405 MMDVM protocol version: 1, description: OpenGD77 Hotspot v0.0.72
I: 2019-12-10 19:57:58.425 Display Parameters
I: 2019-12-10 19:57:58.426 Type: None
W: 2019-12-10 19:57:58.426 No valid display found, disabling
I: 2019-12-10 19:57:58.428 DMR Network Parameters
I: 2019-12-10 19:57:58.428 Address: 64.94.238.196
I: 2019-12-10 19:57:58.428 Port: 62031
I: 2019-12-10 19:57:58.428 Local: random
I: 2019-12-10 19:57:58.428 Jitter: 700ms
I: 2019-12-10 19:57:58.428 Slot 1: disabled
I: 2019-12-10 19:57:58.428 Slot 2: enabled
I: 2019-12-10 19:57:58.428 Mode Hang: 20s
I: 2019-12-10 19:57:58.428 Info Parameters
I: 2019-12-10 19:57:58.428 Callsign: KD2LH
I: 2019-12-10 19:57:58.428 RX Frequency: 438600000Hz
I: 2019-12-10 19:57:58.428 TX Frequency: 438600000Hz
I: 2019-12-10 19:57:58.428 Power: 1W
I: 2019-12-10 19:57:58.428 Latitude: 35.981499deg N
I: 2019-12-10 19:57:58.428 Longitude: -78.561798deg E
I: 2019-12-10 19:57:58.429 Height: 0m
I: 2019-12-10 19:57:58.429 Location: "Wake Forest, FM05RX"
I: 2019-12-10 19:57:58.429 Description: "USA"
I: 2019-12-10 19:57:58.429 URL: "http://www.qrz.com/db/KD2LH"
M: 2019-12-10 19:57:58.429 DMR, Opening DMR Network
I: 2019-12-10 19:57:58.429 RSSI
I: 2019-12-10 19:57:58.429 Mapping File: /usr/local/etc/RSSI.dat
I: 2019-12-10 19:57:58.430 Loaded 14 RSSI data mapping points from /usr/local/etc/RSSI.dat
I: 2019-12-10 19:57:58.430 DMR Id Lookups
I: 2019-12-10 19:57:58.430 File: /usr/local/etc/DMRIds.dat
I: 2019-12-10 19:57:58.430 Reload: 24 hours
I: 2019-12-10 19:57:58.797 Loaded 147819 Ids to the DMR callsign lookup table
I: 2019-12-10 19:57:58.797 Started the DMR Id lookup reload thread
I: 2019-12-10 19:57:58.797 DMR RF Parameters
I: 2019-12-10 19:57:58.797 Id: 315916508
I: 2019-12-10 19:57:58.797 Color Code: 1
I: 2019-12-10 19:57:58.797 Self Only: yes
I: 2019-12-10 19:57:58.797 Embedded LC Only: no
I: 2019-12-10 19:57:58.797 Dump Talker Alias Data: yes
I: 2019-12-10 19:57:58.797 Prefixes: 0
I: 2019-12-10 19:57:58.797 Call Hang: 3s
I: 2019-12-10 19:57:58.797 TX Hang: 4s
I: 2019-12-10 19:57:58.797 Mode Hang: 20s
I: 2019-12-10 19:57:58.797 OVCM: off
I: 2019-12-10 19:57:58.797 DMR Roaming Beacons Type: off
Starting logging, please wait...
M: 2019-12-10 20:03:37.063 DMR Slot 2, received network voice header from KD2LH to TG 98977
M: 2019-12-10 20:03:37.824 DMR Talker Alias (Data Format 1, Received 6/21 char): 'KD2LH '
M: 2019-12-10 20:03:37.824 DMR Slot 2, Embedded Talker Alias Header
M: 2019-12-10 20:03:37.824 0000: 04 00 6A 4B 44 32 4C 48 20 *..jKD2LH *
M: 2019-12-10 20:03:38.548 DMR Talker Alias (Data Format 1, Received 13/21 char): 'KD2LH DMR ID '
M: 2019-12-10 20:03:38.548 DMR Slot 2, Embedded Talker Alias Block 1
M: 2019-12-10 20:03:38.548 0000: 05 00 44 4D 52 20 49 44 20 *..DMR ID *
M: 2019-12-10 20:03:39.267 DMR Talker Alias (Data Format 1, Received 20/21 char): 'KD2LH DMR ID 3159165'
M: 2019-12-10 20:03:39.267 DMR Slot 2, Embedded Talker Alias Block 2
M: 2019-12-10 20:03:39.267 0000: 06 00 33 31 35 39 31 36 35 *..3159165*
M: 2019-12-10 20:03:39.987 DMR Talker Alias (Data Format 1, Received 21/21 char): 'KD2LH DMR ID 3159165 '
M: 2019-12-10 20:03:39.987 DMR Slot 2, Embedded Talker Alias Block 3
M: 2019-12-10 20:03:39.987 0000: 07 00 20 00 00 00 00 00 00 *.. ......*
M: 2019-12-10 20:03:41.907 DMR Slot 2, received network end of voice transmission from KD2LH to TG 98977, 4.8 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-10 20:03:58.989 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-10 20:04:03.490 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 4.3 seconds, BER: 0.5%
M: 2019-12-10 20:06:11.348 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2019-12-10 20:06:16.569 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 5.0 seconds, BER: 0.8%
M: 2019-12-10 20:06:19.737 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2019-12-10 20:06:24.719 DMR Slot 2, received network end of voice transmission from 9990 to KD2LH, 5.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-10 20:09:41.667 DMR Slot 2, received RF voice header from KD2LH to TG 31377
M: 2019-12-10 20:09:46.885 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 31377, 5.0 seconds, BER: 0.7%
M: 2019-12-10 20:10:11.144 DMR Slot 2, received network voice header from KD2LH to TG 31377
M: 2019-12-10 20:10:11.907 DMR Talker Alias (Data Format 1, Received 6/21 char): 'KD2LH '
M: 2019-12-10 20:10:11.907 DMR Slot 2, Embedded Talker Alias Header
M: 2019-12-10 20:10:11.907 0000: 04 00 6A 4B 44 32 4C 48 20 *..jKD2LH *
M: 2019-12-10 20:10:12.624 DMR Talker Alias (Data Format 1, Received 13/21 char): 'KD2LH DMR ID '
M: 2019-12-10 20:10:12.624 DMR Slot 2, Embedded Talker Alias Block 1
M: 2019-12-10 20:10:12.624 0000: 05 00 44 4D 52 20 49 44 20 *..DMR ID *
M: 2019-12-10 20:10:13.346 DMR Talker Alias (Data Format 1, Received 20/21 char): 'KD2LH DMR ID 3159165'
M: 2019-12-10 20:10:13.346 DMR Slot 2, Embedded Talker Alias Block 2
M: 2019-12-10 20:10:13.346 0000: 06 00 33 31 35 39 31 36 35 *..3159165*
M: 2019-12-10 20:10:13.824 DMR Slot 2, received network end of voice transmission from KD2LH to TG 31377, 2.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-10 20:12:35.296 DMR Slot 2, received network voice header from N1ID to TG 98977
M: 2019-12-10 20:12:35.937 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N1ID J'
M: 2019-12-10 20:12:35.937 DMR Slot 2, Embedded Talker Alias Header
M: 2019-12-10 20:12:35.937 0000: 04 00 6A 4E 31 49 44 20 4A *..jN1ID J*
M: 2019-12-10 20:12:36.656 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N1ID John E H'
M: 2019-12-10 20:12:36.656 DMR Slot 2, Embedded Talker Alias Block 1
M: 2019-12-10 20:12:36.656 0000: 05 00 6F 68 6E 20 45 20 48 *..ohn E H*
M: 2019-12-10 20:12:36.895 DMR Slot 2, received network end of voice transmission from N1ID to TG 98977, 1.6 seconds, 0% packet loss, BER: 0.0%
E: 2019-12-10 20:12:38.146 No reply from the modem for some time, resetting it
M: 2019-12-10 20:12:38.146 Closing the MMDVM
M: 2019-12-10 20:12:54.354 Opening the MMDVM
I: 2019-12-10 20:13:03.635 MMDVM protocol version: 0, description:
M: 2019-12-10 20:13:03.712 DMR Slot 2, received RF late entry from KD2LH to TG 98977
M: 2019-12-10 20:13:03.811 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 2.3 seconds, BER: 0.8%
M: 2019-12-10 20:13:25.768 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-10 20:13:25.950 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 0.0 seconds, BER: 0.0%
M: 2019-12-10 20:13:26.367 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-10 20:13:30.148 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 3.6 seconds, BER: 0.7%
M: 2019-12-10 20:13:35.252 DMR Slot 2, received network voice header from N1ID to TG 98977
M: 2019-12-10 20:13:35.908 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N1ID J'
M: 2019-12-10 20:13:35.908 DMR Slot 2, Embedded Talker Alias Header
M: 2019-12-10 20:13:35.908 0000: 04 00 6A 4E 31 49 44 20 4A *..jN1ID J*
M: 2019-12-10 20:13:36.627 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N1ID John E H'
M: 2019-12-10 20:13:36.628 DMR Slot 2, Embedded Talker Alias Block 1
M: 2019-12-10 20:13:36.628 0000: 05 00 6F 68 6E 20 45 20 48 *..ohn E H*
M: 2019-12-10 20:13:37.466 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N1ID John E Haddam C'
M: 2019-12-10 20:13:37.467 DMR Slot 2, Embedded Talker Alias Block 2
M: 2019-12-10 20:13:37.467 0000: 06 00 61 64 64 61 6D 20 43 *..addam C*
M: 2019-12-10 20:13:38.188 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N1ID John E Haddam CT'
M: 2019-12-10 20:13:38.188 DMR Slot 2, Embedded Talker Alias Block 3
M: 2019-12-10 20:13:38.188 0000: 07 00 54 00 00 00 00 00 00 *..T......*
M: 2019-12-10 20:13:38.305 DMR Slot 2, received network end of voice transmission from N1ID to TG 98977, 3.0 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-10 20:13:42.256 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-10 20:13:58.638 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 16.2 seconds, BER: 0.8%
M: 2019-12-10 20:14:04.893 DMR Slot 2, received network voice header from N1ID to TG 98977
M: 2019-12-10 20:14:05.544 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N1ID J'
M: 2019-12-10 20:14:05.544 DMR Slot 2, Embedded Talker Alias Header
M: 2019-12-10 20:14:05.544 0000: 04 00 6A 4E 31 49 44 20 4A *..jN1ID J*
M: 2019-12-10 20:14:06.267 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N1ID John E H'
M: 2019-12-10 20:14:06.268 DMR Slot 2, Embedded Talker Alias Block 1
M: 2019-12-10 20:14:06.268 0000: 05 00 6F 68 6E 20 45 20 48 *..ohn E H*
M: 2019-12-10 20:14:15.284 DMR Slot 2, network watchdog has expired, 2.1 seconds, 0% packet loss, BER: 0.0%
E: 2019-12-10 20:14:15.284 No reply from the modem for some time, resetting it
M: 2019-12-10 20:14:15.284 Closing the MMDVM
M: 2019-12-10 20:14:17.319 Opening the MMDVM
I: 2019-12-10 20:14:19.402 MMDVM protocol version: 1, description: OpenGD77 Hotspot v0.0.72
M: 2019-12-10 20:14:19.422 DMR Slot 2, received network late entry from N1ID to TG 98977
M: 2019-12-10 20:14:19.448 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2019-12-10 20:14:19.448 DMR Slot 2, Embedded Talker Alias Block 3
M: 2019-12-10 20:14:19.448 0000: 07 00 54 00 00 00 00 00 00 *..T......*
M: 2019-12-10 20:14:19.453 DMR Slot 2, received network end of voice transmission from N1ID to TG 98977, 0.8 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-10 20:14:22.174 DMR Slot 2, received network voice header from N1ID to TG 98977
M: 2019-12-10 20:14:22.826 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N1ID J'
M: 2019-12-10 20:14:22.826 DMR Slot 2, Embedded Talker Alias Header
M: 2019-12-10 20:14:22.826 0000: 04 00 6A 4E 31 49 44 20 4A *..jN1ID J*
M: 2019-12-10 20:14:23.547 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N1ID John E H'
M: 2019-12-10 20:14:23.547 DMR Slot 2, Embedded Talker Alias Block 1
M: 2019-12-10 20:14:23.547 0000: 05 00 6F 68 6E 20 45 20 48 *..ohn E H*
M: 2019-12-10 20:14:24.386 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N1ID John E Haddam C'
M: 2019-12-10 20:14:24.386 DMR Slot 2, Embedded Talker Alias Block 2
M: 2019-12-10 20:14:24.386 0000: 06 00 61 64 64 61 6D 20 43 *..addam C*
M: 2019-12-10 20:14:25.108 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N1ID John E Haddam CT'
M: 2019-12-10 20:14:25.108 DMR Slot 2, Embedded Talker Alias Block 3
M: 2019-12-10 20:14:25.108 0000: 07 00 54 00 00 00 00 00 00 *..T......*
M: 2019-12-10 20:14:26.667 DMR Slot 2, received network end of voice transmission from N1ID to TG 98977, 4.4 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-10 20:14:35.897 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-10 20:14:41.478 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 5.4 seconds, BER: 1.0%
M: 2019-12-10 20:14:46.042 DMR Slot 2, received network voice header from N1ID to TG 98977
M: 2019-12-10 20:14:46.674 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N1ID J'
M: 2019-12-10 20:14:46.674 DMR Slot 2, Embedded Talker Alias Header
M: 2019-12-10 20:14:46.674 0000: 04 00 6A 4E 31 49 44 20 4A *..jN1ID J*
M: 2019-12-10 20:14:47.412 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N1ID John E H'
M: 2019-12-10 20:14:47.412 DMR Slot 2, Embedded Talker Alias Block 1
M: 2019-12-10 20:14:47.412 0000: 05 00 6F 68 6E 20 45 20 48 *..ohn E H*
M: 2019-12-10 20:14:48.133 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N1ID John E Haddam C'
M: 2019-12-10 20:14:48.133 DMR Slot 2, Embedded Talker Alias Block 2
M: 2019-12-10 20:14:48.133 0000: 06 00 61 64 64 61 6D 20 43 *..addam C*
M: 2019-12-10 20:14:48.850 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N1ID John E Haddam CT'
M: 2019-12-10 20:14:48.850 DMR Slot 2, Embedded Talker Alias Block 3
M: 2019-12-10 20:14:48.850 0000: 07 00 54 00 00 00 00 00 00 *..T......*
E: 2019-12-10 20:14:52.307 No reply from the modem for some time, resetting it
M: 2019-12-10 20:14:52.307 Closing the MMDVM
M: 2019-12-10 20:14:54.309 Opening the MMDVM
E: 2019-12-10 20:15:07.124 Unable to read the firmware version after six attempts
M: 2019-12-10 20:15:42.493 Opening the MMDVM
Re: Hotspot mode - Apparently stuck in TX
@kd2lh
That's a different problem.
The hotspot stopped responding.
That's a different problem.
The hotspot stopped responding.
Re: Hotspot mode - Apparently stuck in TX
HI, I have this running on a Pi Zero W now. We'll see if the slower computer / usb interface makes a difference.
Re: Hotspot mode - Apparently stuck in TX
Logging started:
Live Logs
Starting logging, please wait...
M: 2019-12-11 20:32:57.468 DMR Slot 2, received RF voice header from KD2LH to 9990
I saw this anomaly in the log:
M: 2019-12-11 20:58:34.891 DMR Slot 2, received network end of voice transmission from N4CWZ to TG 3137, 43.3 seconds, 6% packet loss, BER: 0.0%
M: 2019-12-11 20:58:38.958 DMR Slot 2, received network voice header from N4AMP to TG 3137
M: 2019-12-11 20:58:38.959 DMR Slot 2, network watchdog has expired, 0.1 seconds, 0% packet loss, BER: 0.0%
E: 2019-12-11 20:58:38.964 No reply from the modem for some time, resetting it
M: 2019-12-11 20:58:39.002 Closing the MMDVM
M: 2019-12-11 20:58:41.003 Opening the MMDVM
I: 2019-12-11 20:58:43.015 MMDVM protocol version: 1, description: OpenGD77 Hotspot v0.0.72
After just under 2 hours, I saw this error:
M: 2019-12-11 22:13:24.792 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-11 22:17:24.930 DMR Slot 2, RF user has timed out
The thing is that I had not transmitted in that timeframe.
PiStar showed the hotspot in TX, but things still operated and it received a local RF transmission, resetting everything. So, TX was left on, but it didn't lock up.
In fact, the last local RF transmission received by the hotspot had been minutes earlier:
M: 2019-12-11 21:50:53.916 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-11 21:50:58.055 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 3.6 seconds, BER: 0.5%
Later, I found the Pi-Star session with log running was reset, and I had to login again.
Within a minute of login, this was logged. "TG 0" shows up on the GD77 display. The HotSpot is NOT locked up, and the radio responded properly to a Parrot call.
Live Logs
Starting logging, please wait...
M: 2019-12-12 03:11:02.353 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 03:13:54.570 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2019-12-12 03:13:59.075 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 4.3 seconds, BER: 0.6%
M: 2019-12-12 03:14:02.262 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2019-12-12 03:14:06.529 DMR Slot 2, received network end of voice tr
More were received, without any lockup:
M: 2019-12-12 04:00:18.516 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 04:02:55.137 DMR Slot 2, RF user 0 rejected
Got more of these overnight, but the hotspot has not locked up using the Pi Zero W:
M: 2019-12-12 12:19:39.737 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 12:42:37.213 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 12:43:34.010 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 12:48:05.360 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 13:06:20.628 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-12 13:06:26.181 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 5.4 seconds, BER: 0.9%
Live Logs
Starting logging, please wait...
M: 2019-12-11 20:32:57.468 DMR Slot 2, received RF voice header from KD2LH to 9990
I saw this anomaly in the log:
M: 2019-12-11 20:58:34.891 DMR Slot 2, received network end of voice transmission from N4CWZ to TG 3137, 43.3 seconds, 6% packet loss, BER: 0.0%
M: 2019-12-11 20:58:38.958 DMR Slot 2, received network voice header from N4AMP to TG 3137
M: 2019-12-11 20:58:38.959 DMR Slot 2, network watchdog has expired, 0.1 seconds, 0% packet loss, BER: 0.0%
E: 2019-12-11 20:58:38.964 No reply from the modem for some time, resetting it
M: 2019-12-11 20:58:39.002 Closing the MMDVM
M: 2019-12-11 20:58:41.003 Opening the MMDVM
I: 2019-12-11 20:58:43.015 MMDVM protocol version: 1, description: OpenGD77 Hotspot v0.0.72
After just under 2 hours, I saw this error:
M: 2019-12-11 22:13:24.792 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-11 22:17:24.930 DMR Slot 2, RF user has timed out
The thing is that I had not transmitted in that timeframe.
PiStar showed the hotspot in TX, but things still operated and it received a local RF transmission, resetting everything. So, TX was left on, but it didn't lock up.
In fact, the last local RF transmission received by the hotspot had been minutes earlier:
M: 2019-12-11 21:50:53.916 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-11 21:50:58.055 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 3.6 seconds, BER: 0.5%
Later, I found the Pi-Star session with log running was reset, and I had to login again.
Within a minute of login, this was logged. "TG 0" shows up on the GD77 display. The HotSpot is NOT locked up, and the radio responded properly to a Parrot call.
Live Logs
Starting logging, please wait...
M: 2019-12-12 03:11:02.353 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 03:13:54.570 DMR Slot 2, received RF voice header from KD2LH to 9990
M: 2019-12-12 03:13:59.075 DMR Slot 2, received RF end of voice transmission from KD2LH to 9990, 4.3 seconds, BER: 0.6%
M: 2019-12-12 03:14:02.262 DMR Slot 2, received network voice header from 9990 to KD2LH
M: 2019-12-12 03:14:06.529 DMR Slot 2, received network end of voice tr
More were received, without any lockup:
M: 2019-12-12 04:00:18.516 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 04:02:55.137 DMR Slot 2, RF user 0 rejected
Got more of these overnight, but the hotspot has not locked up using the Pi Zero W:
M: 2019-12-12 12:19:39.737 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 12:42:37.213 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 12:43:34.010 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 12:48:05.360 DMR Slot 2, RF user 0 rejected
M: 2019-12-12 13:06:20.628 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-12 13:06:26.181 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 5.4 seconds, BER: 0.9%
Re: Hotspot mode - Apparently stuck in TX
Pi-Star just momentarily started dropping voice packets. This is the log:
M: 2019-12-12 14:44:52.704 DMR Slot 2, RF user 0 rejected
The hotspot is continuing to receive voice packets from the VOIP network, and it continues to transmit through the GD77. This has continued over a number of different users on the talkgroup.
Within a few minutes of this, Pi-Star stopped communicating with the GD77 without any error indication.
I think it's possible that the USB interface or code responding to USB within OpenGD77 was overrun... especially since the slower Pi Zero W lasts much longer than a faster Pi4B.
M: 2019-12-12 14:44:52.704 DMR Slot 2, RF user 0 rejected
The hotspot is continuing to receive voice packets from the VOIP network, and it continues to transmit through the GD77. This has continued over a number of different users on the talkgroup.
Within a few minutes of this, Pi-Star stopped communicating with the GD77 without any error indication.
I think it's possible that the USB interface or code responding to USB within OpenGD77 was overrun... especially since the slower Pi Zero W lasts much longer than a faster Pi4B.
Re: Hotspot mode - Apparently stuck in TX
Just don't take for granted Internet and BrandMeister servers.
Errors are possible everywhere.
Errors are possible everywhere.
Re: Hotspot mode - Apparently stuck in TX
This also even applies to repeaters.
I have noticed bugs in the Motorola IPSC2 server dashboard, where it sometimes seems to display the wrong ID number for a short transmission
I initially thought this is a problem with the OpenGD77, But then noticed someone using a Motorola radio also had the same effect.
Re: Hotspot mode - Apparently stuck in TX
One more lockup:
M: 2019-12-12 22:07:56.455 DMR Slot 2, received network end of voice transmission from 2W0JMK to TG 98977, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-12 22:15:09.310 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-12 22:19:09.463 DMR Slot 2, RF user has timed out
There was no local RF activity at the time. The last RF activity some minutes earlier had been KD2LH to TG 98977, Something caused the packet to be resent from the GD77 to PiStar out of a buffer, not from an active RF signal.
While "TX" was stuck on PiStar's dashboard, I was able to transmit later to the radio and it functioned properly. I transmitted to the GD77 two times. The first transmission was not sent to PiStar by the GD77. When the first transmission ended it reset the frozen dashboard "TX" and the second transmission one operated correctly:
M: 2019-12-12 22:22:47.647 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 2.5 seconds, BER: 0.6%
M: 2019-12-12 22:22:58.925 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-12 22:23:00.907 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 1.8 seconds, BER: 0.6%
Download the log: here
M: 2019-12-12 22:07:56.455 DMR Slot 2, received network end of voice transmission from 2W0JMK to TG 98977, 1.2 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-12 22:15:09.310 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-12 22:19:09.463 DMR Slot 2, RF user has timed out
There was no local RF activity at the time. The last RF activity some minutes earlier had been KD2LH to TG 98977, Something caused the packet to be resent from the GD77 to PiStar out of a buffer, not from an active RF signal.
While "TX" was stuck on PiStar's dashboard, I was able to transmit later to the radio and it functioned properly. I transmitted to the GD77 two times. The first transmission was not sent to PiStar by the GD77. When the first transmission ended it reset the frozen dashboard "TX" and the second transmission one operated correctly:
M: 2019-12-12 22:22:47.647 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 2.5 seconds, BER: 0.6%
M: 2019-12-12 22:22:58.925 DMR Slot 2, received RF voice header from KD2LH to TG 98977
M: 2019-12-12 22:23:00.907 DMR Slot 2, received RF end of voice transmission from KD2LH to TG 98977, 1.8 seconds, BER: 0.6%
Download the log: here
Re: Hotspot mode - Apparently stuck in TX
I've experienced the same here this morning. In hotspot mode, pi-star reports that my radio is in TX, with no RF traffic. And the same log clue: RF user has timed out. Here are the logs:
M: 2019-12-13 16:17:56.386 DMR Slot 2, received RF voice header from W0RMT to 9990
M: 2019-12-13 16:18:02.266 DMR Slot 2, received RF end of voice transmission from W0RMT to 9990, 5.8 seconds, BER: 0.3%
M: 2019-12-13 16:18:05.542 DMR Slot 2, received network voice header from 9990 to W0RMT
M: 2019-12-13 16:18:11.302 DMR Slot 2, received network end of voice transmission from 9990 to W0RMT, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:18:38.868 DMR Slot 2, received RF voice header from W0RMT to TG 31088
M: 2019-12-13 16:18:42.228 DMR Slot 2, received RF end of voice transmission from W0RMT to TG 31088, 3.2 seconds, BER: 0.3%
M: 2019-12-13 16:30:56.096 DMR Slot 2, received network voice header from ZS5LO to TG 31088
M: 2019-12-13 16:30:56.109 DMR Slot 2, received network end of voice transmission from ZS5LO to TG 31088, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:32:16.338 DMR Slot 2, received network voice header from ZS5LO to TG 31088
M: 2019-12-13 16:32:16.420 DMR Slot 2, received network end of voice transmission from ZS5LO to TG 31088, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:43:32.401 DMR Slot 2, received network voice header from N0OUW to TG 31088
M: 2019-12-13 16:43:32.949 DMR Slot 2, received network end of voice transmission from N0OUW to TG 31088, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:44:28.871 DMR Slot 2, received network voice header from N0OUW to TG 31088
M: 2019-12-13 16:44:29.626 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N0OUW '
M: 2019-12-13 16:44:30.364 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N0OUW DMR ID:'
M: 2019-12-13 16:44:30.485 DMR Slot 2, received network end of voice transmission from N0OUW to TG 31088, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:51:58.874 DMR Slot 2, received RF voice header from W0RMT to TG 31088
M: 2019-12-13 16:55:59.021 DMR Slot 2, RF user has timed out
M: 2019-12-13 16:17:56.386 DMR Slot 2, received RF voice header from W0RMT to 9990
M: 2019-12-13 16:18:02.266 DMR Slot 2, received RF end of voice transmission from W0RMT to 9990, 5.8 seconds, BER: 0.3%
M: 2019-12-13 16:18:05.542 DMR Slot 2, received network voice header from 9990 to W0RMT
M: 2019-12-13 16:18:11.302 DMR Slot 2, received network end of voice transmission from 9990 to W0RMT, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:18:38.868 DMR Slot 2, received RF voice header from W0RMT to TG 31088
M: 2019-12-13 16:18:42.228 DMR Slot 2, received RF end of voice transmission from W0RMT to TG 31088, 3.2 seconds, BER: 0.3%
M: 2019-12-13 16:30:56.096 DMR Slot 2, received network voice header from ZS5LO to TG 31088
M: 2019-12-13 16:30:56.109 DMR Slot 2, received network end of voice transmission from ZS5LO to TG 31088, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:32:16.338 DMR Slot 2, received network voice header from ZS5LO to TG 31088
M: 2019-12-13 16:32:16.420 DMR Slot 2, received network end of voice transmission from ZS5LO to TG 31088, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:43:32.401 DMR Slot 2, received network voice header from N0OUW to TG 31088
M: 2019-12-13 16:43:32.949 DMR Slot 2, received network end of voice transmission from N0OUW to TG 31088, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:44:28.871 DMR Slot 2, received network voice header from N0OUW to TG 31088
M: 2019-12-13 16:44:29.626 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N0OUW '
M: 2019-12-13 16:44:30.364 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N0OUW DMR ID:'
M: 2019-12-13 16:44:30.485 DMR Slot 2, received network end of voice transmission from N0OUW to TG 31088, 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-13 16:51:58.874 DMR Slot 2, received RF voice header from W0RMT to TG 31088
M: 2019-12-13 16:55:59.021 DMR Slot 2, RF user has timed out