Regional naming reference
All 156 recorded counterpart names, with the source position each was read from.
Naming
XPR, XiR, DGP and DP — four names, and which one your order actually needs
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.
A name identifies a family. An ordering code identifies a build. The two are not interchangeable, and the gap between them is where purchase orders go wrong — because the name is what a tender document quotes, while the code is what fixes firmware, band split, keypad layout and regulatory marking.
What this note does not do
This note explains how the decision is made. It does not quote a cross-reference that the catalogue does not itself record, 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.How to use this note
- Find the name you were given — on a tender, a quotation, an existing fleet list — in the families below.
- Read its recorded counterparts, and note that a counterpart is a naming relationship only.
- Carry the name into the enquiry as it was written, and we confirm the code for your destination.
The naming families recorded in this catalogue
These counts are of counterpart names as recorded in the source document, grouped by leading letters. They are not marketing segments, and the grouping is mechanical — the same letters that begin the names in the record.
| Leading letters | Recorded names |
|---|---|
| XiR | 26 |
| XPR | 20 |
| M | 15 |
| GP | 14 |
| DGP | 11 |
| SL | 10 |
| DGM | 8 |
| GM | 8 |
| DEP | 5 |
| PRO | 5 |
| CM | 4 |
| PTX | 4 |
| SLR | 4 |
| CDM | 3 |
| DEM | 3 |
| eP | 3 |
| HT | 3 |
7 further leading-letter groups occur on fewer than 3 rows and are listed on the regional naming reference rather than here.
The pattern is worth naming plainly. One family appears under several regional spellings, and each spelling carries its own regional variants — an "e" suffix for the enhanced generation, an "i" suffix on some Asia builds, an "ex" suffix where the build is the hazardous-area variant. The suffixes are where unintended substitutions happen.
What a name decides, and what only the code decides
| Field | The name | The ordering code |
|---|---|---|
| What it identifies | A family, and roughly which generation. | One build: band split, firmware, keypad and display, marking. |
| Where it appears | Tenders, quotations, fleet lists, forum posts. | Purchase orders, packing labels, warranty claims. |
| What it can settle | Which family you are talking about. | Which unit you will receive. |
| What it cannot settle | Band split, firmware, regulatory marking, what is in the box. | Nothing about the underlying hardware — the code describes the build, not the family. |
| Risk if used alone | You receive a lawful, working radio that is not the one you specified. | Low, provided the code is the one your market requires. |
A counterpart name is not a substitution
Firmware, band split, keypad layout and regulatory marking differ between regional builds. Two radios that share a family name and differ by a suffix can differ in what frequency they may legally transmit on.
Recorded counterparts, as an example
Taken straight from the naming reference, these rows show how one identifier maps onto three regions. Note that the markets recorded here are the ones the source document states — not a general rule about where a name is used.
| Identifier | Recorded market | Recorded counterpart |
|---|---|---|
| DR3000 | Asia | XiR R8200 |
| CP100D | Asia | XiR C2660 |
| CP100D | Asia | XiR C2660 |
| CP100D | Asia | XiR C2660 |
| DP1400 | Asia | XiR P3688 |
| DP2400 | Asia | XiR P6600 |
| DP2400e | Asia | XiR P6600i |
| DP2600 | Asia | XiR P6620 |
| DP2600e | Asia | XiR P6620i |
| DP3400 | Asia | XiR P8200 |
| DP3401 | Asia | XiR P8208 |
| DP3600 | Asia | XiR P8260 |
| DP3601 | Asia | XiR P8268 |
| DP4400 | Asia | XiR P8600 |
| DP4400e | Asia | XiR P8600i |
| DP4401 | Asia | XiR P8608 |
| DP4401e | Asia | XiR P8608i |
| DP4401ex | Asia | XiR P8608ex |
| DP4600e | Asia | XiR P8620i |
| DP4801 | Asia | XiR P8628 |
| DP4601e | Asia | XiR P8628i |
| DP4800 | Asia | XiR P8660 |
| DP4800e | Asia | XiR P8660i |
| DP4801 | Asia | XiR P8668 |
| DP4801e | Asia | XiR P8668i |
| DP4801ex | Asia | XiR P8668ex |
| Identifier | Recorded market | Recorded counterpart |
|---|---|---|
| DR3000 | South America | XPR 8300 |
| DM2600 | South America | XPR2500 |
| DM3401 | South America | XPR4350 |
| DM3601 | South America | XPR4550 |
| DM4401 | South America | XPR5350 / XPR5380 |
| DM4401e | South America | XPR5350e / XPR5380e |
| DM4601 | South America | XPR5550 / XPR5580 |
| DM4601e | South America | XPR5550e / XPR5580e |
| DP2400 | South America | XPR 3300 |
| DP2400e | South America | XPR 3300e |
| DP2600 | South America | XPR 3500 |
| DP2600e | South America | XPR 3500e |
| DP3400 | South America | XPR 6300 |
| DP3401 | South America | XPR 6350 |
| DP3600 | South America | XPR 6500 |
| DP3601 | South America | XPR 6550 |
| DP4401 | South America | XPR 7350 / XPR 7380 |
| DP4401e | South America | XPR 7350e / XPR 7380e |
| DP4801 | South America | XPR 7550 / XPR 7580 |
| DP4801e | South America | XPR 7550e / XPR 7580e |
| Identifier | Recorded market | Recorded counterpart |
|---|---|---|
| DP3400 | Latin America | DGP4150 |
| DP3401 | Latin America | DGP4150 |
| DP3441e | Latin America | DGP8050e |
| DP3600 | Latin America | DGP6150 |
| DP3601 | Latin America | DGP6150+ |
| DP4401 | Latin America | DGP8050 / DGP5050 |
| DP4401e | Latin America | DGP8050e / DGP5050e |
| DP4401ex | Latin America | DGP8050ex |
| DP4801 | Latin America | DGP8550 / DGP5550 |
| DP4801e | Latin America | DGP8550e / DGP5550e |
| DP4801ex | Latin America | DGP8550ex |
The three ways this goes wrong
- A tender written in one region's naming is ordered in another region's naming, and the two builds differ at a suffix.
- A series name is ordered where a code was needed, so the band split is decided by whoever picks the stock.
- A counterpart name is assumed to be a drop-in replacement. It is the same family; it is not necessarily the same build.
Not covered here
- A name that the record does not contain. This catalogue publishes the counterparts it holds and does not extrapolate the pattern to names it has not recorded.
- Which name your regulator or your tender authority will accept on the paperwork. That is a documentary question for them.
- Pricing relationships between regional builds.
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 name exactly as it appears in your document — quoted, not paraphrased.
- The document type it came from: tender, quotation, fleet register or shipping label.
Questions this note answers
They are names for the same families in different regional markets. The build behind the name differs — band split, firmware and marking are set by the ordering code, not the family.
You can enquire by name, and it is usually enough to start. What cannot happen is the name being treated as a complete specification, because it does not fix the band split.
Because those are the counterparts the source document states. A blank is not a claim that no other name exists — it is the absence of a recorded counterpart, and it is left blank rather than filled in.
It can. Suffixes mark generation and variant — including enhanced generations and hazardous-area builds. On a purchase order, the suffix is doing load-bearing work.
Where to go from here
Full catalogue
Read the recorded band, channel capacity and ingress protection per identifier.
Admission and compliance
Why the regional build decides which approval applies to your import.
Buyer notes are written from the catalogue and the published reference pages. They carry no parameter the site cannot evidence, and an unconfirmed value stays unconfirmed here too. BaltiGo is a trading and distribution company supplying Motorola two-way radio hardware into Saudi Arabia and the wider GCC, and does not claim to be a Motorola authorised dealer or official distributor.
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.