What the SharkRF M1KE User Manual Assumes You Already Know

The M1KE manual is a better manual than most. It explains dynamic and static talkgroups properly, it tells you what the dejitter queue is doing and what to change when it misbehaves, and its troubleshooting chapter is honest about faults that lie outside the device. What it does not do is define the vocabulary it works in. There is no glossary, no abbreviations list, and no index — in 108 printed pages.

This page fills that gap. It counts 110 technical terms the manual uses two or more times, of which fewer than 30 are ever explained. Two of them are worse than unexplained: hotspot and SSID each carry two entirely different meanings in this one document, and nothing warns you.

Part One walks the terms in the order you meet them, from switching the mic on to reading the Status page. Part Two is an alphabetical glossary with a search box and the number of times each term appears.

Part One — in the order you meet them

1. What the manual never says the device is

The manual opens at charging the battery. It never states the premise, and the premise governs everything that follows: the M1KE is a network client with no amateur-band transmitter. Its only radio is Wi-Fi, at 21 dBm — about 126 milliwatts, into the room. Every contact you make travels over somebody else's server.

Three consequences the manual leaves you to work out:

The behavior you get is the network's, not the device's. The manual says so once, in a note buried in the DMR chapter — "Talkgroups and reflectors are network features, they are completely handled by the network and not the M1KE, and their behavior may be different on each server." That sentence explains most of what confuses new owners.

Licensed and unlicensed mode licensed mode, 4 uses · unlicensed mode, 3 uses — a setting chosen during initialization, changeable later under Owner information. In unlicensed mode the server lists come up empty and you must add your own. The manual states the mechanic without stating the reason: the published server lists are amateur radio infrastructure, and access assumes a licence.

Your callsign is not enough. callsign, 61 uses DMR, NXDN and P25 route on numbers. The M1KE looks your callsign up in an ID database during setup and fills the numbers in for you, which is helpful and also hides the fact that somebody had to issue them.

2. Before you can finish the initialization setup

DMR ID 16 uses — a seven-digit number issued on application, with proof of licence, by the registration body serving your country. The manual never says what it is or where to get one. It does tell you, in troubleshooting, that the device does not care whether yours is valid — only the network does.

NXDN ID — same idea, a different register, filled from the same lookup.

ID database 5 uses — SharkRF's copy of the public callsign-to-ID tables. It fills your IDs at setup, replaces IDs with callsigns in the call log, and can be switched off if the device runs where there is no internet.

D-STAR registration registration, 14 uses — a separate thing entirely from a DMR ID, and the manual only gestures at it. Classic REF and XRF servers require a callsign registered in the D-STAR system. There is a Check D-STAR registration button on the Quick Setup page. Nothing explains what the registration system is, that it is run by gateway operators rather than by SharkRF, or that the registered callsign must match what you type exactly — no suffix, no trailing space. That last point appears only in the troubleshooting chapter, ninety pages later.

3. The Connectors page, decoded

Connector 159 uses — SharkRF's word for one network protocol implementation plus its settings. One is active at a time; a few can stay alive in the background. It is the single most-used term in the manual, and it is defined in one sentence on printed page 92, long after you have needed it.

What the manual does not give you is any basis for choosing. It says which connector reaches which network, but not what distinguishes them.

4. The numbers that are commands

On DMR there is no menu for linking. You link by calling a number, and certain numbers are instructions rather than destinations. The manual explains the mechanics well; what it never says is why — that this range was reserved for control long before hotspots existed, and that a "call" to it carries no audio at all.

Quick call 25 uses — the M1KE's name for sending one of these. The manual describes it as "the same as pressing PTT for a short time (kerchunking)", which is the only appearance of the word kerchunk in the document, offered as if you already knew it. You did not send audio; you sent a control message with your ID attached. And SharkRF is straight with you about the consequence: "These empty calls will also show up on the BrandMeister Network's dashboard."

Dynamic, static and auto-static dynamic, 14 · static talkgroup, 7 · auto static, 8 — this the manual does explain, and explains correctly, including the auto-static rule that most sources get wrong: the first talkgroup you call after calling 4000 is linked auto-static and will not time out. Call 4000 again to clear it.

