[wsjt-devel] Tail for ALL.TXT

2019-11-20 Thread Eric Lundstrom
Windows 10 allows the installation of Ubuntu bash as an optional Windows 
feature. That would include the tail command and many other Linux commands. A 
search on "ubuntu bash windows" should provide instructions on how to install 
this useful subsystem.

Eric WB6CVR
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] REMOVE ALL !!!!!!!

2019-11-20 Thread Carl Buehler
I've been trying too but still receiving messages.

On Wed, Nov 20, 2019, 21:56 Neil Zampella  wrote:

> Sorry Stan .. that won't do it.
>
> At the top of each email there should be this blurb:
>
> "
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> or, via email, send a message with subject or body 'help' to
> wsjt-devel-requ...@lists.sourceforge.net
>
> "
>
> Head to the first link, and unsubscribe from there.
>
> Neil, KN3ILZ
>
> On 11/20/2019 5:19 PM, Stan Gantz wrote:
> >
> >
> >
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] REMOVE ALL !!!!!!!

2019-11-20 Thread Neil Zampella

Sorry Stan .. that won't do it.

At the top of each email there should be this blurb:

"

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
or, via email, send a message with subject or body 'help' to
wsjt-devel-requ...@lists.sourceforge.net

"

Head to the first link, and unsubscribe from there.

Neil, KN3ILZ

On 11/20/2019 5:19 PM, Stan Gantz wrote:







___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] REMOVE ALL !!!!!!!

2019-11-20 Thread Stan Gantz





___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Gary Hinson
There's also a step zero, Paul, that doesn't involve digging out, dusting
off and connecting your dummy load: simply turn down your TX power output.
Unless you are VERY unfortunate, a few watts or milliwatts of RF is unlikely
to cause problems.  

 

Gradually increase your TX power until the problems occur, and you have a
strong indication that RF is the culprit.  You then have the option to stay
below the problematic level and carry on working stuff, meanwhile attempting
to fix the issue with shielding, grounding, ferrites, layout changes, better
feeders etc. until you're OK with higher power (if you need it).

 

Problems that only occur on one or some bands are another clue that RF is
probably the issue. 

 

73

Gary  ZL2iFB

 

From: Paul Randall  
Sent: 21 November 2019 10:31
To: WSJT software development 
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

 

Anyone who experiences peculiar behaviour from their station on some
band/frequency/antenna/rig upon activating the transmitter should firstly
perform this most basic test.

 

STEP 1A1A1 - Try to reproduce the problem with the transmitter directly
connected to a dummy load. This test should virtually eliminate the
possibility that simple EMI is the culprit (which it is in most cases).

 

Having suffered the problem myself, I know first hand that the above is
excellent advice.

 

Kind regards and good DX to all,

Paul G3NJV

 

 

 

  _  

From: Jim Jennings mailto:w...@comcast.net> >
Sent: 20 November 2019 16:55
To: WSJT software development mailto:wsjt-devel@lists.sourceforge.net> >
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue 

 

The symptoms suggest to me RF getting into a USB cable between computer and
the rig's CI-V USB port.  My cousin had a similar situation with his
FTDX-3000 on 40 and 30M FT8, where the rig would abruptly quit transmitting
if he tried to exceed about 25 watts.  The problem was solved by winding
some of the "spare" length of the computer to CAT USB cable on a ferrite
toroid (FT240-43 used in this case).  He can now increase to full output
power of the rig (100W) without anything "flinching."  Just a thought.  73,

 

Jim, W7XZ

 

From: Christopher Diederich via wsjt-devel 

Sent: Wednesday, November 20, 2019 05:01

To: Paul Randall ; WSJT software development ;
wsjt-devel-ow...@lists.sourceforge.net
  

Cc: Christopher Diederich 

Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

 

I will run it into a dummy load to check though. Thanks for the suggestion. 

 

Chris

 

Get Outlook for iOS  





On Wed, Nov 20, 2019 at 7:53 AM -0500, "Christopher Diederich"
mailto:k1...@yahoo.com> > wrote:

I have not tested with a dummy load.  Other digital modes and phone don't
have the same issue, and SWR is 2.5:1 into OCF 80 meter dipole, which is
tuned easily with my LDG. 

 

Get Outlook for iOS  





On Wed, Nov 20, 2019 at 5:12 AM -0500, "Paul Randall"
mailto:paulfrand...@hotmail.com> > wrote:

Does it do it when the rig is running into a dummy load?

 

 

 

Sent from my Samsung Galaxy smartphone.

 

 

 Original message 

From: Christopher Diederich via wsjt-devel mailto:wsjt-devel@lists.sourceforge.net> > 

Date: 20/11/2019 01:59 (GMT+00:00) 

To: wsjt-devel@lists.sourceforge.net
 ,
wsjt-devel-ow...@lists.sourceforge.net
  

Cc: Christopher Diederich mailto:k1...@yahoo.com> > 

Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue 

 

 

Get Outlook for iOS  


  _  


From: Christopher Diederich mailto:k1...@yahoo.com> >
Sent: Tuesday, November 19, 2019 8:26 PM
To: wsjtgr...@yahoogroups.com  
Subject: 40 Meter Power USB-D issue 

 

Good evening,

 

I am experiencing a recent issue that has arisen where my IC-7300 is
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other
digital modes and phone work fine, and no other bands have the low power
issue.  Also, the rig occasionally changes from USB-D to USB when keying.
Any ideas?

 

IC-7300

