Articles‎ > ‎

JS8CALL

Updated Dec 2018


There’s a new kid on the block and his name is FT8CALL JS8CALL. Still in development, the mode is based on FT8 but is designed for typed QSOs rather than semi-automated exchanges. Usage is shooting up, at least according to PSK Reporter. While it isn’t a product of Joe Taylor, K1JT, it appears to use the WSJT-X codebase with an extra layer that handles the text-encoding. Hence it uses a new mode, JS8. This does mean that the JS8CALL software doesn’t decode FT8 signals and vice versa. It almost certainly also means it will be a little less robust than FT8.

 

JS8CALL, originally known as FT8CALL, has been developed by Jordan, KN4CRD. He has put together documentation on the new software which contains links to the latest releases. You can find it here: https://docs.google.com/document/d/159S4wqMUVdMA7qBgaSWmU-iDI4C9wd4CuWnetN68O9U/preview#

 

JS8CALL is still under (very) active development so keep an eye on js8call.com for the latest news. The development releases have a lifetime of 10 days, so you will need to keep updating if you want to keep using the mode.


And here was my first go (of FT8CALL) - a set of automatic responses from stations in Beacon (now much changed) mode - you could send commands by putting a special character after their callsign and can get QTH, signal reports, TX power, station details etc




And here the blue labels show the stations that uploaded spots of my 40m transmissions to pskreporter.info:


I also had a regular QSO with 5P6MJ,  although I don't think of us really knew what we were doing. It was very confusing because another station seemed to start a QSO with him at the same time!

73 de Mike G4RAA
Comments