Date   

Locked Re: Rig Control error with FT-857D

Reino Talarmo
 

Mark,

It should be totally safe without any downsides with v2.2.2. At least I have not seen any comment on this mail list.

Good Luck and 73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Mark Sunderlin
Sent: 11. lokakuuta 2020 3:30
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Rig Control error with FT-857D

 

there is a known issue with the Hamlib version in WSJT-X v2.2.2, the Yaesu FT-817/818/897 drivers don't work. Selecting the FT-857 driver should work for genuine versions of these rigs, some rigs that emulate the FT-817 do not work with the FT-857 driver.

I thought I was going crazy as this weekend I decided to get my 817 out of the closet and try some super QRP FT8 (The lowest my FT-991a will do is 5W) ... and it was driving me nuts .. did my Ct62 cable break in storage?

Then I found this thread and set it to FT-857 and relaxed. This should get me through until 2.2.3 ... But ... is there any downside / side effect I should about using 857 setting, with an (true, physical) 817 rig? 


Locked Re: Ancient history: JT65-HF

Jim Brown
 

On 10/10/2020 1:58 PM, John, K9MM wrote:
I was using the program JT65-HF, a modification by W6CQZ,
I also used it and liked it, but as Neil said, a lot has changed since 2012. :) Many of us use WSJT-X and/or JTDX; just as serious RTTY contesters use both MMTTY and 2Tone, some of us use both WSJT-X and JTDX at the same time. It's common for MMTTY to get decodes that 2Tone doesn't, and vice-versa. Likewise for WSJT-X and JTDX.

73, Jim K9YC


Locked Re: log

Jim Shorney
 

See here:

https://wsjtx.groups.io/g/main/search?q=%3Ceh%3E

73

-Jim
NU0C

On Sat, 10 Oct 2020 16:45:20 -0500
"John Kjos" <john@...> wrote:

When I start the program, it says Error Scanning ADIF Log, Invalid ADIF
Header. Any help please?

73 John W9RPM


Locked Re: Ancient history: JT65-HF

Andrew O'Brien
 

I was a beta tester for that software back in the early days of JT65A on HF.  The author got tired of the "drama" caused by some users and gradually QSB'd away.
Andy K3UK


Locked Re: Hamlib error: Protocol error while testing getting current VFO (FT-817 / FT-818)

Mark Sunderlin
 

On Fri, Jul 31, 2020 at 04:27 AM, neil_zampella wrote:
In fact, the last Hamlib update that was incorporated included problems that caused issues for many Yeasu rigs.   That is why there was (is) a workaround to use the FT-857 (I believe) selection for other Yeasu 800 series rigs.
Thank the gods of propagation for this group. I was going crazy wondering why my CT-62 cable, after all these years of working with my 857, went dead when I tried to use it with my 817 ... :-) 

Switched WJTX 2.2.2 to 857, all is well. Any side effects of using the 857 mode I should know about as we wait for 2.2.3? 


Locked Re: error

Dave Garber <ve3wej@...>
 

Discussed here many times, edit the wsjt log adi file   <eh> should be <eoh>  i believe

Dave Garber
VE3WEJ / VE3IE


On Sat, Oct 10, 2020 at 4:29 PM John Kjos <john@...> wrote:
I keep getting, ERROR SCANNING ADIF Log, Invalid ADIF header.

Any ideas?

73 John W9RPM

--
EMAIL: john@...
WEBPAGE: http://www.w9rpm.com/
DX CLUB: http://www.tcdxa.org/





Locked Re: Rig Control error with FT-857D

Mark Sunderlin
 

there is a known issue with the Hamlib version in WSJT-X v2.2.2, the Yaesu FT-817/818/897 drivers don't work. Selecting the FT-857 driver should work for genuine versions of these rigs, some rigs that emulate the FT-817 do not work with the FT-857 driver.

I thought I was going crazy as this weekend I decided to get my 817 out of the closet and try some super QRP FT8 (The lowest my FT-991a will do is 5W) ... and it was driving me nuts .. did my Ct62 cable break in storage?

Then I found this thread and set it to FT-857 and relaxed. This should get me through until 2.2.3 ... But ... is there any downside / side effect I should about using 857 setting, with an (true, physical) 817 rig? 



Locked Re: log

Bruce
 

Hello John,,

If no one has helped you, I believe that I can fix your file for you. I will need you to email two WSJTx files to me. If you give me your phone number to my direct email (w8hw@...) I will be happy to call you and talk you through this.

73, Bruce, W8HW

===============================


On 10/10/2020 5:45 PM, John Kjos wrote:

When I start the program, it says Error Scanning ADIF Log, Invalid ADIF Header. Any help please?

73 John W9RPM





Locked Re: Hamlib Error With IC-9700

Stan Edwards - WA4DYD
 

Someone ask directly the interface:  USB directly to the radio for both CAT, programming, and audio codec.  Just for the record, the programming software connects and will communicate with the radio.


Locked Hamlib Error With IC-9700

Stan Edwards - WA4DYD
 

Today when attempting to use my IC-9700 I am getting the following error message when attempting to connect to the radio:

Rig Control Error - Hamlib error- Command rejected by the rig while exchanging VFOs

This error was not present during the June VHF contest and this is the first time I've tried to connect the radio since the contest.  I checked the drivers and they are current.  This happened with three different computers which I have used previously.  I don't really understand how things may have changed.  All options are set properly for the IC-9700.  The only thing that would potentially have changed that would cause this type of error seems to be the Hamlib library for the 9700.

Any suggestions?

Thanks,
Stan Edwards, WA4DYD


Locked Re: Ancient history: JT65-HF

neil_zampella <neilz@...>
 

John

