[wsjt-devel] Double logging contacts

2020-09-21 Thread Bill Mullin
When the "Log QSO" window pops up, a single click on OK will log the 
contact.  But I've discovered when things are moving quickly, especially 
on FT4, that I sometimes accidentally double click on the "OK" button 
which caused the QSO to be logged twice.  Is it possible to tell the 
program that single or double clicks on this button are to be treated 
the same?


Thanks & 73,
Bill - AA4M

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


[wsjt-devel] 2 suggestions

2020-09-10 Thread Bill Mullin
After 22 months and 17,000(+) Q's, I have 2 suggestions for WSJT-X, both 
which I believe will be simple to implement.


- Twice now I've accidentally left  tune ON and left the room!  If tune 
was limited to 15 seconds or so, this could never happen again.  Better 
yet, make it possible for the user to optionally set his/her maximum 
tune time.


- I generally operate with the menus OFF.  Changing modes back and forth 
from FT8 & FT4 takes a number of clicks.  A nice shortcut would be 
allowing the 2nd block from the lower left to also be used for changing 
modes.


Other than these minor suggestions, the program is sensational. Better 
yet, after losing most of my hearing and being off the air for 21+ 
years, WSJT-X allowed me to return to ham radio!


73, Bill  AA4M

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


Re: [wsjt-devel] Drop down band-selector list problem

2020-06-09 Thread Bill Mullin

Oops, I'll try again, sorry!

Hello Bill,

I'm not sure what you're talking about?  Here's the list without the 7.071:

http://aa4m.com/Pic1.jpg

And here it is with the 7.071:

http://aa4m.com/Pic2.jpg

73, Bill  AA4M
Tucson, AZ

On 06/09/2020 08:30:04, Bill Somerville wrote:

On 09/06/2020 16:14, Bill Mullin wrote:
Here's something to think about.  When I added 7.071 to the menu, 
this should have made no difference to the drop down menu since the 
characters "7.071" are the same width or even smaller than many of 
the other lines in the menu. It makes no sense that this would have 
caused the truncation of ANY characters.


Hi Bill,

are you sure you added 7.071 MHz? I ask because I only see one 40m 
frequency on your messed up drop down list. When you enter new working 
frequencies the entry is in MHz i.e. 7.071 . If you entered 7071 that 
that is 7.071 GHz.


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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] Drop down band-selector list problem

2020-06-09 Thread Bill Mullin

Hello Bill,

I'm not sure what you're talking about?  Here's the list without the 7.071:

http://aa4m.com/Pic1.jpg

And here it is with the 7.071:

http://aa4m.com/Pic2.jpg <http://aa4m.com/Pic1.jpg>

73, Bill  AA4M
Tucson, AZ

On 06/09/2020 08:30:04, Bill Somerville wrote:

On 09/06/2020 16:14, Bill Mullin wrote:
Here's something to think about.  When I added 7.071 to the menu, 
this should have made no difference to the drop down menu since the 
characters "7.071" are the same width or even smaller than many of 
the other lines in the menu. It makes no sense that this would have 
caused the truncation of ANY characters.


Hi Bill,

are you sure you added 7.071 MHz? I ask because I only see one 40m 
frequency on your messed up drop down list. When you enter new working 
frequencies the entry is in MHz i.e. 7.071 . If you entered 7071 that 
that is 7.071 GHz.


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


Re: [wsjt-devel] Drop down band-selector list problem

2020-06-09 Thread Bill Mullin

Hey Reino,

I've tried dragging the border to the right with no luck.  Being able to 
enlarge the window such as you have done would solve the problem 
forever! :-)


73, Bill


On 06/09/2020 08:14:29, Reino Talarmo wrote:


Hello Bill,

Thanks for the pictures. I myself use Windows PrtSc key take copy of 
the screen (or just the active window by Alt+PrtSc, does not work in 
this case) and insert that into Paint. There I select the part I want 
to paste and Copy it. Then I can past it into the mail as below. This 
requires that also recipient has HTML support in mail.


The issue you presented is a full question mark to me. As you see in 
my screen the frequency list is much wider and all fits in!


