Re: [wsjt-devel] RC4 oddity

Tnx Rory. I do prefer split, true, but “CQ PLUS” is as close as I can get to “CQ FT8+” within the confines of the CQ message format i.e. CQ[space][up to 4 letters][space][my callsign][space][my 4-char grid]. I’m currently on 15m FT8+ a little above 2000 Hz on the usual VFO frequency,

[wsjt-devel] Contest mode: Crashing on attempting to log QSO

Running rc4. I've enabled the RR contest mode, and made several successful QSOs. However each time I click OK in the popup prompt for logging, WSJT-X exits immediately (with no message). Before starting the contest mode I clicked on "Reset cabrillo log". It looks like the QSOs are being logged

[wsjt-devel] CRASH on LOGGING

Hi Also, seeing this. On first log attempt in the mock contest, WSJTx crashes, no error message. Windows 64 Pro, ver1803 Build 17134.407 73 Gavin ZL3GAV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net

[wsjt-devel] RC4 Mock

I've noticed that WSJT-X logging thinks it's on local time - see the Contest Log - the QSOs do make it in Z time to my HRD log via JTAlert though. (We are +10hrs on UTC) There are some signals at 14.078 that I can't decode in RC4 or 1.9.1 - which is a bit of a mystery (they were there before the

Re: [wsjt-devel] CONTEST LOG TIME SHOWS LOCAL NOT UTC

On 20/11/2018 01:30, SKI W4PPC wrote: Just started to "play" and noticed (attached) that the log shows local time and not the UTC time Sincerely: Stephen Hi Stephen, thanks for reporting that issue. It is indeed a defect in the display of the time, unfortunately a similar defect lies

[wsjt-devel] crash on attempt to log

Bill, Start WSJT-X with RU mode enabled. Then without doing anything else, click on Log QSO, then OK. WSJT-X aborts. no error messages. Rick - K5GZR ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] crash on attempt to log

On 20/11/2018 02:22, K5GZR - Rick wrote: Bill, Start WSJT-X with RU mode enabled. Then without doing anything else, click on Log QSO, then OK. WSJT-X aborts… no error messages. Rick – K5GZR Hi Rick, thanks for the recipe but it is not that simple. It works for me. Still trying to work

Re: [wsjt-devel] RC 4 testa.

Ya know, Chuck, it's almost refreshing not having a bajillion sigs to hunt thru. I'm find RC4 just fine. I'm on 40m right now, have worked about 6 guys in the last 15 minutes, and had time to ready your email :-) 73, N0AN Hasan On Mon, Nov 19, 2018 at 12:35 PM Chuck Furman wrote: > I have gone

[wsjt-devel] Issues getting RC4 to work with Debian 9.6

I've been having some issues both in compiling and attempting to install the Debian AMD64 .deb package. I'm running Debian 9.6, fully patched. When I attempt to install the supplied .deb, it responds as follows. I checked a few and at least some dependencies may not be met in current Stretch

Re: [wsjt-devel] CONTEST LOG TIME SHOWS LOCAL NOT UTC

This is true but the adi output data shows UTC. Don AA5AU From: SKI W4PPC [mailto:ski.w4...@gmail.com] Sent: Monday, November 19, 2018 7:30 PM To: wsjt-devel@lists.sourceforge.net Subject: [wsjt-devel] CONTEST LOG TIME SHOWS LOCAL NOT UTC Just started to "play" and noticed (attached)

Re: [wsjt-devel] CRASH on LOGGING

I created an empty file, cabrillo.log, in the regular log directory. Logging no longer causes the program to crash. (This new file remains empty, but I think it is only filled when you choose export?) Mark KC1GWX On Mon, Nov 19, 2018 at 9:34 PM ZL3GAV wrote: > Hi > > > > Also, seeing this. >

[wsjt-devel] Contest Log: Received not filled in

In View > Contest Log The Sent is filled in, the Rx is empty Hasan ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] 2.0 RC4

GA Jim, Tnx qso earlier. Win10 decided it needed to update, so it started to misbehave. All is well., 73, N0AN Hasan On Mon, Nov 19, 2018 at 4:17 PM wrote: > Just my .02 worth. On 40m now with very compromised antenna ( a 20’ piece > of downspout) and I’m decoding a lot of 77bit traffic. Even

[wsjt-devel] RC4 RX autotune bug

Hi. I'm pretty sure I've seen this before with earlier WSJT-X versions. Maybe it's just my misunderstanding. I was calling CQ in WSJT-X v2 RC4 when N6ORB responded to me, off-frequency. Thanks David! We completed an FT8+ QSO no problem thanks to Auto Seq and Call 1st, but during the

Re: [wsjt-devel] Potential RC4 bug ? Auto Seq setting not sticky

On 11/19/2018 7:16 PM, Mark Spencer VE7AFZ wrote: I downloaded and installed a fresh copy of RC-4 onto a different computer (a laptop running Windows 10 pro) a noticed the same behaviour. While running FT8 if I select auto sequence and then re start the application auto sequence is not

[wsjt-devel] Attempt to write log in RTTY contest mode causes WSJT-X to terminate

Trying to participate in RTTY RU test tonight with RC4 on Win 10 pro. Was able to complete a QSO normally. But when I clicked OK on the Log QSO popup, there was a pause, then WSJT-X terminated with no warning or error message. Same happens in Field Day mode. Works fine when not in RU or FD

Re: [wsjt-devel] Potential RC4 bug ? Auto Seq setting not sticky

Hi: I downloaded and installed a fresh copy of RC-4 onto a different computer (a laptop running Windows 10 pro) a noticed the same behaviour. While running FT8 if I select auto sequence and then re start the application auto sequence is not enabled. I hope this information is of some use.

[wsjt-devel] 2.0 RC4

Just my .02 worth. On 40m now with very compromised antenna ( a 20' piece of downspout) and I'm decoding a lot of 77bit traffic. Even worked K1JT just a few ago. I'm convinced and looking forward to the final release. 73 Jim NY0J --- This email has been checked for viruses by

[wsjt-devel] CONTEST LOG TIME SHOWS LOCAL NOT UTC

Just started to "play" and noticed (attached) that the log shows local time and not the UTC time Sincerely: Stephen ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Contest mode: Crashing on attempting to log QSO

Microsoft Windows 10 Pro Version 10.0.17134 Build 17134 On Mon, Nov 19, 2018 at 9:12 PM Bill Somerville wrote: > On 19/11/2018 21:01, Mark James wrote: > > Running rc4. I've enabled the RR contest mode, and made several > > successful QSOs. > > > > However each time I click OK in the popup

[wsjt-devel] RU Contest - crash when logging

Linux Ubuntu MATE 18.04.1 AMD64 Popup box: Subprocess error Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a /home/superman/.local/share/WSJT-X -t /tmp/WSJT-X Process crashed Console error: [20181119 20:23:16.319 CST W] QProcess: Destroyed while process ("/usr/bin/jt9"

Re: [wsjt-devel] RU Contest - crash when logging

On 20/11/2018 02:29, Dave J Barnes wrote: Linux Ubuntu MATE 18.04.1 AMD64 Popup box: Subprocess error Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a /home/superman/.local/share/WSJT-X -t /tmp/WSJT-X Process crashed Console error: [20181119 20:23:16.319 CST W] QProcess

[wsjt-devel] Erased wsjtx_log.adi but still getting green CQs

Erased wsjt_log.adi hoping I would get fresh color coded CQs when set up for the RU Test tonight but all CQs are still in GREEN. What am I doing wrong? Don AA5AU ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net

Re: [wsjt-devel] Potential RC4 bug ? Auto Seq setting not sticky Off List

Hi Joe. I don't really follow the WSJT reflector any more (to many emails to wade thru for my taste) and I must have missed the bulk of the announcements on this list pertaining to this issue. A quick search via my iPhone using the phrase "auto sequence" in my email in box only turned up one

Re: [wsjt-devel] Potential RC4 bug ? Auto Seq setting not sticky Off List

On 20/11/2018 01:06, Mark Spencer wrote: Hi Joe. I don't really follow the WSJT reflector any more (to many emails to wade thru for my taste) and I must have missed the bulk of the announcements on this list pertaining to this issue. A quick search via my iPhone using the phrase "auto

Re: [wsjt-devel] Contest mode: Crashing on attempting to log QSO

On 19/11/2018 21:01, Mark James wrote: Running rc4. I've enabled the RR contest mode, and made several successful QSOs. However each time I click OK in the popup prompt for logging, WSJT-X exits immediately (with no message). Before starting the contest mode I clicked on "Reset cabrillo

Re: [wsjt-devel] RTTY RU Test Results

John, One question since you were using N1MM as well in the test. On the Modes tab in N1MM Config I checked "Always RTTY." Logging directly from WSJT-X/JTAlerts into the ARRLRTTY each Q hit the N1MM log fine. Each Q was logged as an FT8 Q. Unfortunately N1MM seems rather fussy as it gave all

[wsjt-devel] RU Test results - only green highlighted CQs

Could never get highlighting of CQ stations to work correctly after clearing wsjtx_log.adi. Joe suggested I restart the program. I did and even rebooted the PC thinking something was being held in memory, but none of that worked. I also searched for any other wsjtx_log.adi files and there were

Re: [wsjt-devel] RU Contest - crash when logging

Ubuntu MATE 18.04.1 AMD64 Popup box: Subprocess error Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a /home/superman/.local/share/WSJT-X -t /tmp/WSJT-X Process crashed Console error: [20181119 20:23:16.319 CST W] QProcess: Destroyed while process ("/usr/bin/jt9") is sti

Re: [wsjt-devel] RU results

On 20/11/2018 04:02, Carey Fisher wrote: 2. Odd timing happened a few times. A Tx started before the decoding of Rx had finished. See attached for an example. Notice the two lines at 020600. Hi Carey, that is normal, if your CPU is very busy or the decoding is complex the decode may not

[wsjt-devel] RTTY RU Test - Contest Log

Overall perfect operation. No crashes with WSJTx or JTAlert combination with HRD LB logged from WSTJx directly. Win 10 Pro w/plenty of SSD RAM and system memory. All current versions. Problems: 1) Time logged as local not UTC (already noted by many others) 2) Entry sequence (left column) 1-9

Re: [wsjt-devel] RU Contest - crash when logging

On 20/11/2018 03:46, Carey Fisher wrote: Bill, My logging to ACLog worked correctly, sent and rcvd RST, except for Mexico QSO. Screenshot attached. 73, WB4HXE, Carey Hi Carey, can you extract the section of your ALL.TXT file that covers the QSO with XE1MEX, the entry from the wsjtx_log.adi

[wsjt-devel] RTTy mock test

Lots of fun on a chilly November evening. My feet were cold but the band was hot. Lots of signals. It mostly went pretty smoothly. 42 logged instances of 77 bit goodness. Just a few comments, some of which may be expected behavior. When calling a station with TX2, if the other op responds

Re: [wsjt-devel] RU Contest - crash when logging

t:* Re: [wsjt-devel] RU Contest - crash when logging >> >> >> >> On 20/11/2018 02:29, Dave J Barnes wrote: >> >> Linux Ubuntu MATE 18.04.1 AMD64 >> >> Popup box: Subprocess error >> >> >> >> Running: /usr/bin/jt9 -s WSJT-X -w 1 -m

[wsjt-devel] RTTY RU "test"

Win10, IC-7300, WSJT-X V2.0.0 rc4 As others have reported the "contest log" window and the Cabrillo file show local date and time 11-19-18, 9:15. I renamed the Cabrillo log before the contest to avoid confusion.  No cabrillo file was created during the test. The Cabrillo file was created after

Re: [wsjt-devel] wsjt-devel Digest, Vol 57, Issue 148

A log problem I had was that there was no way to delete a couple of duplicates I got from out of sequence operations. I could erase the signal report and exchange, which would enable me to later see which entries were bogus, but could not erase other fields like call sign. I had several

Re: [wsjt-devel] RU results

Thanks Bill, I can see a processor upgrade in my future! 73, WB4HXE On Mon, Nov 19, 2018 at 11:09 PM Bill Somerville wrote: > On 20/11/2018 04:02, Carey Fisher wrote: > > 2. Odd timing happened a few times. A Tx started before the decoding of Rx > had finished. See attached for an example.

[wsjt-devel] RU Practice

I used wsjt-x standalone in the RU Practice. I saw only one anomaly, besides the known bug of all CQ’s being colored green. On two occasions, when I double-clicked a call in the left pane, I actually called the station just below the one I clicked on. For example, I tried to call AA5AU, but

[wsjt-devel] RU: duplicate log entries

Hi! tonight test: while calling VP8LP few times, he was not receiving my RR73, so he gave 023 to somebody else. (I got 025, hopefully: I will never know, he is not in LotW). Anyhow, QSOs were logged by automatic logging. So, I have three times same station in the log. Proposal: do not log

[wsjt-devel] RTTY RU Test Results

Everything worked marvelously here, though I noticed the WSJT-X Contest Log was recording local times. Moot for me since N1MM+ was doing the primary logging/tracking mults/etc. Happy camper here; tnx so very much to all the WSJT-X team. 73 John W7CD ARRLRTTY Summary Sheet Start

[wsjt-devel] RU results

1. Logging to ACLog worked well for me. 2. Odd timing happened a few times. A Tx started before the decoding of Rx had finished. See attached for an example. Notice the two lines at 020600. 73, WB4HXE -- Carey Fisher careyfis...@gmail.com ___

Re: [wsjt-devel] RU Contest - crash when logging

- crash when logging > > > > On 20/11/2018 02:29, Dave J Barnes wrote: > > Linux Ubuntu MATE 18.04.1 AMD64 > > Popup box: Subprocess error > > > > Running: /usr/bin/jt9 -s WSJT-X -w 1 -m 3 -e /usr/bin -a > /home/superman/.local/share/WSJT-X -t /tmp/WSJT

Re: [wsjt-devel] Contest mode: Crashing on attempting to log QSO

It worked perfectly for me, except for one operator error. I worked 27 stations, including a new band-entity via LOTW. I forgot that it is JT-Alert, not WSJT-X, that pushes logging info to HRD Logbook, and I closed JT-Alert in the middle of the contest, thinking I wouldn't need alerts since I was

[wsjt-devel] RTTY run

Evening: Overall perfect operation. No crashes with WSJTx or JTAlert combination with N3FLP's ACL 6.4 logging WSJT-x directly without issues to time UTC/Local...(other issue with time on earlier email was already noted).. running on Window's 7 Pro. Enjoyed the time. Thank you. Sincerely:

Re: [wsjt-devel] CRASH on LOGGING

On 11/19/2018 6:31 PM, ZL3GAV wrote: Hi Also, seeing this. On first log attempt in the mock contest, WSJTx crashes, no error message. Windows 64 Pro, ver1803 Build 17134.407 Seeing exactly this problem, too. Win10 Pro 64. Dana K6JQ 73 Gavin ZL3GAV

Re: [wsjt-devel] RU Contest - crash when logging

Hi Bill, Carey,Sorry Carey but you are not in log and therefore you did not get the report. I revised the .wav files and I did not find your call sign at the time you recorded the QSO  (date and time are local PC not UTC as already reported by others)This is my log: 73AlexXE1MEX On

Re: [wsjt-devel] RC 4 testa.

I have it downloaded but have not fully migrated yet. Reason, on the west coast of the US there are very few if any stations I can hear and work yet. Scotty W7PSK -- Original Message -- From: "M Lewton" To: "WSJT software development" Sent: 11/19/2018 8:06:51 AM Subject: Re:

Re: [wsjt-devel] Reminder: FT8 mock contest tomorrow

It would be fun, but the wrong time of the day. 0400-0500 local time here, the graveyard shift. Good luck everybody! De OH6VDA Tom > 18. nov. 2018 kl. 20:15 skrev Joe Taylor : > > A one-hour "practice contest" will be held tomorrow using the FT8 mode and > the ARRL RTTY Roundup rules. > >

Re: [wsjt-devel] Reminder: FT8 mock contest tomorrow

You can participate. Leave your station on so it captures the fun. Analyze the action when you are done. On Mon, Nov 19, 2018 at 11:50 AM Tom Ramberg via wsjt-devel < wsjt-devel@lists.sourceforge.net> wrote: > It would be fun, but the wrong time of the day. 0400-0500 local time here, > the

Re: [wsjt-devel] RC 4 testa.

Amen I tried RC4 for the last hr. with CQ's on 160-30 and got many replies but not one using RC4!! Apparently a very small part of the population using RC4. What's it going take to get them to change their ways? ;-) 73 Dwight NS9I On 11/17/2018 4:01 AM, Krzysztof Krzemiński wrote:

Re: [wsjt-devel] RC 4 testa.

I used rc3 for about 1/2 hour on several bands using 77 bit to tx and rx. I got one reply when there were hundreds on the bands. Possibly more will be on the practice today. Tuesday, November 20, 0200-0300 UTC (Monday evening, NA time Regards and 73s VE3FBZ London Amateur Radio Club

Re: [wsjt-devel] RC 4 testa.

November 30th, when it self-destructs. Neil, KN3ILZ On 11/19/2018 3:04 AM, dgb wrote: Amen I tried RC4 for the last hr. with CQ's on 160-30 and got many replies but not one using RC4!! Apparently a very small part of the population using RC4. What's it going take to get them to

Re: [wsjt-devel] RC 4 testa.

Alas 1.9.1 has no “use or discard by” date. Going to be an uphill slog on HF FT8. Look how many comments have already been generated. Geo/KF2T > On Nov 19, 2018, at 8:58 AM, Neil Zampella wrote: > > November 30th, when it self-destructs. > > Neil, KN3ILZ > On 11/19/2018 3:04 AM, dgb

Re: [wsjt-devel] RC 4 testa.

I suspect a large population is using one of the mutants (JTDX etc.) and probably don't even know about any of this. That said... I have used both and WSJT-X pretty much offers everything now that I looked for in JTDX. On Mon, Nov 19, 2018 at 3:34 AM dgb wrote: > Amen > > I tried RC4 for

Re: [wsjt-devel] RC 4 testa.

>> November 30th, when it self-destructs. As least Version 2 users with prior RC-Version  Just an idea – what is to implement in the first final Version a feature to send a free text, which can be red on old versions like “pls update wsjt” or so ? Hopefully the switch will go faster than.

Re: [wsjt-devel] RC 4 testa.

Check https://pskreporter.info/cgi-bin/pskstats.pl\ There are still 81 people currently using the venerable JT65-HF. Almost 4,000 on MSHV and JTDX combined. Multiple users on WSJT-X 1.6, 1.7, 1.8, and a sea of old RC’s. I’m going to take a

Re: [wsjt-devel] RC 4 testa.

Yes, The most evident problem is exactly this, IMHO: too many "WSJT-X surrogates" around are delaying the huge mass to swap to WSJT-X version 2.0, 77-bit FT8. -- 73 de Marco, PY1ZRJ Il 19/11/18 12:16, Ryan Tourge ha scritto: > I suspect a large population is using one of the mutants (JTDX

Re: [wsjt-devel] RC 4 testa.

Hi all. Undoubtedly there is a curve, somewhat slow and being conservative, for those things as application changes. The counterpart is to force peoples model of change. Advice on start, etc. Not the evil, as patch dates for one of the most used client OS. Let's look when RC3 will be EOL, not that

Re: [wsjt-devel] RC 4 testa.

Hi all, We Mutants and surrogates are watching closely ;) don't worry about us. Both or more software's are installed. Best regards and RR73 9A5CW Datuma pon, 19. stu 2018. 15:21 Ryan Tourge I suspect a large population is using one of the mutants (JTDX etc.) and > probably don't even know

Re: [wsjt-devel] RC 4 testa.

I look at it sort of like a new dx/band/state challenge. I also do not restrict myself solely to tx above 2k and, sometimes, tx “CQ 77”. Al Pawlowski, K6AVP Los Osos, CA USA > On Nov 19, 2018, at 07:12, wsjt-devel-requ...@lists.sourceforge.net wrote: > > [wsjt-devel] RC 4 testa.

Re: [wsjt-devel] RC 4 testa.

Patrick, If it wasn't for mutants I wouldn't have had the pleasure to work you. I was probably using JTDX for this contact. Call sign Worked Date/Time Band Mode Freq QSL *DXCC* Details N2YQT 9A5CW 2018-02-25 21:01:00 30M FT8 10.13724

Re: [wsjt-devel] RC 4 testa.

I view myself as being a pioneer with RC4 and don't expect that there will be many stations using it now, but that the number using it will gradually increase over time. As Joe said, there is going to be confusion for a while. A great many hams will not even know that RC4 exists. I would not have

Re: [wsjt-devel] RC 4 testa.

Hi Ryan, I was joking a bit, but most likely people still doesn't want to migrate on 77 bit bcs of lack of activity, software or other personal reasons. Probably they can live with 75 bits... Thanks for the QSO. 73 Patrik 9A5CW ... Evolution Different characteristics tend to exist within any

Re: [wsjt-devel] RC 4 testa.

...Windows XP is still being used in several home computer around the globe, I hope that this will be not the same for WSJT-X. On the other hand, freedom is a wonderful thing and we cannot impose others using a different software. My hope is that hams will at least give a try to WSJT-X

Re: [wsjt-devel] RC 4 testa.

Hello I have been trying to use rc4 since the morning it was released. Probably made 10 or 20 contacts each day. This morning for one hour on 40 meters I called CQ many, many times no luck. Lots of signals but no decodes. A few answered in the waterfall but they didn't decode. I get out quite

Re: [wsjt-devel] RC 4 testa.

I have gone to RC4 and I’m not looking back. I guess everyone is desperate to make as many contacts as possible. If you are, maybe you shouldn’t be a beta tester. I’m making lots of contacts on 20/40 Meters. And when I can’t find anyone, I switch to JT65. Remember, you can’t just listen. Call CQ.

Re: [wsjt-devel] RC 4 testa.

Oh, yes, Lets give up everybody. Joe and his team was wasting his time, creating for you previous perfect version. Of course previous version was perfect from the start. No one RC was created. So, why to help him now? He should be perfect as you are. They are doing a lot of RC's, why, software

Re: [wsjt-devel] RC 4 testa.

Better bring a fresh bottle. I'm out. On 11/19/2018 14:27, George J. Molnar wrote: I’m going to take a deep breath or six. Then maybe join in the Scotch Drinking Club. --- This email has been checked for viruses by AVG. https://www.avg.com ___