I use Split operation = Rig with my Icom radios, which puts the radio in
SPLIT mode, in which VFO A is the receive VFO, and VFO B is the transmit
VFO.
Now, when changing bands, WSJT-X only changes the frequency of VFO A,
leaving VFO B on the preious band, until a WSJT-X initiated transmission
It seems my issue may be related to an aspect of the problems reported
here: https://sourceforge.net/p/wsjt/mailman/message/36478478/.
In that thread, Uwe describes trying to distinguish between "New Call" and
"New Call on Band" with foreground color only, and observes that it doesn't
work.
In addition to this practice contest just prior to the actual FT8 Roundup
next weekend, there will be an identical practice on Wednesday evening NA
time (0200-0300 UTC Thursday, 29 November).
Don and I feel another practice will be useful since we all need to ensure
we have installed and
Hi George,
In my instructions for reproducing the problem, I unchecked everything,
except for CQ in message, and New Call on Band. It doesn't make
any difference what foreground color LoTW User Highlight is using. And it
doesn't make any difference what foreground color CQ in message is using,
it
Gary,
I'm fairly sure it has always been this way, even before v1.8 and FT8.
I see to remember that it was the reason the last CQ caller's 73 was
added to the 'conversation', to trigger the Log QSO window. Adding
the RR73 as an option in v1.9 was to acknowledge what a log of CQ
callers
Hello Dev team,
while reading the last batch of posts here, I noticed a reference by
another that their system appear to jump into JT9 in certain circumstances
so while pondering what is going on with my RC5 install, I noticed the Red
TX marker on the waterfall is the size I would expect for JT9
Prob uncheck LoTW User highlight or change it to see if that's the
problem.
On Tue, Nov 27, 2018 at 8:00 PM Paul Kube wrote:
> This issue involves foreground color, not background color:
>
> In Settings > Colors:
>
>
>1. Click Reset Highlighting, and confirm
>2. Uncheck all boxes in the
This issue involves foreground color, not background color:
In Settings > Colors:
1. Click Reset Highlighting, and confirm
2. Uncheck all boxes in the Decode Highlighting list
3. Right click CQ in message, Foreground Color, pick something other
than black, e.g. red; click OK
4.
"Still jumps out of 73 (Tx5) to CQ (Tx6). Only a problem with the very weak
signals that don't decode it the first time. I am getting better at guessing
who will need it repeated and moving back to TX5 and enabling TX.
Even though "Disable TX after 73" is not checked?"
Maurice - I concur that
Took RC5 for a run late this afternoon on 40M. 6 quick Q's, including 1 DX.
Other than the need to Reset Highlighting at the start (previously
reported), there were no issues. Very smooth and stable. Very grateful to
Joe, Steve, Bill for this latest.
Look forward to the FT8 Roundup this
ris WA4MIT
20m 5X TU best 73 GL 14.076878
JK13bm FT8 EM63eh
WA4MIT -13 -24
WA4MIT 154100 154000
35.000 20181127
Hi Morris,
that's fine.
The needed call or needed call on band is equivalent to a worked before
marker. If you turn those on then any CQ calls with a green background
(o
Hi.
The 'prompt me to log QSO' setting only seems to do its thing when I send a
73 message - specifically, it seems, I have to send a free-text message
containing the string "73". So, if I send a custom message to conclude a
QSO, one that doesn't include 73, I'm not prompted to log the QSO.
I
3eh WA4MIT
-13 -24 WA4MIT 154100
154000 35.000 20181127
On Tuesday, November 27, 2018, 5:09:09 PM CST, Bill Somerville
wrote:
Hi Morris,
the order of fields in an ADIF record doesn't matter. The outstanding issue
with WSJT-X v2.0.0 RC5 is that it doesn't interpret ADIF record cont
Hello Dev team,
I was asked today about the tone markers in the Wide Graph when using
JT65 as it would seem in V2.x these have been dropped. Could not see any
mention of this in the release notes but guess it was a development
decision, just want to make sure it was not an unexpected outcome?
Hello Joe
I tried rc5 on 2 ea. I5 computers running Windows 10 pro.. Latest versions.
Running rc5 yesterday afternoon and today. Works very good, FT8 only
tested.
A lot more operators today, must be catching on.
I was getting tired working the same 20 or so hams the last week.
Still jumps
Bill if one were to import from a logging program would the order of the
fields matter if we used something like ADIF Master to par the ADI fields down
to the same as that WSJT-X saves just in a different order.
Thanks 73 Morris WA4MIT
On Tuesday, November 27, 2018, 3:50:28 PM CST, Bill
Thanks Neil. Done
Ken VK4GC
On Wed, 28 Nov 2018 at 00:59, Neil Zampella wrote:
> I'd uninstall RC3 as it is not supposed to be used after Nov 30th.
>
> I'd put 1.9.1 back on for the time being until 2.0 goes general release
> for DXPeditions if nothing else.
>
> Neil, KN3ILZ
> On 11/27/2018
Thanks, need 77bit both ends or the old protocol both ends. So at the
moment down under VK/ZL- in the times i operate - few - getting more -
77bit signals. So fa,r 6m FT8 and 2m MSK144 operators still using non 77bit
software.
Build it and they will come - eventually!!
thanks Joe
Ken
On Tue, 27
On 27/11/2018 17:00, DG2YCB, Uwe wrote:
Many thanks for great work on the color scheme! Basic functions work
well now with v2.0.0-rc5 here at my PC. (Windows 10 64 bit)
However, there seems to be some minor bugs left. May the following
observations help you to identify them as well:
(1)
On 27/11/2018 21:30, Al wrote:
Note below the change in color for GW4HDR after I called him the
first time..
Note also that even though I had just worked N8TCP, now colored for
new call...
Hi Al,
there is one outstanding issue in the highlighting that I am aware of,
it is related to
Hi Eugene,
On 11/27/2018 2:26 PM, Eugene UA1NAN wrote:
Hi friends!
I can send a translation (not machine) into Russian of the article
"Quick-Start Guide to WSJT-X 2.0" from Joe Taylor, K1JT.
73, Eugene, UA1NAN.
Thanks for this offer! I will be happy to post your translation on the
WSJT
Hi Steve,
Thanks for the report. You do know that ""W6XX W7WM RR73 TNX" is not a
legal FT8 message, right?
Nevertheless, the program should not crash when it's given a bad
message. This defect will be fixed in the 2.0 GA release.
-- Joe, K1JT
On 11/27/2018 2:19 PM, Steve Boone
Hi friends!
I can send a translation (not machine) into Russian of the article
"Quick-Start Guide to WSJT-X 2.0" from Joe Taylor, K1JT.
73, Eugene, UA1NAN.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
Sorry, I didn't report this during RC4 but I accidentally discovered this
unusual behavior with WSJT-X just before RC5 was released. This also
happens in RC5.
While in QSO at transmitting step TX1, TX2 or TX3
I manually change TX4 to "W6xx W7WM RR73 TNX" [1 or 2 extra characters
does not fail)
On 11/27/2018 12:07 PM, Jari A wrote:
... I work several qsos with RC5 on FT8, then got silent with FT8, so I
change to JT65 as I saw traffic on it.
I also note, that after I change from JT65 to JT9, RC5 keeps tx on FT8,
even JT9 is indicated below date/ time window.
Aaah! Now I understand
Ah. Thanks, Joe and Wolfgang.
73 Paul K6PO
On Tue, Nov 27, 2018 at 10:11 AM Wolfgang wrote:
> Hello Paul,
>
> oh yes, if you left click into that pop-up window, RX & TX is set on that
> position
>
> 73 de Wolfgang
> OE1MWW
>
> Tuesday, November 27, 2018, 6:52:52 PM, you wrote:
>
>
> wsjt-x
On 27/11/2018 15:57, Wolfgang wrote:
Interresting finding:
151030 -11 0.3 2302 ~ CQ W7AH DM42 CQ Zone 3
but
154215 -18 0.2 2445 ~ CQ K0VM EN42 U.S.A.
EN42 in in CQ Zone 4, but rc5 reports it as 'U.S.A.'
73 de Wolfgang
OE1MWW
Hi Wolfgang,
the way the zone is calculated is via the
Hi Charlie, Jari, and all,
Thanks for your reports -- they are much appreciated. I'm sure you
understand that our recent work has mostly been related to HF interests
-- in particular, the new 77-bit protocols for FT8 and MSK144, and new
special messages for contesting.
We are certainly not
On 11/27/2018 12:52 PM, Paul Kube K6PO wrote:
wsjt-x 2.0.0-rc5
Windows 10 Pro x64 Version10.0.17134 Build 17134
Position the mouse cursor in the waterfall window.
Right click.
A small dialog pops up announcing "Set Rx and Tx Offset".
The Rx and Tx offsets themselves are not affected.
However,
wsjt-x 2.0.0-rc5
Windows 10 Pro x64 Version10.0.17134 Build 17134
Position the mouse cursor in the waterfall window.
Right click.
A small dialog pops up announcing "Set Rx and Tx Offset".
The Rx and Tx offsets themselves are not affected.
However, the WSJT-x Special Mouse Commands documentation
Thanks, Jari
Sounds like this is a different issue to what I was reporting.
73
Charlie
> Hi Charlie, others
>
> No, I work several qsos with RC5 on FT8, then got silent with FT8, so I
> change to JT65 as I saw traffic on it.
>
> I also note, that after I change from JT65 to JT9, RC5 keeps tx
Hi Charlie, others
No, I work several qsos with RC5 on FT8, then got silent with FT8, so I
change to JT65 as I saw traffic on it.
I also note, that after I change from JT65 to JT9, RC5 keeps tx on FT8,
even JT9 is indicated below date/ time window.
Rgds,
:Jari / oh2fqv
On Tue, Nov 27, 2018 at
Hi Jari
Did you start rc5 after getting a mode jump to JT9 with 1.9.1?
That is the only way I have found so far to see the effects of a mode jump
with rc5.
I posted some findings on this a few messages ago.
73
Charlie G3WDG
> Windows 7 64 bit
>
> JT65 errors:
>
> Double click to rx call sign
Interresting finding:
151030 -11 0.3 2302 ~ CQ W7AH DM42 CQ Zone 3
but
154215 -18 0.2 2445 ~ CQ K0VM EN42 U.S.A.
EN42 in in CQ Zone 4, but rc5 reports it as 'U.S.A.'
73 de Wolfgang
OE1MWW
P.S: Did Texas leave the United States of America with an 'Texit'? ;-)
--
Windows 7 64 bit
JT65 errors:
Double click to rx call sign not working to reply
Waterfall pointers looks like JT9
Transmit audio FT8 ( sending my own call with locator )
Decodes JT65 fine.
error repeatable, restart did not change the error.
Rgds,
:Jari / oh2fqv
Is there a chance you will change that to a double click Joe? I think
ISCAT could be a LOT of fun. I was amazed at the sensitivity!!
Rory, K5CKS
On Tue, Nov 27, 2018 at 9:17 AM Joe Taylor wrote:
> On 11/27/2018 9:54 AM, Rory Bowers wrote:
> > I installed rc5 this morning and ran ISCAT B on
Allan,
It is absolutely critical that all spread the vibes… but preaching here where
the converted play is just the start.
Perhaps beaconing of a V1 message may be required from 10th December until say
the 20th Jan? i.e. A dead-simple, possibly language-alternating clear message
such as
On 11/27/2018 9:54 AM, Rory Bowers wrote:
I installed rc5 this morning and ran ISCAT B on 6M. I got two calls
from my CQ. When I tried to double click on one of them the program
said "Double Click Not Available for ISCAT Mode". How do you answer a
call in ISCAT Mode??
Thanks,
Rory, K5CKS
I forgot to mention ISCAT B decoded almost perfectly at -20. I Only saw
one character error.
Rory, K5CKS
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
I'd uninstall RC3 as it is not supposed to be used after Nov 30th.
I'd put 1.9.1 back on for the time being until 2.0 goes general release
for DXPeditions if nothing else.
Neil, KN3ILZ
On 11/27/2018 12:08 AM, Ken Myers wrote:
Sure I had read it. Not the problem. Needed another station that
I installed rc5 this morning and ran ISCAT B on 6M. I got two calls from
my CQ. When I tried to double click on one of them the program said
"Double Click Not Available for ISCAT Mode". How do you answer a call in
ISCAT Mode??
Thanks,
Rory, K5CKS
___
Hi Joe
More on this.
On closing and restarting rc5 after 1.9.1 has mode jumped, as noted below
rc5 waterfall has the appearance of mode having jumped.
If I then close and start 1.9.1, the waterfall is normal.
On then closing 1.9.1 and restarting rc5 the waterfall is normal.
Charlie
> Hi Joe
Hi Joe
I've looked now at the mode jump issue with JT65.
Running rc5 with the set of 100 simulation files using the same settings
that reliably triggered the mode jump with 1.9.1 there is no sign of the
mode jump.
However when I used 1.9.1, to check I could still reproduce the behaviour
On 27/11/2018 08:07, jarmo wrote:
a small update for the project web page. Fedora Linux has moved on to
version 29 and the RPM packages are built for that version.
73
Bill
G4WJS.
Seems to work on Fedora 28 also
Jarmo
Hi Jarmo,
thanks for the report, always worth a try but no guarantees
Hi Joe
I have had a first look at rc5 from JT65 EME perspective.
I have not yet looked at the mode jumping fix.
Summary of results here:
https://drive.google.com/drive/folders/11Ph7EMvBTMWv5Ta5tJTufe50FzKu80TM?usp=sharing
Also see that auto-seq checkbox is not visible for QRA64, JT65 and
Mon, 26 Nov 2018 22:28:31 +
Bill Somerville kirjoitti:
> Hi Joe,
>
> a small update for the project web page. Fedora Linux has moved on to
> version 29 and the RPM packages are built for that version.
>
> 73
> Bill
> G4WJS.
Seems to work on Fedora 28 also
Jarmo
46 matches
Mail list logo
