freetel-codec2 — sub 5 kbit/s open source voice codec

[Freetel-codec2] [Announcement] FreeDV Activity Day - April 18-19, 2026

[Mooneer S. <mo...@gm...>]

Hi all,

This is a reminder that this month's FreeDV Activity Day is this coming
weekend. (As a reminder, Activity Day takes place on the third weekend of
every month.) This event will bring together people interested in HF
digital voice on the air for conversation and fun. Contacts using the
official application as well as ezDV, the SM1000 handheld microphone and
other supporting devices and applications are welcome.

Event time: 12AM Pacific time (0700Z) on April 18 to 11:59PM on April 19
(0659Z on April 20) (48 hours).

Suggested frequencies:
160 meters: 1.997 MHz
80 meters: 3.625, 3.643, 3.693, 3.697 MHz or 3.803 MHz
60 meters (in countries where allowed): 5.4035 MHz or 5.3665 MHz
40 meters: 7.177 MHz or 7.197 MHz
20 meters: 14.236 MHz or 14.240 MHz
17 meters: 18.118 MHz
15 meters: 21.313 MHz
12 meters: 24.933 MHz
10 meters: 28.330 or 28.720 MHz
10 GHz (for those in range of QO-100): 10489.640 MHz

(Note that LSB/DIGL is used below 10MHz as per current convention for voice
modes, USB/DIGU otherwise. 60 meters is of course USB/DIGU only.)

As this isn't a contest, there's no pressure to make contacts or send logs,
but you can always confirm QSOs via the usual means if you'd like (LoTW,
eQSL, QRZ, etc.) Enabling reporting (PSK Reporter and FreeDV Reporter) in
the FreeDV application and joining FreeDV Reporter and Discord are
recommended, however, so others can see that you're on the air and hearing
them (for instance, here's the current map of listeners). :D

Feel free to spread this far and wide among your local ham friends and
groups! :) Let me know if you have any questions about the event and
definitely post here if you have issues getting the application working
prior to the event.

Thanks,

-Mooneer K6AQ

[Freetel-codec2] [Announcement] FreeDV Activity Day - March 21-22, 2026

[Mooneer S. <mo...@gm...>]

Hi all,

This is a reminder that this month's FreeDV Activity Day is this coming
weekend. (As a reminder, Activity Day takes place on the third weekend of
every month.) This event will bring together people interested in HF
digital voice on the air for conversation and fun. Contacts using the
official application as well as ezDV, the SM1000 handheld microphone and
other supporting devices and applications are welcome.

Event time: 12AM Pacific time (0700Z) on March 21 to 11:59PM on March 22
(0659Z on March 23) (48 hours).

Suggested frequencies:
160 meters: 1.997 MHz
80 meters: 3.625, 3.643, 3.693, 3.697 MHz or 3.803 MHz
60 meters (in countries where allowed): 5.4035 MHz or 5.3665 MHz
40 meters: 7.177 MHz or 7.197 MHz
20 meters: 14.236 MHz or 14.240 MHz
17 meters: 18.118 MHz
15 meters: 21.313 MHz
12 meters: 24.933 MHz
10 meters: 28.330 or 28.720 MHz
10 GHz (for those in range of QO-100): 10489.640 MHz

(Note that LSB/DIGL is used below 10MHz as per current convention for voice
modes, USB/DIGU otherwise. 60 meters is of course USB/DIGU only.)

As this isn't a contest, there's no pressure to make contacts or send logs,
but you can always confirm QSOs via the usual means if you'd like (LoTW,
eQSL, QRZ, etc.) Enabling reporting (PSK Reporter and FreeDV Reporter) in
the FreeDV application and joining FreeDV Reporter and Discord are
recommended, however, so others can see that you're on the air and hearing
them (for instance, here's the current map of listeners). :D

Feel free to spread this far and wide among your local ham friends and
groups! :) Let me know if you have any questions about the event and
definitely post here if you have issues getting the application working
prior to the event.

Thanks,

-Mooneer K6AQ

[Freetel-codec2] New mailing list for emergency communications

[Bruce P. <br...@pe...>]

Please see https://groups.google.com/a/perens.com/g/emergency_communications
I will move discussion to that list from here.

Topics for discussion:

Developing a portable, multi-head, transport-independent, emergency
communications systems for the incident command system.

One that's perhaps a start or at least one of the transport providers: Pat:
https://github.com/la5nta/pat/tree/master/internal/forms

    Thanks

    Bruce

-- 
Bruce Perens K6BP

Re: [Freetel-codec2] Incident Command System Automation

[Bruce P. <br...@pe...>]

I will establish a mailing list.

Don't use YAML for anything, it has some fundamental problems, for example
the "Norway" problem: "NO" is one of an unfortunate _list_ of words that
evaluate to false. I will set up a mailing list. Mooneer also told me about
https://github.com/la5nta/pat/ which is modern portable code interoperable
with Winlink.

    Thanks

    Bruce

