Set up Analog APRS on BTECH DMR radios
The short version
Program the APRS path you will actually use
Analog APRS sends a short data burst over an analog FM channel. Program the authorized local frequency, your amateur callsign and SSID, the right symbol and path, and either live GPS or a verified fixed position.
The original U.S. example bundled APBT62 with 144.390 MHz, a WIDE path, Turbo power, and 600 ms timing. Of those settings, only the destination call is tied to the radio family: APBT62 for DMR-6X2/PRO and APBT72 for DA-7X2. Frequency, path, power, and timing depend on the network you use. Choose the lowest practical power and a responsible interval.
Models covered
Every model can send Analog APRS; receive support differs
The base DMR-6X2 supports Analog APRS transmit. DMR-6X2 PRO and DA-7X2 add Analog APRS receive/display capabilities. Use the exact model CPS, the registered destination call for that model family, and local path, timing, and power settings.
Compare models and required versions
| Model | Verified procedure | Required version | Important difference |
|---|---|---|---|
| DMR-6X2 | Analog APRS transmit | Firmware 2.01 or later; current matching CPS | This guide covers Analog APRS transmit on DMR-6X2. Analog APRS receive is not included in this procedure. |
| DMR-6X2 PRO | Analog APRS transmit and receive | Current PRO firmware/CPS | Use the PRO implementation’s integrated APRS receive, filter, and log controls; DA-7X2 provides its own receive and display controls. |
| DA-7X2 | Analog APRS TX/RX | Current DA firmware/CPS | DA-7X2 uses its registered APBT72 destination call, not the 6X2-family APBT62 value. |
Program the identity and beacon first
-
Back up and enable the exact APRS functions
Read the radio and save an untouched codeplug. In matching CPS, enable GPS and APRS as needed. Analog APRS receive controls apply to DMR-6X2 PRO and DA-7X2, not the base DMR-6X2.
-
Enter your station identity
Use your assigned amateur callsign without inventing another user’s identity. Select the SSID and map symbol that describe the station’s actual use.
-
Choose live GPS or fixed position
For a moving station, obtain a fresh GPS lock. For a fixed beacon, enter and verify the stationary coordinates and remember to change them before moving the radio.
-
Set destination call and timing for the exact model
Use the registered destination call for the model family: APBT62 for DMR-6X2 and DMR-6X2 PRO, or APBT72 for DA-7X2. These identifiers are not local preference settings. Confirm the other prewave/delay fields in the current exact-model documentation.
-
Set a local path and responsible interval
Use the path coordinated for your area, or no path when direct reception is the goal. Begin with manual/PTT testing rather than a rapid automatic beacon.

Create the analog channel that carries the packet
-
Create an authorized analog channel
Enter the local APRS receive/transmit frequency, bandwidth, and any receive behavior. Use transmit-disable when the channel is only for monitoring or the operator is not authorized to transmit.
-
Enable Analog APRS on that channel
Choose the model’s Analog APRS report type and PTT behavior. On PRO/DA, enable APRS Receive only when received packet display/logging is intended.
-
Match power to the real path
Use the lowest practical power that reaches the intended local station or digipeater. Do not copy the old Turbo-only instruction; current firmware/model behavior and good network practice take precedence.
-
Put the channel in a zone and write
Save the working file, add the channel to an accessible zone, write it, power-cycle, and read it back before transmitting.
-
Send one controlled packet
Listen first. Obtain a valid GPS position when using live location, send one packet, and confirm a local receiver, digipeater, or appropriate map/service receives the expected callsign and coordinates.

Troubleshooting
| What happened | Likely reason | Next check |
|---|---|---|
| The radio says it sent but nothing hears it | Wrong frequency/path, no GPS fix, unsuitable antenna, timing mismatch, or receiver out of range | Verify one variable at a time with a nearby monitor or local APRS operator before increasing power. |
| The map shows an old position | Fixed beacon is selected or GPS has not refreshed | Choose live GPS and wait for current coordinates, or update the fixed position deliberately. |
| PRO/DA receives packets but filters them out | Receive filter callsign/SSID or channel settings do not match | Check the exact model’s APRS Receive/filter fields and test with a known local packet. |
| Packets are too frequent | PTT upload and automatic interval are both active or the interval is too short | Disable the behavior you do not need and select a responsible local interval. |
| The original screenshot values fail | They belong to an older model/firmware/region example | Return to the current exact-model CPS, model manual, and local APRS plan. |
Manuals, software, and related guides
Common questions
Is 144.390 MHz always the correct frequency?
No. It is a common North American APRS frequency, not a universal worldwide value or transmit authorization. Verify the band plan and APRS practice where you operate.
Should transmit power always be Turbo?
No. Use the lowest practical power for the intended local path. The legacy article documented one older behavior; do not turn it into a family-wide rule.
Can I copy WIDE1-1,WIDE2-1 everywhere?
No. Paths are local network choices. An unnecessary or unsuitable path can create excess traffic or fail to reach the intended route.

Comments (4)
I set mine up as per the examples. It appears to transmit incrementally, but I see no result on aprs.fi. What gives ?
I can get results with my other system from the same location and antenna.
Cool! Smooth new beginning, thanks!
this will be APRS exclusive application radio
totally self contained APRS -= just add antenna?
no additional components – hardware to try and integrate?
can this radio run off of 12Vdc Cigarette Lighter Socket in automobile?
Can you please explain why the APRS channel is necessary?