Re: [wsjt-devel] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X? (long crashdump)

2017-07-12 Thread Hisashi T Fujinaka

On Thu, 13 Jul 2017, Bill Somerville wrote:


On 13/07/2017 03:57, Hisashi T Fujinaka wrote:
What rig do you have?


  Elecraft K3. I think it's pretending to be a Kenwood in hamlib.

  Oddly, 1.7.0 was working fine but now that I made some FT8 contacts with
  1.8.0-rc1 it's crashing as well.

Hi Hisashi,

Elecraft use a slighly modified version of the Kenwood CAT protocol which is 
why the Hamlib driver is associated with Kenwood
rigs, ~90% of the functionality is shared.

I will contact you off list with an instrumented version of WSJT-X that will 
allow me to see what is going wrong.

It is late here so I must sleep. It will probably be later today.


Thanks!

--
Hisashi T Fujinaka - ht...@twofifty.com
BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee

--
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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X? (long crashdump)

2017-07-12 Thread Bill Somerville

On 13/07/2017 03:57, Hisashi T Fujinaka wrote:

What rig do you have?


Elecraft K3. I think it's pretending to be a Kenwood in hamlib.

Oddly, 1.7.0 was working fine but now that I made some FT8 contacts with
1.8.0-rc1 it's crashing as well. 


Hi Hisashi,

Elecraft use a slighly modified version of the Kenwood CAT protocol 
which is why the Hamlib driver is associated with Kenwood rigs, ~90% of 
the functionality is shared.


I will contact you off list with an instrumented version of WSJT-X that 
will allow me to see what is going wrong.


It is late here so I must sleep. It will probably be later today.

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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X? (long crashdump)

2017-07-12 Thread Hisashi T Fujinaka

On Thu, 13 Jul 2017, Bill Somerville wrote:


On 13/07/2017 03:16, Hisashi T Fujinaka wrote:

Thread 9 Crashed:: QThread
0   libsystem_kernel.dylib0x7fffdd9cdd42 __pthread_kill + 
10

1   libsystem_pthread.dylib   0x7fffddabb457 pthread_kill + 90
2   libsystem_c.dylib 0x7fffdd933420 abort + 129
3   libsystem_c.dylib 0x7fffdd933592 abort_report_np + 
181

4   libsystem_c.dylib 0x7fffdd959f28 __chk_fail + 48
5   libsystem_c.dylib 0x7fffdd959ef8 
__chk_fail_overflow + 16
6   libsystem_c.dylib 0x7fffdd95a413 __sprintf_chk + 
199
7   org.k1jt.wsjtx0x000101f57937 kenwood_set_freq + 
359
8   org.k1jt.wsjtx0x000101efdeeb rig_set_split_freq 
+ 331
9   org.k1jt.wsjtx0x000101efe9d7 
rig_set_split_freq_mode + 167
10  org.k1jt.wsjtx0x000101eb826c 
HamlibTransceiver::do_tx_frequency(unsigned long long, Transceiver::MODE, 
bool) + 812
11  org.k1jt.wsjtx0x000101eb1212 
TransceiverBase::set(Transceiver::TransceiverState const&, unsigned int) + 
402


Hi Hisashi,

looks like there is a Hamlib problem. It is crashing when trying to set the 
frequency of the split VFO.


What rig do you have?


Elecraft K3. I think it's pretending to be a Kenwood in hamlib.

Oddly, 1.7.0 was working fine but now that I made some FT8 contacts with
1.8.0-rc1 it's crashing as well.

--
Hisashi T Fujinaka - ht...@twofifty.com
BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee

--
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] Another Suggestion for 3 Extra Bits in FT8

2017-07-12 Thread Bill Somerville

On 12/07/2017 20:17, Morgen Benner wrote:
I was thinking since you could gain a lot of useful propagation 
information from JT-Mode QSOs, what if we included some info to help 
further define the parameters involved in the contact.  You can't fit 
much in 3 bits, but what about some sort of "Station Type Identifier" 
like this:


3 Bits APP

Antenna Type
0PP = Omnidirectional (Vert, Dipole)
1PP = Directional (Yagi, Log)

Station Power (as entered or possibly queried by CAT)
A00 = 0-10 Watts
A01 = 11-25 Watts
A10 = 26-50 Watts
A11 = 50+ Watts

73,
KC9SWV - Morgen
President, TARA


Hi Morgan,

WSPR has this pretty well covered already. WSPR stations transmit their 
power and grid locator. It is probably safe to assume they are running 
omni-direction aerials and the data is available from the WSPRNet.org 
site as a map or a database query suitable for external analysis. It 
also has many millions of historical spots going back many years.


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] Another Suggestion for 3 Extra Bits in FT8

2017-07-12 Thread Morgen Benner
Richard,

Good point about CAT polling. Could still be entered by the operator
though. Thoughts on the general concept? Is it viable or useful at all to
anyone else? What if it was reported to PSKReporter with the spot?

KC9SWV
Morgen

On Jul 12, 2017 5:21 PM, "Richard Stanley via wsjt-devel" <
wsjt-devel@lists.sourceforge.net> wrote:

Station power via cat would not be accurate.
I run the radio at 100 watts all the time and use the Pwr slider to keep it
between 5 and 10 watts so reading from cat would give the wrong result, I
know I am not the only op that works this way.

Richard G7OED


*From:* Morgen Benner
*Sent:* Wednesday, July 12, 2017 8:17 PM
*To:* WSJT software development
*Subject:* [wsjt-devel] Another Suggestion for 3 Extra Bits in FT8

I was thinking since you could gain a lot of useful propagation information
from JT-Mode QSOs, what if we included some info to help further define the
parameters involved in the contact.  You can't fit much in 3 bits, but what
about some sort of "Station Type Identifier" like this:

3 Bits APP

Antenna Type
0PP = Omnidirectional (Vert, Dipole)
1PP = Directional (Yagi, Log)

Station Power (as entered or possibly queried by CAT)
A00 = 0-10 Watts
A01 = 11-25 Watts
A10 = 26-50 Watts
A11 = 50+ Watts

73,
KC9SWV - Morgen
President, TARA

--

--
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



--
[image: Avast logo] 

This email has been checked for viruses by Avast antivirus software.
www.avast.com 

<#m_-2567588550430837593_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


--
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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X? (long crashdump)

2017-07-12 Thread Bill Somerville

On 13/07/2017 03:16, Hisashi T Fujinaka wrote:

Thread 9 Crashed:: QThread
0   libsystem_kernel.dylib0x7fffdd9cdd42 
__pthread_kill + 10
1   libsystem_pthread.dylib   0x7fffddabb457 pthread_kill 
+ 90

2   libsystem_c.dylib 0x7fffdd933420 abort + 129
3   libsystem_c.dylib 0x7fffdd933592 
abort_report_np + 181

4   libsystem_c.dylib 0x7fffdd959f28 __chk_fail + 48
5   libsystem_c.dylib 0x7fffdd959ef8 
__chk_fail_overflow + 16
6   libsystem_c.dylib 0x7fffdd95a413 __sprintf_chk 
+ 199
7   org.k1jt.wsjtx0x000101f57937 
kenwood_set_freq + 359
8   org.k1jt.wsjtx0x000101efdeeb 
rig_set_split_freq + 331
9   org.k1jt.wsjtx0x000101efe9d7 
rig_set_split_freq_mode + 167
10  org.k1jt.wsjtx0x000101eb826c 
HamlibTransceiver::do_tx_frequency(unsigned long long, 
Transceiver::MODE, bool) + 812
11  org.k1jt.wsjtx0x000101eb1212 
TransceiverBase::set(Transceiver::TransceiverState const&, unsigned 
int) + 402


Hi Hisashi,

