Hi!
Funny I had to read Alan's reply from mail archive (web), I did not get
that mail at all.
if you calling CQ (TX1) and someone(s) answer to it qso starts from
point you start first TX2 transmission (to any of answering stations).
It is very clear. There is no exchange happened yet, and
HI!
Just worked a short OH-FT8 contest that uses "NA VHF" settings with WSJT-X.
I had my logging program using UDP remote connect to WSJT-X and once
contest was over I created Cabrillo logs. From WSJT-X and from my
logging program. Just to compare.
Then I started to wonderwhy logs
Oh, what a sandstorm!
I write once more as I got an idea that perhaps clears out, or not, way
of thinking for those who are not RF experts.
We all know, (do we?), what SDR rig is. Look for webSDR receives
(Googling...) it gives a view if SDR is not familiar.
OK!
WSJT-X software turns your
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
How do you know that?
Perhaps on low bands but higher HF bands you can not hear others near
by. Besides most of qsos are running "split" Station A on different
audio frequency slot as opponent B.
I would rather see improvement where CQ (TX6) and answer to CQ (TX1)
would be randomized. So
Laurie, VK3AMA via wsjt-devel kirjoitti 21.2.2023 klo 13.06:
This is not a bug. WSJT-X has always behaved this way, emitting a UDP
status message with each character typed.
I would not like to see this long-standing behavior changed.
de Laurie VK3AMA
(JTAlert author)
Like always; I guessed
Hi!
Found annoying property of UDP Status (#1) message.
If you enter new callsign to DXCall column the new status message is
sent after every letter you type. This makes receiving program very hard
to decide when there is complete callsign available. (needs timeout
routine because of this)
That may also depend on RX tuning.
If you put VFO a bit off from reported frequency the audio will appear
in different place.
I do often tune a bit off to get Fox little bit higher in audio for
better copy.
And for the three times R without RR73 and move to higher frequency
(below 1kHz):
Jim Shorney via wsjt-devel kirjoitti 16.2.2023 klo 15.05:
So you do the best you can with what little you have. Who knows, maybe their
GPS was in one of the boxs left on the boat. It seems unfair to criticize when
none of us was there.
No critics, done what was possible.
How ever it seems to
Marco Calistri via wsjt-devel kirjoitti 15.2.2023 klo 22.17:
Yeah!
HI!
Cqrlog wsjtx-remote can support only one remote wsjtx at time. Using
multicast UDP I think you can have several wsjtxs sending to Cqrlog, but
you have already found the problem that arises.
The remote code is very
Hi!
Very strange qso in 10m with J8/AJ4YX. Or was it really AJ4YX after all?
-Fedora 37
-Wsjtx 2.6.1 (compiled from source)
-rigctl Hamlib 4.6~git tammi 19 05:32:18Z 2023 SHA=268f44 (compiled from
source)
-ICOM IC7300
The callsign of AJ4YX varied as <...>, , and
in ALL.TXT and screen.
I just wonder...
We did qso on 144.150 (qsy by vfo knob). After qso I moved back to
144.174 that is saved to wsjtx/frequencies.
Because wsjtx sends heard calls to pskreporter as a "block" time to time
I think the sending happened after our qso when I was again back on 144.174
I just wonder
Hi!
I worked a local qso on 144.150 using FT8 (that was displayed on WSJT-X
frequency reading)
Afterwards I looked at pskreporter where both our calls were reported on
144.175
I.E. frequency that was stored WSJT-X band quick settings (144.174) +
audio frequency.
Now question is:
Does
Builds and runs also in Fedora36 /LXDE but now main window is even wider
than before.
And there is no way to make it narrower after startup as before, except
when HOUND mode is selected.
Then it can be set as narrow as rc4, but when returning from HOUND it
gets wider again and does not allow
HI Larry!
I am a Linux user.
I worked last 15 years with Windoze servers and clients versions up to
W7. When retired I do not have any need to touch them any more. Linux
has Wine, but I do not have any need to run Windoze programs via it.
Cqrlog has it all. And what it does not have I can
HI Jim!
No Windozes in house.
I use Cqrlog for logging and at the moment WSJT-X is sending a contest
name in UDP logging frame to Cqrlog that can not be defined.
That's why I always need to fix contest names of FT8 qsos afterwards
with Cqrlog's group edit to be similar with all other modes
Hi!
Sorry if this feature exist. I did not find a mention about it from user
guide.
There are now several contests that use WSJT-X contest modes. It would
be nice to have user defined contest name to logging window.
That way name logged (also via UDP message) could be set by contest. And
(second try to send this message. 1st one did not show up on list)
Hi!
Found also another issue:
If wsjt-x is closed with Hound-mode running the *next start will
activate hound-mode again* (tested that by setting TX under 1000Hz and
started TX. It jumped random ove 1000Hz) *but the mainwidow
OH1MRR suggested that because FH/OK1M does use pure wsjt-x it causes the
problem.
Could be he is using other software, but as far as I can understand
mainwindow.ccp lines 3930 - 3960 do not care is the Fox true fox or mshv.
If that is the reason, then the problem lays somewhere else in code.
Black Michael kirjoitti 18.9.2022 klo 16.59:
I think it's because your callsign is being hashed and the logic is
not allowing for a hashed callsign.
This section removes hash marks from the foxCall -- but not my_callsign.
I had plain call OH1KH (or OH1KJ) there. When my call is hashed it is
Hi!
Found also another issue:
If wsjt-x is closed with Hound-mode running the *next start will
activate hound-mode again* (tested that by setting TX under 1000Hz and
started TX. It jumped random ove 1000Hz) *but the mainwidow view is mixed*.
As you can see red "hound" stays there, but
a 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 hound
Hi!
Just worked FH/OK1M on 21.091 using hound mode.
After called a while I got answer, but wsjtx just continued calling.
I had manually click on the received report line and after that wsjtx
moved to proper TX frequency and started to give R-report.
When I got RR73 wsjtx just continued to
-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 CDT, Saku
Hi!
BTW, now version 2.6.0rc2 has property that if "Hold TX frequency" is
checked sending an UDP frame created from decode of station keeping QSO
can start TX. Previously it just "preloaded" Std. messages and moved RX
to station frequency but did not fire transmitter.
I see this as bad
This is interesting. It seems that my ISP is dropping some mails (not
even in trash folder) and I have missed the beginning of this chain.
But to the subject:
Timer is good, but I have suggested (without any comment) few times to
randomize hound transmit frequency. That would keep "big guns"
I can also confirm sudden crash of wsjtx where JT9 process left running.
It did happen when I was playing with new mode buttons. I pressed
several buttons during one receive period and suspect that caused the crash.
How ever I could not reproduce it any more after restart.
My setup is Fedora
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-devel ma
HI!
With Fedora 35:
git clone https://git.code.sf.net/p/wsjt/wsjtx
and after that making compile gives:
Rick via wsjt-devel kirjoitti 23.7.2022 klo 11.02:
Hi Jarmo,
I compiled from sources too. Worked OK for me
Check your install.
Rick (GM4JIB)On 23/07/2022 08:15, jarmo via wsjt-devel
it should have done when audio moved 500->2800 while TX,
not now when RX period is started.
This is worse now as before rig did move while transmitting, but return
to RX went to wrong frequency. (1 bug)
Now rig does not move while transmitting and return to RX goes still
wrong. (2 bugs)
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
source tarball
on Ubuntu 18.04.6 LTS.
This seems to be a defect in hamlib; RX-frequency should always stay put.
73's de Kari, oh2gqc
On 3.6.2022 10.58, Saku via wsjt-devel wrote:
Subject:
Re: [wsjt-devel] Hamlib testing
From:
Saku via wsjt-devel
<mailto:wsjt-devel@lists.sourceforge.net>
Hi Michael !
Could you test with your IC-7300 this way:
set "split rig" and check "Allow TX frequency changes while
transmitting" in settings/general tab
Set your TX around 300Hz by shift+left click on waterfall. Start TX
period and while your TX is on move your TX around 2800Hz by
Hi Mike!
I have been using version that I have downloaded from Git on 2022-03-18
It has a problem that seems to be also in this latest version.
Fedora 35 linux
Wsjt-x v2.5.4 d28164-dirty
Icom Ic 7300
I am starting rigctld from script with:
mypath=/usr/local/bin/
myrigctld=rigctld
Hi!
Is <3X2021> one of then calls where Hound qso fails? Nothing done here,
other Hound qsos are gone well before but not this one.
Wsjx did not notice he answered to me. Just continue calling. When I
finally understood to push T3-button at right time I got RR73 but even
then my Hound just
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
Hi I
Think you were using linux. Then open command console and:
cd ~/.local/share/WSJT-X
grep -ni HisCall ALL.TXT | grep -i YourCall
Shows qso in fast and easy way (with line numbers of ALL.TXT).
Just replace the callsigns in command.
Jim Shorney via wsjt-devel kirjoitti 19.2.2022 klo 6.57:
HI Tony!
Have you tried to move mouse cursor on Pwr slider, not click at all, but
use mouse roll to move slider instead?
Anthony Hackenberg via wsjt-devel kirjoitti 12.2.2022 klo 0.05:
However, the minute I mouse click on that slider's position, the
slider's pointer jumps down to the bottom
Joe Taylor via wsjt-devel kirjoitti 3.1.2022 klo 18.54:
You can also download the packages from our SourceForge site:
https://sourceforge.net/projects/wsjt/files/
It may take a short time for the SourceForge site to be updated.
Is the [remote "origin"]
url =
Hi!
OS Fedora 35
rig Icom ic 7300
Hamlib self compiled
Hamlib 4.5~git ti joulu 14 22:54:46 2021 + SHA=db3837
Wsjtx self compiled
WSJT-X v2.5.3 69f9ec-dirty
Hamlib started from script:
rigctld -m 3073 -r /dev/icom7300 -t 4532 -s 19200 -C auto_power_on=0
--vfo &
Wsjtx settings:
Hamlib
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@hamtpad .git]$ rigctld
I agree with Reino!
I have set TX 1Hz up after three retries. It is amazing how often it helps!
If that does not make effect within few tries then just randomly jump TX
around band during every TX period so long that opponent station
receives your signal.
Sometimes trying first to jump to
HI!
I have done simple list file of US_callsign=state to cqrlog that can be
used with wsjtx remote connection.
The list is created from file that can be downloaded from fcc
(ftp://wirelessftp.fcc.gov/pub/uls/complete/l_amat.zip) holding all
information of callsign holders.
When US callsign is
Black Michael kirjoitti 12.11.2021 klo 15.54:
Try a new config and see if that fixes the problem.
wsjtx -r test
Mike W9MDB
Hi Mike!
No help. It is what it is and has always been so.
Image: started with test setup, minimized horizontally, closed, started
again.
F34/LXDE: laptop
HI!
I see the problem #1 every day when I open wsjtx. And every day I shrink
it horizontally to minimum. And again it starts wider than set at last time.
It is a "property" and I have tried to modify the main window with QT
designer, but as it branches to several pages it seems to be very hard
Just compiled version 2.5.1 (from sourceforge).
When I first started that one the main window was about 6cm wider than
old one in my display.
I could shrink it to back reasonable width (those 6cms), but when I
closed it and started again it's again back to that huge width.
After that I
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
Or you can zip the file:
zip -j9m ~/ALL1.zip ~/.local/share/WSJT-X/ALL.TXT
This will zip and remove ALL.TXT. Change number 1 to 2 ...3... etc. on
next times.
Zipping will reduce the file size approx 80% and you still have
everything there if needed.
On 16.10.2021 0.38, Bobby Chandler via
Hi!
With linux command console you can do it fast with:
grep -i oh1kh ~/.local/share/WSJT-X/ALL.TXT > ~/MYALL.TXT
That makes file MYALL.TXT to your home directory. Just replace my call
with your own.
After checked MYALL.TXT you can delete the ALL.TXT
rm ~/.local/share/WSJT-X/ALL.TXT
And
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 will try
Hi Marco!
Sounds familiar, hi...
As you use #2 Net Hamlib rigctld as cqrlog's rig you have to start
rigctld elsewhere with rig parameters. I guess that happens via bash script.
There you should use "--vfo" to get wsjtx work with split=rig.
Unfortunately that causes problems with cqrlog. It
HI !
My opinion:
I have also tested this some time ago running both programs in parallel
with same linux PC, same rig IC7300, OCF dipole 80-10m.
If wsjt-x decode is set to "Normal" or "Deep" I would rather say
"slightly better, in some cases".
But difference is so small that it did not cause
BSYSTEMS=="usb", ATTRS{idVendor}=="10c4",
ATTRS{idProduct}=="ea60" , ATTRS{serial}=="0001", SYMLINK+="ardu"
#Xduino UNO V
ACTION=="add", SUBSYSTEMS=="usb", ATTRS{idVendor}=="1a86",
ATTRS{idProduct}=="7523
Hi Reino, Bill and Mike!
FYI
It looks like the PTT staying on was an RFI problem after all.
Nothing changed in station setup, but a wire from the rear chassis of
IC7300 to a filter box that ICOM has in it's power cable was loosen
(fully detached).
As it is at back side of rig it is not
? Hamlib 4.3 release is
rolling out very soon.
You can check out the current version...
git clone https://github.com/Hamlib/Hamlib.git
<https://github.com/Hamlib/Hamlib.git>
Mike W9MDB
On Tuesday, August 31, 2021, 01:22:47 AM CDT, Saku via wsjt-devel
wrote:
There is no effect settin
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
Black Michael via wsjt-devel kirjoitti 27.8.2021 klo 18.22:
Those cache times are showing 10134ms = 10 seconds since the last time
ptt was polled. For FT4 that's not good.
What is your polling rate in WSJT-X?
Mike W9MDB
Hi MIke!
Poll rate is 5sec. Compared to FT4 period it is too long,
Thanks Bill!
Pulled last Hamlib from GItHub, compiled and installed.
Then cloned wsjt-x from sourceforge, made CMAKE_PREFIX_PATH to point
that cloned Hamlib directory and compiled.
Now I have running version that again has same problem than some time ago:
If I use 17m, then change to 20m
Bill Somerville via wsjt-devel kirjoitti 27.8.2021 klo 14.05:
if you are not going to use the bundled Hamlib sources then there is
little point in starting with the WSJT-X sources tarball we provide.
That tarball is specifically set up to build WSJT-X using that bundled
Hamlib. You would be
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
Hei!
Do you set *absolute minimums* for H and W and then close/open wsjtx?
As Bill says if window is a bit bigger for both directions, with my
display resolution ~2cm in H and ~1,5cm in W, retains it. That breaks
the whole display window positioning setup in every start with this
rather
HI!
If you set wsjtx main window to minimum horizontal and vertical size it
is not saved/loaded when wsjtx starts again resulting bigger main window
that was set.
Saving window W and H and X,Y position at close and reload them at start
should give same sized window.
OS Fedora Linux 34/ LXDE
I have done just so: use /usr prefix to override package hamlib.
With Fedora it is no problem to remove Hamlib package:
rpm -e --nodeps hamlib
And it does not remove all ham programs at same time because of
dependencies.
---
I have now pulled my hamlib clone directory from git and
HI Mike !
No error reported. Frequency just stays on where it was set by "monitor
returns to last used frequency". No change, no error.
I do not see any connection of File/Settings/Frequencies and rig
polling. It should read what rig display has in not depending on what is
in band selector
Thanks Bill!
I have not touched Settings/general ... I cannot remember when was the
last time. Perhaps it was some day in stone age. :-)
Both "monitor off..." and "monitor returns ..." were unchecked. Checked
now the "monitor returns to last used frequency" and it helps for "OOB"
problem.
Hi!
Just upgraded my Fedora from 33 to 34.
Removed all self compiled hamlib and wsjtx versions and installed
packages from repository:
wsjtx-2.4.0-1.fc34.x86_64
hamlib-4.1-1.fc34.x86_64
It seems to work. Only one question arises:
*Is it in purpose that every time I start wsjtx it shows
Rather good way to get qso one period faster. Important with VHF ES
DXing (mostly 6m). Conditions change so fast.
There are not so many 4 character grids in Japan. And if callsign's QRZ
or HamQTH entry is up to date external logger adds the locator, usually
6 characters, or even more precise.
69 matches
Mail list logo
