New Overlay for DMRGateway - welcome your comments

Help with DMR issues
VE6DV
Posts: 42
Joined: Sun May 13, 2018 4:34 pm
Location: Edmonton, Alberta

Re: New Overlay for DMRGateway - welcome your comments

Post by VE6DV »

MW0MWZ wrote: Fri May 22, 2020 1:23 pm
VE6DV wrote: Thu May 21, 2020 4:20 pm IPSC2-QuadNet is setup for dual time slots. Out of curiosity, is your new overlay setup for a hotspot with a duplex board or a simplex board?

/edit - I believe I have figured this out. I had to modify your overlay to accommodate my simplex board:

Once I changed the rules to make everything on TS2 the overlay started working for me as intended.

Thanks for the help,

Jeff VE6DV
See my revised version of the rules in the top post;
Now you only need to change this one line:

Code: Select all

TGRewrite4=2,80001,1,1,9999
to

Code: Select all

TGRewrite4=2,80001,2,1,9999
So that all the re-writes send to Slot 2 on the network, and you only need this when using a simplex hotspot.
Outstanding! Thanks again, Andy. I will give this a try and let you know if I notice any issues.

Jeff VE6DV
73 - Jeff VE6DV
VE6DV
Posts: 42
Joined: Sun May 13, 2018 4:34 pm
Location: Edmonton, Alberta

Re: New Overlay for DMRGateway - welcome your comments

Post by VE6DV »

Not sure why, but your new configuration is still not working for me. The IPSC2 server dashboard shows that it is sending audio to my hotspot but my hotspot remains silent. However when I use this configuration it seems to work fine. Also with your configuration the DMR+ Parrot doesn't seem to work when I transmit to 89990. I wonder if it is something with the difference in hardware? I am running a single band DVMega hat.

[DMR Network 2]
Enabled=1
Address=168.235.109.210
Port=55555
TGRewrite0=2,8,2,9,1
TGRewrite1=2,80001,2,1,7
TGRewrite2=2,80505,2,505,1
TGRewrite3=2,80800,2,800,100
TGRewrite4=2,83801,2,3801,8
TGRewrite5=2,80009,2,9,9991
TypeRewrite=2,89990,2,9990
PCRewrite0=2,84000,2,4000,1001
SrcRewrite0=2,9,2,8,1
SrcRewrite1=1,1,2,80001,7
SrcRewrite2=2,505,2,80505,1
SrcRewrite3=2,800,2,80800,100
SrcRewrite4=2,3801,2,83801,8
SrcRewrite5=1,9,2,80009,9991
Password="PASSWORD"
Debug=0
Id=1234567
Name=DMR+_IPSC2-QUADNET
Options="TS1_1=1;TS1_2=235;TS1_3=3;TS1_4=13;TS1_5=133;TS1_6=315;TS1_7=320;TS1_8=505"

Ah the joys of learning new things. Troubleshooting and just finding what works. This is what amateur radio is all about.
73 - Jeff VE6DV
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New Overlay for DMRGateway - welcome your comments

Post by MW0MWZ »

VE6DV wrote: Fri May 22, 2020 7:03 pm Not sure why, but your new configuration is still not working for me. The IPSC2 server dashboard shows that it is sending audio to my hotspot but my hotspot remains silent. However when I use this configuration it seems to work fine. Also with your configuration the DMR+ Parrot doesn't seem to work when I transmit to 89990. I wonder if it is something with the difference in hardware? I am running a single band DVMega hat.

[DMR Network 2]
Enabled=1
Address=168.235.109.210
Port=55555
TGRewrite0=2,8,2,9,1
TGRewrite1=2,80001,2,1,7
TGRewrite2=2,80505,2,505,1
TGRewrite3=2,80800,2,800,100
TGRewrite4=2,83801,2,3801,8
TGRewrite5=2,80009,2,9,9991
TypeRewrite=2,89990,2,9990
PCRewrite0=2,84000,2,4000,1001
SrcRewrite0=2,9,2,8,1
SrcRewrite1=1,1,2,80001,7
SrcRewrite2=2,505,2,80505,1
SrcRewrite3=2,800,2,80800,100
SrcRewrite4=2,3801,2,83801,8
SrcRewrite5=1,9,2,80009,9991
Password="PASSWORD"
Debug=0
Id=1234567
Name=DMR+_IPSC2-QUADNET
Options="TS1_1=1;TS1_2=235;TS1_3=3;TS1_4=13;TS1_5=133;TS1_6=315;TS1_7=320;TS1_8=505"

