After working faultlessly for several days on 6m FT8, I am getting an error message when I try to TX on 10m FT8 with the IC-705.
I checked the COM ports and audio selection (all fine). I re-installed WSJT-X v2.6 (same issue). The next thing is to re-install sound cards on the IC-705 and try again.
Apparently WSJT-X 2.7.1 is now on general release. There is a YouTube video all about it. I shall have to download the new version and have a play.
UPDATE 1050z: No it is not!! I just looked and I could only see this as a release candidate. I expect it soon will be on general release.
I deleted lots of WAV files from my PC (WSJT-X saves them all!!) and this allowed me to do a Windows update.
However, for some reason, after doing a restart on my QDX I can receive OK, it does not TX on FT8. I checked this on my QMX+ and that does not TX either. It seems to recognise the QDX audio and CAT control works on the QMX+.
At the moment I am on 10m QRP WSPR with my stand-alone 500mW WSPR beacon (no spots on this as well!).
I think this must go down as a "bad hair day". In other words it's totally crap. My brain hurts!
UPDATE 1712z: In desperation, I am doing a full PC reset to factory settings to see if this fixes it. The PC is really only used with WSJT-X.
UPDATE 2151z: For some reason the PC still refuses to recognise the QDX. Tomorrow I shall try with the SignaLinkUSB and the FT817ND which should work. With Windows there must be some magic that I am missing to get the PC to “see” the QDX. Apparently it is all to do with the USB port recognising the QDX whereas with Linux there is no issue.
Those interested in digital modes may be pleased to hear that the latest release candidate of WSJT-X is available. I have no idea when this will be formally released.
Up to now, I have always used WSJT-X for FT8. There have been some reports that JTDX decodes more stations.
Do you have view please? I try to use the latest released version.
I have been told that WSJT-X has been generally released as V2.6.0. I use WSJT-X for both FT8 and WSPR. Later today I expect to download this version if it is generally released.
On the official website, it is still shown as a release candidate. Usually a new version is released about now, so perhaps my informant has advanced information?
Apparently there is a new version of WSJT-X available as a pre-release candidate. At the moment on WSPR and FT8 I use V2.5.4, which is the latest fully released version. The latest candidate release is V2.6-rc4. I must download it and try it.
FT8 is now very popular. It is possible the decode sensitivity is slightly better with this newer version.
For some reason (probably by mistake) I assumed that PI4 was one of the modes supported by WSJT-X. Imagine my surprise today when I found it not there. My version of WSJT-X is 2.5.4.
Instead I had to download some special software to decode PI4. I have not yet checked if there is a map upload a bit like PSKreporter maps.
I was hoping to decode one of the Irish beacons, EI1KNH/B on 40.013 MHz PI4.
If PI4 is not supported by WSJT-X why is it used rather than FT8 or WSPR by beacons? I don't think it is magically better than FT8.
My other questions are (1) what mode do I select and (2) what dial frequency do I set to decode EI1KNH/B in PI4? At the moment it is set to 40.013 DIG on the FT817ND, but I have no idea if this is correct.
UPDATE 2057z: It looks like EI1KNH/B now uses FT8 instead of PI4, so I am now monitoring FT8 instead. It sends FT8 every 10 minutes. See https://www.qrz.com/db/EI1KNH/. I shall monitor overnight.
So far today, I have received loads of stations on 10m FT8 RX despite most of the antenna being on the ground awaiting the erection of the 8m dipole.
I notice these were not being uploaded to PSKreporter for some reason, so I shall restart WSJT-X in case this is at fault.
UPDATE 1521z: I did a resync to internet time and restarted WSJT-X: still no spots on PSKreporter.
UPDATE 1530z: All now seems well, with 10 stations recently uploaded. This will remain a puzzle. All uploads relate to stations spotted in the last 20 minutes.
OFCOM has told me my permit to TX on 8m is coming. My intention is to send FT8 most of the time, with the occasional CW and WSPR.
I know my widebanded FT817ND produces power at 8m and is clean. I also know PSKreporter supports 8m. Then, last night, I had a sudden panic. Did WSJT-X support 8m?
This morning I checked - it does! I am sure with a hack it would have been possible, but in its standard form it does already.
I hope to do some local CW crossband tests as well initially. My permit should start in early April and last for a year.
My shack PC runs Windows 10. Currently it is almost exclusively used for WSJT-X.
At some point I may want to upgrade the Chromebook. If I do this, this current Chromebook might end up in the shack. Although the Chromebook will run Linux apps, I have never bothered.
Does anyone know how to install WSJT-X on a Chromebook please?
I am definitely NOT a computer nerd, so would need very simple instructions!
Both these modes are part of the WSJT-X suite from Joe Taylor.
WSPR needs about 6Hz of spectrum (not much) and 2 minutes for the most common form of WSPR. WSPR is really a beaconing mode.
FT8 is a communications mode and needs about 50Hz with 15 second TX slots. WSPR works with signals much weaker than FT8. FT8 works with signals much weaker than SSB or CW.
Both offer the minimum exchange of data and neither are "chatting" modes. As they work with very weak signals and need so little bandwidth they have been transformative in amateur radio. They are not instead of speech modes, but as well as.
There are other modes also available in the free WSJT-X suite.
Personally, I enjoy both modes, especially as my voice is poor since my 2013 stroke.
Today the released version of WSJT-X V2.3.0 was made available. Previously just release candidates were available.
With Windows 10 I had all sorts of issues as it tried to block the download in case it harmed the PC. I said "keep" and "install anyway". Only then could I go ahead.
The latest release candidate of WSJT-X has been released. It is rc4. When I tried to install it on my Windows 10 machine it kept blocking it. After going through the hoops several times I eventually installed it. This version runs until Feb 2nd when I expect to go through all this hassle again. I know why this is done: to keep the PC safe. rc3 no longer works after Jan 26th.
WSJT-X is used for FT8 and WSPR here
Southgate News reports that a new digital mode may be coming later this year called Q65 as part of WSJT-X suite. I have just downloaded the latest release candidate for WSJT-X (2.3.0-rc3), but I have not checked if it is there.
See https://physics.princeton.edu/pulsar/k1jt/Q65_Quick_Start.pdf
See http://www.southgatearc.org/news/2021/january/new-digital-protocol-q65.htm#.YAbrz_GTLrc
Since changing to the latest release candidate version of WSJT-X it has been totally stable on FT8, whereas with V2.2.2 I often had issues with my USB SignaLink with no decodes and smeary waterfalls. I use Windows 10 and I wonder if they did a bug fix? The difference is very noticeable.
For the last 12 hours or so, I have been using the latest "release candidate" version of WSJT-X, which is 2.3.0-rc2. Certainly on FT8 it appears stable and works well. The only thing I have found is an annoying pop-up box saying I do not have logbook of the world on my PC. I seem to recall this on an earlier version.
There is a "release candidate" version of WSJT-X that introduces some new modes. Normally, these are issued as fully released versions soon when they have been beta tested and bugs removed.
See https://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main-2.3.0-rc1_en.html
Several times I have noticed a bug with WSJT-X with FT8.
When I use my Windows 10 machine, it seems not to recognise my SignaLink USB interface until a few minutes after I have switched on. After a while it recognises it and starts to decode OK. Before then, signals on the waterfall look smeared and there are no decodes.
At first I thought it was RF feedback, but it seems to be any band and any antenna. I have still to try the new release candidate version 2.3 to see if this has been corrected.
I am more convinced than ever that WSJT-X has a bug with Windows-10. This never happened with earlier versions of WSJT-X. I am using the latest released version.
For some periods FT8 appears on the waterfall screen with smeary signals and no decodes. It is as if the decoder does not "get" the signals correctly. After a time it corrects itself and decoding starts.
This is a real pain.
I might try the latest release candidate to see if this is better.
Every few weeks I take a peek at the narrowband activity on Oscar 100, the geosynchronous satellite. My own view is activity is patheticall...
