Regional naming reference
The full recorded cross-reference, filterable, with provenance on every row.
Naming, worked example
Is the DP1400 the same radio as the XiR P3688, the CP200d or the DEP450?
Yes, as a family relationship — and that is the whole of the claim. This catalogue records three counterparts for the DP1400, one per market, and none of them is a specification.
This is the single most common naming question, so it is worth answering with the record rather than with a rule. Against the DP1400, the source document records three regional counterparts. All three describe the same hardware family. None of them tells you the band split.
What this note does not do
This note explains how the decision is made. It does not quote a substitution approval, or a claim that two regional builds are interchangeable, 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 the record actually says
| Identifier | Recorded market | Recorded counterpart |
|---|---|---|
| DP1400 | Asia | XiR P3688 |
| DP1400 | Latin America | DEP450 |
| DP1400 | South America | CP200d |
Three rows, three markets, one identifier. Note what is absent from the table as well: no band split, no firmware version, no keypad layout, no regulatory marking. A counterpart is a naming relationship, and the record is deliberately narrow about it.
| Identifier | Series | Frequency band | Channel capacity | Ingress protection |
|---|---|---|---|---|
| DP1400 | DP | VHF/UHF; Analog + DMR | 16 | IP54 |
Read from the catalogue at build time. A field the source document does not confirm is shown as unconfirmed rather than omitted.
The identifier line above and the three counterpart names are two different kinds of fact. One is a build; the others are names. Writing an order needs the first, and it is the first that changes between markets.
What the counterpart relationship is good for
- Recognising that a document naming the XiR P3688 and a document naming the DP1400 are discussing the same family, so they can be reconciled rather than treated as two requirements.
- Explaining a fleet register that mixes names, when equipment was bought in different markets over several years.
- Choosing which name to search on, when a supplier's page uses one spelling and your paperwork uses another.
Where the relationship stops being useful
| Question | Answered by the counterpart name? | What actually answers it |
|---|---|---|
| Which band the unit covers | No | The ordering code and the delivered label. |
| Which firmware generation | No | The ordering code and the suffix on it. |
| Whether it may be imported and used in your country | No | Your regulator's type approval for that specific build. |
| What is in the box | No | The packing list on the quotation line. |
| Whether the two are drop-in substitutes | No | A build-level comparison, and in some cases the approving authority. |
The sentence to avoid writing
"The DP1400 is the same as the CP200d, so either will do." The first half is a naming relationship this catalogue does record. The second half is a substitution decision this catalogue does not make, and which your approving authority may not accept.
Not covered here
- A judgement on whether any two builds are interchangeable for your application.
- Counterparts for identifiers where the record holds none. They are shown as blank on the naming reference rather than inferred.
- Price, stock or lead time for any of the names above.
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.
- Which of the names is on your existing paperwork — quoted exactly as written.
- Whether you are consolidating a fleet bought in more than one market.
Questions this note answers
That is a build-level decision, not a naming decision. Confirm the band split and marking required at your destination, then compare builds. This site does not assert that any two regional builds are interchangeable.
Because three are what the source document records. Other markets may well sell it under further names, but an unrecorded name is left unrecorded rather than filled in from general knowledge.
That is a documentary requirement set by whoever wrote the tender or issues the import documentation. Ask them which name they need to see on the paperwork.
The one you were given, exactly as written. Then add your destination country and the frequency range you are licensed for — those two fields are what the code is resolved against.
Where to go from here
Portables
The category the DP1400 sits in, with the recorded parameters for each identifier.
Compose an enquiry brief
Builds a complete specification request you can copy into your own mail or messaging app.
Identifiers named in this note
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.