Date   

Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

Bob Lewis
 

If you change the name of the file, that is the same as deleting it as far as WSJT-x is concerned so it creates a new empty log file (with the eh error). I routinely COPY (not rename) my log file to a differently named backup log file located on a different hard drive so that I always have a backup. I never delete or rename the original log file.

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of John L. Broughton
Sent: Monday, September 07, 2020 1:06 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

 

That is not my problem. The file is never deleted  except I change the name most every day. At least twice, when I had a few QSOs in the log file and quit a WSJT-X session, when I started the next session, the log file still had the QSOs in it, but the eoh was changed to eh.

I can't say for certain that the eoh gets changed to eh only when I already have an existing logging file and not when a new one is created as I don't recall the situation each time this has happened, just the last two times. I am now paying attention to see if it ever happens on the original creation of the log file. I have checked the log file after closing WSJT-X and the eoh has been there.

73,

John, WB9VGJ

On 9/4/2020 1:31 PM, Philip Rose via groups.io wrote:

The other cause could be another program such as a logger reading the wsjtx log file then deleting it. So the next time the user start wsjtx it creates a new file with the bum header. 

 

My homebrew logger has that option but I don't use it 

 

Phil GM3ZZA


--
73 Phil GM3ZZA

 

Virus-free. www.avg.com



 

 


Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

Bill Somerville
 

John,

if you re using JTAlert then you should configure it to automatically insert your completed WSJT-X QSOs into your HRD log. That would save you a lot of trouble.

73
Bill
G4WJS.

On 07/09/2020 18:00, John L. Broughton wrote:
That file contained all the contacts I made in the prior session. When I opened the next session, the eoh had been changed to eh.

My habit is that most every day, I save the wsjx_log.adi to another name and a new file is created the next time I open WSJT-X. I upload the daily files to LoTW and eQSL, import the file to my HRD log (I like it as it is handy for displaying all the essential elements of a QSO when I have to check a QSO for confirmation purposes on QRZ or eQSL), and then import my LoTW log into QRZ. I like to do all that manually rather than logging each contact directly into some other log.

I rely on the running log in JTAlert to flag worked before stations, wanted calls/DX/states, etc.

73,

John, WB9VGJ
--
John L. Broughton
wb9vgj@arrl.net
2silverhondas@gmail.com
www.wb9vgj.us

On 9/4/2020 1:23 PM, Jim Preston N6VH wrote:

On 9/3/2020 6:29 PM, John L. Broughton wrote:
Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ
--
John L. Broughton
wb9vgj@arrl.net
2silverhondas@gmail.com
www.wb9vgj.us
John,

Since that is your entire file, and you have been using WSJT-X for several years, then that indicates that something is either re-naming or deleting your previous file. Other wise, that file would have many more entries in it. The only way I know that that could happen, would be if you click on File/Erase wsjtx_log.adi. Since I don't think that is happening, I have no idea what is causing the problem, but I am reasonably certain it is not WSJT-X. I don't think an AV program would pick on that particular file. There must be something on your computer that is causing this.

73,

Jim N6VH


Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

John L. Broughton
 

That is not my problem. The file is never deleted  except I change the name most every day. At least twice, when I had a few QSOs in the log file and quit a WSJT-X session, when I started the next session, the log file still had the QSOs in it, but the eoh was changed to eh.

I can't say for certain that the eoh gets changed to eh only when I already have an existing logging file and not when a new one is created as I don't recall the situation each time this has happened, just the last two times. I am now paying attention to see if it ever happens on the original creation of the log file. I have checked the log file after closing WSJT-X and the eoh has been there.

73,

John, WB9VGJ

On 9/4/2020 1:31 PM, Philip Rose via groups.io wrote:
The other cause could be another program such as a logger reading the wsjtx log file then deleting it. So the next time the user start wsjtx it creates a new file with the bum header. 

My homebrew logger has that option but I don't use it 

Phil GM3ZZA

--
73 Phil GM3ZZA

Virus-free. www.avg.com


    


Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

Reino Talarmo
 

John,

 

Thanks for solving the mystery!

 

There is a known bug in wsjt-x v2.2.2 and at the generation of a new wsjtx_log.adi file the header is ended with <eh>, hi.

 

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of John L. Broughton
Sent: 7. syyskuuta 2020 20:00
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

 

That file contained all the contacts I made in the prior session. When I opened the next session, the eoh had been changed to eh.

