The adapter and radio link
FSQ
Use FSQ for the radio path. Its capacity and timing apply to the same file service.
FSQ details →JSQ transport · the idea
Build the services once.
Choose the modem
for the path.
JSQ puts conversations, mail, files, and network services in a shared transport layer above the modems. The services are implemented once. Different supported radio links carry them.
A service architecture for digital radio—not another waveform or a particular application.
Change the organizing principle
The services live
above the modem boundary.
When services are tied to a waveform, choosing its features means accepting its radio limits. Choosing a more sensitive link can mean giving up features you need. JSQ separates those choices with a shared service layer above the modems.
Waveform-centered design
Separate service stacks
- Mode AChat · Files · Relay · DiscoveryFaster text · Lower sensitivity
- Mode BMessaging · Mail · Relay · DiscoveryWeak signal · Slower text
- Mode CChat · Mail · Files · DiscoveryConnection required · Proprietary modem
Choose the features.
Accept that mode’s limits.
The JSQ approach
One shared service layer
Choose the link.
Keep the shared services.
Example link details and sources
Mode A: connectionless, HF/FM. Top text speed ≈60 WPM. Estimated HF minimum SNR: −17 dB at 20 WPM; −14 dB at top speed. The illustrated file service lacks whole-file verification. Rate and sensitivity table →
Mode B: connectionless, HF. Normal speed ≈16 WPM at an estimated minimum SNR of −24 dB. Mail can be stored at an intermediate station. User guide →
Mode C: connected chat through a proprietary modem, HF/FM. Speed adapts to the link, bandwidth, and license. Its low-rate HF broadcast reference is 18 bit/s at ≈−21 dB SNR; this is not a guaranteed threshold for maintaining a connected chat. Low-rate broadcast figures →
Rates and sensitivity describe specific profiles, not a controlled comparison or guaranteed operating minimums. The sensitivity and text-rate contrast between A and B refers to these examples. HF sensitivity figures do not describe the FM radio path.
Why I built JSQ · Jerome Goddard II, W4IJG
The parts I loved.
The experience I wanted.
My goal for JSQ is a paradigm shift in amateur radio digital modes: separating the services we use from the modem or waveform that carries them. I hope JSQ will be the first of many projects to embrace this approach, giving operators the freedom to choose the link that suits the path while keeping the capabilities they rely on.
I was an avid user of FSQ, JS8, and AX.25 packet on APRS. I loved the freedom of keyboard-to-keyboard conversation in FSQ. Its commands also let us build an ad hoc network: relay a message, repeat my message, store and retrieve files, ask for heard lists, and check signal reports. We could check in, cooperate, and work out who could hear whom. JS8’s weak-signal reception, heartbeats, and signal checks were another part of what drew me in. JS8 also let me save a message on a station for later retrieval. That was a major motivation for JSQ’s mail custodian feature.
I liked the speed of APRS packets over AX.25 and the idea of exchanging files through a packet BBS. I wanted that usefulness without tying the workflow to a persistent connected-mode modem link.
But each system had its own modem and quirks. For the way I wanted to operate, the interfaces felt dated and centered on the modem. I wanted conversations, files, mail, and the network to be the starting point.
That became JSQ: bring those useful operating ideas together in a transport protocol above the individual modems. OpenJSQ is the application that puts that approach in front of the operator.
Where the name comes from
Conversation meets cooperation.
The name tells the story: J from JS8, and SQ from FSQ.
JS8 / JS8Call
Messages with somewhere to go.
Directed and stored messages inspired messaging and mail custody.
The shared design goalFSQ / FSQCall
A channel where stations cooperate.
Live conversation and cooperating stations inspired chat and station services.
The FSQ-derived actionsJS8’s weak-signal reception is an inspiration for the project. OpenJSQ does not use the JS8 waveform and is not over-the-air compatible with JS8Call. Peer compatibility · Performance evidence and limits
A clear boundary
Each layer has
one job.
- 01 Application
- Presents conversations, objects, and results to the operator. OpenJSQ is an application built on this model.
- 02 JSQ services
- Implement the common rules for messaging, mail custody, file recovery, groups, and network services.
- 03 Bearer adapter
- Translates service requests into the form each radio link can carry.
- 04 Modem or TNC
- Turns data into a radio signal and decodes received signals.
Follow one useful task
Change the carrier.
Keep the file service.
A reliable file transfer makes the separation concrete. Change the modem below: the shared service responsibilities stay in place.
The shared JSQ service · unchanged
Reliable file transfer
- Track the object and transfer progress
- Recover missing pieces
- Reuse retained progress when the same object is offered again
- Check the complete file and report the result
The adapter and radio link
AX1200
Use AX1200 for the radio path. Its capacity and timing apply to the same file service.
AX1200 details →The adapter and radio link
JG25 Experimental
Use the experimental JG25 link. Its capacity and timing apply to the same file service.
JG25 specification →Each binding uses the same service model.
What the separation makes possible
Services and modems
can evolve independently.
Choose for the path.
Select a supported modem for the radio conditions while retaining the common service model.
Improve a service once.
Changes to a shared service can benefit its supported bearers without separate service redesigns.
Add a link, not another stack.
A new modem provider implements a suitable adapter to the existing services. It need not recreate them.
The public service contract gives other applications a basis for compatible implementations.
Common meaning. Real radio limits.
The link still matters.
The radio path still determines speed, capacity, and latency. Both stations must support the requested service, and station policy still applies.
Signals and peer compatibility →Delivery and custody definitions →
Explore the public service model.
Read the contract, or see it at work in OpenJSQ.