Notes.txt said:DSD+ 2.165
...
...
Added support for the DMR TIII CPS-P3 numbering plan. If all talkgroups and radio IDs
seen on a TIII system only use values in the range 1048577 to 16743880, the operators
are likely using CPS-P3. If ", CPS-P3" is appended to the network's entry in the
DSDPlus.networks file, DSD+ will translate the AI (air interface) talkgroup and radio
numbers to their equivalent CPS-P3 values. Do NOT make this change for TIII systems
that are not using CPS-P3.
Original .networks file entry: TIII, 1000:13, "AcmeInc", 5
Original talkgroup: 1048577
Original radio ID: 1048600
Updated .networks file entry: TIII, 1000:13, "AcmeInc", 5, CPS-P3
CPS-P3 talkgroup: 328-20-900
CPS-P3 radio ID: 328-20-223
CPS-P3 talkgroup format: prefix-fleet-group
CPS-P3 radio ID format: prefix-fleet-unit
Prefix range is 328 to 806; typically, different prefix ranges are assigned
to each radio shop / airtime provider in a large TIII network
Fleet range is 20 to 89
Group range is 900 to 999
Fleets 20 to 41 can have unit values from 200 to 899
Fleets 42 to 89 are limited to unit values 200 to 549
Hello, the DMR BS regular relay I am talking about is not a TIII relayThis is what the DSDPlus v2.368 Notes.txt has to say about it.
Hello, the TIII control channel shows the ch channel number in the dsd+This is what the DSDPlus v2.368 Notes.txt has to say about it.
I thought you said it was a "DMR BS conventional relay".Hello, the TIII control channel shows the ch channel number in the dsd+
Show what?What is the reason why dsd+event LOG does not show these
This is displayed by the TIII control channel dsdThen going by what I posted from the notes.txt, support is only for the DMR TIII CPS-P3 numbering plan.
I thought you said it was a "DMR BS conventional relay".
Now there is a TIII control channel involved.
Show what?
Hello, TIII control channel shows ch channel number in dsd+, dsd+ event LOG does not show what is the reason, only shows neighbor and CCThen going by what I posted from the notes.txt, support is only for the DMR TIII CPS-P3 numbering plan.
I thought you said it was a "DMR BS conventional relay".
Now there is a TIII control channel involved.
Show what?
Hello, does DMR Tier 2 support converting CPS-P3It is very confusing what you are asking. First you seemed to ask what change needs to be made to the .NETWORKS file for CPS-P3 conversion.
Post 2 references the part in the DSDPlus Notes file where you find the information
Then you say it is not trunked but post lines from Tier III (trunking)
Did you edit your DSDPlus.NETWORKS file to enable CPS-P3 dialing scheme?? Are all the frequencies populated in the DSDPlus Frequencies file?
hello, one more questionIt is very confusing what you are asking. First you seemed to ask what change needs to be made to the .NETWORKS file for CPS-P3 conversion.
Post 2 references the part in the DSDPlus Notes file where you find the information
Then you say it is not trunked but post lines from Tier III (trunking)
Did you edit your DSDPlus.NETWORKS file to enable CPS-P3 dialing scheme?? Are all the frequencies populated in the DSDPlus Frequencies file?

- The version I am using is the latest 2.368 Neighbor repeats the problem I don't know why?When I look at the ETSI TII standard, they talk about dialing schemes but don't refer to CPS-P3. The DMR standard allows manufacturers to add options to their products. I found one reference to it in a Hytera document but it doesn't say much about it
Couple of other points...
- Verify that you are using the latest version of DSDPlus, I recall that the repeating Neighbor list was fixed.
- You also are not doing Voice Following so none of the channel information seen on the voice channels is provided.
- Have you populated your files for the system? NETWORKS, FREQUENCIES, SITES?
I would try running DSD+ in CC monitoring mode or combined CC/VC monitoring mode. Channel grants might be ignored when not in a CC monitoring mode.- the channel I'm on is the TIII control channel, I just need the Event Log to show tgt and src and ch
Hello, running DSD+ in CC monitor mode or CC/VC combined monitor mode does not show channel authorization after my tests. Grant/LateEntry only shown in dsd+ data filesI would try running DSD+ in CC monitoring mode or combined CC/VC monitoring mode. Channel grants might be ignored when not in a CC monitoring mode.
For the repeating neighbour entries, I'd email a raw audio sample to the fastlane address. Looks like a bug.

I have populated the file you mentioned, including the frequencyThere is no Event to log as you have it set for control channel only (no voice). That shows at the top of the screenshot "No VF"
You need to populate the files I mentioned. If it is done, go to the Control Tab and choose "Combined CC/VC monitor."
You already have 3 channels (6 slots) showing.
Channel 509/510 (Control Channel), Channel 689/690 (Voice) and 793/794 (voice). You need to determine the frequencies that match with activity on Ch 690 & 793 and enter them along with the control channel frequency.