On Wed, Mar 11, 2026 at 4:30 PM Stuart Longland via Freetel-codec2 <
fre...@li...> wrote:

> On 12/3/26 02:57, Bruce Perens via Freetel-codec2 wrote:
> > With this said, I am going to finish the bigger project first, and the
> > capability to edit the ICS forms and transport them as JSON will be part
> of
> > it. The rest of this will be shelved until I am satisfied with the larger
> > project, unless someone else wants to take it up.
>
> How about YAML?  The original message almost is YAML in its raw form.  I
> could be misinterpreting the raw message format, but as a concept:
>
> Subject: GENERAL MESSAGE (ICS 213)
> Body: |
>      ** THIS IS AN EXERCISE **
>      1. Incident Name: ODMT Winter FTX
>      2. To (Name and Position): Local Radio Operators
>      3. From (Name and Position): Don Reid - W7DMR : Wren Digital RADO
>      4. Subject: Winink test
>      5. Date: 2026-02-21
>      6. Time: 11:46
>      7. Message:
>
>      We are not finding good HF RMS stations to talk to with the NVIS
> antennas we have setup.  I found one, W7OWO on 40m.
>      Telnet via a Starlink connection works well even at the low 500k
> baud "Standby" service.
>
>      8. Approved by: Don Reid
>      8a. Position/Title: RADO
>
> Sender:
>      Callsign: W7DMR
>      Lat: 45.562500
>      Lon: -122.875000
>      MGRS: null
>      Location Source: Grid square
>      Express Version: 1.7.23.0
> Template Version: ICS 213  v.43.8
> Changes Allowed: no
>
> Both human-and-machine readable.  The same as JSON:
>
> {
>      "Subject": "GENERAL MESSAGE (ICS 213)",
>      "Body": "** THIS IS AN EXERCISE **\n1. Incident Name: ODMT Winter
> FTX\n2. To (Name and Position): Local Radio Operators\n3. From (Name and
> Position): Don Reid - W7DMR : Wren Digital RADO\n4. Subject: Winink
> test\n5. Date: 2026-02-21\n6. Time: 11:46\n7. Message:\n\nWe are not
> finding good HF RMS stations to talk to with the NVIS antennas we have
> setup.  I found one, W7OWO on 40m.\nTelnet via a Starlink connection
> works well even at the low 500k baud \"Standby\" service.\n\n8. Approved
> by: Don Reid\n8a. Position/Title: RADO\n",
>      "Sender": {
>          "Callsign": "W7DMR",
>          "Lat": 45.5625,
>          "Lon": -122.875,
>          "MGRS": null,
>          "Location Source": "Grid square",
>          "Express Version": "1.7.23.0"
>      },
>      "Template Version": "ICS 213  v.43.8",
>      "Changes Allowed": false
> }
>
> Admittedly is more compact, but not as readable.
> --
> Stuart Longland (aka Redhatter, VK4MSL)
>
> I haven't lost my mind...
>    ...it's backed up on a tape somewhere.
>
>
>
> _______________________________________________
> Freetel-codec2 mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>


-- 
Bruce Perens K6BP

Re: [Freetel-codec2] Incident Command System Automation

[Stuart L. <st...@lo...>]

On 12/3/26 02:57, Bruce Perens via Freetel-codec2 wrote:
> With this said, I am going to finish the bigger project first, and the
> capability to edit the ICS forms and transport them as JSON will be part of
> it. The rest of this will be shelved until I am satisfied with the larger
> project, unless someone else wants to take it up.

How about YAML?  The original message almost is YAML in its raw form.  I 
could be misinterpreting the raw message format, but as a concept:

Subject: GENERAL MESSAGE (ICS 213)
Body: |
     ** THIS IS AN EXERCISE **
     1. Incident Name: ODMT Winter FTX
     2. To (Name and Position): Local Radio Operators
     3. From (Name and Position): Don Reid - W7DMR : Wren Digital RADO
     4. Subject: Winink test
     5. Date: 2026-02-21
     6. Time: 11:46
     7. Message:

     We are not finding good HF RMS stations to talk to with the NVIS 
antennas we have setup.  I found one, W7OWO on 40m.
     Telnet via a Starlink connection works well even at the low 500k 
baud "Standby" service.

     8. Approved by: Don Reid
     8a. Position/Title: RADO

Sender:
     Callsign: W7DMR
     Lat: 45.562500
     Lon: -122.875000
     MGRS: null
     Location Source: Grid square
     Express Version: 1.7.23.0
Template Version: ICS 213  v.43.8
Changes Allowed: no

Both human-and-machine readable.  The same as JSON:

