Andy,
the starting freq for 40m was 7.080 .. it was very busy here in PA.
Neil, KN3ILZ
On 12/1/2018 2:46 PM, Andreas Ma wrote:
Hi David and all
Same problem here. I’m on 7090 (40m as it is nearly 9 p.m. here)
having plenty of signals in the waterfall display, but very few
decodes.
Urp .. re-read your post, RC5 but it wouldn't truncate anything. If
this were happening more people would have reported this. Even the Tx1
message should have been fine.
Again, a full screen cap of the entire window would help.
Neil
On 12/1/2018 11:49 AM, Neil Zampella wrote:
Which RC
Which RC version? A full screen cap would have helped as it would
have shown what the last Tx was, etc.
Neil, KN3ILZ
On 12/1/2018 11:02 AM, Drew White wrote:
This morning I attempted an FT8 RC5 connection with C4XMAS. My
initial transmission was truncated after the 'E' in "EN50". I then
hand button – and the arrow points down (towards the RX frequency).
Have I missed something here?
Allan, OZ5XN.
*Fra:*Neil Zampella [mailto:ne...@techie.com]
*Sendt:* 1. december 2018 13:09
*Til:* wsjt-devel@lists.sourceforge.net
*Emne:* Re: [wsjt-devel] Graphic confusion ;-)
Allan,
I'm not sure
Nope ...
Last month .. still using the same encoder/decoder at least the
name of the executable was finally changed last year.
.. and the UI is horrible.
Neil, KN3ILZ
On 12/1/2018 8:07 AM, Wolfgang wrote:
Re: [wsjt-devel] "FT8 Roundup" mock contest Hello Neil,
sorry,
I have to ask
But that would cause confusion to a lot of people who are new to the
digital modes seeing multiple frequencies on a single band for
JT65/JT9/FT8/etc.
Its much easier to have those who do contests (or follow DXPeditions)
1. Create a new configuration for each contest. (IE: RTTY Roundup)
2.
Allan,
I'm not sure what you're saying, are you talking about V5?. The arrow to
move the RX freq to TX points up (away) from the RX to the TX, and vice
versa. How is that confusing? Most people love that change.
Neil, KN3ILZ
On 12/1/2018 5:05 AM, m...@oz5xn.dk wrote:
Just a single
For what reason? The clone teams are using the 77 bit WSJT-X code,
and to many people that program window UI is horrible.
Neil, KN3ILZ
On 11/30/2018 9:56 PM, Serge Smirnoff R6YY wrote:
27.11.2018 0:55, Joe Taylor пишет:
Another one-hour "practice contest" is scheduled for Saturday,
This has been discussed on the list already.
See the message at :
https://sourceforge.net/p/wsjt/mailman/message/36472448/
Neil, KN3ILZ
On 11/29/2018 11:38 PM, Tim Goeppinger wrote:
I am very thankful and appreciative to the administrators of Winter
Field Day for allowing FT8 as
a Digital
Steve,
you didn't give what Windows version you're using.
I loaded it on Win8.1 with the defaults, and had no issues. Evidently
the installer adds a system path variable or the like, as I didn't
change the default install location and it works fine.
Neil, KN3ILZ
On 11/29/2018 4:36 PM,
There were a few times I wasn't watching JT-Alert where I started a
reply, then caught it a few seconds in and stopped. I think it may
be written off to there weren't that many stations and anything that
popped up with a CQ was clicked on :)
Neil, KN3ILZ
On 11/28/2018 10:53 PM, John
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
and RC5 installed in different folders.
Go back to RC3 when lonely, RC5 when courageous!!
Cheers
Ken
On Tue, 27 Nov 2018 at 14:55, Neil Zampella <mailto:ne...@techie.com>> wrote:
Ken,
did you read the Quick Start guide. Release Candidates 4 & 5
(released today) a
Ken,
did you read the Quick Start guide. Release Candidates 4 & 5 (released
today) are only 77bit, they will NOT decode 75 bit FT8, which is
probably why you're not seeing decodes on a normal FT8 frequency. The
Quick Start advises that you use the standard FT8 frequency, but use the
audio
Al,
RC3 can decode both 75 and 77 bit transmissions, RC4 can't that could be
the reason.
Neil, KN3ILZ
On 11/25/2018 2:08 PM, Al wrote:
I have been running both RC3 & RC4 on the same PC decoding the same
digital audio stream.
At time I have noted that I get decode for 77bit station in RC3
Tom,
I've been using my KX3 for digital work for years. I second Don's
advice about using the KXUSB cable for CAT control. The Signallink is
nothing but a external Sound Card, a very expensive soundcard. Since
you already have it use it, but my advice on sound interfacing is this.
November 30th, when it self-destructs.
Neil, KN3ILZ
On 11/19/2018 3:04 AM, dgb wrote:
Amen
I tried RC4 for the last hr. with CQ's on 160-30 and got many replies
but not one using RC4!!
Apparently a very small part of the population using RC4.
What's it going take to get them to
1/16/2018 10:59 AM, Neil Zampella wrote:
Nope .. just the KXUSB cable .. does it all.
On 11/16/2018 9:34 AM, John Pierce wrote:
Is there any special cableing required to use HRD software with a KX3?
John, AD2F
---
This email has been checked for viruses by AVG.
https://www.avg
Nope .. just the KXUSB cable .. does it all.
On 11/16/2018 9:34 AM, John Pierce wrote:
Is there any special cableing required to use HRD software with a KX3?
John, AD2F
---
This email has been checked for viruses by AVG.
https://www.avg.com
Gary,
I seriously doubt you were called by 75 bit users, as they can't decode
anything you're sending with RC4. So there's really no need to include
anything about RC4 or 77BT in your CQ transmission.
Neil, KN3ILZ
On 11/16/2018 3:18 AM, Gary Hinson wrote:
RC4 works down here on the Far
FWIW ... you don't need to use 'FREE TEXT' to send CQ DX .. just insert
the ' DX ' between the CQ and your CALLSIGN (with a single space
between) in the TX6 message and it will work fine.
Neil, KN3ILZ
On 11/12/2018 10:26 AM, Al Pawlowski wrote:
There is definitely a problem with “free text”
Hi all,
since I've been using FT8 with its auto-sequence system, I've always had
the message tab on Tab 1. However, there was a comment on the FT8
forum that the auto-sequence would not progress unless the user was on
Tab 1, and not Tab 2 in RC3.
Any truth to that requirement and/or
FWIW .. there is NO need to have CQ DX in the 'free text area' as you
can add that to the standard CQ message by just typing it in and letting
the system work as designed.
Neil, KN3ILZ
On 11/1/2018 12:29 PM, Al Pawlowski wrote:
Similar (rc3 on Win) problem just occurred with me. Using Tab 1
Considering that Joe Taylor has specifically said that v2.0-RC3 will
default to 77 bit messages in DXPedition mode and should not be used for
any DXPeditions until after the final General Availability release; and
VP6D on the website's FT8 operating procedure page asks that v1.9.1 be
used
FWIW ... K1JT in the FT8 DXPedition mode user guide specifically says,
if you can't hear the DXPedition station, don't call them.
Item #7 for hounds says:
"Please do not call Fox if you are not receiving his transmissions. Do
not call Fox if he issues a directed CQ (“CQ EU”, “CQ 7”, …) and
See attachment ..
On 10/17/2018 1:23 PM, 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 with
WSJT-X but
Could you explain .. "hopelessly broken" ... did you check to see if the
'worked B4' setting is checked under colors? Are you sure you didn't
wipe out your log files with the install?
More information is helpful so that the developers can figure if there
is a problem or not.
Neil,
Bill,
OS: Windows 8.1
Neil, KN3ILZ
On 10/17/2018 11:28 AM, Neil Zampella wrote:
Hi All,
I too received the LoTW error. The ARRL has just changed their sites
to use TLS 1.1, so this may also contribute to this issue.
Neil, KN3ILZ
---
This email has been checked for viruses by AVG
Hi All,
I too received the LoTW error. The ARRL has just changed their sites
to use TLS 1.1, so this may also contribute to this issue.
Neil, KN3ILZ
---
This email has been checked for viruses by AVG.
https://www.avg.com
___
wsjt-devel
Why are you using a locally compiled version of 1.9.1. There IS no
v1.10.0 as it was a number change for any bug fixes in 1.9.1, there's
nothing new in that.
If v2.0-RC2 works ... use it.
Neil, KN3ILZ
On 10/15/2018 2:23 PM, Höss Lajos wrote:
Hi,
I tried this version of
Ah ... I need to review that manual again :(
On 10/9/2018 10:12 AM, Neil Zampella wrote:
As mentioned in the Quick Start guide, both boxes need to be checked
when testing 77bit mode. These are two different 'flags' or
'switches' as I believe the encoder & decoder are two sepa
new message, and if I decoded an
old message, I would reply with old message. otherwise, why are there
separate selections for TX and RX message format?
things only work if both are selected or both are not selected.
not really an issue, more of a queston.
On Mon, Oct 8, 2018 at 11:22 PM
Um .. lets not add complexity when there is a perfectly good alternative
that does this and more ... JT-Alert
Neil, KN3ILZ
On 10/7/2018 5:18 PM, Chuck Furman wrote:
Gary Hinson and Bill Pence,
You guys both got my point! By the time your brain picks someone to
call, and your fingers click
Um ... perhaps there aren't any stations calling CQ ?? It decodes, but
has nothing to display.
Neil
On 10/7/2018 10:29 AM, Frans Boot wrote:
WSJT-X 2.0 RC1 doesn’t seem to decode each receive cycly if the box CQ
ONLY is checked.
73, Frans PA0FBR
Verzonden vanuit Mail
surprised that Yaesu and Kenwood are not ahead of Elecraft... but what
does it matter anyway. I don't know a soul who would sell their
Elecraft rig just because of the results of that "survey".
Dave - K9FN
On Wed, Oct 3, 2018 at 11:26 PM Neil Zampella <mailto:ne...@techie.com>>
Might have more to do with the fact that ICOM is a supporter/advertiser
on that site .. LOL
Neil, KN3ILZ
On 10/3/2018 11:51 AM, Charlie T wrote:
You know, I'll bet the reason Icom is #1 in this survey is just possibly,
I'm going out on a limb here, they got more votes.
Along the same lines,
Mike,
I had heard anecdotal stories about Xfinity modems and ethernet
connections to non-computer equipment. I actually had one customer who
had the problem, I took a spare Linksys router, and connected it between
the Xfinity modem, and the equipment, and that fixed the issue for my
Jim,
I use PTT with both my K2 and my KX3, its just one additional USB
connection to the PC. The other is to my external USB soundcard which
does audio for both.
Neil, KN3ILZ
On 10/2/2018 4:20 AM, Jim Brown wrote:
On 10/1/2018 10:47 PM, Rick WA6NHC wrote:
While thousands may use VOX
Just uncheck the DXCC box .. it fixes the issue.
Neil, KN3ILZ
On 9/26/2018 6:29 PM, Don Hill AA5AU wrote:
I saw Joe's post that says we can use either rc1 or rc2 in tonight's FT8 RU
test. I have not upgraded to -rc2 yet because of the JTAlert bug since
JTAlert is extremely important to me
I agree with you Don on a way to just turn off color coding, or just let
the user decide what they want, but trying to accommodate everyone is
turning into the predicted black hole.
As far as JT-Alert, Laurie is only one person, and while he's been
trying to get the code moved to a
Uwe,
the pre-2.0 log DOES NOT contain six character grids, other than your
own. I'm looking at my log for the past year, and the logged station
only shows the 4 character grid since that's the only thing sent in the
standard exchange.
Its not a bug, its a lack of DATA. You cannot match
Tom,
some stations are using clone programs that have bastardized the
DXPedition mode, or early 1.9.1-RC versions that did not have the
standard FT8 frequency lock out.
Nothing you can do about that, and it does not appear that you did not
receive any type of signal report.
Its up to you
Jim,.
On 9/22/2018 8:42 PM, DeYoung James wrote:
Greetings,
Thanks to Joe for taking his valuable time to respond.
I didn't realize that the Enable TX should stop after each QSO.
Apparently it does in V2.0.0-rc1. However, tonight I am back running
V.1.9.1. I have made 5 QSOs in a row on
Um ... I don't remember JT65 or JT9 having any auto-sequence setup in
WSJT-X. They are both 42/46 second Tx cycles, plenty of time to
dbl-click on a decode.
Neil, KN3ILZ
On 9/22/2018 7:46 PM, Justin EI3CTB wrote:
Hello,
I tried to have a QSO in JT9 & JT56 after downloading
This has been the case for FT8 since the first v1.9 beta back in 2017.
The developers do NOT want to create an automated QSO machine, so human
intervention to initiate another CQ call is required.
Neil, KN3ILZ
On 9/22/2018 1:42 AM, DeYoung James wrote:
1) The transmitter always goes off
I believe this is as designed as far as the grid being Tx and displayed.
This is from the 'New Features' text file as found on K1JT's WSJT-X webpage:
--
8. Compound or nonstandard callsign calling CQ
FWIW .. I use the paid AVG Internet Security and the program installed
without error.
That said, many antivirus programs will be triggered on Ham Radio
programs as they are not in 'wide spread' use, and are not in their
lists of authenticated programs.
Neil, KN3ILZ
On 9/17/2018 3:32 PM,
One thing to add ... once you have the CAT control setup properly, you
should change bands via WSJT-X, as it will control the band changes on
the rig, not the reverse.
Neil, KN3ILZ
On 9/12/2018 6:15 PM, Don Wilhelm wrote:
Richard,
You must have communications between WSJT-X and the K3S in
Hi all,
I was looking in the 1.9.1 user guide for an explanation of why using
the 'Hold Tx Freq' should be checked, when I noticed that its not
mentioned, but the old 'Lock Tx=Rx" option is!
Obviously this was overlooked by everyone, and should be updated for v2.0.
73,
Neil, KN3ILZ
---
This is normal. From the User Manual, section 4.2:
"/Split Operation/: Significant advantages result from using *Split*
mode (separate VFOs for Rx and Tx) if your radio supports it. If it does
not, /WSJT-X/ can emulate such behavior. Either method will result in a
cleaner transmitted
Paul,
I understand you're not wanting to use the PC Sound Card for Digi, as
too often Windows sounds get into the transmission. FWIW .. you really
don't need a Signalink with the KX3, but since you already have it I can
understand your using it. In future if you want to take the KX3 for
Hi Don & Phil,
I have my K2 setup for WSJT-X and found that the K2 settings in the
Hamlib3 version in WSJT-X do not seem to work properly. What I did was
use DXLab's DX Commander as the rig interface, so it is talking to the
K2, and then I have that selected as the 'rig' in WSJT-X.
This
Charlie,
I hadn't checked the history lately, but the block was released in 1.9.1
... you're right about the Doppler correction though.
Neil, KN3ILZ
On 8/17/2018 8:36 AM, char...@sucklingfamily.free-online.co.uk wrote:
Neil
I believe that 1.9.2 blocks fox and hound from transmitting on
Many people build their own version, if you build WSJT-X right now,
you'll get 1.9.2.
The only difference (as I understand it) between it, and v1.9.1 is that
the source code has been moved to use GIT, rather than Subversion as the
version control system.
Neil, KN3ILZ
On 8/17/2018 7:35 AM,
(philosophical) interpretation stated in
item 2.?
take
de JA5AEA
Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows 10
*From:* Neil Zampella
*Sent:* Friday, August 10, 2018 10:49:14 AM
*To:* wsjt
ance, too.
George J Molnar
Virginia, USA
> On Aug 8, 2018, at 8:04 AM, Neil Zampella mailto:ne...@techie.com>> wrote:
>
> Frankly, I don't see where you're getting the idea that JT65
sensitivity is missing?
>
> It is stil
FT8 was never supposed to have the same sensitivity as JT65 .. you can't
not with only 13 or 14 seconds of Tx time. As was pointed out,
you can have -24 reports on FT8 but its more a result of the noise floor
in your location or the receiving station's location.
Not to mention that
Frankly, I don't see where you're getting the idea that JT65
sensitivity is missing?
It is still much more sensitive than FT8, and will be for the
foreseeable future, as are the other WSJT-X modes. JT9A is at -27,
JT65A is at -25, and QRA64A is at -26. FT8 is -21 .. all this is
based
I'm fairly sure that Bill was referring to the fact that Microsoft is
not supporting WinXP in any way, shape or form, thus obsolete.
He is NOT saying that WSJT-X 1.9.1 will not work with XP.
IMHO, anyone still on XP and linked to the internet is asking for
issues. Complaints about Windows
Anton,
at the bottom of each digest or email, there is a URL to unsubcribe
go here at the lower part of the page:
https://sourceforge.net/projects/wsjt/lists/wsjt-devel
Neil, KN3ILZ
On 7/26/2018 9:38 AM, Anton STEINWIDER wrote:
Hello WSJT-Team !
Please finish the sending of the infomails
Jim
There is no added complexity of PTT using CAT at all. The KX3 (and K2
for that matter) is just triggered by CAT commands, and not VOX.
I've cot CAT control of PTT on my KX3 and K2, and all I had to do was
plug in the K2's serial cable, and the KXUSB for the KX3. Even my IC-718
(now in
. Keep it simple.
73 and good DX
KC4IM
On Jul 5, 2018, at 9:27 PM, Neil Zampella <mailto:ne...@techie.com>> wrote:
Bill,
true, but he was asking about FLDidgi to send CW ...
Neil, KN3ILZ
On 7/5/2018 9:25 PM, Bill Rowlett wrote:
With the Elecraft USB cable, your computer, you sen
Bill,
true, but he was asking about FLDidgi to send CW ...
Neil, KN3ILZ
On 7/5/2018 9:25 PM, Bill Rowlett wrote:
With the Elecraft USB cable, your computer, you send CW from your keyboard. The
beauty of the KX3.
On Jul 5, 2018, at 7:11 PM, Neil Zampella wrote:
Aaron,
you really don't
Aaron,
you really don't need the Signalink, just two stereo audio cables (I
used the ones in the KX3-PCKT cable set) a good soundcard in your PC or
an external USB soundcard, and the KXUSB cable that comes with the KX3.
This gives you the audio input/output you need, and the CAT control
.. and if you add JT-Alert to the mix, it can do the QRZ lookup for you ..
Neil, KN3ILZ
On 7/3/2018 5:32 PM, Carl Yaffey wrote:
On Jul 3, 2018, at 4:42 PM, Grant Youngman wrote:
and don’t care to find out what the other guy’s name is or what he/she does
when they aren’t punching at their
Wes,
you're taking that out of context. The structured messages allow for
redundancy if some of the original message is missing. The decoder can
take the sync symbols so that the system can understand what type of
message it is, it still needs the callsign and signal report.
More details
Mike,
the only automation is in the middle of the contact, the operator has to
be in front of the radio and computer in order to select a station to
answer, to begin transmission, and to log the QSO.
None of that is automated in WSJT-X. I cannot speak for other programs
that have gone
Andy,
that's not right ... you have to be in the shack to make sure the system
keeps calling as there is a 2 minute timer that will turn off your
transmission. It is also suggested that if you don't get a reply
back after the first two minute period, manually move the Tx freq.
Finally,
Remote RS-BA1 console.
John
*From:*Neil Zampella [mailto:ne...@techie.com]
*Sent:* Tuesday, July 3, 2018 4:39 PM
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel] Icom IC-7700/RS-BA1/WSJT-X
John,
I don't think that Hamlib or Omnirig uses UDP packets to control the
rig, its
Bill,
Thanks ... always learning something new. Need to file this one away.
Neil
On 7/3/2018 7:50 PM, Bill Somerville wrote:
On 04/07/2018 00:39, Neil Zampella wrote:
I don't think that Hamlib or Omnirig uses UDP packets to control the
rig, its more a bidirectional serial interface
Utility app) and full
remote capability, albeit only with their software. I can’t believe
Icom is proprietary with its IP stack, as some say.
*From:*Neil Zampella [mailto:ne...@techie.com]
*Sent:* Tuesday, July 3, 2018 11:18 AM
*To:* wsjt-devel@lists.sourceforge.net
*Subject:* Re: [wsjt-devel
If I remember right, the CW ID is not implemented for FT8, as it would
then Tx into the next time slice. There's only a second between the end
of the FT8 transmission and the end of the Tx period. In JT65/JT9 you
have a bit more time.
Neil, KN3ILZ
On 7/3/2018 3:01 PM, David Tiller wrote:
John,
I was using my IC-718 with full CAT control without the CT-17 using a
cable from XGGCOMMS.com ... this one looks like the one you need:
**Icom CAT IC-Cable-7-USB-ISO**
The interface offers full USB CAT Control and 600:600 Ohm transformer
isolated audio interfacing of your Icom
To unsubscribe, copy and paste the URL that's listed at the bottom of
this message thread. You'll get a page that you will have to enter your
email address in, then click on the UNSUBSCRIBE button.
Neil, KN3ILZ
On 7/2/2018 7:09 PM, John wrote:
On Tue, 03 Jul 2018 09:04:04 +1000, Ed Stokes
Lee,
I get the digest too, and the Elecraft reflect includes the messages as
attachments. I'm not sure what email program you're using, as I use
Thunderbird, and it does this.
What I do is if I find a message I want to reply to I look at the list,
get an idea of which message it is in the
Charlie,
the consensus of many on the FB pages is that this station was a pirate.
Neil, KN3ILZ
On 6/30/2018 11:09 AM, Charles Suckling wrote:
Hi Mike
The problem with needing to see a CQ is that the dxpedition may rarely
transmit a CQ (some folks were reporting this yesterday). Then,
I realize I didn't give the release number: 45427a (all that is shown
there).
Neil
On 6/30/2018 4:19 AM, Neil Zampella wrote:
Joe,
I was able to duplicate this this morning.
Action:
WSJT-X in Hound mode on 20m, I was trying to adjust my bandwidth
properly to make sure I can see the FOX
Wayne,
you've almost made me want to order another K2 kit, even though I just
finished one. That said, if anyone has one they want someone else to
build .. hi hi.
Neil, KN3ILZ
On 6/29/2018 5:21 PM, Wayne Burdick wrote:
A few years ago, in a distant land known for its modular seafood
I can backup Don's statement about the K2.
I have my K2/100 working reliably with the KAT100, connected to the PC
using a serial to USB adapter. Using the DXLabs DX Commander to
control the rig, and interface with WSJT-X, PTT is through CAT.
I can even work remotely using VNC, as the DX
Joe,
I was able to duplicate this this morning.
Action:
WSJT-X in Hound mode on 20m, I was trying to adjust my bandwidth
properly to make sure I can see the FOX at around 200 + Hz. Not
seeing a thing there, but then saw one station that was replying at
305, and thought at least they see
Yep .. been there, .. done that ... waited for the replacement from
California ... ... and as Richard points out, finished mine with
timely advice from Don.
FWIW .. its often faster to email to supp...@elecraft.com, as Don
usually answers within a few hours or less.
Neil, KN3ILZ
On
select it.
I'm running the latest release of WSJT-X, Windows 10, and an ICOM
IC-7300.
73,
John
John L. Broughton
www.wb9vgj.us
wb9...@arrl.net
2silverhon...@gmail.com
On 6/28/2018 4:46 AM, Neil Zampella wrote:
You can easily take care of this by creating a separate Configuration
for Fox & H
You can easily take care of this by creating a separate Configuration
for Fox & Hound mode.
Very easily done, you don't have to edit frequencies until you know of a
new DXPedition you wish to contact, and you don't have to worry about
changing any other settings that may mess up your normal
You can do that with a Screen Capture program now. Windows 10 includes
one, and Gadwin Print Screen is free for the download in 32 & 64 bit
versions.
Neil, KN3ILZ
On 6/27/2018 5:50 PM, Bill Turner wrote:
Most FT8 users have email addresses in QRZ, so you can send them a
screen shot. In my
I just finished mine, and its loaded.
I agree with all the previous advice, I picked up another 40 drawer
parts cabinet for the parts, used them both, and kept them in order
that way. Each board had its own area of the cabinets,Packing Box bag
in one area, Control Board in the next, RF
Just wondering .. since I saw the NA VHF Contest checkbox on the main
window, do you have VHF/UHF/Microwave featured turned on?
What happens if you uncheck that box?
Neil, KN3ILZ
On 6/12/2018 8:27 PM, Steve Sacco NN4X wrote:
It exists, and was last modified today, and looks like the
Um ... just a heads up to the Elecraft folks, the older 1.13.6.17
version is the only version that's shown on the Firmware & Software page
on the Elecraft website.
Neil, KN3ILZ
On 6/8/2018 8:23 PM, John Hiatt wrote:
Does it have to be that old version? The current version is at:
of the saying when someone only has a hammer in
their toolbox.
Again, the OP should be read, understood, and answered.
I think some here think software is perfect; and all platforms produce
identical results.
I've posted a bug; plain and simple.
On Wed, Jun 6, 2018, 8:19 PM Neil Zampella
Can you prove that its not RF in the shack? If you can verify that RF
is not causing it then its a bug, otherwise, there is no issues with the
software in your case.
Neil, KN3ILZ
On 6/6/2018 5:27 PM, John C. Westmoreland, P.E. wrote:
OK, so we're 100% clear - and I want this bug report to
Rick .. you can do this by going to this URL and unsubscribing your self:
http://mailman.qth.net/mailman/listinfo/elecraft
On 6/5/2018 3:36 PM, Rick Chilcote wrote:
__
Elecraft mailing list
Home:
So you're saying that if you select K3 as the rig, and PTT to use CAT,
you get error messages?
FWIW .. FT8 mode DEFINITELY needs CAT control, especially if you're
going to be chasing any DXpeditions as they will be using the Fox &
Hounds mode. It also makes sure that when you send spots to
FWIW .. you can do it yourself by heading to this url:
http://mailman.qth.net/mailman/listinfo/elecraft
Neil, KN3ILZ
On 6/3/2018 7:52 PM, Greg Neely wrote:
Thanks.
73
KL4JN
__
Elecraft mailing list
Home:
Considering that FT8 is done with 8-tone frequency-shift keying (8-FSK)
at 12000/1920 = 6.25 baud. I'd like to know how you can get that tone
in CW?
As far as the S/N threshold of the various WSJT-X modes (from the
protocol specs in the WSJT-X user guide):
FT8 : -21
JT4A
Not really, the release version is 1.9.0 ... all the previous versions
were release candidates, nothing more.
Neil, KN3ILZ
On 5/30/2018 8:49 AM, John wrote:
Hi Bill,
The release note needs a minor fix:
Release: WSJT-X Version 1.9.0
June 1, 2018
FWIW .. really not needed, as FT8 decodes the entire passband, and the
station you're replying to will receive your transmission. Its
better if you find a Tx location, set the Hold TX Freq, and answer
everyone from there. Stations will then be able to see your answer
clear of any other
I just finished my K2 build, with all the options and Agree with Peter,
there if you buy the options now, the K2 manual will point out just when
you should install the various plugs and other components during the
main K2 build.
My advice, all the K2 manuals are online as PDF at the Elecraft
he change KAT2 R6 to 470
ohms, there is a resistor provided in the K60XV kit for that.
73,
Don W3FPR
On 5/20/2018 11:27 PM, Neil Zampella wrote:
Hi all ..
has anyone seen this type of issue with their K2. Before installing
the K60XV, I had no problems seeing 10 w on 40 meters. After
ins
Hi all,
over on the FT8 Facebook group, there has been a lot of discussion about
people sending QSY transmissions using FT8 'free text' modes. I
realize that its needed for MSK144, but could it be disabled for those
modes that have no need of using it? Apparently some LIDs are sending it
Since the issue stopped when you reverted back to a previous Windows
build, its a Windows issue; probably drivers or the like.
Not much the WSJT-X developers can do about that.
Neil, KN3ILZ
On 5/23/2018 8:44 AM, Dave Crockett wrote:
My apologies in advance if this has been covered, but I
Hi all ..
has anyone seen this type of issue with their K2. Before installing
the K60XV, I had no problems seeing 10 w on 40 meters. After
installing the K60XV, I can't get above 1 watt on 40 meters OR 60 meters.
Did I screw something up, or is there some menu setting I missed when I
201 - 300 of 429 matches
Mail list logo