My habit is that most every day, I save the wsjx_log.adi to another name and a new file is created the next time I open WSJT-X. I upload the daily files to LoTW and eQSL, import the file to my HRD log (I like it as it is handy for displaying all the essential elements of a QSO when I have to check a QSO for confirmation purposes on QRZ or eQSL), and then import my LoTW log into QRZ. I like to do all that manually rather than logging each contact directly into some other log.

I rely on the running log in JTAlert to flag worked before stations, wanted calls/DX/states, etc.

73,

John, WB9VGJ

On 9/4/2020 1:23 PM, Jim Preston N6VH wrote:


On 9/3/2020 6:29 PM, John L. Broughton wrote:

Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ
--
John L. Broughton
wb9vgj@...
2silverhondas@...
www.wb9vgj.us


John,

Since that is your entire file, and you have been using WSJT-X for several years, then that indicates that something is either re-naming or deleting your previous file. Other wise, that file would have many more entries in it. The only way I know that that could happen, would be if you click on File/Erase wsjtx_log.adi. Since I don't think that is happening, I have no idea what is causing the problem, but I am reasonably certain it is not WSJT-X. I don't think an AV program would pick on that particular file. There must be something on your computer that is causing this.

73,

Jim N6VH





 

 


Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

Reino Talarmo
 

John,

 

At the time 2.9.2020 01:46:00, when you started contact with WB5CXJ, you had no wsjtx_log.adi file for whatever reason.

At the next time you opened WSJT-X (next day) you got that error indication. So at the time error game you had in your computer that wsjtx_log.adi file with the header ending <eh> and nothing was changed at that time or between 2.9.2020 02:44:45.

 

So why you had no wsjtx_log.adi 2.9.2020 at 01:46:00 is the actual question to ask and answer, hi!

 

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of John L. Broughton
Sent: 7. syyskuuta 2020 19:42
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

 

That's what I said below. The file had some contacts in it, but the eoh got changed to eh. I changed it back and all was good.

73,

John, WB9VGJ

On 9/4/2020 4:42 AM, Al Groff via groups.io wrote:

Are you sure that after editing in the eoh, that the .adi file is actually saved with the edit ?
AL, K0VM

On 9/3/2020 8:39 PM, Bill Somerville wrote:

On 04/09/2020 02:29, John L. Broughton wrote:

On 9/3/2020 4:09 PM, Bob Lewis wrote:

It seems to me that if WSJT-x created a new log file with the ???eh??? problem, that log file would be empty or contain only the contacts you have logged since the original log file was deleted. It wouldn???t take an existing log file and just change the eoh to eh. When the new version of WSJT-x came out I simply installed it over the old version. It kept all of my settings and my log file. I never saw the ???eh??? problem because the new WSJT-x has never crated a new log file. I agree, something has to be deleting or renaming the WSJT-x log file, forcing it to create a new one.

??

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Martin G0HDB
Sent: Thursday, September 03, 2020 6:44 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIf header"

??

On Thu, Sep 3, 2020 at 07:49 PM, John L. Broughton wrote:

I have had it happen a few times. The last being last evening when I started the program. For some reason WSTJT-X removes the o in eoh at the end of the header, likely when the program shuts down or starts. Then I have to open the ADIF file and put the o back in.

??

There must be something else in your system that's either deleting or renaming the wsjtx_log.adi file, which results in WSJT-X having to create a new file with the defective header when you start the program.

You need to investigate what's causing your wsjtx_log.adi files to be deleted or renamed rather than 'blaming' the WSJT-X app for what you're experiencing.

--
Martin G0HDB

 

Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ

John,

clearly you have a new WSJT-X ADIF log file there. As with Ed, K6ELE, something has deleted or renamed your WSJT-X ADIF log file.

73
Bill
G4WJS.



 

 

Image removed by sender.

Virus-free. www.avg.com



 

 


Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

John L. Broughton
 

That file contained all the contacts I made in the prior session. When I opened the next session, the eoh had been changed to eh.

My habit is that most every day, I save the wsjx_log.adi to another name and a new file is created the next time I open WSJT-X. I upload the daily files to LoTW and eQSL, import the file to my HRD log (I like it as it is handy for displaying all the essential elements of a QSO when I have to check a QSO for confirmation purposes on QRZ or eQSL), and then import my LoTW log into QRZ. I like to do all that manually rather than logging each contact directly into some other log.

I rely on the running log in JTAlert to flag worked before stations, wanted calls/DX/states, etc.

73,

John, WB9VGJ

On 9/4/2020 1:23 PM, Jim Preston N6VH wrote:

On 9/3/2020 6:29 PM, John L. Broughton wrote:
Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ
--
John L. Broughton
wb9vgj@...
2silverhondas@...
www.wb9vgj.us

John,

Since that is your entire file, and you have been using WSJT-X for several years, then that indicates that something is either re-naming or deleting your previous file. Other wise, that file would have many more entries in it. The only way I know that that could happen, would be if you click on File/Erase wsjtx_log.adi. Since I don't think that is happening, I have no idea what is causing the problem, but I am reasonably certain it is not WSJT-X. I don't think an AV program would pick on that particular file. There must be something on your computer that is causing this.

73,

Jim N6VH





    


Re: FT-847 and SCU-17 Question

Joe Subich, W4TV
 

I'd like to find out if I can use this setup on HF, 6m and VHF using
the data connector on the rear.
No. The PKT connector is valid for only VHF DATA (FM Packet, page 17
of the FT-847 Operating Manual). For HF data (USB/LSB) you need to use the Data In/Out (3.5 mm) connector (AFSK TNC Connections, page 16 of
the FT-847 Operating Manual).

73,

... Joe, W4TV


On 2020-09-07 12:41 PM, John wrote:
Hi,
Is anyone on the list using the FT-847 and a SCU-17 for WSJTX?
I'd like to find out if I can use this setup on HF, 6m and VHF using the data
connector on the rear. Currently using an outboard sound card and the front mike
and audio connectors plus the9pin DB serial for the PTT
Thanks,
John
John Mc Hugh, K4AG
Coordinator for Amateur Radio
National Hurricane Center, WX4NHC
Home page:-http://www.wx4nhc.org
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>


Re: Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIF header"

John L. Broughton
 

That's what I said below. The file had some contacts in it, but the eoh got changed to eh. I changed it back and all was good.

73,

John, WB9VGJ

On 9/4/2020 4:42 AM, Al Groff via groups.io wrote:
Are you sure that after editing in the eoh, that the .adi file is actually saved with the edit ?
AL, K0VM

On 9/3/2020 8:39 PM, Bill Somerville wrote:
On 04/09/2020 02:29, John L. Broughton wrote:
On 9/3/2020 4:09 PM, Bob Lewis wrote:

It seems to me that if WSJT-x created a new log file with the ???eh??? problem, that log file would be empty or contain only the contacts you have logged since the original log file was deleted. It wouldn???t take an existing log file and just change the eoh to eh. When the new version of WSJT-x came out I simply installed it over the old version. It kept all of my settings and my log file. I never saw the ???eh??? problem because the new WSJT-x has never crated a new log file. I agree, something has to be deleting or renaming the WSJT-x log file, forcing it to create a new one.

??

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Martin G0HDB
Sent: Thursday, September 03, 2020 6:44 PM
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] Anyone have this problem on startup? "Error Scanning ADIF Log, invalid ADIf header"

??

On Thu, Sep 3, 2020 at 07:49 PM, John L. Broughton wrote:

I have had it happen a few times. The last being last evening when I started the program. For some reason WSTJT-X removes the o in eoh at the end of the header, likely when the program shuts down or starts. Then I have to open the ADIF file and put the o back in.

??

There must be something else in your system that's either deleting or renaming the wsjtx_log.adi file, which results in WSJT-X having to create a new file with the defective header when you start the program.

You need to investigate what's causing your wsjtx_log.adi files to be deleted or renamed rather than 'blaming' the WSJT-X app for what you're experiencing.

--
Martin G0HDB


Well, I can't imagine any program that would be looking at a WSJT-X file in a WSJT-X directory and going in and removing one letter in the header. If that were the case, I'd expect to have seen it long before now. The few times it has happened has been with my current version, v 2.2.2, and the version before that. I've been using WSJT-X for several years and this is a recent development.

As I said, I had the problem most recently yesterday. I had made a few contacts the day before with no problem. When I opened WSJT-X yesterday, I got the error. Here are the contents of the entire file as it appeared when I opened WSJT-X before I edited it to put the o back in:

