I just noticed that mine was not showing the band either. I switched "N Avg
4" to "Nvg 3", and now it is displaying time and band.
On Sun, 2 Dec 2018 at 17:20, Thomas Webb wrote:
> For whatever reason, the wide graph display on both Ver 1.9 & 2.0 has gone
> goofy.
>
> The lines between 15 second
s his QRZ Information updated noting that his station is now
> at the remote site in EM56.
>
>
>
> Ed.. AB4IQ
>
>
>
> *From:* Chuck Furman [mailto:chuck.fur...@gmail.com]
> *Sent:* Sunday, December 2, 2018 11:41 AM
> *To:* WSJT software development
> *Subjec
.
On Sun, Dec 2, 2018 at 12:01 OG55W wrote:
> FT never gives my grid in my CQ
> And I am operating in Finland from several grids, like KP20, KP13, KP30
> etc.
> in QRZ.com there is a place only for one grid.
>
> In LoTW the grid is OK.
>
> 73 Keijo OG55W
>
> *From:*
im operating remote is that I am unable to add from
> qrz.com
>
>
>
> On Sun, Dec 2, 2018, 12:44 PM Chuck Furman
>> Bill,
>>
>> I’m confused. Why does remote operating affect the grid? I operate
>> remotely all the time. I operate from my kitchen, my living
Bill,
I’m confused. Why does remote operating affect the grid? I operate remotely
all the time. I operate from my kitchen, my living room, patio, etc. I’ve
also operated from China and Dubai. But in all cases, the station is in my
house in Plano, Texas... in grid EM13oc. The grid square never chan
This looks very similar to what I'm seeing here in Dallas, Texas. I see
many people receiving my signal in NA and EU, but I'm not decoding much. I
think there are a lot of unattended stations sending reports to the PSK
Reporter.
On Thu, 29 Nov 2018 at 02:00, Tom Ramberg via wsjt-devel <
wsjt-devel
break the
> laws of physics.
>
> It’s 77 bits or bust, basically - mostly bust at present until word gets
> out about the sexy new version of FT8.
>
> In other words, we’re using FT8+ not FT8, pushing back the front ears.
>
> 73
> Gary ZL2iFB
>
>
>
> *From
Thank you. I knew I was missing something.
On Wed, Nov 28, 2018 at 7:38 PM Bill Somerville
wrote:
> On 29/11/2018 01:30, Chuck Furman wrote:
> > I’m confused. Why is CQ 77 helpful?
>
> Hi Chuck,
>
> the idea is a hint to v2.0.0 RC3 or RC4 users who probably will not have
I’m confused. Why is CQ 77 helpful? Only people who are already on 77 bit
mode will decode you. Am I missing something? I am just curious. It seem
more useful to TX on 75 bits with something like “PSE USE 77BIT”
On Wed, Nov 28, 2018 at 7:23 PM Al Pawlowski wrote:
> I have used “CQ 77 …..” a few
I loaded RC5 this afternoon. I went to 40m and almost immediately made five
contacts. I got great signal reports. Then. nothing. The waterfall has
been completely full of strong signals, but nothing was decoding. No 77 bit
signals. I called CQ on and off for three hours. No responses. So I
ch
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.
Y
Hi Joe,
Sorry about my last email regarding the five minute timer. I was typing it
at the same time you were sending your message. I’m very happy to hear what
you said about the timer.
On Fri, Nov 16, 2018 at 2:26 PM Joe Taylor wrote:
> Hi all,
>
> Please! No need for any more comments about a
I lost several contacts due to the 5 minute timer. When signals are weak,
and repeat transmissions are necessary, you can easily spend 15 minutes on
one contact. I don’t want to spend my time watching the clock and moving
the mouse over and over. At least the watchdog timer gives you a visual
warn
I just switched from 20M to 40M. I found a clear frequency and started to
call CQ. Two stations answered me. But my software just kept sending CQ. It
took me a couple of minutes before I realized that auto seq and call 1st
were unchecked. I know this is a known issue. I just want to go on record
as
Please follow instructions in the "Quick-Start Guide to WSJT-X 2.0",
https://physics.princeton.edu/pulsar/k1jt/Quick_Start_WSJT-X_2.0.pdf
It is easy to fix the LoTW problem.
On Thu, 15 Nov 2018 at 05:15, Ricky Dye wrote:
> New to the group and need some help. I am running Windows 10 Home using
RC4 installed with no complications. I made five contacts within the first
few minutes.
I did not look to see how auto seq and call first were initially set. But
they must have been checked, because my first five contacts were fine.
Observations:
After closing the program and reopening it, auto
CO2BG was calling CQ.
I called him.
Somehow another contact popped up on the same frequency. Maybe conditions
shifted?
Then, CO2BG called KB9A.
On the next time slot, he called me.
Again, another station slipped in on my end. That's fine.
But my TX was disabled automatically.
I double-clicked on th
I thought it was just me. Yes, if you get an RRR or RR73 a second time
AFTER you have sent 73, the auto seq reverts back to sending signal reports
again. This is extremely frustrating. You can't blame the other station.
Due to QSB or QRM, he/she may not have received your 73, so naturally they
will
Yes, I am seeing the exact same behavior with the colors. Many of the green
stations are not in my log. Seems like a bug to me.
KG6PH
Chuck
On Wed, 17 Oct 2018 at 15:43, Attila Kocis wrote:
> Hi
>
>
>
> This is the way I have the colors in the settings
>
>
>
> But I receive many lines in the le
Here is the correct version:
[image: image.png]
On Wed, 17 Oct 2018 at 12:53, Bill Somerville wrote:
> On 17/10/2018 18:38, Chuck Furman wrote:
>
> [image: image.png]
>
> Hi Chuck,
>
> the command you need to type is:
>
> WHERE libeay32.dll
>
> you omitted
The good news... a feature was added to change the foreground color. It
works on the setup page. I change black text on a red background to white
on read.
The bad news... in an actual QSO, the foreground color is still black.
___
wsjt-devel mailing list
[image: image.png]
On Wed, 17 Oct 2018 at 12:28, Bill Somerville wrote:
> Hi All,
>
> I need some help from the community to try and diagnose these issue. I
> suspect it is an OpenSSL problem with old version of the OpenSSL DLLs
> being used. It would be nice to package the OpenSSL libraries wit
I like the use of red for My Call in Message, but I find black a poor
choice against a red background. I would much prefer white as in this
example: My Call in Message.
It would be nice to have the ability to change the font color, even if it's
just a choice of black or white, and maybe a bold opt
This is what I'm using:
[image: image.png]
[image: image.png]
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
After rebooting, now I can install WSJT-X RC3, but I am getting the LoTW
message that other are seeing.
On Wed, 17 Oct 2018 at 10:39, Bill Somerville wrote:
> On 17/10/2018 16:29, Chuck Furman wrote:
> > I just uninstalled all previous versions of WSJT-X. When I try to
> > ins
I'm seeing the same LoTW message like others are seeing:
[image: image.png]
Chuck KG6PH
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
I just uninstalled all previous versions of WSJT-X. When I try to install
RC3, I get this message. I even selected "Run as Administrator". Any ideas
what I'm doing wrong? I never had trouble before.
Chuck KG6PH
Plano, Texas
[image: image.png]
___
wsjt-
a warning/confirmation message, though, would work better I think
> – something like “He’s calling CQ EU but you are not in Europe. Do you
> really want to respond? Click here to call him anyway …”
>
>
>
> The program would need to be told or calculate our areas, and “CQ DX”
>
so the call he intended
> was now above his mouse pointer.
>
> On Sun, Oct 7, 2018, 3:53 PM Gary McDuffie wrote:
>
>>
>>
>> > On Oct 6, 2018, at 19:59, Chuck Furman wrote:
>> >
>> > Several times I accidentally clicked on a station calling CQ DX or
I often forget that I have "Hold Tx Freq" checked. Then, I accidentally
call someone or call CQ on top of another station. I know... I should watch
the waterfall more carefully.
I suggest highlighting the "Hold Tx Freq" text with a bright color, so it
is obvious when the box is checked.
Example:
Please add a checkbox for* "Do not answer directed CQ's"* or maybe "*Disable
answering directed CQ's*" or "*Respond to general CQ's only*".
Several times I accidentally clicked on a station calling CQ DX or some
other directed CQ. This often happens just as the Band Activity window
updates. I cli
31 matches
Mail list logo