looks like there is a Hamlib problem. It is crashing when trying to set 
the frequency of the split VFO.


What rig do you have?

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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X? (long crashdump)

2017-07-12 Thread Hisashi T Fujinaka

Process:   wsjtx [2201]
Path:  /Applications/wsjtx.app/Contents/MacOS/wsjtx
Identifier:org.k1jt.wsjtx
Version:   v1.8.0-rc1 (1.8.0-rc1)
Code Type: X86-64 (Native)
Parent Process:??? [1]
Responsible:   wsjtx [2201]
User ID:   1000

Date/Time: 2017-07-11 19:28:50.641 -0700
OS Version:Mac OS X 10.12.5 (16F73)
Report Version:12
Anonymous UUID:9D4D34C4-1C9C-2F4C-E0C9-CEC3CC8D4D4C


Time Awake Since Boot: 1700 seconds

System Integrity Protection: enabled

Crashed Thread:9  QThread

Exception Type:EXC_CRASH (SIGABRT)
Exception Codes:   0x, 0x
Exception Note:EXC_CORPSE_NOTIFY

Application Specific Information:
detected buffer overflow

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib  0x7fffdd9c634a mach_msg_trap + 10
1   libsystem_kernel.dylib  0x7fffdd9c5797 mach_msg + 55
2   com.apple.CoreFoundation0x7fffc7cf2874 
__CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation0x7fffc7cf1cf1 __CFRunLoopRun + 1361
4   com.apple.CoreFoundation0x7fffc7cf1544 CFRunLoopRunSpecific 
+ 420
5   com.apple.HIToolbox 0x7fffc7251ebc 
RunCurrentEventLoopInMode + 240
6   com.apple.HIToolbox 0x7fffc7251cf1 
ReceiveNextEventCommon + 432
7   com.apple.HIToolbox 0x7fffc7251b26 
_BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit0x7fffc57eaa54 _DPSNextEvent + 1120
9   com.apple.AppKit0x7fffc5f667ee 
-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] 
+ 2796
10  com.apple.AppKit0x7fffc57df3db -[NSApplication run] 
+ 926
11  libqcocoa.dylib 0x0001086ed6bf 
QCocoaEventDispatcher::processEvents(QFlags) + 
2143
12  org.qt-project.QtCore   0x00010685d781 
QEventLoop::exec(QFlags) + 401
13  org.qt-project.QtCore   0x000106861bb5 
QCoreApplication::exec() + 341
14  org.k1jt.wsjtx  0x000101e2d1b3 main + 7779
15  libdyld.dylib   0x7fffdd89f235 start + 1

Thread 1:
0   libsystem_kernel.dylib  0x7fffdd9ce44e __workq_kernreturn + 
10
1   libsystem_pthread.dylib 0x7fffddab8621 _pthread_wqthread + 
1426
2   libsystem_pthread.dylib 0x7fffddab807d start_wqthread + 13

Thread 2:
0   libsystem_kernel.dylib  0x7fffdd9ce44e __workq_kernreturn + 
10
1   libsystem_pthread.dylib 0x7fffddab8621 _pthread_wqthread + 
1426
2   libsystem_pthread.dylib 0x7fffddab807d start_wqthread + 13

Thread 3:
0   libsystem_kernel.dylib  0x7fffdd9ce44e __workq_kernreturn + 
10
1   libsystem_pthread.dylib 0x7fffddab8621 _pthread_wqthread + 
1426
2   libsystem_pthread.dylib 0x7fffddab807d start_wqthread + 13

Thread 4:
0   libsystem_kernel.dylib  0x7fffdd9ce44e __workq_kernreturn + 
10
1   libsystem_pthread.dylib 0x7fffddab8621 _pthread_wqthread + 
1426
2   libsystem_pthread.dylib 0x7fffddab807d start_wqthread + 13

Thread 5:
0   libsystem_kernel.dylib  0x7fffdd9ce44e __workq_kernreturn + 
10
1   libsystem_pthread.dylib 0x7fffddab8621 _pthread_wqthread + 
1426
2   libsystem_pthread.dylib 0x7fffddab807d start_wqthread + 13

Thread 6:
0   libsystem_kernel.dylib  0x7fffdd9ce44e __workq_kernreturn + 
10
1   libsystem_pthread.dylib 0x7fffddab8621 _pthread_wqthread + 
1426
2   libsystem_pthread.dylib 0x7fffddab807d start_wqthread + 13

Thread 7:
0   libsystem_kernel.dylib  0x7fffdd9ce44e __workq_kernreturn + 
10
1   libsystem_pthread.dylib 0x7fffddab8621 _pthread_wqthread + 
1426
2   libsystem_pthread.dylib 0x7fffddab807d start_wqthread + 13

Thread 8:: Qt bearer thread
0   libsystem_kernel.dylib  0x7fffdd9cf19e poll + 10
1   org.qt-project.QtCore   0x0001068b3a90 
qt_safe_poll(pollfd*, unsigned int, timespec const*) + 544
2   org.qt-project.QtCore   0x0001068b4f75 
QEventDispatcherUNIX::processEvents(QFlags) + 885
3   org.qt-project.QtCore   0x00010685d781 
QEventLoop::exec(QFlags) + 401
4   org.qt-project.QtCore   0x00010669beee QThread::exec() + 110
5   org.qt-project.QtCore   0x00010669f85a 0x106675000 + 174170
6   libsystem_pthread.dylib 0x7fffddab893b _pthread_body + 180
7   libsystem_pthread.dylib 0x7fffddab8887 _pthread_start + 286
8   libsystem_pthread.dylib 0x7fffddab808d thread_start + 13

Thread 9 Crashed:: QThread
0   

Re: [wsjt-devel] menus bug report

2017-07-12 Thread Gary McDuffie

> On Jul 12, 2017, at 6:09 PM, George J Molnar  wrote:
> 
> In any mode, select “Menus” OFF (unchecked).
> Headers in Band Activity and RX Frequency windows disappear (as expected)
> Open Preference pane
> Close Preferences with OK
> Band Activity header returns without UTC…Message line
> RX Frequency header returns WITH UTC…Message line.

Meant to mention this earlier but kinda fits to tag onto yours George.  When 
you turn menus off on the main window the window jumps to new locations.  
Turning menus back on does NOT return it to the previous location.  Kind of a 
PIB to move back each time.  That said, I never turn menus off on main window, 
but I’m sure someone does/will.

Gary
--
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] FT8 suggestion

2017-07-12 Thread Bill Turner via wsjt-devel
I have been using my compiled versions of WSJTX for several days and have been 
blown away with what you all have accomplished.  Downloaded 1.8.0 from JOe's 
website and it is spectacular.
Joe had indicated that FT8 would be a contest mode and that is quite good as 
long as you are operating a running station. Calling CQ and letting the 
software find responses on your frequency. I worked 4 contacts in eight minutes 
tonight (slow as I was adding names from QRZ to the WSJTX log).
Could you consider having two forms of FT8, one as is for running stations and 
one for Search and Pounce operation?  If the data sent in 12 to 13 seconds or 
less can be decoded and presented, that would leave the operator 3 to 5 seconds 
to find a station that is calling CQ and answer him or her.  FT8R and FT8S for 
example. If the data can be decoded in 10 seconds, you would have 5 seconds to 
look for a station CQing.
Thanks to all of the team for the great work you have put into WSJTX.
Bill Turner, W4WNT
--
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] menus bug report

2017-07-12 Thread George J Molnar
Noticed earlier, but tested on 7861.

In any mode, select “Menus” OFF (unchecked).
Headers in Band Activity and RX Frequency windows disappear (as expected)
Open Preference pane
Close Preferences with OK
Band Activity header returns without UTC…Message line
RX Frequency header returns WITH UTC…Message line.

MacOS 10.13 Beta



George J Molnar
Nevada, USA
KF2T  @GJMolnar





--
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] WSJT-X v1.8 User Guide

2017-07-12 Thread Morgen Benner
I think the link should have been:

http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.8.0-rc1.html

73,
KC9SWV - Morgen
President, TARA

On Wed, Jul 12, 2017 at 3:46 PM, Joe Taylor  wrote:

> Hi all,
>
> Most of the necessary updates of the WSJT-X User Guide to cover features
> in Version 1.8 are now in place.  Use *Help -> Online User Guide* or *F1*
> or click here:
>
> http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx
> -main-1.7.1-devel.html
>
> Some screen shots still need to be updated.  If you find errors or
> omissions, or anything else that could be improved, please report details
> here.
>
> -- 73, Joe, K1JT
>
> 
> --
> 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] WSJT-X v1.8 User Guide

2017-07-12 Thread Neil Zampella
Um .. Joe .. the link is still showing the 1.7.0 user guide.  No mention 
of FT8, or Freq Calibration, etc.


Neil, KN3ILZ


On 7/12/2017 3:46 PM, Joe Taylor wrote:

Hi all,

Most of the necessary updates of the WSJT-X User Guide to cover 
features in Version 1.8 are now in place.  Use *Help -> Online User 
Guide* or *F1* or click here:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html 



Some screen shots still need to be updated.  If you find errors or 
omissions, or anything else that could be improved, please report 
details here.


-- 73, Joe, K1JT





--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Richard Lamont
On 12/07/17 17:04, Bill Somerville wrote:

> this has been reported by several users who are building from sources on
> multiple platforms. I have not yet discovered what the reason is and I
> cannot reproduce it myself. Yours is the first report, albeit third
> party, that the official release kit is suffering this problem. Can you
> try the official v1.8.0-rc1 installer and see if that also has the same
> problem please?

I thought I'd mentioned it already, but I'm still seeing the problem
with the Ubuntu rc1-r7847 .deb downloaded from sourceforge.

73,
Richard G4DYA

--
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] FT8 and "Call 1st"

2017-07-12 Thread iain macdonnell - N6ML
On Tue, Jul 11, 2017 at 7:22 PM, Ross Primrose  wrote:
> One feature I'd like to see is if you answer a CQ, and the station comes
> back to someone else, halt tx...

YES!! +1

To the "wetware" comment - the argument for having auto seq in the
first place applies here - you don't have a lot of time to observe the
decode and take the appropriate action. Yes, you can halt after you've
already started transmitting, but it'd be nice to not have to
scramble

73,

~iain / N6ML

--
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] Disable TX if called stn answers other

2017-07-12 Thread Richard Lamont
On 12/07/17 19:19, Gary McDuffie wrote:
> 
>> On Jul 12, 2017, at 8:08 AM, Rich - K1HTV  wrote:
>>
>> For that reason, having the WSJT-X software halt your calling the station 
>> that answered someone else, I believe that the suggested feature be 
>> incorporated into future releases.
> 
> I’d second that.  I think it would be a good idea.  Since I would be calling 
> on the same sequence as the other person who called him, it would have to 
> detect it from the called stations reply.

Thirded.

73,
Richard G4DYA

--
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] r7855 frequency update

2017-07-12 Thread Alessandro Gorobey via wsjt-devel

Hi Bill,

sorry, I not read all new code

Il 12/07/2017 22:12, Bill Somerville ha scritto:

On 12/07/2017 21:04, Alessandro Gorobey via wsjt-devel wrote:
but as I can update/reset/modify my actual frequency configurations 
without destroy all other parameters ?


Where I can find a reset/recharge button  ? 


Hi Sandro,

go to "Settings->Frequencies" and right-click the working frequencies 
table.


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


--
73
Sandro
IW3RAB

--
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] r7855 frequency update

2017-07-12 Thread Bill Somerville

On 12/07/2017 21:04, Alessandro Gorobey via wsjt-devel wrote:
but as I can update/reset/modify my actual frequency configurations 
without destroy all other parameters ?


Where I can find a reset/recharge button  ? 


Hi Sandro,

go to "Settings->Frequencies" and right-click the working frequencies table.

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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Gary McDuffie

> On Jul 12, 2017, at 12:34 PM, Gary McDuffie  wrote:
> 
> 
>> On Jul 12, 2017, at 11:15 AM, Black Michael via wsjt-devel 
>>  wrote:
>> 
>> The Region is being saved in the INI filebut resets to ALL on WSJT-X 
>> startup.
> 
> Now this is something I haven’t tried.  I change configurations to check it 
> and it stays.  I haven’t been closing the program to test it.  I’ll do so in 
> an hour or two when I get home.
> 
> Gary - AG0N

Confirmed.  Closing program and reopening it maintains IARU setting also.

Gary - AG0N


--
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] r7855 frequency update

2017-07-12 Thread Alessandro Gorobey via wsjt-devel

Hi,

r7855 release update FrequencyList.cpp

OK,but as I can update/reset/modify my actual frequency configurations 
without destroy all other parameters ?


Where I can find a reset/recharge button  ?

In v1.7.1 I have 4 configurations, eg. HF-ONLY, WSPR, VHF-UP ..

OOT: seem that enabling pskreporter FT8 give strange effects. Too many 
like new mode ???


--
73
Sandro
IW3RAB
--
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] WSJT-X v1.8 User Guide

2017-07-12 Thread Joe Taylor

Hi all,

Most of the necessary updates of the WSJT-X User Guide to cover features 
in Version 1.8 are now in place.  Use *Help -> Online User Guide* or 
*F1* or click here:


http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-1.7.1-devel.html

Some screen shots still need to be updated.  If you find errors or 
omissions, or anything else that could be improved, please report 
details here.


-- 73, Joe, K1JT

--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Bill Somerville

On 12/07/2017 20:16, K5GZR - Rick wrote:

Replying to Bill and Mike,
R7847 installed using the official rc1 installer works as designed.   I can
select Region 2, exit WSJT-X, reenter WSJT-X, and the Region 2 setting is
retained.  I do not know the release numbers the other ops were using, nor
can I confirm that either of them was in fact using 1.8.0-rc1.   Hoping that
Mike will be able to identify the source of the problem.  Thanks, Rick -
K5GZR


Hi Rick,

thanks for that. We are working on it, something deep down is misbehaving.

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] Another Suggestion for 3 Extra Bits in FT8

2017-07-12 Thread Morgen Benner
I was thinking since you could gain a lot of useful propagation information
from JT-Mode QSOs, what if we included some info to help further define the
parameters involved in the contact.  You can't fit much in 3 bits, but what
about some sort of "Station Type Identifier" like this:

3 Bits APP

Antenna Type
0PP = Omnidirectional (Vert, Dipole)
1PP = Directional (Yagi, Log)

Station Power (as entered or possibly queried by CAT)
A00 = 0-10 Watts
A01 = 11-25 Watts
A10 = 26-50 Watts
A11 = 50+ Watts

73,
KC9SWV - Morgen
President, TARA
--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread K5GZR - Rick
Replying to Bill and Mike,
R7847 installed using the official rc1 installer works as designed.   I can
select Region 2, exit WSJT-X, reenter WSJT-X, and the Region 2 setting is
retained.  I do not know the release numbers the other ops were using, nor
can I confirm that either of them was in fact using 1.8.0-rc1.   Hoping that
Mike will be able to identify the source of the problem.  Thanks, Rick -
K5GZR
--

Date: Wed, 12 Jul 2017 17:15:33 + (UTC)
From: Black Michael 
To: WSJT software development 
Subject: Re: [wsjt-devel] IARU Region selection in Settings > General
is not 'sticking'
Message-ID: <1940879683.4033693.1499879733...@mail.yahoo.com>
Content-Type: text/plain; charset="utf-8"

