N3FJP Bridge Setup

Use the N3FJP Bridge to connect Map-panion with your N3FJP logging workflow. The bridge runs locally and allows newly logged QSOs to be shared with Map-panion in a clean, local-first way.

This bridge is designed to stay simple, avoid CAT conflicts, and work quietly in the background once installed. N3FJP remains the logger side of the workflow, while Yaesu CAT and QSY functions now live in the separate Yaesu Bridge.

What you need

Map-panion installed or running

The N3FJP Bridge files

N3FJP Logger installed and working

N3FJP TCP API enabled

Python 3.9 or newer

A Windows system where the bridge can run in the background

For most users, N3FJP and Map-panion will run on the same computer. In that setup, the default bridge settings usually work with little or no editing.

What the N3FJP Bridge Does

The N3FJP Bridge connects N3FJP Logger’s TCP API to Map-panion and other local tools. It is designed to stay local, simple, and safe.

Main bridge functions

Broadcast newly logged QSOs over UDP

Notify Map-panion when new QSOs are logged

Run quietly in the background through a local bridge service

Extract the Bridge Files

Extract the zip so the bridge files live in:
C:\n3fjp-bridge

Do not rename the folder.

Expected folder structure

				
					Code block
C:\n3fjp-bridge\
scripts\
src\
config.json
README.md
USERGUIDE.md

Enable the N3FJP TCP API

In N3FJP Logger, open the API settings and enable the TCP API server.

  1. Open N3FJP Logger
  2. Go to Settings
  3. Open Application Program Interface (API)
  4. Enable TCP API Enabled (Server)
  5. Confirm the port is set to 1100

The bridge must be able to reach N3FJP on the same port that N3FJP is using.
The default is 1100.

Install the Bridge Service

Open PowerShell as Administrator, then run the installation steps
from inside the C:\n3fjp-bridge folder. 

				
					Code block
cd C:\n3fjp-bridge

Get-ChildItem -Recurse | Unblock-File

powershell -ExecutionPolicy Bypass -File .\scripts\Install-N3FJPBridge.ps1

This creates a Scheduled Task that runs the bridge in the background.

A log off/on or reboot is required before the scheduled task starts normally.

What the Installer Does

The installer script is designed to make setup easier and keep the bridge running quietly in the background.

Typical installer actions

Ensures C:\n3fjp-bridge exists

Detects Python

Creates or preserves config.json

Creates a hidden launcher

Creates a Scheduled Task to run the bridge at logon

This gives the bridge a simple “install once, let it run” workflow.

Verify the Bridge Is Running

After installation, confirm that the bridge is running correctly.

Open this in your browser:

http://127.0.0.1:8788/health

You can also check the log file:

C:\n3fjp-bridge\bridge.log

If the health check does not respond

Confirm the bridge task is running

Confirm the Scheduled Task was created correctly

Confirm N3FJP TCP API is enabled

Confirm the bridge config is valid

N3FJP Bridge Config Basics

The bridge uses a local config.json file. For most users, only a few values matter.

Typical settings

N3FJP_HOST
N3FJP_PORT
MYCALL_FALLBACK
UDP_DEST_IP
UDP_DEST_PORT
MAP_BASE_URL
BRIDGE_HTTP_PORT

What Map-panion Uses From the Bridge

When you log a QSO in N3FJP, the bridge can send that information to Map-panion so newly logged QSOs appear automatically on the map.Subheading

Typical local values

UDP destination: 127.0.0.1:12060
Bridge HTTP host: 127.0.0.1
Bridge HTTP port: 8788
Map-panion base URL: http://localhost:3001

Restart and Test

Once the bridge is installed and N3FJP TCP API is enabled, test the workflow with a real log entry.

  1. Confirm the bridge health check responds
  2. Open N3FJP Logger
  3. Open Map-panion
  4. Log a QSO in N3FJP
  5. Confirm the QSO appears in Map-panion

If the bridge is installed through the Scheduled Task workflow, a sign-out/sign-in or reboot may be needed before the background bridge starts automatically.

Portable Version Note

If you are using the portable version of Map-panion, the config.json file needs to live beside the portable .exe.

After you save the integration settings, Map-panion writes them to config.json. If that file is not already there, it will be created after saving.

After saving, restart Map-panion so the new settings are loaded.

For portable installs, keep the app in its own folder so the .exe and config.json stay together.

Troubleshooting

Bridge is not running

Confirm the Scheduled Task was created
Confirm Python is installed
Confirm the bridge files are in C:\n3fjp-bridge
Confirm the launcher and script paths are correct

Health check does not respond

Confirm the bridge is actually running
Confirm the bridge port is 8788
Confirm firewall settings are not interfering
Check bridge.log for errors

No QSO appears in Map-panion

Confirm N3FJP TCP API is enabled
Confirm the N3FJP port matches the bridge config
Confirm Map-panion is running locally
Confirm UDP destination and Map base URL are correct

Settings do not stick after restart

Confirm Map-panion is saving its config correctly
Portable users should keep the app in its own folder
Confirm that config.json is beside the portable .exe
Save the settings, then restart Map-panion

Quick Summary

The N3FJP Bridge connects N3FJP Logger to Map-panion for local logging-related workflows.

Extract the bridge to C:\n3fjp-bridge

Enable the N3FJP TCP API

Run the installer script as Administrator

Verify http://127.0.0.1:8788/health

Log a QSO and confirm Map-panion receives it

Keep portable config.json beside the portable .exe