Perfect answer, thanks Bill.
73 Keith G6NHU
> On 2 Dec 2018, at 00:42, Bill Somerville wrote:
>
>
> currently WSJT-X can only help you with detecting dupes when they call CQ .
> To get this working you must move aside your wsjtx_log.adi file (you will
> want to put it back after the contest)
Hi Again:
Thinking again about this thing, best explanation ContestLog file got
corrupted probably at entry 26 and that affected no more QSO were being
logged. Yes, there was something I remember happening with the popup QSO
window where garbage from PPT was received at one of the fields. Have
c
KI4US. I saw getting decoded and spotted several times. I guess
propagation was not helping to the folks I was trying to work?
On Sun, Dec 2, 2018 at 12:19 AM Paul Kube wrote:
> Or, send a bunch of CQ's and type your call in to
> https://pskreporter.info/pskmap.html.
>
> 73, Paul K6PO
>
> On
Everything worked well for me. I had a lot of decodes and contacts. My best
DX was Finland. The key commands of shift + F12 and shift +F11 to move the
xmt freq up or down 60 Hz was very handy. And being able to extend the
bandwidth using ctrl + shift + F12 by 2 KHz was great. I made most of my
con
Or, send a bunch of CQ's and type your call in to
https://pskreporter.info/pskmap.html.
73, Paul K6PO
On Sat, Dec 1, 2018 at 8:50 PM Edfel Rivera wrote:
> Hi:
>
> Your callsign is?
>
> Could check, I am at 40m, KP4AJ
>
> On Sat, Dec 1, 2018 at 11:45 PM Bill Pence wrote:
>
>> Yep
>> I see lot
Hi:
Your callsign is?
Could check, I am at 40m, KP4AJ
On Sat, Dec 1, 2018 at 11:45 PM Bill Pence wrote:
> Yep
> I see lots of cq ru using rc5. Few answers when i reply.
>
> On Sat, Dec 1, 2018, 11:40 PM Edfel Rivera
>> Hi:
>>
>> Be sure to use frequencies 7080 40m, 14130 20m. Also clock sy
What frequency are you on?
On Saturday, December 1, 2018, 10:33:56 PM CST, Dave Barr
wrote:
During the FT8 Roundup, I am decoding only a fraction of the signals I
can hear and see on the water fall. RX selectivity is wide. RF gain
has been lowered. The rx level bar hovers betwe
Yep
I see lots of cq ru using rc5. Few answers when i reply.
On Sat, Dec 1, 2018, 11:40 PM Edfel Rivera Hi:
>
> Be sure to use frequencies 7080 40m, 14130 20m. Also clock sync is
> essential. UTC diff no more than 1.5 seconds. RC5 testing HUGE today (day
> and night). Worked bunch stations.
I made a few QSOs with RC5 feeding MacLoggerDX the N1MM+ data. The main QSO
information came through fine, but there was no exchange data for my log..
An exchange of 539 NJ from K1JT is apparently built from 539 and
NJ,
and 549 0044 for CE1OEB from 549 and 0044.
It doesn’t seem as if you send
Hi:
Be sure to use frequencies 7080 40m, 14130 20m. Also clock sync is
essential. UTC diff no more than 1.5 seconds. RC5 testing HUGE today (day
and night). Worked bunch stations.
73'
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 11:33 PM Dave Barr wrote:
> During the FT8 Roundup, I am decoding only
I have opposite. I decode many, but few qso's...
I guess I am in a propagation hole right now
On Sat, Dec 1, 2018, 11:34 PM Dave Barr During the FT8 Roundup, I am decoding only a fraction of the signals I
> can hear and see on the water fall. RX selectivity is wide. RF gain
> has been lowered.
During the FT8 Roundup, I am decoding only a fraction of the signals I
can hear and see on the water fall. RX selectivity is wide. RF gain
has been lowered. The rx level bar hovers between 50 and 60. Yet I
decode only a few, or one, or none of the signals present. Earlier RCs
and 1.9 had n
Yes, I am (attached). Not a biggie, I deleted and recreated that log entry
again with the correct band. I suspect it got confused because I had 40M
selected in the main program, even thouth I entered 20m in the log pop-up. It
came out correct after put WSJT-X back on 20. Except for the time, th
Hi:
Forgot to tell (previous post) those recent QSO were using TAB1.
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 10:08 PM Edfel Rivera wrote:
> Hi All:
>
> Well, after editing the 569 0064 to 569 FL (row 26) QSO are logging again
> and nicely. What was the problem, not sure but Recevd 569 0064 was the
Hi All:
Well, after editing the 569 0064 to 569 FL (row 26) QSO are logging again
and nicely. What was the problem, not sure but Recevd 569 0064 was the
only thing I changed to get the QSO saving again. See below. QSO time
reflects how long this issue interrupted QSO logging. BTW, QSO logging n
On 02/12/2018 02:52, Jim Shorney wrote:
I manually created a log entry and it accepted it this time. Now, however, I am
trying to correct the hand in the log to 20m, but 20m does not show up on the
selection list when on that line. In fact, it only seems to show up on the list
for entries that
That seems to have been the problem with my WL7CG contact. I manually created a
log entry and it accepted it this time. Now, however, I am trying to correct
the hand in the log to 20m, but 20m does not show up on the selection list when
on that line. In fact, it only seems to show up on the li
Hi:
Well, this is nonsense. After editing last recorded QSO which received
column was 569 0064 for LW5DR . I changed to FL just to test. Be assured
I didn't edited that file in anyway before trying this. After that QSO were
again saved. I have worked:
023330 -24 0.1 1564 ~ KP4AJ MI0LLG RR73
Hi Edfel,
sorry I was not clear. The edits I am referring to are to the Contest
Log window rows. As it stands in WSJT-X v2.0.0 RC5 edits to fields in
the Contest Log window table are not committed until you change the
focus to another row. Until you do that pending edits will block the
additi
Hi Bill:
I filled those fields (operator, name) because fields were empty (not
populated by the program) and because program pop up message was Invalid
QSO. Was a way to test if that empty fields were the reason for the error.
Anyway, Invalid QSO popups keeps happening and they are empty at those
Hi JIm:
Yes, I tried that too. Name is not more there long ago.
Thanks!
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 8:57 PM Jim Shorney wrote:
>
> I don't know if there is any kind of check on the Operator field for
> something that looks like a valid call, but you may want to put your call
> in the
Hi Edfel,
I am fairly certain that the logging lockout when al the required fields
are populated is related to unsaved edits to the contest log window. As
it stands you have to move to another row to commit any edits, then you
can log a new row.
I am surprised how many reports of this there
I don't know if there is any kind of check on the Operator field for something
that looks like a valid call, but you may want to put your call in there
anyway. Having your name in there is bound to confuse some software
somewhere... :)
73
-Jim
NU0C
On Sat, 1 Dec 2018 20:41:37 -0500
Edfel R
I have noticed a specific scenario that has happened several times during the
contest. This happens when I have called a CQing station two or three times
with no reply and I bail and go call another. Then I see the first station
replying to me with TX3 while I am calling the new one. So I bail
Hi Jim:
See the another popup window 'Invalid QSO' below, at capture you are
refering, I tried placing my name in Operator to see if having that field
blank was the problem. There are also others with similar problem:
https://mail.google.com/mail/u/0/#inbox/QgrcJHrjBQfqKcQGxpzNBkSHmpVzzlKMjDV
7
Hi Bill:
Not big deal or a must. Probably when working with standard frequencies
the 'anomaly' is negligible.
Thank you all development team!!
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 8:18 PM Bill Somerville
wrote:
> On 02/12/2018 01:09, Edfel Rivera wrote:
> > Hi:
> >
> > If I access configu
Andy,
the starting freq for 40m was 7.080 .. it was very busy here in PA.
Neil, KN3ILZ
On 12/1/2018 2:46 PM, Andreas Ma wrote:
Hi David and all
Same problem here. I’m on 7090 (40m as it is nearly 9 p.m. here)
having plenty of signals in the waterfall display, but very few
decodes. Changing
I wonder if it does not like that you have your name in the OPERATOR field
instead of your callsign. AFAIK the ADIF field that this maps to is for
operator call, which CAN be different from the station call under certain
circumstances.
73
-Jim
NU0C
On Sat, 1 Dec 2018 17:32:38 -0500
Edfel Rive
On 02/12/2018 01:09, Edfel Rivera wrote:
Hi:
If I access configuration (was at 7.080.00, when exit configuration,
program sets frequency to 7.078.00. Just pointing if this is the
intended behavior. IMO when exit configuration screen, frequency
should not change.
Thanks.
Edfel
KP4AJ
Hi
Hi:
If I access configuration (was at 7.080.00, when exit configuration,
program sets frequency to 7.078.00. Just pointing if this is the intended
behavior. IMO when exit configuration screen, frequency should not
change.
Thanks.
Edfel
KP4AJ
___
wsjt
Bill:
Sorry, yes TAB1 populates Rcp Sent and Exc Sent but program refuses to log
QSO using both option automatic or Promp me. Disabled logging so I can
continue. I even trioed closing everything but WSJTX. I clsed JTAlert,
Firefox. etc.
Thanks again,
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 7:57
No, I didn’t. Thanks.
Dave / NX6D
From: Bill Somerville
Sent: Saturday, December 1, 2018 4:33:52 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] "New Call", working?
On 02/12/2018 00:17, David Fisher wrote:
Am I right in thinking that the “ne
I had the same happen with a contact with WL7CG. Nothing I did would make it
acceptable to the program. I just bailed and will enter it manually later.
73
-Jim
NU0C
On Sat, 1 Dec 2018 17:45:55 -0500
Edfel Rivera wrote:
> Hi Bill:
>
> TAB1 populates Recp Sent and Exc Sent, GRID was not popu
Bill,
Thanks for that explanation. I realise its fairly early days and ok on the
current limited capabilities in this space.
To make contest mode more viable IMHO it would need to provide dupe feedback on
any callsign I selected at the time of selection for calling (in search and
pounce) or as
My guess with N3FJP RTTY Log is that everything is looking for AC Log and
not that log. Sounds like maybe a fix needed in JT Assist..
Mike K7DD
On Sat, Dec 1, 2018 at 4:48 PM Bill Somerville
wrote:
> On 02/12/2018 00:25, David Fisher wrote:
>
> FWIW, Bill, it’s not particularly obvious that
On 02/12/2018 00:25, David Fisher wrote:
FWIW, Bill, it’s not particularly obvious that there is a horizontal
association between the Field Day / RTTY Roundup options and the
“Exch” fields. They are pretty far apart horizontally from the
options they are associated with. Lots of mistakes wil
On 02/12/2018 00:34, Grant VK5GR wrote:
Keith,
I have been trying to figure out how to get dupe alerts etc too.
N1MM doesn’t do it - because the station is not loaded into the main entry
window of N1MM and only appears at the end of the QSO directly into the log via
UDP - after the damage has
FWIW, Bill, it’s not particularly obvious that there is a horizontal
association between the Field Day / RTTY Roundup options and the “Exch” fields.
They are pretty far apart horizontally from the options they are associated
with. Lots of mistakes will be made in this configuration.
Dave /
On 02/12/2018 00:17, David Fisher wrote:
Am I right in thinking that the “new call” color coding is not
working? When I enable this option, I never see any calls highlighted
this way.
Dave / NX6D
Hi Dave,
do you have the "Settings->General->Show DXCC, grid, and worked-before
status" opt
Keith,
I have been trying to figure out how to get dupe alerts etc too.
N1MM doesn’t do it - because the station is not loaded into the main entry
window of N1MM and only appears at the end of the QSO directly into the log via
UDP - after the damage has been done so to speak.
WSJT has no dupe
FYI - I am also having N3FJP logging issues at same time. It is"ARRL RTTY"
s/w and API all set up and working (less the data for send report). But
still issue. WSJT-X is sending all data over, less "St/Pr/#" field (I'm
manually inputting this)
[image: image.png]
and WSJT-X returning error:
[image:
Am I right in thinking that the “new call” color coding is not working? When I
enable this option, I never see any calls highlighted this way.
Dave / NX6D
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/list
Well that worked for 1 qso so far but it is working now. Thanks, I was
confusing the TAB1 to the TAB key on the keyboard. Senior moment.
TNX K7dd
On Sat, Dec 1, 2018 at 3:39 PM Bill Somerville
wrote:
> On 01/12/2018 23:33, Michael Baker wrote:
> > I tried a full reset of everything. Now it do
This zombie topic has been around since the early days of FT8. According to
some, the arrows point the correct way, according to others they point
backwards. Like the arrows, there are arguments both ways. Clearly, it’s an
individual thing.
Would it not be possible (at some future point –
On 01/12/2018 23:33, Michael Baker wrote:
I tried a full reset of everything. Now it doesn't turn the program
off but the report fields are still left blank. TAB only moves the
cursor. Reset the time with Dimension 4 just because.
Still get "can't log" error message but when the data is put in
I tried a full reset of everything. Now it doesn't turn the program off but
the report fields are still left blank. TAB only moves the cursor. Reset
the time with Dimension 4 just because.
Still get "can't log" error message but when the data is put in all is ok.
For some unknown reason my N3FJP So
Confirmed - not value of sent/recv.
Going to restart everything...
On Sat, Dec 1, 2018 at 3:18 PM Tim Thorson wrote:
> My fields blank = Rpt Sent & Exch sent.
>
> I enter missing info along with Name and hit [OK] = error
>
> Last few QSOs I could not log (auto)
>
> Q: assume Exch sent would be
My fields blank = Rpt Sent & Exch sent.
I enter missing info along with Name and hit [OK] = error
Last few QSOs I could not log (auto)
Q: assume Exch sent would be (for me) "536 CA" as example..(?)
On Sat, Dec 1, 2018 at 3:10 PM Bill Somerville
wrote:
> On 01/12/2018 23:03, Tim Thorson wro
On 01/12/2018 23:03, Tim Thorson wrote:
Still an issue. Happens (why?) in my case, when sent & Rcvd reports
are equal/same... ...still testing,
Hi Tim,
is the lockout happening after you have edited a row in the Contest Log
window?
73
Bill
G4WJS.
__
Still an issue. Happens (why?) in my case, when sent & Rcvd reports are
equal/same... ...still testing,
On Sat, Dec 1, 2018 at 12:48 PM Edfel Rivera wrote:
> Hi All:
>
> For those getting annoyed for the popuo telling invalid QSO, you just have
> to fill Rcp Sent and Exc Sent. Nothing more cli
Hi Bill:
Not wanting to save QSO here is another.
Thanks again
Edfel
On Sat, Dec 1, 2018 at 5:58 PM Michael Baker wrote:
> Now mine is closing the program when I hit log entry. UG!
>
> Mike K7DD
>
> On Sat, Dec 1, 2018 at 2:49 PM Edfel Rivera wrote:
>
>> Hi Bill:
>>
>> TAB1 populates Rec
On 01/12/2018 22:54, Michael Baker wrote:
Now mine is closing the program when I hit log entry. UG!
Mike K7DD
Hi Mike,
any message box with an error?
73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.s
Now mine is closing the program when I hit log entry. UG!
Mike K7DD
On Sat, Dec 1, 2018 at 2:49 PM Edfel Rivera wrote:
> Hi Bill:
>
> TAB1 populates Recp Sent and Exc Sent, GRID was not populated. However,
> QSO refused to get logged even if I complete blank fields. Similar happen
> with N5
On 12/1/2018 2:26 PM, Bill Somerville wrote:
On 01/12/2018 22:20, Dana Myers wrote:
On 12/1/2018 1:56 PM, Edfel Rivera wrote:
Hi Again:
Same happens with "Prompt me to log QSO". Those fields are not populated.
Same here.
Dana K6JQ
Hi Edfel and Dana,
if you are using Tab 2 in WSJT-X th
Hi Bill:
TAB1 populates Recp Sent and Exc Sent, GRID was not populated. However, QSO
refused to get logged even if I complete blank fields. Similar happen with
N5OK.
73'
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 5:30 PM Bill Somerville
wrote:
> On 01/12/2018 22:20, Dana Myers wrote:
> > On 12/1/2018
Same issue here. Had to insert the sent report before it would go to the log.
Even after when I did an ADIF file I have stuff to fix. Instead of the 539
etc. it just put out 59. It did recognize it was Digital/FT8.
Ed.. AB4IQ
From: Scott L. [mailto:sco...@gmail.com]
Sent: Saturday, D
Hi:
QSO below was refused to Log into ContestLog. ContestLog have 26 entries
also other QSO after that was logged. Not sure why but had to cancel
logging of N5OK QSO.
Thanks.
73'
Edfel
KP4AJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.ne
On 01/12/2018 22:20, Dana Myers wrote:
On 12/1/2018 1:56 PM, Edfel Rivera wrote:
Hi Again:
Same happens with "Prompt me to log QSO". Those fields are not
populated.
Same here.
Dana K6JQ
Hi Edfel and Dana,
if you are using Tab 2 in WSJT-X then try switching to Tab 1.
73
Bill
G4WJS.
On 12/1/2018 1:56 PM, Edfel Rivera wrote:
Hi Again:
Same happens with "Prompt me to log QSO". Those fields are not populated.
Same here.
Dana K6JQ
Thanks.
Edfel
On Sat, Dec 1, 2018 at 4:55 PM Edfel Rivera mailto:edfelj...@gmail.com>> wrote:
Hi Bill:
Thanks for reply. Enclose
Hi Again:
Same happens with "Prompt me to log QSO". Those fields are not populated.
Thanks.
Edfel
On Sat, Dec 1, 2018 at 4:55 PM Edfel Rivera wrote:
> Hi Bill:
>
> Thanks for reply. Enclosed the reporting setting.
>
> 73'
>
> Edfel
> KP4AJ
>
> On Sat, Dec 1, 2018 at 4:30 PM Bill Somerville
Hi Bill:
Thanks for reply. Enclosed the reporting setting.
73'
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 4:30 PM Bill Somerville
wrote:
> On 01/12/2018 20:45, Edfel Rivera wrote:
> > For those getting annoyed for the popuo telling invalid QSO, you just
> > have to fill Rcp Sent and Exc Sent. Nothi
Synchronized y computer clock with atomic clock and have lots of
decodes now
NM5Z
On 12/1/2018 1:31 PM, Don Hill AA5AU
wrote:
Check
your clock?
From:
On 01/12/2018 20:45, Edfel Rivera wrote:
For those getting annoyed for the popuo telling invalid QSO, you just
have to fill Rcp Sent and Exc Sent. Nothing more click ok and QSO is
logged. That simple.
As feature request, I would like the program to populate the GRID
field, when possible.
On 01/12/2018 21:13, Edfel Rivera wrote:
My QTH is Puerto Rico, PR is not allowed, I placed DX. However, first
box not allows to write there.
Hi Edfel,
the upper box is for entering your ARRL Field Day exchange, it is not
relevant to ARRL RTTY Roundup mode. DX in the lower box is correct fo
Hi Mike:
My QTH is Puerto Rico, PR is not allowed, I placed DX. However, first box
not allows to write there.
73'
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 4:09 PM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> DId you put your state in the Advanced settings for the RTTY R
DId you put your state in the Advanced settings for the RTTY Roundup?
de Mike W9MDB
On Saturday, December 1, 2018, 2:49:09 PM CST, Edfel Rivera
wrote:
Hi All:
For those getting annoyed for the popuo telling invalid QSO, you just have to
fill Rcp Sent and Exc Sent. Nothing more cli
Hi Edfel,
Special Op. / ARRL RTTY was checked right from the start. Don’t know what the
problem is.
73s de Andy, oe3dmb
Von: Edfel Rivera [mailto:edfelj...@gmail.com]
Gesendet: Samstag, 01. Dezember 2018 20:54
An: WSJT software development
Betreff: Re: [wsjt-devel] not decoding ru
Hi All:
For those getting annoyed for the popuo telling invalid QSO, you just have
to fill Rcp Sent and Exc Sent. Nothing more click ok and QSO is logged.
That simple.
As feature request, I would like the program to populate the GRID field,
when possible.
73'
Edfel
KP4AJ
__
Hi:
After enlarging WSJTX window stop responding and TAsk Manager was required
to close program
73'
Edfel
KP4AJ.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On 01/12/2018 19:44, Edfel Rivera wrote:
One thing I have noticed when PPT is active open windows get input and
not respond to OS as should. OS Windows 10. Not sure if others have
observed this behavior.
Hi Edfel,
that sounds like RFI disrupting your mouse of keyboard connections. A
test
JT Alert is telling me that there are between 5 and 10 new stations calling
CQ on each time slot to on 14.130 with the RU Test Contest. Now if these
guys would just stay on v2 after the test, it would be awesome.
--
George Cotton, WB5JJJ
___
wsjt-devel
Hi Andreas:
I worked yesterday night various stations, 7080, be sure to set in Advance
Special Op and ARRL RTTY. Right now on 20m 14130 many RC4 -5 Stations and
decodind!
73'
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 2:51 PM Andreas Ma wrote:
> Hi David and all
>
>
>
> Same problem here. I’m on 709
Hi:
Configuration --> Advance --> Special Operating [x] -- > ARRL RTTY [x] and
yes goto 14130 whwre testing on 20m is huge.
73'
Edfel
KP4AJ
On Sat, Dec 1, 2018 at 2:18 PM WB5JJJ wrote:
> These stations with 5xx numbers should NOT be operating on the standard
> FT8 frequencies. They are opera
Hi David and all
Same problem here. I’m on 7090 (40m as it is nearly 9 p.m. here) having plenty
of signals in the waterfall display, but very few decodes. Changing back to
V1.9.1 no decode at all (as expected). Changing to 7074 getting dozens of
decodes per time slot. Clocks are accurate.
Hi All:
First I am very positive with WSJTX v2 RC5. Have worked DX many US states,
Poland, Slovenia, and more. One thing I have noticed when PPT is active
open windows get input and not respond to OS as should. OS Windows 10.
Not sure if others have observed this behavior.
Very pleased with Con
Check your time sync. Decoding 20-30 per pass here in Arkansas on 14.130.
On Sat, Dec 1, 2018 at 1:31 PM David Pickard wrote:
> I have v2-rc5 installed. Worked several stations yesterday on FT8. I am
> currently on 14.130 and hear lots of FT8 signals and see them on the
> waterfall but am showi
Check your clock?
From: David Pickard [mailto:n...@cableone.net]
Sent: Saturday, December 1, 2018 1:07 PM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] not decoding ru
I have v2-rc5 installed. Worked several stations yesterday on FT8. I am
currently on 14.130 and hear lots of
I have v2-rc5 installed. Worked several stations yesterday on
FT8. I am currently on 14.130 and hear lots of FT8 signals and see
them on the waterfall but am showing very few decodes. I moved up
2khz and heard lots of signals but no decodes.
--
David
A multitude of ANTO's (stateside) on 14.130 for the Round Up. Looks like a
lot of guys have made the jump to RC5 at least for this test contest. WF
looks better than 14.074 since everybody is v2 here today.
--
George Cotton, WB5JJJ
___
wsjt-devel mail
These stations with 5xx numbers should NOT be operating on the standard FT8
frequencies. They are operating as RTTY Round Up, but that starts on
14.130 and up to 14.150 and similar on other bands.
On Sat, Dec 1, 2018 at 1:12 PM Dale Wheeler via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrot
Running on 80m now but picking out stations I haven’t worked - With only 20 Qs
in the log it’s fairly easy to see who I’ve worked before but is there any way
to get dupe checking somehow?
I’m using a Mac so linking to something like N1MM isn’t possible.
73 Keith G6NHU
__
Are you saying to clear the log, export it as a blank log. Then when the
contest is over export to the already created blank log. Or just saying make
sure to clear the log so if there were already entries those would have to be
edited out of the contest submission.
Sorry to be dense but this
I looked at it. Saw the UI screen shots. No thanks. Sticking with WSJT-X.
73
-Jim
NU0C
On Sat, 1 Dec 2018 10:58:27 -0500
Neil Zampella wrote:
> Nope ...
>
> Last month .. still using the same encoder/decoder at least the
> name of the executable was finally changed last year.
> .. and
Puzzled by this sequence:
180845 Tx 1263 ~ CQ RU G3WDG IO92
180900 -5 0.0 1444 ~ G3WDG WB3D 529 VA
180915 Tx 1263 ~ WB3D G3WDG 559 0002
180930 -4 0.2 464 ~ G3WDG W4RJF 529 NC
180945 Tx 1263 ~ WB3D G3WDG 559 0002
180954 Tx 1263 ~ WB3D G3WDG R 559 0002
cq at 18084
Hi Bill,
Thanks for pointing me in the right direction. During the test, I was able
to get the QSOs fed into N1MM+ although for some reason that I've yet to
work out although it recognized multipliers everything came through with
zero points. Presumably a config issue on my end, I'll figure it out
On 01/12/2018 17:39, Paul Kube wrote:
Bill, You really should change the tooltips though. "Set Tx frequency
to Rx Frequency" makes it sound like the direction is from Tx to Rx,
and then the arrows seem to point the "wrong" direction.
Paul,
take the sentence "Set Tx frequency to Rx Frequency",
On 12/1/2018 12:33, G3WDG char...@sucklingfamily.free-online.co.uk wrote:
Just wondering what the TX # spinner is used for (located to right of RX
freq combo box) on mainwindow GUI?
For non US/Canada stations, the contest exchange is signal report and
QSO serial number.
-- Joe, K1JT
> . You'll just have to learn the convention and put up with it.
Bill, You really should change the tooltips though. "Set Tx frequency to Rx
Frequency" makes it sound like the direction is from Tx to Rx, and then the
arrows seem to point the "wrong" direction.
"Copy Tx frequency to Rx frequency"
Just wondering what the TX # spinner is used for (located to right of RX
freq combo box) on mainwindow GUI?
Charlie
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
I didn’t even read the tooltip, I just assumed that the arrow on the right
copied the frequency from the top field to the bottom one.
73 Keith G6NHU
> On 1 Dec 2018, at 17:02, m...@oz5xn.dk wrote:
>
> Hi Guys,
>
> You are right guys. Just follow the arrows and ignore the tool tip. Then it
On 01/12/2018 10:05, m...@oz5xn.dk wrote:
Just a single confusing graphic detail that might be corrected: On the
two buttons for moving TX / RX to the same frequency, the arrows turn
illogically (remains from 1.9 and earlier). The arrows should turn
opposite so they point to what you do, i.e.
Hi Guys,
You are right guys. Just follow the arrows and ignore the tool tip. Then it
works! J
Thanks!
73, Allan
Fra: Frank Kirschner [mailto:frank.kirsch...@gmail.com]
Sendt: 1. december 2018 17:32
Til: al...@nelsson.net; WSJT software development
Emne: Re: [wsjt-devel] Graphic confusi
Hello devolpers,
I know that JT65 issues are not high on your list, but when you have
time please have a look into this:
When using JT65, numeric characers ( 0 - 9 ) are missing from message
texts in ALL.TXT.
For example, these messages...
..are written to ALL.TXT like this:
2018-12-01 16
Thanks for the report Drew - I confirm the issue that you described. I’m
looking at it now, and it’ll be fixed for the GA release.
Steve k9an
> On Dec 1, 2018, at 10:02 AM, Drew White wrote:
>
> This morning I attempted an FT8 RC5 connection with C4XMAS. My initial
> transmission was truncate
On 01/12/2018 16:02, Drew White wrote:
This morning I attempted an FT8 RC5 connection with C4XMAS. My
initial transmission was truncated after the 'E' in "EN50". I then
removed EN50 from TX1. His transmissions to me also appears to be
truncated.
Drew K9CW
Hi Drew,
thanks for the issue r
Urp .. re-read your post, RC5 but it wouldn't truncate anything. If
this were happening more people would have reported this. Even the Tx1
message should have been fine.
Again, a full screen cap of the entire window would help.
Neil
On 12/1/2018 11:49 AM, Neil Zampella wrote:
Which RC version
Which RC version? A full screen cap would have helped as it would
have shown what the last Tx was, etc.
Neil, KN3ILZ
On 12/1/2018 11:02 AM, Drew White wrote:
This morning I attempted an FT8 RC5 connection with C4XMAS. My
initial transmission was truncated after the 'E' in "EN50". I then
Having written database software for mostly non-technical users, I
completely agree. Users love progress, but they hate change. In order to
get enthusiastic adoption of new releases, I had to show it would be
easier, faster, or more powerful for the users.
Hams, on the other hand, are technically-
Allan,
I think I see the problem. You are misinterpreting the word "to" in the
tool tip. If the tool tip for the arrow from Rx to Tx said, "Copy Rx freq
to Tx," instead of "Set Tx freq to Rx freq," (and conversely for the other
button), would that help?
Or, as has been suggested, just ignore the
This morning I attempted an FT8 RC5 connection with C4XMAS. My initial
transmission was truncated after the 'E' in "EN50". I then removed EN50
from TX1. His transmissions to me also appears to be truncated.
Drew K9CW
--
**
* K9CW DXCC: 363/340
1 - 100 of 123 matches
Mail list logo
