"Odd" behavior regarding unique/actual Radio IDs and DSDplus.radios file

[wx2watch]

Hi All, I’m currently running DSDplus2p390 and I am monitoring a federal (NPS) phase 1, P-25 system with the goal of identifying the individual handheld radios, as “gathered” from the DSDplus.radios file. However, I have encountered some odd behavior regarding the names/radio ID of several radios.

When the AllSeenRadios window shows the “realtime” radio traffic IDs , at least three radios of this group (823, 854, 882) ALL display as 559 and NOT as a unique ID even in DSDplus.radios. (i.e. they do not appear at all within the file but I know they exist – see next paragraph)

(I have identified approximately 60 radios, all with a unique ID number. I also happened to have physical possession of the three radios in question that do not appear in the DSDplus.radios file)

Maybe a bug with DSDplus or could it be a programming issue within the Moto system set-up?

Can anyone tell me what parameter DSDplus is looking at to cause this behavior?

(i.e. Obviously the Motorola systems “knows” all the radios but DSDplus appears to not know all.)

Thanks,
John

 

[cg]

Where are you getting your info from as to 823, 854, 882? Etched into the front of the radio? DSDPlus simply reports the data seen over the P25 signal. I doubt those three IDs are somehow a bug in the program where there is no history of similar reports for the past however many years that the program has been out.
With the limited information given, I would guess a programmer cloned the radios and didn't change the radio ID on the target radios.

chris

 

[wx2watch]

Where are you getting your info from as to 823, 854, 882? Etched into the front of the radio? DSDPlus simply reports the data seen over the P25 signal. I doubt those three IDs are somehow a bug in the program where there is no history of similar reports for the past however many years that the program has been out.
With the limited information given, I would guess a programmer cloned the radios and didn't change the radio ID on the target radios.

chris

Yes, the IDs are engraved on the radios I had access to. Not trying to bash DSDplus! I was just wondering about what parameters it (and the Moto programming) look at to determine the true ID of the radio in question. (please note I'm not saying I would understand the technical jargon but Chris' explanation sounds on target to me. ) THANKS for the response.

 

[Ubbe]

Yes, the IDs are engraved on the radios I had access to.

Doesn't the other two radios display the ID of the first radio if you push the PTT, or even do a private call between them?

/Ubbe

 

[wx2watch]

Doesn't the other two radios display the ID of the first radio if you push the PTT, or even do a private call between them?

/Ubbe

To answer Ubbe's questions:

1)The "odd" radios do display on other Moto HTs as 559 when I transmit with them.

2) Unfortunately, I don't know anything about private call - I'm just a "push to talk" user on this system.


So, I'm gonna go with Chris' explanation. (Probably best for me to let this go rather than bumping a request up the chain of command... ha,ha)

And once again, thanks to all for your interest in solving/explaining this non-issue to me.

 

[slicerwizard]

The "odd" radios do display on other Moto HTs as 559 when I transmit with them.

Well, there's your answer - they're clones.

 

[GTR8000]

Sounds like whoever programmed them forgot to change the subscriber ID when cloning from the template codeplug. Oops. Have them sent back to the radio shop to get the correct ID's in them.

 

[KevinC]

Sounds like whoever programmed them forgot to change the subscriber ID when cloning from the template codeplug. Oops. Have them sent back to the radio shop to get the correct ID's in them.

I wonder how may “wrong audio” issues this has caused?