I"m using 7857 and can duplicate the problem.The Region is being saved in
the INI filebut resets to ALL on WSJT-X startup.
Trying to debug now.
de Mike W9MDB

  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net
 Sent: Wednesday, July 12, 2017 11:07 AM
 Subject: Re: [wsjt-devel] IARU Region selection in Settings > General is
not 'sticking'
   
 On 12/07/2017 16:00, K5GZR - Rick wrote:
  
   I?ve seen this situation discussed here before, and thought that it had
been resolved, but? I can go to File > Settings > General and pick ?Region
2? from the IARU Region: dropdown list. However, if I exit WSJT-X, when I
restart WSJT-X, I see that the IARU Region: value has been returned to
?All?. And, as expected, the same thing happens if I switch to another
configuration and then switch back to the original configuration. My ?Region
2? selection value is not staying with the configuration. I just rebuilt
Hamlib, and then built r7856 to confirm that the problem has not been
resolved for me.?? OS is Windows 10. I have confirmed with 2 other operators
that they are seeing this same situation with wsjtx-1.8.0-rc1-win32.exe and
subsequent devel releases. Rick ? K5GZR   
 Hi Rick, this has been reported by several users who are building from
sources on multiple platforms. I have not yet discovered what the reason is
and I cannot reproduce it myself. Yours is the first report, albeit third
party, that the official release kit is suffering this problem. Can you try
the official v1.8.0-rc1 installer and see if that also has the same problem
please? 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] WSJT-X: Important, [please read if you use an external PA with WSJT-X

2017-07-12 Thread Dave AA6YQ
As you noted offline, Bill, I did not receive the message below. My comments 
are preceded by +++.


On 01/07/2017 13:49, Bill Somerville wrote:
>
> Hi Dave,
>
> thanks for your comments. I will address the last as that seems to be 
> the area where I think some progress on safety can be made. The last 
> version of the Commander TCP/IP documentation you sent us states:
>
> 
>
> 16. Report transmit status, e.g.
> CmdSendTX
> returns a single field in ADIF syntax specifying whether the 
> transceiver is transmitting, e.g.
> OFF
> or
> ON
> Not all transceivers respond to this directive.
>
> -
>
> The last sentence is ambiguous. What happens if a transceiver does not 
> respond?

+++ If the Commander is configured to control a transceiver that supports RX/TX 
switching via an external signal, Commander keeps
track of the transceiver's RX/TX state, and report that.

+++ If Commander can't control the transceiver's RX/TX state either via an 
external signal or via a CAT command, and if the
transceiver can't report its RX/TX state via a CAT command, then the CmdSendTX 
command above will always report ON 

> Could this exchange be modified to deal with the above scenario by 
> responding with OFF until  directive has been sent to the rig to ask 
> it to transmit when it would return ON. 

+++ As you report below, Commander already does that.

To complement the opposite 
> would be needed for directives to return to receive. 

+++ As you report below, Commander already does that.aa

I ask this 
> because at least we could get into the ballpark of when the rig 
> actually goes to Tx when a sequence of directives to Commander ending 
> with transmit request are processed.
>
> WSJT-X already has a dedicated thread for rig control and it can 
> trivially poll using this command once a request to go to Tx has been 
> sent, it has nothing else to do at this point. How often is acceptable 
> for a polling rate? 

+++ That's purely a "consumption of CPU resources" issue.

We would like to be able to detect the rig PTT 
> event within 100ms at worst.

+++ Polling every 100 ms should have no measurable impact on CPU resource 
consumption.


> Does the above directive respond with ON if RTS or DTR are used to key 
> the rig when the rig is one that does not have the ability to report 
> Tx status via a CAT query?

+++ Yes. It also works if a parallel port data signal is used to switch the 
transceiver between RX and TX.

>
> 73
> Bill
> G4WJS.
>
Hi Dave,

as a further data point. I am experimenting with the Commander TCP/IP 
command CmdSendTX and I am seeing an interesting behaviour. Just using 
the command after sending a CmdTX command seems to synchronize with the 
actual rig PTT event. I assume this is because CmdSendTX is queued in 
Commander behind the CmdTX command and the reply cannot be delivered 
until the former has been actioned.

+++ Correct.

This is despite the rig I am using 
having no CAT command to query PTT (IC-756) so it also appears to answer 
my query above about what happens in that case.

+++ Correct. Presumably, you're using an external interface controlled by a 
serial port modem control signal or parallel port data
signal to generate a SEND signal for your IC-756.

I will code a change to WSJT-X than does multiple CmdSendTX commands at 
10ms intervals until the expected response occurs or 1s expires. If one 
second expires WSJT-X will abort with a suitable error on the basis that 
the rig is not working.

+++ There may be some older transceivers that report RX/TX status via CAT 
command but could take longer than 1 second to switch
state after being directed to do so. Ideally, you would poll every 10 ms for 1 
second, and then poll every 100 ms for another 2
seconds before concluding that there's a problem.

   73,

   Dave, AA6YQ




--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Gordon Higgins
7847 hear no problem with region 1 stays put   windows 7 pro

On 12 July 2017 at 19:35, Bill Somerville  wrote:

> On 12/07/2017 19:31, Gary McDuffie wrote:
>
> On Jul 12, 2017, at 9:00 AM, K5GZR - Rick  
>  wrote:
>
> I have confirmed with 2 other operators that they are seeing this same 
> situation with wsjtx-1.8.0-rc1-win32.exe and subsequent devel releases.
>
> It’s working on the RC that I pulled Rick.  Interestingly, I pulled another 
> one last night (WSJT-X page) and noticed a different rev number than I did on 
> the earlier one from the same site.  Your rev is higher than mine, by the 
> way.  I’ll have to look when I get home, but I think it was either 7847 or 
> something close to that.
>
> Gary - AG0N
>
> Hi Gary,
>
> I made a small foobar building the kits, the Windows one missed out a very
> minor non-functional change. It was updated yesterday so all the published
> installers for WSJT-X v1.8.0 RC1 now identify as r7847 on all platforms.
>
> 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
>
>
--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Bill Somerville

On 12/07/2017 19:31, Gary McDuffie wrote:

On Jul 12, 2017, at 9:00 AM, K5GZR - Rick  wrote:

I have confirmed with 2 other operators that they are seeing this same 
situation with wsjtx-1.8.0-rc1-win32.exe and subsequent devel releases.

It’s working on the RC that I pulled Rick.  Interestingly, I pulled another one 
last night (WSJT-X page) and noticed a different rev number than I did on the 
earlier one from the same site.  Your rev is higher than mine, by the way.  
I’ll have to look when I get home, but I think it was either 7847 or something 
close to that.

Gary - AG0N


Hi Gary,

I made a small foobar building the kits, the Windows one missed out a 
very minor non-functional change. It was updated yesterday so all the 
published installers for WSJT-X v1.8.0 RC1 now identify as r7847 on all 
platforms.


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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Gary McDuffie

> On Jul 12, 2017, at 11:15 AM, Black Michael via wsjt-devel 
>  wrote:
> 
> The Region is being saved in the INI filebut resets to ALL on WSJT-X 
> startup.

Now this is something I haven’t tried.  I change configurations to check it and 
it stays.  I haven’t been closing the program to test it.  I’ll do so in an 
hour or two when I get home.

Gary - AG0N
--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Gary McDuffie

> On Jul 12, 2017, at 9:00 AM, K5GZR - Rick  wrote:
> 
> I have confirmed with 2 other operators that they are seeing this same 
> situation with wsjtx-1.8.0-rc1-win32.exe and subsequent devel releases.

It’s working on the RC that I pulled Rick.  Interestingly, I pulled another one 
last night (WSJT-X page) and noticed a different rev number than I did on the 
earlier one from the same site.  Your rev is higher than mine, by the way.  
I’ll have to look when I get home, but I think it was either 7847 or something 
close to that.

Gary - AG0N
--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread John Nelson
I am using rc1 (r7847) on a Mac OSX 10.11.6 and the region remains set to 1 and 
is not reset to ALL on startup.   Like Bill, I cannot reproduce this problem.

— John G4KLA
--
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] Idea: CQ "intent" bits

2017-07-12 Thread Gary McDuffie

> On Jul 12, 2017, at 8:51 AM, Gavin Scott  wrote:
> 
> So for example adding a couple bits to the CQ message to indicate the kind of 
> contacts being sought, one for "quick contact" and one for "ragchew" say, so 
> that 10 might mean "just looking for contacts", 11 "Willing to ragchew if you 
> want to" and 01 "Really just want to ragchew”.

Have you operated these modes?  There’s no such thing as ragchewing on them.  
It’s all canned messages.

Gary - AG0N
--
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] Disable TX if called stn answers other

2017-07-12 Thread Gary McDuffie

> On Jul 12, 2017, at 8:08 AM, Rich - K1HTV  wrote:
> 
> For that reason, having the WSJT-X software halt your calling the station 
> that answered someone else, I believe that the suggested feature be 
> incorporated into future releases.

I’d second that.  I think it would be a good idea.  Since I would be calling on 
the same sequence as the other person who called him, it would have to detect 
it from the called stations reply.

Gary - AG0N
--
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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

2017-07-12 Thread Hisashi T Fujinaka

Yes. I think that's what I said in my second message.

On Wed, 12 Jul 2017, John Nelson wrote:


Hi Hisashi,

I have checked that wsjtx-1.8.0-rc1 works correctly on 10.12.5 with my iMac.

Please visit Applications > Utilities > Console and look at System Reports 
and/or User Reports and us know what messages concerning wsjtx or jt9 you find there. 
   If you reboot your Mac, does WSJT-X still crash immediiately on opening?

? John G4KLA
--
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


--
Hisashi T Fujinaka - ht...@twofifty.com
BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee

--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Black Michael via wsjt-devel
I"m using 7857 and can duplicate the problem.The Region is being saved in the 
INI filebut resets to ALL on WSJT-X startup.
Trying to debug now.
de Mike W9MDB

  From: Bill Somerville 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Wednesday, July 12, 2017 11:07 AM
 Subject: Re: [wsjt-devel] IARU Region selection in Settings > General is not 
'sticking'
   
 On 12/07/2017 16:00, K5GZR - Rick wrote:
  
   I’ve seen this situation discussed here before, and thought that it had been 
resolved, but… I can go to File > Settings > General and pick ‘Region 2’ from 
the IARU Region: dropdown list. However, if I exit WSJT-X, when I restart 
WSJT-X, I see that the IARU Region: value has been returned to ‘All’. And, as 
expected, the same thing happens if I switch to another configuration and then 
switch back to the original configuration. My ‘Region 2’ selection value is not 
staying with the configuration. I just rebuilt Hamlib, and then built r7856 to 
confirm that the problem has not been resolved for me.   OS is Windows 10. I 
have confirmed with 2 other operators that they are seeing this same situation 
with wsjtx-1.8.0-rc1-win32.exe and subsequent devel releases. Rick – K5GZR   
 Hi Rick, this has been reported by several users who are building from sources 
on multiple platforms. I have not yet discovered what the reason is and I 
cannot reproduce it myself. Yours is the first report, albeit third party, that 
the official release kit is suffering this problem. Can you try the official 
v1.8.0-rc1 installer and see if that also has the same problem please? 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


   --
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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

2017-07-12 Thread C. Gary Rogers
I used on MacBook Pro running the latest version of OSX Sierra last evening to 
make four QSOs on 20m in conjunction with JT Bridge and RumlogNG and had no 
issues whatsoever. All programs played together well. 

Sent from my iPhone

> On Jul 12, 2017, at 12:00 PM, Bill Somerville  wrote:
> 
> Hi Hissashi,
> 
> there should be a crash reporter entry in the console log, that should help a 
> lot with diagnosis.
> 
> 73
> Bill
> G4WJS.
> 
>> On 12/07/2017 15:33, Hisashi T Fujinaka wrote:
>> OS version is 10.12.5. 
>> 
>> No error messages (I can check console later). 
>> 
>> How much more of the version number do you need? 
>> 
>> On Wed, 12 Jul 2017, Bill Somerville wrote: 
>> 
>>> On 12/07/2017 03:32, Hisashi T Fujinaka wrote: 
>>>   I tried rebooting and it's still crashing on open. 
>>> 
>>>   On Tue, 11 Jul 2017, Hisashi T Fujinaka wrote: 
>>> 
>>> I tried to close and reopen and now all my versions of 
>>> wsjtx (1.8.0-rc1 
>>> and 1.7.0) are all crashing on open. 
>>> 
>>> Hi Hisashi, 
>>> 
>>> sorry you are having problems with WSJT-X. Are you getting any error 
>>> message, if so what is it? Also it would help to know what 
>>> operating system and version you are using please? 
>>> 
>>> 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
--
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] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread Bill Somerville

On 12/07/2017 16:00, K5GZR - Rick wrote:


I’ve seen this situation discussed here before, and thought that it 
had been resolved, but…


I can go to File > Settings > General and pick ‘Region 2’ from the 
IARU Region: dropdown list.


However, if I exit WSJT-X, when I restart WSJT-X, I see that the IARU 
Region: value has been returned to ‘All’.


And, as expected, the same thing happens if I switch to another 
configuration and then switch back to the original configuration.


My ‘Region 2’ selection value is not staying with the configuration.

I just rebuilt Hamlib, and then built r7856 to confirm that the 
problem has not been resolved for me.   OS is Windows 10.


I have confirmed with 2 other operators that they are seeing this same 
situation with wsjtx-1.8.0-rc1-win32.exe and subsequent devel releases.


Rick – K5GZR


Hi Rick,

this has been reported by several users who are building from sources on 
multiple platforms. I have not yet discovered what the reason is and I 
cannot reproduce it myself. Yours is the first report, albeit third 
party, that the official release kit is suffering this problem. Can you 
try the official v1.8.0-rc1 installer and see if that also has the same 
problem please?


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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

2017-07-12 Thread Bill Somerville

Hi Hissashi,

there should be a crash reporter entry in the console log, that should 
help a lot with diagnosis.


73
Bill
G4WJS.

On 12/07/2017 15:33, Hisashi T Fujinaka wrote:

OS version is 10.12.5.

No error messages (I can check console later).

How much more of the version number do you need?

On Wed, 12 Jul 2017, Bill Somerville wrote:


On 12/07/2017 03:32, Hisashi T Fujinaka wrote:
  I tried rebooting and it's still crashing on open.

  On Tue, 11 Jul 2017, Hisashi T Fujinaka wrote:

I tried to close and reopen and now all my versions of 
wsjtx (1.8.0-rc1

and 1.7.0) are all crashing on open.

Hi Hisashi,

sorry you are having problems with WSJT-X. Are you getting any error 
message, if so what is it? Also it would help to know what

operating system and version you are using please?

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] Idea: CQ "intent" bits

2017-07-12 Thread Gavin Scott

So the 1.8rc release notes mention of unallocated message bits motivated me to 
subscribe here and throw out an idea I've been thinking about for a while.

I'd like to be able to indicate in a CQ message the intent of the call. People today 
will call CQ DX, or CQ  to direct a call, but I'd like to be able 
to also indicate in some standard fashion whether I'm just looking to add contacts to 
the log, or whether I'm looking for, or willing to have, a ragchew session.

For digital modes, I wornder if there would be any value in formalizing 
something like this such that it could be communicated to the user via color 
highlighting etc., or perhaps used by automation.

The value would be in better connecting people by common interest, and perhaps 
avoid anxiety for new users who are afraid of getting caught up in a long 
conversation (something that already seems to draw people to the JT modes).

So for example adding a couple bits to the CQ message to indicate the kind of contacts being sought, one for "quick 
contact" and one for "ragchew" say, so that 10 might mean "just looking for contacts", 11 "Willing 
to ragchew if you want to" and 01 "Really just want to ragchew".

Good idea? Dumb idea?

G.--
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] Autoseq patch

2017-07-12 Thread Black Michael via wsjt-devel
Tx 5 no longer gets overwritten until callsign changes -- fixes autoseq and 
double-click progressionAllow compound callsigns to work correctly with autoseq
https://www.dropbox.com/s/9mn29wj02akglye/autoseq.patch?dl=1

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] FT8 and "Call 1st"

2017-07-12 Thread Ross Primrose
I would submit that for ANY automated QSO sequencing STOPPING when you 
shouldn't be transmitting is MORE important than sending the correct 
transmission at the right time...


73

On 7/12/2017 11:03 AM, Neil Zampella wrote:
FWIW .. you have you mouse pointer over the HALT button, and you get 
ready to click, as for the missed period ... ?


I joked to a few people about this way back when FT8 was introduced, 
but jeez people ... its only 15 seconds ...


Neil, KN3ILZ


On 7/12/2017 10:28 AM, Ross Primrose wrote:
You must have faster wetware than I do... It's next to impossible to 
halt TX before the next TX cycle starts, and once the TX cycle 
starts, even if you halt it after 1sec you loose the possibility of 
decoding anyone else in that 15sec...


73, Ross N4RP

On 7/12/2017 7:15 AM, James Shaver (N2ADV) wrote:
That's built into the wetware (brain matter) of the person 
controlling the program :)



On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:

One feature I'd like to see is if you answer a CQ, and the station 
comes back to someone else, halt tx...


73, Ross N4RP


On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
As Jim said, its a nice AID to us old timers that cant click the 
red in 1 second


-- Original Message --
From: "Jim - N4ST" 
To: "'WSJT software development'" 
Sent: 7/11/2017 4:07:40 PM
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


Please keep "Call 1st".  It is a great aid to us old timers.
If people don't like it, don't click the box.


73,
Jim - N4ST


-Original Message-
From: Erik - [mailto:erikcarl...@live.com]
Sent: Tuesday, July 11, 2017 12:02
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


"We are interested in feedback from users on the question of 
partial QSO

automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns 
such as
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence 
stops. Not a
big deal since reciprocal calls such as this one are not too 
common. My

over-riding request is to not remove "Call 1st".

Erik EI4KF.


 


--
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


--
FCC Section 97.313(a) “At all times, an amateur station must use 
the minimum transmitter power necessary to carry out the desired 
communications.”



-- 


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



--
FCC Section 97.313(a) “At all times, an amateur station must use the minimum 
transmitter power necessary to carry out the desired communications.”


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

2017-07-12 Thread John Nelson
Hi Hisashi,

I have checked that wsjtx-1.8.0-rc1 works correctly on 10.12.5 with my iMac.

Please visit Applications > Utilities > Console and look at System Reports 
and/or User Reports and us know what messages concerning wsjtx or jt9 you find 
there.If you reboot your Mac, does WSJT-X still crash immediiately on 
opening?

— John G4KLA
--
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] FT8 and "Call 1st"

2017-07-12 Thread Neil Zampella
FWIW .. you have you mouse pointer over the HALT button, and you get 
ready to click, as for the missed period ... ?


I joked to a few people about this way back when FT8 was introduced, but 
jeez people ... its only 15 seconds ...


Neil, KN3ILZ


On 7/12/2017 10:28 AM, Ross Primrose wrote:
You must have faster wetware than I do...  It's next to impossible to 
halt TX before the next TX cycle starts, and once the TX cycle starts, 
even if you halt it after 1sec you loose the possibility of decoding 
anyone else in that 15sec...


73, Ross N4RP

On 7/12/2017 7:15 AM, James Shaver (N2ADV) wrote:
That's built into the wetware (brain matter) of the person 
controlling the program :)



On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:

One feature I'd like to see is if you answer a CQ, and the station 
comes back to someone else, halt tx...


73, Ross N4RP


On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
As Jim said, its a nice AID to us old timers that cant click the 
red in 1 second


-- Original Message --
From: "Jim - N4ST" 
To: "'WSJT software development'" 
Sent: 7/11/2017 4:07:40 PM
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


Please keep "Call 1st".  It is a great aid to us old timers.
If people don't like it, don't click the box.


73,
Jim - N4ST


-Original Message-
From: Erik - [mailto:erikcarl...@live.com]
Sent: Tuesday, July 11, 2017 12:02
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


"We are interested in feedback from users on the question of 
partial QSO

automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns 
such as
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence 
stops. Not a
big deal since reciprocal calls such as this one are not too 
common. My

over-riding request is to not remove "Call 1st".

Erik EI4KF.


 


--
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


--
FCC Section 97.313(a) “At all times, an amateur station must use the 
minimum transmitter power necessary to carry out the desired 
communications.”



-- 


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


[wsjt-devel] IARU Region selection in Settings > General is not 'sticking'

2017-07-12 Thread K5GZR - Rick
I've seen this situation discussed here before, and thought that it had been
resolved, but.

I can go to File > Settings > General and pick 'Region 2' from the IARU
Region: dropdown list.

However, if I exit WSJT-X, when I restart WSJT-X, I see that the IARU
Region: value has been returned to 'All'.

And, as expected, the same thing happens if I switch to another
configuration and then switch back to the original configuration.

My 'Region 2' selection value is not staying with the configuration.

I just rebuilt Hamlib, and then built r7856 to confirm that the problem has
not been resolved for me.   OS is Windows 10.

I have confirmed with 2 other operators that they are seeing this same
situation with wsjtx-1.8.0-rc1-win32.exe and subsequent devel releases.

Rick - K5GZR

--
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] FT8 and "Call 1st"

2017-07-12 Thread Black Michael via wsjt-devel
We probably need a warning if the Tx 5 message will not be recognized as a 
final message in auto sequence.Which right now means it doesn't contain a 73.
de Mike W9MDB


  From: Neil Zampella 
 To: wsjt-devel@lists.sourceforge.net 
 Sent: Wednesday, July 12, 2017 9:50 AM
 Subject: Re: [wsjt-devel] FT8 and "Call 1st"
   
 The problem with that is, the person calling CQ on the other end  has a 
program expecting to find a 73.   That said ... why would you need to?    If 
its to say something like 'Lotw eqsl tu', well that breaks the autoseq on the 
other side, but they can find that out now with a QRZ lookup !!
  
 On 7/12/2017 7:41 AM, Gordon Higgins wrote:
  
 to send free text u nead to remove auto seq  this works ok thanks 
  
 On 12 July 2017 at 12:38, Gordon Higgins  wrote:
 
 ? why in auto seqence will it not send free text  tx5 ft8 ?

 On 12 July 2017 at 12:15, James Shaver (N2ADV)  wrote:
 
