Re: [wsjt-devel] Feature request: WSJT-X

2018-03-15 Thread John Ward
Aah. Ok. One day ill get to EME. Thanks and Regards John Ward 73 de John ZS1EQ On 16 Mar 2018 08:42, wrote: > Hi John > > The problem OZ1LPR ran into was during some EME tests of the new Doppler > modes in 1.9.0. He was attempting to operate manual split with Doppler > tracking set to off, i

Re: [wsjt-devel] Feature request: WSJT-X

2018-03-15 Thread charlie
Hi John The problem OZ1LPR ran into was during some EME tests of the new Doppler modes in 1.9.0. He was attempting to operate manual split with Doppler tracking set to off, in an attempt to disable CAT frequency commands to his radio completely. He found that having set up his VFO A and VFO B t

Re: [wsjt-devel] Feature request: WSJT-X

2018-03-15 Thread John Ward
Morning. Cant you simply avoid the birdie by adjusting the tx/rx frequency settings with the mouse on the waterfall display and then use the "fake" options in the settings? Thanks and Regards John Ward 73 de John ZS1EQ On 16 Mar 2018 8:17 AM, wrote: > Hi Peter > > One option might be to arrang

Re: [wsjt-devel] Feature request: WSJT-X

2018-03-15 Thread charlie
Hi Peter One option might be to arrange PTT via a serial port to the mic PTT line and not have to use CAT, in which case the Rig to 'None' would work. I have heard of one other request for what you are asking, from OZ1LPR, for much the same reasons. 73 Charlie G3WDG >> >> Hello, >> > > firstly

[wsjt-devel] Feature request: WSJT-X

2018-03-15 Thread Peter Sumner
> > Hello, > firstly my thanks to those who are at the coal face developing WSJT and its brothers. I would like to see if it would be possible to include a toggle on the main GUI that stops WSJT-X sending frequency set commands to the transceiver. When I control my IC-7600 and my IC-910 with WSJT

Re: [wsjt-devel] wsjtx-1.9.0-rc2 build failure with gcc-8.0.1

2018-03-15 Thread Black Michael via wsjt-devel
The gcc reponse to this problem is "not a bug" since the standard requires len=1 as the only valid thing for type c_char in the iso_c_bindingThe FORTRAN group response is that gcc has had a bug allowing len>1 since this has been true since FORTRAN 2003. So...unless we put pressure on gcc to main

[wsjt-devel] (no subject)

2018-03-15 Thread ja1lzk
unscribe Windows メール から送信-- 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

Re: [wsjt-devel] Split FT8 QSY bug?

2018-03-15 Thread Joe Taylor
Rich -- On 3/15/2018 11:39 AM, Rich - K1HTV wrote: If at all possible, I'd recommend that a 4-digit (160 thru 40M) or 5-digit (30M thru 6M) number in a CQ text message be interpreted as the frequency to set VFO-B. It is harder to misinterpret an exact frequency, especially once the DXpedition

Re: [wsjt-devel] wsjtx-1.9.0-rc2 build failure with gcc-8.0.1

2018-03-15 Thread Black Michael via wsjt-devel
Nope...not the way it works.    c(10) would be an array of char * Mike On Thursday, March 15, 2018, 11:21:16 AM CDT, Jaroslav Skarvada wrote: The report for reference: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84885 But shouldn't it be: character(kind=c_char) :: c(10) to map 1:1 to

Re: [wsjt-devel] wsjtx-1.9.0-rc2 build failure with gcc-8.0.1

2018-03-15 Thread Jaroslav Skarvada
The report for reference: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84885 But shouldn't it be: character(kind=c_char) :: c(10) to map 1:1 to C language definition: char c[10]; ? Aren't we exploiting here some non-documented GNU Fortran feature? Jaroslav, OK2JRQ - Original Message -

Re: [wsjt-devel] wsjtx-1.9.0-rc2 build failure with gcc-8.0.1

2018-03-15 Thread Black Michael via wsjt-devel
I've been able to reproduce this on a small example with 8.0.1 and have submitted a bug report.This fails to compile with 8.0.1 but does compile with pre 8.0 compilersIt only shows the error when the character declaration is inside a type block. subroutine foo(i,c)   use, intrinsic :: iso_c_bin

Re: [wsjt-devel] Split FT8 QSY bug?

2018-03-15 Thread Rich - K1HTV
If at all possible, I'd recommend that a 4-digit (160 thru 40M) or 5-digit (30M thru 6M) number in a CQ text message be interpreted as the frequency to set VFO-B. It is harder to misinterpret an exact frequency, especially once the DXpedition mode starts being used and DX stations use Rx frequen

Re: [wsjt-devel] WSJT-X v1.9.0-rc2 fox mode anomaly (Windows)

2018-03-15 Thread John S. Howell, Jr.
HI Joe, Steve, Mike, Sorry about the confusion. Steve and Mike, you are exactly correct. It wasn't obvious to me that I just had to click on the tab!! I'm using a standard version of Windows 10. Here is a video I made prior to understanding it was my own user error - illustrating the (non) issu

Re: [wsjt-devel] Split FT8 QSY bug?

2018-03-15 Thread Black Michael via wsjt-devel
OK...so it added the 1st 3 digits as 190kHz to 1MHz to come up with 1.190 So what do we want to do with a 4 or 5 digit QSY like this? #1 Ignore it?#2 Change to it and handle it differently than the 3-digit QSY? de Mike W9MDB On Thursday, March 15, 2018, 9:59:33 AM CDT, Rich - K1HTV wrote:

Re: [wsjt-devel] Split FT8 QSY bug?

2018-03-15 Thread Joe Taylor
Hi Rich, Apparently H40YM transmitted "CQ 1908 H40YM", indicating that he was hoping to raise JAs in a higher part of the band. That's a free text message, so double-clicking on it will *not* put H40YM into your DX Call box. Of course, you can do this manually, however. Double-clicking on

Re: [wsjt-devel] Split FT8 QSY bug?

2018-03-15 Thread Rich - K1HTV
Mike, yes a QSY message was seen: >From the Band Activity window: --- 160m 112315 10 0.2 700 ~ CQ N9MB EN70 K 112315 4 1.4 864 ~ CQ WB9JOX EN61 K 112315 -18 0.7 1957 ~ CQ 1908 H40YM !where? >From the Rx Frequency

Re: [wsjt-devel] Split FT8 QSY bug?

2018-03-15 Thread Black Michael via wsjt-devel
That's almost a QSY request but that format is expecting a 3-digit frequency so would've thought you'd see a 190kHz movement Did you see a QSY message in your Rx window? de Mike W9MDB On Thursday, March 15, 2018, 6:49:15 AM CDT, Rich - K1HTV wrote: This morning, a few minutes be

[wsjt-devel] Add frequency translation to wsjtx for multiple instance of wsjtx on same I/Q audio stream.

2018-03-15 Thread Olivier SCHMITT
Hello Dear OM developer friends, Since the future of the radio is in SDRs having high bandwidth, I wonder if it would be interesting to add a frequency translation feature in WSJTX. This would make it possible to have SDRs of 96khz, 192khz or 384khz in I / Q audio and to be able to use the sa

Re: [wsjt-devel] WSJT-X v1.9.0-rc2 fox mode anomaly (Windows)

2018-03-15 Thread Steven Franke
Hi Joe and John, I wonder if John’s observation relates to the fact that switching from Fox mode to Hound mode will not change which Tab is currently visible. When the user selects Fox mode, WSJT-X will automatically select Tab 3. If Fox mode is then turned off, or if Hound mode is selected, T

Re: [wsjt-devel] WSJT-X v1.9.0-rc2 fox mode anomaly (Windows)

2018-03-15 Thread Black Michael via wsjt-devel
I thing what he may be referring to is that the tab window stays on tab 3.  I suppose it would be nice to remember what tab you were on and go back to that... de Mike W9MDB On Thursday, March 15, 2018, 7:59:29 AM CDT, Joe Taylor wrote: Hi John, On 3/15/2018 1:02 AM, John S. Howell,

Re: [wsjt-devel] WSJT-X v1.9.0-rc2 fox mode anomaly (Windows)

2018-03-15 Thread Joe Taylor
Hi John, On 3/15/2018 1:02 AM, John S. Howell, Jr. AF3K wrote: Exploring the new release and found what seems like a minor bug: Un-checking fox mode does not return the main screen to non fox mode. To replicate: File -> Settings ->Advanced Check Fox FT8 DXpedition mode & click OK. Main scree

[wsjt-devel] Split FT8 QSY bug?

2018-03-15 Thread Rich - K1HTV
This morning, a few minutes before local sunrise, H40YM showed up on 160 Meter FT8 on 1840 KHz calling "CQ 1908 H40YM". He was listening up the band in the 160M Japan operating area frequency window. Wanting to to work the H40 split, I temporarily set the WSJT-X File/Settings/Radio/ "Split Oper

[wsjt-devel] wsjtx-1.9.0-rc2 build failure with gcc-8.0.1

2018-03-15 Thread Jaroslav Skarvada
Hi, with gfortran 8.0.1 the compilation of wsjtx fails with the following error: make[2]: Leaving directory '/builddir/build/BUILD/wsjtx-1.9.0-rc2/wsjtx/build' jt9com.f90:44:47: Error: Component 'datetime' of BIND(C) type at (1) must have length one jt9com.f90:45:45: Error: Component 'mycall' o