Radio: AnyTone AT-D878UVII Plus
Target Use: Personal hotspots (Pi-Star, WPSD, OpenSpot, ZumSpot, etc.)
Networks: BrandMeister-style dynamic talkgroups
Design Goal: Fast access, zero clutter, predictable behavior
Core Design Philosophy
Hotspots are not repeaters. A hotspot codeplug must prioritize:
- Dynamic talkgroups only
- Single frequency simplex
- Minimal zones
- Rapid TG switching
- No scanning
- Low power
This template assumes one hotspot frequency (e.g., 433.550 MHz or 438.800 MHz). You can duplicate it later for additional hotspots.
1. Hotspot Global Settings (Critical)
Before creating channels, configure these radio-wide settings:
RF & Power
- TX Power: LOW
- Bandwidth: Narrow
- Squelch: Default
- VOX: OFF
Roaming & Scan
- Roaming: DISABLED
- Auto Scan: DISABLED
- Dual Watch: OPTIONAL (generally OFF)
Bluetooth
- Bluetooth: ENABLED (optional)
- BT PTT: Optional, not required
2. Frequency Plan (Single Simplex)
Choose one simplex frequency and use it consistently:
Common choices
- UHF: 433.550 / 438.800 / 439.9875
- VHF (less common): 145.790
Rule
One frequency. One color code. One hotspot zone.
3. Digital Channel Template (Master)
Create one base channel, then duplicate it.
Base Channel Settings
- RX Frequency: Hotspot frequency
- TX Frequency: Hotspot frequency
- Color Code: 1 (match hotspot)
- Time Slot: 2 (BrandMeister best practice)
- Admit Criteria: Channel Free
- TX Power: Low
- In Call Criteria: Follow Admit
Save this channel as:
HS-BASE
4. Hotspot Zone Layout (Recommended)
ZONE: HOTSPOT – CORE
This is your primary operating zone.
| Channel Name | Talkgroup | Time Slot | Notes |
|---|---|---|---|
| HS-TG9 | TG9 | TS2 | Local / reflect hotspot |
| HS-TG91 | TG91 | TS2 | Worldwide |
| HS-TAC310 | TG310 | TS2 | TAC |
| HS-TAC311 | TG311 | TS2 | TAC |
| HS-DROP | TG4000 | TS2 | Disconnect |
Rules
- No static talkgroups
- No scanning
- No mixed modes
ZONE: HOTSPOT – REGIONAL (Optional)
Add only what you actually use:
| Channel Name | Talkgroup |
|---|---|
| HS-STATE | Statewide TG |
| HS-REGION | Regional TG |
| HS-NATION | Nationwide TG |
If unused for 30 days → delete.
ZONE: HOTSPOT – EVENTS (Optional)
Temporary zone for:
- Nets
- Special events
- Contests
Delete after use.
5. Channel Naming Standard (Hotspot)
HS-[TG]
Examples:
HS-TG9
HS-TG91
HS-TAC310
HS-DROP
This keeps the channel list short, readable, and fast.
6. Talkgroup Behavior Rules
Always Use Dynamic TGs
- Key up once to activate
- Disconnect with TG4000
- Avoid leaving unused TGs open
Best Practice
After every long QSO:
Select HS-DROP
Key PTT once
7. APRS with Hotspot (Optional but Clean)
If using DMR APRS:
- Create one APRS channel only
- Disable beacon flooding
- Use longer intervals (10–30 min)
Do not mix APRS into your CORE zone.
8. What NOT to Include (Very Important)
Do not include:
- Static talkgroups
- Roaming channels
- Multiple hotspot frequencies in one zone
- Scan lists
- Analog channels
- Weather channels
Hotspot codeplugs should feel “boring”—that is intentional.
9. Hotspot Codeplug File Naming
878_HOTSPOT_[NETWORK]_[DATE]_vX.rdt
Examples
878_HOTSPOT_BM_2026-01-08_v1.rdt
878_HOTSPOT_TRAVEL_2026-01-08_v1.rdt
10. Recommended Workflow
First Load
- Write hotspot codeplug
- Power cycle radio
- Confirm hotspot dashboard activity
- Test TG9 → TG91 → DROP
Daily Use
- Stay in HOTSPOT – CORE
- Switch TGs by channel, not menus
Maintenance
- Review talkgroups quarterly
- Delete unused channels aggressively
Final Guidance
A hotspot-optimized codeplug should:
- Have fewer than 15 channels
- Require zero scrolling
- Be usable without looking at the radio
- Never interfere with EMCOMM or daily repeater operation