it is totally obsolete as improvements have been made in JT65, along with newer protocols.   There are some differences, which you will see in the new version of WSJT-X v2.3.0 when it is released to General Availability.   Right now its in Release Candidate status but can be used without problems for JT65, JT9, FT8 and so on.

Neil, KN3ILZ

On 10/10/2020 3:58 PM, John, K9MM wrote:

I started using JT65 in 2012. I was using the program JT65-HF, a modification by W6CQZ, because as I recall it was optimized in some way for HF operation compared to the version of WSJT which was then current.

Can I assume that with all the improvements that have been made in the software since 2012 WSJT-X v2.2.2 is now better than JT65-HF for using JT65 on the HF bands? I haven't used JT65-HF in several years and would like to uninstall it if it is obsolete. Thanks!

73,

John, K9MM




John Kjos
 

When I start the program, it says Error Scanning ADIF Log, Invalid ADIF Header. Any help please?

73 John W9RPM

--
EMAIL: john@...
WEBPAGE: http://www.w9rpm.com/
DX CLUB: http://www.tcdxa.org/


Locked Ancient history: JT65-HF

John, K9MM
 

I started using JT65 in 2012. I was using the program JT65-HF, a modification by W6CQZ, because as I recall it was optimized in some way for HF operation compared to the version of WSJT which was then current.

Can I assume that with all the improvements that have been made in the software since 2012 WSJT-X v2.2.2 is now better than JT65-HF for using JT65 on the HF bands? I haven't used JT65-HF in several years and would like to uninstall it if it is obsolete. Thanks!

73,

John, K9MM


Locked Re: error

Bill Somerville
 

On 10/10/2020 21:26, John Kjos wrote:
I keep getting, ERROR SCANNING ADIF Log, Invalid ADIF header.

Any ideas?

73 John W9RPM
Hi John,

you are probably running WSJT-X v2.2.2, that version has a defect that causes it to create an invalid ADIF logfile header. You can fix the header with a text editor (Notepad.exe is fine on Windows). The file name is wsjtx_log.adi and you need to change the first line where it has <eh> to <eoh>, the  file is in the WSJT-X log files directory ("Menu->File->Open log directory").

73
Bill
G4WJS.


Locked error

John Kjos
 

I keep getting, ERROR SCANNING ADIF Log, Invalid ADIF header.

Any ideas?

73 John W9RPM

--
EMAIL: john@...
WEBPAGE: http://www.w9rpm.com/
DX CLUB: http://www.tcdxa.org/


Locked Re: Leadership issue & [WSJTX] Movin' on up

George Armstrong
 

KTF,

You raise a good point; however, I suggest we need to encourage AR leadership to determine and advise solutions to this issue. Establish a statistically clear sub-channel as a calling frequency when you can.

73,
George
K9GA


From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of Kermit Lehman via groups.io <ktfrog007@...>
Sent: Thursday, October 8, 2020 11:11 AM
To: main@wsjtx.groups.io <main@wsjtx.groups.io>
Subject: [WSJTX] Movin' on up
 
FT8 is extremely popular and the covid-19 pandemic has doubled down on FT8 activity.  During their peak activity times 20m and 40m are so congested that QSOs become difficult.  How about trying moving the dial frequency up a small amount, 500 or 1000 Hz?  This would open up some new territory without sacrificing too much of the view of the standard band.


73,

Ken, AB1J


Locked Re: Vertical spikes every 1000 hz prevent decoding

 

The high speed and full speed modes have a sync pulse every 125us.
Phil.

On 10 Oct 2020 19:40, Andy TALBOT <andy.g4jnt@...> wrote:
I see weak 1kHz spikes on every USB soundcard I've used (admittedly, most based around PCM2900 chips)

Never really thought much of it, as they're typical 50 - 70dB below full scale.
Interesting to know it may be USB sync,



--
73 Phil GM3ZZA


Locked Re: Vertical spikes every 1000 hz prevent decoding

JP Tucson, AZ
 

Hmmm...

If they are 50-70 dB down... you shouldn't see them at all if you have it setup right. 

Mine barely shows anything at all @ the bottom -25dB limit.

Besides that, those images posted earlier showed very strong; i.e. red marks.

73 - John - N7GHZ


On Sat, Oct 10, 2020, 11:40 AM Andy TALBOT <andy.g4jnt@...> wrote:
I see weak 1kHz spikes on every USB soundcard I've used (admittedly, most based around PCM2900 chips)

Never really thought much of it, as they're typical 50 - 70dB below full scale.
Interesting to know it may be USB sync,





Locked Re: Vertical spikes every 1000 hz prevent decoding

Andy Talbot
 

I see weak 1kHz spikes on every USB soundcard I've used (admittedly, most based around PCM2900 chips)

Never really thought much of it, as they're typical 50 - 70dB below full scale.
Interesting to know it may be USB sync,


Locked Re: Nevada QSO Party use of FT8/4

Patrick Hung
 

I don't know about needing to add the frequency to the list - I simply tuned it to 14078 and it stayed there, while listening/transmitting. I turned off Split to stay on the frequency.


Best regards,

Patrick Hung


On Sat, Oct 10, 2020 at 11:20 AM Dave Garber <ve3wej@...> wrote:
is 14.078 in your frequency list as a ft8 frequency...  maybe has to added

Dave Garber
VE3WEJ / VE3IE


On Sat, Oct 10, 2020 at 12:06 PM Patrick Hung <pathung@...> wrote:
I've been trying to establish contact on 14.078 MHz, but WSTJX isn't decoding, despite apparent signals on the waterfall, as well as the normal FT8 signal sounds. 

Decoding works just fine on 7.074 MHz.

What could be the cause of this?
--
73,
Patrick, W2TAR






--
73,
Patrick, W2TAR