building frequency , site loader and site files

[bigears323]

when building frequency and the 2 site files for DMR Motorola Capacity Plus Multi Site (TRBO)
or DMR Motorola Connect Plus (TRBO)
do we list them as DMR or Cap+ for the reference lines to decode properly eg;

;Acces Communications (Quebec) 8044 DMR Motorola Connect Plus (TRBO) these decode as dmr
DMR, 167, 001, 01, 451.400, 0.0, 0
DMR, 167, 001, 01, 451.400, 0.0, 0
DMR, 167, 001, 02, 452.775, 0.0, 0
DMR, 167, 001, 02, 452.775, 0.0, 0

;*Administration Portuaire Montreal 10553 DMR Motorola Capacity Plus Single Site (TRBO) these decode as cap+
Cap+, 10553, 001, 01, 423.0500, 0.0, 0
Cap+, 10553, 001, 03, 423.6125, 0.0, 0
Cap+, 10553, 001, 05, 422.8500, 0.0, 0

 

[slicerwizard]

Use DMR for conventional channels.

Use Cap+, Con+, TIII for trunked DMR channels.

Select pseudo network IDs for Cap+ systems.

Use optional DCC field when more than one DMR site can be RX'd on a given RF channel.


; DSD+ frequency file
;
; line format:
;
; protocol, network ID, site number, OTA channel number, TX frequency, RX frequency, sort order [, DCC]
;
;
; use site number = 0 for network-wide definition
;
; use 0.0 for unknown frequencies
;
; use sort order = 0 to sort by OTA channel number
;
;
; protocols:
;
; ProVoice
; P25
; D-Star
; Fusion
; IDAS
; NEXEDGE48
; NEXEDGE96
; dPMR
; DMR
; Cap+
; Con+
; TIII
; XPT

...

 

[aps_ak]

Select pseudo network IDs for Cap+ systems

Pardon if this is a silly question - but does this essentially mean you “make up” network IDs? So if I have two separate Cap+ systems, I can call one system ID 1 and the other system ID 2?

 

[Kazzaw]

Yep - Cap+ systems don't have a network ID, but to differentiate the different systems they need to be configured with different IDs

 

[aps_ak]

Yep - Cap+ systems don't have a network ID, but to differentiate the different systems they need to be configured with different IDs

Thanks! This resolved a question I had pop up today.