JS8Call QSO Party

The first official JS8 QSO Party is now open! If you haven't had an opportunity to make many JS8 QSOs...now is your chance! For more detail: https://groups.io/g/js8call/viewevent?eventid=361585&calstart=2018-10-19

Many stations will be running JOTA on Saturday so keep an eye out for 'em! If you're a JOTA station, feel free to call: "CQ JOTA CQ K" or similar.

Here's how I'll be calling during the weekend: "CQ QSO PARTY CQ K"

If you have any questions, feel free to respond in this thread so everybody can chime in. You can also use the sked chat for announcements: https://groups.io/g/js8call/chat/1422

I've loaded up the latest version (0.75) but haven't managed to find anyone to work, so hope to get someone in the log this weekend.

73

Jim
ZL1LC

FT8 Call is dead. Long Live JS8Call

FT8Call is no longer.  It has morphed into JS8Call.  The JS comes from the creator Jordan Sherer, KN4CRD.

He has released a significantly  upgraded version, version 0.7 which may be found at  https://groups.io/g/js8call/message/1251  

Remember it is not backward compatible with earlier versions such as 0.5.

Look forward to chatting with you.

73

Jim

ZL1LC

FT8CALL Version 0.6

Here's the latest news on FT8Call.  Not that the newest version is not backward compatible with the earlier version.

Another week down and another release of FT8Call on the books. I'm excited to bring you the next development version of FT8Call, version 0.6. Version 0.5 expires on Monday, and 0.6 is backwards incompatible, so you'll need to upgrade as soon as possible. If you want to cut to the chase, head over to the download page to grab the new version: https://groups.io/g/ft8call/wiki/FT8Call-Latest-Release-Download-Links

If you forgot what FT8Call is...not a problem. It's an experimental amateur radio application to test the feasibility of a digital mode with the robustness of FT8, combined with a messaging and network protocol layer for weak signal communication on HF, using keyboard-to-keyboard style interface. And...the experiment is working! There are operators all over the world trying out FT8Call and having success when other modes have not worked for them. I like to say...it's better to communicate slowly than to not be able to communicate at all. 

There's some new stuff included in 0.6 so don't forget to read up on the documentation: https://docs.google.com/document/d/159S4wqMUVdMA7qBgaSWmU-iDI4C9wd4CuWnetN68O9U/edit?usp=sharing

FT8Call version 0.5

Just received this.

Howdy Folks,

I'm excited to bring you the next development version of FT8Call, version 0.5, and boy do I have some fun stuff included in here for you! If you forgot what FT8Call is, no worries... it's an experiment to test the feasibility of message passing over FT8 modulation using a new protocol (but, it has certainly evolved into a lot more than that now!).

If you want to cut to the chase, head over to the download page to grab the new version: https://groups.io/g/ft8call/wiki/FT8Call-Latest-Release-Download-Links

But also, don't forget to read up on the documentation: https://docs.google.com/document/d/159S4wqMUVdMA7qBgaSWmU-iDI4C9wd4CuWnetN68O9U/edit?usp=sharing

There is also a new website: http://ft8call.info/ that you should bookmark. We'll eventually be transitioning documentation and download links over to the new site.

So, without further to do, here are the notable changes in 0.5:

* There's a compiled MacOS version :)

* Directed messages are now the default if you have a callsign selected. You shouldn't have to double click the call for each subsequent message.

* New Frequencies. Sliding down 2kHz for most bands into the JT9 territory. Now, before you grab your pitchforks...the application also is blocking transmitting in the lower 500Hz of the passband. This means that there's enough room for over 25 simultaneous JT9 signals on their frequencies:

160m: 1.842 MHz // 2kHz above FT8

80m: 3.578 MHz // 5kHz above FT8

40m: 7.078 MHz // 4kHz above FT8

30m: 10.130 MHz // 6kHz below FT8

20m: 14.078 MHz // 4kHz above FT8

17m: 18.104 MHz // 4kHz above FT8

15m: 21.078 MHz // 4kHz above FT8

12m: 24.922 MHz // 9kHz above FT8

10m: 28.078 MHz // 4kHz above FT8

6m: 50.318 MHz // 5kHz above FT8

* Added a new GRID directed message that allows grid locators up to 12 characters to be transmitted. For those grids, we now allow spotting to both PSKReporter and APRS-IS! (APRS-IS will receive spots for locators >= 6 chars, and you can configure which APRS-IS server to spot to)

* You can also send and spot raw APRS packets, but that's undocumented for now ;) Email me if you'd like to know how to use it!

* You can now send a query to see if another station has heard a specific station with the "QSO" query. e.g., ALLCALL QSO KN4CRD? This is helpful if you're trying to set up a relay to a specific station.

* The band activity, call activity and rx windows are now restored when switching to and from other bands.

* Added some new generic directed messages.

* Added a "REPLY" button, so there's no more question about how to reply to a CQ. This message is configurable, but it defaults to "HW CPY?" so new users know what to do.

* You can now sort the band activity and call activity windows!

* Improved the usability of the waterfall.

* Removed the PWR command. It wasn't being used frequently. Feel free to put your power level in your QTC message!

* Squashed a ton of bugs!

I hope you enjoy testing this new version! Let me know if you run into anything weird or have any other improvements to the application. Most of these changes above came from feature requests from other operators. Your great idea could be next!

One last thing before I go... the ft8call groups.io is switching from an announcement-only group to a discussion group. If you're not interested in discussion...head over to your preferences https://groups.io/g/ft8call/editsub and select to receive "Special Notices Only" (these emails).

Cheers!

Best,

Jordan / KN4CRD

FT8CALL

Everyone knows FT8 has taken over the bands since it was introduced just over a year ago.  I looked at the 12 hour data on PSKReporter PSK Reporter Band Activity  and it was the mode of choice for 95% of QSO on all modes including SSB and CW.  The problem with FT8 is that it is basically a PC to PC mode and is often called a "zombie" mode, but it gets through in our poor propagation far better than any other mode.

Some smart characters have taken the FT8 concepts and engineered a new mode called FT8CALL, which has the same noise resistant characteristics and transmits a character per second but allows a keyboard to keyboard chat.  It does this by splitting the messages into 15 second bursts, just like FT8, and, by using a different encoding method, allows symbols to represent blocks of text.  Look at the video FT8CALL Video for a good introduction. 

Go to Groups.IO to download the software via the link Groups.IO Download  Unfortunately IOS is not yet supported but it is supported on versions of Linux, Raspberry Pi and Windows 10, so I'm running it on a separate device. 

FT8 and FT8CALL do not work together, and use different frequencies.  

There's a few new smarts in FT8CALL, including one that looks like it has been taken from FSQ, where the transmitting station sends out an All Stations message, and receive replies, including signal reports, from all station that can hear his transmission.

Look forward to working you on this new mode.

73

Jim

ZL1LC

Update  I hear FT8CALL version 0.5 is due out in a few days.  Check the download website on 1 September.

Version 1.9.1 of FT8 now out

I see that there was an updated version of FT8 released at the beginning of the month.

Get the latest download from FT8 Download

It doesn't seem to crash on the Decode button as the 1.9.0 version did.

See you on the bands.

Think about your eyes

We all spend too much time looking at display screens, more so if we are running digital modes.  

Have a look at Blue Light

It will give you some ideas as to how to protect your eyes and make them last a little longer.