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
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,
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
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
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
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
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 bui
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 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
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
Re: Bill Somerville
> Hi Chris,
>
> your request is not being ignored, we are a bit busy at present. I was
> hoping the existing Linux package maintainers might have some comments as
> well.
Hi,
I share Bill's concerns about Flatpak being something that doesn't
really fit into the normal world
Re: Richard Shaw
> Not exactly what I meant. We (Fedora Linux) can only assume certain
> processor facilities can be "assumed" when targeting a specific platform
> (x86_64, i686, s390x, ppc, aarch64, etc.). Which is separate from my desire
> to take advantage of them.
>
> It's a bit more
Re: Andrew Neumeier via wsjt-devel
> Closing the program and restarting it is met with the warning about a 'stale
> lock file'. Computer has to be restarted to be able to restart WSJTx.
Rebooting shouldn't be necessary, but sometimes there's a stale "jt9"
process left in the background that has
Re: David Schmocker
> Tx slider seems unnecessary because every radio (correct me if wrong) allows
> a Tx or drive level reduction on the radio itself).
By that argument, you could as well put an attenuator into your
antenna line to have the RX level reduced to what you wanted.
Christoph
Re: Joe Taylor
> Most people on this list know I'm a scientist, so I'll use a scientific
> analogy. Copying or adapting our code (which is still in development) and
> publishing the result is analogous to entering our laboratory when its door
> was left open, copying the laboratory notebooks
Re: Adrian Fewster
> I run debian here, and just added sid to my apt source list to pickup
> v2.3.0 on debian, on apt update and upgrade.
Fwiw, wsjtx is also in buster-backports, in case people do not want to
upgrade their stable systems to bullseye/unstable yet.
wsjtx |
Re: jeff millar
> Hello all,
>
> What percentage of bits are needed to produce a valid decode? I'm asking
> because sometimes I may start a transmit session some seconds late.
This is a nice article including graphs about decoding probabilities
vs timing:
Hi,
it would be nice if the FST4 cycle length left a trace in the
wsjtx.log and wsjtx_log.adi files.
Christoph DF7CB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: jeff millar
> WSJTX starts, starts receiving, responds to Tune every thing is normal.
> But on Enable Tx and start of a Tx cycle, it keys, but no transmit tones.
> Tune works but Tx does not. the messages look right.
There have been reports that using Tune and Transmit in the same cycle
leads
Re: Black Michael via wsjt-devel
> I'd like to hook up with you and debug this.
> Do you do Skype? We can use "Quick Assist" if you are on Windows 10.
I apparently haven't mentioned Debian often enough ;)
Jitsi works quite well, but unfortunately I have a Bridge sked in a
few minutes. Some time
Re: Patrick 9A5CW
> have the same problem.
> If i start the radio in USB mode, manually i change with a button on the
> radio IC706mk2 mode to CW, then i go back into WSJT-X i
> chose a freq from the dropdown menu list, radio is trying to switch to that
> selected frequency but can't do it.
I
Re: Bill Somerville
> > ... and the "Hamlib error: Invalid parameter while exchanging VFOs" popup.
>
> Hi Christoph,
>
> the rigctld trace doesn't show any errors. Please put the attached file into
> the local configuration directory ~/.config and run the test again then quit
> WSJT-X. It will
Re: Black Michael via wsjt-devel
> So if you do an "ldd" on the executables they all point to the same libhamlib
> ?
$ ldd /usr/bin/wsjtx | grep hamlib
libhamlib.so.4 => /lib/x86_64-linux-gnu/libhamlib.so.4
(0x7f556f2a)
$ ldd /usr/bin/rigctl* | grep hamlib
libhamlib.so.4
Re: Bill Somerville
> Is your WSJT-X built against the same hamlib-dev package that fldigi is? I
> would guess that it is so something else must be broken.
Everything is linked against the 4.0 release tarball, yes.
Christoph
___
wsjt-devel mailing
Re: Black Michael via wsjt-devel
> Does the Debian WSJT-X use hamlib as a shared library?
> Sounds like that may be the problem.
Mike, please stop suggesting that moving away from shared linking
would solve any problems. That will not happen on Debian.
> There is a binary incompatibility that
Hi,
since I switched the Debian wsjtx package to hamlib 4.0 with my IC706,
Hamlib rigctld operation doesn't work anymore:
Hamlib error: Invalid parameter while exchanging VFOs
FLdigi works fine through rigctld, both with the 3.3 and 4.0 hamlib.
(Including adjusting the rig number in rigctld.)
Re: Bill Somerville
> It would be far better to remove any declarations like structs
> from the public API so that nothing depends on offsets of fields being
> constant between releases. Your suggestion would make many minor releases
> breaking API changes when that's not really necessary. And yes
Re: Bill Somerville
> that's a really bad solution to this issue given the frequency of Hamlib
> releases.
Well the obvious fix here is to actually create hamlib releases :)
Christoph
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Re: Black Michael
> I don't believe that solves the problem.
> If one refers to data structures in code you can't rely on shared libraries.
> You need to stick to the API.
If you are referring to source-level API compatibility that is true (I
was referring to ABI changes), but if you are
Re: Black Michael via wsjt-devel
> Seems we had a problem on Linux WSJT-X builds as they are using the hamlib
> shared library instead of static build.I've already recommended they switch
> to static.
> The problem crept up where one version of hamlib worked but another was
> getting the wrong
Re: Adrian
> I repacked a deb file to run on latest Debian Buster here, working well re
> v2.2.2.
>
> libgfortran4 only defined in control, and installed with package
>
> http://vk4tux.duckdns.org/1x1/wsjtx_2.2.2_amd64.deb
Fwiw, you can install wsjtx 2.2.2 from Debian buster-backports:
Re: Al Kozakiewicz
> 2. Clear "hold tx freq" whenever QSY via combo box. You will never want
> to be at the same offset when changing bands. If you want to hold a freq you
> should be made to select a clear one before camping out.
I'd rather wish to have "Hold TX" checked by default in
Re: DG2YCB, Uwe
> How can I find information on such a configuration file for the new internal
> system and data logging function? Is there any documentation yet? Which
> parameters can be set and how? Is it also possible to deactivate the logging
> (to further reduce the number disk accesses)?
Re: Jim Shorney
> Hit F2 and you skip the first two. It Advanced was the last tab you were in
> you also skip the third. Quick and easy.
Why is there no "F2" label on the File -> Settings... menu entry?
Some of the other F keys have labels, e.g. in the View menu.
Christoph
Re: Richard Shaw
> Is there not a debian/ubuntu equivalent to "mock" on RPM based systems?
pbuilder or sbuild.
Christoph
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: Daniel Uppström
> Hi,
> Maybe this has already been answered here, if so I am sorry. However;
> It seems some Linux distros has dropped libgfortran3. Trying to install WSJT
> 2.2.2 from the deb-package is therefore not possible.
Which distribution release are you on?
Christoph
Re: Jon Anhold
> 154445 -21 0.1 2385 ~ KM8V 5F0KOH R BB71 ? a2
The decoder is running 3 times as much per period.
Christoph
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: Claude Frantz
> Now, the question which occurs for me is "is it better to switch to Debian
> stable ?". The sublevels (stable, testing, etc.) are not the same in Debian
> and Fedora. For me, it's difficult to understand which are the matching
> sublevels.
>
> At the present state, I think
Am 24. Oktober 2020 16:05:19 MESZ schrieb Claude Frantz
:
>Hello all,
>
>which problems do I have to expect when trying to compile the source
>code from the git repo using Debian STABLE ? Which are the solutions
>available ?
>
>Best wishes,
>Claude (DJ0OT)
>
>
Paul, Bill,
thanks for the insights.
Maybe all it takes to fix this perceived mess is to have wsjtx monitor
all modes in parallel, even if the period lengths are different. CPU
time is likely much cheaper than the electricity bill for the
transceiver anyway. :)
73,
Christoph DF7CB
PS: Debian
Hi,
I have some concerns that the naming of the new FST protocols will
confuse everyone, because the names are just too close together. In
the wsjtx mode menu the list is now:
FST4
FST4W
FT4
FT8
which all look similar. Also, when saying "I have worked A0BC in FST4"
people will likely not always
Re: Pino Zollo
> Hi,
>
> I wonder if the program can decode at the same time all the different
> tone spacing ...
>
> Having to chose between 7 T/R periods every one with different tone
> spacing, which is the probability of having chosen the right one ?
I had similar thoughts. IMHO the reason
Re: Bill Somerville
> id
Fwiw, if `id` (groups in effect) and `id uwe` (groups as per
/etc/group) report different group memberships, you need to re-login.
Christoph
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Re: DG2YCB, Uwe
> [0.790264] 00:06: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a
> [6.712122] :02:00.0: ttyS4 at I/O 0xe0c0 (irq = 16, base_baud =
> [6.712346] :02:00.0: ttyS5 at I/O 0xe0c8 (irq = 16, base_baud =
>
> What am I doing wrong? Do I have to configure
Am 5. September 2020 07:39:53 MESZ schrieb Al Reeves :
>For some reason when I now launch WSJT-X I get the following error
>message:
>
>
>
>Any Ideas?
>
>Al
>W1JHU
Open the adif log in a text editor and change to .___
wsjt-devel mailing list
Re: Richard Shaw
> I figured it out... x10.
>
> I had the inputs and outputs reversed. Apparently there was enough
> bleedover to even make a contact which is why I thought it was hooked up
> correctly.
>
> Sorry for the noise.
Literally :)
Thanks for cheering me up,
Christoph
Re: Black Michael
> If you have a bug to report please do. The problem the flag would address is
> people saying "X doesn't work" when it's known that the rig can't do X.
All the patches in the Debian package are already in the hamlib git
except for the typo fix that I just submitted as PR.
Re: Black Michael via wsjt-devel
> What I was referring to though was a flag that is "known" to be true. Perhaps
> for both for split and data/pkt. WSJT-X would default to enabled unless the
> the flag is present in either TRUE or FALSE state. And perhaps the tooltip
> on Split and Data/pkt
Re: Black Michael via wsjt-devel
> 3009 Icom IC-706 20200614.0
> Untested RIG_MODEL_IC706
My 706 (no mk something) works flawlessly.
(I used to get "rig communication problem" popups, but these are rare
now and I think the problem is in the USB
Re: Bill Somerville
> On 07/06/2020 20:48, Andy Durbin wrote:
> > So back to my original question - Why does WSJT-X freeze Wide Graph
> > during TX?
>
> I suspect the answer is because for the vast majority of users it would be a
> hindrance, because Rx periods would scroll off screen twice as
Re: Rich Zwirko - K1HTV
> I just downloaded and installed RC3. With the RxFrequency column in focus,
> the Erase button works, but with the Band Activity side in focus the Erase
> button has no effect. However, using a right click and then selecting
> 'Erase' does work OK on both sides.
Re: jeff millar
> Removing all the wsjtx packages improved the situation. dpkg now installs
> wsjtx incompletely and leaves a broken package. Ubuntu 20.04 has
> libgfortran5 by default, 4 is available and 3 is not. For libreadline, 8
> is the default and 5 is available.
>
> Is there a way to
Re: Bill Somerville
> that looks like you have some other package installed in /usr/local called
> wsjtx-data2.1.2+repack-2build1, I have no idea what that is, but suggest you
> uninstall that package before trying to install our amd64 package.
The Debian package is split into wsjtx, wsjtx-data,
Re: Chris Sullivan
> I've seen this a couple of times before on RC1, Windows 10-64.
>
> I responded to a CQ from VE3VN (Hold TX set, also auto seq & call 1st). Just
> after my transmission began I halted tx because I noticed he had called CQ
> WC, which I guess isn't me. Then I saw, in red in
Re: Bill Somerville
> this change is deliberate. Prior versions favour strong stations calling at
> the lowest audio offset, we think it is better to randomize the frequency
> order to give all stations more equal weighting. This is particularly in
> respect of the "Call 1st" feature. There is
Re: Joe Taylor
> WSJT-X 2.2.0 will be a significant program upgrade offering many new
> features.
The new "show most decodes earlier" feature is awesome, thanks!
Probably related: I noticed that the list of decodes is now pretty
much unsorted. Would it be possible to at least sort each batch by
Re: Black Michael via wsjt-devel 2020-03-26
<1563809814.1581787.1585232631...@mail.yahoo.com>
> 4.0 breaks the ABIergo the major version bump.
That's why we have sonames, yes.
All I'm asking is that you try to get a hamlib release out before
wsjtx uses it if there's any breaking changes. Of
Thanks Bill.
Re: Bill Somerville 2020-03-26
<4dfad234-90d0-94bd-e39b-581cc84cd...@classdesign.com>
> This is tricky area, even if there were many more Hamlib releases it is
> still hard to get the latest rig support.
If this discussion is only about rig support then I guess we can worry
a lot
Re: Black Michael 2020-03-26 <2012473983.1578425.1585230719...@mail.yahoo.com>
> What makes you think WSJT-X needs to use the system libraries? There's no
> such requirement that I've ever heard of.WSJT-X is written (as are all
> applications) to use specific capabilities in hamlib.
> I'll bet
Re: Black Michael via wsjt-devel 2020-03-26
<423480794.1565067.1585229983...@mail.yahoo.com>
> The hamlib release you need is in the WSJT-X tarball.Read the directions on
> building it.Since you maintain the Fedora distribution you should be building
> it correctly and not use your system
Re: Bill Somerville 2020-03-26
<6a2deab9-b75a-a5db-2ce8-3e443e39a...@classdesign.com>
> All I can say is that I think that type
> of restriction is wise with dynamically linked libraries, but with static
> linking there are no real issues since the forked content is fully
> encapsulated within
Re: Black Michael via wsjt-devel 2020-02-26
<176445943.542281.1582729953...@mail.yahoo.com>
> On a side note...I fully believe that we need to disable anybody transmitting
> to Fox unless they've decoded them at least once (and decoded them recently
> too...maybe a 5-minute timeout or less).
Re: Rich Zwirko - K1HTV 2020-02-20
> If you use the "Blank lines between decode period" option,disregard the
> data below the separating dashed line which does NOT show the band on the
> right side of the line.
The point is, if wsjtx knows there was a band change with possibly
mixed decodes,
Re: Dwayne Sinclair 2020-01-14 <1a7fafe0-f3f3-45ff-8ec9-a0f3e1f60...@gmail.com>
> I would like to propose adding RTTY to WSJT-X for two reasons 1. As a means
> to reframe the DXCC discussion away from FT8 itself to “it’s just a UI for
> managing QSO’s”, and 2. I believe WSJT-X would be a great
Re: W5MMW Matt Manjos 2020-01-07
> - User chooses to QSY to 160m band via the drop-down in WSJT. Their 40m
> antenna will not tune to 160m, so they need their rig to be ready to send
> RF on 1.840 MHz in order for their antenna switcher/tuner to operate
I'm seeing the same problem with IC706,
Re: Graham c 2020-01-03
> WSPR of course uploads reception reports to wsprnet.org. WSJT-X uploads FT8
> reports to pskreporter.info but only for those CQ messages -
> as far as I know something like VE3GHM FN25 (without the CQ) would not get
> uploaded by WSJT-X to pskreporter.info.
Calling
The attached patch has been sitting in the Debian package for quite a
while, please consider applying it.
Christoph
Description: Fix spelling error
Author: Enrico Rossi
Last-Update: 2018-08-22
--- a/Configuration.ui
+++ b/Configuration.ui
@@ -951,7 +951,7 @@
wsjtx contains *two* code copies of qcustomplot.cpp:
$ ls -l plots/
-rw-rw-r-- 1 cbe cbe2111 Dez 1 21:18 main.cpp
-rw-rw-r-- 1 cbe cbe1272 Dez 1 21:18 mainwindow.cpp
-rw-rw-r-- 1 cbe cbe 393 Dez 1 21:18 mainwindow.h
-rw-rw-r-- 1 cbe cbe 909 Dez 1 21:18 mainwindow.ui
Re: Roy Gould 2019-07-27
> It does not seem to me that there is any reason that FT4 and FT8 cannot
> operate together in the same channel. If this is so, then why have separate
> channels for them?
FT8 is quite good at decoding even overlapping signals in parallel.
However, from my experience,
Is there a reason the "Hold Tx" checkbox isn't checked by default?
This list seems to be discussing this over an over, and instead of
hoping that people might click it, why isn't it just on?
Christoph
___
wsjt-devel mailing list
Re: SP5MI GG 2019-07-24
> My name is Greg. I tried to install WSJT-X from Debian package 32-bit:
> wsjtx_2.1.0_i386.deb. I have Debian 10 with LXDE 32 bit.
Use the package from Debian unstable:
https://packages.debian.org/sid/wsjtx
Christoph
___
Re: Bill Somerville 2019-07-18
<6f30c9d0-3471-8e36-0100-93bc2117a...@classdesign.com>
> this is due to a rather awkward implementation. There is currently a project
> underway to refactor the WSJT-X source code base, the first target is to
> improve the implementation details that cause this
Re: Greg Beam 2019-07-15
> I am not certain, but, I thought I read that Debian was including these
> newer versions of WSJT-X at the distribution level. If so, that would be
> really good news and negate the need for PPA's.
We aren't updating packages to newer versions in stable releases (with
a
Re: Bill Somerville 2019-06-04
<1accb949-2c9d-cecb-faa5-1cda815bd...@classdesign.com>
> thanks for the update. Note that we have released WSJT-X v2.1.0 RC7 which
> includes that patch so it is now obsolete.
Yeah, I noticed just after applying the patch, but figured reporting
back success would
Re: Bill Somerville 2019-06-03
> > It's segfaulting for me (amd64 Debian buster, Debian packaging):
>
> can you try the attached patch please?
The patch fixes the problem, thanks!
Christoph
___
wsjt-devel mailing list
Re: To WSJT software development 2019-06-02 <20190602205424.ga3...@msg.df7cb.de>
> Re: Joe Taylor 2019-06-02 <93dbfb69-b762-58fa-5e4e-0094419b1...@princeton.edu>
> > - OK/Cancel buttons on Log QSO window maintain fixed positions
>
> Thanks :)
>
> > Release candidate WSJT-X 2.1.0-rc6 will be
Re: Joe Taylor 2019-06-02 <93dbfb69-b762-58fa-5e4e-0094419b1...@princeton.edu>
> - OK/Cancel buttons on Log QSO window maintain fixed positions
Thanks :)
> Release candidate WSJT-X 2.1.0-rc6 will be available for beta-testing
It's segfaulting for me (amd64 Debian buster, Debian packaging):
$
Re: Adam Bartlett 2019-05-10
> One of the challenges of automatic updating is package managers and such on
> the Linux side are often generations behind (not a big deal, but if a user
> installs Ubuntu, types "apt install wsjtx" and they still have 1.x in their
> repo it's going to confuse them)
Re: Bill Somerville 2019-04-30
> I don't recall if the Icom IC-706 Mk0 can accept CAT commands while
> transmitting, I doubt it as it has pretty primitive CAT control. Make sure
> that you have "Settings->General->Allow Tx frequency changes while
> transmitting" unchecked. You can also try
Re: To wsjt-devel@lists.sourceforge.net 2019-04-30
<20190430070450.gb28...@msg.df7cb.de>
> > your assumption is correct, unexplained rig control errors are a sign of
> > serious CAT issues. Which rig, what error inc. details, what settings?
>
> IC706 (not MK-something), via rigctld.
>
> With
Re: Wolfgang 2019-04-30 <1196675657.20190430172...@gmail.com>
> since the cycle time is now only 6 seconds and the vertical max.
> speed can only be set to 'N Avg 1' (same as in FT8) the vertical
> width of the waterfall cycles are relative small. Could be twice
> in width - if possible.
Yeah it
Re: Bill Somerville 2019-04-30
<57907294-a4b4-57dc-ce2a-4f13c54df...@classdesign.com>
> It is not too complex to push the release branch to the Source Forge git
> repo if the development team agree. If you make a credible case for doing so
> I am sure we can comply.
It would be nice to have it
Re: Bill Somerville 2019-04-29
<6c16f722-5577-e692-e1a3-78a3c38b9...@classdesign.com>
> In summary WSJT-X v2.1.0 RC5 will have the following FT4 suggested
> frequencies (the Iter1 column):
>
> Band Iter0 Iter1 Notes
> -
> 80 3595 3575 (plus
Re: K2DBK-WSJT 2019-04-30 <0ed301d4fefd$1af82cc0$50e88640$@k2dbk.com>
> I saw a mention of this on the announcement thread but figured I'd start a
> new one: Using FT4, after a few CQs the rig will change to another FT-4
> frequency.
From a parallel thread:
"I found out that changing the mode to
Re: Bill Somerville 2019-04-29
<0e3a78ef-8583-b7ec-0eeb-b7f11fab5...@classdesign.com>
> On 29/04/2019 22:16, Christoph Berg wrote:
> > Maybe my rig control is much more instable than the occasional "Rig
> > control error" popups suggest
>
> Hi Chris
Re: Bill Somerville 2019-04-29
> > https://doc.qt.io/archives/qq/qq19-buttons.html
> >
> > Christoph
>
> Hi Christoph,
>
> not disagreeing but there are reasons for this that I can't reveal. Let's
> just say it is to deter LIDs. Sorry.
If the idea is to make people think before logging, I'd
Re: Bill Somerville 2019-04-29
> > Manual log qso, has Ok and Cancel buttons at least 4 different positions
> > within different qsos
> This is intentional. Is it causing you insurmountable problems?
Very annoying. There are styleguides that suggest putting the OK and
cancel buttons in certain
Re: James Shaver 2019-04-29
> I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode
> getting changed back to FT8 and my frequency is jumping to 14.074. This
> appears to be random (though it still shows the “FT4” configuration as being
> selected). Selecting FT4 as
Re: James Shaver 2019-04-05
> I’ve experienced this since 1.7 but it’s not consistently reproducible.
>
> > What really surprised me, is how at the end of the 15s cycle, I would
> > then receive this same message, as if it were another station calling
> > me! It was highlighted in red, it had
Re: To Black Michael 2019-04-05 <20190405140829.gn7...@msg.df7cb.de>
> Re: Black Michael via wsjt-devel 2019-04-05
> <2079659523.17205032.1554472856...@mail.yahoo.com>
> I didn't mean grabbing it from the rig via full-duplex. It could just
> be faked because wsjtx knows what signal it is
Re: Black Michael via wsjt-devel 2019-04-05
<2079659523.17205032.1554472856...@mail.yahoo.com>
> Short answer...no...
> Long answernot many rigs can receive and transmit at the same time. You
> have to watch the waterfall before you start transmitting to avoid being on
> top of somebody.
Re: Darren Freeman 2019-04-05
> IIRC this fake transmission appeared in the waterfall window, also. It
> seems like the audio output was being looped back into the decoder.
Fwiw, would it be possible to actually keep the waterfall running
while transmitting (without decoding)? It would nicely
Re: Bill Somerville 2019-04-05
<6eed6403-230e-f83e-69f5-94ebb5037...@classdesign.com>
> WSJT-X makes no claim to handle multiple concurrent QSOs correctly. You must
> edit the "Log QSO" entry fields to the values you think are correct, or at
> least review them before clicking OK to log the QSO.
Re: Frank Kirschner 2019-04-01
> Almost every time I'm trying to work a DX station, I call and call with no
> success, until I hit Halt TX. As soon as I do that, the DX station comes
> back to me.
>
> Could you write some software that would get the DX station to respond
> sooner? This would
Re: Bill Somerville 2019-03-28
> this issue is already fixed in the current official release of WSJT-X
> v2.0.1.
Oh, sorry for not cross-checking that. Thanks for the quick reply!
Christoph DF7CB
___
wsjt-devel mailing list
Hi,
I'm one of the Debian maintainers for wsjtx. The gcc maintainers have
reported that wsjtx is failing with the upcoming gcc 9:
[ 58%] Building Fortran object CMakeFiles/wsjt_fort.dir/lib/ft8/chkcrc13a.f90.o
/usr/bin/gfortran -DBIGSYM=1 -DCMAKE_BUILD -DQT5 -DQT_NO_DEBUG_OUTPUT
96 matches
Mail list logo
