Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

2017-11-25 Thread Bill Somerville 

On 26/11/2017 02:34, carc...@gmail.com wrote:

So, on to Mac OS 10.13.1:

When I try and run WSJT-X the "splash screen" briefly appears then get 
"Shared Memory Error", unable to create shared memory segment. 
Followed by "Fatal error, shared memory error", yes, related.


OM,

please read the ReadMe.txt file at the root directory of the installer 
DMG, it contains important instructions needed to prepare you Mac for 
use with WSJT-X.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

2017-11-25 Thread Bill Somerville 

Hi OM,

some comments in line below.

On 26/11/2017 02:34, carc...@gmail.com wrote:
Today I tried 1.8.0 release. After a few transmits the waterfall 
window would freeze.
Closing the program via the "X" in the upper right hand corner seemed 
to work, but
upon trying to start up WSJT-X again I'd get the lock file hadn't been 
deleted.


Task manager wouldn't find the executable running, but I still can't 
delete the lock file,

claiming that some program has it locked.
Boot, delete the lock file, start WSJT-X again, and eventually get the 
same results.
I seem to remember someone early-on suggesting using the "File" menu 
to exit

the program, so this problem still exists?
I suspect there is a problem with the reliability of your audio 
connections to your rig. How is your rig connected to your PC for audio?


Another problem, with the Yaesu FT-857d (4800 bps, eight bits, 1 stop 
bit) always
after transmitting the program would complain about timing out when 
trying to read
the frequency. This would occasionally also occur in 1.7.0. Now it 
happens after

every transmission.

When running FT8 retrying to establish communications with the radio 
would re-establish, but probably too late. I couldn't see if anyone 
was responding.


Make sure you do not have "Settings->Radio->Allow Tx frequency changes 
while transmitting" checked as that is not possible with the Yaesu 
FT-817/857/897(D) series of rigs.


If you are using some form of VOX, particularly the SignaLink USB for 
audio then reduce any VOX delay to the minimum. It can also help to 
switch to CAT PTT rather than VOX, even with the SignaLink USB.


73
Bill
G4WJS.


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Windows 10 multiple problems and OS X 10.13.1 problems

2017-11-25 Thread carcarx 
I changed QTHs and am now in a condo, so it's rare for me to get my
multiband
vertical up on its tripod to operate.

Earlier in the summer I'd used 1.8.0 RC1 and operated FT8 enough to get my
sig spotted.

Today I tried 1.8.0 release. After a few transmits the waterfall window
would freeze.
Closing the program via the "X" in the upper right hand corner seemed to
work, but
upon trying to start up WSJT-X again I'd get the lock file hadn't been
deleted.

Task manager wouldn't find the executable running, but I still can't delete
the lock file,
claiming that some program has it locked.
Boot, delete the lock file, start WSJT-X again, and eventually get the same
results.
I seem to remember someone early-on suggesting using the "File" menu to exit
the program, so this problem still exists?

Another problem, with the Yaesu FT-857d (4800 bps, eight bits, 1 stop bit)
always
after transmitting the program would complain about timing out when trying
to read
the frequency. This would occasionally also occur in 1.7.0. Now it happens
after
every transmission.

When running FT8 retrying to establish communications with the radio would
re-establish, but probably too late. I couldn't see if anyone was
responding.

FLDIGI/FLRIG run fine.

Earlier in the summer I was using a hardwired USB connection. I'd have to
sit
outside on the balcony of my condo to operate. I'd overheat.

Got a Rigblaster Blue so that I could sit inside. Connection seems to be
fine, but
after a bit, trying to turn off Bluetooth,
Windows never seems to finish starting up the Bluetooth settings so that I
can even
get to the point to see what's connected and/or turn Bluetooth off.

Windows 10 machine is a Sony Vaio Intel i7 @ 1.6Ghz, with 6 GB RAM

Any log files I can contribute to help debug this?

So, on to Mac OS 10.13.1:

When I try and run WSJT-X the "splash screen" briefly appears then get
"Shared Memory Error", unable to create shared memory segment. Followed by
"Fatal error, shared memory error", yes, related.

Help!

Thanks! 73 de KH6CP
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Split frequency logging

2017-11-25 Thread Dan Malcolm 
Very cool Mike.  Thanks

__
Dan – K4SHQ

From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Saturday, November 25, 2017 6:55 AM
To: WSJT software development 
Cc: Black Michael 
Subject: Re: [wsjt-devel] Split frequency logging

That change is in beta testing for JTAlert right now.  And it's working

[Inline image]

de Mke W9MDB

On Saturday, November 25, 2017, 5:48:59 AM CST, Dan Malcolm 
> wrote:


Claude et al,
Exactly.  That's why this is a development question.  The ADIF fields are
there, and apparently not being used, or I missed a setting somewhere.

I agree in principle with Karl.  Too much automation is not a good thing.
But as long as frequency is being logged, it should be done with the correct
frequencies.  If the WSJT-X developers don't want to deal with it fine.
Just say so and I'll continue manual corrections.  Not a big deal, but was
curious.

__
Dan – K4SHQ

-Original Message-
From: Claude Frantz 
[mailto:claude.fra...@bayern-mail.de]
Sent: Wednesday, November 22, 2017 9:43 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency logging

On 11/22/2017 02:25 PM, Dan Malcolm wrote:

Hi Dan & all,

> WSJT-X is pretty good at running QSO’s with ‘split’ frequency
> operation.  JTAlert is essential for smooth QSO tracking and logging.
> What I am missing is logging the separate frequencies for a split QSO.
> I suspect that most ops don’t track the different Tx and Rx
> frequencies, but I do.  Perhaps the data manager in me.
The ADIF specification defines a FREQ field containing the TX frequency in
MHz and an additional FREQ_RX field containing the RX frequency in MHz, in
the case of split operation.

Best wishes,
Claude (DJ0OT)


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Call change while logging

2017-11-25 Thread Bill Somerville 

On 25/11/2017 13:17, Black Michael via wsjt-devel wrote:
There's a problem logging with JTAlert (and perhaps other apps too) if 
you leave the logging dialog box open and change the active call sign.


JTAlert maintains the additional logging info by the active call 
signlike countryso you may end up logging the wrong country.


There's a potential fix for WSJT-X that's not too oneroussimply 
disalow changing the DX Call while the logging box is open...simply 
disable it (to make it obvious) and reenable after logging.


I'll be happy to make that patch if deemed appropriate.

de Mike W9MDB


Hi Mike,

that issue is not due to WSJT-X and I don't think a change in WSJT-X is 
warranted. There is nothing wrong with starting a new QSO before logging 
the prior one, no information is lost as the Log QSO window holds the 
information until the "Ok" button is pressed.


I believe the issue is that JTAlert looks up the country for the call 
sign, surely it can do that for the call sign in the Log QSO UDP record, 
in fact it really should as a QSO may have been completed with a 
compound call holder without their prefix/suffix being exchanged during 
the QSO even though it is known from prior decodes. The user could quite 
reasonably log a prefix or suffix that was never in the DX Call field.


73
Bill
G4WJS.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Call change while logging

2017-11-25 Thread Black Michael via wsjt-devel 
There's a problem logging with JTAlert (and perhaps other apps too) if you 
leave the logging dialog box open and change the active call sign.
JTAlert maintains the additional logging info by the active call signlike 
countryso you may end up logging the wrong country.
There's a potential fix for WSJT-X that's not too oneroussimply disalow 
changing the DX Call while the logging box is open...simply disable it (to make 
it obvious) and reenable after logging.
I'll be happy to make that patch if deemed appropriate.
de Mike W9MDB

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Split frequency logging

2017-11-25 Thread Black Michael via wsjt-devel 
That change is in beta testing for JTAlert right now.  And it's working




de Mke W9MDB

On Saturday, November 25, 2017, 5:48:59 AM CST, Dan Malcolm 
 wrote:  
 
 Claude et al,
Exactly.  That's why this is a development question.  The ADIF fields are
there, and apparently not being used, or I missed a setting somewhere.  

I agree in principle with Karl.  Too much automation is not a good thing.
But as long as frequency is being logged, it should be done with the correct
frequencies.  If the WSJT-X developers don't want to deal with it fine.
Just say so and I'll continue manual corrections.  Not a big deal, but was
curious.

__
Dan – K4SHQ

-Original Message-
From: Claude Frantz [mailto:claude.fra...@bayern-mail.de] 
Sent: Wednesday, November 22, 2017 9:43 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency logging

On 11/22/2017 02:25 PM, Dan Malcolm wrote:

Hi Dan & all,

> WSJT-X is pretty good at running QSO’s with ‘split’ frequency 
> operation.  JTAlert is essential for smooth QSO tracking and logging.
> What I am missing is logging the separate frequencies for a split QSO. 
> I suspect that most ops don’t track the different Tx and Rx 
> frequencies, but I do.  Perhaps the data manager in me.
The ADIF specification defines a FREQ field containing the TX frequency in
MHz and an additional FREQ_RX field containing the RX frequency in MHz, in
the case of split operation.

Best wishes,
Claude (DJ0OT)


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel  --
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Split frequency logging

2017-11-25 Thread Dan Malcolm 
Claude et al,
Exactly.  That's why this is a development question.  The ADIF fields are
there, and apparently not being used, or I missed a setting somewhere.  

I agree in principle with Karl.  Too much automation is not a good thing.
But as long as frequency is being logged, it should be done with the correct
frequencies.  If the WSJT-X developers don't want to deal with it fine.
Just say so and I'll continue manual corrections.  Not a big deal, but was
curious.

__
Dan – K4SHQ

-Original Message-
From: Claude Frantz [mailto:claude.fra...@bayern-mail.de] 
Sent: Wednesday, November 22, 2017 9:43 AM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] Split frequency logging

On 11/22/2017 02:25 PM, Dan Malcolm wrote:

Hi Dan & all,

> WSJT-X is pretty good at running QSO’s with ‘split’ frequency 
> operation.  JTAlert is essential for smooth QSO tracking and logging.
> What I am missing is logging the separate frequencies for a split QSO. 
> I suspect that most ops don’t track the different Tx and Rx 
> frequencies, but I do.  Perhaps the data manager in me.
The ADIF specification defines a FREQ field containing the TX frequency in
MHz and an additional FREQ_RX field containing the RX frequency in MHz, in
the case of split operation.

Best wishes,
Claude (DJ0OT)


--
Check out the vibrant tech community on one of the world's most engaging
tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel