Author Topic: Time Slot 1 not viable on Prime?  (Read 137 times)

0 Members and 0 Guests are viewing this topic.

Offline K9DJN

  • Newbie
  • *
  • Posts: 3
  • Referrals: 0
Time Slot 1 not viable on Prime?
« on: February 06, 2021, 07:58:03 am »
I have a very simple DMR Gateway config where all TGIF traffic goes to TS1, with the "other network" on TS2. It works just fine with Legacy, but I have yet to be able to use Self Care on Prime to set a talk group on TS1. The API Manager on Legacy allows me to change TG's without a PTT burst, but when Self Care worked I could also change them there to either Time Slot.

My DMR hostpot uses a duplex board, so this is how I run split networks. I also have two DMR radios, one for each Time Slot, so no need for complicated prefixes. Has anyone else tried to use TS1 on Prime?

Doug
K9DJN

Share on Facebook Share on Twitter


Offline KG6RUT

  • Newbie
  • *
  • Posts: 5
  • Referrals: 0
  • Call Sign: KG6RUT
Re: Time Slot 1 not viable on Prime?
« Reply #1 on: February 07, 2021, 11:35:25 am »
I have my duplex, well duplexing but I know others that do it your way.....So yes I have a Static set on TS1. I assume I set it trough Selfcare, but since I tweaked several pi-star files to see the TGIF Manager section on the Admin page, it may have been set through that.....did it weeks ago and cant remember.

Offline K9DJN

  • Newbie
  • *
  • Posts: 3
  • Referrals: 0
Re: Time Slot 1 not viable on Prime?
« Reply #2 on: February 07, 2021, 01:42:16 pm »
Interesting. So there is an API on Prime? Any time I have tested it, there is no more TGIF Manager on the Admin page of PiStar that I can see. But I never rebooted after making the change. Maybe I'll try that next.

You might try again with Self Care sometime. What is does for me is when I set a TG on TS1, it really sets it on TS2 no matter what.

Offline KG6RUT

  • Newbie
  • *
  • Posts: 5
  • Referrals: 0
  • Call Sign: KG6RUT
Re: Time Slot 1 not viable on Prime?
« Reply #3 on: February 07, 2021, 01:45:45 pm »
hmm, that sort of reminds me that I think I had that as well...so I mustve set it thru the pi-star UI.....port 5040 isnt opened yet so if you were to modify the files as I have, you wont see any sessions, but IIRC, setting the TS did in fact work...GL!

Offline kc5afm

  • Newbie
  • *
  • Posts: 1
  • Referrals: 0
Re: Time Slot 1 not viable on Prime?
« Reply #4 on: May 27, 2021, 11:35:08 pm »
Gentlemen, are you guys still using duplex boards on TGIF? I've noticed an odd issue with TS1 which I've been able to reproduce it on different hotspots, where MMDVM seems to be crashing and restarting and then after it comes back up, only the talkgroup from TS2 works and I never hear anything on TS1 (even though if I talk on TS1 it is heard on the talkgroup, but is one -way).  This is easy to see if I set both TS1 and TS2 to the same talkgroup as I have in the logs below.  You will see both TS1 and TS2 are receiving the same TG, then it appears MMDVM crashes and restarts and then only TS2 is receiving the TG. 

I'll likely post this in the pistar forums too, just wondered if anyone else saw this as it may only affect duplex boards.

The hotspots are all running Pistar 4.1.4 with firmware 1.5.2. 

Here's what I see in the logs, and this seems to be caused by something cron.daily is running (I haven't made any changes to cron, not using dmr gateway in fact dmrgateway shows disabled, etc. just standard config):

