Hi,
I have a strange problem. I bought a new DMR dual hotspot. Jumbospot V1.3 MMDVM_HS_Dual_Hat MMDVM on Pi3.
Everything is fine. But while listening to TG91, after 10 minutes the Pi_Star dashboard stops showing new QSOs and also the TYT MD-UV390 stops listening.
I have no static TGs defined on the Brandmeister.
When I push PTT, I start hearing the TG again and the Pi-Star dashboards starts displaying new QSOs.
As far as I know, on the repeaters there are such timeouts but not for personal hotspots.
My Pi-star version is 4.1.6
Thanks and 73s,
S.Ince
Pi-Star Dashboard and TYT390 listening stops after 10 minutes
Re: Pi-Star Dashboard and TYT390 listening stops after 10 minutes
I think I have a solution.
Dual (duplex) hotspots can't auto-static a TG like simplex hotspots do.
That's why disconnecting automatically after 10 minutes.
The solution is: Defining the TG as a static TG on the Brandmeister.
ıf you want to disconnect from the TG, since it is a very busy one, you can TG4000 and leave.
Am I right?
73s,
S.Ince
Dual (duplex) hotspots can't auto-static a TG like simplex hotspots do.
That's why disconnecting automatically after 10 minutes.
The solution is: Defining the TG as a static TG on the Brandmeister.
ıf you want to disconnect from the TG, since it is a very busy one, you can TG4000 and leave.
Am I right?
73s,
S.Ince
Re: Pi-Star Dashboard and TYT390 listening stops after 10 minutes
Hi,
this is not a "strange problem", more a "works as designed"
What you've done is called "dynamic booking" of a talk group. This is, when someone wishes to listen to a talk group, which is NOT static booked on a repeater. So the user does a short TX on this talkgroup to the repeater and the repater will book this TG from the BM master.
The BM master then will send all qsos on this TG to the repeater for a specific time after the first TX in this TG on this repeater. And THIS time is your "10 minutes".
So you have 2 possible actions to listen for a longer time to this TG:
this is not a "strange problem", more a "works as designed"
What you've done is called "dynamic booking" of a talk group. This is, when someone wishes to listen to a talk group, which is NOT static booked on a repeater. So the user does a short TX on this talkgroup to the repeater and the repater will book this TG from the BM master.
The BM master then will send all qsos on this TG to the repeater for a specific time after the first TX in this TG on this repeater. And THIS time is your "10 minutes".
So you have 2 possible actions to listen for a longer time to this TG:
- Do a short TX every 10minutes in this TG
- Book this TG static to your Hotspot
73s de Thomas, DG0OFZ
Re: Pi-Star Dashboard and TYT390 listening stops after 10 minutes
Yes, all correct.TB1BSI wrote: ↑Tue Feb 22, 2022 7:27 pm Dual (duplex) hotspots can't auto-static a TG like simplex hotspots do.
That's why disconnecting automatically after 10 minutes.
The solution is: Defining the TG as a static TG on the Brandmeister.
ıf you want to disconnect from the TG, since it is a very busy one, you can TG4000 and leave.
Am I right?
73s de Thomas, DG0OFZ
Re: Pi-Star Dashboard and TYT390 listening stops after 10 minutes
Duplex hotspots ARE repeaters in the realm of Brandmeister.
I don't know if keying up on 4000 disconnects a define STATIC talk group. After all, you defined it to be "always on" (static). You can, however, key up on a different talk group, which will become a dynamic entry (timing out after some period of time if not rekeyed, at which point the static group will return). As I recall, BM blocks other talk groups from being relayed for some time period, so the dynamic group would block your static until it times out (or is disconnected by command).
I think only the BM API on the Pi-Star admin page (or direct connection to BM configuration pages themselves) and make a long-term drop of a static group.
I don't know if keying up on 4000 disconnects a define STATIC talk group. After all, you defined it to be "always on" (static). You can, however, key up on a different talk group, which will become a dynamic entry (timing out after some period of time if not rekeyed, at which point the static group will return). As I recall, BM blocks other talk groups from being relayed for some time period, so the dynamic group would block your static until it times out (or is disconnected by command).
I think only the BM API on the Pi-Star admin page (or direct connection to BM configuration pages themselves) and make a long-term drop of a static group.
--
AF6VN
Dennis L Bieber
Re: Pi-Star Dashboard and TYT390 listening stops after 10 minutes
Oh yes!
I didn't read it complete...
TG4000 only disconnects dynamically booked TGs.
I didn't read it complete...
TG4000 only disconnects dynamically booked TGs.
73s de Thomas, DG0OFZ
Re: Pi-Star Dashboard and TYT390 listening stops after 10 minutes
Thank you Thomas, Thanks you Dennis
Well, I am new to DMR and used a simplex hotspot for 1 month then switched to duplex 2 days ago.
And yes you are right Dennis, my hotspot is now under the Repeaters section of Brandmeister, and this explains my other question, why I can't see my hotspot on the Brandmeister hotspot section, like I used to see before, with my simplex hotspot.
One topic, many answers, thanks a lot,
Hope to meet you on air and 73s,
Saruhan
Well, I am new to DMR and used a simplex hotspot for 1 month then switched to duplex 2 days ago.
And yes you are right Dennis, my hotspot is now under the Repeaters section of Brandmeister, and this explains my other question, why I can't see my hotspot on the Brandmeister hotspot section, like I used to see before, with my simplex hotspot.
One topic, many answers, thanks a lot,
Hope to meet you on air and 73s,
Saruhan