Re: [wsjt-devel] possible bugs

I've never heard of the reason why it was ever connected in the first place.Only thing I can think of is somebody wanted the meter to reflect what the waterfall was doing which is of dubious use now that the Flatten option is a much better solution. And it really did not affect the "input dB

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

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. -- Hisashi T Fujinaka - ht...@twofifty.com BSEE + BSChem + BAEnglish + MSCS + $2.50

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

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

Re: [wsjt-devel] possible bugs

OK Bill .. but why did it affect the input dB reading ? Just curious. On 7/11/2017 5:32 PM, Bill Somerville wrote: On 11/07/2017 22:24, Neil Zampella wrote: the slider is no longer a 'digital gain' that affects sound input, it only affect the graph. Hi Neil, it never has been a digital

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

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. -- Hisashi T Fujinaka - ht...@twofifty.com -- Check out the vibrant tech community on one of the world's most

Re: [wsjt-devel] libgomp1 >=4.9

On 12/07/2017 01:58, Pino Zollo wrote: Please, where to find libgomp1 >=4.9 for Mint 17.3 alias Ubuntu 14.04 32bit ? Here is not available:https://packages.ubuntu.com/search?keywords=libgomp1 neither here:https://pkgs.org/download/libgomp1 TU 73 Pino ZP4KFX Hi Pino, it is

Re: [wsjt-devel] libgomp1 >=4.9

Hi Pino, I am not sure you can, as I "think" Mint 17.3 is based on Trusty (14.04), I could be wrong, but. Trusty, even with the updates is showing gcc-4.8 https://packages.ubuntu.com/trusty/libx32gomp1 https://packages.ubuntu.com/trusty/i386/libx32gomp1/filelist You could either upgrade, or

[wsjt-devel] Important : JTAlert needs upgrading (to 2.9.10) for those testing FT8 mode.

JTAlert users who are testing the new FT8 mode need to upgrade their JTAlert version to 2.9.10 to avoid sending spots to HamSpots.net as T10 mode or JT9 mode (JTAlert earlier than 2.9.8) Users using early versions of JTAlert who don't want to upgrade (HRD6 log with JTAlert 2.8.7) need to turn

[wsjt-devel] libgomp1 >=4.9

Please, where to find libgomp1 >=4.9 for Mint 17.3 alias Ubuntu 14.04 32bit ? Here is not available: https://packages.ubuntu.com/search?keywords=libgomp1 neither here: https://pkgs.org/download/libgomp1 TU 73 Pino ZP4KFX

Re: [wsjt-devel] Distribution

Laurie have you considered adding other modes for WAS track? or was it always JT65/JT9? -- Original Message -- From: "Laurie, VK3AMA" <_vk3a...@vkdxer.net> To: wsjt-devel@lists.sourceforge.net Sent: 7/11/2017 1:19:51 PM Subject: Re: [wsjt-devel] Distribution On 12/07/2017 4:10 AM,

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

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

Re: [wsjt-devel] Build Error

that was it I had closed it but apparently it didn’t close all the way -- Original Message -- From: "Ricky Scott W7PSK" To: "Black Michael" ; "WSJT software development" Sent: 7/11/2017 4:04:37 PM Subject: Re:

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

Re: [wsjt-devel] Build Error

Ill check Mike thanks -- Original Message -- From: "Black Michael" To: "Ricky Scott W7PSK" ; "WSJT software development" Sent: 7/11/2017 3:59:32 PM Subject: Re: [wsjt-devel] Build Error That error means WSJT-X

Re: [wsjt-devel] Build Error

That error means WSJT-X was still running and in use.  You might have a hung task or just didn't exit it. de Mike W9MDB From: Ricky Scott W7PSK To: WSJT software development ; wsjt-devel@lists.sourceforge.net Sent: Tuesday, July 11,

[wsjt-devel] Possible bugs v2

Hi again, I see my error with the slider, it do say "digital gain graph windows" I assume it was same as its been few years with wsjt-x 1.7. As it change level display dB level, in the past. I need to learn better of new features on 1.8.rc1. Too excited to get on the band with it, so rtfm was

Re: [wsjt-devel] possible bugs

On 11/07/2017 22:24, Neil Zampella wrote: the slider is no longer a 'digital gain' that affects sound input, it only affect the graph. Hi Neil, it never has been a digital gain control for anything but the waterfall and 2D spectrum graph. That is why it has been disconnected from the input

[wsjt-devel] JT65/JT9 Marker Setting - r7850

Um .. shouldn't the JT65/JT9 marker setting be grayed out for FT8?? v1.7.1.-r7850 Neil, KN3ILZ -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org!

Re: [wsjt-devel] possible bugs

Jari, the slider is no longer a 'digital gain' that affects sound input, it only affect the graph. Input adjustment is either through your OS sound mixer, or physically from your rig. If you put your mouse over the slider it will give the 'tool tip' about this. I've got a KX3, and

Re: [wsjt-devel] possible bugs

I just went through this with another user and he had to take out some very noisy cards from his desktop.With no input signal you should see pretty much no signal. The input level has no control anymore from WSJT-X...it never did control the recording level...only the waterfall level.  It was

Re: [wsjt-devel] Bugs in command line tools in WSJTX 1.8.0-rc1

Dani - We are aware of the fact that the command line tools are not stable at the moment. They will be cleaned up and tested before the GA release. Steve, k9an > On Jul 11, 2017, at 3:52 PM, Dani EA4GPZ wrote: > > Hi all, > > I have compiled WSJTX 1.8.0-rc1 from source

[wsjt-devel] possible bugs

Hello, I'm new here, so apologies if I cause extra havoc. WSJT-X 1.8.0-rc1 Windows 7 pro 64 bits I think I seen few anomalies: Digital gain does not change input level, bar remain green and at 62dB level, even no input signal. Second thing I note is TX5. If I do CQ and wish to mark TX 5 after

[wsjt-devel] Bugs in command line tools in WSJTX 1.8.0-rc1

Hi all, I have compiled WSJTX 1.8.0-rc1 from source an I'm finding the following bugs in the command line tools. jt9 will always segfault when run for JT9: $ jt9 -9 00_01.wav Program received signal SIGSEGV: Segmentation fault - invalid memory reference. Backtrace for

Re: [wsjt-devel] Apparent Distorted Signals

Also be aware that you're also seeing FFT effect where a strong signal looks "sloppy" due to the color coding as the FFT frequencies are not perfect.There's always FFT frequency spreading but you just don't see it as it's usually closer to the noise floor. Here's an example of a loopback test

Re: [wsjt-devel] Distribution

On 12/07/2017 4:10 AM, Bill Somerville wrote: RR, Laurie. My mistake as mentioned in the other post. I will claim I did it so developers of other software get a head start. BTW I did some basic tests with JTAlert using it to initiate MSK144 and FT8 QSOs from alerts. This was necessary as I

[wsjt-devel] Apparent Distorted Signals

Drifting a little from the “extra 3 bits” conversation, folks noticing “dirty” signals in the waterfall should not jump to the conclusion that it is the transmitter’s fault. Between propagation conditions, multipath, and a zillion permutations of AGC, NB, and filter settings, the fact is that

Re: [wsjt-devel] Suggestions for three extra bits in FT8

If you throw attenuation at the signal and the issue goes away, the cause is most likely on the receive side. It also helps to have a panadapter available (something that isn't tied into the AF chain). The waterfall itself should not be used to determine signal quality. 73, Jim S. N2ADV

Re: [wsjt-devel] Suggestions for three extra bits in FT8

If you want to see what your signal looks like use hamspots.net to see who is receiving your signal.  This will indicate if they are using JTAlert.You can then search for their callsign on hamspots.net to see if they are transmitting...which would mean they are sitting at their rig. Then use

Re: [wsjt-devel] Suggestions for three extra bits in FT8

Thanks, Bill (and Gary in the previous reply)! I’m pretty sure my receive is fine - IC-7300 into my mac using USB connection, AGC off, notch filter off, noise blanker off, noise reduction off, IP+ off, and RF Gain/USB AF Output level adjusted to 30 db with no signals present. There is no

Re: [wsjt-devel] Suggestions for three extra bits in FT8

On 2017-07-11 12:12 PM, Tim Carlson wrote: Use one of the extra bits to indicate my desire for signal feedback. Email address for my callsign could be looked up from ??? I am fairly sure that FT8 uses the same message encoding as JT65, in which case FT8 also has the ability to send an

Re: [wsjt-devel] Suggestions for three extra bits in FT8

On 11/07/2017 19:12, Tim Carlson wrote: Would you consider that the first signal on the left is being overdriven somewhat? Or is that just a consequence of a stronger signal? Or is it some atmospheric condition causing the signal to spread? Hi Tim, hard to tell but it is all too common

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

I find that Shift+F11 or +F12 do indeed move my TX frequency but the RX frequency also moves a little as well. Erik EI4KF. -Original Message- From: Joe Taylor [mailto:j...@princeton.edu] Sent: 11 July 2017 18:19 To: WSJT software development Subject:

Re: [wsjt-devel] Suggestions for three extra bits in FT8

> On Jul 11, 2017, at 12:12 PM, Tim Carlson wrote: > > Would you consider that the first signal on the left is being overdriven > somewhat? Or is that just a consequence of a stronger signal? Or is it some > atmospheric condition causing the signal to spread? This could

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

Thanks for clarifying Joe, and thank you for the hard work you and the development team pour into this awesome software and exciting new modes! Sorry I misunderstood the suggestion. I do like the idea of quasi-channelizing FT8 since it's so dense that it has issues with decoding overlapping

Re: [wsjt-devel] Frequencies Missing in Configuration

On 11/07/2017 18:36, Tim Carlson wrote: Sometime between building and running the latest update and installing v1.8.0-rc1 r7847 (on OS X), the frequencies for my only named configuration all disappeared. The default configuration still has all the frequencies, so I cloned it and reset my

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

Hi all, For the auto 60Hz shift on answering CQs, I think this is a bad idea. We have never considered anything like an "auto shift" of Tx frequency. What we *might* do is provide an easy way to move your Tx frequency up or down manually in increments of 60 Hz (or perhaps some other

[wsjt-devel] Frequencies Missing in Configuration

Sometime between building and running the latest update and installing v1.8.0-rc1 r7847 (on OS X), the frequencies for my only named configuration all disappeared. The default configuration still has all the frequencies, so I cloned it and reset my preferences. I’ve always let the IARU Region

Re: [wsjt-devel] Distribution

On 11/07/2017 18:24, Laurie, VK3AMA wrote: I bet, most people are running r7843 (as am I) because Sourceforge sent an announcement email (to subscribers) that the rc1 installer was available for download. RR, Laurie. My mistake as mentioned in the other post. I will claim I did it so

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

I'm new to the group, so I hope it's okay to share my opinion as I've used JT9/65 for some time now and just started using FT8 last night. Personally, I don't care for the Call 1st or Call Weak options. Seems too automated for me. It's only a 15 second cycle, so no big deal if you don't get

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

> On Jul 11, 2017, at 9:42 AM, Joe Taylor wrote: > > We are interested in feedback from users on the question of partial QSO > automation. Should "Call 1st" be changed or removed? I think the way you’ve done it is just right. You are giving the operator the OPTION of

Re: [wsjt-devel] wsjt-devel Digest, Vol 41, Issue 158

After the announcement I did an update/upgrade and now have the option to compile the 1.8 branch as well. I compiled rc1 and version matches the rc1 on sourceforge. I've been running it for a few hours. Switch between FT8 and JTy5/9 works fine including frequency switch. In FT8 mode I find

Re: [wsjt-devel] Fwd: Re: r7848 TX starts within cycle

Hello Joe, Tuesday, July 11, 2017, 7:04:42 PM, you wrote: > I think you are objecting to the ability to start a transmission after > the nominl start time, thus ensuring that only some fraction of the > normal number of symbols will be sent. > If I have understood you correctly, I do not

Re: [wsjt-devel] Distribution

Because I saw somewhere that you would prefer for people to only run the official ones for now I downloaded from Joes link and it is 7843 so should I stop using it and build from JTSDK as normal ? Joe has released it so I fail to understand how it could be an unofficial source ? I am out so

Re: [wsjt-devel] Fwd: Re: r7848 TX starts within cycle

Hi Wolfgang, On 7/11/2017 12:22 PM, Wolfgang OE1MWW wrote: If I have "TX even/1st" unchecked and I "Enable TX", the transmission starts with CQ, disregarding the 15 sec. cycle time. I checked that again, this can happen twice a minute, depends on the setting and the activation of "Enable

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

Hi Bill, Yes, all the builds Launchpad are complete. I had trouble with Zesty and Clang, but believe it’s resolved now. Here’s The info: Current Version: WSJT-X 1.8.0 RC1 Ubuntu Distro’s: Trusty, Xenial, Yakkety, Zesty Supported Arach: i386, amd64, armv7, armv8, ppc64el

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

I like the feature. Suggestions for its “final”condition include - 1) May be enabled or disabled by operator 2) Apply equally to all modes 3) Work only with standard sequence messages 4) Require a minimum of one user intervention per contact (logging/reset sequence, after 73) 5) Support complex

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

I wouldn’t know what to do with a patch if it came up and bit me on the . Gratified though to know that it is in the pipeline for a future release. Thank you as always. Erik EI4KF. From: Black Michael via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net] Sent: 11 July 2017 16:08 To:

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

I think the fact that it's user selectable is important and I agree it should be kept because the turnaround time to respond to an inbound message is very short (this is especially noticeable for those of us that do 99% of our operating remotely where internet connections may prevent successful

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

On 11/07/17 16:42, Joe Taylor wrote: > We are interested in feedback from users on the question of partial QSO > automation. Should "Call 1st" be changed or removed? I think "Call 1st" is necessary, because there isn't nearly enough time for an operator to decide manually. As long as TX Enable

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

Thanks Joe. Since you're looking for opinions, hers's mine: 1. I like FT8. I like the fast exchange. I also like the automation so far. I agree that I would not want a "QSO machine". If that's what I wanted, I'd just turn off my mind and sit in front of the TV all day. However I like the

[wsjt-devel] Fwd: Re: r7848 TX starts within cycle

>> If I have "TX even/1st" unchecked and I "Enable TX", >> the transmission starts with CQ, disregarding the 15 sec. cycle time. I checked that again, this can happen twice a minute, depends on the setting and the activation of "Enable TX". Nevertheless, I think in terms of a 'clean protocol',

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

I did send the patch that fixes that...did you see it? de Mike W9MDB From: Erik - To: WSJT software development Sent: Tuesday, July 11, 2017 11:04 AM Subject: Re: [wsjt-devel] FT8 and "Call 1st" "We are interested in

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

keep fist call. ok on enable tx as u say it would be like sim 31 give up go out come back see hue u worked hi On 11 July 2017 at 17:02, Erik - wrote: > > "We are interested in feedback from users on the question of partial QSO > automation. Should "Call 1st" be changed

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

Joe, first, thanks for the intense amount of work you and the others have put into this project! The results keep getting better and better! You may recall years back a program named "Lan-Link. It was designed for HF/VHF packet and was fairly widespread using PK-232 and other TNCs.

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

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

Hi all, WSJT-X v1.8.0-rc1 includes an optional feature that is a significant departure from all previous WSJT-related software. When you call CQ in FT8 mode with both "Auto Seq" and "Call 1st" checked, the program automatically selects the first decoded response to your CQ and starts a QSO

Re: [wsjt-devel] WSJTX RC1

Ok I must have missed that. Calling CQ automatically is nothing new. This is done with keyers for both CW/SSB. Of course on CW/SSB, the operator has to ‘manually’ acknowledge a reply. Thanks for the clarification. 73 de Sebastian, W4AS > On Jul 11, 2017, at 11:21 AM, Steve Huston

Re: [wsjt-devel] WSJTX RC1

On Tue, Jul 11, 2017 at 11:09 AM, Seb wrote: > I am seeing the same problem (at least with FT8), Enable Tx goes out after > logging a QSO. I do NOT have Disable Tx after sending 73 enabled. I believe this was the intended behavior; from an email yesterday: On Mon, Jul 10,

Re: [wsjt-devel] r7848

Title: Re: [wsjt-devel] r7848 If I have "TX even/1st" unchecked and I "Enable TX", the transmission starts with CQ, disregarding the 15 sec. cycle time. 73 de Wolfgang OE1MWW -- Amateur radio is the most expensive type of free-of-charge communication! Amateurfunk ist die teuerste Art

Re: [wsjt-devel] WSJTX RC1

I am seeing the same problem (at least with FT8), Enable Tx goes out after logging a QSO. I do NOT have Disable Tx after sending 73 enabled. v1.8.0-rc1 on Windows 10 64-bit. 73 de Sebastian, W4AS > On Jul 11, 2017, at 6:13 AM, Gordon Higgins wrote: > > HI all using

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian AND armbian = success.

On 11/07/2017 14:45, Nikiforos Kontopoulos wrote: Actually I’ve just finished installing the deb file on my …..Armbian powered OrangePi Plus 2e (xfce) as I fortold right after the Raspbian version. As you have already guessed there was some messages about unmet dependencies concerning

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian AND armbian = success.

Hello dr Bill and many tks for your wonderful work! If only we lived a bit closer to lend you some of my hw for further testing. Actually I’ve just finished installing the deb file on my …..Armbian powered OrangePi Plus 2e (xfce) as I fortold right after the Raspbian version. As you have

Re: [wsjt-devel] Auto-sequence (r7848)

A small change to get that to work. Index: mainwindow.cpp===--- mainwindow.cpp      (revision 7849)+++ mainwindow.cpp      (working copy)@@ -2782,7 +2782,7 @@ void MainWindow::FT8_AutoSeq(QString message) {   int

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

On 11/07/17 14:18, Bill Somerville wrote: > On 11/07/2017 14:13, Richard Lamont wrote: >> On 11/07/17 13:44, Bill Somerville wrote: >> >>> I would appreciate reports of how well the Debian installer we have >>> provided with the WSJT-X v1.8.0 RC1 release works. As with the other >>> early release

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

On 11/07/2017 14:13, Richard Lamont wrote: On 11/07/17 13:44, Bill Somerville wrote: I would appreciate reports of how well the Debian installer we have provided with the WSJT-X v1.8.0 RC1 release works. As with the other early release kits you will have to install dependencies manually and

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

On 11/07/17 13:44, Bill Somerville wrote: > I would appreciate reports of how well the Debian installer we have > provided with the WSJT-X v1.8.0 RC1 release works. As with the other > early release kits you will have to install dependencies manually and > use rpm/yum/dnf to install them. In your

Re: [wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

On 11/07/2017 13:36, Nikiforos Kontopoulos wrote: Finished compiling and tested wsjt-x v1.8.0-rc1 on my raspberry pi 3 with Raspbian. 20m Jt65a + Ft8 work like a charm. Had some qsos already. Will also try to compile it on armbian for OrangePi plus 2e. Hi Nik, glad to here it is working

[wsjt-devel] wsjt-x v1.8.0-rc1 on raspbian = success.

Hello all. Finished compiling and tested wsjt-x v1.8.0-rc1 on my raspberry pi 3 with Raspbian. 20m Jt65a + Ft8 work like a charm. Had some qsos already. Will also try to compile it on armbian for OrangePi plus 2e. Best 73 de SV1EEX - Nik Sent from

[wsjt-devel] Beta Release: WSJT-X Version 1.8.0-rc1

The WSJT Development Group is pleased to announce a candidate release of WSJT-X Version 1.8.0. This is a beta release, already tested in the field by around 160 alpha-test users. A short list of new features and capabilities (including the new FT8 and FreqCal modes) can be found in the

[wsjt-devel] Beta Release: WSJT-X Version 1.8.0-rc1

The WSJT Development Group is pleased to announce a candidate release of WSJT-X Version 1.8.0. This is a beta release, already tested in the field by around 160 alpha-test users. A short list of new features and capabilities (including the new FT8 and FreqCal modes) can be found in the

Re: [wsjt-devel] Distribution

On 11/07/2017 12:35, James Shaver (N2ADV) wrote: Please be advised that there are some enterprising souls sharing links directly to Sourceforge distributing the Release Candidate files all over social media. Seeing posts crop up everywhere. Hi James, I'm afraid it is worse than that,

[wsjt-devel] Distribution

Please be advised that there are some enterprising souls sharing links directly to Sourceforge distributing the Release Candidate files. There have been posts all over Facebook so far and people are downloading like crazy.

[wsjt-devel] Distribution

Please be advised that there are some enterprising souls sharing links directly to Sourceforge distributing the Release Candidate files all over social media. Seeing posts crop up everywhere. -- Check out the vibrant

[wsjt-devel] wsjt-x 1.8RC! great! Only small flies in the ointment

JT8 seems to really rock'n'roll. Two fairly small problems: 1'st report after selecting a new callsign to work, should be kept until end of QSO. I'm to old for this fast-paced mode, I really need ½-1s more between overs to react before the next message hits

Re: [wsjt-devel] Possible bug in 7818 thru 7844

On 11/07/17 01:57, George J Molnar wrote: > I can confirm Gary’s report on 7844 for MacOS. > > George J Molnar, KF2T > Nevada, USA I can confirm it on 7844, 7848 and rc1 for Ubuntu 16.04. 73, Richard G4DYA --

Re: [wsjt-devel] WSJTX RC1

On 11/07/2017 10:57, char...@sucklingfamily.free-online.co.uk wrote: I must have missed the announcement that installers for 1.8.0 are available for download now. Hi Charlie and all, no such announcement has been made (ok perhaps one in that SourceForge automatically tells registered users

Re: [wsjt-devel] WSJTX RC1

HI all using ft8 v1.8.0-rc1 when i call cq with call 1st ticked workes fine call sequence as exppeted but when i have logged call, enable tx goes out @ i have to re enable to call cq again, i do not have disable tx after sending 73 ticked ?? now looking for dxcc n0 50 in ft8like mode,

Re: [wsjt-devel] WSJTX RC1

Hi Greg All understood. I must have missed the announcement that installers for 1.8.0 are available for download now. As you note, we should concentrate on testing that. 73 Charlie > Erik, All, > > At this point in the release cycle, its beneficial to the development team > to test the

Re: [wsjt-devel] WSJTX RC1

Greg – thank you, clear and concise. Another observation, probably already known but anyway: clearly FT8 usage has spiked today now that an official downloadable release is available. I am CQing on 20m and getting multiple callers. But no decodes. I have to stop CQing and wait several periods

Re: [wsjt-devel] WSJTX RC1

Erik, All, At this point in the release cycle, its beneficial to the development team to test the installation, as well as new features, on as many instances as possible. Bill created installers for most, if not all, the supported distributions. We should be testing that release, and providing

Re: [wsjt-devel] WSJTX RC1

Ok Iain, I think I follow. My weird way of thinking made me believe that 1.8.0-devel releases would go to 1.8.0 and not 1.7.1-devel releases. For the average user, it is confusing - or maybe it's just me I suppose. Thanks anyway. Erik. -Original Message- From: iain macdonnell - N6ML

[wsjt-devel] Auto-sequence (r7848)

EA8/G8BCG called CQ and I answered: EA8/G8BCG EI4KF G8BCG returned a report (I know why G8BCG and not EA8/G8BCG) Auto-sequence, though enabled, did not function and the entire contact had to be made manually. Of course that isn't a problem but I wonder if that is the expected behaviour. It

Re: [wsjt-devel] WSJTX RC1

Hi Charlie - I'm too thick to follow, please try again. Everyone can download the official release at https://sourceforge.net/projects/wsjt/files/wsjtx-1.8.0-rc1/wsjtx-1.8.0-rc1-win32.exe/download and get 1.8.0 but a svn update and compile gets 1.7.1 Can you elaborate a bit more on the

Re: [wsjt-devel] WSJTX RC1

On Mon, Jul 10, 2017 at 11:57 PM, Erik - wrote: > > I guess I’m having a ‘duh’ moment: r7848 is wsjtx-1.8.0-rc1 (I presume) ……….. > if I update svn and compile I get r7848 but it is 1.7.1-devel and this is > what I do not understand due to my total lack of knowledge. If

Re: [wsjt-devel] WSJTX RC1

Hi Erik No, r7848 is still 1.7.1. While preparations have been made for 1.8.0 those are not yet implemented in what we build. 73 Charlie G3WDG > > I guess I'm having a 'duh' moment: r7848 is wsjtx-1.8.0-rc1 (I presume) > ... if I update svn and compile I get r7848 but it is

[wsjt-devel] WSJTX RC1

I guess I'm having a 'duh' moment: r7848 is wsjtx-1.8.0-rc1 (I presume) ... if I update svn and compile I get r7848 but it is 1.7.1-devel and this is what I do not understand due to my total lack of knowledge. If someone could tell me in layman's terms why that is I would be grateful.