Ah the joys of learning new things. Troubleshooting and just finding what works. This is what amateur radio is all about.
let me dig up a simplex board and get some testing done.... I'll come back to you shortly...
I will focus on TG 320, and link to Quadnet and let you know what I find out...
Andy

73 de MW0MWZ
http://pistar.uk
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New Overlay for DMRGateway - welcome your comments

Post by MW0MWZ »

OK here goes....

So I went back over my work, and back over the DMRGateway WiKi and I had totally mis-understood part of the functionality... oops, so if you read my rules and thought I was nuts, you were probably correct.

This ruleset seems to work pretty good (and does not require modification for duplex and simplex hotspots...

Code: Select all

[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=123456701
Name=DMR+_IPSC2-QUADNET
Options="Userlink=1;"
What to the re-writes do;
TGRewrite0=2,8,2,9,1
We swap TG8 on your hotspot to be TG9 on the network, this is mostly for the Reflectors;

TGRewrite1=2,80505,2,505,1
TG 505 should be on TS1 (on the network side) when you are a Repeater or running a Duplex hat (more on this later - stick with me).

TGRewrite2=2,80800,2,800,100
Everything from 800-899 should end up on TS2 (on the network side).

TGRewrite3=2,83801,2,3801,8
3801-3808 should end up on TS2 (on the network side).

TGRewrite4=2,89990,2,9990,1
Parrot needs to be on TS 2 only on the network side.

TGRewrite5=2,80001,1,1,9999
Catch-all rule, so anything not matched by the above rules is sent to the network on TS1 (again more on this in a moment).

TGRewrite6=2,80001,2,1,9999
2nd Catch all rule to match anything we missed above and send it to TS2 (on the network) - the sharp eyed among you will notice that this rule should *NEVER* get a hit, since the one above will be hit first - yes I agree, but again, stick with me :)

PCRewrite0=2,84000,2,4000,1001
Catch the Private calls used for Reflectors.


OK so thats the explanation, now back to that werird pair of rules that made no sense;
TGRewrite4=2,80001,1,1,9999
TGRewrite5=2,80001,2,1,9999

This looks crazy, and it is a little, but in the very best ways :)
IPSC2+ knows if you connect simplex or duplex, if you connect simplex, it sends the traffic back on TS 2, always - very handy, if you connect duplex it sends it back on either TS1 or TS2 depending on where that TalkGroup should live and where it is being used. The most important thing, and the bit that caught me out because I was not awake, is that these same rules are matched in BOTH directions, so when you write the outbound call from your HT on 80320 (TS2) for example, it is sent to the network as 320 on TS1... Great, now the SAME rule is matched in reverse when the traffic comes back for TG 320 on TS1 form the network - and that all works as expected on duplex boards / repeaters... however...
When you connect a simplex board, the network side helps you out by sending everything back on TS2, and none of the rules were triggered and so it all went into a black hole.... here is where the 2nd rule comes in, that DOES match the traffic now coming back on TS2, and correctly re-writes it back to 80320 TS2 for your radio.

I really made that look hard, but thanks for sticking with it :) this is why I need your help testing my moderately nutty ideas :)

I have already updated all my posts in this thread with the new rule-set - give it a shot pls.
Andy

73 de MW0MWZ
http://pistar.uk
VE6DV
Posts: 42
Joined: Sun May 13, 2018 4:34 pm
Location: Edmonton, Alberta

Re: New Overlay for DMRGateway - welcome your comments

Post by VE6DV »

Will do, Andy. I will install it in just a few minutes and let you know how things work out. Thank you also for the explanation for what each line does. I was going to go through it and try and figure it out later today so great timing.

