Hi all, I am pleased to announce that Dennis, W1UE has agreed to take responsibility for hamlib beta testing.
So: *I hereby appoint him as our new official head of the Hamlib Beta Testing Group!* Concrete next steps of the new Hamlib Beta Testing Group should be the following: 1. Find beta testers for the most widely used, say 12 to 25 rigs and assign the responsibilities. 2. *The first concrete task of the Hamlib Beta Testing Group is to find as soon as possible (realistically within 2 to 3 weeks) _one_ hamlib version that runs on all these "key rigs" without problems.* As before, technical problems should be solved in close cooperation with Mike W9MDB, whose work and expertise I greatly appreciate. But this is something else than systematic testing and bug finding, and we need both. 3. Then I can use this version for the next update of WSJT-X or wsjt-x_improved, which I plan to do in the not too distant future (at least for wsjt-x_improved). 4. If a date for the next release is foreseeable, I would inform Dennis in advance, so that he and his Hamlib Beta Testing Group can select the best performing hamlib version. Keep in mind, that I always need the hamlib source code, as well as the binaries in 64-bit and 32-bit. So the group must make sure that these 3 files are available for the selected hamlib version. So, now it is enough from me on this topic. *From now on, Dennis is called to start with the work.* I wish from the bottom of my heart much success! 73 de Uwe, DG2YCB Am 13.05.2023 um 09:09 schrieb Uwe, DG2YCB via wsjt-devel:
Dear WSJT-X users, Please allow me to summarize again here on this email reflector a topic that is very important to me and to all of us. My original post was on https://groups.io/g/wsjtgroup, so maybe it's best if you join the discussion there. Despite great personal commitment of the hamlib developers it has unfortunately happened very often that immediately after a new WSJT-X release serious problems with one or another hamlib rig driver become apparent. If something like this happens over and over again, it shows that there is a *systematic* error somewhere. In my opinion this is due to the fact that *too few* users try the current development versions of hamlib, so that errors are detected *too late*. Keep in mind that hamlib drivers often change as they evolve. So I*would like to ask you all that enough OMs act as hamlib bata tester in the future.* For those who own one of the rigs below and work on Windows, just do the following every 2, 3 or 4 weeks: 1. Download the daily updated libhamlib-4.dll file available on https://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll. 2. Copy the file to the bin folder of your WSJT-X installation (i.e. usually c:\WSJT\wsjtx\bin). Rename the existing libhamlib-4.dll file beforehand so you can use it again later. 3. Start WSJT-X (or the respective variant), connect your rig via hamlib (i.e. *not* via OmniRig, HRD, DXLabSuite, etc.) and check if the CAT control runs properly. 4. If anything is not working properly, please contact Mike W9MDB via direct email, so he or his team can fix the bug in time. 5. If everything works fine, keep the new libhamlib-4.dll file, otherwise delete it and rename the previously used one. 6. In the future I would like to contact you before a new WSJT-X or wsjt-x_improved release to be able to choose a bug free hamlib version. In my opinion, at least the following rigs need to be tested regularly regarding hamlib: * Yaesu: FT-991, FT-101, FT-847 * Kenwood: which models? * Icom: IC-7300, IC-9100, IC-9700, IC-705 * Elecraft: KX3, what else? * FlexRadio: which models? * Anything else? *Now, the most important thing is that **one of you* *organizes it*. I can't do it myself because of time constraints, and Mike W9MDB is also overloaded with work. For example, what about the people who have stood out so intensively in the last few days with posts about something trivial? Wouldn't one of you like to take over and invest your energy there? *Seriously: Who?* *Y**ou are now requested! * I mean, what needs to be done is evident: 1. Create a list of commonly used rig models. 2. Find beta testers for each of these models and assign responsibilities. 3. Get an overview of the status quo and summarize the results clearly. Something like this can be done e.g. with a simple Excel file: It's sad enough that obviously, the hamlib development team can't do something so essential themselves. But *this definitely has to come now*, because we can't get the next frustration after every new WSJT-X release. Makes no sense! So, again: *Who of you will take this in hand and organize such a systematic beta testing? *I do not want to see one more "stupid" post as long as this problem is not solved, hi, hi!* *73 de Uwe, DG2YCB _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
