That's not the format for the FT8 RoundupIt only takes the state in the
exchange and a signal report.
Check paragraph 4 here.
https://www.rttycontesting.com/ft8-roundup/rules/
de Mike W9MDB
On Friday, November 30, 2018, 1:39:38 PM CST, Al Flapan
wrote:
I went to settings and
According to the FT8 Roundup
ruleshttps://www.rttycontesting.com/ft8-roundup/rules/
4. Exchange:
4.1. United States: Signal report and State.
4.2. Canada: Signal report and Province.
4.3. DX: Signal report and consecutive serial number, starting with 001.
de Mike W9MDB
On Thursday,
According to the FT8 Roundup
ruleshttps://www.rttycontesting.com/ft8-roundup/rules/
4. Exchange:
4.1. United States: Signal report and State.
4.2. Canada: Signal report and Province.
4.3. DX: Signal report and consecutive serial number, starting with 001.
de Mike W9MDB
On Thursday,
Another horrible article by a "science writer". No references and the article
itself says "not expected to be overly powerful"...apparently not even power
enough for NOAA to pay any attention to it.
I'm reminded of Chicken Little
de Mike W9MDB
On Saturday, November 24, 2018,
Solar winds happen all the time. Where did you see a warning about this?
NOAA doesn't show any alerts
https://www.swpc.noaa.gov/products/notifications-timeline
de Mike W9MDB
On Saturday, November 24, 2018, 10:42:32 AM CST, n...@comcast.net
wrote:
STREAM of solar wind is
How about a web page only for bugs?
Could be put in the Help menu "Known Bugs/Issues" and doesn't require a new
release to keep current. A section for each release would be appropriate
showing "Fixed" status too.
Users would eventually learn to check that first avoiding most of the repeat
Black Michael via wsjt-devel wrote:
> > It was mentioned a while ago that changes would be made to the Fox
> > mode to avoid the power loss for multiple QSOs going on.
> Some months ago we said "The existing FT8 DXpedition mode will still
> be supported, and a more pow
It was mentioned a while ago that changes would be made to the Fox mode to
avoid the power loss for multiple QSOs going on.
Has this been done? rc4 still points to the old DXpedition guide.
de Mike W9MDB
___
wsjt-devel mailing list
Is the specific contest mode used during decode? Couldn't the meaning of those
3 bits change depending on which contest is in place?
de Mike W9MDB
On Tuesday, November 20, 2018, 8:07:09 AM CST, Bill Somerville
wrote:
On 20/11/2018 13:20, Brian Waterworth wrote:
I
CST, Joe Taylor
wrote:
On 11/15/2018 9:17 AM, Black Michael via wsjt-devel wrote:
> Was checking out the recent_calls hash and noticed this:
>
> mskrtd.f90: recent_calls(i)(1:13)=' '
>
> But recent_calls is char*12.
Not correct. See at top
Was checking out the recent_calls hash and noticed this:
mskrtd.f90: recent_calls(i)(1:13)=' '
But recent_calls is char*12.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
If the 7851 is like the 7300 then you have to be in USB DATA mode to transmit
over the USB interface.You should select Data/Pkt mode in the WSJT-X radio
settings.
de Mike W9MDB
On Sunday, November 11, 2018, 1:14:24 AM CST, Stephen Ireland
wrote:
Hi Folks,
This may nor
Known problem with RC3 and it's not fatal...just annoying.
Solution provided by Bill here in #4.
https://sourceforge.net/p/wsjt/mailman/message/36443778/
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
And can you confirm you have USB mode selected in WSJTX?Mike
Sent from Yahoo Mail on Android
On Sat, Nov 3, 2018 at 11:30 AM, Tom Ramberg wrote: Yes,
I used the FTdx5000 rig entry, in lack of FTdx3000. And no, it did not change
the VFO B to USB on transmit. I didn't notice, so lost two
I guess you were using the FTDX5000 rig entry?
Can you repeat this problem? I do notice that VFOB mode does not get set until
you transmit.So if you make the mode on VFOB LSB and start WSJT-X it will stay
LSB until you transit.But, when you transmit it should change VFOB's mode to
USB if you
Known problem with RC3 and it's not fatal...just annoying.
Solution provided by Bill here in #4.
https://sourceforge.net/p/wsjt/mailman/message/36443778/
de Mike W9MDB
On Friday, November 2, 2018, 10:16:13 AM CDT, Dale Wheeler via wsjt-devel
wrote:
windows 10
wsjt-x
That would (should) have no bearing.Mike
On Sunday, October 28, 2018, 8:42:19 AM CDT, Mike
wrote:
More on previous reply, I will using hold tx frequency if that could have any
bearing.
Mike
On 10/28/2018 6:03 AM, Black Michael via wsjt-devel wrote:
You must be double
The directions are missing the phrase "if your rig is capable of it". Kind of
assumes everybody understands this stuff.
Bandwidth settings are on of the big variables on rigs and have generally
gotten wider as the years have gone on.
So...if your FT-100 cannot widen bandwidth you are stuck
You must be double-clicking the wrong message.If this was a bug we'd have all
sorts of complaints.
Can you give an example of what you are clicking on, what you expect, and what
you get?
de Mike W9MDB
On Sunday, October 28, 2018, 5:08:59 AM CDT, Mike
wrote:
When I was using it
happening as the interface/Flex
interprets commands actually intended for a Kenwood radio.
Again, thanks for the response - much appreciated!
On Oct 27, 2018, at 12:17 PM, Black Michael via wsjt-devel
wrote:
The flex backend in hamlib which WSJT-X uses is just using the standard Kenwood
calls
The flex backend in hamlib which WSJT-X uses is just using the standard Kenwood
calls to set split.
All that does is the SP1 command which should simply turn on split
It also sets the freq and mode for VFOB using the standard kenwood commands.
It knows nothing of slices.
So it's really
, USA
On Oct 27, 2018, at 10:55 AM, Black Michael via wsjt-devel
wrote:
Ensure you don't have the other frequency on a separate slice. That may be
confusing things.Just put on one slice and it should behave.
de MIke W9MDB
On Saturday, October 27, 2018, 2:05:02 AM CDT, Star Light
work just fine on one slice. That’s one
of the reasons I posted the question.
Does anybody have any actual knowledge about this?
Thanks, Russ
Sent from my iPhone
On Oct 25, 2018, at 9:16 PM, Black Michael via wsjt-devel
wrote:
I don't know why you would need separate slices to work split
Would really like to see Fox messages passed through to JTAlert.Then one can
use JTAlert's audio alerts and email features to hear DX alerts.Plus spotting
the Fox would seem a good idea so that propagation paths could be seen on
PSKReported and such.
de Mike W9MDB
Did you try searching the archives? This has been asked and answered numerous
times.
Known problem with RC3 and it's not fatal...just annoying.
Solution provided by Bill here in #4.
https://sourceforge.net/p/wsjt/mailman/message/36443778/
de Mike W9MDB
On Thursday, October
I don't know why you would need separate slices to work split in WSJT-X.
Aren't slices really for different frequency ranges?
Split in WSJT-X is all inside the audio band pass of one slice. It just
adjusts the frequency so that the audio is always in the 1500-2000Hz
offset.Split is really
Have you tried any others? Maybe the FTdx5000?
Looks like the 3000 has the same command set.
If it does work we can add a definition for it.
de Mike W9MDB
On Thursday, October 25, 2018, 9:45:30 PM CDT, S.WATANABE
wrote:
What radio can I choose for my Yaesu FTdx3000 to interface
Noticing a few operators calling TX1 below 1000.Is that now blocked in V2.0?
Or should it be? At best they are wasting their time and at worst causing
interference to others.
>From the guide for those that aren't aware:
Hounds make initial calls anywhere in the range 1000 – 4000 Hz.
Fox
A decrease of bandwidth by a factor of 6 will increase reported SNR by
approximately 16dB.But that's just a matter of what noise reference you
use...not any real change in the signal level.If you used signal peak instead
of RMS the SNR reported would be really lowit's all relative to the
To summarize what you saw it appears V31MA was running in Fox mode but you
weren't in Hound mode.
So at 122930 he sent you RR73 and he was done with you and moved on.
Everything past that is him talking to somebody else as your call never shows
up again in his tranmissions.
de Mike W9MDB
122830
Seems it's not possible to turn off 77-bit messages when Hound is selected?As
soon as I save it and come back in they're checked again.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Small omission in the RC3 online docs
--config
and
wsjtx --config FT8
wsjtx -c Echo
Should be--config=
wsjtx --config=FT8
wsjtx -c Echo
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Special callsigns don't work in RC3known limitation.
de Mike W9MDB
On Thursday, October 18, 2018, 9:43:26 AM CDT, Attila Kocis
wrote:
Hi
Using RC3 on Win10 Pro x64 v1803
CR140AA calling CQ in 77 bit mode.
My Settings: 77bit tx and rx checked.
When I try to
t; || r.toInt()==73 || "RR73" == r) {
if(ui->tabWidget->currentIndex()==1) {
gen_msg = 5;
if (ui->rbGenMsg->isChecked ()) m_ntx=7;
On Thursday, October 18, 2018, 8:16:46 AM CDT, Joe Taylor
wrote:
Mike --
On 10/17/2018 5:22
Already answered...solution here.
https://sourceforge.net/p/wsjt/mailman/message/36443778/
de Mike W9MDB
On Thursday, October 18, 2018, 1:29:04 AM CDT, David Kjellquist
wrote:
Loaded up rc3
I'm getting an error window on startup Error Loading LOTW user
data Too many
Was working a QSO...logged him during the 73 being sent from me.He came back
with another RRR and the autosequence then sent R+00 instead of 73. Had to
turn off autoseq to finish the QSO.
This is another example of why we need to relax the sequencing with the patch I
provided before.
de Mike
Please ignore thisclicked the wrong button.Mike
On Wednesday, October 17, 2018, 4:11:25 PM CDT, Black Michael via
wsjt-devel wrote:
That path is only taken if the file does not exist or forced_fetcth is true.
On Wednesday, October 17, 2018, 11:38:56 AM CDT, Bill
That path is only taken if the file does not exist or forced_fetcth is true.
On Wednesday, October 17, 2018, 11:38:56 AM CDT, Bill Somerville
wrote:
On 17/10/2018 17:29, Black Michael via wsjt-devel wrote:
Problem is likely related to the fact that redirect_count only gets
You sure it worked? This is what I get in the lotw.csv file
301 Moved Permanently
Moved Permanently
The document has moved https://lotw.arrl.org/lotw-user-activity.csv;
>here.
de Mike W9MDB
On Wednesday, October 17, 2018, 3:49:22 PM CDT, David Tiller
wrote:
> LOTW and EQSL
That package works here. Hopefully nothing else breaks.
de Mike W9MDB
On Wednesday, October 17, 2018, 2:31:41 PM CDT, Bill Somerville
wrote:
On 17/10/2018 18:23, Bill Somerville wrote:
Open a Command prompt window (*not* Administrator mode),
type the following command at
is the solution besides copying the dlls into the wsjtx\bin directory?
Sure can't put the dlls in the system path.
de Mike W9MDB
On Wednesday, October 17, 2018, 2:09:35 PM CDT, Bill Somerville
wrote:
On 17/10/2018 19:59, Black Michael via wsjt-devel wrote:
> If you're still gett
If you're still getting the redirect error copy these two files into
\wsjt\wsjtx\bin and the problem should be solved.
libeay32.dllssleay32.dll
de Mike W9MDB
On Wednesday, October 17, 2018, 1:57:38 PM CDT, John Zantek
wrote:
Where libeay32.dll
C:\Program Files (x86)\Intel\iCLS
Yup...you're right...both are needed. I didn't test the Fetch after it
downloaded successfully the 1st time.
Mike
On Wednesday, October 17, 2018, 1:08:36 PM CDT, Bill Somerville
wrote:
On 17/10/2018 18:59, Black Michael via wsjt-devel wrote:
> I copied the most current libea
Bingo...you got it Bill.That's why I only saw the error once. First time I
started WSJT-X from the end of the installation and that's when I got the
error. After that I was doing it from a JTSDK prompt so was getting
libeay32.dll from the path in there.
In Windows 10 cmd prompt no path is
, October 17, 2018, 11:38:56 AM CDT, Bill Somerville
wrote:
On 17/10/2018 17:29, Black Michael via wsjt-devel wrote:
Problem is likely related to the fact that redirect_count only gets reset to
zero if the file does not exist or forced_fetch==true
Should be reset on every attempt
JJ
wrote:
Nothing there. What is the filename? I'll search my drive to see if I can
find it elsewhere.
On Wed, Oct 17, 2018 at 11:34 AM Black Michael via wsjt-devel
wrote:
RC3 now downloads the file automatically if it doesn't exist.It puts the file
in the same location as your
I saw it just the once on Windows 10. Tried deleting the file and cannot
recreate the error.Not sure if the file would have been there when I started
RC3 the 1st time.
de Mike W9MDB
On Wednesday, October 17, 2018, 10:58:16 AM CDT, Bill Somerville
wrote:
On 17/10/2018 16:51,
RC3 now downloads the file automatically if it doesn't exist.It puts the file
in the same location as your WSTJ-X.ini file.File/Open log directory
de Mike W9MDB
On Wednesday, October 17, 2018, 11:29:03 AM CDT, WB5JJJ
wrote:
Without the LoTW downloaded file, all users are in black.
Problem is likely related to the fact that redirect_count only gets reset to
zero if the file does not exist or forced_fetch==true
Should be reset on every attempt.
if (!QFileInfo::exists (csv_file_name) || forced_fetch) {
current_url_.setUrl (url);redirect_count_ = 0;
Somerville wrote:
On 17/10/2018 16:05, Black Michael via wsjt-devel wrote:
> FYI...got an error about "too may redirects" on the lotw download on
> first run. Still ran after that so definitely not fatal.
>
> A 2nd startup didn't produce the error. Deleted the lotw file an
Try a reboot and see if that fixes it...could be a cache problem.
de Mike W9MDB
On Wednesday, October 17, 2018, 10:18:59 AM CDT, WB5JJJ
wrote:
Get this error on each start up of RC3 as well.
On Wed, Oct 17, 2018 at 10:11 AM Black Michael via wsjt-devel
wrote:
FYI...got an error
FYI...got an error about "too may redirects" on the lotw download on first run.
Still ran after that so definitely not fatal.
A 2nd startup didn't produce the error. Deleted the lotw file and ran again
and did not get the error and the download was succesful.
So perhaps just a transient error.
2018 at 2:39 PM Gary McDuffie wrote:
> On Oct 15, 2018, at 11:22, Black Michael via wsjt-devel
> wrote:
>
> Maybe we have a different opinion of the path-of-least-resistance here.
Personally, I often double click a line just to have the callsign looked up and
get the grid, whether
wrote:
On 15/10/2018 17:59, Black Michael via wsjt-devel wrote:
> I never tailend a QSO that way...working them split is the way to go.
Hi Mike,
working split and tail-ending are orthogonal, in fact doing both should
be best practice for efficient tail-ending, isn't this a key reason
know about everybody else but 100% of my cases when I double-click such
an entry I have to turn off Enable Tx as that's not the behavior I want.
Mike
On Monday, October 15, 2018, 11:39:34 AM CDT, Bill Somerville
wrote:
On 15/10/2018 17:07, Black Michael via wsjt-devel wrote
Many times need to double-click somebody sending another RRR or 73.
I think we can relax the QSO sequencing such that double-clicking on a message
with a different dxcall can select the correct responding message.I've been
running this for a couple weeks and it seems to behave quite nicely. So
mented for it. I am working on the 847 one though. MikeOn
Thursday, October 11, 2018, 5:44:36 PM CDT, Bill Pence
wrote: Would this also work for ft847 early serial that also have 1way cat
communicatio no s?Maybe be a short how to...
On Thu, Oct 11, 2018, 6:35 PM Black Michael via wsjt-d
11, 2018, 5:44:36 PM CDT, Bill Pence
wrote: Would this also work for ft847 early serial that also have 1way cat
communicatio no s?Maybe be a short how to...
On Thu, Oct 11, 2018, 6:35 PM Black Michael via wsjt-devel
wrote:
Quick fix is to add the hamlib_settings.json file in the same place
wrote:
Nonot implemented for it. I am working on the 847 one though. MikeOn
Thursday, October 11, 2018, 5:44:36 PM CDT, Bill Pence
wrote: Would this also work for ft847 early serial that also have 1way cat
communicatio no s?Maybe be a short how to...
On Thu, Oct 11, 2018, 6:35
PM Black Michael via wsjt-devel
wrote:
Quick fix is to add the hamlib_settings.json file in the same place as your
WSJT-X.ini file with the following lines in it
{
"config": {
"fakefreq": "1"
}
}It looks like the real get_freq was never implemen
Yaesu FT-840 - it can receive CAT
commands, but does not report anything back.
Karl Heinz - K5KHK
On Mon, Oct 8, 2018 at 10:44 AM Black Michael via wsjt-devel
wrote:
What version of WSJT-X are you using right now?
Looks like we need a new rig entry for the earlier serial #'s and I can build
you
What version of WSJT-X are you using right now?
Looks like we need a new rig entry for the earlier serial #'s and I can build
you one for testing.
de Mike W9MDB
On Monday, October 8, 2018, 9:34:22 AM CDT, Shane Stroud
wrote:
I have discovered that the early serial numbered models
until it happens again.
Thanks for response Steve.
MIke
On Thursday, October 4, 2018, 4:40:35 PM CDT, Steven Franke via wsjt-devel
wrote:
Mike,
On Oct 3, 2018, at 9:26 AM, Black Michael via wsjt-devel
wrote:
Having a problem with transmit signals behaving badly when 12dB down
You probably won't notice it at 1-3W. I also have an ANAN 100 and use Voice
Banana as Muzychenko had too many dropouts.
If you set WSJT-X at -12dB and adjust your PA settings to get something more
like 100W you should see the power gradually increase over a few seconds.
de Mike W9MDB
build up to full power. This only
happens on the initial key up after changing bands. After that it's full power
at PTT.
Thought it just might be a characteristic of the IC-7610, so I didn't give it
too much thought.
George
On Wed, Oct 3, 2018 at 9:33 AM Black Michael via wsjt-devel
wro
Having a problem with transmit signals behaving badly when 12dB down or more on
RC2. The behavior I see is my output power gradually rises over about 3
seconds and that's what started my investigation. If above 12dB no
problem...power is spot on when PTT is asserted...but this is just a
Known bug
For now disable "Show DXCC, grid, and worked-before status".
de Mike W9MDB
On Saturday, September 29, 2018, 1:54:20 AM CDT, Fernando Martinez
wrote:
I'm user of WSJT-X and JTAlert for more than 1 year. I'have worked with wsjt-x
2.0.0 rc1 during some days with
FYI...doesn't crash on RC2 on WIndows 10.
de Mike W9MDB
On Friday, September 28, 2018, 9:39:48 AM CDT, jarmo wrote:
Fri, 28 Sep 2018 12:07:40 +0100
Bill Somerville kirjoitti:
> you should be able to replay the .WAV files and determine which
> period causes he issue. Set the
All signal reports came up with -13/-02 when logged.
What's the intent for the signal reports to be logged?
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
I'm using RC2 with FLRIg 1.3.41.27 without any problems using the FLRig
interface in the WSJT-X radio selection.
On Wednesday, September 26, 2018, 3:06:08 PM CDT, Bill Somerville
wrote:
On 26/09/2018 20:56, IZ3XNJ Stefano Comelli wrote:
> Hi... I am the only one having troubles
I submitted this before but since it's not in RC2 here it is again.
Need to turn off transmit before we reset power after Tune otherwise can get a
power spike at the end of Tune.
else { // we're turning off so remember our Tune pwr setting and reset to Tx
pwrif
Turn off Settings/General/Show DXCC, and worked-before status
de Mike W9MDB
On Wednesday, September 26, 2018, 12:12:18 PM CDT, Jesús Gutiérrez
Rodríguez wrote:
Good afternoon, I am observing that the revision rc2, decoding in 77 bits
(14078), the JTAlert X program, does not
Ahh yes...that was it. Thanks Laurie.I basically turned off all the colors and
didn't notice the LOTW example blanked out too.
Mie
On Tuesday, September 25, 2018, 5:33:28 PM CDT, Laurie, VK3AMA
<_vk3a...@vkdxer.net> wrote:
On 26/09/2018 8:17 AM, Black Michael via wsjt-devel
, Sep 25, 2018 at 2:25 PM Bill Barrett wrote:
Hello Mike;Seems to be an issue on Windows 7Pro.Doubled checked on several
times.
BillW2PKY
On Tue, Sep 25, 2018 at 4:47 PM Black Michael via wsjt-devel
wrote:
Nope...works fine here on WIndows 10.
de Mike W9MDB
On Tuesday, September 25
Nope...works fine here on WIndows 10.
de Mike W9MDB
On Tuesday, September 25, 2018, 3:34:14 PM CDT, Gene H
wrote:
I have seen a problem with today's release of -rc2 whereby when I click
on a valid JTAlertX callsign the information is not being received and
processed by WSJT-X
Question...Joe...you had said you were going to change the hound mode so that
they could transmit all the signals at once without losing transmit power per
signal.
Has that change been implemented in RC1?
de Mike W9MDB
___
wsjt-devel mailing list
ran) it flags a much smaller fraction of all
messages, this way.
-- Joe, K1JT
On 9/20/2018 4:55 PM, Black Michael via wsjt-devel wrote:
> Is this logic backwards here??? Seems we don't want the "not" here.
>
> In displaytext.cpp
>
> if(call2.size()>0 a
Is this logic backwards here??? Seems we don't want the "not" here.
In displaytext.cpp
if(call2.size()>0 and !m_LoTW.contains(call2)) {
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
You should be able to do it by setting up a new port in PowerSDR under the CAT
control for PTT Control RTS or DTR.Then pick that COM port and method in WSJT-X
Radio setup.
de Mike W9MDB
On Wednesday, September 19, 2018, 1:44:57 PM CDT, Frank Kirschner
wrote:
I am slowly getting
I know compound calls aren't supported in the 2.0 version for the 75-bit
messages...but
If you put a compound call in the DX Call box (like from double-clicking) and
generate std msgsthen remove the compound from the call and generate again
all the TX boxes get changed except TX 5 which
Did you put a callsign in the DX Call box? And did you reset your frequencies
so that 14.078 is a valid choice?
Enable TX is working for me with that exact same setup.
de Mike W9MDB
On Monday, September 17, 2018, 2:41:35 PM CDT, John Zantek
wrote:
Immediately, I'm drawn to test the
This patch does fix the problem correctlyand turns out the
on_monitorButton_clicked isn't needed.
@@ -5917,6 +5920,7 @@
}
}
else { // we're turning off so remember our Tune pwr setting and reset to Tx
pwr
+ stopTx(); // ensure rig stops tx before we change power as tuning is
Scratch that patchit messes up the memory for tuningtI'll fix it.
Mike
On Thursday, September 13, 2018, 2:30:14 PM CDT, Black Michael
wrote:
The order of operation for adjusting the tuning power back to operational
power needs to change.It was causing a potential power
The order of operation for adjusting the tuning power back to operational power
needs to change.It was causing a potential power spike for about 10-20ms before
tuning was actually turned off.So simply move it ahead of the power
adjustment.Tuning should most always be less than operationalso
Wsjtx doesn't do awards at all. Mike
Sent from Yahoo Mail on Android
On Tue, Sep 11, 2018 at 3:41 PM, Pietro Paolo Pirrone
wrote: ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
and how, to handle
in the data transfer.
Many thanks.
Piero
Il giorno mar 11 set 2018 alle ore 21:33 Black Michael via wsjt-devel
ha scritto:
You could just use the N1MM ADIF record sent from WSJT-X via TCP.
de Mike W9MDB
On Tuesday, September 11, 2018, 2:26:01 PM CDT, Pietro Paolo
You could just use the N1MM ADIF record sent from WSJT-X via TCP.
de Mike W9MDB
On Tuesday, September 11, 2018, 2:26:01 PM CDT, Pietro Paolo Pirrone
wrote:
Hi everyone,
this is Piero, IK1TZO, coauthor of EasyLog, a logging program born in the far
1989.
Me and my brother Franco
> On Aug 27, 2018, at 1:53 PM, Black Michael via wsjt-devel
> wrote:
>
> You've got "Fake It" checked so the rig will change by 500Hz for every 500Hz
> below 1500 or above 2000.
>
> I'd recommend you change to "Rig" for split and it will use VFOB on spl
Not a typoincludes the file as requested. I guess you're thinking it
should be "common.h" but that's just a matter of coder preference.
de Mike W9MDB
On Friday, August 24, 2018, 5:10:14 AM CDT, Alessandro Gorobey via
wsjt-devel wrote:
Hi All,
I noticed that in mainwindow.h
Chris - N3PLM
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Tuesday, August 7, 2018 9:38 AM
To: wsjt-devel@lists.sourceforge.net
Cc: Black Michael
Subject: Re: [wsjt-devel] no decode
Hmmm hamspots.net doesn't show any transmissions from you for t
Don't know how WSJT-X is being built for the Linux crowd but perhaps we should
mitigate anyways by adding the recommend line so the relocation tables are
retained just-in-case? The only mingw build I'm familiar with is mingw-32 for
hamlib.
https://www.kb.cert.org/vuls/id/307144
de Mike W9MDB
Hmmm hamspots.net doesn't show any transmissions from you for the last 16 hours
so you may not be transmitting as you think.
You say your time is good but what does http://time.is tell you?
de Mike W9MDB
On Tuesday, August 7, 2018, 8:21:08 AM CDT, seaka...@juno.com
wrote:
I've
the new time.
Would it be possible to display the total created offset in your tool and have
a button to undo the offset?
73,Ton pa0tbr
On 5 August 2018 at 19:38, Black Michael via wsjt-devel
wrote:
Version 1.2 on my QRZ page fixed the ctrl-click problem.
de Mike W9MDB
On Sunday, August 5, 2
Version 1.2 on my QRZ page fixed the ctrl-click problem.
de Mike W9MDB
On Sunday, August 5, 2018, 12:10:45 PM CDT, Brian G3VGZ
wrote:
Alt click doesn't seem to work here. only way to reverse seems to be add a -
in front of the number.
Black Michael via wsjt-devel wrote:
> I
Oops...you're right...typo in the codeI'll get a new version 1.2 out as
soon as I can.
Mike
On Sunday, August 5, 2018, 12:10:45 PM CDT, Brian G3VGZ
wrote:
Alt click doesn't seem to work here. only way to reverse seems to be add a -
in front of the number.
Black Michael via
of the number.
Black Michael via wsjt-devel wrote:
> I did limit it to 0.5 seconds -- but you can keep on clicking the button
> to do it multiple times.
>
> Tell ya' what...I've just uploaded a new version to my QRZ page and
> expanded it to allow 10 seconds. Also you can Ctrl-Click
FYI...was trying to chase this down and noticed that sending output the speaker
and capturing that the problem disappeared...would reappear on the virtual
cable (VB-Cable).Rebooted and the problem disappeared on VB-Cable too.
But...also noticed this in the code which perhaps somebody should
Black Michael via wsjt-devel wrote:
Noticed that an FT8 (or JT9 or JT65) signal starts out at a level noticeably
above the average power level when a high power on the slider.
Is there a reason for this? Seems like this could overdrive some rigs
running at max power already. Only noticeabl
The main solution was turning on HRD logging :-)
Other things had to do with audio settings for operations, wide graph settings,
and such.
de Mike W9MDB
On Thursday, August 2, 2018, 4:53:13 PM CDT, Frank Kirschner
wrote:
There were a bunch of settings that needed attention that I
Noticed that an FT8 (or JT9 or JT65) signal starts out at a level noticeably
above the average power level when a high power on the slider.
Is there a reason for this? Seems like this could overdrive some rigs running
at max power already.Only noticeable when WSJT-X level is above -3.4dB and
901 - 1000 of 1443 matches
Mail list logo
