Finally home but dropbox file is not there anymore
-Original Message-
From: James Shaver (N2ADV) [mailto:n2...@windstream.net]
Sent: Friday, April 08, 2016 9:27 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Rig control issue v6596
Will do when I get home
73,
Jim S.
N2ADV
Hi All - running R8033 I ran into an oddity with the auto sequence.
While I was working a station on 30 meters, we exchanged reports, I sent
an RRR and suddenly another station who must have been working someone
on the exact same frequency (propagation change) sent 73 to another
station he
I'm having the same issue using Windows 7 Home Premium where I've had to
end the process and reopen WSJT-X to get it to work again. I'm not using
the TS-2000 emulation, I'm using the current recommended settings for
WSJT-X and the Flex 6XXX series in the radio settings.
On 9/16/2017 10:12
I see it even though I'm using the Flex 6XXX setting (and I make sure
that JTAlert is not running just to be sure)
On 9/16/2017 3:01 PM, Bill Barrett wrote:
Hello Bill-
Recently switched over to the FLEX Radio 6XXX driver and I don't think
I have observed the orphaned processes since then.
Drop me a note, George, we can find a semi-empty corner of a band :)
Jim S.
N2ADV
On 9/21/2017 4:05 PM, Joe Taylor wrote:
Hi George,
On 9/21/2017 3:56 PM, George J Molnar wrote:
Joe, would absolutely not remove sh - it’s incredibly useful. My
intention was to say the term should be written
I was running 8101 as well, George.
Jim S.
N2ADV
On 9/22/2017 1:19 PM, George J Molnar wrote:
Same experience last night with N2ADV on FT8. I called him in contest
mode, which did not seem to advance the sequence. When I switched back
to “normal,” the sequence progressed.
My version 8101.
I use the entirety of the waterfall - I have yet to click the "menus"
box by accident...
Jim S.
N2ADV
On 9/11/2017 12:33 PM, DG2YCB, Uwe wrote:
Wouldn’t be a good alternative to use instead the checkbox a
right-hand click or something like that? Maybe I am the only one
having issues with
That's normal - user interaction to start another QSO is required to
prevent "QSO machines"
Jim S.
N2ADV
On 9/7/2017 7:49 PM, Rich - K1HTV wrote:
Using 1.8.0-rC2 r8069
Under Settings, General tab, under 'Behavior', the "Disable TX after
73" unchecked. However, when the Tx5 (73)
This can also be found by checking the release notes link right above
the download links on the WSJT-X homepage:
https://physics.princeton.edu/pulsar/k1jt/Release_Notes_1.8.0.txt
See you on the air.
Jim S.
N2ADV
On 9/10/2017 9:14 AM, char...@sucklingfamily.free-online.co.uk wrote:
Hi
It took a bit of a higher-than-usual concentration of caffeine for me to
snap into it but after that, I have begun to really like it.
Jim S.
N2ADV
On 9/28/2017 2:12 PM, Ron Gibson wrote:
Hi Joe,
I for one have adapted to the "Tx frequency is not changed unless Ctrl
is held down" just fine!
Hello, Hiro-san.
The good news is that the functionality of "Lock TX=RX" is still
available thanks to the update yesterday (thanks, Joe) - the settings
now includes an option to emulate this behavior "Double-click on call
sets Tx and Rx freqs" so you should be good to go!
Jim S.
N2ADV
On
of the group or Google (JTSDK).
Jim S.
N2ADV
On 9/30/2017 7:36 PM, w...@frontier.com wrote:
Where do I get the new upload ?? made some 9200 contact with jt65 and ft8
On Saturday, September 30, 2017 2:23 PM, James Shaver
<n2...@windstream.net> wrote:
Correction: when responding to a
Yep, it's working even with directional CQ's - thanks!
Jim S.
N2ADV
On 9/30/2017 4:17 PM, George J Molnar wrote:
Looks good and works well. Think the new logic is...logical.
George J Molnar, KF2T
Nevada, USA
On Sep 30, 2017, at 3:12 PM, DXer wrote:
Jim, Joe,
Correction: when responding to a CQ via the UDP server using JTAlert,
the RX will move and the TX does not unless you hold the control key
down which may cause issues for some.
Sorry, my fingers are moving faster than my brain today, apparently.
Jim S.
N2ADV
On 9/30/2017 2:19 PM, James
Ok, restarted the machine (Win 7 Pro) and now both the TX and RX are
moving. Maybe a glitch on my end. I'll keep an eye on it.
Jim S.
N2ADV
On 9/30/2017 2:30 PM, James Shaver wrote:
Hi Vince - yes, that's what I mean. How very odd that I'm seeing
different results. I'll play around
you you mean clicking on the
callsign in JTAlert? If yes, it's working for me, that is, both Tx and
Rx move to the same frequency as the CQ calling station.
73 de Vince, VA3VF
On 2017-09-30 2:19 PM, James Shaver wrote:
Works well but when using the UDP server to respond to CQ's via
JTAlert
I just deleted the draft email I was composing literally just now about
this exact subject - I tend to operate remotely (99% of the time) While
a lot of that is done using a small laptop, I also use my iPad to
remotely control my home machine which gets me on the air otherwise I
would hardly
I just deleted the draft email I was composing literally just now about
this exact subject - I tend to operate remotely (99% of the time) While
a lot of that is done using a small laptop, I also use my iPad to
remotely control my home machine which gets me on the air otherwise I
would hardly
Thanks, Joe! Building 8144 now and will report back.
Jim S.
N2ADV
On 9/29/2017 2:01 PM, Joe Taylor wrote:
After further testing in the field, the experimental changes
introduced in r8125 and later will now become permanent.
In r8144 I have added an option to enforce simplex operation (thus
Just tested - works great running my shack PC remotely from my iPad.
Jim S.
N2ADV
On 9/29/2017 2:01 PM, Joe Taylor wrote:
After further testing in the field, the experimental changes
introduced in r8125 and later will now become permanent.
In r8144 I have added an option to enforce simplex
Auto sequence was implemented with FT8 because of the tight timeframes
required to determine which part of the sequence to follow next. There
is no such need with JT65 and JT9.
Jim S.
N2ADV
On 9/29/2017 3:09 PM, Pino Zollo wrote:
Please,
Add autosequence also to JT65/JT9 modes
With
is TX
frequency (it was Madeira Islands so he had a decent pileup on his
frequency and wasn't able to decode me). I had to quickly uncheck the
box in the settings and send a 73 where I was before.
Jim S.
N2ADV
On 9/29/2017 2:51 PM, James Shaver wrote:
Just tested - works great running m
This has been discussed before - the answer is no otherwise the ability
to compile packages may be taken away entirely.
On 8/26/2017 7:21 PM, Steve Nance wrote:
I would like to have access to later code than rc1 7843, but don't
want to install all the dev stuff required to compile the
This was done early on to make sure people followed the sequence - if
someone decided to get creative and skip a step, the software is smart
enough to get them back on track. Not sure why skipping the grid and
saving 15 seconds is so desired.
Jim S.
N2ADV
On 9/1/2017 8:19 AM, Erik -
Completely agree, Joe.
I operate with the waterfall “off” 99% of the time and don’t have any issues
people are talking about. The only time I turn the waterfall “on” is to
visually locate an empty place to call CQ so I don’t call CQ over someone
already on a spot. Folks appear to be
It wasn't "too long ago" when the spark people grumbled about CW. Then the
CW people grumbled about AM Phone. Then the AM Phone people grumbled about
SSB.
If you don't like it, don't do it - stick with CW and SSB, they aren't going
away anytime soon and a good number of us here enjoy those
Is there some reason you’re using RC3 and not the latest version? I’d
recommend going that path first.
Jim S.
N2ADV
From: Unni Tharakkal [mailto:unnitharak...@gmail.com]
Sent: Saturday, November 18, 2017 7:05 AM
To: WSJT software development
Subject: [wsjt-devel] WSJTx ver 1.8-rc3
Is there some reason you’re using RC3 and not the latest version? I’d
recommend going that path first.
Jim S.
N2ADV
From: Unni Tharakkal [mailto:unnitharak...@gmail.com]
Sent: Saturday, November 18, 2017 7:05 AM
To: WSJT software development
Subject: [wsjt-devel] WSJTx ver 1.8-rc3
It was on my list of things to do in between vomiting children (the stomach bug
is being tossed around between my little ones like a baseball).
Jim S.
N2ADV
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, November 9, 2017 12:21 AM
To: WSJT
I announced in the FB group because I think this is pretty cool J
(that’s what I meant in my earlier note – I need to remember coffee first, THEN
email J )
From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, November 9, 2017 12:21 AM
To: WSJT
There are several people who have outright said they refuse to use 1.9.1 (or
WSJTX in general) and/or that they refuse to use DXPedition Mode because they
“don’t agree with being forced to use it.” I’m willing to bet some of the
people causing QRM fall into that category, as well, for some odd
I’ve literally only heard them with FT8 (still haven’t gotten them in the log
because I could only hear them for about an hour on 20 and an hour on 30 at -20
and below) – I’ve heard the pileup for CW and SSB but can’t hear Baker at all.
If that trend continues, my ONLY chance of getting them
When I am sitting in a park or out on a snowmobile trail with my KX3 and my
laptop using a GPS for time sync since there’s no cell reception there,
anything that relies on the Internet will be basically useless to me. Why
would we aim to exclude a growing number of such users like me? Perhaps
Yes but my previous question about Internet usage still stands: When I am
sitting in a park or out on a snowmobile trail with my KX3 and my laptop using
a GPS for time sync since there’s no cell reception there, anything that relies
on the Internet will be basically useless to me. Why would we
, 2018, at 6:38 PM, James Shaver wrote:
Yes but my previous question about Internet usage still stands: When I am
sitting in a park or out on a snowmobile trail with my KX3 and my laptop using
a GPS for time sync since there’s no cell reception there, anything that relies
on the Internet
Agreed. I’m baffled as to how such a comparison could even be attempted.
Honestly, the comparison is more like apples to dairy cattle.
People can (and do) operate without using a DX Spotting network and get along
just fine. Other than a DX Cluster being used to possibly know who the DX
Joe, can we use the 1.7.1 dev branch on air? I've been building along the
1.8.1 branch instead because of an earlier note you had out there.
Thanks!
Jim S.
N2ADV
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Tuesday, January 23, 2018 9:57 AM
To: WSJT
Thanks, Bill!
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Tuesday, January 23, 2018 10:11 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X issue with Dark QT themes
On 23/01/2018 15:01, James Shaver wrote:
> Joe, can we
Is there a reason TY7C chose a well known PSK watering hole for this "test"?
That probably made the PSK users quite angry...
Jim S.
N2ADV
-Original Message-
From: jarmo [mailto:oh1...@nic.fi]
Sent: Monday, March 12, 2018 4:39 AM
To: WSJT software development
Subject: [wsjt-devel] FT8
[mailto:oh1...@nic.fi]
Sent: Wednesday, March 14, 2018 7:24 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] DXpedition mode: dissapointed somehow
Wed, 14 Mar 2018 06:24:30 -0400
"James Shaver (N2ADV)" <n2...@windstream.net> kirjoitti:
> TY7C should not h
Somerville [mailto:g4...@classdesign.com]
Sent: Wednesday, March 14, 2018 8:13 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] DXpedition mode: dissapointed somehow
On 14/03/2018 10:24, James Shaver (N2ADV) wrote:
> TY7C should not have even been using DXPedition Mode.
Hi Jim,
wh
It took me a few days to get it the way I wanted it but I like it way better.
Jim S.
N2ADV
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Wednesday, March 7, 2018 11:27 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] WSJT-X 1.9.0 rc2
stand this behavior. It means that, in most cases, you
should not just leave your rig on and monitoring the DX after you have stopped
paying attention, as you could be in for a surprise when your rig springs to
life and starts TXing.
Steve K9AN
> On Mar 7, 2018, at 10:05 AM, James Shaver <n2...@win
Yep, twice the timer had expired on me right as the “Fox” called me and I had
to scramble.
Jim S.
N2ADV
From: Bill Turner via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Wednesday, March 7, 2018 11:03 AM
To: WSJT Software Development
Cc: Bill Turner
Subject: [wsjt-devel]
software development
Subject: Re: [wsjt-devel] Timer
Jim --
I don't think you had to scramble. If Fox calls you, your Tx3 message will be
sent (somewhere in 300-900 Hz), even if Tx Enable is not engaged.
-- Joe
On 3/7/2018 11:05 AM, James Shaver wrote:
> Yep, twice the timer
Unfortunately, they’re using the DXPedition mode on the “normal” 15 meter
frequency and ops are inadvertently stomping all over several QSO’s in
progress. I witnessed several busted contacts and had a few myself as a
result.
From: Ray Jacobs [mailto:rjacobs...@verizon.net]
Sent:
And the “normal” 17 meter frequency as well with the same results…
From: James Shaver [mailto:n2...@windstream.net]
Sent: Wednesday, March 21, 2018 5:59 PM
To: 'WSJT software development'
Subject: RE: [wsjt-devel] Split mode ft 8
Unfortunately, they’re using the DXPedition mode
Hey Jim – happy to post it there if someone has it handy to provide.
Jim S.
N2ADV
From: W4TMO via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Thursday, March 22, 2018 8:44 PM
To: WSJT software development; Richard Stanley
Cc: W4TMO
Subject: Re: [wsjt-devel] Ft 8 in
It also might not be a bad thing if some well-meaning but otherwise
uninformed ops running 1.8 wander into the "pileup" as it may help simulate
real-world conditions where this may also happen with more frequency.
Though they may not decode the "fox" I've seen any number of times where
people will
This is people using JT65HF Image Controller. Google “easypal” - not my cup of
tea and I think it’s silly but different strokes...
> On Oct 19, 2018, at 7:08 PM, wrote:
>
> I’m running RC#3 and I’m seeing this for the first time. Not sure if it is
> unique to Ver 3.0 or just something ‘ve
Yes, please. The whole “what constitutes a QSO” has been beaten to a bloody
pulp -
The search function will uncover plenty on the subject from all sides.
Jim S.
N2ADV
> On Oct 15, 2018, at 7:47 PM, Gary wrote:
>
> End this NOW or I will drop off of this list.
>
> Gary - W9BS
>
>
>
Just create a different profile for DXPedition Mode use only. Details on that
are in the manual.
Jim S.
N2ADV
> On Oct 31, 2018, at 7:34 AM, Pino Zollo wrote:
>
> Hi,
>
> Having used F/H DXpedition mode a few times I feel the need to have two
> frequencies listsone for the normal
They’re running knock off software that bastardizes the F/H code. All they’re
doing is causing confusion instead.
> On Nov 8, 2018, at 4:25 PM, Pino Zollo wrote:
>
> Wasn't it disabled on standard frequencies ?
>
> 73 ZP4KFX
>
> 212100 Tx 752 ~ KH2F ZP4KFX GG14
> 212045 -13 0.1 2493 ~
If you do a search of the group, a number of people REQUESTED the functionality
that was added to the ESC key. So far, it’s come in extremely handy for myself
and a number of others with whom I’ve spoken.
Jim S.
N2ADV
> On Nov 15, 2018, at 5:24 PM, George Hall wrote:
>
> Greetings
I tried a search but came up dry on this particular issue with this level of
detail: using FT8 when calling CQ, if I switch from TX6 to TX5 to send FFT
(such as “QRM PSE AGN?” or “SRI NO DECODE”) and then for the next cycle I
return to TX6 to return to calling CQ, if I get a decode in any
Doing ok for me. Made several contacts on 20 meters with no issues that we’re
not operator error. :)
Jim S
N2ADV
> On Nov 13, 2018, at 2:01 PM, John Kludt wrote:
>
> Folks,
>
> Likewise here, loaded right up, making Q's above 2000 Hz no issues to report.
>
> John K4SQC
>
>> On Tue, Nov
>From Joe’s post yesterday about known bugs:
“1. If a message's first callsign contains only characters 0-9 and A-F it
will be interpreted as a hexadecimal number. The message will be
transmitted and decoded as if the first callsign were telemetry data;
the remaining parts are lost.
Lock TX and RX was removed back in the evolution of 1.8 (RC2 if memory serves).
Jim S.
N2ADV
From: Edfel Rivera [mailto:edfelj...@gmail.com]
Sent: Wednesday, September 19, 2018 12:26 PM
To: WSJT software development
Subject: [wsjt-devel] WSJTX 2 RC1 - Feedback and Question
Hi:
Can someone please block this user? This is the 5th blank note from this
person.
> On Sep 25, 2018, at 6:25 AM, Анатолий wrote:
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
>
Please stop sending empty messages to the dev list.
> On Sep 23, 2018, at 11:15 AM, Анатолий wrote:
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Had that other ham read the documentation that goes along with the DXPedition
Mode, he would realize that for “Hounds,” the transmit cycles is automatically
disabled after a few cycles no matter what the operator selects as options.
Jim S.
N2ADV
> On Sep 22, 2018, at 8:42 PM, DeYoung James
Nope it can be done post install of 2.0 without issues.
Jim S.
N2ADV
> On Dec 11, 2018, at 10:26 PM, R SCHMAHL wrote:
>
> The fix for the LotW error: Does that have to be done before you download Ver
> 2.0 or can it be done after download? I upgraded to ver2.0 and ignored all
> warnings
We are free to use these different modes anywhere the band plans allow them.
The major issue is that there are still users of the other modes that “live” in
those areas about which you speak. For example, there are quite a few
experimenters still using JT65 using QRPP levels who may not be
Take a peek at the quick start guide as well as the large splash screen that
comes up when you open RC5…
(you’ll find there that RC4 and RC5 are not backwards compatible with the older
versions).
Jim S.
N2ADV
From: w...@frontier.com [mailto:w...@frontier.com]
Sent: Friday,
Brian, it appears you don't understand email reflectors vs email lists.
There has never been an expectation that anyone read all the emails that
come via the reflector.
There is a search function right on the Dev List page that anyone who is
reporting bugs should check first to see if what
Bob, repeated (read: CONSTANT) feedback about things like non standard call
signs not being compatible with the “older” version of the FT8 Protocol among
other things as well as the demand to use FT8 in things like Field Day or
contests is driving it. In short, this is what the users have been
The other person needs to check to see if NA Contest Mode is selected in the
menu.
From: m...@handgunrepairshop.com [mailto:m...@handgunrepairshop.com]
Sent: Sunday, November 18, 2018 7:30 PM
To: 'WSJT software development'
Subject: [wsjt-devel] RC4 Unexpected Behavior of RR73
As
Anything so new is going to flag on a lot of anti-virus programs.
Us end-users need to be on our toes because we are still smarter than our
machines (for now).
:)
Jim S.
N2ADV
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, September 17, 2018
First thing I noticed was that when using the "RR73" in TX4 on 7.078 using
2.0, I haven't once had to repeat that part of the sequence in a couple
dozen contacts. What a remarkable difference!
Jim S.
N2ADV
-Original Message-
From: Joe Taylor [mailto:j...@princeton.edu]
Sent: Monday,
Add me to that list. Well said, as always, Bill.
Jim S.
N2ADV
> On Mar 31, 2019, at 2:11 PM, Bobby Chandler wrote:
>
> Bravo Bill! I agree 100%.
>
> Bobby/N4AU
>
> From: Bill Somerville
> Sent: Sunday, March 31, 2019 11:53 AM
> To: wsjt-devel@lists.sourceforge.net
> Subject: Re:
I’ve experienced this since 1.7 but it’s not consistently reproducible.
> On Apr 5, 2019, at 7:15 AM, Darren Freeman
> wrote:
>
> Hi all,
>
> I believe I found a bug, but sadly I can't reproduce it now that I've
> restarted the application. It was happening consistently at the time.
>
>
Ha! I have experienced this so often lol
> On Apr 1, 2019, at 12:27 PM, George J Molnar wrote:
>
> KF6E has spilled the beans! The secret “whine mode” feature in WSJT-X has
> been revealed. On April 1st, of all days.
>
> Whine mode is exotic code that scans the operator’s brainwaves for
The auto sequence is an operator assistance tool, not an operator replacement
tool - as the control operator it’s a good idea to closely watch the exchange
and be ready to change on the fly if the other operator acts unpredictability.
The auto sequence can’t do everything...
> On Mar 1, 2019,
Double clicking on TX1 will skip the grid. This is useful when band conditions
are unstable. Grid is optional anyhow and not useful for much other than
turning your antenna toward the station.
More info on skipping TX1 is available in the user manual (press F1).
Jim S.
N2ADV
> On Apr 9,
A quick press of F4 clears the call. Retention of the call between band changes
is useful if you’re chasing a DXPedition on multiple bands.
Jim S.
N2ADV
> On Apr 12, 2019, at 10:59 AM, Svend Aage Jessen wrote:
>
> Would be nice, though not nessersary, to clear dx call also after
> exit the
This almost sounds partially like ALC Overshoot that is more of a problem with
some radios than with others (it was really nasty on a TS590 that a friend had
sent to me to test out). The pure 8-tone FSK signal does seem to make this more
obvious on some of my radios than others. Some of my
Hi Paul,
Good info (and similar to my own line of thinking in the response I just sent
on ALC Overshoot) but I’d recommend one minor change:
Your statement “The best way to avoid spikes in any rig using FT8...” - I’d be
cautious with the “any rig” generalization. Some of the popular radios
You need to click on the link at the bottom of every email from this list to
unsubscribe.
73,
Jim S.
N2ADV
> On Jun 25, 2019, at 1:58 PM, James Buffington wrote:
>
> j...@jimbuffington.com
> ___
>
> IN GOD WE TRUST
>
> "The Ultimate in
have I seen any sigs.
>
> I'll try a few CQs on 15 and 10 to see if any spots show up.
>
> 73, N0AN
> Hasan
>
>
>> On Tue, Apr 30, 2019 at 9:50 AM James Shaver wrote:
>> I watched one CW signal on 40 intentionally move until it was zero beat with
>> it
There’s already a thread on this with 50+ responses...
> On Apr 30, 2019, at 10:10 PM, Edfel Rivera wrote:
>
> --541e5a0587ca073c
> Content-Type: text/plain; charset="UTF-8"
>
> Hi:
>
> I noticed sometimes the popup window to log QSO shows OK at the left
> (expected) and sometimes
r. Let's revisit this in six months
> and see where we stand.
>
> Best regards,
>
> Gary, K7EK
>
> ---
>
>
> On Tuesday, April 30, 2019, 7:32:44 AM EDT, James Shaver
> wrote:
>
>
> 60 is never included because people don’t read before they tran
*my. Not “it”
Auto correct on iOS hates me.
> On Apr 30, 2019, at 10:47 AM, James Shaver wrote:
>
> I watched one CW signal on 40 intentionally move until it was zero beat with
> MY signal. Not a single QSO was disrupted by them. Hilariously, their
> attempt to QRM gave me g
I’m on 20 meters - After about 2-3 minutes of operating, I’m seeing the mode
getting changed back to FT8 and my frequency is jumping to 14.074. This
appears to be random (though it still shows the “FT4” configuration as being
selected). Selecting FT4 as the mode does not put me back to 14.080
Hey, Bill - thanks. See my last note re: same :)
73,
Jim S.
N2ADV (ex KD2BIP)
> On Apr 29, 2019, at 2:38 PM, Bill Somerville wrote:
>
>> On 29/04/2019 19:30, James Shaver wrote:
>> Also, I’m already seeing quite a few people that have skipped step 8 in the
>> set
Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32 bit)
machine, it won’t resolve for me unless I restart.
73,
Jim S.
N2ADV (ex KD2BIP)
> On Apr 29, 2019, at 2:49 PM, Bill Somerville wrote:
>
>> On 29/04/2019 19:38, James Shaver wrote:
>> Fol
Are you saying that the
> "Menu->Mode->FT4" button is not functioning?
>
> 73
> Bill
> G4WJS.
>
>> On 29/04/2019 19:54, James Shaver wrote:
>> Hey Bill - on my Win10 64 bit machine that works but on my Win7 Home (32
>> bit) machine, it won’t resolv
4/2019 20:05, James Shaver wrote:
>> Hey Bill - I’ll click on the mode menu, select “FT4” and the mode will
>> remain in FT8 mode until I close WSJTX down and reopen it.
>>
>> 73,
>>
>> Jim S.
>> N2ADV
>
> Hi Jim,
>
> that seems unlikely. Are you
to my below about step 8 - looks like the release email has
a slight conflict with the PDF - perhaps the PDF with the setup instructions
should be modified?
73,
Jim S.
N2ADV (ex KD2BIP)
> On Apr 29, 2019, at 2:30 PM, James Shaver wrote:
>
> I’m on 20 meters - After about 2-
I’ve been in the RR73 loop quite a bit
73,
Jim S.
N2ADV (ex KD2BIP)
> On Apr 29, 2019, at 3:07 PM, DG2YCB, Uwe wrote:
>
> Hi, just made a couple of FT4 QSOs. Works well. However, sometimes it’s
> somewhat difficult to get the QSOs completed. Endless exchange of reports but
> no 73 or RR73
I can read between the lines and I think it’s fantastic.
> On Apr 29, 2019, at 5:58 PM, Jim Nuytens via wsjt-devel
> wrote:
>
> There's always a more determined LID. ;-)
>
>> On 4/29/2019 17:29, Bill Somerville wrote:
>> Christoph,
>>
>> not disagreeing but there are reasons for this that I
One tiny CW frequency in a 3kHz passband should not be much of an issue if you
have a notch filter - try to notch it out and see if that helps.
> On Apr 29, 2019, at 7:58 PM, Rich Zwirko - K1HTV wrote:
>
> Well,
>Guess what station is on 7047 KHz, the new 40 Meter FT4 frequency and what
60 is never included because people don’t read before they transmit (I know
that’s a shocker) and were transmitting out of band or illegally because of the
vast differences between 60 meter rules.
> On Apr 30, 2019, at 7:25 AM, Christoph Berg wrote:
>
> Re: Bill Somerville 2019-04-29
>
It never ceases to amaze me how so many hams instantly jump to the conclusion
that what they witness on the air is automatically attributed to intentional
“rudeness” or ill intent.
His s/n is not really relevant - it’s very possible that even if propagation
was, to coin a phrase, putting this
For what it’s worth, I’m not seeing any difference with my 6300 and DAX/SSDR
3.0.19 between 2.0.1 and 2.1.0 RC5. ‘
Your 6600 must be defective - send it to me for, uh, proper disposal. ;).
73,
Jim S.
> On May 2, 2019, at 8:16 AM, Bill Somerville wrote:
>
>> On 02/05/2019 12:55, Al
Probably more a question for the WSJTGroup list rather than the Dev list - for
what it’s worth, there are dozens of threads on this topic there already that
are searchable. :)
73,
Jim S.
N2ADV
> On May 2, 2019, at 9:40 AM, Topher Petty wrote:
>
> I'm simply curious about one thing...
>
>
.wav files are pretty big and it may cause issues for people with limited
bandwidth internet connections who participate via email. Perhaps host the
.wav files via a third party site like SoundCloud, DropBox, or the like?
73,
Jim S.
N2ADV (ex KD2BIP)
> On May 2, 2019, at 4:27 PM, Topher
FWIW: I still use JT9 regularly using milliwatts of power for experiments and
get stomped on by JS8 constantly.
> On Apr 28, 2019, at 11:51 AM, Bill Somerville wrote:
>
>> On 28/04/2019 16:07, Richard Solomon wrote:
>> Since roll-out is imminent, have we an agreement on which
>> frequencies
At one point the controls for F/H were on the main part of the GUI and the
group was flooded with questions asking why they were receiving and
transmitting “funny” because they were inadvertently checking the box when it
was on the main page. That went away when the box was moved into the
Helps to read the PDF and the announcement fully. The answer is there.
> On Apr 22, 2019, at 5:32 PM, Enrique Scheuer
> wrote:
>
> Hello all
>
> Just coming in and also wanting to give my contribution..
>
> May I ask where to download the FT4 beta version?
>
> 73 de Enrique
> PY2CP
>
Double clicking on TX1 skips sending the grid. This is done to maximize QSO
completion rates during short openings. Grid is entirely optional and
superfluous on HF.
More info is available in the user manual on this function.
Jim S.
N2ADV
> On Apr 10, 2019, at 2:13 PM, Timothy Hickman
>
1 - 100 of 164 matches
Mail list logo