Try checking out hamlib in a new directory.
I'm seeing that the build-aux directory isn't being cleaned.
de Mike W9MDB
On Sunday, March 15, 2020, 01:58:46 PM CDT, Claude Frantz
wrote:
> The first lines of the output are:
>
> $ make clean
> CDPATH="${ZSH_VERSION+.}:" && cd . &&
Can you please run rigctld with "-Z -v" and redirect the log to a file.
Then send me the file.
Are you running one of the split modes? What happens with no split?
de Mike W9MDB
On Sunday, March 15, 2020, 11:03:02 AM CDT, Claude Frantz
wrote:
Hi Bill, Mike & all,
I'm testing
Was working with another ham who has a bit of a problem keeping up with the
mental task of everything going on and understanding it.
Thought of two things WSJT-X could do to prevent boo-boos
In Hound mode:
#1 When changing bands select TX1 automatically#2 When RR73 has been received
from Fox
Was working with someone trying the VP8PJ dxpedition and he had a problem that
I think needs fixing.
He was pulled down by Fox to 346 and lost the path so got bumped to 646 and
continued to transmit until timed out. He then went 1000 and continued TX3
which then immediately bumped back down to
Why aren;t the times for ALL.TXT taken from the jt9 decode process which has to
get them right since it's got the wav filename to work with?
de Mike W9MDB
On Thursday, February 20, 2020, 05:16:06 PM CST, Bill Somerville
wrote:
On 20/02/2020 22:01, Martin Davies G0HDB wrote:
I'm
I just noticed the same thing today. I had two decode periods that both showed
the same time in ALL.TXT when I was debugging problem with JTAlert. I
confirmed they were two separate periods by decoding the WAV files manually.
So the question is where does time for ALL.TXT come from and/or how
Don't bother with less than 16GB. 4GB is considered absolute minimum for
Windows 10 when you aren't doing anything.CPU bound includes memory speed too
as does cache matter so faster memory and bigger cache can help considerably.
This would be my criteria
#1 Minimum memory -- 16GB#2 Minimum disk
It may be rig related...here's a video on how to setup rigctld debugging that
you can send rig debug logs.
https://www.youtube.com/watch?v=0yZG1-v-BXA
Bill...it would be super nice if we could get debug turned on in WSJT-X as the
behavior is a bit different and different code paths.
de Mike
Looking at Steve's explanation it appears we can get up to 4 passes -- the
additional pass for the multiple methods on each main pass.Sound right?
Mike
On Thursday, December 26, 2019, 11:07:24 AM CST, Black Michael
wrote:
Ok...not as insane as I thought I wasthe XYL will be
Ok...not as insane as I thought I wasthe XYL will be happy with that :-)
I'm debugging this on a friend's computer.
Here's a dropbox link to the WAV file that produces 4 passes as can be seen
below which I've put in bold and
if the non-AP decoding attempts have failed
to produce a decode for a candidate, before moving on to the next candidate in
a decoding pass.
73
Bill
G4WJS.
On 26/12/2019 14:56, Black Michael via wsjt-devel wrote:
OK...let's call it 4-pass thenI wasn't including the rx offset
, December 26, 2019, 08:50:50 AM CST, Bill Somerville
wrote:
On 26/12/2019 14:36, Black Michael via wsjt-devel wrote:
> Is there a 3-pass going on now in 2.1.2?
> I'm seeing 3 passes from the decodes.
> de Mike W9MDB
Mike,
this is nothing new. The first decode attempt is at the
Is there a 3-pass going on now in 2.1.2?I'm seeing 3 passes from the
decodes.de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Consider transitioning to FLRig -- actively supported and can set up with all
sorts of programs talking to it either via rigctld or rigctlcom
I haveWSJT-XLog4OM3 local utilitiesN1MMFLDigi
All working at once talking to the rig.
WSJT-X -> FLRigLog4OM -> rigctld -> FLRigLocal utils -> both waysN1MM
Just change the WSJT-X definition to unsigned int. Actually it would seem to
me that typedef in HamliblibTransceiver.hpp should be deleted.
de Mike W9MDB
On Sunday, December 22, 2019, 10:41:20 AM CST, Alessandro Gorobey via
wsjt-devel wrote:
Hi all,
I try to recompile wsjtx
Not in the middle.after you're supposedly done and moved to somebody else
and they repeat the RR73.
Mike
On Sunday, December 22, 2019, 03:41:06 AM CST, Reino Talarmo
wrote:
While in the middle of a QSO you should use either ’Now’ or ’Next’ to modify
message sequence instead
Visit the link in the email.
de Mike W9MDB
On Thursday, December 19, 2019, 05:46:49 AM CST, JD Delancy
wrote:
unsubscribe w3...@comcast.net wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Turns out it was a bug in the FLRig backend in hamlib.
Testing the fix now
de Mike W9MDB
On Wednesday, December 18, 2019, 11:25:24 AM CST, Saku
wrote:
Black Michael via wsjt-devel kirjoitti 18.12.2019 klo 13.43:
> Not a collision.try it yourselfset rig to VFOA US
That was what I meant by not behaving well on Fake It.Of course your
explanation is much better :-)
Mike
On Wednesday, December 18, 2019, 07:10:48 AM CST, Bill Somerville
wrote:
On 18/12/2019 12:24, Black Michael via wsjt-devel wrote:
> The only reason you would HAVE to run Mode=
The only reason you would HAVE to run Mode=Rig Split on WSJT-X is if your rig
doesn't behave well on Fake It.Generally speaking rigs will behave a bit better
in Rig Split.
If you are saying you don't run Fake It either then you are risking harmonics
and/or power loss. Split and Fake It both
to FLRig, another
local utility talks to rigctld
All works hunky-dory except for this one bug-a-boo. Gotta' get some debug
today.
On Wednesday, December 18, 2019, 03:36:23 AM CST, Saku
wrote:
Black Michael via wsjt-devel kirjoitti 18.12.2019 klo 0.47:
Band change seems to work all
Hamlib
On Tuesday, December 17, 2019, 05:01:25 PM CST, Bill Somerville
wrote:
On 17/12/2019 22:47, Black Michael via wsjt-devel wrote:
v2.1.2
We're getting an inconsistent and somewhat hard to reproduce situation where
on an IC-7300 VFOB is not getting set to USB-D
v2.1.2
We're getting an inconsistent and somewhat hard to reproduce situation where on
an IC-7300 VFOB is not getting set to USB-D.
It seems to me that WSJT-X should be setting USB-D mode to VFOA and, when in
split, to VFOB on every transmit but it appears there's some time when WSJT-X
thinks
It's not a lockout file.
The idea is very simple.
Right now call first always picks the 1st decode...ergo the problem
So the idea is that once a call is worked it gets put in a list (doesn't matter
whether or not you log it). The call first logic checks the list and ignores
anybody in it.If
an see in the link below the noise at TX start:
https://youtu.be/peVSAZQ08yU
which cause power overshooting at the beginning of the timeslot.
73,
From: Black Michael via wsjt-devel
Sent: 1 décembre 2019 23:36
To: WSJT software development
Cc: Black Michael
Subject: Re: [wsjt
I'm all ears for opinions from operators who have had a call pileup on them.
If Call 1st is to be implemented at all it should be robust.
It's a trivial patch which I'll make myself and submit for consideration in
WSJT-X.
de Mike W9MDB
___
wsjt-devel
Seems double-clicking an RR73 in 2.1.2 sends TX4 instead of TX5. I guess
either would work but TX5 seems more in line with a normal QSO.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Audio dropout like this is usually caused by the USB audio device
disconnecting.And that is usually case by RFI. Chokes on USB cables (and all
other cables) usually solves the problem.Ensure your ethernet cables are
shielded too. Newer CAT 7 or CAT 8 cables are already shielded. And ground
Yes you can post a web link.
de Mike W9MDB
On Sunday, December 1, 2019, 06:21:03 PM CST, Frederic Beaulieu
wrote:
Hi,
I'm using WSJT-X/FT8 regularly for more than a year now. One month ago, I start
to notice on my IC-7300's audio scope that occasionnaly, no audio was sent
are in the queue pop the top one off and
work it. Keep the queue depth to a limit or add time to it to time out entries
after a programmable limit.
Mike
On Saturday, November 30, 2019, 10:17:58 PM CST, Jim Brown
wrote:
On 11/30/2019 2:15 PM, Black Michael via wsjt-devel wrote:
>
Karl...download the latest hamlib from my fork. Compile it and use rigctld to
test and generate debug.
https://github.com/mdblack98/Hamlib.git
rigctld -m 122 -r /dev/ttyx -s 19200 -v -Z > com port and baud
to suit your setup.
Change WSJT-X to use "Hamlib NET rigctl" and the Test button
You need to upgrade to 2.1.2
There was an Icom bug that was fixed and probably is what you're seeing.
de MIke W9MDB
On Wednesday, November 27, 2019, 09:34:59 AM CST, m.weiss--- via wsjt-devel
wrote:
Hello WSJT,
I am having problems with CAT control between WSJT-X and my Icom
AM CST, Bill Somerville
wrote:
Hi Mike,
is this just a build from the current Hamlib master, or are there some more
patches to come? I ask because I want to build WSJT-X 2.1.2 kits today with
this issue resolved.
73
Bill
G4WJS.
On 26/11/2019 12:44, Black Michael via wsjt-devel
Helps if I send the right dropbox link
https://www.dropbox.com/s/dyopovfc318r0dd/bin.zip?dl=0
Mike
On Monday, November 25, 2019, 11:12:30 PM CST, Black Michael
wrote:
For those having Icom rig control problems here's a zip file of a 32-bit
version of hamlib.
For those having Icom rig control problems here's a zip file of a 32-bit
version of hamlib.
https://www.dropbox.com/s/9gv73e9m0stijxw/gitnotes.docx?dl=0
It will work with the 64-bit version of WSJT-X also.
#1 Unzip this file into it's own directory.
#2 Ensure WSJT-X is not running.
#3 Run this
Please run this and send me the log.txt file
In the WSJTX\bin directory run this
rigctl-wsjtx -m 378 -r COM1 -s 19200 -Z -v V VFOA f q 2>&1 >log.txt
Adjust COM port and baud rate to suit
de Mike W9MDB
On Monday, November 25, 2019, 04:29:10 PM CST, Gene H
wrote:
Same here
AM, Black Michael via wsjt-devel
wrote:
Did you click on the Unsubscribe link on this page:
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Which points to this:
https://sourceforge.net/projects/wsjt/lists/wsjt-devel/unsubscribe
de Mike W9MDB
On Thursday, November 21, 2019, 10:31:09
Did you click on the Unsubscribe link on this page:
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Which points to this:
https://sourceforge.net/projects/wsjt/lists/wsjt-devel/unsubscribe
de Mike W9MDB
On Thursday, November 21, 2019, 10:31:09 AM CST, James Kennedy
wrote:
Good
Try using FLRig and rigctld instead.
FLRig to your rigrigctld to FLRigLog4OM to rigctldWSJT-X to FLRigFLDigi to FLRig
I have all of these running at once.
de Mike W9MDB
On Tuesday, November 19, 2019, 11:43:38 AM CST, Zeev Stadler
wrote:
Hello Doug,
Getting the log from WSJT-X to
wrote:
On 13/11/2019 17:37, Black Michael via wsjt-devel wrote:
> WSJT-X decided to die this morning when I was doing some frequency
> calibration testing.
> While idling it crashed and would not restart.
>
> The WSJT-X.ini file in this link does not allow WSJT-X.ini to start -
WSJT-X decided to die this morning when I was doing some frequency calibration
testing.While idling it crashed and would not restart.
The WSJT-X.ini file in this link does not allow WSJT-X.ini to start -- it
crashes soon after startup.
https://www.dropbox.com/s/1w5imlr2ym2v29z/wsjt-x.ini?dl=0
Small boo-boo in fmtave...says kHz instead of MHzAlso...the frequency
resolution should be improved to Hz for doing other measurements like for the
FMT where the frequencies may not be even kHz intervals. I'd recommend
everything be changed to Hz for consitency and ease of interpretation.
t to Rig
I'm doing transceive on slice C set to DIGU , No split set on the flex and the
freq does not change on the Flex .
I've used The F/H from day one, setup the way it is and always assumed I was
transmitting where the red Goalie is
Ed N5DG
On 11/5/2019 9:59 AM, Black Michael
It sounds like you do have Split set in the WSJT-X rig control, right?But it
sounds like you were transmitting on VFOA...which would have been 500Hz lower.
So what does your Flex tell you?
This has nothing to do with Fox/Hound.
de Mike W9MDB
On Tuesday, November 5, 2019, 09:53:37 AM CST,
You don't have ALL.TXT either so something is really wrong with your setup.
Look at the WSJT-X.ini file (use Notepad) and find the "SaveDir" entry and see
where it points to.
de Mike W9MDB
On Thursday, October 31, 2019, 07:51:03 PM CDT, Carl Buehler
wrote:
Thank you for the
I believe what he's saying is that the # of slots should be controlled better.
For example, if you are responding to a call from a single slot stay in the
single slot.Or use the signal report from incoming calls to determine if you
can afford to lose the dB going to multislot with them.
It was
A known bug -- just resize the window and it will show again.
de Mike W9MDB
On Tuesday, October 15, 2019, 10:43:19 PM CDT, Donn Taylor
wrote:
Just updated to the latest WSJTx that supports FT4. When I first open the
program the setting window is available and I am able to make
confusion. If this protocol used TCP WSJT-X
would definitely be the server.
Mike
On Tuesday, October 15, 2019, 09:06:47 AM CDT, Michael Pittaro
wrote:
On Tue, Oct 15, 2019 at 9:34 AM Black Michael via wsjt-devel
wrote:
>
> NetworkMessage.hpp -- several places. Though after r
6:45:44 AM CDT, Bill Somerville
wrote:
On 15/10/2019 05:35, Black Michael via wsjt-devel wrote:
> The description in the WSJT-X source is using the terminology of
> WSJT-X as the server and anybody talking to it as clients.
Mike,
where are you seeing that? It is not correct and
The description in the WSJT-X source is using the terminology of WSJT-X as the
server and anybody talking to it as clients.
There are simply messages from and to wsjt-x.
You'll note that every message described shows Out/In capability.Out means from
wsjt-xIn means to wsjt-x.
The heartbeat
According to http://wsprnet.org/drupal/wsprnet/stats the 7-day moving average
looks to be 1.4M spots per day.
de MIke W9MDB
On Thursday, October 10, 2019, 08:43:48 AM CDT, Philip Gladstone
wrote:
How much traffic does WSPRNET get? How many spots are reported on a daily
basis? I'm
I note that the audio thread is set to priority 4 in the code.
m_audioThreadPriority = static_cast (m_settings->value
("Audio/ThreadPriority", QThread::HighPriority).toInt () % 8);
I have periodic times when decoding stops for a couple of cycles (appears to be
due to disk activity on the SSD)
I see it nowalready been removed by the time it gets to the
regexthanks Bill.
Mike
On Friday, September 6, 2019, 03:43:54 PM CDT, Bill Somerville
wrote:
On 06/09/2019 21:00, Black Michael via wsjt-devel wrote:
Hmmm...that expression doesn't seem work
exp.
It ended up like this:
QRegularExpression words_re
{R"(^(?:(?(?:CQ|DE|QRZ)(?:\s?DX|\s(?:[A-Z]{1,4}|\d{3}))|[A-Z0-9/]+|\.{3})\s)(?:(?[A-Z0-9/]+)(?:\s(?[-+A-Z0-9]+)(?:\s(?(?:OOO|(?!RR73)[A-R]{2}[0-9]{2})))?)?)?)"};
73
Bill
G4WJS.
On 06/09/2019 20:38, Black Michael via wsjt-deve
]{2}[0-9]{2})))?)?)?)"};
73
Bill
G4WJS.
On 06/09/2019 20:38, Black Michael via wsjt-devel wrote:
Yeah..I guess you mean it should have been an OR clause?
Mike
On Friday, September 6, 2019, 02:34:37 PM CDT, Bill Somerville
wrote:
On 06/09/2019 18:24, B
Yeah..I guess you mean it should have been an OR clause?
Mike
On Friday, September 6, 2019, 02:34:37 PM CDT, Bill Somerville
wrote:
On 06/09/2019 18:24, Black Michael via wsjt-devel wrote:
Here's the patch to fix the double-click on <...>
de Mike W9MDB
*** &quo
. If you guys don’t hear about things, how can you
know about them? Sorry if reporting frustration annoyed you.
On Sep 4, 2019, at 7:18 AM, Black Michael via wsjt-devel
wrote:
Let me give an example
Running JTAlert (I don't even look at the WJST-X window anymore) you see a call
y
If Meinberg wasn't working it's probably because you didn't select your
continent from the pulldown during installation.
WIndows time will not work very well in the long run.
de Mike W9MDB
On Friday, September 6, 2019, 12:14:02 PM CDT, Ken Chandler
wrote:
Hi guys
Seems it was
This has been asked numerous times and I've never seen a reply about it.I'd
like to think it has been fixed but nobody knows what changes are done anymore.
de Mike W9MDB
On Tuesday, September 3, 2019, 11:06:35 AM CDT, Andy Durbin
wrote:
With WSJT-X 2.1.0 and this group of decodes
Looks like something umw.edu has implemented. It's not from this list.
http://tmda.net/
On Tuesday, August 20, 2019, 10:11:57 PM CDT, Matthew Miller
wrote:
Not sure if this email will get thru or not...just noticed when I replied to a
message in this board I got an odd email...is
Look at the audio mixer control and adjust the audio level there for WSJT-X.
What I'm not sure of is if this is a Windows 10 update that caused it or a Qt
library change.I think Bill has mentioned it's a recent Windows 10 update that
put the mixer in the path now.
Does the 32-bit version cause
It appears you may be dropping audio. Do you have other decodes at 140145,
140215 ?
#1 File/Delete all *wav.#2 Ensure you have an exclusion for
%LOCALAPPDATA%\WSJT-X in all your antivirus/malware software.#3 Save/All
Then watch the save directory and see if the WAV files aren't being saved.
And what was the solution?
de Mike W9MDB
On Thursday, August 8, 2019, 12:29:57 PM CDT, Jan C. Robbins
wrote:
FT8 up and running with FTDX-101MP. Tks to all who responded! 73
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Give the FT-991 entry a try and see how it does. It's got the same IF command
response so might work.Looks like we'll have to add it.
de Mike W9MDB
On Thursday, August 8, 2019, 09:54:29 AM CDT, Jan C. Robbins
wrote:
Is there any way to use current WSJT-X (2.0.1) with the new
’ in WSJT-X plays with
drop-outs unfortunately.
de Hans PD4RM
Op 6 aug. 2019, om 21:17 heeft Black Michael via wsjt-devel
het volgende geschreven:
What's does the Behringer's USB driver show for the data rate? Should be 48kHz
de Mike W9MDB
On Tuesday, August 6, 2019, 02:10:45 PM CDT
What's does the Behringer's USB driver show for the data rate? Should be 48kHz
de Mike W9MDB
On Tuesday, August 6, 2019, 02:10:45 PM CDT, Hans Schiessl
wrote:
WSJT-X version: 2.10Platform: Windows 10Audio interface: USB Behringer
UCA222Both on 32 and 64 bit tested
Issue:When
I just confirmed this behavior. If you re-enable during the LogQSO popup it
gets turned of when you click OK.
de Mike W9MDB
On Tuesday, August 6, 2019, 09:40:29 AM CDT, Dave Slotter, W3DJS
wrote:
No, it's not happening because of 73 messages. Please re-read what I wrote
before
The solution to prevent extra files and extra program entries is to NOT put the
version # in the installer application name. It should just be "WSJTX" and not
"WSJT x.x.x".That's what causes the multiple program entries that are difficult
to remove.
I don't what's being used an installer but
Been there for quite a while...couldn't tell you exactly when it was added but
I'm pretty sure it was early in the Fox/Hound development.
Mike
On Tuesday, August 6, 2019, 12:26:53 AM CDT, Bill Richter
wrote:
Is it new or did it just get unchecked during an update? I know it was
Signals > 1000 will only show if you check "Rx All Freqs"
de Mike W9MDB
On Monday, August 5, 2019, 11:23:25 PM CDT, Bill Richter
wrote:
When I switch to Hound mode, I no longer see decodes in the decode window.
Signals are still present in the waterfall. Is this expected behavior?
owngrading to previous
version problemsall sorts of reasons to have a backup. Manual backup may
be best plus the one-time copy if there is no backup.
Mike
On Monday, August 5, 2019, 09:09:59 AM CDT, Bill Somerville
wrote:
On 05/08/2019 14:53, Black Michael via wsjt-devel wrote:
#1 Make the default installation path use the version number (including RC
candidates) do avoid all the duplicate entries one gets in the application
manager.
#2 Make a "Backup" menu entry to allow backing up the INI file and create a
backup by default if it doesn't exist.
de Mike W9MDB
Do a frequency reset
File/Settings/Frequencies -- right-click in Working Frequencies and "Reset".
de Mike W9MDB
On Wednesday, July 31, 2019, 08:27:00 PM CDT, John Zantek
wrote:
Ø I noticed that while using the FT8 mode on a standard FT8 frequency, when
when the FT4 mode is
ncorrectly and somebody started
interpreting it as a propagation mode label.
Oh well
https://groups.yahoo.com/neo/groups/adifdev/conversations/topics/6055
On Wednesday, July 31, 2019, 11:12:15 AM CDT, Bill Somerville
wrote:
On 31/07/2019 16:58, Black Michael via wsjt-devel wrote:
> The A
The ADIF committee apparently thinks all software is easy to change and should
do so to match their intentions.
We unsuccessfully fought this idea so you'll just have to live with what
they've done.
de Mike W9MDB
On Wednesday, July 31, 2019, 10:54:00 AM CDT, Serge Smirnoff R6YY via
gle. I've changed dongles, ...no difference. I've chased
the sound card potential issue from several angles...that's not it.
...and Windows system uses the internal sound card of the computer.
Hasan
On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel
wrote:
What do you have for the soundc
not it.
...and Windows system uses the internal sound card of the computer.
Hasan
On Tue, Jul 30, 2019 at 7:43 AM Black Michael via wsjt-devel
wrote:
What do you have for the soundcard setting in JTAlert and WSJT-X?
On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri
wrote:
Uwe,I just changed
What do you have for the soundcard setting in JTAlert and WSJT-X?
On Tuesday, July 30, 2019, 07:30:17 AM CDT, Hasan al-Basri
wrote:
Uwe,I just changed both those settings you recommended. Now, I'll have to
wait, up to a couple days to see if it accomplished anything.
Unfortunately
Attribute it to inexperienceyou should contact them and help to politely
educate them.
Something like:
Hi there OM,Saw you in a QSO with and after the QSO was complete you
called CQ on the same offset.You should consider working people in split by
choosing a Tx offset that is clear of
There's an inconsistency in double-clicking Tx4 selector.I assume txb4 should
be same as txrb4 for the FT4 RR73 settings.
void MainWindow::on_txrb4_doubleClicked (){ // RR73 only allowed if not a type
2 compound callsign auto const& my_callsign = m_config.my_callsign (); auto
is_compound =
Is this from the 64-bit version? Can you test the 32-bit version?
de Mike W9MDB
On Thursday, July 18, 2019, 08:03:24 AM CDT, Andy Durbin
wrote:
"You should also note that the frequency is immediately reset back to
where it was before the resolution test started.:
Bill,
I provided
Try Joe's presentation here
http://dokufunk.org/upload/taylor.ppsx
de Mike W9MDB
On Wednesday, July 17, 2019, 04:47:20 AM CDT, Conrad PA5Y
wrote:
Hello Joe I am quite interested to learn more about the GMSK waveform
generation, where can I read more about it and the
Did you do a frequency reset?
de Mike W9MDB
On Tuesday, July 16, 2019, 01:53:27 PM CDT, Marco Calistri
wrote:
In my case, with OpenSuse Tumbleweed 64 bits, I have an RPM package
which helps to adjust Qt5 settings and I have selected Style=QtCurve.
The Style=Fusion is also available
Rename WSJT-X.ini and see if that fixes it. Could be a corrupt filewe've
seen that a few times.
de Mike W9MDB
On Tuesday, July 16, 2019, 05:45:37 AM CDT, DG2YCB, Uwe
wrote:
I’ve had it five times now, that when trying to open “Settings” WSJT-X 2.1.0
64-bit showed an empty
File/Settings/Frequences -- right-click in "Working Frequencies" and Reset.
de Mike W9MDB
On Monday, July 15, 2019, 12:04:32 PM CDT, Tim Goeppinger via wsjt-devel
wrote:
I do not see the FT4 frequencies in the frequency list. I read the user
guide and did not see this addressed.
, 2019 at 11:36 AM Black Michael via wsjt-devel
wrote:
Oopsso no disconnect...so now we have to find out what problem he's having
specifically.
C:\WSJT\wsjtxrc7\bin>ft8code "CQ 3DA0VV EM49" Message
Decoded
Err
i3.n3
1. CQ 3DA0VV EM49 CQ 3DA0VV
* 4. Nonstandard calls
de Mike W9MDB
On Tuesday, July 9, 2019, 10:22:10 AM CDT, Bill Somerville
wrote:
On 09/07/2019 16:13, Black Michael via wsj
There does seem to be a disconnect between the GUI and the coding software.This
is with RC7.
But looks good hereC:\WSJT\wsjtxrc7\bin>jt9code "CQ 3DA0VV EM49" Message
Decoded Err? Type
:
31 hours and counting since I installed the debug version you sent me the link
to. No errors. Will report more tomorrow morning.I can't imagine that this
install somehow fixed the issue?73, N0ANHasan
On Sat, Jul 6, 2019 at 2:38 PM Black Michael via wsjt-devel
wrote:
What web browser do you
the debug version you sent me the link
to. No errors. Will report more tomorrow morning.I can't imagine that this
install somehow fixed the issue?73, N0ANHasan
On Sat, Jul 6, 2019 at 2:38 PM Black Michael via wsjt-devel
wrote:
What web browser do you use? There aren't a lot of these report so
period.
Rick WK1P
From: Black Michael via wsjt-devel
Sent: Saturday, July 6, 2019 3:35:43 PM
To: pe...@ni6e.com; WSJT software development
Cc: Black Michael
Subject: Re: [wsjt-devel] WSJT Audio Input Loss What web browser do you use?
There aren't a lot of these report so it doesn't seem like
What web browser do you use? There aren't a lot of these report so it doesn't
seem like this is a common problem otherwise we'd hear more about it5.
There has to be something in common.
So what does your audio path look like? Rig, sound card, USB Hub?, PC model.
de Mike W9MDB
On
ack for rx audio) Audio sounds perfect to
the ear. Levels are right...Most peculiar!
73, N0ANHasan
On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel
wrote:
Failing audio or rig connections are most always due to RFI or USB ports going
to sleep.If RFI low power transmissions can be tested
r both RX and
TXand has been for over a year. Any further ideas are most welcome
(TS-590sg, running from headphone jack for rx audio) Audio sounds perfect to
the ear. Levels are right...Most peculiar!
73, N0ANHasan
On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel
wrote:
Fail
Was working K2A and after sending 73 set up to work another call.
K2A repeated the RRR and when double-clicked WSJTX picked TX4 instead of TX5
de Mike W9MDB___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
It appears that usbif4cw is just a CW interface. Why would you integrate it
with WSJT-X which doesn't do CW?
de Mike W9MDB
On Thursday, July 4, 2019, 08:57:47 AM CDT, usbif...@nksg.net
wrote:
Hello all,
We are developing a digital mode / CW interface named USBIF4CW from 2002.
2019 at 4:39 PM Black Michael via wsjt-devel
wrote:
Failing audio or rig connections are most always due to RFI or USB ports going
to sleep.If RFI low power transmissions can be tested and if they work but high
power does not then it's RFI.The USB ports going to sleep can be
solved.https://www.win
audio) Audio sounds perfect to
the ear. Levels are right...Most peculiar!
73, N0ANHasan
On Wed, Jul 3, 2019 at 4:39 PM Black Michael via wsjt-devel
wrote:
Failing audio or rig connections are most always due to RFI or USB ports going
to sleep.If RFI low power transmissions can be tested and if they
2019 2:36 PM, Black Michael via wsjt-devel wrote:
Failing audio or rig connections are most always due to RFI or USB ports
going to sleep. If RFI low power transmissions can be tested and if they work
but high power does not then it's RFI. The USB ports going to sleep can be
solved.
Failing audio or rig connections are most always due to RFI or USB ports going
to sleep.If RFI low power transmissions can be tested and if they work but high
power does not then it's RFI.The USB ports going to sleep can be
601 - 700 of 1443 matches
Mail list logo