That's built into the wetware (brain matter) of the person controlling the 
program :)
  
 > On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:
 >
 > One feature I'd like to see is if you answer a CQ, and the station comes 
 > back to someone else, halt tx...
 >
 > 73, Ross N4RP
 >
 >> On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
 >> As Jim said, its a nice AID to us old timers that cant click the red in 1 
 >> second
 >>
 >> -- Original Message --
 >> From: "Jim - N4ST" 
 >> To: "'WSJT software development'" 
 >> Sent: 7/11/2017 4:07:40 PM
 >> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
 >>
 >>> Please keep "Call 1st".  It is a great aid to us old timers.
 >>> If people don't like it, don't click the box.
 >>>
 >>> 
 >>> 73,
 >>> Jim - N4ST
 >>>
 >>>
 >>> -Original Message-
 >>> From: Erik - [mailto:erikcarl...@live.com]
 >>> Sent: Tuesday, July 11, 2017 12:02
 >>> To: WSJT software development 
 >>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
 >>>
 >>>
 >>> "We are interested in feedback from users on the question of partial QSO
 >>> automation.  Should "Call 1st" be changed or removed?"
 >>>
 >>> I like it as it is. One thing though, it gets broken by callsigns such as
 >>> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a
 >>> big deal since reciprocal calls such as this one are not too common. My
 >>> over-riding request is to not remove "Call 1st".
 >>>
 >>> Erik EI4KF.
 >>>
 >>>
 >>> -- -- 
 >>> 
 >>> --
 >>> 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.n et
 >>> 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.n et
 >>> 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.n et
 >> https://lists.sourceforge.net/ lists/listinfo/wsjt-devel
 >
 >
 > --
 > FCC Section 97.313(a) “At all times, an amateur station must use the minimum 
 > transmitter power necessary to carry out the  desired communications.”
 >
 >
 > -- -- 
 > --
 > 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.n et
 > 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.n et
 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! 

Re: [wsjt-devel] FT8 and "Call 1st"

2017-07-12 Thread Neil Zampella
The problem with that is, the person calling CQ on the other end has a 
program expecting to find a 73.   That said ... why would you need 
to?If its to say something like 'Lotw eqsl tu', well that breaks the 
autoseq on the other side, but they can find that out now with a QRZ 
lookup !!



On 7/12/2017 7:41 AM, Gordon Higgins wrote:

to send free text u nead to remove auto seq  this works ok thanks

On 12 July 2017 at 12:38, Gordon Higgins > wrote:


? why in auto seqence will it not send free text  tx5 ft8 ?

On 12 July 2017 at 12:15, James Shaver (N2ADV)
> wrote:

That's built into the wetware (brain matter) of the person
controlling the program :)

> On Jul 11, 2017, at 10:22 PM, Ross Primrose > wrote:
>
> One feature I'd like to see is if you answer a CQ, and the
station comes back to someone else, halt tx...
>
> 73, Ross N4RP
>
>> On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
>> As Jim said, its a nice AID to us old timers that cant
click the red in 1 second
>>
>> -- Original Message --
>> From: "Jim - N4ST" >
>> To: "'WSJT software development'"
>
>> Sent: 7/11/2017 4:07:40 PM
>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>>
>>> Please keep "Call 1st".  It is a great aid to us old timers.
>>> If people don't like it, don't click the box.
>>>
>>> 
>>> 73,
>>> Jim - N4ST
>>>
>>>
>>> -Original Message-
>>> From: Erik - [mailto:erikcarl...@live.com
]
>>> Sent: Tuesday, July 11, 2017 12:02
>>> To: WSJT software development
>
>>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>>>
>>>
>>> "We are interested in feedback from users on the question
of partial QSO
>>> automation.  Should "Call 1st" be changed or removed?"
>>>
>>> I like it as it is. One thing though, it gets broken by
callsigns such as
>>> EA8/G8BCG. When commuted to G8BCG for the QSO, auto
sequence stops. Not a
>>> big deal since reciprocal calls such as this one are not
too common. My
>>> over-riding request is to not remove "Call 1st".
>>>
>>> Erik EI4KF.
>>>
>>>
>>>


>>> --
>>> 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

>
>
> --
> FCC Section 97.313(a) “At all times, an amateur station must
use the minimum transmitter power necessary to carry out the
desired communications.”
>
>
>

--
> Check out the vibrant tech community on 

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

2017-07-12 Thread Hisashi T Fujinaka

OS version is 10.12.5.

No error messages (I can check console later).

How much more of the version number do you need?

On Wed, 12 Jul 2017, Bill Somerville wrote:


On 12/07/2017 03:32, Hisashi T Fujinaka wrote:
  I tried rebooting and it's still crashing on open.

  On Tue, 11 Jul 2017, Hisashi T Fujinaka wrote:

I tried to close and reopen and now all my versions of wsjtx 
(1.8.0-rc1
and 1.7.0) are all crashing on open.

Hi Hisashi,

sorry you are having problems with WSJT-X. Are you getting any error message, 
if so what is it? Also it would help to know what
operating system and version you are using please?

73
Bill
G4WJS.





--
Hisashi T Fujinaka - ht...@twofifty.com
BSEE + BSChem + BAEnglish + MSCS + $2.50 = coffee

--
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] FT8 and "Call 1st"

2017-07-12 Thread Ross Primrose
You must have faster wetware than I do...  It's next to impossible to 
halt TX before the next TX cycle starts, and once the TX cycle starts, 
even if you halt it after 1sec you loose the possibility of decoding 
anyone else in that 15sec...


73, Ross N4RP

On 7/12/2017 7:15 AM, James Shaver (N2ADV) wrote:

That's built into the wetware (brain matter) of the person controlling the 
program :)


On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:

One feature I'd like to see is if you answer a CQ, and the station comes back 
to someone else, halt tx...

73, Ross N4RP


On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
As Jim said, its a nice AID to us old timers that cant click the red in 1 second

-- Original Message --
From: "Jim - N4ST" 
To: "'WSJT software development'" 
Sent: 7/11/2017 4:07:40 PM
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


Please keep "Call 1st".  It is a great aid to us old timers.
If people don't like it, don't click the box.


73,
Jim - N4ST


-Original Message-
From: Erik - [mailto:erikcarl...@live.com]
Sent: Tuesday, July 11, 2017 12:02
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"


"We are interested in feedback from users on the question of partial QSO
automation.  Should "Call 1st" be changed or removed?"

I like it as it is. One thing though, it gets broken by callsigns such as
EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a
big deal since reciprocal calls such as this one are not too common. My
over-riding request is to not remove "Call 1st".

Erik EI4KF.



--
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


--
FCC Section 97.313(a) “At all times, an amateur station must use the minimum 
transmitter power necessary to carry out the desired communications.”


--
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



--
FCC Section 97.313(a) “At all times, an amateur station must use the minimum 
transmitter power necessary to carry out the desired communications.”


--
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] FT8 and "Call 1st"

2017-07-12 Thread Rich - K1HTV
Gordon,

   I believe that is that way because once you disable Auto Seq it will 
continue sending your last message over and over and not go to the next step to 
disable TX.


The answer is that if you want to send a free test TX5 message, populate the 
message box and turn off Auto Sequence.   Then proceed the old fashion, JT65 
way, of clicking on the message you want to be sent next until the QSO is 
complete.


73,

Rich - K1HTV


= = =



Send wsjt-devel mailing list submissions to

Date: Wed, 12 Jul 2017 12:38:16 +0100
From: Gordon Higgins 
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"
Message-ID:

Content-Type: text/plain; charset="utf-8"

? why in auto seqence will it not send free text tx5 ft8 ?
--
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] Disable TX if called stn answers other

2017-07-12 Thread Rich - K1HTV
I agree with Ross, N4RP in the software automatically halting your transmission 
if the station you called came back to another station. The problem is that by 
the time 'wetware'  gets info from eballware which has to scan the screen to 
see if another is calling, and then tell fingerware to determine where eyeware 
says the disable TX button is...by that time you have interfered with the QSO 
in progress.


For that reason, having the WSJT-X software halt your calling the station that 
answered someone else, I believe that the suggested feature be incorporated 
into future releases.