M: 2021-05-26 07:56:46.882 DMR Slot 1, received network end of voice transmission from VE3RD to TG 31665, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 08:11:08.204 DMR Slot 2, received network voice header from K9SAH to TG 31665
M: 2021-05-26 08:11:08.209 DMR Slot 1, received network voice header from K9SAH to TG 31665
M: 2021-05-26 08:11:08.313 DMR Slot 2, received network end of voice transmission from K9SAH to TG 31665, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 08:11:08.318 DMR Slot 1, received network end of voice transmission from K9SAH to TG 31665, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 08:12:23.181 DMR Slot 2, received network voice header from K9SAH to TG 31665
M: 2021-05-26 08:12:23.187 DMR Slot 1, received network voice header from K9SAH to TG 31665
M: 2021-05-26 08:12:23.275 DMR Slot 2, received network end of voice transmission from K9SAH to TG 31665, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 08:12:23.280 DMR Slot 1, received network end of voice transmission from K9SAH to TG 31665, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 08:57:07.367 Closing the MMDVM
I: 2021-05-26 08:57:08.311 Stopped the DMR Id lookup reload thread
M: 2021-05-26 08:57:08.311 DMR, Closing DMR Network
I: 2021-05-26 08:57:08.311 MMDVMHost-20200615_Pi-Star_v4 exited on receipt of SIGTERM
I: 2021-05-26 08:57:14.854 This software is for use on amateur radio networks only,
I: 2021-05-26 08:57:14.854 it is to be used for educational purposes only. Its use on
I: 2021-05-26 08:57:14.854 commercial networks is strictly prohibited.
I: 2021-05-26 08:57:14.854 Copyright(C) 2015-2020 by Jonathan Naylor, G4KLX and others
M: 2021-05-26 08:57:14.854 MMDVMHost-20200615_Pi-Star_v4 is starting
M: 2021-05-26 08:57:14.854 Built 17:21:54 Jun 15 2020 (GitID #3313fe8)
~~skipping the dump of parameters here

It seems MMDVM is crashing and restarting and when it comes back, I only have TS2, not receiving anything from TS1:

M: 2021-05-26 09:01:07.426 DMR Slot 2, received network voice header from K4WPO to TG 31665
M: 2021-05-26 09:01:08.915 DMR Slot 2, received network end of voice transmission from K4WPO to TG 31665, 1.5 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 09:14:41.064 DMR Slot 2, received network voice header from W8TVR to TG 31665
M: 2021-05-26 09:14:42.621 DMR Slot 2, network watchdog has expired, 0.1 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 09:30:54.628 DMR Slot 2, received network voice header from N8KQ to TG 31665
M: 2021-05-26 09:30:55.167 DMR Slot 2, received network end of voice transmission from N8KQ to TG 31665, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2021-05-26 09:36:06.424 DMR Slot 2, received network voice header from VK6KBY to TG 31665
M: 2021-05-26 09:36:08.401 DMR Slot 2, received network end of voice transmission from VK6KBY to TG 31665, 1.9 seconds, 0% packet loss, BER: 0.0%



pi-star@pi-star(rw):pi-star$ grep Stopped *
MMDVM-2021-05-26.log:I: 2021-05-26 08:57:08.311 Stopped the DMR Id lookup reload thread
MMDVM-2021-05-27.log:I: 2021-05-27 08:57:08.228 Stopped the DMR Id lookup reload thread


I see that cron.daily runs every morning on the 57 minute of hour 3, which would be 08:57 for central time:

57 3   * * *   root   mount -o remount,rw / && cd / && run-parts --report /etc/cron.daily

in syslog, I see:
May 27 03:57:01 pi-star CRON[17744]: (root) CMD (mount -o remount,rw / && cd / && run-parts --report /etc/cron.daily)
May 27 03:57:01 pi-star kernel: [887565.720408] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
May 27 03:57:02 pi-star kernel: [887566.604431] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
May 27 03:57:04 pi-star pistar-watchdog.service[8216]: Warning: Stopping dmrgateway.service, but it can still be activated by:
May 27 03:57:04 pi-star pistar-watchdog.service[8216]:   dmrgateway.timer
May 27 03:57:06 pi-star systemd[1]: Starting DMRGateway Radio Servce...
May 27 03:57:06 pi-star systemd[1]: dmrgateway.service: Control process exited, code=exited, status=1/FAILURE
May 27 03:57:06 pi-star systemd[1]: dmrgateway.service: Failed with result 'exit-code'.
May 27 03:57:06 pi-star systemd[1]: Failed to start DMRGateway Radio Servce.
May 27 03:57:06 pi-star pistar-watchdog.service[8216]: Job for dmrgateway.service failed because the control process exited with error code.
May 27 03:57:06 pi-star pistar-watchdog.service[8216]: See "systemctl status dmrgateway.service" and "journalctl -xe" for details.
May 27 03:57:07 pi-star systemd[1]: Stopping PiStar-Watchdog Service Watchdog...
May 27 03:57:07 pi-star pistar-watchdog.service[18085]: Killing pistar-watchdog PID 8218
May 27 03:57:07 pi-star systemd[1]: pistar-watchdog.service: Main process exited, code=killed, status=15/TERM
May 27 03:57:07 pi-star systemd[1]: pistar-watchdog.service: Succeeded.
May 27 03:57:07 pi-star systemd[1]: Stopped PiStar-Watchdog Service Watchdog.
May 27 03:57:07 pi-star systemd[1]: Stopping MMDVMHost Radio Servce...
May 27 03:57:07 pi-star mmdvmhost.service[18091]: Killing MMDVMHost PID 8208
May 27 03:57:08 pi-star systemd[1]: mmdvmhost.service: Succeeded.
May 27 03:57:08 pi-star systemd[1]: Stopped MMDVMHost Radio Servce.

What could be causing it to try to restart the services?


 

Related Topics

  Subject / Started by Replies Last post
1 Replies
142 Views
Last post May 12, 2019, 01:09:57 pm
by N1KK
0 Replies
73 Views
Last post May 12, 2019, 11:39:24 am
by ke5cdk
2 Replies
107 Views
Last post February 29, 2020, 11:27:06 am
by N1KK
2 Replies
112 Views
Last post June 20, 2020, 05:45:21 pm
by KO4DJM
2 Replies
23 Views
Last post February 08, 2021, 02:15:08 pm
by nj3h