One TGID, Two Systems, Two Different Users

[mfn002]

I have recently come across a somewhat annoying problem when programming an XPR5550 I just got. I have two different systems that have the same TGID number. I've found I can't just enter the TGID twice with two different names, so is there another way to do this?

 

[N4KVE]

I have recently come across a somewhat annoying problem when programming an XPR5550 I just got. I have two different systems that have the same TGID number. I've found I can't just enter the TGID twice with two different names, so is there another way to do this?

Sorry, no. When you try to enter it a 2nd time it will say already entered, or something similar. These were business radios where there might be a few different TG's. No one ever figured this would happen.

 

[mfn002]

Sorry, no. When you try to enter it a 2nd time it will say already entered, or something similar. These were business radios where there might be a few different TG's. No one ever figured this would happen.

Thanks. I figured as much, but I just wanted to make sure.

 

[KevinC]

If they don't use the same radio ID's you can label those to differentiate between the two systems.

 

[N1GTL]

Hopefully Motorola will someday allow the entry of multiple digital IDs like you can with MDC. Until then we are stuck with a radio wide digital ID. Not helpful for those who want to use Capacity Plus and amateur DMR with the same radio.

 

[N4KVE]

Years ago when my friend set up his repeater, [nothing to do with D-Marc] where there are only 2 TG's. he chose 3175 for one TG because the repeater was on 443.175. That TG was called FLA DMR 2. Later on, D-Marc decides to use 3175 TG for SW. Since our users first assigned 3175 to say FLA DMR 2, when they tried to enter that same TG in their radios for the D-Marc system to say SW, they couldn't, as it was already taken. So anybody using 3175 on D-Marc had to see FLA DMR 2. We had 3175 first. Why D-Marc stole it, I'll never know, since the Plantation factory is 10 miles from our repeater.