Configuring Pi-Star for the Yaesu FT5DR and YSF Reflectors

FIELD NOTE
Type: Configuration / Operating Practice
Related Project: Ham Radio
System Status: Operational
Date / Time: July 14, 2026; Arizona time
Location / Environment: Home station in Goodyear, Arizona; private low-power simplex hotspot over Wi-Fi
Equipment / Software: Raspberry Pi Zero 2 W Rev 1.0; Pi-Star 4.1.13; STM32-DVM / MMDVM_HS Raspberry Pi Hat; modem firmware HS_Hat v1.5.2; Yaesu FT5DR; hotspot frequency 440.950000 MHz
Outcome: The FT5DR and Pi-Star exchanged C4FM traffic, connected to YSF reflectors, and completed a usable parrot test.
Last Verified: July 14, 2026

Summary

This procedure configures a Yaesu FT5DR to use a private Pi-Star hotspot as an Internet gateway to YSF reflectors. The radio uses a short simplex C4FM/DN RF link to the hotspot. Pi-Star then routes the digital stream to the selected reflector.

The FT5DR WIRES-X screen is being used as a limited YSFGateway control interface. A Pi-Star hotspot connects to YSF or FCS reflectors; it is not a native registered Yaesu WIRES-X node.

Tested Baseline

Item	Tested value
Computer	Raspberry Pi Zero 2 W Rev 1.0
Pi-Star	4.1.13
Controller	MMDVMHost, Simplex Node
Modem	STM32-DVM / MMDVM_HS Raspberry Pi Hat (GPIO)
Modem firmware	HS_Hat v1.5.2
Hotspot frequency	440.950000 MHz
Radio	Yaesu FT5DR
Radio mode	DN fixed
Transmit power	LOW1, approximately 0.1 W with the standard battery
DG-ID	TX 00 / RX 00

Before Starting

Connect Pi-Star to working Wi-Fi and verify that the dashboard loads.
Confirm that Pi-Star detects the MMDVM modem and displays its firmware.
Select a legal, locally appropriate hotspot frequency and use the minimum practical power.
Enter the operator callsign in both Pi-Star and the FT5DR.
Keep the radio several feet from the hotspot during testing to avoid overloading the receiver.
Plan to save a Pi-Star backup after the configuration works.

Part 1: Configure Pi-Star for YSF

1. Open Configuration

Open the Pi-Star dashboard and select Configuration, or browse to:

http://pi-star/admin

2. Select the controller

Controller Software	MMDVMHost
Controller Mode	Simplex Node

Select Apply Changes.

3. Enable the YSF RF path

Service	Initial setting
YSF Mode	ON
DMR Mode	OFF
D-Star Mode	OFF
M17 Mode	OFF
P25 Mode	OFF
NXDN Mode	OFF
YSF2DMR / YSF2NXDN / YSF2P25	OFF for the initial YSF test
DMR2YSF and other cross-modes	OFF

Select Apply Changes. Starting with one mode makes RF and network troubleshooting much easier.

4. Complete General Configuration

Field	Setting
Hostname	A unique local name, such as `pi-star`
Node Callsign	Your amateur callsign
CCS7 / DMR ID	Not required for basic YSF; an existing valid ID may remain
Radio Frequency	Your selected simplex hotspot frequency; tested at 440.950000 MHz
Latitude / Longitude	Approximate station location
Town / Country	Station area and country
Radio / Modem Type	The exact installed MMDVM modem
Node Type	Private for a personal hotspot
APRS Host Enable	OFF for initial testing
System Time Zone	The local time zone; America/Phoenix for the tested station

Select Apply Changes.

5. Configure Yaesu System Fusion

Field	Setting
YSF Startup Host	Select a YSF reflector; use a parrot reflector for the first test
UPPERCASE Hostfiles	ON is acceptable and matches the tested configuration
WiresX Passthrough	ON when using FT5DR direct-ID control

Select Apply Changes. Return to the dashboard and confirm that YSF is enabled and the YSF network service has started.

Part 2: Configure the FT5DR Hotspot Memory

FT5DR setting	Value
Frequency	Match the Pi-Star frequency exactly; tested at 440.950000 MHz
Shift	Simplex / no repeater offset
Tone / DCS	OFF
Communication mode	DN fixed
Transmit power	LOW1
DG-ID TX	00
DG-ID RX	00
Suggested memory name	`PISTAR-YSF`

