ASTRO 25 / P25 · Technician Training Hub

Learn the system
by running it.

A hands-on training bench for the radio technician: see how a trunked call sets up, map the core architecture, and sweep a feedline like you're at the tower base. Built to learn by doing — not by reading manuals.

Standards-based · interactive · independent study

▸ Start the training path

tiered curriculum · foundations → field engineer · progress saved on this device

Call-flow sim · online Architecture ref · online Field bench · online Fault trainer · online
Module 01 · Simulator

Trunking Call-Flow

how a P25 group call sets up

Key up a radio and watch the signaling move: affiliation, control-channel request, channel grant, talk path, teardown. Starve the channel pool and see queuing and busy behavior under load.

live topologyqueue / busyauto traffic
Enter simulator
Module 02 · Reference

Core Architecture

what every box does

A clickable map of the ASTRO 25 core: Zone Controller, UEM/UCS, KMF, gateways, RF site, and dispatch. Tap any element for its role and model family, plus the K/L/M core scaling tiers.

clickable mapcore tierscomponent cards
Open reference
Module 03 · Bench

Field Technician Bench

site, RF & feedline work

Sweep an antenna and feedline against the −14 dB limit, then find the fault by distance. Plus R56 grounding, the measurements that matter, and the instruments you'll carry.

sweep trainerR56 groundingtest bench
Open bench
Module 04 · Trainer

Fault-Injection Trainer

symptom → diagnosis

A fault hits the system; symptoms report in from users and dispatch. Read the pattern, commit to a diagnosis — failsoft, site trunking, a dead console, or RF — and check your reasoning against the answer.

failure modesdiagnosescored
Start diagnosing
Module 05 · Lesson

Follow the Packet

a radio call is just packets

Build a packet, then move it across site → core yourself — predicting at each device which layer it reads. A guided, step-by-step intro to encapsulation and routing, with QoS as its own follow-on lesson.

predict & revealencapsulationself-paced
Start lesson
Module 06 · Trainer

Radio or Network?

OSI fault isolation

Trouble tickets that all sound like "my radio's broken." Gather clues, climb the OSI ladder, and isolate the layer the fault actually lives at — the instinct every field engineer earns the hard way.

predict & revealOSI ladderscored
Work the tickets
Module 07 · Explorable

The Transport Network

the road the packets drive on

Click through the LAN-at-a-site, the WAN backhaul, and the gateways at each end — and flip on "show redundancy" to see the doubled-everything design that defines a mission-critical network. The architecture behind the trainers.

explorableredundancyLAN / WAN
Explore the network
Module 08 · Simulator

Roaming the System

follow a radio across sites

Drag a subscriber across a multi-site coverage map and watch it automatically re-register on the strongest control channel — seamless within an RFSS, a SIP handshake across the ISSI to a foreign one. Flip on "island site" to see roaming fail when a site loses the core.

drag or driveauto re-registerisland site
Start roaming
Module 09 · Simulator

Simulcast & Voting

many sites, one conversation

Talk-out: slide the transmitter timing and watch the overlap zone go from clean to distorted as sites fall out of GPS sync. Talk-in: adjust receiver quality and watch the comparator vote the best copy, packet by packet, as multipath fades the winner.

timing syncoverlap zonevoting
Run the system
Module 10 · Explorable

Encryption, KMF & OTAR

the keys to secure voice

Trace a key through its life — generated in the KMF, loaded by KVL, kept current over the air with OTAR. Then rekey a fleet and watch who misses it: the powered-off radio, the stale one. The real vocabulary (TEK, KEK, CKR) and the fix for that garbled-audio fault.

key lifecycleOTAR rekeyAES‑256
Trace the keys
Module 11 · Capstone

The Capstone

when it's not just one thing

The final trainer. Ambiguous faults that span RF, transport, call processing, simulcast, and encryption — where the first symptom misleads and two subsystems look guilty at once. Gather evidence across the whole system, then commit. One scenario hides two faults.

multi-subsystemevidence-firstscored
Take the capstone
Module 12 · Explorable

The Codeplug

what's inside a radio's config

Tap through a radio's codeplug field by field — Unit ID, talkgroups, NAC, control channels, the failsoft frequency — and learn what each one is and the exact symptom you get when it's wrong. Demystifies the CPS screen before you ever open it.

codeplugCPS conceptsfield-by-field
Open the codeplug
Module 13 · Explorable

Inside the RF Site

the GTR 8000 rack

A whole ASTRO 25 RF site lives in one rack. Tap the modules — base radios, site controller, combiner, multicoupler, voting receivers — to learn each one, and flip on redundancy to see the no-single-point-of-failure design that replaced the old QUANTAR stations.

GTR 8000 ESSsite rackredundancy
Open the rack

A path through the bench

No fixed order, but if you're starting cold, this sequence builds the mental model layer by layer.

START

See a call work

Run the call-flow sim until the grant sequence feels obvious. That's the heartbeat of trunking.

THEN

Name the boxes

Open the architecture map and connect each signaling step to the element that performs it.

NEXT

Touch the RF

Move to the field bench and sweep a feedline — the work that keeps those sites on the air.

REPEAT

Break things

Inject faults, reason from symptom to cause, and check yourself against the diagnosis.

⚿ About this hub

CORE·LAB is an independent, standards-based study tool. It teaches concepts and troubleshooting reasoning using the open P25 (TIA-102) standard and publicly referenced material like R56. It is not affiliated with or endorsed by Motorola Solutions and reproduces no proprietary software, service procedures, or configuration data — those stay with their licensed sources, which each module points to. Simulated values are illustrative and exist to build intuition, not to model any specific product.

ESC to close
core@lab:~$