Win 10 Pro 64 bit

HRD version 6.7.0.244

WSJT-X version 2.1.0

 

73

Chris Diederich K1LDO

 

 

  _  

  _  

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net  
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Paul Randall
Anyone who experiences peculiar behaviour from their station on some 
band/frequency/antenna/rig upon activating the transmitter should firstly 
perform this most basic test.

STEP 1A1A1 - Try to reproduce the problem with the transmitter directly 
connected to a dummy load. This test should virtually eliminate the possibility 
that simple EMI is the culprit (which it is in most cases).

Having suffered the problem myself, I know first hand that the above is 
excellent advice.

Kind regards and good DX to all,
Paul G3NJV




From: Jim Jennings 
Sent: 20 November 2019 16:55
To: WSJT software development 
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

The symptoms suggest to me RF getting into a USB cable between computer and the 
rig’s CI-V USB port.  My cousin had a similar situation with his FTDX-3000 on 
40 and 30M FT8, where the rig would abruptly quit transmitting if he tried to 
exceed about 25 watts.  The problem was solved by winding some of the “spare” 
length of the computer to CAT USB cable on a ferrite toroid (FT240-43 used in 
this case).  He can now increase to full output power of the rig (100W) without 
anything “flinching.”  Just a thought.  73,

Jim, W7XZ

From: Christopher Diederich via wsjt-devel
Sent: Wednesday, November 20, 2019 05:01
To: Paul Randall ; WSJT software development ; 
wsjt-devel-ow...@lists.sourceforge.net
Cc: Christopher Diederich
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

I will run it into a dummy load to check though. Thanks for the suggestion.

Chris

Get Outlook for iOS



On Wed, Nov 20, 2019 at 7:53 AM -0500, "Christopher Diederich" 
 wrote:

I have not tested with a dummy load.  Other digital modes and phone don’t have 
the same issue, and SWR is 2.5:1 into OCF 80 meter dipole, which is tuned 
easily with my LDG.

Get Outlook for iOS



On Wed, Nov 20, 2019 at 5:12 AM -0500, "Paul Randall" 
 wrote:

Does it do it when the rig is running into a dummy load?



Sent from my Samsung Galaxy smartphone.


 Original message 
From: Christopher Diederich via wsjt-devel 
Date: 20/11/2019 01:59 (GMT+00:00)
To: wsjt-devel@lists.sourceforge.net, wsjt-devel-ow...@lists.sourceforge.net
Cc: Christopher Diederich 
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue


Get Outlook for iOS

From: Christopher Diederich 
Sent: Tuesday, November 19, 2019 8:26 PM
To: wsjtgr...@yahoogroups.com
Subject: 40 Meter Power USB-D issue

Good evening,

I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes from USB-D to USB when keying. Any ideas?

IC-7300
Win 10 Pro 64 bit
HRD version 6.7.0.244
WSJT-X version 2.1.0

73
Chris Diederich K1LDO






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

2019-11-20 Thread Grant VK5GR
George,

 

Allow me to answer your questions in line:

 

| Aren’t major efforts (those we expect to use F/H) frequencies pre-coordinated 
and published in advance of the trip? 

 

You would like to think so. In practice despite trying to do just that the 
larger expeditions just took the information I tried sending about 

A35JT and filed it into the circular filing cabinet – then published my 
proposed A35JT frequencies as their own despite being told we 

were going out there months before they published theirs. So you cannot rely on 
pre-coordination.

 

| Do holiday-style trips really need F/H?

 

Depends on where they go now doesn’t it? If it was a one man holiday trip to a 
top 40-50 most wanted destination (or even a top 100 it seems) 

you can very quickly overwhelm and destroy the main standard FT8 channels. 
Whether it is one person or 30 at the DXpedition site doesn’t matter. 

If the location they are operating from is rarely activated and they have more 
than 5-6 callers at a time trying to work them, then there is a case 

to move to Fox/Hound mode, one – to speed up your QSO rate and two – to prevent 
overwhelming the main channels.

 

| Major dxpeditions should never operate in the standard watering holes, right? 
Isn’t there advice about this in the manual?

 

The software in fact means that you cant activate FOX mode on one of the 
primary frequencies. We are not talking about running FOX mode on the 

Existing standard mode frequencies anyway.

 

| So, why would operators looking to maximize QSO count need additional band 
monitoring displays? Shouldn’t they 
| concentrate on answering the calls headed their way? Clearing contacts would 
seem to be the goal, not searching a 
| pileup for a multiplier or rare one, right?

 

Sorry but this looks like a question from someone who has never been on the 
receiving end of an expedition FOX operation.

 

a.   We are trying to maximise QSO count

b.  There is no band activity display currently – so if another FOX 
operation starts up on top of you, you really don’t know about it initially – 
only secondary indications start to give you a hint that there is a problem.

c.   The multiplier comment is also irrelevant because in FOX mode I can do 
that today with the controls I have for stations calling me 
anyway – if I want to preference someone I can without the band activity window

 

| I grant you, DQRM or operator error can wreak havoc. Wouldn’t this show up in 
the fox’s completion rate and thus 
| raise suspicion by an experienced operator?

 

And it does – but it takes time and an experienced operator to see their 
completion rate fall. Unfortunately there are multiple reasons the

completion rate can fall – often caused by people using standard mode to call a 
FOX station repeatedly on the FOX uplink sub-channel. Direct
evidence on screen that there are callers for another FOX on the same frequency 
as yourself would allow you to more quickly take evasive 
action – or better still give you pause and not start up your FOX CQ on top of 
someone else in the first place. 

 

| For hounds not willing to set up a profile, why? It is extremely easy and 
affords you the ability to enter the Dxpeditions 
| published frequencies, switch between them nearly instantly, and keep some 
semblance of order by not editing your normal 
| frequency list. Is there an advantage I am missing?

 

Couldn’t agree more – do it all the time – but this is not at issue here

 

Your other questions I will leave others to reply to as they are not about FOX 
mode operation from the FOX operator position.

 

Regards,

Grant VK5GR – Dxpedition Leader for A35JT Tonga

 

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X is unable to share Omni-Rig with Log4OM?

2019-11-20 Thread Bill Somerville

Hi Zeev,

ok, thanks for checking that. The next step is to get a diagnostic log 
from OmniRig. To turn on debug logging in OmniRig you must modify the file:


"%AppData%\Afreet\Products\OmniRig\OmniRig.ini"

Add the following to the top of that file:

[Debug]
Log=1

that will cause the OmniRig server process to create a trace log called 
OmniRig.log in the same directory. Run a minimal test to reproduce one 
of the issues and send me that file attached to a PM please?


73
Bill
G4WJS.

On 20/11/2019 19:59, Zeev Stadler wrote:

Hello Bill,

None of the programs is running in elevated mode and the problem exists.

See 
https://user-images.githubusercontent.com/1304610/69273411-fb01cb00-0be0-11ea-95de-78effc5197bc.png 
for a screenshot


73
Zeev
4X5ZS

On Wed, Nov 20, 2019 at 9:48 PM Bill Somerville > wrote:


Hi Zeev,

I still suspect one of relevant processes is running with elevated
rights. You can check directly using Windows Task Manager. Start
Task Manager, switch to the "Details" tab, right-click any column
heading and press the "Select columns" button, in the window that
pops up check the "Elevated" option. This will add a new detail
column with values of "Yes" or "No" for each process's elevated
status. Check that wsjtx.exe, OmniRig.exe, and the Log4OM
processes are running without elevation.

Note that there several ways to run a process with elevated rights
including explicitly running as Administrator or checking the
"Properties->Compatibility->Run this program as an administrator"
option in either the program executable, or shortcut used to start it.

As I stated before, none of the relevant programs should be run
with Administrator rights, it is not necessary and only creates a
security risk. If any process is running with elevated rights it
will be blocked from interoperating with other processes that do
not have elevated rights. Elevated rights are only needed to
access protected files and directories and other protected system
resources, none of which are needed for basic user applications
like log keeping, CAT control, audio streams, or accessing remote
network resources.

73
Bill
G4WJS.

On 20/11/2019 17:52, Zeev Stadler wrote:

Hello Bill,

Below I have described to scenarios.

In "Option 1" WSJT-X has an intermittent communication problem
with Omni-Rig, but Log4OM is unable to communicate with the rig.

In "Option 2" WSJT-X produced en error: "OmniRig: timeout waiting
for update from rig", and WSJT-X is unable to communicate with
the rig.

Please let me know how can I further help clarify the problem.

73
Zeev
4X5ZS

On Tue, Nov 19, 2019 at 5:31 PM Zeev Stadler
mailto:zeev.stad...@gmail.com>> wrote:

This is my first post here. I've tried the Yahoo group, but
that did not help. Hopefully the developers here can shed
some light on the expected behavior.

Omni-Rig main feature is "multithreading: multiple programs,
written by different authors in different languages, can
control the radio via Omni-Rig at the same time
". I therefore expected that
WSJT-X would be able to run in parallel with Log4OM when both
programs use Omni-Rig. So far I failed to do so.

Can these programs work simultaneously with Omni-Rig?
_
_
_Option 1:_ First WSJT-X completes its initialization and
then Log4OM is started
Log4OM would not connect with Omni-Rig. During the startup of
Log2OM, WSJT-X's rig-control indicator would turn orange or
it will show a rig-control error. These errors are easy fixed
by a retry.

_Option 2:_ First Log4OM completes its initialization and
then WSJT-X is started
WSJT-X show a Rig Control Error "OmniRig: timeout waiting for
update from rig"

Similar behavior is seen when trying to run SWJT-X
simultaneously with HolyLogger
.

On the other hand, Log4OM and HolyLogger are happy to work
simultaneously with Omni-Rig. In addition, changes in the
rig's frequency are reflected in both loggers. This is true
for changes made directly on the rig and when the frequency
is changed using Log4OM.

I'm using WSJT-X latest version (v.2.10.0) and Log4OM latest
version (1.40.0.0) on a Windows 10 Home PC. The behavior
described above is when all programs are run as
administrator, as suggested in the Yahoo group.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Christopher Diederich via wsjt-devel

  
  
  

Thanks for the assistance. I have a shielded USB cable wrapped in a 
toroid connecting the two, and have a powered USB hub to hopefully further 
isolate the computer from the radio. This was in response to the rig/pc 
connection dropping previously. 
I’ll double check the setup and connections. 



‘73de K1LDOChris Diederich

  




On Wed, Nov 20, 2019 at 12:01 PM -0500, "Jim Jennings"  wrote:














The symptoms suggest to me RF getting into a USB cable between computer and 
the rig’s CI-V USB port.  My cousin had a similar situation with his 
FTDX-3000 on 40 and 30M FT8, where the rig would abruptly quit transmitting if 
he tried to exceed about 25 watts.  The problem was solved by winding some 
of the “spare” length of the computer to CAT USB cable on a ferrite toroid 
(FT240-43 used in this case).  He can now increase to full output power of 
the rig (100W) without anything “flinching.”  Just a thought.  
73,
 
Jim, W7XZ


 

From: Christopher Diederich via wsjt-devel 

Sent: Wednesday, November 20, 2019 05:01
To: Paul Randall ; WSJT software development ; 
wsjt-devel-ow...@lists.sourceforge.net 

Cc: Christopher Diederich 
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D 
issue
 



I will run it into a dummy load to check though. 
Thanks for the suggestion. 
 
Chris
 
Get Outlook 
for iOS



On Wed, Nov 20, 2019 at 7:53 AM -0500, "Christopher 
Diederich"  
wrote:



  
  
  
  I have not tested with a dummy load.  Other 
  digital modes and phone don’t have the same issue, and SWR is 2.5:1 into OCF 
  80 meter dipole, which is tuned easily with my LDG. 
   
  Get Outlook for iOS



  On Wed, Nov 20, 2019 at 5:12 AM -0500, "Paul Randall" 
   
  wrote:


  


Does it do it when the rig is running into a dummy load?
 
 
 

Sent from my Samsung Galaxy 
smartphone.
 
 
 Original message 
From: Christopher Diederich via wsjt-devel 
 
Date: 20/11/2019 01:59 (GMT+00:00) 
To: wsjt-devel@lists.sourceforge.net, 
wsjt-devel-ow...@lists.sourceforge.net 
Cc: Christopher Diederich  
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue 
 







 
Get Outlook for iOS



From: 
Christopher Diederich 
Sent: Tuesday, 
November 19, 2019 8:26 PM
To: 
wsjtgr...@yahoogroups.com
Subject: 40 Meter Power USB-D issue 
 








Good evening,
 
I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  
Other digital modes and phone work fine, and no other bands have the low 
power issue.  Also, the rig occasionally changes from USB-D to USB when 
keying. Any ideas?
 
IC-7300
Win 10 Pro 64 bit
HRD version 6.7.0.244
WSJT-X version 2.1.0
 
73
Chris Diederich K1LDO
 
 









___
wsjt-devel mailing 
list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X is unable to share Omni-Rig with Log4OM?

2019-11-20 Thread Bill Somerville

Hi Zeev,

I still suspect one of relevant processes is running with elevated 
rights. You can check directly using Windows Task Manager. Start Task 
Manager, switch to the "Details" tab, right-click any column heading and 
press the "Select columns" button, in the window that pops up check the 
"Elevated" option. This will add a new detail column with values of 
"Yes" or "No" for each process's elevated status. Check that wsjtx.exe, 
OmniRig.exe, and the Log4OM processes are running without elevation.


Note that there several ways to run a process with elevated rights 
including explicitly running as Administrator or checking the 
"Properties->Compatibility->Run this program as an administrator" option 
in either the program executable, or shortcut used to start it.


As I stated before, none of the relevant programs should be run with 
Administrator rights, it is not necessary and only creates a security 
risk. If any process is running with elevated rights it will be blocked 
from interoperating with other processes that do not have elevated 
rights. Elevated rights are only needed to access protected files and 
directories and other protected system resources, none of which are 
needed for basic user applications like log keeping, CAT control, audio 
streams, or accessing remote network resources.


73
Bill
G4WJS.

On 20/11/2019 17:52, Zeev Stadler wrote:

Hello Bill,

Below I have described to scenarios.

In "Option 1" WSJT-X has an intermittent communication problem with 
Omni-Rig, but Log4OM is unable to communicate with the rig.


In "Option 2" WSJT-X produced en error: "OmniRig: timeout waiting for 
update from rig", and WSJT-X is unable to communicate with the rig.


Please let me know how can I further help clarify the problem.

73
Zeev
4X5ZS

On Tue, Nov 19, 2019 at 5:31 PM Zeev Stadler > wrote:


This is my first post here. I've tried the Yahoo group, but that
did not help. Hopefully the developers here can shed some light on
the expected behavior.

Omni-Rig main feature is "multithreading: multiple programs,
written by different authors in different languages, can control
the radio via Omni-Rig at the same time
". I therefore expected that
WSJT-X would be able to run in parallel with Log4OM when both
programs use Omni-Rig. So far I failed to do so.

Can these programs work simultaneously with Omni-Rig?
_
_
_Option 1:_ First WSJT-X completes its initialization and then
Log4OM is started
Log4OM would not connect with Omni-Rig. During the startup of
Log2OM, WSJT-X's rig-control indicator would turn orange or it
will show a rig-control error. These errors are easy fixed by a retry.

_Option 2:_ First Log4OM completes its initialization and then
WSJT-X is started
WSJT-X show a Rig Control Error "OmniRig: timeout waiting for
update from rig"

Similar behavior is seen when trying to run SWJT-X simultaneously
with HolyLogger .

On the other hand, Log4OM and HolyLogger are happy to work
simultaneously with Omni-Rig. In addition, changes in the rig's
frequency are reflected in both loggers. This is true for changes
made directly on the rig and when the frequency is changed using
Log4OM.

I'm using WSJT-X latest version (v.2.10.0) and Log4OM latest
version (1.40.0.0) on a Windows 10 Home PC. The behavior described
above is when all programs are run as administrator, as suggested
in the Yahoo group.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X is unable to share Omni-Rig with Log4OM?

2019-11-20 Thread Zeev Stadler
 Bill,

Yes, I've tried the non-administrative runs too. In fact, none of the
possible combinations enabled both programs to communicate with Omni-Rig.

73
Zeev
4X5ZS

On Wed, Nov 20, 2019 at 8:01 PM Bill Somerville 
wrote:

> On 20/11/2019 17:52, Zeev Stadler wrote:
> > Hello Bill,
> >
> > Below I have described to scenarios.
> >
> > In "Option 1" WSJT-X has an intermittent communication problem with
> > Omni-Rig, but Log4OM is unable to communicate with the rig.
> >
> > In "Option 2" WSJT-X produced en error: "OmniRig: timeout waiting for
> > update from rig", and WSJT-X is unable to communicate with the rig.
> >
> > Please let me know how can I further help clarify the problem.
> >
> > 73
> > Zeev
> > 4X5ZS
>
> Zeev,
>
> have you ensured that neither WSJT-X nor Log4OM are running with
> Administrator rights?
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


[wsjt-devel] Sorry!

2019-11-20 Thread George J Molnar
Cockpit error here led me to believe I lost my first (draft) response, so I 
re-wrote it. My apologies for the wasted bandwidth. Admins, please feel free to 
strike the older of my two similar missives.

George J Molnar
Arlington, Virginia, USA___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

2019-11-20 Thread George J Molnar
A couple recent comments on Fox/Hound mode have me perplexed. 

Aren’t major efforts (those we expect to use F/H) frequencies pre-coordinated 
and published in advance of the trip? 

Do holiday-style trips really need F/H?

Major dxpeditions should never operate in the standard watering holes, right? 
Isn’t there advice about this in the manual?

So, why would operators looking to maximize QSO count need additional band 
monitoring displays? Shouldn’t they concentrate on answering the calls headed 
their way? Clearing contacts would seem to be the goal, not searching a pileup 
for a multiplier or rare one, right?

I grant you, DQRM or operator error can wreak havoc. Wouldn’t this show up in 
the fox’s completion rate and thus raise suspicion by an experienced operator?

For hounds not willing to set up a profile, why? It is extremely easy and 
affords you the ability to enter the Dxpeditions published frequencies, switch 
between them nearly instantly, and keep some semblance of order by not editing 
your normal frequency list. Is there an advantage I am missing?

Hound mode allows full passband monitoring capability, check-box on the main 
screen. Is this insufficient to check band activity before jumping in? I 
thought the receive side of hound mode looks and acts like “normal” FT8. 

In the event of multi-signal operation from non-WSJT-x operations (perhaps in 
the watering holes), why would there be interest in switching to hound mode? 
Standard FT8 works perfectly in this situation. Identifying the mode of 
operation takes little time - if you see someone above 1000 Hz complete a 
contact, it’s not F/H. Or am I confused?

I appreciate the group’s indulgence and patience.

George J Molnar, KF2T 
Arlington, Virginia, USA___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

2019-11-20 Thread George J Molnar
Please forgive what may be ridiculous questions. Some are for foxes, others 
for hounds.

Fox/Hound operation should only be carried out away from the main “watering 
holes,” right? For expeditions, isn’t it standard practice to coordinate with 
other expeditions before leaving home to ensure efficient spectrum use?

Why is looking for another station on the same DF and cycle helpful? Wouldn’t 
the sudden influx of calls for someone-not-you be a tipoff?

Is building a configuration for F/H so onerous, since it could even include the 
announced DXpedition frequencies in the drop down without messing with 
day-to-day use?

Isn’t there a “receive all frequencies” checkbox on the main screen during F/H 
operation? Is this not sufficient to monitor the pileup before jumping in?

Is there value to monitoring another frequency while operating F/H that can’t 
best be solved with a second instance?





George J Molnar, KF2T 
Arlington, Virginia, USA
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X is unable to share Omni-Rig with Log4OM?

2019-11-20 Thread Bill Somerville

On 20/11/2019 17:52, Zeev Stadler wrote:

Hello Bill,

Below I have described to scenarios.

In "Option 1" WSJT-X has an intermittent communication problem with 
Omni-Rig, but Log4OM is unable to communicate with the rig.


In "Option 2" WSJT-X produced en error: "OmniRig: timeout waiting for 
update from rig", and WSJT-X is unable to communicate with the rig.


Please let me know how can I further help clarify the problem.

73
Zeev
4X5ZS


Zeev,

have you ensured that neither WSJT-X nor Log4OM are running with 
Administrator rights?


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X is unable to share Omni-Rig with Log4OM?

2019-11-20 Thread Zeev Stadler
Hello Bill,

Below I have described to scenarios.

In "Option 1" WSJT-X has an intermittent communication problem with
Omni-Rig, but Log4OM is unable to communicate with the rig.

In "Option 2" WSJT-X produced en error: "OmniRig: timeout waiting for
update from rig", and WSJT-X is unable to communicate with the rig.

Please let me know how can I further help clarify the problem.

73
Zeev
4X5ZS

On Tue, Nov 19, 2019 at 5:31 PM Zeev Stadler  wrote:

> This is my first post here. I've tried the Yahoo group, but that did not
> help. Hopefully the developers here can shed some light on the expected
> behavior.
>
> Omni-Rig main feature is "multithreading: multiple programs, written by
> different authors in different languages, can control the radio via
> Omni-Rig at the same time ". I therefore
> expected that WSJT-X would be able to run in parallel with Log4OM when both
> programs use Omni-Rig. So far I failed to do so.
>
> Can these programs work simultaneously with Omni-Rig?
>
> *Option 1:* First WSJT-X completes its initialization and then Log4OM is
> started
> Log4OM would not connect with Omni-Rig. During the startup of Log2OM,
> WSJT-X's rig-control indicator would turn orange or it will show a
> rig-control error. These errors are easy fixed by a retry.
>
> *Option 2:* First Log4OM completes its initialization and then WSJT-X is
> started
> WSJT-X show a Rig Control Error "OmniRig: timeout waiting for update from
> rig"
>
> Similar behavior is seen when trying to run SWJT-X simultaneously with
> HolyLogger .
>
> On the other hand, Log4OM and HolyLogger are happy to work simultaneously
> with Omni-Rig. In addition, changes in the rig's frequency are reflected in
> both loggers. This is true for changes made directly on the rig and when
> the frequency is changed using Log4OM.
>
> I'm using WSJT-X latest version (v.2.10.0) and Log4OM latest version
> (1.40.0.0) on a Windows 10 Home PC. The behavior described above is when
> all programs are run as administrator, as suggested in the Yahoo group.
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X is unable to share Omni-Rig with Log4OM?

2019-11-20 Thread Bill Somerville

On 20/11/2019 17:19, Zeev Stadler wrote:
I would appreciate a word from the developers - should we expect to 
have WSJT-X in parallel with other programs that use Omni-Rig?


Hi Zeev,

you have not told us exactly does not work yet. If you get an error 
message from WSJT-X, what does it say including the details. For you 
convenience you can copy the full error message text to the Windows 
clipboard by hitting CTRL+C whille the error message has keyboard focus.


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X is unable to share Omni-Rig with Log4OM?

2019-11-20 Thread Zeev Stadler
I would appreciate a word from the developers - should we expect to have
WSJT-X in parallel with other programs that use Omni-Rig?
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

2019-11-20 Thread David Gilbert


I don't use Fox/Hound, of course, but it seems to me that VK5GR's 
request when using it is legitimate.  I wouldn't have said anything at 
all if it weren't for the dev reply that cited a lack of screen real 
estate as the reason for not addressing it.


It's not bitching to point out the obvious.

Dave   AB7E


On 11/20/2019 4:29 AM, Fred Price wrote:
Ya know if you so much want this why not open your computer and 
reprogram the interface yourself?
What's it take 30 seconds to open settings or change a config? Is the 
DX going to disappear in that time?
I guess everyone forgot about when the NA contest mode had a check box 
on the GUI. So many wondered why they were in contest mode because 
they mistakingly checked the box.
Most like the dev group has a lot more to do then move a check box. 
I'd bet they have life's outside of ham radio as well. I think the dev 
group does a helluva job. Just one last thing, how can anybody bitch 
about free software


On Nov 19, 2019 7:25 PM, David Gilbert  wrote:


If anyone was seriously concerned about real estate usage in the
WSJT-X
user window there wouldn't be all that wasted space in the lower left
corner for any of the modes.  The Frequency display doesn't need
to be
anywhere near that large, DX Call and DX Grid is mostly
superfluous, the
size of the Date/Time box is ridiculous ...   and all of that
could be
resized and repositioned under the Auto Seq and Call 1st buttons.

All of which has been brought up before.

Dave   AB7E

On 11/19/2019 2:36 PM, Grant VK5GR wrote:
> Joe,
>
> As for the band activity window - yes screen realestate is
cluttered as it
> stands - but not being able to see the band activity is an
extremely serious
> problem on the air. The "workarounds" proposed are just that -
workarounds.
> Not all Fox operators will be that savvy (although I wish I had
thought of
> the tail ALL.TXT idea out on the island).
>
> Regards,
> Grant
>



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Jim Jennings
The symptoms suggest to me RF getting into a USB cable between computer and the 
rig’s CI-V USB port.  My cousin had a similar situation with his FTDX-3000 on 
40 and 30M FT8, where the rig would abruptly quit transmitting if he tried to 
exceed about 25 watts.  The problem was solved by winding some of the “spare” 
length of the computer to CAT USB cable on a ferrite toroid (FT240-43 used in 
this case).  He can now increase to full output power of the rig (100W) without 
anything “flinching.”  Just a thought.  73,

Jim, W7XZ

From: Christopher Diederich via wsjt-devel 
Sent: Wednesday, November 20, 2019 05:01
To: Paul Randall ; WSJT software development ; 
wsjt-devel-ow...@lists.sourceforge.net 
Cc: Christopher Diederich 
Subject: Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

I will run it into a dummy load to check though. Thanks for the suggestion. 

Chris

Get Outlook for iOS




On Wed, Nov 20, 2019 at 7:53 AM -0500, "Christopher Diederich" 
 wrote:


  I have not tested with a dummy load.  Other digital modes and phone don’t 
have the same issue, and SWR is 2.5:1 into OCF 80 meter dipole, which is tuned 
easily with my LDG. 

  Get Outlook for iOS




  On Wed, Nov 20, 2019 at 5:12 AM -0500, "Paul Randall" 
 wrote:


Does it do it when the rig is running into a dummy load?



Sent from my Samsung Galaxy smartphone.


 Original message 
From: Christopher Diederich via wsjt-devel 
 
Date: 20/11/2019 01:59 (GMT+00:00) 
To: wsjt-devel@lists.sourceforge.net, 
wsjt-devel-ow...@lists.sourceforge.net 
Cc: Christopher Diederich  
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue 


Get Outlook for iOS



From: Christopher Diederich 
Sent: Tuesday, November 19, 2019 8:26 PM
To: wsjtgr...@yahoogroups.com
Subject: 40 Meter Power USB-D issue 

Good evening,

I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes from USB-D to USB when keying. Any ideas?

IC-7300
Win 10 Pro 64 bit
HRD version 6.7.0.244
WSJT-X version 2.1.0

73
Chris Diederich K1LDO









___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

2019-11-20 Thread Joe Taylor

Grant --

On 11/19/2019 4:36 PM, Grant VK5GR wrote:


We tested a lot of the station before we left - as much functionality and
hardware as we could in fact. However in the case of FOX mode, that is
something that is extremely difficult to test ... 


Actually, the disabling of *Tx Enable* after Fox sends RR73 in WSJT-X 
2.1.0 is very easy to confirm.  Fox needs only make a single QSO with 
someone acting as Hound.  Do it over the air, if you wish, but it's 
trivial to simulate by using two instances of WSJT-X running on a single 
computer, with loop-back audio.



... until you arrive somewhere
where people will a) accept you should be running FOX mode and b) are able
to attract enough callers to even conduct the test. I'm afraid your
suggestion of "test before you leave" in this case perhaps isn't a practical
one :) 


Quite the contrary.


Most expeditions running FOX mode these days start with small 2-3 man
shows which head out to exotic places that justify FOX mode. Things like the
RR73 problem only really become apparent after perhaps 15-30 minutes of use
when it dawns on you what is going on too. In reality most FOX stations
don't have the resources to try a full FOX mode QSO test as you suggested
prior to leaving.


Again, this makes no sense.


As for the band activity window - yes screen realestate is cluttered as it
stands - but not being able to see the band activity is an extremely serious
problem on the air. The "workarounds" proposed are just that - workarounds.
Not all Fox operators will be that savvy (although I wish I had thought of
the tail ALL.TXT idea out on the island).


Managing a pileup, perhaps in the presence of unrelated QRM, is surely 
the responsibility of the operator of a much desired DX station. 
Yesterday I described two different ways to keep track of such 
"unrelated QRM".


-- Joe, K1JT


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

2019-11-20 Thread Tom Ramberg via wsjt-devel
Fred, I see no bitching here, just friendy questions and mostly very polite 
answers.

73 de Tom OH6VDA (occasionally semi-rare JW6VDA)

Sendt fra min iPad Air 2

> 20. nov. 2019 kl. 13:34 skrev Fred Price :
> 
> 
> Ya know if you so much want this why not open your computer and reprogram the 
> interface yourself?
> What's it take 30 seconds to open settings or change a config? Is the DX 
> going to disappear in that time?
> I guess everyone forgot about when the NA contest mode had a check box on the 
> GUI. So many wondered why they were in contest mode because they mistakingly 
> checked the box.
> Most like the dev group has a lot more to do then move a check box. I'd bet 
> they have life's outside of ham radio as well. I think the dev group does a 
> helluva job. Just one last thing, how can anybody bitch about free software
> 
> On Nov 19, 2019 7:25 PM, David Gilbert  wrote:
> 
> If anyone was seriously concerned about real estate usage in the WSJT-X 
> user window there wouldn't be all that wasted space in the lower left 
> corner for any of the modes.  The Frequency display doesn't need to be 
> anywhere near that large, DX Call and DX Grid is mostly superfluous, the 
> size of the Date/Time box is ridiculous ...   and all of that could be 
> resized and repositioned under the Auto Seq and Call 1st buttons.
> 
> All of which has been brought up before.
> 
> Dave   AB7E
> 
> On 11/19/2019 2:36 PM, Grant VK5GR wrote:
> > Joe,
> >
> > As for the band activity window - yes screen realestate is cluttered as it
> > stands - but not being able to see the band activity is an extremely serious
> > problem on the air. The "workarounds" proposed are just that - workarounds.
> > Not all Fox operators will be that savvy (although I wish I had thought of
> > the tail ALL.TXT idea out on the island).
> >
> > Regards,
> > Grant
> >
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> 
> 
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Christopher Diederich via wsjt-devel

  
  
  

I will run it into a dummy load to check though. Thanks for the 
suggestion. 
Chris



Get Outlook for iOS

  




On Wed, Nov 20, 2019 at 7:53 AM -0500, "Christopher Diederich" 
 wrote:











  
  
  

I have not tested with a dummy load.  Other digital modes and phone 
don’t have the same issue, and SWR is 2.5:1 into OCF 80 meter dipole, which is 
tuned easily with my LDG. 



Get Outlook for iOS

  




On Wed, Nov 20, 2019 at 5:12 AM -0500, "Paul Randall" 
 wrote:
















Does it do it when the rig is running into a dummy load?










Sent from my Samsung Galaxy smartphone.







 Original message 
From: Christopher Diederich via wsjt-devel 

Date: 20/11/2019 01:59 (GMT+00:00) 
To: wsjt-devel@lists.sourceforge.net, wsjt-devel-ow...@lists.sourceforge.net

Cc: Christopher Diederich  
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue 














Get 
Outlook for iOS



From: Christopher Diederich 

Sent: Tuesday, November 19, 2019 8:26 PM

To: wsjtgr...@yahoogroups.com

Subject: 40 Meter Power USB-D issue
 










Good evening,





I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes
 from USB-D to USB when keying. Any ideas?





IC-7300

Win 10 Pro 64 bit

HRD version 6.7.0.244

WSJT-X version 2.1.0





73

Chris Diederich K1LDO






























___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Christopher Diederich via wsjt-devel

  
  
  

Hi Kevin,
I’ll check it with a dummy load. Figured since PSK31 (7.070)is so close to the 
FT8 freq (7.074) and the power output is fine using PSK31 the antenna was fine. 
Doesn’t hurt to rule the antenna out. Thanks. 
Chris 



Get Outlook for iOS

  




On Tue, Nov 19, 2019 at 9:59 PM -0500, "Kevin McQuiggin"  
wrote:










Hi Chris:
Possibly a suggestion that you have already checked, but how does the power 
look into a dummy load?  Perhaps the power reduction on 40m is due to a new 
mismatch.  It may be a hardware issue rather than a WSJT-X issue!
73,
Kevin 

On Nov 19, 2019, at 5:55 PM, Christopher Diederich via wsjt-devel 
 wrote:




Get Outlook for iOS  From: Christopher Diederich 
Sent: Tuesday, November 19, 2019 8:26 PM
To: wsjtgr...@yahoogroups.com
Subject: 40 Meter Power USB-D issue Good evening,
I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes from USB-D to USB when keying. Any ideas?
IC-7300Win 10 Pro 64 bitHRD version 6.7.0.244WSJT-X version 2.1.0
73Chris Diederich K1LDO

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel






___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Christopher Diederich via wsjt-devel

  
  
  

I have not tested with a dummy load.  Other digital modes and phone 
don’t have the same issue, and SWR is 2.5:1 into OCF 80 meter dipole, which is 
tuned easily with my LDG. 



Get Outlook for iOS

  




On Wed, Nov 20, 2019 at 5:12 AM -0500, "Paul Randall" 
 wrote:
















Does it do it when the rig is running into a dummy load?










Sent from my Samsung Galaxy smartphone.







 Original message 
From: Christopher Diederich via wsjt-devel 

Date: 20/11/2019 01:59 (GMT+00:00) 
To: wsjt-devel@lists.sourceforge.net, wsjt-devel-ow...@lists.sourceforge.net

Cc: Christopher Diederich  
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue 














Get 
Outlook for iOS



From: Christopher Diederich 

Sent: Tuesday, November 19, 2019 8:26 PM

To: wsjtgr...@yahoogroups.com

Subject: 40 Meter Power USB-D issue
 










Good evening,





I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes
 from USB-D to USB when keying. Any ideas?





IC-7300

Win 10 Pro 64 bit

HRD version 6.7.0.244

WSJT-X version 2.1.0





73

Chris Diederich K1LDO

























___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] FT8 Fox and Hound Mode - FOX Mode Operator enhancement request

2019-11-20 Thread Fred Price
Ya know if you so much want this why not open your computer and reprogram the 
interface yourself?
What's it take 30 seconds to open settings or change a config? Is the DX going 
to disappear in that time?
I guess everyone forgot about when the NA contest mode had a check box on the 
GUI. So many wondered why they were in contest mode because they mistakingly 
checked the box.
Most like the dev group has a lot more to do then move a check box. I'd bet 
they have life's outside of ham radio as well. I think the dev group does a 
helluva job. Just one last thing, how can anybody bitch about free software

On Nov 19, 2019 7:25 PM, David Gilbert  wrote:

If anyone was seriously concerned about real estate usage in the WSJT-X
user window there wouldn't be all that wasted space in the lower left
corner for any of the modes.  The Frequency display doesn't need to be
anywhere near that large, DX Call and DX Grid is mostly superfluous, the
size of the Date/Time box is ridiculous ...   and all of that could be
resized and repositioned under the Auto Seq and Call 1st buttons.

All of which has been brought up before.

Dave   AB7E

On 11/19/2019 2:36 PM, Grant VK5GR wrote:
> Joe,
>
> As for the band activity window - yes screen realestate is cluttered as it
> stands - but not being able to see the band activity is an extremely serious
> problem on the air. The "workarounds" proposed are just that - workarounds.
> Not all Fox operators will be that savvy (although I wish I had thought of
> the tail ALL.TXT idea out on the island).
>
> Regards,
> Grant
>


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Fwd: 40 Meter Power USB-D issue

2019-11-20 Thread Paul Randall
Does it do it when the rig is running into a dummy load?



Sent from my Samsung Galaxy smartphone.


 Original message 
From: Christopher Diederich via wsjt-devel 
Date: 20/11/2019 01:59 (GMT+00:00)
To: wsjt-devel@lists.sourceforge.net, wsjt-devel-ow...@lists.sourceforge.net
Cc: Christopher Diederich 
Subject: [wsjt-devel] Fwd: 40 Meter Power USB-D issue


Get Outlook for iOS

From: Christopher Diederich 
Sent: Tuesday, November 19, 2019 8:26 PM
To: wsjtgr...@yahoogroups.com
Subject: 40 Meter Power USB-D issue

Good evening,

I am experiencing a recent issue that has arisen where my IC-7300 is 
transmitting on reduced power on 40 meters using FT8 with WSJT-X.  Other 
digital modes and phone work fine, and no other bands have the low power issue. 
 Also, the rig occasionally changes from USB-D to USB when keying. Any ideas?

IC-7300
Win 10 Pro 64 bit
HRD version 6.7.0.244
WSJT-X version 2.1.0

73
Chris Diederich K1LDO


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel