[wsjt-devel] Minor typo

On the Sourceforge site, where there is documentation on JTSDK, there is a minor typographical error: https://sourceforge.net/projects/jtsdk/files/win32/2.0.0/ On this section: Set Environment Options (Important) ... enabble-autorun 73 de Sebastian, W4AS --

Re: [wsjt-devel] Rig Defaults patch

On 14/03/2018 11:30, Black Michael via wsjt-devel wrote: Add default settings to Data Bits, Stop Bits, and Handshake https://www.dropbox.com/s/sjlgkde3uvo2f8m/rigdefaults.patch?dl=1 de Mike W9MDB Hi Mike, thanks for this pa

Re: [wsjt-devel] WSJT-X v1.9.0 rc2 possible problems

Hi John, On 3/16/2018 5:26 PM, John Becker K9MM wrote: 2. At one point, my transmit frequency had jumped to his frequency. See bottom pf page 1: "Hounds acknowledge having been called and send their “R+rpt” message at a randomly selected frequency between 300 and 900 Hz.  These frequency co

Re: [wsjt-devel] WSJT-X v1.9.0 rc2 possible problems

Hi John, On 3/16/2018 5:26 PM, John Becker K9MM wrote: 2. At one point, my transmit frequency had jumped to his frequency. See bottom of page 1: "Hounds acknowledge having been called and send their “R+rpt” message at a randomly selected frequency between 300 and 900 Hz.  These frequency conv

Re: [wsjt-devel] WSJT-X v1.9.0 rc2 possible problems

Joe Taylor wrote: Hi John, On 3/16/2018 3:04 PM, John Becker K9MM wrote: I updated my installation of WSJT-X from v1.8.0 to v1.9.0 rc2 earlier today. I encountered some problems while trying to work TY7C on 17M using DXpedition mode. I don't know how we could make this advice any more clea

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

Hello Bill, for a lot of my EME contacts on 50 MHz I had been using WSJT10, which cannot do PTT via CAT so have changed over to use WSJT-X for these contacts now as I have recently moved the IC-7600 to use only the onboard USB interface in the radio to reduce the complexity of the shack PC as it

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

On 16/03/2018 20:29, Peter Sumner wrote: eg. on WSPR, 144.489 if I type into the box as you suggested (not tried that before I must admit), my test frequency was 144.085 which moved the rig all okay, then if I open the settings menu and close I am now set back to be on 144.489. This is the beha

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

Hello Joe, I have just tried your suggested method, if I then go to the configuration menu and press okay, when it returns to the main interface, the rig reverts to the SET frequency for the WSJT mode selected. eg. on WSPR, 144.489 if I type into the box as you suggested (not tried that before

[wsjt-devel] V1.9.0-RC2 Problem with the size of the elements in the window under wspr

Hello, I tried this new version. 1.9.0-RC2 on windows 10 1709 I.Hoping that someone has not already reported it, there seems to be a problem of sizing elements when using WSPR mode. 1.png is normal in FT8 mode 2.png is when I start wsjtx in FT8 mode then I switch to wspr mode 3.png is when i

Re: [wsjt-devel] WSJT-X v1.9.0 rc2 possible problems

Hi John, On 3/16/2018 3:04 PM, John Becker K9MM wrote: I updated my installation of WSJT-X from v1.8.0 to v1.9.0 rc2 earlier today. I encountered some problems while trying to work TY7C on 17M using DXpedition mode. I don't know how we could make this advice any more clear: *To use FT8 DXp

[wsjt-devel] WSJT-X v1.9.0 rc2 possible problems

I updated my installation of WSJT-X from v1.8.0 to v1.9.0 rc2 earlier today. I encountered some problems while trying to work TY7C on 17M using DXpedition mode. I set the dial on my FT-1000MP Mk V to 18096. I was decoding TY7C and I started calling him. He gave me a report. I sent my report t

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

- Original Message - > > > - Original Message - > > 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_binding > > The FORTRAN group response is that gcc has had a bug allowing len>1 since > >

Re: [wsjt-devel] Special calls

Fri, 16 Mar 2018 14:10:15 + Bill Somerville kirjoitti: > So in short, you are restricted to free text messages with that > callsign, and I doubt it will be very successful. > > 73 > Bill > G4WJS. Bill Tnx for info. Yes I know, qso can be made, BUT, it's not very "handy" I'd say, not worth

Re: [wsjt-devel] Special calls

On 16/03/2018 14:01, jarmo wrote: Our club have got call OG60F, anniversary our clubs OH1AF 60 years being and we have possibility use it whole this year. Now, it would be nice to make FT8 qsos with this call also. What I have tried, it's only possible with free text. What I know, OG is one of O

[wsjt-devel] Special calls

Our club have got call OG60F, anniversary our clubs OH1AF 60 years being and we have possibility use it whole this year. Now, it would be nice to make FT8 qsos with this call also. What I have tried, it's only possible with free text. What I know, OG is one of OH prefixes, as well as OJ, OI and OF

[wsjt-devel] Rig, power, antenna ?

Getting back into radio after many years. Currently only receiving FT8 with an AOR AR3030 and mini-whip antenna. Looking to erect a Windom antenna and purchase a transceiver. I'm in the UK. Last night "listening" on 40m I decoded a station in New York (WU2M) with a -21dB. The question is, was

[wsjt-devel] QSY patch

Restrict QSY response to 3-digit numbers.  CQ + CALLSIGN is now ignored. https://www.dropbox.com/s/6ms4vr876deyy0p/qsy.patch?dl=1 de Mike W9MDB -- Check out the vibrant tech community on one of the world's most engagin

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

Hi Peter, On 3/16/2018 1:28 AM, Peter Sumner VK5PJ wrote: 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. I do manual QSYs all the time when using WSJ-X on VHF bands. It's as simple as ty

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

- Original Message - > 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_binding > The FORTRAN group response is that gcc has had a bug allowing len>1 since > this has been true since FORTRAN 2003. > >