{
     "Subject": "GENERAL MESSAGE (ICS 213)",
     "Body": "** THIS IS AN EXERCISE **\n1. Incident Name: ODMT Winter 
FTX\n2. To (Name and Position): Local Radio Operators\n3. From (Name and 
Position): Don Reid - W7DMR : Wren Digital RADO\n4. Subject: Winink 
test\n5. Date: 2026-02-21\n6. Time: 11:46\n7. Message:\n\nWe are not 
finding good HF RMS stations to talk to with the NVIS antennas we have 
setup.  I found one, W7OWO on 40m.\nTelnet via a Starlink connection 
works well even at the low 500k baud \"Standby\" service.\n\n8. Approved 
by: Don Reid\n8a. Position/Title: RADO\n",
     "Sender": {
         "Callsign": "W7DMR",
         "Lat": 45.5625,
         "Lon": -122.875,
         "MGRS": null,
         "Location Source": "Grid square",
         "Express Version": "1.7.23.0"
     },
     "Template Version": "ICS 213  v.43.8",
     "Changes Allowed": false
}

Admittedly is more compact, but not as readable.
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
   ...it's backed up on a tape somewhere.

Re: [Freetel-codec2] Incident Command System Automation

[Stuart L. <st...@lo...>]

On 12/3/26 02:57, Bruce Perens via Freetel-codec2 wrote:
> I'm not going to burden the freetel-codec2 group with repeated progress on
> this project, I just wanted to close out the conversation for now. The work
> on ICS forms is part of a much larger project that I am close to deploying
> and you will see it when I do. There is, however, an opportunity to improve
> on the ICS workflow currently presented by Winlink, which I experienced
> while working for a local sheriff's communications team. And this is
> related to freetel-codec2 because David's data modems would obviously be
> part of the project.

Is there a mailing list where we can discuss this further so we're not 
clogging up the Codec2 list?

I've been looking at doing something similar for my emergency comms 
group.  At the moment the pieces of the stack that I'm investigating are:

