DMR+ traffic seems to go to BM network

Help with DMR issues
Post Reply
n4bjh
Posts: 5
Joined: Fri Aug 13, 2021 4:02 pm

DMR+ traffic seems to go to BM network

Post by n4bjh »

I'm using the DMRGateway and using BM TGIF DMR+ and DMR2YSF on the pistar. Below is the DMR+ and BM sections.
This may have just started - because I think I got DMR+ working fine... but when I look at the quad dashboard-I see my notspot, I see the static groups (like 321). When I key my HH on 80321, I don't see anything on the IPSC2 dashboard, but on the pistar admin/dashboard, it shows 80321 as a dynamic TG on BM. I tried group and private 80321. This implies to me the code is misdirecting the traffic to BM instead of DMR+. The HH is set to monitor mode so I should hear everything.

I can go on Dude-star with my cellphone and talk on DMR+ TG321 and I hear it on the HH - so it works in that direction.

I'm pretty new and don't pretend to 100% understand this code - but it appears to me that it should direct 8xxxx to DMR+ (although I guess the default is to BM). Also do I need something special for TG 5000 (status) sinilar to TG 4000 (clear)?

thanks for helping a relative newbie

Pi-star 4.1.5 on pi zero w, HH is BTech 6x2; both up to date.

Code: Select all

[DMR Network 1]
Enabled=1
Address=3104.master.brandmeister.network
Port=62031
TGRewrite0=2,9,2,9,1
PCRewrite0=2,94000,2,4000,1001
TypeRewrite0=2,9990,2,9990
SrcRewrite0=2,4000,2,9,1001
PassAllPC0=1
PassAllTG0=1
PassAllPC1=2
PassAllTG1=2
Password="9195568589"
Debug=0
Location=1
Id=317970610
Name=BM_3104_United_States

[DMR Network 2]
Enabled=1
Address=168.235.109.210
Port=55555
TGRewrite0=2,8,2,9,1
TGRewrite1=2,80505,2,505,1
TGRewrite2=2,80800,2,800,100
TGRewrite3=2,83801,2,3801,8
TGRewrite4=2,89990,2,9990,1
TGRewrite5=2,80001,1,1,9999
TGRewrite6=2,80001,2,1,9999
PCRewrite0=2,84000,2,4000,1001
Password="PASSWORD"
Debug=0
Id=317970610
Location=0
Name=DMR+_IPSC2-QUADNET
Options="StartRef=4000;RelinkTime=60;UserLink=1;TS1_1=9;TS1_2=310;TS1_3=320;TS1_4=321;TS1_5=323;"
Last edited by Anonymous on Thu Sep 09, 2021 5:57 pm, edited 1 time in total.
Reason: Next time use a [code] [/code] block on lengthy log postings.
Post Reply