73,

Rich - K1HTV


PS  -  I'm finding FT8 to be great for DXing. In the past 2 days with 50W on HF 
I've already worked 25 countries, the best DX being Australia, Japan, Armenia 
and a contact with a rare one, Iraq.

  

= = =


Date: Wed, 12 Jul 2017 07:15:31 -0400
From: James Shaver (N2ADV) mailto:n2...@windstream.net
To: WSJT software development 
Subject: Re: [wsjt-devel] FT8 and "Call 1st"
Message-ID: 
Content-Type: text/plain; charset=utf-8

That's built into the wetware (brain matter) of the person controlling the 
program 


> On Jul 11, 2017, at 10:22 PM, Ross Primrose  mailto:n...@n4rp.com > wrote:
> 
> One feature I'd like to see is if you answer a CQ, and the station comes 
> back to someone else, halt tx...
> 
> 73, Ross N4RP
> 
--
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] wsjt-x v1.8.0-rc1 Crashing on reopen MacOS X?

2017-07-12 Thread Bill Somerville

On 12/07/2017 03:32, Hisashi T Fujinaka wrote:

I tried rebooting and it's still crashing on open.

On Tue, 11 Jul 2017, Hisashi T Fujinaka wrote:


I tried to close and reopen and now all my versions of wsjtx (1.8.0-rc1
and 1.7.0) are all crashing on open.


Hi Hisashi,

sorry you are having problems with WSJT-X. Are you getting any error 
message, if so what is it? Also it would help to know what operating 
system and version you are using please?


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] FT8 and "Call 1st"

2017-07-12 Thread Gordon Higgins
to send free text u nead to remove auto seq  this works ok thanks

On 12 July 2017 at 12:38, Gordon Higgins  wrote:

> ? why in auto seqence will it not send free text  tx5 ft8 ?
>
> On 12 July 2017 at 12:15, James Shaver (N2ADV) 
> wrote:
>
>> That's built into the wetware (brain matter) of the person controlling
>> the program :)
>>
>> > On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:
>> >
>> > One feature I'd like to see is if you answer a CQ, and the station
>> comes back to someone else, halt tx...
>> >
>> > 73, Ross N4RP
>> >
>> >> On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
>> >> As Jim said, its a nice AID to us old timers that cant click the red
>> in 1 second
>> >>
>> >> -- Original Message --
>> >> From: "Jim - N4ST" 
>> >> To: "'WSJT software development'" 
>> >> Sent: 7/11/2017 4:07:40 PM
>> >> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>> >>
>> >>> Please keep "Call 1st".  It is a great aid to us old timers.
>> >>> If people don't like it, don't click the box.
>> >>>
>> >>> 
>> >>> 73,
>> >>> Jim - N4ST
>> >>>
>> >>>
>> >>> -Original Message-
>> >>> From: Erik - [mailto:erikcarl...@live.com]
>> >>> Sent: Tuesday, July 11, 2017 12:02
>> >>> To: WSJT software development 
>> >>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>> >>>
>> >>>
>> >>> "We are interested in feedback from users on the question of partial
>> QSO
>> >>> automation.  Should "Call 1st" be changed or removed?"
>> >>>
>> >>> I like it as it is. One thing though, it gets broken by callsigns
>> such as
>> >>> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops.
>> Not a
>> >>> big deal since reciprocal calls such as this one are not too common.
>> My
>> >>> over-riding request is to not remove "Call 1st".
>> >>>
>> >>> Erik EI4KF.
>> >>>
>> >>>
>> >>> 
>> 
>> >>> --
>> >>> 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
>> >
>> >
>> > --
>> > FCC Section 97.313(a) “At all times, an amateur station must use the
>> minimum transmitter power necessary to carry out the desired
>> communications.”
>> >
>> >
>> > 
>> --
>> > 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] FT8 and "Call 1st"

2017-07-12 Thread Gordon Higgins
? why in auto seqence will it not send free text  tx5 ft8 ?

On 12 July 2017 at 12:15, James Shaver (N2ADV)  wrote:

> That's built into the wetware (brain matter) of the person controlling the
> program :)
>
> > On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:
> >
> > One feature I'd like to see is if you answer a CQ, and the station comes
> back to someone else, halt tx...
> >
> > 73, Ross N4RP
> >
> >> On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
> >> As Jim said, its a nice AID to us old timers that cant click the red in
> 1 second
> >>
> >> -- Original Message --
> >> From: "Jim - N4ST" 
> >> To: "'WSJT software development'" 
> >> Sent: 7/11/2017 4:07:40 PM
> >> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
> >>
> >>> Please keep "Call 1st".  It is a great aid to us old timers.
> >>> If people don't like it, don't click the box.
> >>>
> >>> 
> >>> 73,
> >>> Jim - N4ST
> >>>
> >>>
> >>> -Original Message-
> >>> From: Erik - [mailto:erikcarl...@live.com]
> >>> Sent: Tuesday, July 11, 2017 12:02
> >>> To: WSJT software development 
> >>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
> >>>
> >>>
> >>> "We are interested in feedback from users on the question of partial
> QSO
> >>> automation.  Should "Call 1st" be changed or removed?"
> >>>
> >>> I like it as it is. One thing though, it gets broken by callsigns such
> as
> >>> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops.
> Not a
> >>> big deal since reciprocal calls such as this one are not too common. My
> >>> over-riding request is to not remove "Call 1st".
> >>>
> >>> Erik EI4KF.
> >>>
> >>>
> >>> 
> 
> >>> --
> >>> 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
> >
> >
> > --
> > FCC Section 97.313(a) “At all times, an amateur station must use the
> minimum transmitter power necessary to carry out the desired
> communications.”
> >
> >
> > 
> --
> > 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] FT8 and "Call 1st"

2017-07-12 Thread James Shaver (N2ADV)
That's built into the wetware (brain matter) of the person controlling the 
program :)

> On Jul 11, 2017, at 10:22 PM, Ross Primrose  wrote:
> 
> One feature I'd like to see is if you answer a CQ, and the station comes back 
> to someone else, halt tx...
> 
> 73, Ross N4RP
> 
>> On 07/11/2017 07:23 PM, Ricky Scott W7PSK wrote:
>> As Jim said, its a nice AID to us old timers that cant click the red in 1 
>> second
>> 
>> -- Original Message --
>> From: "Jim - N4ST" 
>> To: "'WSJT software development'" 
>> Sent: 7/11/2017 4:07:40 PM
>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>> 
>>> Please keep "Call 1st".  It is a great aid to us old timers.
>>> If people don't like it, don't click the box.
>>> 
>>> 
>>> 73,
>>> Jim - N4ST
>>> 
>>> 
>>> -Original Message-
>>> From: Erik - [mailto:erikcarl...@live.com]
>>> Sent: Tuesday, July 11, 2017 12:02
>>> To: WSJT software development 
>>> Subject: Re: [wsjt-devel] FT8 and "Call 1st"
>>> 
>>> 
>>> "We are interested in feedback from users on the question of partial QSO
>>> automation.  Should "Call 1st" be changed or removed?"
>>> 
>>> I like it as it is. One thing though, it gets broken by callsigns such as
>>> EA8/G8BCG. When commuted to G8BCG for the QSO, auto sequence stops. Not a
>>> big deal since reciprocal calls such as this one are not too common. My
>>> over-riding request is to not remove "Call 1st".
>>> 
>>> Erik EI4KF.
>>> 
>>> 
>>> 
>>>  
>>> -- 
>>> 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
> 
> 
> -- 
> FCC Section 97.313(a) “At all times, an amateur station must use the minimum 
> transmitter power necessary to carry out the desired communications.”
> 
> 
> --
> 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