The FT5DR operating manual identifies DN as the standard C4FM voice/data mode. It documents DG-ID 00 as the open setting for communicating without filtering for a particular DG-ID. LOW1 is approximately 0.1 W with the standard battery and is normally sufficient for a hotspot in the same room. fileciteturn27file0

If APRS is active on the B-band, place the hotspot memory on the A-band to avoid disrupting the APRS workflow.

Part 3: Verify the Local RF Path

Open the Pi-Star dashboard.
Tune the FT5DR to the hotspot memory.
Confirm DN mode, LOW1 power, and DG-ID 00/00.
Press PTT, wait about half a second, identify, and transmit for three to five seconds.
Release PTT and check Local RF Activity.

A successful decode normally shows YSF mode, the callsign, RF as the source, transmission duration, RSSI, and sometimes BER. A BER display of ??% means Pi-Star did not calculate a usable value for that transmission; it does not automatically mean the link failed.

The first station tests showed both local RF and gateway activity. Parrot playback initially dropped some syllables, but LOW1 power, additional distance, and longer transmissions produced a usable result. RXOffset and TXOffset calibration remain useful quality improvements.

Part 4: Select a Reflector from Pi-Star

Open Configuration.
Find Yaesu System Fusion Configuration.
Select the desired reflector under YSF Startup Host.
Select Apply Changes.
Return to the dashboard and confirm the reflector under YSF Network.

The startup host is the default destination to which YSFGateway reconnects after restarting.

Part 5: Select a Reflector from the FT5DR

Pi-Star can interpret some commands from the FT5DR WIRES-X-style interface when WiresX Passthrough is enabled. This does not make the hotspot a native WIRES-X node.

Tune the FT5DR to the hotspot memory in DN mode.
Press and hold GM/X for more than one second.
Touch SEARCH & DIRECT.
Touch SEARCH & DIRECT again.
Touch ID so the direct-entry screen shows the # prefix.
Enter the reflector’s five-digit ID.
Touch ENT.
Wait for the command to complete.
Confirm the destination on the Pi-Star dashboard before transmitting.

Example entries:

#99999  DE-Parrot
#69614  US-Phoenix AZ
#85008  US-Arizona
#65635  US-AZPOTA
#32592  US-America Link

The Yaesu direct-ID workflow is SEARCH & DIRECT → SEARCH & DIRECT → ID → five-digit ID → ENT. On Pi-Star, use the dashboard rather than the radio display as the final proof that the target changed.

Disconnecting

Press and hold BAND to disconnect the current YSF destination. Verify the result on the dashboard. Do not use #99999 as a generic disconnect command; in the current Pi-Star reflector list it is a parrot reflector.

Good Reflectors for Initial Testing

YSF ID	Reflector	Use
99999	DE-Parrot	Audio loopback test
21400	ES-PARROT	Alternate parrot test
69614	US-Phoenix AZ	Phoenix-area interest
85008	US-Arizona	Arizona-focused room
65635	US-AZPOTA	Arizona Parks on the Air interest
32592	US-America Link	Large general-purpose destination

Reflector names and IDs can change. Check the current Pi-Star reflector list before treating an ID as permanent.

Operating Practice

Listen for 30 to 60 seconds before transmitting.
Use a complete monitoring call instead of repeated silent key-ups.
Pause briefly after pressing PTT so the RF and network paths can open.
Leave a gap between transmissions for network delay and break-in traffic.
Identify normally and keep tests short.
Do not assume a quiet reflector is broken.
Move long conversations away from busy wide-area destinations when practical.

Troubleshooting

Symptom	Check
No Local RF Activity	Frequency, simplex operation, DN mode, tone/DCS off, DG-ID 00/00, modem type, distance, and radio power
Local RF but no network traffic	Wi-Fi, YSF service, valid startup host, and gateway status
Direct-ID command does nothing	WiresX Passthrough, five-digit entry, Pi-Star/YSFGateway version, and dashboard confirmation
ENT does not show a native room page	Expected on some hotspots; Pi-Star does not provide the complete native WIRES-X protocol
Chopped syllables	LOW1 power, more distance, PTT lead-in, Wi-Fi quality, RXOffset, and TXOffset
BER shows ??%	Use a longer transmission and judge the returned audio
No users heard	Monitor longer, try a larger room, or make a clear spoken call

Conclusion

The working foundation is straightforward: matched simplex frequency, DN mode, LOW1 power, DG-ID 00/00, YSF enabled, and a valid reflector. The Pi-Star web interface remains the most dependable way to select and verify the default destination. FT5DR direct-ID control is convenient when supported, but every change should be confirmed on the dashboard.