Unfortunately I am just a user of the program and cannot tell whether 
there is a simple corrective action available. Perhaps font size 
change could affect. At least an excessive font size 20 caused the 
same display as you have!


The circled S is explained in section 10.3. Left in User Guide:

A small colored circle appears in green if the CAT control is 
activated and functional. The green circle contains the character S if 
the rig is detected to be in *Split* mode. The circle becomes red if 
you have requested CAT control but communication with the radio has 
been lost.


73, Reino OH3mA

*From:*Bill Mullin [mailto:mrb...@aa4m.com]
*Sent:* 9. kesäkuuta 2020 16:39
*To:* Reino Talarmo ; 
wsjt-devel@lists.sourceforge.net

*Subject:* Re: [wsjt-devel] Drop down band-selector list problem

Hello Reino,

For some reason my screen capture program would not work with the drop 
down menu, so I photographed the before and after menus.


This is the menu before adding another FT8 frequency:

http://aa4m.com/Pic1.jpg

And this is the menu after adding 7.071, FT8, All regions:

http://aa4m.com/Pic2.jpg

As you can see, the menu is still usable, it is just a little truncated.

While at it, what is the "S" in the green circle for?

Thanks & 73, Bill  AA4M


On 06/09/2020 00:11:29, Reino Talarmo wrote:

Hi Bill,

You may add a picture into the mail itself using HTML encoding.
Just make a copy of the picture and drop it into the mail.

Without a picture it is impossible to comment what you really see
and how exactly you added those using Menu. Do you mean by
‘manually’ that you typed frequency into the box left to the
circle and frequency display? Is the frequency display background
still black or does it change into red?

I cannot repeat your symptoms in my v2.2.1. I am using Finnish
keyboard and I need to use ‘,’ as decimal separator. If I try to
use ‘.’ then it is just ignored and e.g. 7.041 it taken as 7041
MHz. But that may not be you issue.

Did you added frequencies for ‘FT8 mode’ only, not ‘all’?

73, Reino OH3mA

    *From:*Bill Mullin [mailto:mrb...@aa4m.com]
*Sent:* 9. kesäkuuta 2020 4:20
*To:* wsjt-devel@lists.sourceforge.net
<mailto:wsjt-devel@lists.sourceforge.net>
*Subject:* [wsjt-devel] Drop down band-selector list problem

I posted this in another forum but got no answer, so I thought I'd
try here.

This problem is difficult to describe!  From the new WSJT-X 2.2.1
user's manual:

"On a trial basis, and in response to numerous suggestions from around
the world, we have added a second set of suggested dial frequencies
for FT8 on three HF bands and also on 6 meters. The new suggested dial
frequencies are 7.071, 10.133, 14.071, and 50.310 MHz. These
frequencies will appear in your drop-down band-selector list after you
go to the "Settings | Frequencies" tab, right-click on the frequency
table, and select "Reset".  Alternatively, you can add the new FT8
frequencies manually."

I tried adding the new frequencies both using the menus and then
manually.  In both cases the FT8 portion of the drop down
band-selector list become somewhat truncated. The list is still
usable so this should be considered a cosmetic problem only.

Note that I'd include a picture of the scrambled menu if I thought
the group accepted attachments.  Note also the the FT4 menu is not
affected by additions to the FT8 menu.

73, Bill - AA4M



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


Re: [wsjt-devel] Drop down band-selector list problem

2020-06-09 Thread Bill Mullin
My settings are Arial, Regular, Bold, 8.  Your settings also caused the 
truncation on my WSJT display.


My full display is set for 1600x900, I tried a number of different 
display modes but none made any difference.  So I reset Arial, Bold, 8 
to Arial, Regular, 8 with no difference.  So then I tried Arial, Bold, 7 
which fixed the problem.  But - the reason I use Bold/8 is that it is 
easier on my 75 year old eyes!  Having to reduce font size or change 
from bold to regular creates new problems for me.


Here's something to think about.  When I added 7.071 to the menu, this 
should have made no difference to the drop down menu since the 
characters "7.071" are the same width or even smaller than many of the 
other lines in the menu.  It makes no sense that this would have caused 
the truncation of ANY characters.


Again, this is a trivial problem, but if I was a programmer in the WSJT 
group I'd certainly want to look into this oddity!


G3WJS - shutting down the program and restarting makes no difference.  
Even a full reboot does not resolve the problem.


73, Bill - AA4M


On 06/09/2020 06:50:04, Gene H wrote:


Curious what your fonts are that you are using. Looks like they may be 
too large to fit the text in the GUI. Here are mine:


On 6/9/2020 8:38 AM, Bill Mullin wrote:

Hello Reino,

For some reason my screen capture program would not work with the 
drop down menu, so I photographed the before and after menus.


This is the menu before adding another FT8 frequency:

http://aa4m.com/Pic1.jpg

And this is the menu after adding 7.071, FT8, All regions:

http://aa4m.com/Pic2.jpg

As you can see, the menu is still usable, it is just a little truncated.

While at it, what is the "S" in the green circle for?

Thanks & 73, Bill  AA4M


On 06/09/2020 00:11:29, Reino Talarmo wrote:


Hi Bill,

You may add a picture into the mail itself using HTML encoding. Just 
make a copy of the picture and drop it into the mail.


Without a picture it is impossible to comment what you really see 
and how exactly you added those using Menu. Do you mean by 
‘manually’ that you typed frequency into the box left to the circle 
and frequency display? Is the frequency display background still 
black or does it change into red?


I cannot repeat your symptoms in my v2.2.1. I am using Finnish 
keyboard and I need to use ‘,’ as decimal separator. If I try to use 
‘.’ then it is just ignored and e.g. 7.041 it taken as 7041 MHz. But 
that may not be you issue.


Did you added frequencies for ‘FT8 mode’ only, not ‘all’?

73, Reino OH3mA

*From:*Bill Mullin [mailto:mrb...@aa4m.com]
*Sent:* 9. kesäkuuta 2020 4:20
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* [wsjt-devel] Drop down band-selector list problem

I posted this in another forum but got no answer, so I thought I'd 
try here.


This problem is difficult to describe!  From the new WSJT-X 2.2.1 
user's manual:


"On a trial basis, and in response to numerous suggestions from around
the world, we have added a second set of suggested dial frequencies
for FT8 on three HF bands and also on 6 meters. The new suggested dial
frequencies are 7.071, 10.133, 14.071, and 50.310 MHz. These
frequencies will appear in your drop-down band-selector list after you
go to the "Settings | Frequencies" tab, right-click on the frequency
table, and select "Reset".  Alternatively, you can add the new FT8
frequencies manually."

I tried adding the new frequencies both using the menus and then 
manually.  In both cases the FT8 portion of the drop down 
band-selector list become somewhat truncated. The list is still 
usable so this should be considered a cosmetic problem only.


Note that I'd include a picture of the scrambled menu if I thought 
the group accepted attachments.  Note also the the FT4 menu is not 
affected by additions to the FT8 menu.


73, Bill - AA4M





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

--
Gene Hinkle
9109 Topridge Drive, Austin, TX 78750
e-mail to Gene:ghin...@gmail.com
cell phone or text messaging:  (512) 413-9251
--


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


Re: [wsjt-devel] Drop down band-selector list problem

2020-06-09 Thread Bill Mullin

Hello Reino,

For some reason my screen capture program would not work with the drop 
down menu, so I photographed the before and after menus.


This is the menu before adding another FT8 frequency:

http://aa4m.com/Pic1.jpg

And this is the menu after adding 7.071, FT8, All regions:

http://aa4m.com/Pic2.jpg

As you can see, the menu is still usable, it is just a little truncated.

While at it, what is the "S" in the green circle for?

Thanks & 73, Bill  AA4M


On 06/09/2020 00:11:29, Reino Talarmo wrote:


Hi Bill,

You may add a picture into the mail itself using HTML encoding. Just 
make a copy of the picture and drop it into the mail.


Without a picture it is impossible to comment what you really see and 
how exactly you added those using Menu. Do you mean by ‘manually’ that 
you typed frequency into the box left to the circle and frequency 
display? Is the frequency display background still black or does it 
change into red?


I cannot repeat your symptoms in my v2.2.1. I am using Finnish 
keyboard and I need to use ‘,’ as decimal separator. If I try to use 
‘.’ then it is just ignored and e.g. 7.041 it taken as 7041 MHz. But 
that may not be you issue.


Did you added frequencies for ‘FT8 mode’ only, not ‘all’?

73, Reino OH3mA

*From:*Bill Mullin [mailto:mrb...@aa4m.com]
*Sent:* 9. kesäkuuta 2020 4:20
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* [wsjt-devel] Drop down band-selector list problem

I posted this in another forum but got no answer, so I thought I'd try 
here.


This problem is difficult to describe!  From the new WSJT-X 2.2.1 
user's manual:


"On a trial basis, and in response to numerous suggestions from around
the world, we have added a second set of suggested dial frequencies
for FT8 on three HF bands and also on 6 meters. The new suggested dial
frequencies are 7.071, 10.133, 14.071, and 50.310 MHz. These
frequencies will appear in your drop-down band-selector list after you
go to the "Settings | Frequencies" tab, right-click on the frequency
table, and select "Reset".  Alternatively, you can add the new FT8
frequencies manually."

I tried adding the new frequencies both using the menus and then 
manually.  In both cases the FT8 portion of the drop down 
band-selector list become somewhat truncated.  The list is still 
usable so this should be considered a cosmetic problem only.


Note that I'd include a picture of the scrambled menu if I thought the 
group accepted attachments.  Note also the the FT4 menu is not 
affected by additions to the FT8 menu.


73, Bill - AA4M



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


[wsjt-devel] Drop down band-selector list problem

2020-06-08 Thread Bill Mullin

I posted this in another forum but got no answer, so I thought I'd try here.

This problem is difficult to describe!  From the new WSJT-X 2.2.1 user's 
manual:


"On a trial basis, and in response to numerous suggestions from around
the world, we have added a second set of suggested dial frequencies
for FT8 on three HF bands and also on 6 meters. The new suggested dial
frequencies are 7.071, 10.133, 14.071, and 50.310 MHz.  These
frequencies will appear in your drop-down band-selector list after you
go to the "Settings | Frequencies" tab, right-click on the frequency
table, and select "Reset".  Alternatively, you can add the new FT8
frequencies manually."

I tried adding the new frequencies both using the menus and then 
manually.  In both cases the FT8 portion of the drop down band-selector 
list become somewhat truncated.  The list is still usable so this should 
be considered a cosmetic problem only.


Note that I'd include a picture of the scrambled menu if I thought the 
group accepted attachments.  Note also the the FT4 menu is not affected 
by additions to the FT8 menu.


73, Bill - AA4M
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] WSJT-X not finding microphone!

2019-11-13 Thread Bill Mullin
OK, things seem about back to normal. My Codec microphone gain and 
speaker gain both have a range of 1-100.  I've set both at 50, them made 
a few QSO's.  Does 50 seem about right?


BTW, fixing this problem was 99% guesswork and 1% skill.  I have no idea 
what I did to scramble things up or what I did to fix them, I just hope 
I never have to go through this again!


I'm glad I resolved this problem since VK9CZ has been spotted on FT8 and 
I need this for a digital ATNO!  :)


73, AA4M



On 11/13/2019 16:27:02, Bill Mullin wrote:
I'm getting closer.  I have no idea how I did it, but the S-meter is 
now showing full scale and bright red (clipping).  I'm getting light 
copy out of a crowded band, which I guess is a step in the right 
direction, but how do I get the receive gain down to a respectable level?


Thanks, Bill  AA4M


On 11/13/2019 13:53:19, Bill Mullin wrote:
Yesterday, no problems at all.  First thing this morning WSJT is 
giving me messages that there are audio sound input problems.  I 
spent a LONG time researching this and ultimately found that the 
microphone is not being recognized.  I've been to the Windows 
microphone privacy permissions page and ensured that the proper 
permissions were in place.  I've turned the permissions off then off, 
then rebooted with no luck.  The permission page also told me that 
the last connection to the microphone was yesterday by WSJT-X.


Later:  I've also discovered that DXLab Commander is not having any 
problem hearing signals and is reading signals on its S-meter.  
WSJT-X is OK on transmit, but the S-meter is flat and the program is 
not copying anything.  I've uninstalled and installed both WSJT-X and 
the audio drivers 1.30 but the problem remains the same.  I am using 
an IC-7610 and have an IC-7300 as a backup Xcvr.  I just substituted 
the 7300 for the 7610 and found the problem is exactly the same. The 
clock is dead on accurate.


I'm stumped - what do I need to do to get WSJT-X to recognize the 
microphone audio input?


Thanks & 73,
Bill - AA4M



___
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] WSJT-X not finding microphone!

2019-11-13 Thread Bill Mullin
I'm getting closer.  I have no idea how I did it, but the S-meter is now 
showing full scale and bright red (clipping).  I'm getting light copy 
out of a crowded band, which I guess is a step in the right direction, 
but how do I get the receive gain down to a respectable level?


Thanks, Bill  AA4M


On 11/13/2019 13:53:19, Bill Mullin wrote:
Yesterday, no problems at all.  First thing this morning WSJT is 
giving me messages that there are audio sound input problems.  I spent 
a LONG time researching this and ultimately found that the microphone 
is not being recognized. I've been to the Windows microphone privacy 
permissions page and ensured that the proper permissions were in 
place.  I've turned the permissions off then off, then rebooted with 
no luck.  The permission page also told me that the last connection to 
the microphone was yesterday by WSJT-X.


Later:  I've also discovered that DXLab Commander is not having any 
problem hearing signals and is reading signals on its S-meter.  WSJT-X 
is OK on transmit, but the S-meter is flat and the program is not 
copying anything.  I've uninstalled and installed both WSJT-X and the 
audio drivers 1.30 but the problem remains the same.  I am using an 
IC-7610 and have an IC-7300 as a backup Xcvr.  I just substituted the 
7300 for the 7610 and found the problem is exactly the same.  The 
clock is dead on accurate.


I'm stumped - what do I need to do to get WSJT-X to recognize the 
microphone audio input?


Thanks & 73,
Bill - AA4M



___
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] WSJT-X not finding microphone!

2019-11-13 Thread Bill Mullin
Yesterday, no problems at all.  First thing this morning WSJT is giving 
me messages that there are audio sound input problems.  I spent a LONG 
time researching this and ultimately found that the microphone is not 
being recognized. I've been to the Windows microphone privacy 
permissions page and ensured that the proper permissions were in place.  
I've turned the permissions off then off, then rebooted with no luck.  
The permission page also told me that the last connection to the 
microphone was yesterday by WSJT-X.


Later:  I've also discovered that DXLab Commander is not having any 
problem hearing signals and is reading signals on its S-meter.  WSJT-X 
is OK on transmit, but the S-meter is flat and the program is not 
copying anything.  I've uninstalled and installed both WSJT-X and the 
audio drivers 1.30 but the problem remains the same.  I am using an 
IC-7610 and have an IC-7300 as a backup Xcvr.  I just substituted the 
7300 for the 7610 and found the problem is exactly the same.  The clock 
is dead on accurate.


I'm stumped - what do I need to do to get WSJT-X to recognize the 
microphone audio input?


Thanks & 73,
Bill - AA4M

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


[wsjt-devel] Missing QSO's

2019-09-24 Thread Bill Mullin
I was just checking and found that my WSJTX.log file contains 6,950 
QSO's, whereas my wsjtx_log.adi file contains 3 less QSO's,  Is there an 
easy way to import the missing Q's into the wsjtx_log.adi file?  Better 
yet, is there a way to fully import the WSJTX.log file to the 
wsjtx_log.adi file?


73, Bill - AA4M



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


Re: [wsjt-devel] Please read: Windows users installing the latest v2.1.0 GA 64-bit version

2019-07-18 Thread Bill Mullin

Which folder should this new file be installed into?

Thanks/73,
Bill  AA4M

On 2019-07-18 00:38:22, Tom Ramberg via wsjt-devel wrote:
Could you please provide a link to the installation file of 
WIN64_OpenSSL_1.1.0k_Light?


73 de OH6VDA Tom
Sendt fra min iPad Air 2

18. jul. 2019 kl. 01:39 skrev Bill Somerville >:



Hi,

you may get an SSL/TLS network error when fetching a fresh LoTW users 
database ("Settings->Colors->Logbook of the World User Validation"). 
The WSJT-X User Guide current states that the OpenSSL v1.0.2 
libraries are required for this to work, this is incorrect for the 
64-bit version of WSJT-X, that requires the latest v1.1.0 version of 
the OpenSSL libraries. The instructions are the same except use the 
Win64_OpenSSL_v1.1.0k_Light package for the 64-bit version of WSJT-X.


Apologies for the release notice not containing this information, I 
have only just discovered this new dependency.


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 mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] What's causing this?

2019-03-04 Thread Bill Mullin
Another question - is there any way to turn off the time/band indicators 
at the left of the grid, without changing the height of the listening 
segments?


Thanks, AA4M

On 2019-03-04 06:55:47, Bill Somerville wrote:

Hi Bill,

looks like you have the notch filter engaged on your receiver.

73
Bill
G4WJS.

On 04/03/2019 13:52, Bill Mullin wrote:

Like this:
*
**http://aa4m.com/links/Flatten_Off.jpg*

That's definitely not the fix!

73

On 2019-03-04 06:39:47, Black Michael via wsjt-devel wrote:

What does it look like with Flatten turned off?

de Mike W9MDB




On Monday, March 4, 2019, 7:36:18 AM CST, Bill Mullin 
 wrote:



I have "dead space" running from about 1300 - 1700 on all bands:

*http://aa4m.com/links/Problem.jpg*

This screen capture shows that this dead space is in the same 
location on 80, 40, 30, and 20 meters.  I'm running WSJT-X 2.0.1 and 
have been since the day it came out.  This problem started 
yesterday, so I don't think it's a glitch in the program.  I've 
probably (accidentally) screwed up a parameter but I have no idea 
which one.  Can anyone help?


73, Bill - AA4M





___
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] What's causing this?

2019-03-04 Thread Bill Mullin
That was it, I was using the notch during the ARRL SSB contest and 
forgot to turn it off!


Thank you Bill, George & Mike!

73, Bill - AA4M

On 2019-03-04 06:55:47, Bill Somerville wrote:

Hi Bill,

looks like you have the notch filter engaged on your receiver.

73
Bill
G4WJS.

On 04/03/2019 13:52, Bill Mullin wrote:

Like this:
*
**http://aa4m.com/links/Flatten_Off.jpg*

That's definitely not the fix!

73

On 2019-03-04 06:39:47, Black Michael via wsjt-devel wrote:

What does it look like with Flatten turned off?

de Mike W9MDB




On Monday, March 4, 2019, 7:36:18 AM CST, Bill Mullin 
 wrote:



I have "dead space" running from about 1300 - 1700 on all bands:

*http://aa4m.com/links/Problem.jpg*

This screen capture shows that this dead space is in the same 
location on 80, 40, 30, and 20 meters.  I'm running WSJT-X 2.0.1 and 
have been since the day it came out.  This problem started 
yesterday, so I don't think it's a glitch in the program.  I've 
probably (accidentally) screwed up a parameter but I have no idea 
which one.  Can anyone help?


73, Bill - AA4M





___
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] What's causing this?

2019-03-04 Thread Bill Mullin

Like this:
*
**http://aa4m.com/links/Flatten_Off.jpg*

That's definitely not the fix!

73

On 2019-03-04 06:39:47, Black Michael via wsjt-devel wrote:

What does it look like with Flatten turned off?

de Mike W9MDB




On Monday, March 4, 2019, 7:36:18 AM CST, Bill Mullin 
 wrote:



I have "dead space" running from about 1300 - 1700 on all bands:

*http://aa4m.com/links/Problem.jpg*

This screen capture shows that this dead space is in the same location 
on 80, 40, 30, and 20 meters.  I'm running WSJT-X 2.0.1 and have been 
since the day it came out.  This problem started yesterday, so I don't 
think it's a glitch in the program.  I've probably (accidentally) 
screwed up a parameter but I have no idea which one.  Can anyone help?


73, Bill - AA4M

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net <mailto: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


[wsjt-devel] What's causing this?

2019-03-04 Thread Bill Mullin

I have "dead space" running from about 1300 - 1700 on all bands:

*http://aa4m.com/links/Problem.jpg*

This screen capture shows that this dead space is in the same location 
on 80, 40, 30, and 20 meters.  I'm running WSJT-X 2.0.1 and have been 
since the day it came out.  This problem started yesterday, so I don't 
think it's a glitch in the program.  I've probably (accidentally) 
screwed up a parameter but I have no idea which one.  Can anyone help?


73, Bill - AA4M

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


[wsjt-devel] F/H, hound unable to transmit on even times!

2019-03-02 Thread Bill Mullin

New member here, forgive me if this has been asked before!

T31EU was on 3.574 in F/H mode, at least I thought he was after seeing 
the following line:


   134545 -6 2.5 489 ~ JA0EBV RR73; UK8AEA  -14


As you can see, the Fox was transmitting on the odd seconds (15, 45).  
But WSJT-X would not allow me to transmit on the even times (00, 30), 
only on the odds.  Because of this, I was unable to work the Fox.  I dug 
in the F/H documentation and saw no requirement that the Fox transmit on 
the even times.  So is this a bug in 2.0.1 or was I doing something 
wrong?  I also reloaded 2.0.0 as a test, but again I was unable to 
transmit as a Hound on even times.


Maybe I should ask if there is a requirement in F/H that the Fox stay on 
even times and the Hound on odd?  If so, how do you explain the above 
F/H line from T31EU?


73, Bill - AA4M

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


[wsjt-devel] OpenSSL Questions

2018-12-22 Thread Bill Mullin

The following information is from the 2.0.0 FT8 User's guide:

 *

   You can download a suitable /OpenSSL/ package from _Windows OpenSSL
   Packages_, you need the latest *Win32 v1.0.2 Lite* version (Note it
   is the Win32 package even if you are using a 64-bit Windows
   operating system) which at the time of writing was _Win32 OpenSSL
   Lite__Package_.

 *

   Install the package and accept the default options, including the
   option to copy the /OpenSSL/ DLLs to the Windows system directory
   (this is important).

I located the package, the current version is 
_*Win64OpenSSL_Light-1_1_0j*_, which I'm sure makes no difference.  
FWIW, there is a 1.0.2j lite also available.


When attempting to install, the default directory for the install was 
given as _*C:\OpenSSL-Win64*_ which I'm sure is wrong!  So my question 
is:  which system folder should I be installing to:  C:\Windows\System, 
C:\Windows\System32, or C:\Windows\SysWOW64?  FWIW, I've searched my 
system and found no copies of any files named OpenSSL*.* yet I've had no 
problems . . . so far.


Thanks, Bill - AA4M


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


[wsjt-devel] 200 or 2000 Hz

2018-12-10 Thread Bill Mullin

I asked this question on another list but did not get a usable answer:

With 1.9.1 we were told to use 200 HZ to Start and change this to 2000 
Hz for RC5.  Which should we use for the 2.0.0 GA version?  Is there 
some frequency that may be better than 200 or 2000?


Thanks,
Bill - AA4M

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


Re: [wsjt-devel] Bug Report

2018-12-10 Thread Bill Mullin

On 12/10/18 Mon 9:58 AM, Bill Somerville wrote:

On 10/12/2018 16:48, Bill Mullin wrote:
I'm not seeing color options for "worded before" on my copy of 2.0.0 
GA. I do see "New Call on Band", but this does not seem to be working 
for me.  Note that I only have "My Call", "New Call on Band", 
"Calling CQ", and "Transmitted Message" checked.


Hi Bill,

if you think the "New Call on Band" highlighting is not working 
correctly then you should be able to verify by checking your 
wsjtx_log.adi file for supporting evidence.


E.g. if you see a CQ decode highlighted with the "New Call on Band" 
colours and you think you have worked that station before on the 
current band (and mode if you have "Highlight by Mode" checked as 
well) then can you reply with the ADIF record in your wsjtx_log.adi 
file that shows your previous contact with that station.


Likewise if you think a CQ decode should be highlighted as a new call 
on the band (and mode if you have "Highlight by Mode" checked as well) 
and you have "Settings->General->Show DXCC, grid, and worked before 
status" checked, scan your wsjtx_log.adi file to double check there is 
no record of a QSO with that station on the current band.


73
Bill
G4WJS.


Hello Bill,

That worked!  "Settings->General->Show DXCC, grid, and worked before 
status" checked has resolved that problem.  I never realized that 
getting colors to work properly required a 2nd check in another tab!  I 
do notice that new calls are coming in light blue for "New Call on 
Band", but only when they CQ.  Is that by design or do I have another 
problem.  As things are now I'd be reluctant to tailgate knowing that I 
might be working a duplicate call/band.


Thanks for the great support,
Bill - AA4M



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


Re: [wsjt-devel] Bug Report

2018-12-10 Thread Bill Mullin

Hello Bill,

I'm not seeing color options for "worded before" on my copy of 2.0.0 
GA.  I do see "New Call on Band", but this does not seem to be working 
for me.  Note that I only have "My Call", "New Call on Band", "Calling 
CQ", and "Transmitted Message" checked.


73, Bill - AA4M


On 12/10/18 Mon 9:15 AM, Bill Somerville wrote:

Hi OM,

turning on all the decode highlighting options is probably unwise. 
Unless you have worked almost everything you will get information 
overload. Everyone's DXing objectives are different and also how far 
each of us have progressed towards  of our goals varies. I would 
strongly recommend turning on only a couple of the *worked before 
options* and working towards completing the less onerous ones that you 
have any interest in. For example a new operator on HF might like to 
tick off each continent, then maybe CQ Zones, then getting stuck into 
tracking down new DXCC entities. A VHF and up operator may well start 
straight off with grid squares and depending on their location also 
DXCC entities.


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] WAV files

2018-12-06 Thread Bill Mullin
I posted this with the FT8-digital-mode group but was not able to find a 
fix to the problem.


Looking in the folder C:\Users\*\AppData\Local\WSJT-X\Save, I found 
100's of .WAV files.  I realize that they can be deleted from the WSJT-X 
File menu, but is there any way I can simply tell the program to not 
save them?  Since I'm only interested in having FT8 QSO's rather than 
developing software, I don't think I need them . . . do I?


FWIW, I just set both 1.9.1 and 2.0.0 RC5 for Save > None, deleted all 
my WAV files, then had 2 FT8 QSO's on 18 MHz.  I checked and I now had 4 
new WAV files!  How can I stop these files from being created?


Thanks,
Bill - AA4M

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


[wsjt-devel] 2 Questions

2018-12-03 Thread Bill Mullin
These questions are from my most recent use of 1.9.1.  If changes have 
been made to RC5 which cover the subjects, sorry!


1.  In Settings > Reporting, if I do NOT check "Prompt me to log QSO", 
will WSJT skip logging or do it automatically?  FWIW, I'd hope it was 
the latter since this would remove a minor step in each QSO.


2.  I just started using Tab 2 - much nicer than Tab 1!  Is it possible 
to combine the last 2 steps for CQing and answering CQ to one step each: 
"XX0XX AA4M RR73", thereby ending the QSO?


Thanks, Bill - AA4M

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


[wsjt-devel] Missing grid square info

2018-12-02 Thread Bill Mullin
I'm an FT8 newbie - made my first QSO with this mode less than a week 
ago.  The below problem may have been discussed before and I apologize 
if I missed it.  Anyway, I notice that both my LOG and ADI files are 
randomly missing grid squares. Here's my last 6 QSO's, all made today:


2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,

3 of the 6 grid square information is missing, in spite of the fact that 
it was definitely sent to me.  This group was with 1.9.1.  I also had 16 
QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid 
information in the LOG or ADI file.


Is this a known problem?  Will these missing grids cause me any problems 
in the future?


Tnx & 73,
Bill  AA4M

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