Hotspot mode - Apparently stuck in TX

ad4uu
Posts: 9
Joined: Thu Dec 12, 2019 11:24 pm

Re: Hotspot mode - Apparently stuck in TX

Post by ad4uu » Mon Dec 16, 2019 12:50 am

Bud,

Here is syslog file text. The time of the TX hang was 19:33:35. Call KF6S.

Code: Select all

Dec 15 19:32:59 pi-star-23 ntpd[1336]: Soliciting pool server 198.50.238.156
Dec 15 19:32:59 pi-star-23 ntpd[1336]: Soliciting pool server 64.22.253.155
Dec 15 19:33:00 pi-star-23 ntpd[1336]: Soliciting pool server 171.66.97.126
Dec 15 19:33:00 pi-star-23 ntpd[1336]: Soliciting pool server 142.147.92.5
Dec 15 19:33:00 pi-star-23 ntpd[1336]: Soliciting pool server 204.2.134.163
Dec 15 19:33:00 pi-star-23 ntpd[1336]: Soliciting pool server 107.21.100.177
Dec 15 19:33:01 pi-star-23 ntpd[1336]: Soliciting pool server 184.105.182.15
Dec 15 19:33:01 pi-star-23 ntpd[1336]: Soliciting pool server 208.69.120.241
Dec 15 19:33:01 pi-star-23 ntpd[1336]: Soliciting pool server 192.111.144.114
Dec 15 19:33:01 pi-star-23 ntpd[1336]: Soliciting pool server 12.167.151.1
Dec 15 19:33:02 pi-star-23 ntpd[1336]: Soliciting pool server 163.237.218.19
Dec 15 19:33:02 pi-star-23 ntpd[1336]: Soliciting pool server 2607:f058:120::c
Dec 15 19:33:02 pi-star-23 ntpd[1336]: Soliciting pool server 38.229.71.1
Dec 15 19:33:03 pi-star-23 ntpd[1336]: Soliciting pool server 50.116.52.97
Dec 15 19:33:04 pi-star-23 ntpd[1336]: Soliciting pool server 104.236.116.147
Dec 15 19:33:11 pi-star-23 systemd[1]: Created slice User Slice of pi-star.
Dec 15 19:33:11 pi-star-23 systemd[1]: Starting User Manager for UID 1000...
Dec 15 19:33:11 pi-star-23 systemd[1]: Started Session c1 of user pi-star.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Listening on GnuPG cryptographic agent (access for web browsers).
Dec 15 19:33:11 pi-star-23 systemd[1538]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
Dec 15 19:33:11 pi-star-23 systemd[1538]: Reached target Timers.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
Dec 15 19:33:11 pi-star-23 systemd[1538]: Reached target Paths.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Listening on GnuPG cryptographic agent and passphrase cache.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Listening on GnuPG network certificate management daemon.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Reached target Sockets.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Reached target Basic System.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Reached target Default.
Dec 15 19:33:11 pi-star-23 systemd[1538]: Startup finished in 89ms.
Dec 15 19:33:11 pi-star-23 systemd[1]: Started User Manager for UID 1000.
Dec 15 19:33:16 pi-star-23 kernel: [   82.745118] random: crng init done
Dec 15 19:33:16 pi-star-23 kernel: [   82.745131] random: 7 urandom warning(s) missed due to ratelimiting
Dec 15 19:33:38 pi-star-23 kernel: [  104.539351] usb usb1-port1: disabled by hub (EMI?), re-enabling...
Dec 15 19:33:38 pi-star-23 kernel: [  104.539375] usb 1-1: USB disconnect, device number 2
Dec 15 19:33:38 pi-star-23 kernel: [  104.539644] cdc_acm 1-1:1.0: failed to set dtr/rts
Dec 15 19:33:38 pi-star-23 kernel: [  104.749333] Indeed it is in host mode hprt0 = 00021501
Dec 15 19:33:38 pi-star-23 kernel: [  104.959210] usb 1-1: new full-speed USB device number 3 using dwc_otg
Dec 15 19:33:38 pi-star-23 kernel: [  104.959613] Indeed it is in host mode hprt0 = 00021d01
Dec 15 19:33:38 pi-star-23 kernel: [  105.200673] usb 1-1: New USB device found, idVendor=1fc9, idProduct=0094, bcdDevice= 1.01
Dec 15 19:33:38 pi-star-23 kernel: [  105.200679] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 15 19:33:38 pi-star-23 kernel: [  105.200684] usb 1-1: Product: MCU VIRTUAL COM DEMO
Dec 15 19:33:38 pi-star-23 kernel: [  105.200688] usb 1-1: Manufacturer: NXP SEMICONDUCTORS
Dec 15 19:33:38 pi-star-23 kernel: [  105.201283] cdc_acm 1-1:1.0: ttyACM1: USB ACM device
Dec 15 19:33:56 pi-star-23 systemd[1]: Starting Pi-Star HostAPD Service...
Dec 15 19:33:56 pi-star-23 systemd[1]: Started Pi-Star HostAPD Service.
Dec 15 19:34:27 pi-star-23 pistar-watchdog.service[1316]: Warning: Stopping dmrgateway.service, but it can still be activated by:
Dec 15 19:34:27 pi-star-23 pistar-watchdog.service[1316]:   dmrgateway.timer
Dec 15 19:34:29 pi-star-23 systemd[1]: Starting DMRGateway Radio Servce...
Dec 15 19:34:29 pi-star-23 systemd[1]: dmrgateway.service: Control process exited, code=exited status=1
Dec 15 19:34:29 pi-star-23 systemd[1]: Failed to start DMRGateway Radio Servce.
Dec 15 19:34:29 pi-star-23 systemd[1]: dmrgateway.service: Unit entered failed state.
Dec 15 19:34:29 pi-star-23 systemd[1]: dmrgateway.service: Failed with result 'exit-code'.
Dec 15 19:34:29 pi-star-23 pistar-watchdog.service[1316]: Job for dmrgateway.service failed because the control process exited with error code.
Dec 15 19:34:29 pi-star-23 pistar-watchdog.service[1316]: See "systemctl status dmrgateway.service" and "journalctl -xe" for details.
Dec 15 19:34:39 pi-star-23 pistar-watchdog.service[1316]: Warning: Stopping ysfgateway.service, but it can still be activated by:
Dec 15 19:34:39 pi-star-23 pistar-watchdog.service[1316]:   ysfgateway.timer
Dec 15 19:34:41 pi-star-23 systemd[1]: Starting Yaesu System Fusion Servce...
Dec 15 19:34:41 pi-star-23 systemd[1]: ysfgateway.service: Control process exited, code=exited status=1
Dec 15 19:34:41 pi-star-23 systemd[1]: Failed to start Yaesu System Fusion Servce.
Dec 15 19:34:41 pi-star-23 systemd[1]: ysfgateway.service: Unit entered failed state.
Dec 15 19:34:41 pi-star-23 systemd[1]: ysfgateway.service: Failed with result 'exit-code'.
Dec 15 19:34:41 pi-star-23 pistar-watchdog.service[1316]: Job for ysfgateway.service failed because the control process exited with error code.
Dec 15 19:34:41 pi-star-23 pistar-watchdog.service[1316]: See "systemctl status ysfgateway.service" and "journalctl -xe" for details.
Dec 15 19:34:51 pi-star-23 pistar-watchdog.service[1316]: Warning: Stopping p25gateway.service, but it can still be activated by:
Dec 15 19:34:51 pi-star-23 pistar-watchdog.service[1316]:   p25gateway.timer
Dec 15 19:34:53 pi-star-23 systemd[1]: Starting P25 Servce...
Dec 15 19:34:53 pi-star-23 systemd[1]: p25gateway.service: Control process exited, code=exited status=1
Dec 15 19:34:53 pi-star-23 systemd[1]: Failed to start P25 Servce.
Dec 15 19:34:53 pi-star-23 systemd[1]: p25gateway.service: Unit entered failed state.
Dec 15 19:34:53 pi-star-23 systemd[1]: p25gateway.service: Failed with result 'exit-code'.
Dec 15 19:34:53 pi-star-23 pistar-watchdog.service[1316]: Job for p25gateway.service failed because the control process exited with error code.
Dec 15 19:34:53 pi-star-23 pistar-watchdog.service[1316]: See "systemctl status p25gateway.service" and "journalctl -xe" for details.
Dec 15 19:35:03 pi-star-23 pistar-watchdog.service[1316]: Warning: Stopping ysfparrot.service, but it can still be activated by:
Dec 15 19:35:03 pi-star-23 pistar-watchdog.service[1316]:   ysfparrot.timer
Dec 15 19:35:05 pi-star-23 systemd[1]: Starting YSF Parrot...
Dec 15 19:35:05 pi-star-23 systemd[1]: ysfparrot.service: Control process exited, code=exited status=1
Dec 15 19:35:05 pi-star-23 systemd[1]: Failed to start YSF Parrot.
Dec 15 19:35:05 pi-star-23 systemd[1]: ysfparrot.service: Unit entered failed state.
Dec 15 19:35:05 pi-star-23 systemd[1]: ysfparrot.service: Failed with result 'exit-code'.
Dec 15 19:35:05 pi-star-23 pistar-watchdog.service[1316]: Job for ysfparrot.service failed because the control process exited with error code.
Dec 15 19:35:05 pi-star-23 pistar-watchdog.service[1316]: See "systemctl status ysfparrot.service" and "journalctl -xe" for details.
Dec 15 19:35:15 pi-star-23 pistar-watchdog.service[1316]: Warning: Stopping p25parrot.service, but it can still be activated by:
Dec 15 19:35:15 pi-star-23 pistar-watchdog.service[1316]:   p25parrot.timer
Dec 15 19:35:17 pi-star-23 systemd[1]: Starting P25 Parrot...
Dec 15 19:35:17 pi-star-23 systemd[1]: p25parrot.service: Control process exited, code=exited status=1
Dec 15 19:35:17 pi-star-23 systemd[1]: Failed to start P25 Parrot.
Dec 15 19:35:17 pi-star-23 systemd[1]: p25parrot.service: Unit entered failed state.
Dec 15 19:35:17 pi-star-23 systemd[1]: p25parrot.service: Failed with result 'exit-code'.
Dec 15 19:35:17 pi-star-23 pistar-watchdog.service[1316]: Job for p25parrot.service failed because the control process exited with error code.
Dec 15 19:35:17 pi-star-23 pistar-watchdog.service[1316]: See "systemctl status p25parrot.service" and "journalctl -xe" for details.
Dec 15 19:35:19 pi-star-23 systemd[1]: Started Session c2 of user pi-star.
Dec 15 19:35:27 pi-star-23 pistar-watchdog.service[1316]: Warning: Stopping ysf2dmr.service, but it can still be activated by:

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

Re: Hotspot mode - Apparently stuck in TX

Post by W0RMT » Mon Dec 16, 2019 1:29 am

ad4uu wrote:
Sun Dec 15, 2019 5:14 pm
Thanks Bud,

Here is the live log. I keyed up 31665. N9KFW keyed up briefly. Then when kc8usa keyed up it Hung on TX.

Starting logging, please wait...
M: 2019-12-15 17:08:46.291 DMR Slot 2, received RF voice header from AD4UU to TG 31665
M: 2019-12-15 17:08:47.494 DMR Slot 2, received RF end of voice transmission from AD4UU to TG 31665, 0.0 seconds, BER: 0.0%
M: 2019-12-15 17:10:12.432 DMR Slot 2, received network voice header from N9KFW to TG 31665
M: 2019-12-15 17:10:12.531 DMR Slot 2, received network end of voice transmission from N9KFW to TG 31665, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2019-12-15 17:11:06.576 DMR Slot 2, received network voice header from KC8USA to TG 31665

Thanks

Dave
This looks like the header was received but it did not receive and send the voice data to the radio. You might check the RF hangtime and Net hangtime in pi-star and make sure they're not set to something really short?

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

Re: Hotspot mode - Apparently stuck in TX

Post by W0RMT » Mon Dec 16, 2019 1:31 am

ad4uu wrote:
Mon Dec 16, 2019 12:50 am
Bud,

Here is syslog file text. The time of the TX hang was 19:33:35. Call KF6S.
I'm not sure what to gather from this one. Maybe someone else can chime in. Perhaps an invalid UID (1000)?

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

Re: Hotspot mode - Apparently stuck in TX

Post by VK3KYY » Mon Dec 16, 2019 2:06 am

The Tier1 version has been stable for several months, so its less likely to be a bug in the Hotspot than something wrong with the PiStar setup

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

Re: Hotspot mode - Apparently stuck in TX

Post by W0RMT » Mon Dec 16, 2019 2:09 am

VK3KYY wrote:
Mon Dec 16, 2019 2:06 am
The Tier1 version has been stable for several months, so its less likely to be a bug in the Hotspot than something wrong with the PiStar setup
I was also thinking it might be on the pi-star side of things. @AD4UU I would try burning a new image of pi-star and starting from scratch.

ad4uu
Posts: 9
Joined: Thu Dec 12, 2019 11:24 pm

Re: Hotspot mode - Apparently stuck in TX

Post by ad4uu » Mon Dec 16, 2019 12:55 pm

Hi guys, Thanks for your help.

I downloaded a fresh image of pi-star 4.0. Configured the basic info in the config screen.

