XPR, XiR, DGP or DP: which name to order
This catalogue records 156 regional counterpart names across 76 identifiers. They are not extra products — they are the same hardware under the names each region sold it as.
By protocol
P25 two-way radios
P25 is an interoperability standard, which is why programme procurement tends to name it instead of a manufacturer. The identifiers below are those this catalogue records as supporting P25. That is a protocol presence recorded per identifier — it is not a statement about which configuration of P25 a given build implements.
Identifiers in this collection
Derived from the catalogue at build time. Nothing on this page is transcribed by hand, so it cannot disagree with the identifier pages it links to.
| Identifier | Series | Protocols | Frequency band | Channel capacity | Ingress protection |
|---|---|---|---|---|---|
| APX 1000 Model 1.5 Single Knob | APX | P25 | Single-band VHF/UHF/700/800/900 MHz; P25 | 512 | IP67 |
| APX 1000 Model 2 Single Knob | APX | P25 | Single-band VHF/UHF/700/800/900 MHz; P25 | 512 | IP67 |
| APX 1000 Model 3 Single Knob | APX | P25 | Single-band VHF/UHF/700/800/900 MHz; P25 | 512 | IP67 |
| APX 1500 O2 Control Head Vehicle Mount Black | APX | P25 | VHF/UHF/700/800 MHz; P25 | 512 | IP54; up to IP56 on selected models or with the O2 control head |
| APX 2000 Model 2 Dual Knob | APX | P25 | Single-band VHF/UHF/700/800/900 MHz; P25 | 1000 | IP67 |
| APX 2000 Model 3 Dual Knob | APX | P25 | Single-band VHF/UHF/700/800/900 MHz; P25 | 1000 | IP67 |
| APX 2500 O7 Control Head Vehicle Mount Black | APX | P25 | VHF/UHF/700/800 MHz; P25 | 512 (standard); 1000 (extended) | IP54; up to IP56 on selected models or with the O2 control head |
| APX 4000 Model 2 Dual Knob | APX | P25 | Single-band VHF/UHF/700/800 MHz; P25 | 512 (standard); 1000 (Enhancement Level 1) | IP67 |
| APX 4000 Model 3 Dual Knob | APX | P25 | Single-band VHF/UHF/700/800 MHz; P25 | 512 (standard); 1000 (Enhancement Level 1) | IP67 |
| APX 4000 XH Model 3 Dual Knob | APX | P25 | Single-band VHF/UHF/700/800 MHz; P25 | 512 (standard); 1000 (Enhancement Level 1) | IP67 |
| APX 4500 O2 Control Head Vehicle Mount Black | APX | P25 | VHF/UHF/700/800 MHz; P25 | 512 (standard); 1000 (extended) | IP54; up to IP56 on selected models or with the O2 control head |
| APX 6000 Model 3.5 Dual Knob | APX | P25 | Single-band VHF/UHF/700/800 MHz; P25 | 1000 (standard); 3000 (Enhancement Level 2) | IP68 (2 m/4 h, configuration-dependent) |
| APX 6000XE Model 2.5 Dual Knob | APX | P25 | Single-band VHF/UHF/700/800 MHz; P25 | 1000 (standard); 3000 (Enhancement Level 2) | IP68 (2 m/4 h, configuration-dependent) |
| APX 7000 Model 3.5 Dual Knob | APX | P25 | Multi-band VHF/UHF/700/800 MHz; P25 | 3000 | IP67 (higher on some XE configurations) |
| APX 7500 O5 Control Head Vehicle Mount Black | APX | P25 | Multi-band VHF/UHF/700/800 MHz; P25 | 1250 | IP54; up to IP56 on selected models or with the O2 control head |
| APX 900 Model 2 Dual Knob | APX | P25 | VHF/UHF/700/800/900 MHz; P25 | 512 | IP68 |
| APX N30 | APX | P25, Analogue | 700/800 MHz; P25 Digital/Analog | 512 | IP68 |
| APX N50 | APX | P25, Analogue | VHF 136-174 MHz; 700/800 MHz; P25 Digital/Analog | 512 (standard); 1000 (Enhancement Level 1) | IP68 |
| SRX 2200 Model 3.5 Dual Knob | SRX | P25 | VHF/UHF/700/800 MHz; P25/tactical communications | 3000 | IP67/IP68 (configuration-dependent) |
19 identifiers in this collection. Every row reads Supports P25 from the catalogue at build time — the same value the identifier page carries. A value the source document does not confirm is shown as unconfirmed rather than omitted.
What this page does not do
This page explains how the decision is made. It does not quote a phase support, a configuration type or a statement that a build meets a named tender, because the site does not hold one it can evidence. Anything shown as unconfirmed on the catalogue pages is unconfirmed here too.
Confirm the position with your regulator, your site authority or your freight forwarder before you commit to an order.What this catalogue records, and what it does not
| Item | Status in this catalogue |
|---|---|
| Whether the identifier supports P25 | Recorded per identifier, and shown in the table on this page. |
| Frequency band and recorded range | Recorded per identifier. |
| Channel capacity | Recorded per identifier, and shown on the identifier page. |
| Ingress protection | Recorded per identifier. |
| Which P25 phase a build implements | NOT recorded. Confirm against the programme specification. |
| Conventional or trunked operation | NOT recorded. This is a system configuration, not an identifier property. |
| Whether a build satisfies a named tender | NOT asserted. Compliance with a specific tender is the awarding authority's judgement, not a supplier's. |
A protocol in the catalogue is not a tender qualification
Programmes set the standard, the configuration and the documentation before a supplier is chosen. This site publishes what it records about each identifier and does not convert that into a claim of compliance with any specific specification.
Read the programme specification against the recorded parameters, and confirm the gaps with the awarding authority before submitting.What a programme enquiry should carry
- The configuration the specification names, not only the protocol.
- The band and the frequency authorisation held by the operating agency.
- Whether the award is staged, since each stage carries its own quotation and PI trail.
- Whether identifiers must be consistent across the delivered batch, and whether they must be listed on the documentation pack.
Not covered here
- Phase, configuration or feature entitlement for any build.
- A documentation pack preview. The composition of a pack is agreed per award.
- Any statement of compliance with a named programme.
What to put in the first message
Every one of these removes a round trip. The enquiry page composes a brief containing them; you send it from your own mail or messaging app.
- Destination country — this decides the approved variant and the marking.
- The frequency range you are licensed to use, in MHz.
- Quantity per site, and whether spares are included in that number.
- Operating environment, if it is classified (hazardous area, mine, tunnel).
- Whether the units must arrive programmed, and if so the channel plan.
- The exact configuration the specification names, quoted from the document.
- Whether the award is staged, and what documentation each stage requires.
Questions this collection raises
The standard is named the same way, but the configuration a programme buys, and the approvals it requires, are set nationally. Confirm against the programme document rather than the protocol name.
Several builds can, which is what makes a staged migration possible. It is a build property — confirm it per ordering code.
This catalogue does not record phase support per identifier, so it does not answer this question. It is set by the programme specification, and it should be confirmed before a quotation is meaningful.
The enquiry brief has a field for documentation requirements. State what the tender asks for and the position is confirmed on the quotation rather than assumed here.
Where to go from here
Analog or digital DMR for a fleet?
Digital is not simply the newer analog. It changes what the radio can be asked to do — and it changes what happens when part of your fleet stays analog.
Other collections
- Digital radios49 identifiers
- Analog radios71 identifiers
- IP68 radios20 identifiers
Enquiry
Send the configuration, not just the model name
Band, destination and quantity decide whether a quotation is usable in one round or three. Compose the brief and it carries all three.