Hi Laurie,
Thanks for this heads-up. SuperFox features are still in a fairly early
stage of development. We need to get the basic operation right, first,
and to gain some experience from in-the-field operation. We'll hope to
satisfy the need you've identified in the next release.
RC5 does not produce udp decode messages (#2) for SuperFox decodes.
Is this a defect or by design?
Without the decodes there is no way for JTAlert to notify a station they
were called by the fox nor to highlight their callsign (the called
station) in the Activity display.
de Laurie VK3AMA
(J
Don --
Charlie, DL3WDG, has already responded to your questions. A few
additional points:
1. If you saved a file with multiple signals that you think should have
decoded, but did not, please send us that file and a copy of your file
WSJT-X.ini.
2. Population of the table of frequencies is
Hi Don
I just tested -rc5 with a simulated two signal Q65-60D wave file (with EME
delay) and multiple decoding works fine here.
The decoding threshold is higher than that needed to decode when the
signal is within the Ftol band, so maybe the signals you could not decode
were just too weak.
Te
I seem to have lost the ability to do multiple decodes. The single decode is
turned off. No matter how many signals are on the waterfalls, I only get
decode on the one where the cursor is sitting. It used to do multiple decodes.
Second item. In echo mode, the frequency 902 MHz is missing fro
Terve Saku,
Hei!
Do you set *absolute minimums* for H and W and then close/open wsjtx?
Yes I did. I narrowed both H & W to the minimum they would go but they
still restored OK after restart
73's de Kari, oh2gqc / oh6bz
___
wsjt-devel mailing
Hei!
Do you set *absolute minimums* for H and W and then close/open wsjtx?
As Bill says if window is a bit bigger for both directions, with my
display resolution ~2cm in H and ~1,5cm in W, retains it. That breaks
the whole display window positioning setup in every start with this
rather small
Hi Saku, long time, no see...
On 12.8.2021 10.07, Saku via wsjt-devel wrote:
HI!
If you set wsjtx main window to minimum horizontal and vertical size
it is not saved/loaded when wsjtx starts again resulting bigger main
window that was set.
Saving window W and H and X,Y position at close and r
On 12/08/2021 08:07, Saku via wsjt-devel wrote:
HI!
If you set wsjtx main window to minimum horizontal and vertical size
it is not saved/loaded when wsjtx starts again resulting bigger main
window that was set.
Saving window W and H and X,Y position at close and reload them at
start should gi
HI!
If you set wsjtx main window to minimum horizontal and vertical size it
is not saved/loaded when wsjtx starts again resulting bigger main window
that was set.
Saving window W and H and X,Y position at close and reload them at start
should give same sized window.
OS Fedora Linux 34/ LXDE
Yes, Thanks to Joe and Team. Working fine here also.
Bobby/N4AU
--
n...@outlook.com
n...@arrl.net
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
For what it’s worth, I’m not seeing any difference with my 6300 and DAX/SSDR
3.0.19 between 2.0.1 and 2.1.0 RC5. ‘
Your 6600 must be defective - send it to me for, uh, proper disposal. ;).
73,
Jim S.
> On May 2, 2019, at 8:16 AM, Bill Somerville wrote:
>
>> On 02/05/2019 12:55, Al wrote:
I've got an ANAN 100 and I don't see any difference in power level between the
32-bit and 64-bit versions.
You can use Audacity to record what's coming out of the WSJT-X audio to see if
it's different between the two.
de Mike W9MDB
On Thursday, May 2, 2019, 7:21:43 AM CDT, Bill Somervil
On 02/05/2019 12:55, Al wrote:
(Flex 6600, SSDR&DAX 3.0.19, Wsjt 2.1.0-rc5, Win10 )
I have noted the the TX output level from WSJT-x v2.1.0-rc5 64bit (
all modes ) is 8db lower than in v2.0.1. The 32 bit version of
2.1.0-rc5 produces the same TX output level as v2.0.1.
It's not an operationa
(Flex 6600, SSDR&DAX 3.0.19, Wsjt 2.1.0-rc5, Win10 )
I have noted the the TX output level from WSJT-x v2.1.0-rc5 64bit ( all
modes ) is 8db lower than in v2.0.1. The 32 bit version of 2.1.0-rc5
produces the same TX output level as v2.0.1.
It's not an operational problem form me as I can compe
Bill:
I am testing RC5 in 6m 50.313 and noticed that Windows disrupting is NOT
happening on the 6m band. I activated RTTY Special Operation to have same
configuration when I detected the issue, Windows operation remains normal
(6m band). Changed to 20m 14.130 to test if problem is still present a
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
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
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
Bill,
No, I have I never imported an ADIF into WSJT... This particular log
was started new with RC4 and continued with RC5.
AL, K0VM
On 11/27/2018 3:47 PM, Bill Somerville wrote:
On 27/11/2018 21:30, Al wrote:
Note below the change in color for GW4HDR after I called him the
first time..
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 weekend
On 27/11/2018 23:58, Morris Wideman via wsjt-devel wrote:
Bill I use HRD for logging/rig control and this is what I saved with
ADIF Master from my log. I use other FT8 software a lot and this meant
many qso`s were not in WSJTX and I had previously trimmed down my HRD
log with master and replace
Bill I use HRD for logging/rig control and this is what I saved with ADIF
Master from my log. I use other FT8 software a lot and this meant many qso`s
were not in WSJTX and I had previously trimmed down my HRD log with master and
replaced the ADI file with this but I noticed I had left fields i
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
contents case-insensitively when it could and should. For example at
least one logging application writes the BAND ADIF field in upper case
ra
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 Some
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 importe
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
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 AD1C
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
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 on
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
___
...@classdesign.com]
Sent: Monday, November 26, 2018 9:15 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] RC5 problem with new grids on the band?
On 27/11/2018 02:35, Don Hill AA5AU wrote:
> It's not just grid squares that are not working. TG9ANF just showed up as
a new DX
On 27/11/2018 02:35, Don Hill AA5AU wrote:
It's not just grid squares that are not working. TG9ANF just showed up as a new
DXCC on 40 meters but I have worked him four times previously on 40-meter FT8.
Hi Don,
thanks for the sample ADIF, I think the problem is the band field which
has an upp
ere.
Don AA5AU
-Original Message-
From: Bill Somerville [mailto:g4...@classdesign.com]
Sent: Monday, November 26, 2018 7:36 PM
To: wsjt-devel@lists.sourceforge.net
Subject: Re: [wsjt-devel] RC5 problem with new grids on the band?
On 27/11/2018 01:26, Don Hill AA5AU wrote:
> Could
I'm finding the Grid part is almost always showing a new grid even though
that station/grid has been worked numerous times. I just unchecked the
Grid and Grid on Band as I've found them inaccurate. I can go the the
wstjx_log.adi and find the call/grid/band/mode logged correctly, but still
showing
On 27/11/2018 01:26, Don Hill AA5AU wrote:
Could the fact that the ADIF is from DXKeeper be the problem? I've been
using the DXKeeper export for many months now and it's always worked. I have
to use the DXKeeper export in order to keep the logs correct for both
instances of WSJT-X I run (two radi
I did a color reset on RC5 startup (also had to disable contest mode as
WSJT-X started in contest mode.) and read the new Quick Start Guide. Then
all CQ decodes from stations I have already worked on the band showed they
were all new grids on the band. This seems to not be working since all of
the
41 matches
Mail list logo
