Re: [wsjt-devel] WSJT-X ver 2.6.1 Spurious Hound TX after band change

This continues to be a problem at my station and it has the potential to damage my equipment as the spurious TX starts before my SteppIR has changed to the new band. Shouldn't WSJT-X clear out all generated messages on band change or, at a minimum, flag that F/H QSO attempt has ended. 73,

Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process

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 Here's a youtube video showing Windows users howto --

Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process

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 Here's a youtube video showing Windows users howto --

Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process

Usually on click ok, the Config pane pops up on radio tab so you can reconfigure , so you don't see that then, ok ? It would be interesting to confirm a program interface like FLrig, Commander or HRD works, or rigctld/Hamlib interface , rather than actual radio choice. 73 vk4tux On

Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process

The Rig Control Error window is never displayed. But to answer your question... going into the settings and doing a 'Test CAT' does not restore the connection. -Scott AA5AM On Wed, Mar 20, 2024 at 7:11 PM Adrian wrote: > Re below ; If you click 'ok', and then are shown the wsjtx radio

Re: [wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process

Re below ; If you click 'ok', and then are shown the wsjtx radio settings tab, does 'Test CAT' restore the cat connection ? 73 vk4tux On 21/3/24 09:52, Scott Armstrong via wsjt-devel wrote: The Rig Control Error pop-up message is not raised. image.png When CAT is restored by turning on

[wsjt-devel] WSJT-X v 2.7.0-rc4/hamlib bug report; CAT failure casues hung process

Hi All, I have encountered a problem running 2.7.0-rc4 with Hamlib version [image: image.png] This impacts an Icom IC-756ProII and IC-746. The issue is not observed when running a IC-9700 The problem is also observed running 2.7.0-rc3 with the new Hamlib version The workaround is to roll back

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

It did show that many differrent linux as well as main Debian advanced flavours were affected. Some source code errors may only affect a limited number of branches, this showed it as widespread. 73 vk4tux On 13/3/24 00:43, Joe Taylor via wsjt-devel wrote: Hi all, On 3/11/2024 11:02 PM,

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

Thank you sir! Compiled and installed successfully. 73 -Jim NU0C On Tue, 12 Mar 2024 10:43:05 -0400 Joe Taylor via wsjt-devel wrote: > Multiple reports of the same issue are not really necessary, especially > after one of us in the development group has already responded. > > Anyway,

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

Hi all, On 3/11/2024 11:02 PM, Jim Shorney NU0C via wsjt-devel wrote: Confirmed same error, Kubuntu 22.04 up to date as of today. Error: Symbol ‘ncand‘ at (1) is USE associated from module ‘q65‘ and cannot occur in COMMON

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

Confirmed same error, Kubuntu 22.04 up to date as of today. Error: Symbol ‘ncand‘ at (1) is USE associated from module ‘q65‘ and cannot occur in COMMON /home/nu0c/src/build/build/wsjtx-prefix/src/wsjtx/qmap/libqmap/q65c.f90:93:3: 73 -Jim NU0C On Tue, 12 Mar 2024 00:59:57 + Stan Gammons

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

I'm seeing the same error on Kubuntu 22.04 uname -a Linux radio2 5.15.0-100-generic #110-Ubuntu SMP Wed Feb 7 13:27:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux [ 95%] Building Fortran object qmap/libqmap/CMakeFiles/qmap_impl.dir/moon2.f90.o [ 95%] Building Fortran object

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

Hi Josh, We're aware of the problem you report, but haven't yet got around to correcting it. It does not affect builds on any of the systems we're using for development. Compiler revisions are getting increasingly fussy about such things. You can do one of the following: 1. Wait for the

Re: [wsjt-devel] WSJT-X 2.7.0-rc4

Hi Josh, I got the same error on my Linux Mint 21,1 ( Linux abc 5.15.0-97-generic #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux ) but on my Raspberry 5 running Debian GNU/Linux 12 (bookworm) ( Linux cde 6.1.0-rpi8-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1

[wsjt-devel] WSJT-X 2.7.0-rc4

On Fedora Core 39, 64 bit, (uname -a Linux fedora 6.7.7-200.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Mar 1 16:53:59 UTC 2024 x86_64 GNU/Linux, gcc version 13.2.1 20231205 (Red Hat 13.2.1-6) (GCC)) I get the following errors building RC4: [ 94%] Building Fortran object

[wsjt-devel] WSJT-X ver 2.6.1 Spurious Hound TX after band change

Several times I have completed an FT8 F/H QSO on one band then changed to another band with Hound mode still active. "Enable TX" is not active and no intended transmissions have yet been made on the newly selected band. However, WSJT-X starts a new transmission to the fox that had been worked

Re: [wsjt-devel] WSJT-X ver 2.6.1 Failed to start OmniRig COM server

A lot of monitors have built in sound. I have seen crazy things where these monitor sound devices cause strange problems. I would disable all the sound devices in your monitors. Carl Moreschi N4PY 127 River Moss Way Hertford, NC 27944 www.n4py.com On 12/20/2023 8:24 AM, Christopher Wawak

Re: [wsjt-devel] WSJT-X ver 2.6.1 Failed to start OmniRig COM server

I have seen this exact scenario with the sound device causing Omnirig to fail to initialize. I can reliably reproduce this and repair it. I've posted about it before to no avail. I have also seen a scenario where the sound devices don't seem to change, but Omnirig fails to initialize even after a

Re: [wsjt-devel] WSJT-X ver 2.6.1 Failed to start OmniRig COM server

It turns out that this problem is very easy to reproduce. First some background on my configuration. The TS-590S has both a USB port and a traditional RS-232 COM port. The USB port connects to an internal USB hub which, in turn, connects to a USB UART for CAT and a PCM2903B USB Audio CODEC.

Re: [wsjt-devel] WSJT-X ver 2.6.1 Failed to start OmniRig COM server

I have it working again. I had disconnected all cables from the laptop to access the battery. When I put it all back together I had swapped the cables for the TS-590S USB port and a 10 port USB hub. I only realized this error when WSJT-X did not see my TS-590S USB audio CODEC. When I put the

[wsjt-devel] WSJT-X ver 2.6.1 Failed to start OmniRig COM server

I'm using WSJT-X ver 2.6.1 on a Win 8.1 laptop. I have been using OmniRig as my radio interface for many months and the only issue has been that first start after a new installation WSJT-X will fail to connect to OmniRig. It always connected ok for second and subsequent starts. Now I cannot

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

I agree. It's good enough as you have it. -- Joe On 12/8/2023 2:50 PM, Uwe, DG2YCB via wsjt-devel wrote: Hi all, Once again regarding my question about EU / AS Turkey: My commit only changes the displayed country name. Theoretically, the distinction between continents etc. should

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

Hi all, Once again regarding my question about EU / AS Turkey: My commit only changes the displayed country name. Theoretically, the distinction between continents etc. should therefore remain unaffected. I have just looked up how LotW and QRZ.com do it. There is also only one entry there,

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

This may all be correct, but at least to me, the decisive factor is what the DXCC rules are. And according to the DXCC list available to me, there is only one "Turkey", namely DXCC No. 390. TA-TC* Turkey EU/AS 39 20 390 73 de DG2YCB,

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

East Thrace or Eastern Thrace, also known as Turkish Thrace or European Turkey, is the part of Turkey that is geographically a part of Southeast Europe. It accounts for 3.03% of Turkey's land area and 15% of its population. The largest city is Istanbul, which straddles the Bosporus between

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

Hi Jim and all, I have analyzed our WSJT-X code regarding this aspect. Results: There seems to be nowhere specified which countries the WAE entities shall be assigned to when the "Include extra WAE entites" checkbox is *not* checked, neither in the CTY.DAT file nor in WSJT-X. This means, if

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

On Thu, Dec 7, 2023 at 2:46 AM Reino Talarmo wrote: > From: Jim Reisert AD1C via wsjt-devel [mailto: > wsjt-devel@lists.sourceforge.net] > > Sent: Thursday, December 7, 2023 3:51 AM > > > 3. 4U is listed as a prefix for Italy. > Regarding #3, this was done so that "new" (previously unknown) 4U >

Re: [wsjt-devel] WSJT-X parsing of the country file, specifically 4U1A (and others)

> From: Jim Reisert AD1C via wsjt-devel > [mailto:wsjt-devel@lists.sourceforge.net] > Sent: Thursday, December 7, 2023 3:51 AM > 3. 4U is listed as a prefix for Italy. Regarding #3, this was done so that "new" (previously unknown) 4U callsigns that are spotted on the DX cluster will propagate

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Geoff -- I was not trying to justify our code that posts only the first decode of duplicates in the same Rx sequence, just to tell you what the code does. I'm sure you can find many places where we have done something simple and straightforward, "just to get it going," even when something

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Absolutely, but this isn’t “The strongest signal over the last n decode periods”, its “The strongest signal _this_ decode period”, which might help reduce the reporting of spurs. And yeah, it’s a rathole. 73, Willie N1JBJ > On Dec 1, 2023, at 7:33 AM, Black Michael via wsjt-devel > wrote: >

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Yes, for WSPR/FST4W signal reports are essential. For FT8 etc. it probably doesn't matter much, but that was not the topic. 73 Stefan On 01.12.23 13:33, Black Michael via wsjt-devel wrote: And does anybody even look at that data anyways? ___

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Actually the strongest is not indicative at all of current conditions.  You can have momentary band conditions either way. What matters is what signal you heard them at.  e.g. "I initially received you at XXdB".  If a user wants to see band conditions for their callsign they can use

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Well, OK, Joe wrote the program, so he really is the ultimate authority. But the “decoded a spur and used that number for the SNR” seems to be the real issue here. In an ideal world, signals for a particular call should be sorted _after_ all the decodes are done, and the strongest (very

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead ofmain decode for strong signals

OG5O Lähetetty Windowsin Sähköpostiista Lähettäjä: Geoff Van der Wagen via wsjt-devel Lähetetty: perjantai 1. joulukuuta 2023 10.56 Vastaanottaja: wsjt-devel@lists.sourceforge.net Kopio: Geoff Van der Wagen Aihe: Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead ofmain decode

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

I would also prefer if the strongest signal would be uploaded. 73 Stefan ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Hi Joe, Puzzled by your response.  I agree with not uploading dupes, but I can't fathom why you wouldn't compare dupes and pick the strongest one.  In a situation like this, clearly the strongest signal is representative of the real conditions. I can't think of a use for uploading any other

Re: [wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Hi Geoff, On 11/30/2023 9:03 PM, Geoff Van der Wagen VK2WA via wsjt-devel wrote: I just had a funny one with a close station, S9+10dB, the transmission was +32 SNR but WSJT-X uploaded only the first decode at -19dB: Queried for all spots me + target, unique NOT ticked: Would have been better

[wsjt-devel] WSJT-X WSPR decoder uploads spur decode instead of main decode for strong signals

Hi all, I just had a funny one with a close station, S9+10dB, the transmission was +32 SNR but WSJT-X uploaded only the first decode at -19dB: Queried for all spots me + target, unique NOT ticked: Would have been better to upload the 32dB spot! Geoff VK2WA

Re: [wsjt-devel] WSJT-X 2.7.0 rc2 flagged as malware

You have met a “false Positive”. Most anti virus programs don’t recognize ham radio software. Aug AG5AT Sent from my iPad > On Oct 27, 2023, at 3:40 PM, F4FPR Benjamin via wsjt-devel > wrote: > > Dear wsjt-x devel list, > I’ve just tried to download the last update of WSJT-X version and it

Re: [wsjt-devel] WSJT-X 2.7.0 rc2 flagged as malware

enjamin > Subject: [wsjt-devel] WSJT-X 2.7.0 rc2 flagged as > malware > > Dear wsjt-x devel list, > I’ve just tried to download the last update of WSJT-X > version and it looks like that the last version is flagged as > the malware onto Sourceforge as such as into > VirusTot

[wsjt-devel] WSJT-X 2.7.0 rc2 flagged as malware

Dear wsjt-x devel list, I’ve just tried to download the last update of WSJT-X version and it looks like that the last version is flagged as the malware onto Sourceforge as such as into VirusTotal, what is going on ? Best regards & 73 Benjamin L / F4FPR / K5AW

Re: [wsjt-devel] WSJT-X 2.7.0-rc2 Switching caller in TX1 message

On 10/10/2023 8:25 PM, Clay Couger N5YJZ via wsjt-devel wrote: There is another bug in both 2.6.1 and 2.7.0 RC2 where the first call is always picked to respond to even if max dist is slected. This behavior is not a bug. "CQ Max Dist" is effective only when the Active Stations window is

Re: [wsjt-devel] WSJT-X 2.7.0-rc2 Switching caller in TX1 message

Hi Clay, Thanks for this issue report. With WSJT-X, CQ: Max Dist only works with certain contest messages, and when you have the Active Stations window open. I have changed this with my wsjt-x_improved program. There it works also for normal messages.

[wsjt-devel] WSJT-X 2.7.0-rc2 Switching caller in TX1 message

After transmitting RR73 or 73 to WB0OQV, but before the next transmission cycle I select 'I4RHP N5YJZ -11' message to send. WSJT-X 2.7.0 RS2 replaces my request with 'W8NGA N5YJZ -03' This issue is not seen in WSJT-X 2.6.1 There is another bug in both 2.6.1 and 2.7.0 RC2 where the first call is

Re: [wsjt-devel] [Wsjt-x-improved-community] [wsjtgroup] Solar Eclipse participation #general

I got some more info from the HamSCI group.  So if you could maintain one band for the duration of the  SEQP that would be best. >From W2NAF The SEQP is going to run for 10 hours from 1200-2200 UTC. See  https://hamsci.org/seqp-rules   What we actually analyze will depend on the quality of

[wsjt-devel] WSJT-X 2.7.0-rc2imp: TIME_ON = TIME_OFF when I am the called station #adif #IssueReport

Using WSJT-X 2.7.0-rc2imp I experience this as a new "feature": When a counterpart responds to my CQ, or he/she tailends a QSO I am finishing, both start time and end time are logged with TIME_OFF only, i.e a duration of 0 seconds. However, when I respond to stations calling CQ, or I tail-end a

Re: [wsjt-devel] WSJT-X as an AppImage

While this always seems to be a good idea on the surface, it really ties the hands of the software's flexibility and portability.  For example, I have run into Appimage issues with GQRX on various platforms.   Usually various library versions out of sync with the Appimage.   To the point where

[wsjt-devel] WSJT-X as an AppImage

Hi all, I recently wrote about building and running WSJT-X in a Docker container ( https://sm6vfz.wordpress.com/2023/07/10/building-and-running-wsjt-x-in-a-docker-container/ ). This works great for me and I no longer plan to run any of the built binaries. But another option I have become

Re: [wsjt-devel] WSJT-X published to WinGet

ur Subject line so it is more specific >> than "Re: Contents of wsjt-devel digest..." >> >> >> Today's Topics: >> >>1. WSJT-X published to WinGet (Chris Keller) >>2. Transverter Offset (tom) >> >> >> ------

Re: [wsjt-devel] WSJT-X published to WinGet

WSJT-X published to WinGet (Chris Keller) >2. Transverter Offset (tom) > > > -- > > Message: 1 > Date: Mon, 17 Jul 2023 11:58:16 -0600 > From: Chris Keller > To: wsjt-devel@lists.sourceforge.net > Subject: [wsjt-devel] WSJT-

[wsjt-devel] WSJT-X published to WinGet

Hello folks, I wanted to let you know that I've published a manifest for WSJT-X in Microsoft's official Windows Package Manager, a.k.a. WinGet. Users comfortable with the command line can now install WSJT-X with the command: winget install

Re: [wsjt-devel] WSJT-X 2.7.0-rc2

Hi Josh, So far, I’m not able to reproduce that behavior here. WSPR band hopping is working fine and Enable Tx stays enabled once it is set. Steve k9an > On Jul 8, 2023, at 5:49 AM, Josh Rovero via wsjt-devel > wrote: > > Builds and runs well on Fedora Core 38 64-bit. > > While WSPR band

[wsjt-devel] WSJT-X 2.7.0-rc2

Builds and runs well on Fedora Core 38 64-bit. While WSPR band hopping, the first band change cycle "unsets" Enable Tx, but after resetting Enable TX, subsequent band changes keep it set. -- P.J. "Josh" Rovero http://www.roveroresearch.org Ham Radio: KK1D

Re: [wsjt-devel] WSJT-X 2.7.0-rc2

Il 07/07/23 13:48, Björn Ekelund via wsjt-devel ha scritto: Hamlib is broken. Again. Rc2 crashes when I select IC-7610. IC-7300 and IC-7851 however seem to work. Björn SM7IUN RC2??? I've not seen any announcements for this RC. --- *73 de Marco, PY1ZRJ (former IK5BCU)*

Re: [wsjt-devel] WSJT-X 2.7.0-rc2

Il 07/07/23 13:48, Björn Ekelund via wsjt-devel ha scritto: Hamlib is broken. Again. Rc2 crashes when I select IC-7610. IC-7300 and IC-7851 however seem to work. Björn SM7IUN ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net

[wsjt-devel] WSJT-X 2.7.0-rc2

Hamlib is broken. Again. Rc2 crashes when I select IC-7610. IC-7300 and IC-7851 however seem to work. Björn SM7IUN ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] wsjt-x Hungarian localization

Hi Janos, Thank you for your Hungarian translation file. I have added it to our source code. I will send you a WSJT-X test version with your file by private email soon. 73 de DG2YCB, Uwe German Amateur Radio Station DG2YCB Dr. Uwe Risse eMail:

[wsjt-devel] WSJT-X 2.7.0-rc1 - Fedora Core 37 build error

Building from the rc1 source: /home/josh/Downloads/wsjtx-2.7.0/src/wsjtx-prefix/src/wsjtx/qmap/libqmap/q65c.f90:23:39: 23 |ndepth,ndiskdat,neme,newdat,nfa,nfb,nfcal,nfshift, & | 1 Error: Symbol ‘nfa’ at (1) is USE associated from

Re: [wsjt-devel] WSJT-X 2.7.0-rc1 Mac build changes

Yes, I did the same. I sent the diffs to Uwe. So far, there are a few quirks in the rc. Mostly with jt-bridge integration not working the same as before. Double clicking on a non-CQing station doesn't seem to populate the DX call but can put your station into "Enable TX" so instead of calling DX

[wsjt-devel] WSJT-X 2.7.0-rc1 Mac build changes

If the team would be willing to accept some diffs for the Mac build under MacOS SDK 13- The main issue on Mac is that sprintf is deprecated and treated as an error. The second issue are a few variables that are declared and incremented but not used anywhere. In qmap/astro.cpp there are

Re: [wsjt-devel] WSJT-X Not Responding on UDP Messages

Hi Laurie, I'm sorry, I didn't see your note. I see it now. I'll respond there. John On Mon, Mar 20, 2023 at 9:15 PM Laurie, VK3AMA via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > > > On 21/03/2023 11:53 am, John via wsjt-devel wrote: > > > > I'm running the latest production

Re: [wsjt-devel] WSJT-X Not Responding on UDP Messages

On 21/03/2023 11:53 am, John via wsjt-devel wrote: I'm running the latest production version of WSJT-X. I use WSJT-X with GridTracker and I am able to click on a station in the GridTracker roster and WSJT-X automatically initiates a QSO. This works perfectly. I have written code in Java

[wsjt-devel] WSJT-X Not Responding on UDP Messages

Hello, I'm running the latest production version of WSJT-X. I use WSJT-X with GridTracker and I am able to click on a station in the GridTracker roster and WSJT-X automatically initiates a QSO. This works perfectly. I have written code in Java that is attempting to send UDP messages to WSJT-X,

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

This appears to be resolved, https://sourceforge.net/p/wsjt/wsjtx/ci/wsjtx-2.6.1/tree/. Thanks to the dev team! Chris, K0SWE On Tue, Feb 14, 2023 at 10:59 AM Brian Morrison via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > On Tue, 14 Feb 2023 16:44:07 + > Barry Jackson via

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

The error was due to an instance of WSJT-X running while trying to update. Sri; Bill W2PKY On Tue, Feb 14, 2023 at 7:49 PM Bill Barrett wrote: > Stuck on this error, Am I doing something wrong? > > > Bill W2PKY > > On Tue, Feb 14, 2023 at 6:28 PM Joe Taylor via wsjt-devel < >

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

Stuck on this error, Am I doing something wrong? Bill W2PKY On Tue, Feb 14, 2023 at 6:28 PM Joe Taylor via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi Barry, > > There have been *many* announcements in a variety of places about our > switch from the Princeton University site to

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

Hi Barry, There have been *many* announcements in a variety of places about our switch from the Princeton University site to SourceForge. The tarfile you want is now linked at the bottom of this web page: https://wsjt.sourceforge.io/wsjtx.html The direct link to the tarfile is:

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

On Tue, 14 Feb 2023 16:44:07 + Barry Jackson via wsjt-devel wrote: > Further to my last and after a good search of the git log it seems > that since 2.5.4 nobody has tagged the releases. > > There are commits with references to making preparations for the > releases of 2.6.0 and 2.6.1 but

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

Further to my last and after a good search of the git log it seems that since 2.5.4 nobody has tagged the releases. There are commits with references to making preparations for the releases of 2.6.0 and 2.6.1 but neither were tagged at release! So this has broken my script which was checking

Re: [wsjt-devel] WSJT-X 2.6.X CAT bug

Do you perhaps have an offset for that band in the Frequencies tab? Mike W9MDB On Tuesday, February 14, 2023 at 06:03:40 AM CST, CT1EKD via wsjt-devel wrote: At version 2.4.x and version 2.6.x When we select 14.074mhz (FT8 mode) the radio goes to 28mhz, (28,128) also if you

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

Forwarded Message Subject: Re: [wsjt-devel] WSJT-X 2.6.1 GA Release Date: Tue, 14 Feb 2023 16:03:56 + (UTC) From: Black Michael Reply-To: Black Michael To: Barry Jackson What does git log show? I show this as the most recent commit commit

[wsjt-devel] WSJT-X 2.6.X CAT bug

At version 2.4.x and version 2.6.x When we select 14.074mhz (FT8 mode) the radio goes to 28mhz, (28,128) also if you add a new QRG at the frequencies list it goes to 28mhz band  I tested it with the ICOM radios 706mkg2 and Icom 746, all the other bands QSY to the correct Freq/band. It

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

On 13/02/2023 23:00, Brian Morrison via wsjt-devel wrote: On Mon, 13 Feb 2023 22:35:13 + Barry Jackson via wsjt-devel wrote: On 16/01/2023 14:22, Joe Taylor via wsjt-devel wrote: The WSJT Development Team is pleased to announce that today the Solar Flux Index is 234 and Sunspot Number is

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

On Mon, 13 Feb 2023 22:35:13 + Barry Jackson via wsjt-devel wrote: > On 16/01/2023 14:22, Joe Taylor via wsjt-devel wrote: > > The WSJT Development Team is pleased to announce that today the > > Solar Flux Index is 234 and Sunspot Number is 195. > > > > Oh, yes: and the WSJT-X 2.6.1 General

Re: [wsjt-devel] WSJT-X 2.6.1 GA Release

On 16/01/2023 14:22, Joe Taylor via wsjt-devel wrote: The WSJT Development Team is pleased to announce that today the Solar Flux Index is 234 and Sunspot Number is 195. Oh, yes: and the WSJT-X 2.6.1 General Availability (GA) release is now available for free download from SourceForge. Hi

Re: [wsjt-devel] WSJT-X

Hi Gary, On 2/5/2023 11:41 AM, Gary IoW G7RES via wsjt-devel wrote: Hello devs, great program, but may I suggest a small edit? Could you make it so that when the band is changed from the drop down in the program it will automatically switch to TX6? As an older software developer myself

[wsjt-devel] WSJT-X

Hello devs, great program, but may I suggest a small edit? Could you make it so that when the band is changed from the drop down in the program it will automatically switch to TX6? As an older software developer myself (.NET, ASP, JSON, Java, C# VB etc) I know this wouldn't be a difficult fix.

Re: [wsjt-devel] WSJT-X 2.6.0 Error in Network Address

I found this same pop-up message on 2.6.1 as well as 2.6.0 -- but never on previous versions. However, I found the issue. Namely, under Reporting -> UDP Server mine read "localhost" instead of an actual/numeric IP (like 127.0.0.1). This warning pop-up appears whether or not you actually

[wsjt-devel] WSJT-X v2.6.1 Apple M1 build available

Hi there, I’ve built and posted a native build of WSJT-X 2.6.1 for Apple M1 on my DropBox if anyone is interested: https://www.dropbox.com/s/88j2iu81148864f/wsjtx.261.zip?dl=0 Enjoy, alex K6LOT ___ wsjt-devel mailing list

[wsjt-devel] WSJT-X 2.6.1 GA Release

The WSJT Development Team is pleased to announce that today the Solar Flux Index is 234 and Sunspot Number is 195. Oh, yes: and the WSJT-X 2.6.1 General Availability (GA) release is now available for free download from SourceForge. Version 2.6.1 is a bug-fix release. It corrects a flaw in

[wsjt-devel] WSJT-X v2.6.0 Apple M1 build available

Hi there, I’ve built and posted a native build of WSJT-X 2.6.0 for Apple M1 on my DropBox if anyone is interested: https://www.dropbox.com/s/014g5jwi4tzamdz/wsjtx.260.zip?dl=0 Enjoy, alex K6LOT ___ wsjt-devel mailing list

[wsjt-devel] WSJT-X 2.6.0 Error in Network Address

A couple days ago I compiled WSJT-X 2.6.0 on Debian Linux 11 without issue, as per Bill's suggestions from a few years ago. I've made several FT8 QSO's, no issues noted. But I just stumbled on a weird bug: When I click File:Settings and then cancel without making any changes there's a

Re: [wsjt-devel] WSJT-X 2.6.0 Array Warnings

Jeff -- Program ft8sim is a stand-alone utility that is not part of WSJT-X. It is never called recursively, or from multiple threads. Have another cup of coffee and don't waste your time trying to resolve such a warning message. Or, if you prefer, change the code to make such a useless

Re: [wsjt-devel] WSJT-X v.2.6.0 GA Release Hound mode problem with Band dropdown

I, too, have seen the band dropdown menu not populate, however I did not use hound mode. I suspect some other reason may be in play. -- Dave Slotter, W3DJS On Sun, Jan 8, 2023 at 10:00 AM Ari Hyvonen via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > Hi,

[wsjt-devel] WSJT-X 2.6.0 Array Warnings

Greetings, I have built WSJT-X 2.6.0 on LMDE 5 and have run across the array warnings in: Building Fortran object CMakeFiles/ft8sim.dir/lib/ft8/ft8sim.f90.o Warning: Array ‘cwave’ at (1) is larger than limit set by ‘-fmax-stack-var-size=’, moved from stack to static storage. This makes the

[wsjt-devel] WSJT-X v.2.6.0 GA Release Hound mode problem with Band dropdown

Hi, If you start the wsjt-x, when hound mode was last used, the program does not correctly populate the Band dropdown list, it loads all the frequencies, it does not apply the mode Filter. Turning off Hound mode by 'FT8' button or by via settings fixes the frequency list. Windows 11, 64 Bit.

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Hi: Problem reported earlier re Win 10 64bit not installing was related with ANtiVirus software. Was able to install after disabling online protection. 73' Edfel KP4AJ On Sat, Jan 7, 2023 at 3:39 PM Marco Calistri via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > No problem Joe! > >

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

No problem Joe! I'm glad that now the topic has been clarified. Best regards, Marco, PY1ZRJ Il 07/01/23 11:52, Joe Taylor ha scritto: Sorry, Marco, I misunderstood your question.  We are not yet up-to-date with incorporating UI translations for the new release.  We will do so as time

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Sorry, Marco, I misunderstood your question. We are not yet up-to-date with incorporating UI translations for the new release. We will do so as time allows. -- Joe, K1JT On 1/6/2023 11:01 PM, Marco Calistri wrote: Il 06/01/23 19:58, Joe Taylor ha scritto: On 1/6/2023 5:14 PM,

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

t;WSJT software development" Kk: "Joe Taylor" Gönderilenler: 6 Ocak Cuma 2023 18:00:02 Konu: [wsjt-devel] WSJT-X 2.6.0 GA Release The WSJT Development Team is pleased to announce the WSJT-X 2.6.0 General Availability (GA) release. Program changes from version 2.5.4, releas

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

W10 64 bit installed OK here, apart from the W10 file catalogue issue I posted a few days ago. Alan G0TLK On 06/01/2023 18:39, Edfel Rivera via wsjt-devel wrote: Hi: Thanks for WSJTX Development. Have 2.6.0 GA crashed (Windows 10 64bit).  Report from Windows Event Viewer. Tried downloading

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Il 06/01/23 19:58, Joe Taylor ha scritto: On 1/6/2023 5:14 PM, Marco Calistri PY1ZRJ via wsjt-devel wrote: I1ve successfully compiled and started WSJT-X 2.6.0, but I notice now that the updated Italian translations have not been included into the current release! It should be obvious that

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

On 1/6/2023 5:14 PM, Marco Calistri PY1ZRJ via wsjt-devel wrote: I1ve successfully compiled and started WSJT-X 2.6.0, but I notice now that the updated Italian translations have not been included into the current release! It should be obvious that updated translations cannot be posted until

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Il 06/01/23 12:00, Joe Taylor via wsjt-devel ha scritto: The WSJT Development Team is pleased to announce the WSJT-X 2.6.0 General Availability (GA) release.  Program changes from version 2.5.4, released one year ago, are described in the Release Notes:

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Happy new year! I have successfully used the update_wsjtx_from_src BASH script found under https://github.com/dslotter/ham_radio_scripts to download WSJTX 2.6.0 source from SourceForge git and build on 8GB Raspberry Pi 4B (4 cores) running HamPi 3.2 in 13 minutes 50 seconds, and also successfully

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Hi Again: The crash happened when installing. At the license window. 73' Edfel KP4AJ On Fri, Jan 6, 2023 at 12:39 PM Edfel Rivera wrote: > Hi: > Thanks for WSJTX Development. Have 2.6.0 GA crashed (Windows 10 64bit). > Report from Windows Event Viewer. Tried downloading again, same result.

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Hi: Thanks for WSJTX Development. Have 2.6.0 GA crashed (Windows 10 64bit). Report from Windows Event Viewer. Tried downloading again, same result. If dev team need specifics send email to edfeljose at gmail.com Thanks 73' Edfel KP4AJ Log Name: Application Source:Application Error

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

OK I made the edit to the Hamlib version in cmakelist.txt to 4.5.3 and was able to build 2.6.0 for Mac. A couple of issues I have encountered during building the last several versions Build environment MacOS SDK, Xcode, dependencies in Macports and Cmake 3.25.1 While building hamlib, I get

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Thanks Uwe,  it works now. Just successfully compiled WSJT-X 2.6.0 on my Ubuntu 18.04 system. 73's de Kari, oh2gqc On 6.1.2023 19.22, Uwe, DG2YCB via wsjt-devel wrote: Try to download again. I think Sourceforge still had the old copy. But the one I downloaded 1 minute ago has the correct

Re: [wsjt-devel] WSJT-X 2.6.0 GA Release

Try to download again. I think Sourceforge still had the old copy. But the one I downloaded 1 minute ago has the correct entry. 73 de DG2YCB, Uwe Am 06.01.2023 um 18:07 schrieb Gary Rogers via wsjt-devel: Same issue for me downloaded from new WSJT-X site. On Jan 6, 2023, at 8:55 AM, Kari

  1   2   3   4   5   6   7   8   9   10   >