- Data link layer: at the moment prototyping with 1200 baud AFSK KISS 
TNCs (I know 1200 baud AFSK over FM is a lemon in terms of noise 
performance but we've got TNCs coming out our ears) but other options 
like ARDOP and FreeDV Data are doable.
- Link layer: AX.25 packet (it's well established and widely understood) 
and possibly Net/ROM.
- Routing layer: UUCP (again, well understood technology)

Into this, SMTP servers like Postfix can readily integrate.  So atop 
this, a IMAP server for message accessibility and a user agent like 
Roundcube.  Those forms then become part of a Roundcube plug-in that 
integrates FEMA message forms into the whole stack.

As a proof-of-concept, there is a system doing something similar: HERMES 
is a packet radio system that utilises UUCP over ARDOP to deliver email, 
they've also expanded it with in-transport CODEC transcoding to allow 
delivery of voice mail, images and apparently short videos as well.

https://www.rhizomatica.org/hermes/

I wouldn't copy this verbatim: for the voice mail part, I think I see 
mention of MELPe, replacing that with Codec2 would be a much better 
option in my opinion, but the concept is sound, and it's clear that it 
does in fact work.  ARDOP seems to be capable of around 1-2kbps, so in 
the same realm of 1200-baud AFSK (in theory; ignoring noise performance 
for now), so the FreeDV data modem could be a big improvement.

UUCP does have the downside that the current implementations of it (e.g. 
Taylor UUCP) assume a "fixed" list of nodes that will never change, but 
I'm not certain that's a requirement of the protocol.

Net/ROM can manage finding a node across a couple of hops and establish 
a connection.  Over that, UUCP manages the file transport and more 
distant routing.  Alternatively, APRS can be used to "ping" a node, 
discover a possible digipeater path, then regular AX.25 used over the 
discovered route.

With some careful work in the interfacing layer to UUCP, you could 
automatically determine a route to the destination via AX.25 or Net/ROM 
nodes to direct a message whereever it is needed.

Regards,
-- 
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
   ...it's backed up on a tape somewhere.

Re: [Freetel-codec2] Incident Command System Automation

[Bruce P. <br...@pe...>]

I'm not going to burden the freetel-codec2 group with repeated progress on
this project, I just wanted to close out the conversation for now. The work
on ICS forms is part of a much larger project that I am close to deploying
and you will see it when I do. There is, however, an opportunity to improve
on the ICS workflow currently presented by Winlink, which I experienced
while working for a local sheriff's communications team. And this is
related to freetel-codec2 because David's data modems would obviously be
part of the project.

I developed yesterday,guiding an AI to do the actual programming, a
heuristic program that ingests the actual FEMA forms much better, making up
for much sloppiness in the way people use Adobe Acrobat to make them. It's
perfect now on the 209 form, which is the most complex one, looks exactly
like the PDF, and has some niceties like linking the same-named fields
together (for example, there is Incident_Name and Incident_Number on each
page) and detecting fields that weren't designated as numeric by context.
The exact field names used by FEMA in Acrobat are used. Unlike Winlink, the
forms are not graphically modified as they are converted to SVG and HTML,
and transport data would be outside of the form. Z layers are used to be
easy on the renderer - when the cursor blinks it doesn't have to re-render
everything, and this stops Chrome "Aw Snap!" crashes. There are a few
glitches that existed when the forms departed FEMA that might be best fixed
with Acrobat (unless there is another good PDF editor capable of doing
that).

The opportunities that I see over the present Winlink.

1. Portability and device indepdenence: there is much opportunity for
handheld devices to be used in the field, and these run Android or iOS,
Windows portables other than Surface are no longer popular, and I can't say
much for Surface adoption. It is also a fact that rugged tablets and
Chromebooks that don't run Windows are much less expensive than my
Panasonic FG-Z1, and emergency responders already have them in hand and are
familiar with their operation. And finaly, let's get rid of the "Win" in
Winlink. Linux should be an option, as should whatever OS is in the device
you wish to use. Using portable Python3 and the web browser as an interface
seems to make this easily done.

2. Multi-Head per transport: The workflow in our sheriff's EOC was not
optimal. There was one person running Winlink and most communcations went
through her, and her workload was very high. Having multiple heads per RF
transport would be a better idea.

3. Transport independence. Winlink can work with a couple of RF modems,
obviously being able to slip a transport program into the system without
regard to the kind of transport would be optimal. David's data modems would
be an obvious choice.

With this said, I am going to finish the bigger project first, and the
capability to edit the ICS forms and transport them as JSON will be part of
it. The rest of this will be shelved until I am satisfied with the larger
project, unless someone else wants to take it up.

    Thanks

    Bruce



On Mon, Mar 9, 2026 at 1:19 PM Bruce Perens <br...@pe...> wrote:

> I found the site where all of this is available for download. They
> transmit the data as a normal ASCII email message with known fields, and
> can reconstitute it into the form. They don't seem to have many of the FEMA
> forms (I have all of them), but they have a large collection of local
> forms. It would be no problem to interoperate with, but I think could be
> improved. They don't even have a checksum on the data, I guess relying on
> the Winliink transport.
>
> I am talking with a FEMA guy about this. The accounting load on them is
> something we don't often see. Every resource is accounted for, and if a
> state uses its FEMA funds improperly, they have to pay FEMA back. They had
> an old proposal to integrate the forms process into an accounting backend
> for logistics and accounting. I would implement it using Odoo and AI
> assistance for the coding (see
> https://github.com/BrucePerens/hams_community for my AI framework), but
> don't yet have all of the details necessary to do so.
>
>     Thanks
>
>     Bruce
>
> On Mon, Mar 9, 2026 at 11:12 AM Don Reid <don...@db...> wrote:
>
>> I don't have a spec.  Here is an example.
>>
>>
>> -----------------------------------------------------------------------------------------------------------------------------------------------------
>>
>> GENERAL MESSAGE (ICS 213)
>>
>> ** THIS IS AN EXERCISE **
>> 1. Incident Name: ODMT Winter FTX
>>
>

-- 
Bruce Perens K6BP

Re: [Freetel-codec2] Incident Command System Automation

[Don R. <don...@db...>]

The ICS forms are under a separate heading from the FEMA ones.

    ICS201
    ICS202
    ICS203
    ICS205
    ICS204
    ICS205A
    iCS205b
    ICS206
    ICS208
    ICS210
    ICS213
    ICS213RR
    ICS214
    ICS214A
    ICS215A
    ICS217A
    ICS309

Don - W7DMR

On 3/9/26 13:19, Bruce Perens via Freetel-codec2 wrote:
> I found the site where all of this is available for download. They 
> transmit the data as a normal ASCII email message with known fields, 
> and can reconstitute it into the form. They don't seem to have many of 
> the FEMA forms (I have all of them), but they have a large collection 
> of local forms. It would be no problem to interoperate with, but I 
> think could be improved. They don't even have a checksum on the data, 
> I guess relying on the Winliink transport.
>
> I am talking with a FEMA guy about this. The accounting load on them 
> is something we don't often see. Every resource is accounted for, and 
> if a state uses its FEMA funds improperly, they have to pay FEMA back. 
> They had an old proposal to integrate the forms process into an 
> accounting backend for logistics and accounting. I would implement it 
> using Odoo and AI assistance for the coding (see 
> https://github.com/BrucePerens/hams_community for my AI framework), 
> but don't yet have all of the details necessary to do so.
>
>     Thanks
>
>     Bruce
>
> On Mon, Mar 9, 2026 at 11:12 AM Don Reid <don...@db...> wrote:
>
>     I don't have a spec.  Here is an example.
>
>     -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>     GENERAL MESSAGE (ICS 213)
>
>     ** THIS IS AN EXERCISE **
>     1. Incident Name: ODMT Winter FTX
>
>
>
> _______________________________________________
> Freetel-codec2 mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Re: [Freetel-codec2] Incident Command System Automation

[Bruce P. <br...@pe...>]

I found the site where all of this is available for download. They transmit
the data as a normal ASCII email message with known fields, and can
reconstitute it into the form. They don't seem to have many of the FEMA
forms (I have all of them), but they have a large collection of local
forms. It would be no problem to interoperate with, but I think could be
improved. They don't even have a checksum on the data, I guess relying on
the Winliink transport.

I am talking with a FEMA guy about this. The accounting load on them is
something we don't often see. Every resource is accounted for, and if a
state uses its FEMA funds improperly, they have to pay FEMA back. They had
an old proposal to integrate the forms process into an accounting backend
for logistics and accounting. I would implement it using Odoo and AI
assistance for the coding (see https://github.com/BrucePerens/hams_community
for my AI framework), but don't yet have all of the details necessary to do
so.

    Thanks

    Bruce

On Mon, Mar 9, 2026 at 11:12 AM Don Reid <don...@db...> wrote:

> I don't have a spec.  Here is an example.
>
>
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> GENERAL MESSAGE (ICS 213)
>
> ** THIS IS AN EXERCISE **
> 1. Incident Name: ODMT Winter FTX
>

[Freetel-codec2] forms

[Daniel C. <do...@mi...>]

  If you have winlink all the forms are listed under message > manage 
html forms.

k6dlc

-- 
Daniel Curry   A.A., B.A
U.S. Air Force Veteran
IPV6 Sage Certified
PGP: AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92
forms

Re: [Freetel-codec2] Incident Command System Automation

[Don R. <don...@db...>]

I don't have a spec.  Here is an example.

-----------------------------------------------------------------------------------------------------------------------------------------------------

GENERAL MESSAGE (ICS 213)

** THIS IS AN EXERCISE **
1. Incident Name: ODMT Winter FTX
2. To (Name and Position): Local Radio Operators
3. From (Name and Position): Don Reid - W7DMR : Wren Digital RADO
4. Subject: Winink test
5. Date: 2026-02-21
6. Time: 11:46
7. Message:

We are not finding good HF RMS stations to talk to with the NVIS 
antennas we have setup.  I found one, W7OWO on 40m.
Telnet via a Starlink connection works well even at the low 500k baud 
"Standby" service.

8. Approved by: Don Reid
8a. Position/Title: RADO
     [Sender: W7DMR Lat: 45.562500, Lon:-122.875000, MGRS: ; Location 
source: Grid square]
------------------------------------
Express Sending Station: W7DMR
Senders Express Version: 1.7.23.0
Senders Template Version: ICS 213  v.43.8
[No changes or editing of this message are allowed]

-----------------------------------------------------------------------------------------------------------------------------------------------------

They combine these with templates that are sent when needed.  The local 
web browser is used to create and display messages.

Attached are the template files for this one.

On 3/9/26 08:12, Bruce Perens via Freetel-codec2 wrote:
> On Mon, Mar 9, 2026 at 5:50 AM Don Reid <don...@db...> wrote:
>
>     The winlink system uses a nice text format that is both human and
>     machine readable.
>
>
> I'm not running Winlink. Is the ICS text format documented anywhere? I 
> spoke with a friend at FEMA and they wanted a document management 
> system but did not get funding to develop one.
>
>     Thanks
>
>     Bruce
>
>
> _______________________________________________
> Freetel-codec2 mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2

Re: [Freetel-codec2] Freetel-codec2 Digest, Vol 188, Issue 1

[David W. <wi...@ww...>]

Bruce,

Great!
This has been needed for so long.

Davw Witten, KD0EAG

On Mon, 9 Mar 2026 at 07:44, <fre...@li...>
wrote:

> Send Freetel-codec2 mailing list submissions to
>         fre...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.sourceforge.net/lists/listinfo/freetel-codec2
> or, via email, send a message with subject or body 'help' to
>         fre...@li...
>
> You can reach the person managing the list at
>         fre...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Freetel-codec2 digest..."
>
>
> Today's Topics:
>
>    1. Incident Command System Automation (Bruce Perens)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 9 Mar 2026 00:54:41 -0700
> From: Bruce Perens <br...@pe...>
> To: Bruce Perens via Freetel-codec2
>         <fre...@li...>
> Subject: [Freetel-codec2] Incident Command System Automation
> Message-ID:
>         <CAK2MWOvSeDCU=
> g_A...@ma...>
> Content-Type: text/plain; charset="utf-8"
>
> For folks who wish to innovate in emergency services communications over
> Amateur Radio, I have created a system to fill out all of the Incident
> Command System forms online, convert the fields to compact JSON, and send
> them over the air (manually so far) and then reconstitute them as the PDF
> form at the other end. This is potentially the seed of automating the
> entire ICS workflow. It's a portable Python3 program and should work on
> anything that hosts Python.
>
> https://github.com/BrucePerens/incident_command
>
>     Thanks
>
>     Bruce
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Freetel-codec2 mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>
>
> ------------------------------
>
> End of Freetel-codec2 Digest, Vol 188, Issue 1
> **********************************************
>

Re: [Freetel-codec2] Incident Command System Automation

[Bruce P. <br...@pe...>]

On Mon, Mar 9, 2026 at 5:50 AM Don Reid <don...@db...> wrote:

> The winlink system uses a nice text format that is both human and machine
> readable.
>

I'm not running Winlink. Is the ICS text format documented anywhere? I
spoke with a friend at FEMA and they wanted a document management system
but did not get funding to develop one.

    Thanks

    Bruce

Re: [Freetel-codec2] Incident Command System Automation

[Don R. <don...@db...>]

The winlink system uses a nice text format that is both human and machine readable.

Don - W7DMR

On March 9, 2026 12:54:41 AM PDT, Bruce Perens via Freetel-codec2 <fre...@li...> wrote:
>For folks who wish to innovate in emergency services communications over
>Amateur Radio, I have created a system to fill out all of the Incident
>Command System forms online, convert the fields to compact JSON, and send
>them over the air (manually so far) and then reconstitute them as the PDF
>form at the other end. This is potentially the seed of automating the
>entire ICS workflow. It's a portable Python3 program and should work on
>anything that hosts Python.
>
>https://github.com/BrucePerens/incident_command
>
>    Thanks
>
>    Bruce

[Freetel-codec2] Incident Command System Automation

[Bruce P. <br...@pe...>]

For folks who wish to innovate in emergency services communications over
Amateur Radio, I have created a system to fill out all of the Incident
Command System forms online, convert the fields to compact JSON, and send
them over the air (manually so far) and then reconstitute them as the PDF
form at the other end. This is potentially the seed of automating the
entire ICS workflow. It's a portable Python3 program and should work on
anything that hosts Python.

https://github.com/BrucePerens/incident_command

    Thanks

    Bruce

[Freetel-codec2] [Announcement] FreeDV Activity Day - February 21-22, 2026

[Mooneer S. <mo...@gm...>]

Hi all,

This is a reminder that this month's FreeDV Activity Day is this coming
weekend. (As a reminder, Activity Day takes place on the third weekend of
every month.) This event will bring together people interested in HF
digital voice on the air for conversation and fun. Contacts using the
official application as well as ezDV, the SM1000 handheld microphone and
other supporting devices and applications are welcome.

Event time: 12AM Pacific time (0800Z) on February 21 to 11:59PM on February
22 (0759Z on February 23) (48 hours).

Suggested frequencies:
160 meters: 1.997 MHz
80 meters: 3.625, 3.643, 3.693, 3.697 MHz or 3.803 MHz
60 meters (in countries where allowed): 5.4035 MHz or 5.3665 MHz
40 meters: 7.177 MHz or 7.197 MHz
20 meters: 14.236 MHz or 14.240 MHz
17 meters: 18.118 MHz
15 meters: 21.313 MHz
12 meters: 24.933 MHz
10 meters: 28.330 or 28.720 MHz
10 GHz (for those in range of QO-100): 10489.640 MHz

(Note that LSB/DIGL is used below 10MHz as per current convention for voice
modes, USB/DIGU otherwise. 60 meters is of course USB/DIGU only.)

As this isn't a contest, there's no pressure to make contacts or send logs,
but you can always confirm QSOs via the usual means if you'd like (LoTW,
eQSL, QRZ, etc.) Enabling reporting (PSK Reporter and FreeDV Reporter) in
the FreeDV application and joining FreeDV Reporter and Discord are
recommended, however, so others can see that you're on the air and hearing
them (for instance, here's the current map of listeners). :D

Feel free to spread this far and wide among your local ham friends and
groups! :) Let me know if you have any questions about the event and
definitely post here if you have issues getting the application working
prior to the event.

Thanks,

-Mooneer K6AQ

Re: [Freetel-codec2] FreeDV at HamCation

[Mooneer S. <mo...@gm...>]

Hi Kelvin,

Yep, that's the plan.

Thanks,

-Mooneer K6AQ

On Fri, Feb 13, 2026, 11:29 AM Kelvin Vanderlip <ke...@va...>
wrote:

> Dear Mouneer,
> Can you post your talk, or the presentation slides, for those who are not
> in Orlando? I use FreeDV myself, and I am working in The Palos Verdes
> Amateur Club to bring more hams into this great project.
> Thank you,
> Kelvin W6KCV
>
>
> On February 12, 2026 6:36:30 PM PST, Mooneer Salem <mo...@gm...>
> wrote:
>
>> Hi all,
>>
>> Sorry for the late notice but we'll be at HamCation in Orlando, FL this
>> weekend. Come stop by our booth in the North Hall (right across from the
>> prize booth) and definitely check out the FreeDV talk I'll be giving at
>> 3:30pm tomorrow :)
>>
>> Thanks,
>>
>> -Mooneer K6AQ
>>
> _______________________________________________
> Freetel-codec2 mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>

Re: [Freetel-codec2] FreeDV at HamCation

[Kelvin V. <ke...@va...>]

Dear Mouneer,
Can you post your talk, or the presentation slides, for those who are not in Orlando? I use FreeDV myself, and I am working in The Palos Verdes Amateur Club to bring more hams into this great project.
Thank you,
Kelvin W6KCV


On February 12, 2026 6:36:30 PM PST, Mooneer Salem <mo...@gm...> wrote:
>Hi all,
>
>Sorry for the late notice but we'll be at HamCation in Orlando, FL this
>weekend. Come stop by our booth in the North Hall (right across from the
>prize booth) and definitely check out the FreeDV talk I'll be giving at
>3:30pm tomorrow :)
>
>Thanks,
>
>-Mooneer K6AQ

[Freetel-codec2] FreeDV at HamCation

[Mooneer S. <mo...@gm...>]

Hi all,

Sorry for the late notice but we'll be at HamCation in Orlando, FL this
weekend. Come stop by our booth in the North Hall (right across from the
prize booth) and definitely check out the FreeDV talk I'll be giving at
3:30pm tomorrow :)