The other thing that has been great timing is over the past few weeks I have also been trying to get my hotspot setup for multi network DMR. With the help of Cliff VE6PLC I was able to get it mostly working however there were still some flaws such as networks talking over top of one another, lack of private call support etc. Your configuration has helped to put me on the right path and has gotten around those flaws in the previous configuration. I am about to publish an article in the amateurradio.com newsletter and I will be sure to give you and Cliff credit in the article once all of the rough edges are worked out for the final configuration.

Thanks again for all of the help.
73 - Jeff VE6DV
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New Overlay for DMRGateway - welcome your comments

Post by MW0MWZ »

Private calls is potentially a problem, for the most part I tend to have mine setup such that anything that isnt accounted for specifically in the rules, is pushed out of Network 1.

If it would help I can post my full config here to that you can compare notes.
I've also been re-testing a few things that I had expected to work a certain way, and they didn't - so I am cleaning up my config also...
Andy

73 de MW0MWZ
http://pistar.uk
VE6DV
Posts: 42
Joined: Sun May 13, 2018 4:34 pm
Location: Edmonton, Alberta

Re: New Overlay for DMRGateway - welcome your comments

Post by VE6DV »

I really liked your solution to send all private calls out to network 1. It makes sense to do this as Brandmeister, at least in North America, is the more popular network and that is where people will more easily be reached. Plus if everyone uses this configuration allowing access to multiple DMR networks, there shouldn't be a problem with them being able to reach one another.

One thing I can't quite figure out is if you try to use the Parrot on DMR+ (talkgroup 9990, 89990 in the code plug) nothing comes back. Watching the IPSC2-QuadNet server dashboard the hotspot isn't routing the call to DMR+. When you have a moment would you mind giving it a try to see if maybe I have something messed up on my end? It worked with the other configuration, but not this one for some reason. Most likely this shouldn't be an issue as the Brandmeister parrot works. But I know someone will probably ask.

Thanks,

Jeff VE6DV
73 - Jeff VE6DV
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New Overlay for DMRGateway - welcome your comments

Post by MW0MWZ »

VE6DV wrote: Sat May 23, 2020 9:02 pm One thing I can't quite figure out is if you try to use the Parrot on DMR+ (talkgroup 9990, 89990 in the code plug) nothing comes back. Watching the IPSC2-QuadNet server dashboard the hotspot isn't routing the call to DMR+. When you have a moment would you mind giving it a try to see if maybe I have something messed up on my end? It worked with the other configuration, but not this one for some reason. Most likely this shouldn't be an issue as the Brandmeister parrot works. But I know someone will probably ask.

Thanks,

Jeff VE6DV
I'll post the full config for each network back here tomorrow for you, but the PC routing is in the [DMR Network 1] on the first page of this thread.

Parrot on DMR+, yeah that should be to-able, I'll work on that in the morning (well later in the morning) too.. :)
Andy

73 de MW0MWZ
http://pistar.uk
VE6DV
Posts: 42
Joined: Sun May 13, 2018 4:34 pm
Location: Edmonton, Alberta

Re: New Overlay for DMRGateway - welcome your comments

Post by VE6DV »

The Parrot on DMR+ is a group call. Odd that it's not working, not even sending a transmission for 89990 to the DMR+ network. Thanks for having a look. No rush, just whenever you happen to get around to it. I'll keep at it as well, maybe I will stumble across why it's not working.
73 - Jeff VE6DV
User avatar
MW0MWZ
Site Admin
Posts: 1505
Joined: Wed Apr 04, 2018 9:15 pm
Location: Wales, UK
Contact:

Re: New Overlay for DMRGateway - welcome your comments

Post by MW0MWZ »

VE6DV wrote: Sun May 24, 2020 2:27 am The Parrot on DMR+ is a group call. Odd that it's not working, not even sending a transmission for 89990 to the DMR+ network. Thanks for having a look. No rush, just whenever you happen to get around to it. I'll keep at it as well, maybe I will stumble across why it's not working.
On DMR+ parrot seems to be required to be on TS2 only;

Code: Select all

[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=123456701
Name=DMR+_IPSC2-QUADNET
Options="Userlink=1;"
Section updated to account for it....
Andy

73 de MW0MWZ
http://pistar.uk
Post Reply