6. Trail Mate Center

Trail Mate Center

Language: English. Chinese version: 6. Trail Mate Center (中文)

Trail Mate Center is a desktop workbench, not the owner of the product core. Without Center, the MCU terminal still owns identity and contacts, communicates, uses offline maps, and provides essential TAK awareness. Center handles established capabilities that fit a desktop better: map preparation, large-screen viewing, export, replay, and diagnosis.

If the device is the field terminal, Trail Mate Center is closer to a preparation and diagnostics workbench.

What It Is

According to the current companion-repository README, Trail Mate Center is an Avalonia-based desktop application that connects to Trail Mate, and to compatible Meshtastic devices, through USB HostLink. It brings several kinds of capability into one application:

• device connection and HostLink protocol interaction
• situational map and message viewing
• offline map caching, export, and completeness checking
• raw frame inspection and protocol-level troubleshooting
• event, message, and session replay
• propagation analysis tooling

The repository contains the desktop application and related shared libraries. It does not contain the device firmware. Keeping that boundary clear matters.

How It Relates To The Device

Trail Mate Center is not required for the device to be usable, but it is also not just an optional extra.

The more precise relationship is:

• without Center, the device can still handle maps, GPS, text communication, and part of the Team workflow
• with Center, offline map preparation, larger situational views, logging, event review, and protocol troubleshooting become much easier

So Center is best understood as a tool layer that improves preparation, understanding, and debugging, not as a hard dependency for core device operation.

What It Currently Does

Connection and protocol handling

The current README explicitly mentions capabilities such as:

• scanning serial ports and connecting through USB HostLink
• configurable ACK timeout and retry count
• auto-connect and auto-reconnect
• replay mode from recorded files
• simultaneous handling of Meshtastic-style traffic and Trail Mate MeshCore protocol decoding

That means it is more than a serial terminal. It is a desktop peer that understands HostLink semantics.

Situational map

Trail Mate Center can display live positions on a large-screen map, with support for:

• OSM, Terrain, and Satellite base layers
• contour and NASA GIBS imagery overlays
• team view, node list, event feed, and tactical action areas
• following the latest position or manually moving around the map during analysis

The device-side map answers “can I still understand the field here and now”. The desktop map answers “can I understand the broader picture, review it later, and prepare resources more efficiently”.

Offline map preparation and export

This is especially important for Trail Mate because it directly feeds the device-side offline map structure. Center can currently:

• select cache areas using rectangles or polygons
• save common regions and fill missing tiles
• build offline caches for chosen base and contour layers
• export to USB media or SD card in a directory layout matching maps/base/... and maps/contour/...
• import KML tracks and prepare route-buffer caches

If you do not want to hand-build tile directory trees, Center is the natural preparation tool inside the project.

Chat, logs, and troubleshooting

Center also supports:

• session lists and message history viewing
• node selection with online state, telemetry summary, and last position
• filtered log viewing with save and copy options
• raw frame inspection
• exporting messages or events to CSV or JSONL

That makes it one of the main troubleshooting entry points, not only a map-preparation tool.

Propagation analysis

Center also includes propagation-analysis-oriented capabilities such as coverage, interference, relay optimization, and more advanced analysis tooling. This is not part of the handheld firmware’s minimum required loop, but it shows that Trail Mate is evolving as a field communication system, not only as a chat device.

Why The Device Still Needs A Desktop Companion

For many users, the value is straightforward:

First, map preparation is much more efficient on desktop. The handheld should read resources, not become a full map-building workstation.

Second, troubleshooting is easier on desktop. Many communication and protocol issues are hard to understand on a small screen but much clearer in situational views, raw-frame views, and filtered logs.

Third, review is easier on desktop. Messages, events, and recorded sessions are easier to inspect, filter, and export there.

Main Tabs At A Glance

According to the current README, Trail Mate Center includes pages such as:

• situation
• propagation
• chat
• configuration
• logs
• event monitor
• raw frames
• export

That layout reinforces that this is a multi-role desktop workbench rather than a single-purpose utility.

How Resources Reach The Device

One of Center’s most important roles is producing data in the same structure the device already expects.

Its exported offline map directories align with device-side paths such as:

maps/base/...
maps/contour/...

This is important because it means:

• the device and the desktop tool are not maintaining unrelated resource systems
• the device can stay simple and read a fixed structure
• the complexity of selecting, caching, and exporting resources is intentionally moved to the desktop side

Current Repository Boundary

The current Center repository includes:

• the Avalonia desktop UI
• HostLink protocol implementation
• Meshtastic protobuf decoding and shared data models
• local storage, replay, export, and offline map cache tooling
• propagation engine and related bridge or service logic

It does not include:

• device firmware
• embedded device-side UI
• a mobile application
• hosted cloud services

Making that separation explicit helps future maintainers avoid mixing desktop responsibilities back into the firmware.

Platforms and Startup

The current README explicitly mentions .NET 8 SDK and startup with:

dotnet run --project src/TrailMateCenter.App

It is a standard desktop application route. Final packaging coverage and release status should still be checked in the companion repository itself rather than assumed from the main firmware wiki.

When Center Is Especially Useful

Open Center first when:

• preparing offline maps
• watching multiple nodes and the map at once
• inspecting raw frames or HostLink data
• exporting messages or events, or replaying a session
• checking configuration or integrating external data sources

Information Still Worth Expanding

Good future additions would include:

• a flow diagram for HostLink and Center interaction
• a side-by-side mapping of Center export directories and device-side directory expectations
• illustrated explanations of the raw-frame, event, and situational pages
• clearer boundary notes between Center and the propagation-analysis modules

For now, the main goal is simply to explain that Center is part of the same system, not another unrelated repository.