Thanks,

-Mooneer K6AQ

[Freetel-codec2] FreeDV 2.2.1 released

[Mooneer S. <mo...@gm...>]

Hi all,

FreeDV 2.2.1 has been released, containing bugfixes for issues discovered
since the release of 2.2.0 along with a change to ensure continued
operation of the FlexRadio integration. It can be downloaded using the
following links:

* Windows:
https://github.com/drowe67/freedv-gui/releases/download/v2.2.1/FreeDV-2.2.1-windows-x86_64.exe
* Linux AppImage (for Intel and AMD PCs):
https://github.com/drowe67/freedv-gui/releases/download/v2.2.1/FreeDV-2.2.1-x86_64.AppImage
* Linux AppImage (for ARM systems, e.g. Raspberry Pi 5+):
https://github.com/drowe67/freedv-gui/releases/download/v2.2.1/FreeDV-2.2.1-aarch64.AppImage
* Linux AppImage for FlexRadio support (needs Raspberry Pi 4 or newer):
https://github.com/drowe67/freedv-gui/releases/download/v2.2.1/FreeDV-FlexRadio-2.2.1-aarch64.AppImage
* macOS:
https://github.com/drowe67/freedv-gui/releases/download/v2.2.1/FreeDV.dmg

More information about this release can be found on GitHub release page:
https://github.com/drowe67/freedv-gui/releases/tag/v2.2.1

Thanks,

-Mooneer K6AQ

Re: [Freetel-codec2] FreeDV 2.2.0 released

[Mooneer S. <mo...@gm...>]

Unfortunately, there is no ETA for this as of yet. This is because work to
do so will likely be part of RADEV2, which itself has no ETA for release.

-Mooneer K6AQ

On Wed, Jan 28, 2026, 8:52 PM Ashhar Farhan <far...@gm...> wrote:

> Moneer,
> thanks for the update! Is there a timeline to making the rade codec pure
> C/C++ ?
>
> On Thu, Jan 29, 2026 at 4:47 AM Mooneer Salem <mo...@gm...> wrote:
>
>> Hi all,
>>
>> FreeDV 2.2.0 has been released, containing bugfixes and feature
>> enhancements, including integration with logging software and enhancements
>> to the previously released FlexRadio integration. It can be downloaded
>> using the following links:
>>
>> Windows:
>> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-windows-x86_64.exe
>> Linux AppImage (for Intel and AMD PCs):
>> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-x86_64.AppImage
>> Linux AppImage (for ARM systems, e.g. Raspberry Pi 5+):
>> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-aarch64.AppImage
>> Linux AppImage for FlexRadio support (needs Raspberry Pi 4 or newer):
>> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-FlexRadio-2.2.0-aarch64.AppImage
>> macOS:
>> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV.dmg
>>
>> More information about this release can be found on GitHub release page:
>> https://github.com/drowe67/freedv-gui/releases/tag/v2.2.0
>>
>> Thanks,
>>
>> -Mooneer K6AQ
>> _______________________________________________
>> Freetel-codec2 mailing list
>> Fre...@li...
>> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>>
> _______________________________________________
> Freetel-codec2 mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>

Re: [Freetel-codec2] FreeDV 2.2.0 released

[Ashhar F. <far...@gm...>]

Moneer,
thanks for the update! Is there a timeline to making the rade codec pure
C/C++ ?

On Thu, Jan 29, 2026 at 4:47 AM Mooneer Salem <mo...@gm...> wrote:

> Hi all,
>
> FreeDV 2.2.0 has been released, containing bugfixes and feature
> enhancements, including integration with logging software and enhancements
> to the previously released FlexRadio integration. It can be downloaded
> using the following links:
>
> Windows:
> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-windows-x86_64.exe
> Linux AppImage (for Intel and AMD PCs):
> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-x86_64.AppImage
> Linux AppImage (for ARM systems, e.g. Raspberry Pi 5+):
> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-aarch64.AppImage
> Linux AppImage for FlexRadio support (needs Raspberry Pi 4 or newer):
> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-FlexRadio-2.2.0-aarch64.AppImage
> macOS:
> https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV.dmg
>
> More information about this release can be found on GitHub release page:
> https://github.com/drowe67/freedv-gui/releases/tag/v2.2.0
>
> Thanks,
>
> -Mooneer K6AQ
> _______________________________________________
> Freetel-codec2 mailing list
> Fre...@li...
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>

[Freetel-codec2] FreeDV 2.2.0 released

[Mooneer S. <mo...@gm...>]

Hi all,

FreeDV 2.2.0 has been released, containing bugfixes and feature
enhancements, including integration with logging software and enhancements
to the previously released FlexRadio integration. It can be downloaded
using the following links:

Windows:
https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-windows-x86_64.exe
Linux AppImage (for Intel and AMD PCs):
https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-x86_64.AppImage
Linux AppImage (for ARM systems, e.g. Raspberry Pi 5+):
https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-2.2.0-aarch64.AppImage
Linux AppImage for FlexRadio support (needs Raspberry Pi 4 or newer):
https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV-FlexRadio-2.2.0-aarch64.AppImage
macOS:
https://github.com/drowe67/freedv-gui/releases/download/v2.2.0/FreeDV.dmg

More information about this release can be found on GitHub release page:
https://github.com/drowe67/freedv-gui/releases/tag/v2.2.0

Thanks,

-Mooneer K6AQ

[Freetel-codec2] [Announcement] FreeDV Activity Day - January 17-18, 2026

[Mooneer S. <mo...@gm...>]

Hi all,

This is a reminder that this month's FreeDV Activity Day is this coming
weekend. (As a reminder, Activity Day takes place on the third weekend of
every month.) This event will bring together people interested in HF
digital voice on the air for conversation and fun. Contacts using the
official application as well as ezDV, the SM1000 handheld microphone and
other supporting devices and applications are welcome.

Event time: 12AM Pacific time (0800Z) on January 17 to 11:59PM on January
18 (0759Z on January 19) (48 hours).

Suggested frequencies:
160 meters: 1.997 MHz
80 meters: 3.625, 3.643, 3.693, 3.697 MHz or 3.803 MHz
60 meters (in countries where allowed): 5.4035 MHz or 5.3665 MHz
40 meters: 7.177 MHz or 7.197 MHz
20 meters: 14.236 MHz or 14.240 MHz
17 meters: 18.118 MHz
15 meters: 21.313 MHz
12 meters: 24.933 MHz
10 meters: 28.330 or 28.720 MHz
10 GHz (for those in range of QO-100): 10489.640 MHz

(Note that LSB/DIGL is used below 10MHz as per current convention for voice
modes, USB/DIGU otherwise. 60 meters is of course USB/DIGU only.)

As this isn't a contest, there's no pressure to make contacts or send logs,
but you can always confirm QSOs via the usual means if you'd like (LoTW,
eQSL, QRZ, etc.) Enabling reporting (PSK Reporter and FreeDV Reporter) in
the FreeDV application and joining FreeDV Reporter and Discord are
recommended, however, so others can see that you're on the air and hearing
them (for instance, here's the current map of listeners). :D

Feel free to spread this far and wide among your local ham friends and
groups! :) Let me know if you have any questions about the event and
definitely post here if you have issues getting the application working
prior to the event.

Thanks,

-Mooneer K6AQ

[Freetel-codec2] [Announcement] FreeDV Activity Day - December 20-21, 2025

[Mooneer S. <mo...@gm...>]

Hi all,

This is a reminder that this month's FreeDV Activity Day is this coming
weekend. (As a reminder, Activity Day takes place on the third weekend of
every month.) This event will bring together people interested in HF
digital voice on the air for conversation and fun. Contacts using the
official application as well as ezDV, the SM1000 handheld microphone and
other supporting devices and applications are welcome.

Event time: 12AM Pacific time (0800Z) on December 20 to 11:59PM on December
21 (0759Z on December 22) (48 hours).

Suggested frequencies:
160 meters: 1.997 MHz
80 meters: 3.625, 3.643, 3.693, 3.697 MHz or 3.803 MHz
60 meters (in countries where allowed): 5.4035 MHz or 5.3665 MHz
40 meters: 7.177 MHz or 7.197 MHz
20 meters: 14.236 MHz or 14.240 MHz
17 meters: 18.118 MHz
15 meters: 21.313 MHz
12 meters: 24.933 MHz
10 meters: 28.330 or 28.720 MHz
10 GHz (for those in range of QO-100): 10489.640 MHz

(Note that LSB/DIGL is used below 10MHz as per current convention for voice
modes, USB/DIGU otherwise. 60 meters is of course USB/DIGU only.)

As this isn't a contest, there's no pressure to make contacts or send logs,
but you can always confirm QSOs via the usual means if you'd like (LoTW,
eQSL, QRZ, etc.) Enabling reporting (PSK Reporter and FreeDV Reporter) in
the FreeDV application and joining FreeDV Reporter and Discord are
recommended, however, so others can see that you're on the air and hearing
them (for instance, here's the current map of listeners). :D

Feel free to spread this far and wide among your local ham friends and
groups! :) Let me know if you have any questions about the event and
definitely post here if you have issues getting the application working
prior to the event.

Thanks,

-Mooneer K6AQ