Re: [wsjt-devel] Hamlib fork repository

2023-11-08 Thread Christoph Berg via wsjt-devel 
Re: Matt Melling via wsjt-devel
> Thanks Mike l. My understanding is that at some point in the past there were 
> some patches needed for Hamlib. Is that no longer the case?

Debian has been building wsjtx with the stock upstream hamlib for ages
without issues.

Christoph DF7CB


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] CQ Hound mode

2023-11-05 Thread Christoph Berg via wsjt-devel 
Re: Reino Talarmo via wsjt-devel
> Just a minor point, I assume. If that is programmed into wsjt-x, then the 
> change will not be backwards compatible. The CQ part of the message is 
> actually a specific pretty long bit string (28 bits, ‘c28’). There could be 
> another bit string for the CQF, but none of the current versions would 
> present it as the CQF and the protocol machine would not work. If you feel a 
> need to study it further, see https://wsjt.sourceforge.io/FT4_FT8_QEX.pdf.

"No bits left" was my first thought as well, but people can put "FOX"
or "FH" in the CQ message even today: "CQ FH X0YZ AB12"

(If they are lucky, someone from Mayotte might even answer. :D)

Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Callsign Security

2023-10-12 Thread Christoph Berg via wsjt-devel 
Re: William Smith via wsjt-devel
> So now we would require cryptographic signing of QSOs?  I mean, I'd be ticked 
> if someone used one of my callsigns, but I wouldn't rally the entire amateur 
> community around a complex solution to the 'problem'.
> 
> It was hard enough for me as a computer professional to get TQSL set up, I 
> gotta say I'd never bother with CryptoSignedQSO, and if I didn't opt-in, 
> would my real QSOs be valid anywhere?

No need to reinvent the wheel, cryptographic signatures on QSOs is
exactly what happens already now when you upload to LoTW using tqsl.

Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] VFO readout on FT8 shutdown

2023-07-20 Thread Christoph Berg via wsjt-devel 
Am 20. Juli 2023 19:58:21 OESZ schrieb Marco Calistri via wsjt-devel 
:
>New Hamlib looks a bit better because with just one manual frequency band 
>correction, the sequences RX/TX keep stable for the rest of my FT8 operation.
>
>But the undesired behavior at the beginning (2 KHz shift after two RX/TX 
>sequences) is still present.
>
>Anyway, thanks for your support, Mike!
>
>
>Best,
>
>Marco, PY1ZRJ
>
>Il 20/07/23 12:34, Black Michael ha scritto:
>> It's on github
>> 
>> Mike W9MDB
>> 
>> 
>> 
>> 
>> On Thursday, July 20, 2023 at 10:33:40 AM CDT, Marco Calistri 
>>  wrote:
>> 
>> 
>> Do you have the link for the source hamlib?
>> 
>> I'm using Linux (mainly).
>> 
>> If this newer version is on GitHub,  I can try compiling from it.
>> 
>> Regards,
>> 
>> Marco, PY1ZRJ
>> 
>> Inviato da Outlook per Android 
>> 
>> *From:* Black Michael 
>> *Sent:* Thursday, July 20, 2023 12:28:54 PM
>> *To:* WSJT software development ; Marco 
>> Calistri 
>> *Subject:* Re: [wsjt-devel] VFO readout on FT8 shutdown
>> Please test the latest hamlib.
>> 
>> https://www.dropbox.com/s/snmkzu8eif89yqs/libhamlib-4.dll?dl=0
>> 
>> Some rigs cannot change frequency while transmitting.  Are you using VOX? 
>> SignaLink?
>> 
>> Some fixes were put in for these Yaeus rigs with this problem so hopefully 
>> this works now for the FT-100 too.
>> 
>> If not
>> Please place this file as described below
>> https://www.dropbox.com/s/t52ngcalsgnpm8m/wsjtx_log_config.ini?dl=0
>> 
>> C:\Users\[username]\AppData\Local\WSJT-X
>> The WSJT-X_Rigcontrol.log file will be in the same location
>> 
>> For Linux put it in
>> ~/.config
>> The WSJT-X_Rigcontrol.log file will be here:
>> ~/.local/share/WSJT-X
>> 
>> For MacOS put it in
>> /Users/[username]/Library/Preferences
>> Restart WSJT-X and duplicate the problem.
>> Shut down WSJT-X
>> 
>> Then send me the WSJT-X_RigControl.log file
>> Mike W9MDB
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Thursday, July 20, 2023 at 09:45:37 AM CDT, Marco Calistri 
>>  wrote:
>> 
>> 
>> I face a similar behavior which last for two or three transmissions 
>> sequences at the beginning of my FT8 session.
>> 
>> This phenomenal started since some months then if it is due Hamlib, it is 
>> something that is being dragged along the new releases.
>> 
>> In my case (using an Yaesu FT-100, mode rig split) starting for example the 
>> transmission on 28074 Mhz, on RX vfo, during the 15 seconds TX displays 
>> 28073, at RX switch the RX vfo shifts to 28073, then TX vfo during the 
>> second transmission, shifts to 28072 Mhz. At third sequence the behavior 
>> repeats, so RX is now at 28072 and TX shifts to 28071.
>> 
>> To correct it, I need to switch the frequency bands selector of WSJTX back 
>> to 28074.
>> 
>> Then the next sequences of RX/TX, after my manual intervention, keeps stably 
>> within the 1 Khz shift: 28074 RX and 28073 TX.
>> 
>> This is not a blocking issue to me but it is a bit annoying having to 
>> correct manually.
>> 
>> Regards,
>> 
>> Marco, PY1ZRJ
>> 
>> Inviato da Outlook per Android 
>> 
>> *From:* Black Michael via wsjt-devel 
>> *Sent:* Thursday, July 20, 2023 10:42:39 AM
>> *To:* wsjt-devel@lists.sourceforge.net 
>> *Cc:* Black Michael 
>> *Subject:* Re: [wsjt-devel] VFO readout on FT8 shutdown
>> That's what you get when you start smooshing buttons.
>> 
>> Here's what happened.
>> 
>> You swap VFOs -- WSJT-X doesn't care.
>> You exit -- WSJT-X saves the VFOB frequency as the "last frequency" used.
>> You start again -- if you have "Monitor returns to last used frequency" it  
>> will then load VFOB's frequency into VFOA.
>> Of course rig split will set VFOB based on VFOA's frequency.
>> 
>> So...
>> 
>> #1 Don't smoosh buttons unless you know what you are doing
>> #2 Turn off "Monitor returns"
>> 
>> Mike W9MDB
>> 
>> 
>> 
>> 
>> 
>> On Thursday, July 20, 2023 at 01:38:29 AM CDT, Glenn Williams via wsjt-devel 
>>  wrote:
>> 
>> 
>> Hello,
>> Comment: The following Human Induced confusion of VFO frequency occurs
>> on FT8 shutdown. Not necessarily a "bug" in WSJT-X. Just thought
>> I would send out the information.
>> 
>> Setup:  Windows 10, Kenwood TS590SG, USB cable driven, both WSJT-X 2.6.1
>> and 2.7.0-rc2. Bands: at least on HF bands.  Everything going well as
>> usual.  TX frequency high enough to separate VFO A and VFO B by 1.000
>> kHz (RIG SPLIT) in this example.
>> 
>> Action creating problem: Human manually toggles VFO A/B button. Now VFO
>> B is in the main position, VFO A on the side, no frequency changes have
>> occurred in either VFO.  Next steps:  EXIT out of WSJT-X. Restart
>> WSJT-X.  Now VFO A displays what VFO B was displaying. VFO B is still 1
>> kHz higher, which is now 2 kHz from the original.  Examples follow.
>> 
>> TX  = 2800 Hz
>>   PC          rig        rig
>> FT8 Display  VFO

Re: [wsjt-devel] "U.S.A" displayed as "U.S.A. of America"

2023-05-17 Thread Christoph Berg via wsjt-devel 
Re: Uwe, DG2YCB via wsjt-devel
> Some users complain that "U.S.A." is displayed as "U.S.A. of America".
> The reason for this is that the maintainers of the CTY.DAT file have
> suddenly changed the name from "United States" to "United States of
> America".

The weird part is that the change was only done in cty.dat, but
cty.csv is still using "United States".

> I will inform the maintainers of the cty.dat file about this annoying
> side effect and hope that they understand that it is better to use the
> name "United States" again.

TBH I would like all DXCC country lists to use the same spelling
variants - the ARRL list seems to prefer "United States of America",
looking at https://www.arrl.org/files/file/DXCC/2022_DXCC_Current.pdf.

Christoph


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] #Bug - Frequency Tracking Error - IC9700 (and IC-7300)

2023-01-16 Thread Christoph Berg via wsjt-devel 
Re: Fred Price via wsjt-devel
> Do you have CV-I Transcrive turned off in the menu? If not turn off and test 
> again.

Hi Fred,