WSJT-X ADIF Export<eh>
<call:6>WB5CXJ <gridsquare:4>EM50 <mode:3>FT8 <rst_sent:3>-12 <rst_rcvd:3>+08 <qso_date:8>20200902 <time_on:6>014600 <qso_date_off:8>20200902 <time_off:6>014715 <band:3>20m <freq:9>14.075923 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:4>N5HC <gridsquare:0> <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-09 <qso_date:8>20200902 <time_on:6>022215 <qso_date_off:8>20200902 <time_off:6>022515 <band:3>20m <freq:9>14.074414 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K2FTC <gridsquare:4>EM98 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-06 <qso_date:8>20200902 <time_on:6>022900 <qso_date_off:8>20200902 <time_off:6>022945 <band:3>20m <freq:9>14.076386 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>W4LES <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+16 <rst_rcvd:3>-23 <qso_date:8>20200902 <time_on:6>023115 <qso_date_off:8>20200902 <time_off:6>023345 <band:3>20m <freq:9>14.075990 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>
<call:5>K1SUU <gridsquare:4>EM84 <mode:3>FT8 <rst_sent:3>+08 <rst_rcvd:3>+06 <qso_date:8>20200902 <time_on:6>024400 <qso_date_off:8>20200902 <time_off:6>024445 <band:3>20m <freq:9>14.074871 <station_callsign:6>WB9VGJ <my_gridsquare:4>DM34 <tx_pwr:2>90 <comment:25>TNX for the QSO. 73, John <eor>


73,

John, WB9VGJ

John,

clearly you have a new WSJT-X ADIF log file there. As with Ed, K6ELE, something has deleted or renamed your WSJT-X ADIF log file.

73
Bill
G4WJS.




Virus-free. www.avg.com


    


FT-847 and SCU-17 Question

John
 

Hi,

Is anyone on the list using the FT-847 and a SCU-17 for WSJTX?
I'd like to find out if I can use this setup on HF, 6m and VHF using the data connector on the rear. Currently using an outboard sound card and the front mike and audio connectors plus the9pin DB serial for the PTT

Thanks,
John
John Mc Hugh, K4AG
Coordinator for Amateur Radio  
National Hurricane Center, WX4NHC
Home page:- http://www.wx4nhc.org


Virus-free. www.avg.com


locked Re: Ubuntu 20.04 Compiling From Source #linux

Stan
 

Hello,

Thanks for the reply.. The deb file was not available tor Ubuntu 20.04

With Kari's help I have WSJTX 2.2.2 running.

73, Stan


-----Original Message-----
From: Georgina Joyce <gena@...>
To: main@wsjtx.groups.io <main@WSJTX.groups.io>
Sent: Mon, Sep 7, 2020 11:06 am
Subject: Re: [WSJTX] Ubuntu 20.04 Source

Hello,

I don't have a Ubuntu system running presently.

What I would do is in a terminal:

Get all updates:

apt-get update

apt-get upgrade

apt-cache search libusb-1.0 | less

and observe what packages contain it and install:

apt-get install <package name>

If it doesn't exist you will have to build that from source too. But it is a good idea to let apt pull most of the weight if you can.

I can't remember why you are building from source but is there a bug to be reported? You might be able to get a .deb file from a testing / development  repo. You may have already explored that route.



On 7 Sep 2020, at 15:35, Stan via groups.io <stanka1ze@...> wrote:

Hello,

My first attempt at a build from source. I have done my best to search for an answer but no luck.

My system is Xubuntu 20.04.1 Thank you for any help,

My problem:
-- Building for for: Linux-x86_64
-- ******************************************************
-- Checking for module 'hamlib'
--   Package 'libusb-1.0', required by 'hamlib', not found
-- Found hamlib
CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
  Could NOT find hamlib (missing: hamlib_LIBRARY_DIRS) (Required is at least
  version "3")
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE)
  CMake/Modules/Findhamlib.cmake:88 (find_package_handle_standard_args)
  CMakeLists.txt:875 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/zx20/build/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeOutput.log".
make[2]: *** [CMakeFiles/wsjtx-build.dir/build.make:68: wsjtx-prefix/src/wsjtx-stamp/wsjtx-configure] Error 1
make[1]: *** [CMakeFiles/Makefile2:442: CMakeFiles/wsjtx-build.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

This looks like I need to find libusb-1.0

Thank you ,
Stan, KA1ZE



Georgina


Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS



Re: WSJTX not Decoding + No Transmit Power being sent through radio

Grumpyguy
 

Hi Neil,

Yes, I read that and ordered both the Xiegu -Cable for cat control along with the DigiMod-3.  The cat control is no problem.  Like Al, stated I believe its going to be in the Digimod-3 sound card itself.  

73


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Monday, September 7, 2020 8:57 AM, neil_zampella <neilz@...> wrote:

Is that the Xggcomms Digimode-3 for the Xiegu G90?   Did you see this on that page:

"READ ME - PTT operation. For use with the X5105 and G90 transceivers the PTT needs to be actuated via the CAT commands.  For this, you will need a separate USB CAT interface. If you do not have one, have a look at our USB CAT Interface Xiegu-Cable-1-USB product (in the shop below) which will work alongside this interface. The Xiegu X108G, the PTT can be keyed via the interface built-in Vox circuit.'

Do you have a CAT cable?

Also ... did you read the directions in this PDF about that rig and the Digimode-3?   http://xggcomms.com/userimages/USB-Digimode-3.pdf

Neil, KN3ILZ

On 9/7/2020 10:04 AM, Grumpyguy via groups.io wrote:
Hi Reino,

I'm using DigiMod-3 as my audio interface between the pc and radio.  It was highly recommended and now I'm finding that several people have had  hit and miss success with it.  I will try finding an replacement for it today and give that a try.

73, Derek - N2ZOD


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, September 7, 2020 12:57 AM, Reino Talarmo <reino.talarmo@...> wrote:

Hi Derek,

 

It seems that you don’t have an audio connection between PC and your rig. Rig control is normally independent of that.
How you have connected audio?

 

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Grumpyguy via groups.io
Sent: 7. syyskuuta 2020 8:59
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJTX not Decoding + No Transmit Power being sent through radio

 

Hello Al,

 

Thanks for the reply.  I have tried that that as well and same results.  I even install the WSJT-X on a windows computer without Rig control and got the same exact results.  I really don' t know what is going on.  I'm extremely frustrated at this point to say the least.  

 

Derek

 

 

Sent with ProtonMail Secure Email.

 

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, September 6, 2020 10:55 PM, Al Rusnak via groups.io <arusnak@...> wrote:

 

Derek: 

 

I’m not familiar with the G90, but why don’t you try running WSJTx without the rig control and cat interface software that you identified.  WSJT does all of that.  Suspect your other programs might be blocking  / interfering with the commands from WSJTX.

 

Al, KE6JAC

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Grumpyguy via groups.io
Sent: Sunday, September 6, 2020 1:01 PM
To: main@WSJTX.groups.io
Subject: [WSJTX] WSJTX not Decoding + No Transmit Power being sent through radio

 

I know you have tested the G-90 and I have not only reviewed countless threads and even followed Julians setup for digi mode which is what I'm truly interested in over anything else.  I'm at my wits end with this

I'm using a MacLoggerDX as my rig control and DigiMod-3 as my Cat interface as well as the audio.  My problem is this:

 


 

Only thing I get on WSJT-X is the following screenshot.  Nothing decodes no matter what band I'm on and when I press enable Tx it switches over to the G-90  with no problem and keys it up but when looking at the G-90 it states no wattage or power is going through.  I'm truly at a loss as to what to do and as well who to turn to for help.  I also checked my computer time and it is synced appropriately.  I'm truly ready to give up on this.  I reconnect the Feedline  to the at both ends 3 times thinking may it was not a good connection and still nothing.  I'm using a EmComm III portable antenna.  I have it set up on my side yard, because I want to make sure it works, before I start going portable with it.  Could you please help me if at all possible Thanks....

 

73 

Derek - N2ZOD 

 

 

Sent with ProtonMail Secure Email.

 

 


Attachments:




Re: WSJTX not Decoding + No Transmit Power being sent through radio

neil_zampella
 

Is that the Xggcomms Digimode-3 for the Xiegu G90?   Did you see this on that page:

"READ ME - PTT operation. For use with the X5105 and G90 transceivers the PTT needs to be actuated via the CAT commands.  For this, you will need a separate USB CAT interface. If you do not have one, have a look at our USB CAT Interface Xiegu-Cable-1-USB product (in the shop below) which will work alongside this interface. The Xiegu X108G, the PTT can be keyed via the interface built-in Vox circuit.'

Do you have a CAT cable?

Also ... did you read the directions in this PDF about that rig and the Digimode-3?   http://xggcomms.com/userimages/USB-Digimode-3.pdf

Neil, KN3ILZ

On 9/7/2020 10:04 AM, Grumpyguy via groups.io wrote:
Hi Reino,

I'm using DigiMod-3 as my audio interface between the pc and radio.  It was highly recommended and now I'm finding that several people have had  hit and miss success with it.  I will try finding an replacement for it today and give that a try.

73, Derek - N2ZOD


Sent with ProtonMail Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, September 7, 2020 12:57 AM, Reino Talarmo <reino.talarmo@...> wrote:

Hi Derek,

 

It seems that you don’t have an audio connection between PC and your rig. Rig control is normally independent of that.
How you have connected audio?

 

73, Reino OH3mA

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Grumpyguy via groups.io
Sent: 7. syyskuuta 2020 8:59
To: main@WSJTX.groups.io
Subject: Re: [WSJTX] WSJTX not Decoding + No Transmit Power being sent through radio

 

Hello Al,

 

Thanks for the reply.  I have tried that that as well and same results.  I even install the WSJT-X on a windows computer without Rig control and got the same exact results.  I really don' t know what is going on.  I'm extremely frustrated at this point to say the least.  

 

Derek

 

 

Sent with ProtonMail Secure Email.

 

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On Sunday, September 6, 2020 10:55 PM, Al Rusnak via groups.io <arusnak@...> wrote:

 

Derek: 

 

I’m not familiar with the G90, but why don’t you try running WSJTx without the rig control and cat interface software that you identified.  WSJT does all of that.  Suspect your other programs might be blocking  / interfering with the commands from WSJTX.

 

Al, KE6JAC

 

From: main@WSJTX.groups.io [mailto:main@WSJTX.groups.io] On Behalf Of Grumpyguy via groups.io
Sent: Sunday, September 6, 2020 1:01 PM
To: main@WSJTX.groups.io
Subject: [WSJTX] WSJTX not Decoding + No Transmit Power being sent through radio

 

I know you have tested the G-90 and I have not only reviewed countless threads and even followed Julians setup for digi mode which is what I'm truly interested in over anything else.  I'm at my wits end with this

I'm using a MacLoggerDX as my rig control and DigiMod-3 as my Cat interface as well as the audio.  My problem is this:

 


 

Only thing I get on WSJT-X is the following screenshot.  Nothing decodes no matter what band I'm on and when I press enable Tx it switches over to the G-90  with no problem and keys it up but when looking at the G-90 it states no wattage or power is going through.  I'm truly at a loss as to what to do and as well who to turn to for help.  I also checked my computer time and it is synced appropriately.  I'm truly ready to give up on this.  I reconnect the Feedline  to the at both ends 3 times thinking may it was not a good connection and still nothing.  I'm using a EmComm III portable antenna.  I have it set up on my side yard, because I want to make sure it works, before I start going portable with it.  Could you please help me if at all possible Thanks....

 

73 

Derek - N2ZOD 

 

 

Sent with ProtonMail Secure Email.

 

 


Attachments:



    


Re: Waterfall active but no decodes

DAVID GRIFFITHS
 

Hi Bill
Since my earlier post I have replaced my audio lead with a new one with a mono jack plug either end going from the transceiver ext. speaker socket to my computer. I now find I have no decodes at all by which I mean I was getting a text indicating whether I was transmitting or receiving. But now I am not even getting that. I did notice that whilst doing a monitor I was looking at the radio tab on the settings menu and noticed that whilst transmitting the Test CAT button was showing green and the Test PTT button was showing red. Then when receiving the red PTT button turned off but the green CAT button was still showing green. The transceiver is receiving and transmitting according to the commands of the computer. I really am at a loss as to what I should try next. Any thoughts?
Kind regards
David Griffiths


From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of Bill Somerville <g4wjs@...>
Sent: 03 September 2020 17:39
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Subject: Re: [WSJTX] Waterfall active but no decodes #WSPR
 

[Edited Message Follows]
[Reason: fix typo]

David,
 
did you check the rig menu options I mentioned? Without those you could be on the wrong frequency or sideband while your rig's VFO shows the expected frequency.
 
How is your rig connected to your PC for audio and CAT?
 
73
Bill
G4WJS.
 
On 03/09/2020 17:36, DAVID GRIFFITHS wrote:
Hi Bill
I have run another test paying particular attention to the points you raise. I can also confirm that the computer is changing the radio's frequencies to exactly the right value. But still no decodes. Again, the receiving data is shown on the screen but not the transmitted data. I sat by the rig whilst it went through the sequence. What should I try next?
Kind regards
David Griffiths
 

From: main@WSJTX.groups.io <main@WSJTX.groups.io> on behalf of Bill Somerville <g4wjs@...>
Sent: 03 September 2020 14:44
To: main@WSJTX.groups.io <main@WSJTX.groups.io>
Subject: Re: [WSJTX] Waterfall active but no decodes #WSPR
 
On 03/09/2020 14:16, DAVID GRIFFITHS wrote:

Although I had posted much of the following before I have some more information so I am posting as a new post.

Now that I have downloaded V2.1.2 I am able to band hop which I couldn't do before. I ran WSJTx this afternoon for a couple of hours. I noticed that most of the activity was receiving (44) with only 7 transmits. Is this normal? With one exception there were no decodes.

I am using an FT450 and Windows 10. The serial port is COM 3 and the computer and radio "talk" to one another OK. The blue decode button lights up blue from time to time and I enabled the TX button. I have ticked "prefer type1 messages" and "no own call decodes".

The audio settings are Realtek high definition audio both input and output. I have checked the clock sync  which is spot on to the second. I am puzzled as to why there was only one decode on 40 meters. 

I had set up the schedule for 80,40,20,15 and 10 metres each for Sunrise grey line, Day, Sunset grey line and night.

I have since tried again without band hopping just on 80 metres. Although the waterfall is active I still get no decodes. Interestingly, although the set up was both receiving and transmitting, only the transmissions were shown on the screen, without decodes.
Having looked at other post on the subject I had previously installed V2.2.2 which I had removed to replace with V 2.1.2 to enable band hopping. I don't know if this is relevant but I thought I should mention it. I would be most grateful for any help.
Kind regards
David Griffiths G4PKV

Hi David,

the ratio of transmissions to receptions is set by the "Tx Pct" spin box, note that on scheduled bands with band hopping the exact ratio may not be what you specify.

Is your rig on frequency and on the right sideband? In the rig menu, assuming you are using DATA mode, you need "D DISP (DATA DISP)" as zero, and "D TYPE (DATA MODE)" as USER-U.

73
Bill
G4WJS.

 


locked Re: Ubuntu 20.04 Compiling From Source #linux

Stan
 

Kari,

Scanning dependencies of target install
[100%] Built target install

WSJTX v2.2.2 is now running!!!

Many thanks,
73 Stan KA1ZE



-----Original Message-----
From: Karza <kari.sillanmaki@...>
To: main@WSJTX.groups.io
Sent: Mon, Sep 7, 2020 11:26 am
Subject: Re: [WSJTX] Ubuntu 20.04 Source

Hi Stan,

On 7.9.2020 18.15, Stan via groups.io wrote:
Hi Kari,

That worked, thanks!

next .....
Could not find a package configuration file provided by "Qt5SerialPort"
  with any of the following names:

    Qt5SerialPortConfig.cmake
    qt5serialport-config.cmake
So you are missing more than one package...
Try this somwhat longish command:
"sudo apt install build-essential git cmake gfortran fftw3-dev qtbase5-dev qttools5-dev libqt5serialport5-dev  qtmultimedia5-dev libqt5multimedia5-plugins libqt5sql5-sqlite autoconf automake libtool texinfo libusb-1.0-0-dev libudev-dev"
That should get you everything you need in order to compile WSJT-X.
'Kari


Re: Focus Shift in WSJT-X

Dale Martin, KG5U
 

The checkbox was checked, Jim. I dont recall ever visiting that part of settings before. I did change Misc/Performance/Check QSO log record from 5 seconds to 20 seconds just this morning, but that had nothing to do with keeping W/J on top.

Many thanks, Jim!

73, dale, kg5u

>In JTAlert - Settings-Applications-WSJT-X/JTDX-To Top Options, do you have "Enable bring WSJT-X to Top" checked? If so, uncheck it and see if that helps.

73,

Jim N6VH


locked Re: Ubuntu 20.04 Compiling From Source #linux

Karza
 

Hi Stan,

On 7.9.2020 18.15, Stan via groups.io wrote:
Hi Kari,

That worked, thanks!

next .....
Could not find a package configuration file provided by "Qt5SerialPort"
  with any of the following names:

    Qt5SerialPortConfig.cmake
    qt5serialport-config.cmake

So you are missing more than one package...

Try this somwhat longish command:

"sudo apt install build-essential git cmake gfortran fftw3-dev qtbase5-dev qttools5-dev libqt5serialport5-dev  qtmultimedia5-dev libqt5multimedia5-plugins libqt5sql5-sqlite autoconf automake libtool texinfo libusb-1.0-0-dev libudev-dev"

That should get you everything you need in order to compile WSJT-X.

'Kari


locked Re: Ubuntu 20.04 Compiling From Source #linux

Stan
 

Hi Kari,

That worked, thanks!

next .....
Could not find a package configuration file provided by "Qt5SerialPort"
  with any of the following names:

    Qt5SerialPortConfig.cmake
    qt5serialport-config.cmake

I tried looking for:
Unable to locate package libqt5libserialport5-dev

Stan


-----Original Message-----
From: Karza <kari.sillanmaki@...>
To: main@WSJTX.groups.io
Sent: Mon, Sep 7, 2020 10:57 am
Subject: Re: [WSJTX] Ubuntu 20.04 Source

Hi Stan,

On 7.9.2020 17.35, Stan via groups.io wrote:
Hello,

My first attempt at a build from source. I have done my best to search for an answer but no luck.

My system is Xubuntu 20.04.1 Thank you for any help,

My problem:
-- Building for for: Linux-x86_64
-- ******************************************************
-- Checking for module 'hamlib'
--   Package 'libusb-1.0', required by 'hamlib', not found

please do "sudo apt install libusb-1.0-0-dev" and try again.
73's de Kari, oh2gqc


Re: Focus Shift in WSJT-X

Jim Preston N6VH
 


On 9/7/2020 6:43 AM, Dale Martin wrote:

 

I’ve been running WSJT-X (v2.2.2) with JTAlert (v2.15.3) on a windows 10 computer for some time now and it has worked very well.

 

This morning, I have noticed if I have WSJT-X and JTAlert running and am working in another application (Word, Excel, N1MM, viewing a PDF, etc), the WSJT-X/JTAlert pair will grab the focus from whatever app I’m in. I have not noticed this before and find it very intrusive and disruptive.

 

I haven’t made any changes to settings in either WSJT-X or JTAlert.

 

Can someone advise, please?

 

(FYI: WSJT-X/JTAlert grabbed focus 7…no, 8 times—it happened just now--in the course of my typing this note).

 

73 and thanks in advance for any help,

 

Dale, kg5u


Dale,

I should have added this to my previous message. JTAlert is now up to 2.16.13. You might want to install the new version.

73,

Jim N6VH


Re: Focus Shift in WSJT-X

Jim Preston N6VH
 


On 9/7/2020 6:43 AM, Dale Martin wrote:

 

I’ve been running WSJT-X (v2.2.2) with JTAlert (v2.15.3) on a windows 10 computer for some time now and it has worked very well.

 

This morning, I have noticed if I have WSJT-X and JTAlert running and am working in another application (Word, Excel, N1MM, viewing a PDF, etc), the WSJT-X/JTAlert pair will grab the focus from whatever app I’m in. I have not noticed this before and find it very intrusive and disruptive.

 

I haven’t made any changes to settings in either WSJT-X or JTAlert.

 

Can someone advise, please?

 

(FYI: WSJT-X/JTAlert grabbed focus 7…no, 8 times—it happened just now--in the course of my typing this note).

 

73 and thanks in advance for any help,

 

Dale, kg5u

Dale,

In JTAlert - Settings-Applications-WSJT-X/JTDX-To Top Options, do you have "Enable bring WSJT-X to Top" checked? If so, uncheck it and see if that helps.

73,

Jim N6VH


locked Re: Ubuntu 20.04 Compiling From Source #linux

Georgina Joyce
 

Hello,

I don't have a Ubuntu system running presently.

What I would do is in a terminal:

Get all updates:

apt-get update

apt-get upgrade

apt-cache search libusb-1.0 | less

and observe what packages contain it and install:

apt-get install <package name>

If it doesn't exist you will have to build that from source too. But it is a good idea to let apt pull most of the weight if you can.

I can't remember why you are building from source but is there a bug to be reported? You might be able to get a .deb file from a testing / development  repo. You may have already explored that route.



On 7 Sep 2020, at 15:35, Stan via groups.io <stanka1ze@...> wrote:

Hello,

My first attempt at a build from source. I have done my best to search for an answer but no luck.

My system is Xubuntu 20.04.1 Thank you for any help,

My problem:
-- Building for for: Linux-x86_64
-- ******************************************************
-- Checking for module 'hamlib'
--   Package 'libusb-1.0', required by 'hamlib', not found
-- Found hamlib
CMake Error at /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
  Could NOT find hamlib (missing: hamlib_LIBRARY_DIRS) (Required is at least
  version "3")
Call Stack (most recent call first):
  /usr/share/cmake-3.16/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE)
  CMake/Modules/Findhamlib.cmake:88 (find_package_handle_standard_args)
  CMakeLists.txt:875 (find_package)


-- Configuring incomplete, errors occurred!
See also "/home/zx20/build/build/wsjtx-prefix/src/wsjtx-build/CMakeFiles/CMakeOutput.log".
make[2]: *** [CMakeFiles/wsjtx-build.dir/build.make:68: wsjtx-prefix/src/wsjtx-stamp/wsjtx-configure] Error 1
make[1]: *** [CMakeFiles/Makefile2:442: CMakeFiles/wsjtx-build.dir/all] Error 2
make: *** [Makefile:84: all] Error 2

This looks like I need to find libusb-1.0

Thank you ,
Stan, KA1ZE



Georgina


Call: M0EBP
DMR ID: 2346259
Allstar: 52178
Locater: IO83PS


13221 - 13240 of 29457