s different than with CW/Phone.
And it is not getting any easier of one logging program uses "time_on"
and other "time_off" when producing Cabrillo log.
--
Saku
OH1KH
Reino Talarmo via wsjt-devel kirjoitti 11.5.2023 klo 10.08:
Hi Saku and Alan,
I think that Alan already
r end of qso).
That is perhaps because in traditional CW or Phone contests the time is
always QSO start time as qsos take only few seconds.
FT8 world is a bit different, or is it anyway?
On what bases it has been chosen that WSJT-X uses qso end time as
C
n markers) on RF spectrum, I.E. does
not cause any "split".
Test with frequency counter. Your TX RFcarrier does not change when
selecting "none", "rig" or "fake it".
And now this subject has been done by me.
--
Saku
OH1KH
_
Sam W2JDB via wsjt-devel kirjoitti 28.4.2023 klo 15.03:
Saku, split on WSJT-X means that WSJT-X can automatically adjust your
frequency so that your transmit audio is always somewhere within the
middle of the audio bandpass.
73,
Sam W2JDB
Hi Sam!
Split, what Google translate says, means
omized. So that every CQ, or every try to answer other's CQ
would happen on different audio slot. If qso is established then TX
audlo would be locked to current audio slot for qso.
--
Saku
OH1KH
Jim Brown via wsjt-devel kirjoitti 28.4.2023 klo 0.53:
Likewise, if we call CQ (or another st
able from wsjt-x.
--
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
)
I do not know if same happens with DXGrid (not tested, because not
needed grid now). Assume it can happen too.
Expected status message with entered callsign to be *generated when
cursor leaves* DXCall column.
Not before. Thank you!
--
Saku
OH1KH
3Y0J at all).
--
Saku
OH1KH
Fred Carvalho via wsjt-devel kirjoitti 17.2.2023 klo 20.52:
John is right. I have never seen 3Y0J transmitting that high. He was
actually below (300-400Hz).
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
and then manually set PC clock.
Accuracy within one second. (enough).
But I am sure they had enough other things to think about.
On the other hand it was very easy to enable "Tx Even/1st" checkbox in
hound mode and recompile. After that no problem with wrong period.
(still no qso...)
d to add latest fixes as pull requests to official because
the code difference is too big. They appear only in my Alpha that I am
using here locally.
Cqrlog is for Linux, not for Windoze. But it is open source, so it is
free for W-programmers to try. I do not have any Windozes in house.
e_link
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
ust wonder did it catch frequency from that moment, not at time when
qso was held on 144.150
Note the difference frequencies, it is bigger than vfo +(-) audio
frequency can produce.
Andrew Neumeier via wsjt-devel kirjoitti 23.12.2022 klo 16.44:
Saku,
My experience has been that pskreporter di
reporting use stored quick setting frequency or true frequency that
is received via CAT ?
In case of former one: Is this bug or not?
Wsjtx-rc5
Fedora 35
IC706
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https
resizing.
Graphics is getting worse direction now!
--
Saku
OH1KH
Josh Rovero via wsjt-devel kirjoitti 30.11.2022 klo 0.15:
Builds and runs fine on Fedora Core 37 Linux, 64-bit.
And the ALL_WSPR.TXT incorrect transmit band issue looks like it's fixed.
--
P.J. "Josh&qu
uot;Propagation mode" , so why not "contest name" ?
(This will be my last reply of this subject for this list. PM to
continue discussion)
--
Saku
OH1KH
Larry Banks via wsjt-devel kirjoitti 14.10.2022 klo 16.23:
Hi Saku,
It is much easier to use a proper contest logging p
ther modes used in contest.
It would be lovely to define correct name already at WSJT-X logging
window and retain that.
Jim Brown via wsjt-devel kirjoitti 14.10.2022 klo 12.13:
Hi Saku,
There are logging programs that keep track of contests. I log contests
with N1MM+ (Freeware), export
ut "EU VHF" with FT8 qsos that have to be changed manually
afterwards.
Good place for contest name would be either:
Make "operator" column smaller and set "contest name" after that on
right side.
or
Below "propagation mode".
In both ca
urce from
https://git.code.sf.net/p/wsjt/wsjtx (same day as Hamlib below)
rigctl Hamlib 4.5~git fri sep 16 13:33:51 2022 + SHA=b1d132
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
.
3930 - 3960 should pass it ok through.
But as said my C is not very good, and I have not followed the whole
receiving chain yet.
I sent another bug report too. But it is not passed to devel list. At
least yet. It had small screen part capture included.
--
Saku
OH1KH
ndow.ccp lines 3930 -
3960 that makes TX3 start / stop fail?
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
as Hamlib below)
rigctl Hamlib 4.5~git fri sep 16 13:33:51 2022 + SHA=b1d132
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
el via wsjt-devel kirjoitti 18.9.2022 klo 15.18:
Can you post the relevant section of ALL.TXT with your QSO data
including all the other decodes around that too?
Mike W9MDB
On Sunday, September 18, 2022 at 07:11:56 AM CDT, Saku via wsjt-devel
wrote:
Hi!
Just worked FH/OK1M on 21.091 using
ay as Hamlib below)
rigctl Hamlib 4.5~git fri sep 16 13:33:51 2022 + SHA=b1d132
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
wsjt-devel kirjoitti 17.8.2022 klo 15.45:
That change also makes working with JTAlert and such programs MUCH
more friendly.
Don't throw the baby out with the bath waterif some actor wants to
create a bot just ignore them
Mike W9MDB
On Wednesday, August 17, 2022 at 01:03:44 AM
I see this as bad thing as it is now very easy to create an external
program that checks log and if callsign or locator is not in log start
calling and make automated qso that way.
I hope it will be returned back as it was before v2.6
--
Saku
OH1KH
Carey Fisher via wsjt-devel kirjoitt
You’re talking about defeating the timer, which is there for a reason.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
closes, as I have wsjt mated to N1mm+ for logging.
Dennis W1UE
On Wed, Jul 27, 2022 at 20:26 mpcorey--- via wsjt-devel
wrote:
So I posted to this list a few weeks ago about the problem with
2.6rc1 suddenly crashing, and to restart ending a JT9 process
through task manager.
--
Saku
ully up to date. (But has parts of rc2, at least
Release notes ;-).
Saku via wsjt-devel kirjoitti 23.7.2022 klo 15.59:
HI!
With Fedora 35:
git clone https://git.code.sf.net/p/wsjt/wsjtx
and after that making compile gives:
--
Saku
OH1KH
___
wsjt-dev
.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
--
Saku
OH1KH
___
wsjt-devel mailing
No...
It does not work. Pulled a few moments ago:
[saku@hamtpad ~]$ rigctld --version
rigctl Hamlib 4.5~git ma kesä 06 15:16:37 2022 + SHA=037384
Here you see what happens: "split - rig", "Allow frequency changes while
transmitting" checked. Icom 7300
https://dri
Yep! I have it.
I will make pull after weekend and see what that brings.
Black Michael via wsjt-devel kirjoitti 3.6.2022 klo 19.50:
You can get the absolute latest with git clone
git clone https://github.com/Hamlib/Hamlib.git
Mike W9MDB
--
Saku
OH1KH
file will be here:
~/.local/share/WSJT-X
Restart WSJT-X and duplicate the problem.
Shut down WSJT-X
Then send me the WSJT-X_RigControl.log file
Mike W9MDB
On Friday, June 3, 2022, 08:33:18 AM CDT, Saku via wsjt-devel
wrote:
Sorry but it does not work. It is even worse.
Interesting side
t has been fixed.
http://n0nb.users.sourceforge.net/
Mike W9MDB
On Friday, June 3, 2022, 05:03:29 AM CDT, Kari Sillanmäki via
wsjt-devel wrote:
Hi Saku, Michael, Mike et al
I can duplicate this behaviour reported by Saku on my 7300.
I'm using the rigctld-wsjtx bundled with WS
figured as ICOM 7300, or if I
have started rigctld with script before starting wsjtx and then using
Hamlib Net rigctld/localhost:4532 in settings/Radio.
Both ways same result. OS is Fedora 35 linux.
--
Saku
OH1KH
5p1kzx Michael via wsjt-devel kirjoitti 2.6.2022 klo 18.32:
Hi Everyone
I
liar with that here's a video on the file browser -
https://www.youtube.com/watch?v=AyVqCJrs9dk
Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Saku
OH1KH
_
d just continued to give R-report.
Halted TX and logged qso.
Fedora35, WSJT-X v2.5.4 d28164-dirty
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
XT on next start.
Then you can make more ALLOLDx files, monthly, or by yearly basis.
Depending how much you use WSJT-X.
--
Saku
OH1KH
Saku via wsjt-devel kirjoitti 19.2.2022 klo 10.01:
i I
Think you were using linux. Then open command console and:
cd ~/.local/share/WSJT-X
grep -ni HisCall ALL
fully I
could manually include the QSO also into my log.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Saku
OH1KH
___
wsjt-devel ma
the bottom
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
e.sf.net/p/wsjt/wsjtx
fetch = +refs/heads/*:refs/remotes/origin/*
not in use any more?
"git pull" gives: "Already up to date" there and it is over month since
last "git pull" was issued.
--
Saku
OH1KH
__
ctor.
This problem exists also with v2.5.2
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Saku kirjoitti 14.12.2021 klo 12.19:
Hamlib error: Invalid parameter
vfo_fixup: vfo=Sub, vfo_curr=currVFO
rig_set_vfo: rig does not have Sub
rig.c(2607):rig_set_vfo return(-1) while exchanging VFOs
It seems that again ic7300 is broken with latest hamlib source.
I think situation is not any
Today I upgraded Fedora 34 to version 35.
As expected the self compiled wsjtx did not start any more.
So I run my "doall.sh" script that:
- pulls Hamlib from
[remote "origin"]
url = https://github.com/Hamlib/Hamlib.git
- compiles and installs it
[saku@ha
opponent's TX frequency may also help
as often he/she transmits on frequency that looks free during his/her RX
period (that is the human mind...). Answering directly on his/her TX
frequency for CQ is not good idea as so many other stations may do the same.
--
Saku
OH1KH
Reino Talarmo via
That
would then help to connect free text to cq in case of several stations
sending them in same period.
--
Saku
OH1KH
John Korpal via wsjt-devel kirjoitti 18.11.2021 klo 20.12:
Grid Locator to State Mapping Enhancement
___
wsjt-devel mailing list
(default) + external monitor 1440x900 (right),
wsjtx at right (monitor)
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
er
than what the frequency should be. I’ve included a screenshot of
what happens when I first launch the program. I don’t know if
these are true bugs or if I just don’t have something configured
properly.
Thank you – K7CB
--
Saku
OH1KH
_
form design is clear, but with C and QT it
is mystery.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
There is something to do with man pages. For example:
[saku@hamtpad ~]$ rigctld --version
rigctl Hamlib 4.4~git ke loka 13 21:02:40 2021 + SHA=16a879
-
chk_vfo
Returns “CHKVFO 1\n” (single line only) if rigctld was
invoked
t
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
5BCU)*
**
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
n...@outlook.com
___
wsjt-devel mailing list
wsjt-devel@lists.sourcefor
Marco Calistri kirjoitti 29.9.2021 klo 16.49:
Hi dear Saku 😁
I was hopefully waiting a feedback from your side as being one member
of the CQRLOG developers team as well as a WSJT-X user.
However, sorry to say this, but your reply doesn't sounds pretty clear
to me... Despite this I wil
the first thing to do
the first period transmit after that is always without audio. So do not
use Tune button for tuning the new band first, just start transmit
immediately and let the first transmit period activate autotuner (just
wondering what the Tune button is for...)
--
Saku
OH1KH
Mar
so small that it did not cause any need to move to JTDX.
Rich - K1HTV via wsjt-devel kirjoitti 14.9.2021 klo 20.55:
*The JTDX decode capability on weak signals is significantly better *
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-dev
Good point Claude!
But I have at the moment only IC7300, WiFi Mouse and Hp laser printer
connected to PC via USB.
I have several symlinks, even for gps (because of some tests years ago)
But I do not have gpsd installed at the moment.
[saku@hamtpad ~]$ cat /etc/udev/rules.d/92-persistent
rted from script with IC7300 settings, WSJTX uses Net Hamlib rigctld
@ localhost:4532
Terve Saku,
Have you ever experienced RFI? Those symptoms do fit to that. Easiest quick
check is to reduce output power and see, if any change. Experts may find
another reason or reasons.
73, Reino OH3mA
is split/rig then if I start to work on 21Mc it works, but if I
then change to 14Mc RX will go to 14Mc but TX at vfoB stays on 21Mc.
So I have to use split/fake it to make it work properly.
--
Saku
OH1KH
Black Michael kirjoitti 31.8.2021 klo 15.37:
Are you compiling with the latest hamlib
There is no effect setting poll rate 1s, 2s or 5s. Always fails after a
while. I would say that shorter poll rate seems to raise problems faster.
I think I clean up everything and recompile all again.
--
Saku
OH1KH
Saku via wsjt-devel kirjoitti 30.8.2021 klo 17.27:
Black Michael via wsjt
poll queue then I
just wonder how it has worked this far from the beginning of FT4 mode.
I'll try next to minimize the poll rate and see what happens.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge
isted also with this version, too.
2021-08-27 14:33:15.401025][00:00:58.757069][RIGCTRL:trace] rig_get_ptt:
cache miss age=10134ms
There are similar with get_mode, get_vfo and get_split_vfo with
ages/widths with times from 23ms to 52460ms
--
Saku
Git guru and I can do just some basic things there.
Hamlib is easy to find from GItHub. It is just "hamlib" and can be found
as first hit of search.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://li
Bill Somerville via wsjt-devel kirjoitti 27.8.2021 klo 11.42:
Hi Saku,
have you tried using the rigctld-wsjtx that is bundled with WSJT-X, or
the one built with the Hamlib package you linked WSJT-X with?
73
Bill
G4WJS.
HI Bill!
No, not tested with rigctld-wsjtx.
But when extracted
s 19200 -C auto_power_on=0
rigctld started from script with IC7300 settings, WSJTX uses Net Hamlib
rigctld @ localhost:4532
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
;s de Kari, oh2gqc / oh6bz
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Cqrlog compiled with QT5 widgets can do this, so I assume it is not
LXDE/QT5 problem to restore window size and position.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt
ersion) of wsjtx source.
How ever my trick worked and now I have latest hamlib and properly
working wsjtx 2.3.1
--
Saku
OH1KH
Bill Somerville via wsjt-devel kirjoitti 3.8.2021 klo 16.32:
Mike,
OK, then uninstall the system package, so long as no other package
depends on it. You are
2.5-3.4kHz fails
more often.
--
Saku
OH1KH
Black Michael via wsjt-devel kirjoitti 3.8.2021 klo 16.10:
WSJT-X most certainly does poll the rig. Though only every 5 seconds
since you set it that way.
Of course it won't poll if it gets an error.
Perhaps you need to reset your frequencies in
oblem. Frequency display does not follow rig if vfo is turned
while cqrlog, accessing the same rigctld daemon, notices frequency
changes. ;-(
-
grep says:
[RIGCTRL][2021-08-03 12:04:34.582825][00:00:00.186587][info] Hamlib
version: Hamlib 4.3~git Sun Jul 25 23:51:03 2021 + SHA=67b7
thing works ok.
*So rc4 is unusable with "split"="rig". If I set "Fake it" all works
after I have cleared the start phase "OOB" like with 2.4.0*
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
ecise.
--
Saku
OH1KH
Derek Turner via wsjt-devel kirjoitti 17.7.2021 klo 9.33:
And why do JAs en mass ignore locators which are fundamental in FT8
exchanges for the rest of us ?
73 de G4SWY Del +++
___
wsjt-devel mailing list
wsjt-
es go happy to near 4000Hz.
JTDX filter, old rigs or too narrow rig filters in use are the reasons
that may drive stations to same small area of used audio band.
--
Saku
OH1KH
Jim Brown kirjoitti 8.7.2021 klo 22.23:
On 7/8/2021 12:02 PM, Jon Anhold wrote:
There are absolutely guys running narrow fi
over there.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
ations use 1st/even period for calling and AS stations
use 2nd/odd period. It makes working a little bit easier than in HF bands.
--
Saku
OH1KH
Tim Goeppinger via wsjt-devel kirjoitti 8.7.2021 klo 6.07:
There are so many times on FT8 or FT4 that the station you are in QSO
with is buried in QRM b
ges to be legacy format.
So it should work with any version that understands and replies in short
form as it "has always been"
--
Saku
OH1KH
Black Michael via wsjt-devel kirjoitti 8.6.2021 klo 15.53:
All those programs will use the system libhamlib.so shared library.
If you do
ldd
Bill Somerville kirjoitti 7.6.2021 klo 20.36:
Hi Saku,
the WSJT-X v2.5.0 RC1 RPM package for Fedora targets Fedora 34, which
is why you are seeing dependency conflicts while attempting to install
on Fedora 33.
Try starting rigctld with a --vfo argument.
73
Bill
G4WJS.
Hi Bill!
Thanks
from WSJT home page
does not install at all having several conflicts with liboost, libc and
libstdc++
Just to FYI, I'm keeping 2.3.1 as it works.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.s
split used) user trusts
it will do it's job.
/That is why I suggest it also should reset delta TX (xit) and maybe
also Rit that may stay on from previous mode.//
/
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
http
before Tx period
using udp #15.
How ever keeping "Enable TX" active would still be operators job, so no
automation for qsos by enabling Tx DF.
That's why I can not see why setting Tx DF does not exist in udp #15.
--
Saku
OH1KH
___
wsj
Did you read my previous message (attacked) or can't I express myself ok?
I said it happens ( also) in linux, and quick halt tx/enable tx releases
audio . Read again , please.
--
Saku
OH1KH
20. maaliskuuta 2021 11.40.17 GMT+02:00 Alessandro Gorobey via wsjt-devel
kirjoitti:
>
In addition:
A) This happens with FT8. It does not happen with FT4
B) If "tune" is not used, I.E. just band changed and double clicked CQ
caller TX works with audio. Using "Tune" button causes bug.
Saku kirjoitti 20.3.2021 klo 8.44:
Hey !
Now when testing more carefully
arting from 1)
Double click on "band activity" or "rx frequency" window does not
matter. Same effect in both.
Cleaning windows and DX call with F4 does not matter.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
tart TX if no output at first go.
There can be something related to recent band change. During these years
I have not been able to reliably reproduce it.
So it exist, but so seldom that you get used to it.
wsjtx 2.3.0
Ic-7300
Fedora 32
--
Saku
OH1KH
Kevin McQuiggin kirjoitti 17.3.2021 klo
install version 2.3.0 into F32?
2.3.0 has depencies to BOOST 1.73 and in F32
there is BOOST 1.69.
So anyone solved this?
Jarmo, oh1mrr
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists
_
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
under Linux and directly
modify the file "wsjtx_log.adi" file.
Thank you. Regards
--
Dave Slotter, W3DJS <https://www.qrz.com/db/W3DJS>
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sour
ing of "-1" (?)
Once again a feature that one just must get used to.
--
Saku
OH1KH
Bill Somerville kirjoitti 21.11.2020 klo 13.33:
Hi Saku,
the passband value -1 id a special one meaning no change. I suspect
what is happening is that he rig is recalling the last used bandwidth
sjtx actually
sends using wsjtx rig model #2, Hamlib Net Rigctld and separately
started rigctld. Tcpdump from traffic between them shows:
[saku@hamtpad ~]$ sudo tcpdump -X port 4532 -i lo | grep PKTUSB
dropped privs to tcpdump
tcpdump: verbose output suppressed, use -v or -vv for full protocol decod
early to half
height of 2.3.0rc2's minimum height.
What is desirable when companion programs are the ones to look at decode
results.
Bill Somerville kirjoitti 16.11.2020 klo 13.42:
Hi Saku,
I am looking into a fix for the height issue with the WSJT-X main
window, it is due to some norma
it gets corrupted when "controls" open and need more
space. There should be window height variable for "controls" visible and
another for "controls" disabled.
Waterfall is a thing that can be lived with because of
can affect to WSJT-X saved settings?
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
hat, but that was not in
question now.
All other programs that I used were working as usual.
Just FYI. I do not think this can be common problem, but it is good to
know. Just in case...
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.s
HI!
I would start by catching the Status (#1) message.
Then, if you just want to change mode, create message by copying
everything else from Status, except mode, and return it back as message #15
If that does not work get better advisor. :-)
--
Saku
OH1KH
Lloyd via wsjt-devel kirjoitti
ents and I
do not know what would happen if there are more than one wsjt-x client
in same multicast group.
Bill Somerville kirjoitti 30.7.2020 klo 15.59:
Hi Saku,
RR, it is not difficult to implement. The main problem has been code
written with ancient programming languages and scripting too
in multicast group, and I can not see any
reason why they would not work when several listeners are online.
Still have to work some qsos to be sure all is ok. (this was too easy to
modify :-O )
Bill Somerville kirjoitti 30.7.2020 klo 14.59:
Hi Saku,
that's no problem, use message_aggre
ing the FT-8 setup into the rest of my
shack so it can drive my network aware antenna switches etc.
73, and thanks!
--al
WB1BQE
___
wsjt-devel mailing list
wsjt-devel@
Now I have tried more.
Fred you said it has been there always. Can you please tell me how I can
make this box appear with FT8 mode?
This clip is taken when MSK144 mode is on. When switch to FT8 it disappears.
So I wonder how you make it?
Saku kirjoitti 1.7.2020 klo 13.47:
Really!
I
o try more. First test (before mailing) it did not do so when
FT8 mode was used.
n...@hotmail.com kirjoitti 1.7.2020 klo 12.05:
FT8 already does this just as MSK144. It always has.
Fred
N2XK
--
Saku
OH1KH
___
wsjt-devel mailing list
that they should peek also 10kHz up?
Auto QSY could be better than self spotting at DXCluster.
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Joe Taylor kirjoitti 11.6.2020 klo 22.18:
Hi Saku,
OG55W is not a standard callsign. Not a good idea to use that with
FT4/FT8/MSK144 in a contest.
-- Joe, K1JT
Thanks Joe !
After night sleep I remember seeing this before. Was it even in user
manual at the time special callsigns
, then press Generate std
messages and then enable TX.
Can be reproduced by generating CQ TEST OG55W with ft8sim.
Os: Fedora 31 Linux
--
Saku
OH1KH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists
1 - 100 of 227 matches
Mail list logo
