Ratpack - User contributions [en]

Formatting

2026-07-31T22:07:37Z

Bean:

[[Category:Index]]

== 2026 07 31 ==
What format do we use to name things?
- Using "/**" then " * " then " */" to write comments
- Method names: Upper Snake Case
- Struct names: Upper Snake Case, append "_t"
- Variables: Lower Snake Case
- Constants: Upper Snake Case
- Files:
- .c, .h, .txt Lowercase with underscores
- .txt and .json Upper Camel Case
- Folders: By vibes

Commit formatting:
- https://gist.github.com/qoomon/5dfcdf8eec66a051ecd85625518cfd13
- <type>(<optional scope>): <description>
- Common Types:
- feat: commits that add or adjust a feature
- fix
- refactor
- style: formatting stuff that does not affect
- test: stuff to do with unit testing
- docs
- build: stuff relating to build frameworks and tools
- merge:

Formatting

2026-07-31T21:34:47Z

Bean: added 'constants' formatting entry

Protocol

2026-07-12T21:58:57Z

Bean: Scheme-Plan yes-yes :3

[[Category:Index]]

== Overview ==
When data should be sent, a packet is generated, this is an arbitrary bit string of arbitrary length. If the packet gets above a threshold, call it an MTU for Max Transfer Unit, then the packet can be split into multiple frames. Each frame is one transmission, containing part or all of a packet, and meta information about itself.

The idea is that by splitting and framing packets, we are able to reduce the amount of continuous air time in use, and reduce issues caused by drift in the bit detection

Some transmissions are framed, others are not to save space. See the [[Protocol#Transaction Format|Transaction Format]] below

== Transaction Format ==
A ____ | Unframed, Occasionally broadcast ping to say ready to transmit, maybe once every two minutes or something
A <- B | Unframed, Reply to A's broadcast, just different(?) preamble then A's callsign, then B's callsign
A -> B | Framed packet, containing list of message hashes
A <- B | Framed packet, containing list of message hashes
A -> B | Framed packet, List of hashes A does hot have
A <- B | Framed packet, List of hashes B does hot have
A -> B | Framed packet, Message data for all requested packets B is missing
A <- B | Framed packet, Message data for all requested packets A is missing

== Packet Framing ==
- One frame contains a preamble, header, packet/packet part, footer

=== Preramble ===
- More than a standard bit string, could just stop transmitting within the block. This will allow the reciever to calibrate their bit width offset
- All messages start this way in some fashion
- Used to detect if this is a transmission for us, or another mode like someone just talking we can ignore
- It could be worth having a distinct preamble for framed packets vs freeform want-to-talk/reply-to-want-to-talk packets
- Something like 11110000110011001010 could be cool, the goal is that it can be listening periodically, then have enough time to spool up the math, and set the timing for where bit edges are

=== Header ===
- Contains meta information about the packet/packet part
- Size of data block in bits/bytes (TBD)
- Hash/Checksum/Parity to verify message integrity (TBD, I vote start with single parity bit, then get more complicated once we're good at this)
- Callsign of sender, need to decide on format. It may be worth finding a standard already in place for amateur radio
- Callsign of intended recipient (Do we want this?)
- Section to say if we are a part of a split packet, and if so, what number out of how many we are, maybe just reserve two bytes for me/total

=== Packet ===
- Arbitrary data, split to fit in frame's MTU then reconstructed

=== Footer ===
- Like header but less
- parity/checksum again(?)
- Callsign of sender in standard format again -- I think this should be the end of the message so if someone doesn't know the format they can do it
- Maybe beep it out in morse code using more standard fm ptt also

Resources

2026-06-06T01:39:00Z

Bean:

This page will hold all our relevant sources, reading material, and so on.

== Articles ==
=== Impact of Information on the Complexity of Asynchronous Radio Broadcasting ===
Authors: Tiziana Calamoneri, Emanuele G. Fusco, and Andrzej Pelc

http://wwwusers.di.uniroma1.it/~calamo/PDF-FILES/information.pdf

== Protocol ==
The FT4 and FT8 Communication Protocols: Motivation and design of the digital modes FT4 and FT8, and some details of how they are implemented in WSJT-X.

https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf

FT8 source code:

https://github.com/kgoba/ft8_lib

JS8 user guide:

https://js8call.com/JS8Call-improved/d6/d14/md_docs_2user__guide_2JS8Call__User__Guide.html

Weak Signal Jovial Turtles (WSJT) homepage:

https://wsjt.sourceforge.io/devel.html


[[Category:Index]]

Resources

2026-06-06T01:38:50Z

Bean:

This page will hold all our relevant sources, reading material, and so on.

== Articles ==
=== Impact of Information on the Complexity of Asynchronous Radio Broadcasting ===
Authors: Tiziana Calamoneri, Emanuele G. Fusco, and Andrzej Pelc

http://wwwusers.di.uniroma1.it/~calamo/PDF-FILES/information.pdf

== Protocol ==
The FT4 and FT8 Communication Protocols: Motivation and design of the digital modes FT4 and FT8, and some details of how they are implemented in WSJT-X.

https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf

FT8 source code:
https://github.com/kgoba/ft8_lib

JS8 user guide:

https://js8call.com/JS8Call-improved/d6/d14/md_docs_2user__guide_2JS8Call__User__Guide.html

Weak Signal Jovial Turtles (WSJT) homepage:

https://wsjt.sourceforge.io/devel.html


[[Category:Index]]

Resources

2026-06-06T01:29:57Z

Bean:

This page will hold all our relevant sources, reading material, and so on.

== Articles ==
=== Impact of Information on the Complexity of Asynchronous Radio Broadcasting ===
Authors: Tiziana Calamoneri, Emanuele G. Fusco, and Andrzej Pelc

http://wwwusers.di.uniroma1.it/~calamo/PDF-FILES/information.pdf

== Protocol ==
The FT4 and FT8 Communication Protocols: Motivation and design of the digital modes FT4 and FT8, and some details of how they are implemented in WSJT-X.

https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf

JS8 user guide:

https://js8call.com/JS8Call-improved/d6/d14/md_docs_2user__guide_2JS8Call__User__Guide.html

Weak Signal Jovial Turtles (WSJT) homepage:

https://wsjt.sourceforge.io/devel.html


[[Category:Index]]

Resources

2026-06-06T00:55:02Z

Bean:

This page will hold all our relevant sources, reading material, and so on.

== Articles ==
=== Impact of Information on the Complexity of Asynchronous Radio Broadcasting ===
Authors: Tiziana Calamoneri, Emanuele G. Fusco, and Andrzej Pelc

http://wwwusers.di.uniroma1.it/~calamo/PDF-FILES/information.pdf

== Protocol ==
The FT4 and FT8 Communication Protocols: Motivation and design of the digital modes FT4 and FT8, and some details of how they are implemented in WSJT-X.

https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf

Weak Signal Jovial Turtles (WSJT) homepage:

https://wsjt.sourceforge.io/devel.html


[[Category:Index]]

Resources

2026-06-06T00:54:48Z

Bean:

This page will hold all our relevant sources, reading material, and so on.

== Articles ==
=== Impact of Information on the Complexity of Asynchronous Radio Broadcasting ===
Authors: Tiziana Calamoneri, Emanuele G. Fusco, and Andrzej Pelc

http://wwwusers.di.uniroma1.it/~calamo/PDF-FILES/information.pdf

== Protocol ==
The FT4 and FT8 Communication Protocols: Motivation and design of the digital modes FT4 and FT8, and some details of how they are implemented in WSJT-X.

https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf

Weak Signal Jovial Turtles (WSJT) homepage:
https://wsjt.sourceforge.io/devel.html


[[Category:Index]]

Resources

2026-06-06T00:54:36Z

Bean:

This page will hold all our relevant sources, reading material, and so on.

== Articles ==
=== Impact of Information on the Complexity of Asynchronous Radio Broadcasting ===
Authors: Tiziana Calamoneri, Emanuele G. Fusco, and Andrzej Pelc

http://wwwusers.di.uniroma1.it/~calamo/PDF-FILES/information.pdf

== Protocol ==
The FT4 and FT8 Communication Protocols: Motivation and design of the digital modes FT4 and FT8, and some details of how they are implemented in WSJT-X.

https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf

Weak Signal Jovial Turtles (WSJT) homepage:
https://wsjt.sourceforge.io/devel.html


[[Category:Index]]

Resources

2026-06-06T00:30:53Z

Bean: Added FT4 protocol document

Shared Documents

2026-04-14T22:27:05Z

Bean:

[[Category:Index]]

Final Presentation: https://docs.google.com/presentation/d/1z0RWML4LscDDLyI2OR0ecD0lyGYomgWG8lHGuEDNWdA/edit?usp=sharing

Final Proposal: https://docs.google.com/document/d/14ydoZ-L2-1_XbjGCP8m4bqDTo7D6e-AzSidDjeT5dfk/edit?usp=sharing
Will be typeset later, this is just for shared when writing words

https://docs.google.com/spreadsheets/d/12KzJ8wqi2Mkw5PzUGracRZwxYwH0GbMwOs3JQOueON8/edit?gid=0#gid=0

Resources

2026-04-09T22:14:37Z

Bean: