From what I can see, there are two "BLUE" selections that MAY NOT be
checked.
Scroll that window, or drag the windows a bit larger, and you should the
see the 'New Call' and 'New Call in Band' checkboxes and colors.
Select those two, and you'll then have new callsigns in a shade of
blue.
All that's left is a screen capture of the colors window so we can see
what is setup there.
Neil, KN3ILZ
On 12/15/2018 5:02 PM, L Barley wrote:
Alrighty thenboth the wsjt_log.adi and the all.txt files are
present and accounted for. I opened the all.txt file in notepad and
it appears to b
Alrighty thenboth the wsjt_log.adi and the all.txt files are present
and accounted for. I opened the all.txt file in notepad and it appears to
be in order, so I'm apparently not well and truly stuffedI hope.
I've saved the preferences both with and without the *Show DXCC, grid, and
worked
Hello Lance
Once you do the things mentioned by Joe and Gary the "CQ in message" becomes B4
contacts. This was mentioned in another message but once figured out it does
work. I used a color that stands out to distinguish this selection. It really
would be fitting to not show these calls. When y
John,
you're not the only one seeing this error, as it has been reported
elsewhere, and on the FT8 and WSJT-X FB groups.
Exact same error, with the exact some file location. Which, BTW, is the
location on the computer of the person who built the executable, nothing
to worry about there.
T
On 15/12/2018 21:20, Johnny Allen wrote:
but I have hidden files showing and there is no user “bill” on my PC.
Hi Johnny,
the user bill is me and there are no hidden files on your machine. The
error message includes the file name and line number of the source code
on my machine where the app
I am not a developer, but encountered this error after installing v2.0. I
can close and reopen the program and it works for a while, but the error
returns.
The details given by the error box (see attached .jpg) are:
"Running: C:\WSJT\wsjtx\bin\jt9 -s WSJT-X -w 1 -m 3 -e C:\WSJT\wsjtx\bi
Hi Lance.
Since you weren’t explicit about those ‘appropriate boxes in the settings area’
but you’ve been working on it for days, I guess you either know what you are
doing there or have hit all possible combinations … but there’s another factor
you didn’t mention. The worked-before functio
Hello Bill,
Thank you for the clear explanation, as always.
One question remains, how long will an entry in the hash table exist for?
In particular is it cleared after a band change?
I sometimes do bandhopping to monitor different bands.
Thanks again and 73,
Ton pa0tbr
On Sat, 15 Dec 2018 at 18:
Hi Lance,
On 12/15/2018 15:18, L Barley wrote:
I'm using v2.0.0 on Windows 10 and the "worked before status" isn't
functioning. It looks like I have the appropriate boxes selected in the
settings area. I've been working on this for several days without any
improvements.
Does anyone els
I'm using v2.0.0 on Windows 10 and the "worked before status" isn't
functioning. It looks like I have the appropriate boxes selected in the
settings area. I've been working on this for several days without any
improvements.
Does anyone else have this issue? Is there a fix for this?
Thanks.
Well I hope that wouldn't be the case, since it's not in the budget to
upgrade this machine any time soon so that would mean dropping the
mode(s) I've got the most enjoyment from in the last few years.
I realized there was another update for 10.14.2 that hadn't been
applied, so I did that and rest
Russ --
You're calling some displays "bogus decodes", and evidently they are
bogus. But you appear to have all the knobs turned up to maximum
aggressiveness. Most if the displayed messages are flagged with "?",
which you may interpret as "caveat emptor", or some such.
Probably you saved "K
Hi Joe
Russ's report noted the reappearance of a callsign that had previously
been decoded ( probably recently) which was then seen as the content
average decode *even after the program was closed and restarted*, and
clear average pressed.
I was therefore wondering whether the decoder was using a
> On Dec 15, 2018, at 11:11 AM, Ton PA0TBR wrote:
>
> I am trying to work out why some callsigns are shown as <...> in WSJT-X
> Sometimes <...> is reflected in JTAlert as ... other times it is not shown
> in JTAlert.
>
> For example:
> 103615 -12 1.8 1590 ~ <...> LZ1PPZ
> 103645 -2 1.8 159
Bill, Joe, Charlie, whoever is interested; here is a new wrinkle to the
problem.
I was operating MSK144 on 2 meters. Got done and decided to switch to JT65
to see if the false decodes would start to happen. It didn't right away, so
went away for a while leaving it running. When I got back I had
Ton --
On 12/15/2018 12:11, Ton PA0TBR wrote:
I am trying to work out why some callsigns are shown as <...> in WSJT-X
Sometimes <...> is reflected in JTAlert as ... other times it is not
shown in JTAlert.
Why not consult the User Guide? Why do you think we bother to write
one, which takes
http://www.physics.princeton.edu/pulsar/K1JT/wsjtx-doc/wsjtx-main-2.0.0.html
Compound call signs
Keijo OG55W
From: Ton PA0TBR
Sent: Saturday, December 15, 2018 7:11 PM
To: WSJT software development
Subject: [wsjt-devel] Callsigns substituted by <...>
I am trying to work out why some callsigns
On 15/12/2018 17:11, Ton PA0TBR wrote:
I am trying to work out why some callsigns are shown as <...> in WSJT-X
Sometimes <...> is reflected in JTAlert as ... other times it is not
shown in JTAlert.
For example:
103615 -12 1.8 1590 ~ <...> LZ1PPZ
103645 -2 1.8 1590 ~ <...> LZ1PPZ R-18
103
Hi Charlie,
On 12/15/2018 12:38, G3WDG wrote:
If deep search is engaged, does it look through call3.txt randomly, or
start for example at the most recent entry?
Deep Search uses whatever is saved in CALL3.TXT. There's nothing
'random' about it, and order in the file does not matter. If you
I am trying to work out why some callsigns are shown as <...> in WSJT-X
Sometimes <...> is reflected in JTAlert as ... other times it is not shown
in JTAlert.
For example:
103615 -12 1.8 1590 ~ <...> LZ1PPZ
103645 -2 1.8 1590 ~ <...> LZ1PPZ R-18
103715 -5 1.9 1589 ~ <...> LZ1PPZ R-20
1037
Bill
If deep search is engaged, does it look through call3.txt randomly, or
start for example at the most recent entry?
Charlie
> Hi Russ,
>
> some comments in line. BTW I don't operate EME so these are based on
> looking at the source code alone.
>
> On 15/12/2018 00:33, Russ wrote:
>> I'm havi
Bill, here is the matching portion from the all.txt file:
2118 -26 2.5 1391 #* W4TAA AA4FF EM50 f
2119 -23 2.9 1453 #* CQ W4TAA EL87 f
181214_212000 Transmitting 144.12 MHz JT65: W4TAA K2TXB FN20
2119 -23 2.9 1453 #* CQ W4TAA EL87
Hi Steve,
I re-booted my MacBook Pro (2018; 2.3 GHz Core i5) from my usual 10.13.6 to
10.14.1 to look more closely at timings with 2.0.0_GA than I did earlier with
a previous test with rc4.
I use a Kenwood TS-870s with USB audio link via SignaLink and CAT control with
a USB-Serial adapter wit
Sorry to give such a subjective report, but that's all I've got at the
moment while I try to gather data. Wanted to get started with this
report before I forget details and in case someone else can say "oh
flip this switch and it gets better."
Upgraded my shack computer last night, first to WSJT-
Second time happened. Now tried work DF1000ZEIL. Reports were
ok, but suddenly:
145201 Tx 2332 ~ OH1MRR
145215 -10 0.1 2208 ~ OH1MRR -12
145230 Tx 2332 ~ OH1MRR R-10
145245 -6 0.1 2208 ~ DF1000ZEIL RR73 <--THIS!
So my auto seq starte
Look at the settings on the Color Tab. WSJT-X 2.0 reports more information then
1.9.1 does. The color tab settings effect this
On Dec 15, 2018 9:15 AM, Michael Baker wrote:
I have noticed that some are sending their CQ Zone along with their call info
when calling CQ. How are they doing that? Ar
I have noticed that some are sending their CQ Zone along with their call
info when calling CQ. How are they doing that? Are they using a different
program for FT8 other than WSJTX?
Just curious.
K7DD Mike
___
wsjt-devel mailing list
wsjt-devel@lists.so
He's probably running one of the 3rd party clones and if so, all bets are
off. He's been contacted numerous times by email, according to previous
commenters, to no avail. Never answers or changes his tactics. Just ignore
him and move on.
73's
On Sat, Dec 15, 2018 at 2:26 AM Gary Kohtala - K7EK
Hi Russ,
some comments in line. BTW I don't operate EME so these are based on
looking at the source code alone.
On 15/12/2018 00:33, Russ wrote:
I'm having a lot of problems using JT65 for EME. The right hand pane,
Average Decodes, seems to have a mind of it's own. For instance, earlier I
w
On 15/12/2018 08:22, Gary Kohtala - K7EK via wsjt-devel wrote:
Here we go again. Not so rare DX is running Fox/Hound in the standard
FT8 segments. Is anyone else seeing this?
I am on 7074. He's been at it for at least several days. Whatever
happened to safeguards against this? I thought
they we
I agree with Allan.
Actually, I didn’t make any sense with the meaning of "CQ in message" which
means “worked before” till now
Hiro/JA1LZK
From: m...@oz5xn.dk [mailto:m...@oz5xn.dk]
Sent: Saturday, December 15, 2018 5:59 PM
To: 'WSJT software development'
Subject: [wsjt-devel] Worked befo
Hi,
Perhaps it was an idea to change the text "CQ in message" to the perhaps more
correct "Worked before" as there appear to be some misunderstandings among some
users.
73, Allan – OZ5XN
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge
Hi Gary,
I totally agree with you. It was also my purpose, to keep my own communication
in the right window without seeing previous QSO partner's new calls. As you say
- it can be seen in the left window. This could be done by a check mark in the
settings "Set RX frequency to TX frequency" afte
Here we go again. Not so rare DX is running Fox/Hound in the standard FT8
segments. Is anyone else seeing this?I am on 7074. He's been at it for at least
several days. Whatever happened to safeguards against this? I thoughtthey were
to be built into WSJTX by the GA of v2.0.
Best regards,
Gary, K
35 matches
Mail list logo