I had bad problems with frequency readout with my IC-7610 through
rigctld when using the VFO knob - mostly in tlf, but wsjtx was also
affected (though less since there's less tuning).

The problems started when I upgraded hamlib from 4.3.1 to 4.5, and
went away when downgrading it again.

Disabling CI-V Transceive made the problems go away on 4.5.4. Thanks
for the tip!

73,
Christoph DF7CB
(one of the Debian maintainers for hamlib and wsjtx)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Typo patch

2022-08-23 Thread Christoph Berg via wsjt-devel 
Re: Christoph Berg via wsjt-devel
> Afaict the whole source tree has CRLF line terminators now. It would
> be nice if that could be reverted, it's making all the patches we have
> in the Debian package fail.

Attached is a patch that is suitable of inclusion (the others are
mostly build system adjustments specific to Debian).

Christoph
Description: patch spelling typo(s) in source

--- a/manpages/man1/wsjtx.1.txt
+++ b/manpages/man1/wsjtx.1.txt
@@ -75,7 +75,7 @@ applications settings dialog.
 
 ~/.local/share/WSJT-X[ - RIGNAME]/save/samples/::
 
-Sample .WAV files suppied with the application are found in this
+Sample .WAV files supplied with the application are found in this
 directory, they may be played back in the application and are referred
 to in the user guide tutorial sections.
 
--- a/manpages/man1/fst4sim.1.txt
+++ b/manpages/man1/fst4sim.1.txt
@@ -64,7 +64,7 @@ QRA64 sub-mode designator.
 
 *snr*::
 
- Add Guassian noise to simulate SNR in 2500 Hz bandwidth.
+ Add Gaussian noise to simulate SNR in 2500 Hz bandwidth.
 
 *W*::
 
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Release Candidate WSJT-X 2.6.0-rc3

2022-08-23 Thread Christoph Berg via wsjt-devel 
Re: Brian Morrison via wsjt-devel
> One small thing, the .tgz file contains the src directory and inside the
> wsjtx.tgz archive within that both of the .desktop files have some
>  terminators whereas in the same files in the git repo they
> have only . This trips up the Fedora spec files for building the
> package, the tool used is expecting the usual Unix  convention.

Afaict the whole source tree has CRLF line terminators now. It would
be nice if that could be reverted, it's making all the patches we have
in the Debian package fail.

Christoph DF7CB


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Are you building WSJT-X ?

2022-04-25 Thread Christoph Berg via wsjt-devel 
>  - Building on what platform?  Windows, Linux, macOS, or other?

We (me and fellow developers) are maintaining the Debian package of
wsjtx. Platforms are all Linux architectures supported by Debian:
https://buildd.debian.org/status/package.php?p=wsjtx

>  - What are your particular programming skills and interests?

I'm mostly the sysadmin-type of programmer, i.e. interested in getting
software to run stably and smoothly. (Debian is about doing that at
scale; my day job includes maintaining the PostgreSQL database
packages for Debian.)

>  - Are you making changes to the code?  If so, toward what end?

There are a few patches in the package, mostly to get the build system
do what we want:
https://salsa.debian.org/debian-hamradio-team/wsjtx/-/tree/master/debian/patches

We should probably submit a few of these for inclusion upstream.

>  - What portions of the code have you studied well enough to understand?

The build system :D

73,
Christoph DF7CB


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Log uses rcvd report from previous QSO

2021-08-12 Thread Christoph Berg via wsjt-devel 
After a QSO with EA8TH, I received a "cold" call from YO9IE which I
answered, but in the log window following that QSO, the -17 report
from the 1st QSO was reused:

201245   0  0.3 1202 ~  CQ EA8TH IL18  Canary Is.
...
201400  Tx  2607 ~  EA8TH DF7CB JO31
201415  -2  0.3 1202 ~  DF7CB EA8TH -17
201430  Tx  2607 ~  EA8TH DF7CB R-02
201445   0  0.3 1202 ~  DF7CB EA8TH RR73
201500  Tx  2607 ~  EA8TH DF7CB 73
201515   1  0.3 1201 ~  CQ EA8TH IL18  Canary Is.
201515  -4  0.8  864 ~  DF7CB YO9IE -04 <-- rx/tx both -4
201532  Tx  2607 ~  YO9IE DF7CB R-04
201545   8  0.8  864 ~  DF7CB YO9IE RR73<-- log dialog wants
to record Send -04 Rcvd -17
201600  Tx  2607 ~  YO9IE DF7CB 73

wsjtx 2.4.0 (haven't had time to upgrade yet)

Christoph DF7CB


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel