forum.pistar.uk

Even though the HotSpot says TS1 is disabled, I can still talk to groups on TS1 and see the activity on the IPSC2 Dashboard. So can someone tell me what's happening?
I assume that the hotspot only uses TS2 but some magic happens on the network side to redirect my traffic to the correct TS? I still use TS1 and set TS1 static groups and program my radio to the correct TS... seems to work but don;t understand the disabled state on the pi-star dashboard.

Time slots are specific to the radio NODE one is connecting on (ie: between your radio and the repeater/hotspot; same with color code). They mean nothing to the various masters that handle talk group routing. It is the repeater owner/operator who decides which talk groups appear on which time slot (though there may be a convention that TS1 is "local" and TS2 is "network linked"). The only thing the network relies upon is the talk group (or private individual) number.

A Simplex hotspot can only run one timeslot. DMO.
You need a duplex install utilising separate tx and rx to benefit from dual timeslot use.

Sent from my SM-G935F using Tapatalk

makes sense - thanks

Copy/replace DMR+ data over Brandmeisterdata to have access for another TG in a simplex hotspot.
Use "DMR Network 2" over "DMR Network 1" in "Expert/Full Edit: DMR GW".
Copy "adress", "port" and change password (from DMR+), add the "Options="StartRef=xxxx;RelinkTime=15;UserLink=1;TS1_1=xxx;" -line at end.
Just apply changes, you can well reboot your hotspot.
DO NOT apply ever "general-configuration-settings" or you will lose the new data!
Use it as a "Brandmeister-hack"! Brandmeister can use TG1 and TG2 well. Cheers!

EXAMPLE:

[DMR Network 1]
#Enabled=1
#Address=86.125.185.64
#Port=55555
#TGRewrite0=2,8,2,9,1
#PCRewrite0=2,84000,2,4000,1001
#TypeRewrite0=2,9990,2,9990
#SrcRewrite0=2,4000,2,9,1001
#PassAllPC0=1
#PassAllTG0=1
#PassAllPC1=2
#PassAllTG1=2
#Password="PASSWORD"
#Debug=0
#Location=0
#Id=2263104
#Name=Hakintosh
#Options="StartRef=4000;RelinkTime=15;UserLink=1;TS1_1=226;TS2_1=2263;"

[DMR Network 2]
#Enabled=0
#Address=86.125.185.64
#Port=55555
#TGRewrite0=2,8,2,9,1
#PCRewrite0=2,84000,2,4000,1001
#Password="PASSWORD"
#Debug=0
#Id=2263104
#Location=0
#Name=DMR+_IPSC2-Romania
#Options="StartRef=4670;RelinkTime=15;UserLink=1;TS1_1=226;"

Std setup Simplex hotspot (DMO) doesnt care abt timeslot. Traffic will flow regardless of what tg it comes into the hotspot over rf and or the interwebs.

It Only matters if using duplex install and /or if any tg rewrites are added.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

M1DNS wrote: ↑Wed Jan 18, 2023 1:25 pm Std setup Simplex hotspot (DMO) doesnt care abt timeslot. Traffic will flow regardless of what tg it comes into the hotspot over rf and or the interwebs.

It Only matters if using duplex install and /or if any tg rewrites are added.

Sent via smoke signals from my SM-G935F M1DNS (Admin)

You can't add a switch in pi-star for TS1 or TS2. All traffic goes in Pi-Star in TS2 only (except Brandmeister).
If you want talk in DMR+/Ipsc2 in TG1 (i'm in Romania) - you can't. Even if you switch radio or cps to TS1.
That's the topic about. In simplex. I made allready qso's in Ipsc that way. No problems.
With or without "Promiscuous mode".

Still good working.

I ran into this situation while I was trying to run an XLX Master as well as DMR Gateway. The problem was that I had the wrong modem selected. I chose one that said Raspberry Pi Hat (Dual Band). Once I selected the MMDVM Raspberry Pi Hat (GPIO) the problem fixed and both TS1 and TS2 are now enabled and both work simultaneously.