Date
1 - 16 of 16
Locked Release Candidate WSJT-X 2.6.0-rc1 #general
|
Dear WSJT-X and MAP65 Users,
We are pleased to announce that Release Candidate WSJT-X 2.6.0-rc1 is ready for download by beta testers. This release has new capabilities beyond WSJT-X 2.5.4. A full list of enhancements can be found in the Release Notes: https://physics.princeton.edu//pulsar/k1jt/Release_Notes.txt Links for downloading WSJT-X 2.6.0 can be found on the WSJT-X Home Page, https://physics.princeton.edu/pulsar/k1jt/wsjtx.html Scroll down to find "Candidate release: WSJT-X 2.6.0-rc1". We hope you will enjoy using this beta release of WSJT-X 2.6.0 and MAP65 3.0.0, and exercising the new mode Q65. As a beta tester you should report on your experiences with new features, successful and otherwise, on one of the relevant WSJT forums. Bugs should be reported by following instructions found here in the User Guide: https://www.physics.princeton.edu//pulsar/K1JT/wsjtx-doc/wsjtx-main-2.6.0-rc1.html#_bug_reports WSJT-X and MAP65 are licensed under the terms of Version 3 of the GNU General Public License (GPLv3). Development of this software is a cooperative project to which many amateur radio operators have contributed. If you use our code, please have the courtesy to let us know about it. If you find bugs or make improvements to the code, please report them to us in a timely fashion. Additional licensing details can be found here: https://physics.princeton.edu//pulsar/k1jt/devel.html -- 73 from Joe, K1JT; Steve, K9AN; Nico, IV3NWV; Chet, KG4IYS; Uwe, DG2YCB; Brian, N9ADG; and John, G4KLA |
|
|
|
Gary Rogers
I’ve installed on Windows 10, MacOS 12.4 and Raspberry Pi using the provided installers. All seem to functioning as intended.
toggle quoted message
Show quoted text
When I try to build from source for MacOS, I get the following fatal error during the Hamlib build portion: /Users/charlesrogers/Build/hamlib-prefix/src/hamlib/src/parallel.h:30:12: fatal error: 'linux/parport.h' file not found # include <linux/parport.h> ^~~~~~~~~~~~~~~~~ 1 error generated. make[5]: *** [dummy.lo] Error 1 make[5]: *** Waiting for unfinished jobs.... make[4]: *** [all-recursive] Error 1 make[3]: *** [hamlib-prefix/src/hamlib-stamp/hamlib-build] Error 2 make[2]: *** [CMakeFiles/hamlib-install.dir/all] Error 2 make[1]: *** [CMakeFiles/package.dir/rule] Error 2 make: *** [package] Error 2 Any thoughts on how to resolve? On Jun 16, 2022, at 8:22 AM, Joe <joe@...> wrote: |
|
|
|
Gary Rogers
When I try to build from source for MacOS, I get a fatal error during the Hamlib build: linux/parport.h file not found…Any thoughts on how to resolve? the MacOS .dmg installer works just fine FYI.
toggle quoted message
Show quoted text
On Jun 16, 2022, at 8:22 AM, Joe <joe@...> wrote: |
|
|
|
Gary Rogers
I’ve installed on Windows 10, MacOS 12.4 and Raspberry Pi using the provided installers. All seem to functioning as intended.
When I try to build from source for MacOS, I get the following fatal error during the Hamlib build portion: /Users/charlesrogers/Build/hamlib-prefix/src/hamlib/src/parallel.h:30:12: fatal error: 'linux/parport.h' file not found # include <linux/parport.h> ^~~~~~~~~~~~~~~~~ 1 error generated. make[5]: *** [dummy.lo] Error 1 make[5]: *** Waiting for unfinished jobs.... make[4]: *** [all-recursive] Error 1 make[3]: *** [hamlib-prefix/src/hamlib-stamp/hamlib-build] Error 2 make[2]: *** [CMakeFiles/hamlib-install.dir/all] Error 2 make[1]: *** [CMakeFiles/package.dir/rule] Error 2 make: *** [package] Error 2 Any thoughts on how to resolve? |
|
|
|
Tim Dawson
FYI, successfully built on Linux (based on Slackware 14.2 - maintained by me via source builds) linked against existing Hamlib 4.5 git pull . . .
toggle quoted message
Show quoted text
Seems to be working OK so far, and no issues with the compile whatsoever. Still taking in the changes . . . but seems stable so far. - Tim On 6/16/22 10:22 AM, Joe wrote:
Dear WSJT-X and MAP65 Users, --
================================================================================ Tim Dawson (tadawson@...) Owner/Engineer TPC Services Bellnet: (972)-221-7385 Lewisville, Texas 75067 "Gaff Tape can't fix 'Stupid', but it can muffle the sound..." |
|
|
|
Mike Black
In Hamlib/src/parallel.h there is this:
toggle quoted message
Show quoted text
#ifdef HAVE_LINUX_PARPORT_H # include <linux/parport.h> #endif Then in config.h /* Define to 1 if you have the <linux/parport.h> header file. */ #define HAVE_LINUX_PARPORT_H 1 config.h is generated by "configure" -- do you use "configure" ?? Mike W9MDB On Thursday, June 16, 2022, 01:54:49 PM CDT, Gary Rogers <cgaryrogers190@...> wrote:
I’ve installed on Windows 10, MacOS 12.4 and Raspberry Pi using the provided installers. All seem to functioning as intended. When I try to build from source for MacOS, I get the following fatal error during the Hamlib build portion: /Users/charlesrogers/Build/hamlib-prefix/src/hamlib/src/parallel.h:30:12: fatal error: 'linux/parport.h' file not found # include <linux/parport.h> ^~~~~~~~~~~~~~~~~ 1 error generated. make[5]: *** [dummy.lo] Error 1 make[5]: *** Waiting for unfinished jobs.... make[4]: *** [all-recursive] Error 1 make[3]: *** [hamlib-prefix/src/hamlib-stamp/hamlib-build] Error 2 make[2]: *** [CMakeFiles/hamlib-install.dir/all] Error 2 make[1]: *** [CMakeFiles/package.dir/rule] Error 2 make: *** [package] Error 2 Any thoughts on how to resolve? |
|
|
|
Gary Rogers
I set the configuration with the cmake GUI. The config.h that worked has:
toggle quoted message
Show quoted text
/* Define to 1 if you have the <linux/parport.h> header file. */ /* #undef HAVE_LINUX_PARPORT_H */ In the file that didn’t work the second line was: #undef HAVE_LINUX_PARPORT_H */ There were several commands in this file with that problem. Of the three config.h files in my build directory, two started with # so I just overwrote the two bad files with the good one and it built. On Jun 16, 2022, at 3:13 PM, Michael Black via groups.io <mdblack98@...> wrote: |
|
|
|
Hi all this might be of help.Running here Windows 10 Dell.I tried several times and this error occurred.C:\WSJT\wsjtx\bin\qt5core.dll. Retry and ignore never worked.Check for file in WSJTX and it was there.DID A RESTART and all downloaded fine.Always worth a restart and retry.I am glad to see JT9 Is still accessible in the mode drop down.Need more users !!!Thanks Joe and the team for all your hard work.Kindest Regards as always.Paul G4YKQ.
toggle quoted message
Show quoted text
On Friday, 17 June 2022, 14:17:37 BST, Gary Rogers <cgaryrogers190@...> wrote:
I set the configuration with the cmake GUI. The config.h that worked has: /* Define to 1 if you have the <linux/parport.h> header file. */ /* #undef HAVE_LINUX_PARPORT_H */ In the file that didn’t work the second line was: #undef HAVE_LINUX_PARPORT_H */ There were several commands in this file with that problem. Of the three config.h files in my build directory, two started with # so I just overwrote the two bad files with the good one and it built. On Jun 16, 2022, at 3:13 PM, Michael Black via groups.io <mdblack98@...> wrote: |
|
|
|
JP Tucson, AZ
Hi Joe & wsjtx team,
Interesting... Could you folks please elaborate on the following... - Correct the handling of messages starting with "CQ xxxx ..." What was 'wrong' with it, how is supposed to work now? - Correct a flaw that could cause Windows to drop audio samples Thanks, I've been noticing this more recently! Haven't changed computer stuff, or radio setup, and couldn't figure out why I appeared to have no-decodes (clock is gps), etc. Hopefully, these issues will go away for good. - Correct the auto-sequencing logic in several specific circumstances What exactly did you correct; i.e. what symptoms? What specific circumstances... so that we can look and make sure on our end it is corrected. (I have long suspected & known that there were several 'bugs' in the auto sequence. I don't know if you have touched this: but I will make this suggestion. PLEASE ! Change the Fox/Hound watchdog! Meaning - please give us an actual countdown to when it is going to shut off our transmitter! That the FH watchdog is not even the same time as the std watchdog is confusing... further, the FH watchdog tends to shut off at the most inopportune times! Like during a QSO (the other station will reply, but your computer won't respond - - - in other words, the program needs to DETECT that the other station has called and automatically turn the TX BACK ON please! ) Next: Please make a section for SOTA/POTA/IOTA... heck, all the '....OTA/s... haha Also for the State QSO parties. Mean allow for the extended exchanges. I have thought about this, understand that each line is limited by bits, etc. My proposed solution is to create a 'special op mode' where you add a TX7 line where a person can STORE the SOTA/POTA number and the auto-sequencer in that mode will jump from Tx5 (..73), to TX 7 and list the stored #. Further, this scheme could also work for QSO parties by allowing them to add/store their State/County.... Ultimately, this could carry forth to a TX8, 9 and 10 for short emergency messages and other such long exchanges. Hopefully to the point where even the Winter Field Day folks get on board with FT8. Thank you |
|
|
|
Jim Brown
Thanks to the team for ongoing work. One comment. Those of us active on 6M have long found the need for a VHF Contest Mode more important than Fox/Hound. It's needed not only during contests, but also when grid expeditions are using it, conditions are highly variable, and stations are in and out in a few minutes. Losing a cycle can mean losing a QSO with a rare grid.
toggle quoted message
Show quoted text
73, Jim K9YC On 6/16/2022 8:22 AM, Joe wrote:
Dear WSJT-X and MAP65 Users, |
|
|
|
Carl - WC4H
Hello all.
Built it 2.6.0 on my Raspberry Pi 4B without any issues. I like the changes and hope to see a few more. So far everything that I use is working. 73. Carl - WC4h |
|
|
|
Pierre FK8IH <jb.gallauziaux@...>
Did a member test it with Quisk as v2.5.4 does not work with Quisk due to Hamlib issue?
73 - Pierre - FK8IH |
|
|
|
Hi JP,
- Correct the handling of messages starting with "CQ xxxx ..."Especially three-digit directional calls (CQ USA, CQ CAN, etc.) could sometimes not be answered correctly. Auto Seq stopped or went crazy. This was corrected. But we had to make sure that the frequency change function still works (e.g. CQ 912). - Correct the auto-sequencing logic in several specific circumstancesSearch the wsjt-devel forum. A couple of months ago, there was a couple of reports that Auto Seq stopped under certain circumstances. We have therefore made the Auto Seq Logig more robust. PLEASE ! Change the Fox/Hound watchdog!I ask for your understanding that we handle this point restrictively. It would not benefit any of us if we allowed rare Fox stations to be called for a very long time. Maybe have breakfast, lunch or dinner in between and hope that WSJT-X will fetch a "new one" for you. No, we must prevent such a thing! But I'll give you a hint: On my wsjt-x_improved versions, I have the Hound watchdog set a bit higher. Feel free to use them. Note: wsjt-x_improved is an enhanced version of WSJT-X. It has the same source code core, but offers some more features and improvements. Some of them have now put also into our official WSJT-X v2.6.0. Nevertheless, only wsjt-x_improved still has (and will have) all the extra features. But it is very easy to switch from one to the other. There are also two versions available with a slightly different GUI (“widescreen” and “AL”). Find this project on Sourceforge: https://sourceforge.net/projects/wsjt-x-improved/. Go to the Files tab so see the available versions. 73 de Uwe, DG2YCB |
|
|
|
Mike Black
I would like to add that I see LOTS of operators doing "blind calling" where it's quite obvious they are NOT decoding the DXpedition.
toggle quoted message
Show quoted text
Please do not do this....if you aren't decoding them then they can't answer you. It's quite possible they may hear you and you will cause the Fox to occupy one slot trying to answer you when you cannot hear them. The other problem associated with this is the # of slots being used by the Fox. If you see just one decode that means they are using 1 slot, two decodes from them is 2 slots and will the 6dB less signal. The more slots the less the signal strength.So, for example, if you decode them at -19dB in one slot but then they switch to 2 slots answering you won't hear them again until they go back to 1 slot. I think the Fox mode needs to look at the signal report they get from the Hound and based on current# of slots potentially reduce the # of slots next period to try and clear out the ones that need the extra signal strength. Whatever happened to the idea of a new Fox mode without the power loss? I realize that likely won't be backwards compatible though. Mike W9MDB On Saturday, June 18, 2022, 08:10:33 AM CDT, Uwe, DG2YCB <dg2ycb@...> wrote:
Hi JP, - Correct the handling of messages starting with "CQ xxxx ..."Especially three-digit directional calls (CQ USA, CQ CAN, etc.) could sometimes not be answered correctly. Auto Seq stopped or went crazy. This was corrected. But we had to make sure that the frequency change function still works (e.g. CQ 912). - Correct the auto-sequencing logic in several specific circumstancesSearch the wsjt-devel forum. A couple of months ago, there was a couple of reports that Auto Seq stopped under certain circumstances. We have therefore made the Auto Seq Logig more robust. PLEASE ! Change the Fox/Hound watchdog!I ask for your understanding that we handle this point restrictively. It would not benefit any of us if we allowed rare Fox stations to be called for a very long time. Maybe have breakfast, lunch or dinner in between and hope that WSJT-X will fetch a "new one" for you. No, we must prevent such a thing! But I'll give you a hint: On my wsjt-x_improved versions, I have the Hound watchdog set a bit higher. Feel free to use them. Note: wsjt-x_improved is an enhanced version of WSJT-X. It has the same source code core, but offers some more features and improvements. Some of them have now put also into our official WSJT-X v2.6.0. Nevertheless, only wsjt-x_improved still has (and will have) all the extra features. But it is very easy to switch from one to the other. There are also two versions available with a slightly different GUI (“widescreen” and “AL”). Find this project on Sourceforge: https://sourceforge.net/projects/wsjt-x-improved/. Go to the Files tab so see the available versions. 73 de Uwe, DG2YCB |
|
|
|
Hi Mike,
To run a second TX audio will double the audio power going to the transmitter. I would assume that most foxes will run their transmitter at optimum power out already, so doubling the audio in will cause the transmitter to overload, surely. Also aren’t we being recommended to keep the audio signal out of WSJT-X to the maximum already? 73 Phil GM3ZZA Sent from Mail for Windows From: Michael Black via groups.io Sent: 18 June 2022 16:25 To: main@wsjtx.groups.io Subject: Re: [WSJTX] Release Candidate WSJT-X 2.6.0-rc1 #general I would like to add that I see LOTS of operators doing "blind calling" where it's quite obvious they are NOT decoding the DXpedition. Please do not do this....if you aren't decoding them then they can't answer you. It's quite possible they may hear you and you will cause the Fox to occupy one slot trying to answer you when you cannot hear them. The other problem associated with this is the # of slots being used by the Fox. If you see just one decode that means they are using 1 slot, two decodes from them is 2 slots and will the 6dB less signal. The more slots the less the signal strength.So, for example, if you decode them at -19dB in one slot but then they switch to 2 slots answering you won't hear them again until they go back to 1 slot. I think the Fox mode needs to look at the signal report they get from the Hound and based on current# of slots potentially reduce the # of slots next period to try and clear out the ones that need the extra signal strength. Whatever happened to the idea of a new Fox mode without the power loss? I realize that likely won't be backwards compatible though. Mike W9MDB On Saturday, June 18, 2022, 08:10:33 AM CDT, Uwe, DG2YCB <dg2ycb@...> wrote: Hi JP, - Correct the handling of messages starting with "CQ xxxx ..."Especially three-digit directional calls (CQ USA, CQ CAN, etc.) could sometimes not be answered correctly. Auto Seq stopped or went crazy. This was corrected. But we had to make sure that the frequency change function still works (e.g. CQ 912). - Correct the auto-sequencing logic in several specific circumstancesSearch the wsjt-devel forum. A couple of months ago, there was a couple of reports that Auto Seq stopped under certain circumstances. We have therefore made the Auto Seq Logig more robust. PLEASE ! Change the Fox/Hound watchdog!I ask for your understanding that we handle this point restrictively. It would not benefit any of us if we allowed rare Fox stations to be called for a very long time. Maybe have breakfast, lunch or dinner in between and hope that WSJT-X will fetch a "new one" for you. No, we must prevent such a thing! But I'll give you a hint: On my wsjt-x_improved versions, I have the Hound watchdog set a bit higher. Feel free to use them. Note: wsjt-x_improved is an enhanced version of WSJT-X. It has the same source code core, but offers some more features and improvements. Some of them have now put also into our official WSJT-X v2.6.0. Nevertheless, only wsjt-x_improved still has (and will have) all the extra features. But it is very easy to switch from one to the other. There are also two versions available with a slightly different GUI (“widescreen” and “AL”). Find this project on Sourceforge: https://sourceforge.net/projects/wsjt-x-improved/. Go to the Files tab so see the available versions. 73 de Uwe, DG2YCB -- 73 Phil GM3ZZA |
|
|
|
Mike Black
The power in Fox mode is reduced to allow for this.
toggle quoted message
Show quoted text
So when the Fox increases slots the power of each signal is reduced. From the FT8 Dxpedition Guide (in the Help menu) Thus, for N Slots = 1, 2, 3, 4, and 5 the average power persignal will be down from P0 by about 0, 6, 9.5, 12, and 14 dB, respectively. The worst thing that can happen if Fox either calls CQ or responds in just one slot and then switches to 5 slots to respond to everybody on the next period. If you decoded Fox at anything less than around -8dB you quite likely won't hear them responding. Mike W9MDB On Saturday, June 18, 2022, 12:02:48 PM CDT, Philip Rose via groups.io <gm3zza@...> wrote:
Hi Mike, To run a second TX audio will double the audio power going to the transmitter. I would assume that most foxes will run their transmitter at optimum power out already, so doubling the audio in will cause the transmitter to overload, surely. Also aren’t we being recommended to keep the audio signal out of WSJT-X to the maximum already? 73 Phil GM3ZZA Sent from Mail for Windows From: Michael Black via groups.io Sent: 18 June 2022 16:25 To: main@wsjtx.groups.io Subject: Re: [WSJTX] Release Candidate WSJT-X 2.6.0-rc1 #general I would like to add that I see LOTS of operators doing "blind calling" where it's quite obvious they are NOT decoding the DXpedition. Please do not do this....if you aren't decoding them then they can't answer you. It's quite possible they may hear you and you will cause the Fox to occupy one slot trying to answer you when you cannot hear them. The other problem associated with this is the # of slots being used by the Fox. If you see just one decode that means they are using 1 slot, two decodes from them is 2 slots and will the 6dB less signal. The more slots the less the signal strength.So, for example, if you decode them at -19dB in one slot but then they switch to 2 slots answering you won't hear them again until they go back to 1 slot. I think the Fox mode needs to look at the signal report they get from the Hound and based on current# of slots potentially reduce the # of slots next period to try and clear out the ones that need the extra signal strength. Whatever happened to the idea of a new Fox mode without the power loss? I realize that likely won't be backwards compatible though. Mike W9MDB On Saturday, June 18, 2022, 08:10:33 AM CDT, Uwe, DG2YCB <dg2ycb@...> wrote: Hi JP, - Correct the handling of messages starting with "CQ xxxx ..."Especially three-digit directional calls (CQ USA, CQ CAN, etc.) could sometimes not be answered correctly. Auto Seq stopped or went crazy. This was corrected. But we had to make sure that the frequency change function still works (e.g. CQ 912). - Correct the auto-sequencing logic in several specific circumstancesSearch the wsjt-devel forum. A couple of months ago, there was a couple of reports that Auto Seq stopped under certain circumstances. We have therefore made the Auto Seq Logig more robust. PLEASE ! Change the Fox/Hound watchdog!I ask for your understanding that we handle this point restrictively. It would not benefit any of us if we allowed rare Fox stations to be called for a very long time. Maybe have breakfast, lunch or dinner in between and hope that WSJT-X will fetch a "new one" for you. No, we must prevent such a thing! But I'll give you a hint: On my wsjt-x_improved versions, I have the Hound watchdog set a bit higher. Feel free to use them. Note: wsjt-x_improved is an enhanced version of WSJT-X. It has the same source code core, but offers some more features and improvements. Some of them have now put also into our official WSJT-X v2.6.0. Nevertheless, only wsjt-x_improved still has (and will have) all the extra features. But it is very easy to switch from one to the other. There are also two versions available with a slightly different GUI (“widescreen” and “AL”). Find this project on Sourceforge: https://sourceforge.net/projects/wsjt-x-improved/. Go to the Files tab so see the available versions. 73 de Uwe, DG2YCB -- 73 Phil GM3ZZA |
|
|