5. Reading the screen, and the Status page

BER 34 uses — the most-used undefined term in the manual. It appears on the call screen, in the call log after the letter B, and on a graph of its own. The word bit error rate never appears; you can infer it from one sentence about "bit errors", and that is all you get. Nothing states what a normal figure looks like, what a bad one means, or what to do about it.

Loss 6 uses — packet loss, shown after the letter L in the call log. On a device whose entire path is somebody's internet connection, this is often the more useful of the two numbers.

Dejitter queue 13 uses — a buffer that holds arriving packets so that uneven network timing does not become uneven audio. This one the manual explains genuinely well, with both failure modes: a queue too short runs empty and the audio stops for a moment; a queue too long adds delay. It even tells you which graph symptom means which. Credit where it is due.

Talker Alias 3 uses — appears once, in parentheses, as an example of "the source station's broadcasted message", and never again. It is the DMR feature that lets a station send its callsign and name inside the transmission rather than relying on the receiver having a database. It is the reason the second line of the call screen is worth looking at.

PCM, A3K, AMBE3000 3 · 1 · 1 — codec names shown on the call screen. A3K appears exactly once, as an example, with no explanation anywhere. The word vocoder never appears in the manual at all, which leaves you without the vocabulary to look any of them up.

prv and data prv, 1 use — call-type codes on the call info line: a private call, and a data call. Decoded properly, which many manuals would not bother to do.

RSSI 2 uses — Wi-Fi signal strength in dBm, with its own graph and a roaming threshold you can set. Never expanded.

6. Two words that mean two things

These are the traps. Both are ordinary words used for two unrelated concepts in the same document, with nothing to mark the switch.

Hotspot 14 uses

In the Advanced usage chapter, a hotspot is your phone sharing its mobile data over Wi-Fi — you set it as the second saved network so the mic follows you out of the house.

In the Homebrew/MMDVM connector, "Hotspot security password" means something completely different: a per-device password you set on the BrandMeister SelfCare website, so that BrandMeister can tell your devices apart and refuse anyone else using your ID. It is called that because MMDVM hotspots were the first devices to need it.

SSID 19 uses, plus a section of its own

Everywhere in the Network and Wi-Fi chapters, SSID means what it means to the rest of the world: the name of a wireless network. The manual glosses it once, correctly — "the network name (SSID)".

But the Homebrew/MMDVM connector has a section headed SSIDs which means something else entirely: a suffix on your DMR ID, so that several of your devices can connect to BrandMeister at once without you holding several IDs. The manual explains what it does, quite clearly, and never once acknowledges that it has just reused the abbreviation.

7. What is missing because it was never SharkRF's to write

Some of these gaps are not really the manual's fault. They are the hobby's vocabulary, and a vendor cannot reasonably be expected to teach all of it. They are listed here because you will still need them.

DG-ID 0 uses — the manual documents a YSFReflector connector and never mentions DG-ID once. On C4FM, DG-ID is the number that selects a room or group within a reflector; on reflectors organised that way, it is the whole point. There is nothing here to tell you it exists.

M17 0 uses — no connector, and no mention. If you came looking for it, the manual cannot tell you whether it is unsupported or whether you simply missed it. As of firmware v65 there is no M17 connector.

Colour code and time slot 0 uses each — core DMR concepts, absent because the M1KE has no RF and never touches a repeater's air interface. Correctly out of scope; worth knowing that is why, so you do not go looking.

Grid square and Maidenhead locator 0 uses — the Location settings take decimal degrees, and there is a page explaining how to obtain them. Hams navigate by grid square. The conversion is left to you.

Your own Wi-Fi router. The troubleshooting chapter asks you to disable client isolation 2 uses, disable band steering 1 use, set channel width to 20 MHz and use channels 1, 6 or 11. Every one of those is sound advice. None is explained.

Part Two — glossary

Alphabetical. The count after each term is the number of times it appears in the manual body, excluding the contents pages and the open-source licence appendix.

Nothing matches that. Try a shorter word.