On 28/03/2018 19:42, Joe Taylor wrote:
On 3/28/2018 11:17 AM, K0TNT wrote:
Setup:
Program version: WSJT-X v1.90-rc3
Rig: Flex 3000 with Gateway dual core processor computer running
Windows 10 Home 64 bit. 8 GB ram, 2.2 GHz, plenty of disk space.
Issue 1: Can't be the WSJT program to work
On 28/03/2018 20:11, Black Michael via wsjt-devel wrote:
Disable the greying out of "Monitor returns to last used frequency"
for the "None" rig entry.
https://www.dropbox.com/s/ivkbi3dm7cb7yeu/lastmon.patch?dl=1
I can see why this was put in...but it prevents some logical
operations when not
Disable the greying out of "Monitor returns to last used frequency" for the
"None" rig entry.
https://www.dropbox.com/s/ivkbi3dm7cb7yeu/lastmon.patch?dl=1
I can see why this was put in...but it prevents some logical operations when
not using CAT control.
de Mike W9MDB
Agreed on all counts, Gary.
73, N0AN
Hasan
On Wed, Mar 28, 2018 at 1:21 PM, Gary McDuffie wrote:
>
>
> > On Mar 28, 2018, at 5:48 AM, Hasan al-Basri
> wrote:
> >
> > Running DXp by the developers for testing and evaluation is justifiable.
>
Hi Carl,
On 3/28/2018 11:17 AM, K0TNT wrote:
Setup:
Program version: WSJT-X v1.90-rc3
Rig: Flex 3000 with Gateway dual core processor computer running Windows
10 Home 64 bit. 8 GB ram, 2.2 GHz, plenty of disk space.
Issue 1: Can't be the WSJT program to work with the Flex and PowerSDR
> On Mar 28, 2018, at 5:48 AM, Hasan al-Basri wrote:
>
> Running DXp by the developers for testing and evaluation is justifiable.
> Releasing DXp "into the wild" with no restraints or protections from abuse is
> irresponsible.
After seeing the results of “turning
Excellent, Look forward to it, Joe.
73, N0AN
Hasan
On Wed, Mar 28, 2018 at 12:35 PM, Joe Taylor wrote:
> The second public test of FT8 DXpedition mode will be conducted on April
> 7, a little over a week from now. You are cordially invited to join us for
> this test. See
> On Mar 28, 2018, at 11:16 AM, Black Michael via wsjt-devel
> wrote:
>
> Turn off "Monitor returns to last used frequency" in Settings/General.
I have a similar problem to his, Mike, but that setting is completely greyed
out on my non CAT version. I’m
> On Mar 28, 2018, at 7:57 AM, George Molnar wrote:
>
> Granted, this accounts for just one Dxpedition at a time.
And given the explanation of what the mode is supposed to be used for, this
would be correct. As I read it, it isn’t for just any DXpedition to use. Only
Hi Alex,
These sound like good ideas to me. A mechanism for sending I/Q data
into WSJT-X has been on our back-burner "To Do" list for some time. But
as you can probably guess, I'm only superficially familiar with the
protocols you're considering. Bill will probably have a more useful
The second public test of FT8 DXpedition mode will be conducted on April
7, a little over a week from now. You are cordially invited to join us
for this test. See the original announcement (copied below) for details.
Even if you read it before, be sure to read the latest revision of the
DuhSo is there a reason dummy mode always returns true?
bool Configuration::monitor_last_used () const {return m_->rig_is_dummy_ ||
m_->monitor_last_used_;}
Mike
On Wednesday, March 28, 2018, 12:23:16 PM CDT, Joe Taylor
wrote:
Mike --
On 3/28/2018 1:16 PM,
Joe is correct, that setting is grayed out.
I just checked, and the Raspberry Pi version behaves the same way
Karl Heinz - K5KHK
On Wed, Mar 28, 2018 at 1:19 PM, Joe Taylor wrote:
> Mike --
>
> On 3/28/2018 1:16 PM, Black Michael via wsjt-devel wrote:
>
>> Turn off
Mike --
On 3/28/2018 1:16 PM, Black Michael via wsjt-devel wrote:
Turn off "Monitor returns to last used frequency" in Settings/General.
Please think before hitting "Send". He said he's not using CAT control,
so that option is grayed out.
-- Joe, K1JT
Turn off "Monitor returns to last used frequency" in Settings/General.
de Mike W9MDB
On Wednesday, March 28, 2018, 10:59:03 AM CDT, Karl Heinz Kremer
wrote:
I am using FT8 with WSJT-X without CAT control (only PTT is controlled via a
serial interface). In order to
At one point, there were 3 extra bits available in the FT8 message payload. If
one is still available, perhaps it could be used like this:
Add a "CONTEST" menu itemWhen clicked, an input screen something akin to this
comes up:
RUN Message S Exchange
__
I am using FT8 with WSJT-X without CAT control (only PTT is controlled via
a serial interface). In order to change the band (and not to report faulty
results to PSKReporter), I have to do the following:
1. Disable transmit and monitor
2. Change the band on my transmitter (and tune the antenna)
Good morning to the group. I have enjoyed using WSJT in its several
modes but have some issues that don't seem to be solvable at my end.
Setup:
Program version: WSJT-X v1.90-rc3
Rig: Flex 3000 with Gateway dual core processor computer running Windows
10 Home 64 bit. 8 GB ram, 2.2 GHz, plenty
Hi Jay,
Thanks for noticing and reporting this seeming oddity. It's a bug, an
unintended consequence of a change that prevents the transmission of
all-blank messages. It has been corrected in code revision r8587.
-- Joe, K1JT
On 3/28/2018 9:58 AM, Jay Hainline wrote:
Currently I
Hello developers,
I am looking into supporting the RTP+RTCP protocol in CW Skimmer, and I want to do this in a way compatible with other software,
including WSJTX. RTP seems to be the best way of exchanging the I/Q data between the programs, but it needs to be complemented
with another
Currently I am using WSJT-X 1.9.0-rc3 r8581 with Windows 10 64 bit computer.
I happened to notice when I place the program into FT8 Hound mode, the Tune
button does not function when a DX Call has NOT been entered and no standard
messages have been created. As soon as I enter a callsign in the
Regarding comments suggesting that a band plan can be implemented and enforced
in software, I don’t think that will work. It would rely on properly engaged
and functional CAT control by the Fox. Given that several stations have already
“jumped the gun” and are using the mode in its incomplete
*The WSJT-X Development Group selected the FT8 frequencies now being used
by all. I believe that after serious consideration, they should define a
recommended DXpedition mode frequencies for each HF band. I'd further
recommend that the 'Frequencies' table be populated with these recommended
Quoting from K9YC:
"It is a LONG established principle of ham radio, defined by FCC Rules and
corresponding laws in other countries, that no one person or group has
priority on any given frequency at any given time; indeed, these Rules
(laws) establish only permitted emission types for a range of
24 matches
Mail list logo