Actually a couple of off-the-top ideas if the new/improved Fox mode doesn't
make it into V2.0 (sounds like it won't) just to prompt some more fully fleshed
ideas...
#1 Limit the power on CQ calls to the power for the # of slots selected. So if
the Fox wants 5 slots it always uses 5-slot power l
Tue, 20 Nov 2018 12:37:02 -0500
Joe Taylor kirjoitti:
> On 11/20/2018 11:51 AM, Black Michael via wsjt-devel wrote:
> > It was mentioned a while ago that changes would be made to the Fox
> > mode to avoid the power loss for multiple QSOs going on.
> Some months ago we said "The existing FT8 DXp
I noticed that I could 100% reproduce a crash (app windows vanish, no error
message) if
I click on OK in the Log Prompting dialog pop-up box, WHILE the final 73
was still transmitting.
If I wait until transmit completes, and THEN click OK to the log dialog
box, the app is OK and
does NOT crash.
When we demonstrate a real FT8 contesting mode, and plenty of operators
interested in it, then we can talk to N1MM about providing the needed
interface. This is the road we followed in the Flex Radio world, and it worked
out very nicely. N1MM now feeds the spot information it gathers to the ra
Settings > Radio > Split Operation > Check Fake It. This seems to do the trick.
Just a bandaid tho. Centering up the dial seems more feasible. 😊
-Scott
KD4YDD
From: M Lewton
Sent: Tuesday, November 20, 2018 4:50 PM
To: WSJT software development
Subject: Re: [wsjt
In checking the wsjtx_log.adi file, I found the state was saved wrongly.
WB3LGC FM29 FT8 +08
+15 20181120 221515
20181120 221615 20m 14.076130
WB5JJJ EM35kg 80
LJ81HM
--
George Cotton, WB5JJJ
PO Box 1025
Russellville, AR 72811
479.968.7737 Home
479.857.7737 Cell
DMR K5CS (Local Repeater
I just logged a contact in Delaware. If you notice the lower right Rcvd
box has unknown information. The 2nd part LJ81HM showed up as the state
when sent to HRD LB. This looks like a grid square, but if so, it's in the
middle of the ocean off Mogadishu, Somalia. Pirates location for sure.
Did n
I agree. A few of operators operating above 2000 have a good signal on the
waterfall, I copy them well but they can't seem to hear me ??
I am running 100 watts using a IC-7300 with BW set to 3600.
It seem that they are running a KW to my 100 watts.
You are right, with some receivers it would be b
As I look at my log from last night's Mock :
View > Contest Log
There are no entries displayed under the Received Column. Should there be?
Looking at the Cabrillo export Log:
QSO: 7078 DG 2018-11-19 2006 N0AN 569 IAK9AN 569
IL
... shows that a Rx exchange exists.
What
Hi!
It would be nice to have function to clean all call tables and reload ADIF log
file.
Currently it is done by restart of WSJTX.
It is handy when running two copies of WSJTX .
(yes, I already called CQ with 2.0-rc4, get answered by rc3 users in 75 bit,
and answered in 1.91 to make a QSO).
I
On 20/11/2018 21:14, Jeff Stai wrote:
So contest loggers already implement a feed of decodes.
Hi Jeff,
do you know if this is documented anywhere?
73
Bill
G4WJS.
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourcefor
hi Bill - I do understand that WSJT-X is a multi-decoder. On a busy band in
RTTY I might have say 4 callsigns to choose from in my receive display
after I call CQ, and the contest logger will highlight based on already
worked, new mult, etc. - and I click or use a hotkey to grab the one I want
to w
Hi Bill;
it's hard to hit a performance target without knowing what the numbers
need to be. Checking each call one at a time externally would surely
be the slowest.
But it also seems like the timing requirements on external dupe
checking could be relaxed entirely by doing something like this, whic
Il 20/11/18 17:41, Dale Wheeler via wsjt-devel ha scritto:
> Running on win10.
>
> Showing wrong colors. See attached picture.
>
> wrong colors.jpg
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.n
Il 20/11/18 17:41, Dale Wheeler via wsjt-devel ha scritto:
> Running on win10.
>
> Showing wrong colors. See attached picture.
>
> wrong colors.jpg
>
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.n
On 20/11/2018 19:25, Brian Moran wrote:
Hi Bill! You say time critical -- how many milliseconds are currently
available to look up the up-to-40-calls and render a 'worked_before'
status for each of them?
Hi Brian,
we have no deadline specified but I would expect the current
implementation to
Hi Bill! You say time critical -- how many milliseconds are currently
available to look up the up-to-40-calls and render a 'worked_before'
status for each of them?
On Tue, Nov 20, 2018 at 11:09 AM Bill Somerville wrote:
>
> On 20/11/2018 18:06, Brian Moran wrote:
> > In the ARRL RTTY Roundup, th
On 20/11/2018 19:01, Jeff Stai wrote:
If I decide to run WSJT-X in the Roundup, I'm not expecting my
preferred logger to have any support for it, so I believe I will be
treating WSJT-X as if it were a stand alone RTTY modem and I'll be
typing stuff into the contest logger - letting the logger k
Hi Bill,The requested file is attached. I think it is clear what happened.
This time I was calling CQ RU along the contest period with Auto Seq and Hold
Tx Freq checked.
02:11:45 the QSO with KG6MC was completed (he got R 549 0005)02:11:30 WB4HXE
and W5LRU called me.02:12:15 I sent R 559 0006 to
On 11/20/2018 10:54 AM, Dave Hachadorian wrote:
It worked OK sometimes, but several callers kept coming back for more
info, apparently looking for that final (TX5) “73” from me.
That's partly because some FT8 operators don't have contesting
experience. The sequence you outline is perfectly rig
Good luck on your surgery Steve!
-Scott
KD4YDD
On Nov 20, 2018, at 1:19 PM, Stephen Ireland
mailto:vk3...@hotmail.com>> wrote:
Mark,
I had considered this and its a fair suggestion – but the start of our band is
say 7.074. Are we not best working under real world congestion – especially on
4
On 20/11/2018 18:06, Brian Moran wrote:
In the ARRL RTTY Roundup, the rules say work stations once per band,
regardless of mode. This means those stations using both RTTY and FT8
modes in the same contest will have to check callsigns in BOTH MODES
to know what to work efficiently.
Will there be
I, too, was running JTAlertX last night for the ‘test, but for a different
reason than to check dupes. JTAlertX and Log4OM are my regularly day-to-day
system. N1MM+ is only launched during contests. Since JTAlertX is basing dupe
declaration on my big log and not the contest, I’m very happy to
hi Brian - If I decide to run WSJT-X in the Roundup, I'm not expecting my
preferred logger to have any support for it, so I believe I will be
treating WSJT-X as if it were a stand alone RTTY modem and I'll be typing
stuff into the contest logger - letting the logger keep track of dupes and
mults an
Amazing activity. Please see the attached.
I have had ft8v2r4 up since first day announced.
It was amazing to see the activity build for this mock contest.
Thanks again..
BCNU DE N2LO~>2018-11-20,01:44:15,2018-11-20,01:45:15,K5WE,EM25,7.078543,FT8,569,569,,FT8
Sent: 569 Rcvd: 569,
2018-11-20,01:
I tried using the following sequence in the contest last night.
I SEND (TX6) CQ RU K6LL DM22
SHE SENDS (TX2) K6LL K7ABC 569 AZ
I SEND (TX3) K7ABC K6LL R 579 AZ
SHE SENDS (TX4) K6LL K7ABC RR73
I SEND (TX6) CQ RU K6LL DM22
It worked OK sometimes, but several callers kept coming back for mor
Mark,
I had considered this and its a fair suggestion – but the start of our band is
say 7.074. Are we not best working under real world congestion – especially on
40m - and not closed-conditions? That is why I raised the Fleishman and Pons
“Cold Fusion” fiasco – an example that runs shivers do
I've also had this issue plus another: I believe in earlier versions if I
DID NOT check the respond to first call and I was answering CQ callers,
after I sent 73 the program would leave the 73 tab in place and NOT MOVE to
CQ tab.
If I'm working others and NOT CALLING CQ, then I do not want the
In the ARRL RTTY Roundup, the rules say work stations once per band,
regardless of mode. This means those stations using both RTTY and FT8
modes in the same contest will have to check callsigns in BOTH MODES
to know what to work efficiently.
Will there be a means supported to do an 'outcall' to a
Hi Bill,
I was fully aware of this before I put the post out there 😊
The logic, I feel, needs a back-check before the condition is evaluated – that
being the termination of transmission only occurs once the conditions for a 73
are received.
* It is possible to have WSJT-X keep sending
On 20/11/2018 14:24, Brian Waterworth wrote:
Would adding another contest to the list of supported wsjtx contests
remove the restriction you cited? And granted, I get that this would
take more time to develop than broadening the allowable characters for
the current ARRL Field Day contest.
Hi
On 20/11/2018 14:20, Black Michael via wsjt-devel wrote:
Is the specific contest mode used during decode? Couldn't the meaning
of those 3 bits change depending on which contest is in place?
de Mike W9MDB
Hi Mike,
that is a possibility for this very specific case where Winter FD
corresponds
Hi Mike,
On 11/20/2018 11:51 AM, Black Michael via wsjt-devel wrote:
It was mentioned a while ago that changes would be made to the Fox mode
to avoid the power loss for multiple QSOs going on.
Has this been done? rc4 still points to the old DXpedition guide.
The only change made to FT8 DXpe
Just did a test with RC4 in RTTY RU mode...
--
'Disable Tx after sending 73 is unchecked.
Clicked 'Next' radio button for Tx5.
Clicked 'Enable Tx'
WSJT-X sent one Tx5 sequence, and left radio button and 'Enable Tx'
unchanged
At start of next Tx5 sequence, WSJT-X selected 'Next' radio button for
David,
Actually I found JTAlters very useful for exactly that reason - dup
checking. But see Joe's note - already handled in RC5 or the GA release.
John
On Tue, Nov 20, 2018 at 11:19 AM David Kjellquist
wrote:
> Has anyone come up with ideas for avoiding dups when using FT8 in a
> large conte
I forgot about that box and was reminded about it some weeks ago. In any case,
it does not seem to work for me in rc3, and I think previously in rc2 - the box
is unchecked yet tx is still disabled when I send a 73.
Al Pawlowski, K6AVP
Los Osos, CA USA
> On Nov 20, 2018, at 04:09, wsjt-devel
It was mentioned a while ago that changes would be made to the Fox mode to
avoid the power loss for multiple QSOs going on.
Has this been done? rc4 still points to the old DXpedition guide.
de Mike W9MDB
___
wsjt-devel mailing list
wsjt-devel@lists.sou
What I have started doing is always going back to the tab after my final
response (RR73 or 73), re-enabling and re-selecting the final message and then
sitting with my mouse of the disable tx button to kill the tx if the other
party responds like they got my last message.
At least in non-contes
Joe, Steve et al -- thanks for your good work here. Last night I believe I
was able to complete QSOs more reliably than in the past, and other people
seemed to be able to decode me at the same power level that had not been
very effective recently with 1.9.1.
On Tue, Nov 20, 2018 at 11:36 AM Joe Ta
After RU time, I responded to a few RU calls while in normal FT8 mode. Got
message "Do you want to switch to Contest mode”. Dismissing the message box
with an “OK”, a close (upper right X) or “close” did not seem to make any
difference in operation. I expected OK might switch modes. Don’t know
Hi Dave and all,
On 11/20/2018 11:11 AM, David Kjellquist WB5NHL wrote:
Has anyone come up with ideas for avoiding dups when using FT8 in a
large contest? JTAlert checks B4 but its display matrix is limited and
not really designed for contest use. N1MM log integration works well but
I don't se
The "73 Loop" is not specific to the contest mode or FT8 v.2. I have this
problem with 1.9 also. I usually log the contact with my RR73, then if the
other station resends R _xx, I click on Tx5 NEXT then enable the transmit.
RR73, RR -xx ... 73
Jim
KC1BB
On Tue, Nov 20, 2018 at 5:58 AM Bill So
On Nov 20, 2018, at 7:18 AM, I wrote:
> I agree with that. My equipment has a sweet spot about 1500Hz. But, it also
> looks like the software adapts transmit frequency accordingly (I’ve seen it
> go 500 Hz either way), even so, I did add 7.500 and 7.700 to my frequency
> list as well.
Du’oh! T
Has anyone come up with ideas for avoiding dups when using FT8 in a
large contest? JTAlert checks B4 but its display matrix is limited and
not really designed for contest use. N1MM log integration works well but
I don't see that it checks for dups prior actual log entry (not much
help). But, I'
Morning:
Again, I had fun last night..as another stated, it was a "hoot"
Thanks.
Stephen Duncheskie, W4PPC
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
On Nov 20, 2018, at 4:37 AM, Stephen Ireland wrote:
>
>
> I realise that Joe K1JT has recommended that for 2.0 RC4 that we should be
> transmitting above 2000hz in offset.
>
> Many of us have radios (i.e. non-SDR’s such as Yaesu’s and Pre-SDR-based
> Icom’s) that have known “performance curv
Hi, group.
Here are my comments for last evening:
All in all ... things went pretty good for me. I did have one issue, though.
I read somewhere that the color ordering could be changed by drag and drop. I
did try that and managed to hang WSJTX in the process. Nothing worked. My only
resolu
--
73 de Marco, PY1ZRJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Hi Bill,
Thanks for the quick response.
If you are referring to potentially extending the current ARRL Field Day to
support the three additional letters, I had first thought about that too.
I even saw in the code where you do the validation. However, I bet the
wsjtx developers would have a reaso
Is the specific contest mode used during decode? Couldn't the meaning of those
3 bits change depending on which contest is in place?
de Mike W9MDB
On Tuesday, November 20, 2018, 8:07:09 AM CST, Bill Somerville
wrote:
On 20/11/2018 13:20, Brian Waterworth wrote:
I particip
On 20/11/2018 13:20, Brian Waterworth wrote:
I participated in the mock RTTY Roundup contest yesterday. What fun.
I am now even more energized to use wsjtx for the upcoming Winter
Field Day. But alas, I won't be able to as the class letters are
different from the ARRL Field Day contest.
As
If you are working above 2000, and might have performance issues on
receiving signals there, another option is to use a higher dial frequency
-- eg 7.075 or 7.076. This doesn't affect the actual frequencies used, just
may make it easier to manage.
On Tue, Nov 20, 2018 at 7:52 AM John Nelson wro
I participated in the mock RTTY Roundup contest yesterday. What fun. I am
now even more energized to use wsjtx for the upcoming Winter Field Day.
But alas, I won't be able to as the class letters are different from the
ARRL Field Day contest.
As was posted on the main wsjtx forum, the wsjtx ARRL
Hi Julian,
On 11/19/2018 9:46 PM, Julian VK4CMV wrote:
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
On 20/11/2018 09:02, Stephen Ireland wrote:
Can the logic possibly be altered so that wsjt-x does not to head to
CQ [Tx 6] unless a 73 is received from the other station in the QSO?
Hi Steven,
this behaviour is determined by the options "Settings->General->Disable
Tx after sending 73" and "Se
Steve,
> one must “adjust” the AF “Power” drive control as one shifts Tx frequency.
Are you not using CAT control with “Split” selected? If so, VFOB is set such
that the audio tone generated is always between 1500 and 2000 Hz which should
always be within the SSB passband. The TX offset is
On 20/11/2018 05:23, Carey Fisher wrote:
Attached is my all.txt with the XE1MEX entries.
Here is the line where Alex, XE1MEX gave me an "R":
021415 4 0.1 1125 ~ WB4HXE XE1MEX R 559 0006
Don't know why I'm not in his log.
Hi Carey,
it looks like you both started another QSO before that me
On 20/11/2018 05:05, Alex Diaz - XE1MEX via wsjt-devel wrote:
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
On Tue, Nov 20, 2018 at 7:41 AM Stephen Ireland wrote:
> Folks,
>
>
>
> I realise that Joe K1JT has recommended that for 2.0 RC4 that we should be
> transmitting above 2000hz in offset.
>
> Many of us have radios (i.e. non-SDR’s such as Yaesu’s and Pre-SDR-based
> Icom’s) that have known “perform
Folks,
I realise that Joe K1JT has recommended that for 2.0 RC4 that we should be
transmitting above 2000hz in offset.
Many of us have radios (i.e. non-SDR’s such as Yaesu’s and Pre-SDR-based
Icom’s) that have known “performance curves” – even at digital settings -
meaning that AF/sound fed to
Bill,
Thanks for the reply. I am running current versions of N1MMLogger+, WSJT-X
and JT Alerts under Win7. First, and I am sure this is where I need some
help, I have never been able to log directly from WSJT-X into N1MM. I use
JTAlerts as a "bridge' if you will between WSJT-X and N1MMLogger+.
My experience using wsjt-x 2.0 rc4 last night:
At the end of my first QSO, a window popped up asking whether to log it. I
clicked on yes and the wsjt-x program crashed.
I did not have my Amateur Contact logging program nor JT-Bridge running.
73, John, K1JSM
-
email: k1
On 11/20/18 10:02 AM, Stephen Ireland wrote:
Hi Stephen & all,
The only resolution is to double-click BACK on the station that issued
the RRR, in which case you often respond with a R-XX response instead of
a 73 … then part of the way through the you nee to resolve the matter
with a [TX 5] ov
Other than the contest log displaying in local time (with AM/PM!), everything
seemed to work fine in the mock contest. No crashes, no unexpected operation.
MacOS Mojave, Flex6600.
George J Molnar
KF2T - Virginia, USA
___
wsjt-devel mailing list
wsj
I’ve had the same problem. Rc4 has worked flawlessly until ru contest. Upon
rr73 had to fill in sent report and when I hit log button I got subprocess
error and program closed without sending qso to log. Using MacBook Pro OS X
high Sierra, JT bridge 2.5.2 and rumlog 4.0.5. Hope that helps. 73 Ga
Hi Folks,
In some far off places where some of us reside often many of us are forced to
operate at Rx levels-of-confidence that some snooty, arrogant amateurs consider
to be “low levels of confidence” (this is another issue that is holding back
FT8v2 ... but this is another story for other post
66 matches
Mail list logo