It worked for about 18 minutes before it hung in TX at 07:40:04.

Here is the system log:
ec 16 07:39:50 pi-star systemd[1]: Failed to start Pi-Star YSF2P25 Service.
Dec 16 07:39:50 pi-star systemd[1]: ysf2p25.service: Unit entered failed state.
Dec 16 07:39:50 pi-star systemd[1]: ysf2p25.service: Failed with result 'exit-code'.
Dec 16 07:40:00 pi-star pistar-watchdog.service[1036]: Warning: Stopping dmr2ysf.service, but it can still be activated by:
Dec 16 07:40:00 pi-star pistar-watchdog.service[1036]: dmr2ysf.timer
Dec 16 07:40:01 pi-star CRON[23546]: (root) CMD (/usr/local/sbin/pistar-upnp.service start > /dev/null 2>&1 &)
Dec 16 07:40:02 pi-star systemd[1]: Starting Pi-Star DMR2YSF Service...
Dec 16 07:40:02 pi-star systemd[1]: dmr2ysf.service: Control process exited, code=exited status=1
Dec 16 07:40:02 pi-star systemd[1]: Failed to start Pi-Star DMR2YSF Service.
Dec 16 07:40:02 pi-star systemd[1]: dmr2ysf.service: Unit entered failed state.
Dec 16 07:40:02 pi-star systemd[1]: dmr2ysf.service: Failed with result 'exit-code'.
Dec 16 07:40:02 pi-star pistar-watchdog.service[1036]: Job for dmr2ysf.service failed because the control process exited with error code.
Dec 16 07:40:02 pi-star pistar-watchdog.service[1036]: See "systemctl status dmr2ysf.service" and "journalctl -xe" for details.
Dec 16 07:40:12 pi-star pistar-watchdog.service[1036]: Warning: Stopping dmr2nxdn.service, but it can still be activated by:
Dec 16 07:40:12 pi-star pistar-watchdog.service[1036]: dmr2nxdn.timer
Dec 16 07:40:14 pi-star systemd[1]: Starting Pi-Star DMR2NXDN Service...
Dec 16 07:40:14 pi-star systemd[1]: dmr2nxdn.service: Control process exited, code=exited status=1
Dec 16 07:40:14 pi-star systemd[1]: Failed to start Pi-Star DMR2NXDN Service.
Dec 16 07:40:14 pi-star systemd[1]: dmr2nxdn.service: Unit entered failed state.
Dec 16 07:40:14 pi-star systemd[1]: dmr2nxdn.service: Failed with result 'exit-code'.
Dec 16 07:40:14 pi-star pistar-watchdog.service[1036]: Job for dmr2nxdn.service failed because the control process exited with error code.
Dec 16 07:40:14 pi-star pistar-watchdog.service[1036]: See "systemctl status dmr2nxdn.service" and "journalctl -xe" for details.
Dec 16 07:40:24 pi-star pistar-watchdog.service[1036]: Warning: Stopping dapnetgateway.service, but it can still be activated by:
Dec 16 07:40:24 pi-star pistar-watchdog.service[1036]: dapnetgateway.timer
Dec 16 07:40:26 pi-star systemd[1]: Starting Pi-Star DAPNet Gateway Service...
Dec 16 07:40:26 pi-star systemd[1]: dapnetgateway.service: Control process exited, code=exited status=1
Dec 16 07:40:26 pi-star systemd[1]: Failed to start Pi-Star DAPNet Gateway Service.
Dec 16 07:40:26 pi-star systemd[1]: dapnetgateway.service: Unit entered failed state.
Dec 16 07:40:26 pi-star systemd[1]: dapnetgateway.service: Failed with result 'exit-code'.
Dec 16 07:40:26 pi-star pistar-watchdog.service[1036]: Job for dapnetgateway.service failed because the control process exited with error code.
Dec 16 07:40:26 pi-star pistar-watchdog.service[1036]: See "systemctl status dapnetgateway.service" and "journalctl -xe" for details.
Dec 16 07:40:30 pi-star kernel: [ 1198.943604] ERROR::handle_hc_chhltd_intr_dma:2214: handle_hc_chhltd_intr_dma: Channel 6, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x06000001
Dec 16 07:40:30 pi-star kernel: [ 1198.943604]
Dec 16 07:40:30 pi-star kernel: [ 1198.943656] ERROR::handle_hc_chhltd_intr_dma:2214: handle_hc_chhltd_intr_dma: Channel 2, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x06000001
Dec 16 07:40:30 pi-star kernel: [ 1198.943656]
Dec 16 07:40:30 pi-star kernel: [ 1198.943714] ERROR::handle_hc_chhltd_intr_dma:2214: handle_hc_chhltd_intr_dma: Channel 5, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x06000021
Dec 16 07:40:30 pi-star kernel: [ 1198.943714]
Dec 16 07:40:30 pi-star kernel: [ 1199.005226] ERROR::handle_hc_chhltd_intr_dma:2214: handle_hc_chhltd_intr_dma: Channel 7, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x06000001
Dec 16 07:40:30 pi-star kernel: [ 1199.005226]
Dec 16 07:40:30 pi-star kernel: [ 1199.005302] ERROR::handle_hc_chhltd_intr_dma:2214: handle_hc_chhltd_intr_dma: Channel 1, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x06000001
Dec 16 07:40:30 pi-star kernel: [ 1199.005302]
Dec 16 07:40:30 pi-star kernel: [ 1199.005351] ERROR::handle_hc_chhltd_intr_dma:2214: handle_hc_chhltd_intr_dma: Channel 3, DMA Mode -- ChHltd set, but reason for halting is unknown, hcint 0x00000002, intsts 0x06000001
Dec 16 07:40:30 pi-star kernel: [ 1199.005351]
Dec 16 07:40:30 pi-star kernel: [ 1199.010535] usb usb1-port1: disabled by hub (EMI?), re-enabling...
Dec 16 07:40:30 pi-star kernel: [ 1199.010560] usb 1-1: USB disconnect, device number 2
Dec 16 07:40:30 pi-star kernel: [ 1199.010834] cdc_acm 1-1:1.0: failed to set dtr/rts
Dec 16 07:40:30 pi-star kernel: [ 1199.210540] Indeed it is in host mode hprt0 = 00021501
Dec 16 07:40:30 pi-star kernel: [ 1199.420321] usb 1-1: new full-speed USB device number 3 using dwc_otg
Dec 16 07:40:30 pi-star kernel: [ 1199.420429] Indeed it is in host mode hprt0 = 00021501
Dec 16 07:40:30 pi-star kernel: [ 1199.663823] usb 1-1: New USB device found, idVendor=1fc9, idProduct=0094, bcdDevice= 1.01
Dec 16 07:40:30 pi-star kernel: [ 1199.663832] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Dec 16 07:40:30 pi-star kernel: [ 1199.663836] usb 1-1: Product: MCU VIRTUAL COM DEMO
Dec 16 07:40:30 pi-star kernel: [ 1199.663840] usb 1-1: Manufacturer: NXP SEMICONDUCTORS
Dec 16 07:40:30 pi-star kernel: [ 1199.664358] cdc_acm 1-1:1.0: ttyACM1: USB ACM device
Dec 16 07:40:36 pi-star pistar-watchdog.service[1036]: Warning: Stopping ircddbgateway.service, but it can still be activated by:
Dec 16 07:40:36 pi-star pistar-watchdog.service[1036]: ircddbgateway.timer
Dec 16 07:40:38 pi-star systemd[1]: Starting ircDDBGateway Radio Servce...
Dec 16 07:40:38 pi-star systemd[1]: ircddbgateway.service: Control process exited, code=exited status=1
Dec 16 07:40:38 pi-star systemd[1]: Failed to start ircDDBGateway Radio Servce.
Dec 16 07:40:38 pi-star systemd[1]: ircddbgateway.service: Unit entered failed state.
Dec 16 07:40:38 pi-star systemd[1]: ircddbgateway.service: Failed with result 'exit-code'.
Dec 16 07:40:38 pi-star pistar-watchdog.service[1036]: Job for ircddbgateway.service failed because the control process exited with error code.
Dec 16 07:40:38 pi-star pistar-watchdog.service[1036]: See "systemctl status ircddbgateway.service" and "journalctl -xe" for details.
Dec 16 07:40:48 pi-star pistar-watchdog.service[1036]: Warning: Stopping timeserver.service, but it can still be activated by:

User avatar
m1dyp
Posts: 605
Joined: Sat Nov 16, 2019 8:03 am
Location: Hertfordshire, U.K.
Contact:

Re: Hotspot mode - Apparently stuck in TX

Post by m1dyp » Mon Dec 16, 2019 2:01 pm

Pi-Star:3.4.17 / Dashboard: 20191206
raspi 3b, 2 gig card

basic config then update

radio firm [c974b13] 19:50:20 dec 15 2019

runs ok, no errors

hope this helps someone

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

Re: Hotspot mode - Apparently stuck in TX

Post by VK3KYY » Mon Dec 16, 2019 11:09 pm

I advise you use the older / stable version 3.4.x

I've not tried v4.x for a month, but had problems last time I did try to use it

3.4.x is stable and works just fine

IW6CNM
Posts: 19
Joined: Mon Nov 18, 2019 5:57 am

Re: Hotspot mode - Apparently stuck in TX

Post by IW6CNM » Mon Dec 16, 2019 11:47 pm

Hi
same problem
pistar version 3.4.17
raspberry 3+
last gd77 fw

Image

hot spot goes stuck on my last call
it keeps stuck untill i press ptt again

thanks
73 de iw6cnm davide

User avatar
W0RMT
Posts: 178
Joined: Sat Nov 16, 2019 12:45 pm
Location: Louisville, CO USA

Re: Hotspot mode - Apparently stuck in TX

Post by W0RMT » Tue Dec 17, 2019 12:55 am

IW6CNM wrote:
Mon Dec 16, 2019 11:47 pm
Hi
same problem
pistar version 3.4.17
raspberry 3+
last gd77 fw

Image

hot spot goes stuck on my last call
it keeps stuck untill i press ptt again

thanks
73 de iw6cnm davide
Try the Tier 1 FW which has been stable in hotspot mode for some time. If the problem still exists with this version let us know.

Post Reply