Date   

locked WSJT-X 2.5.0 - Raspberry Pi 3B+ - WSPR RX Band hopping - Subprocess Error - Cannot open data file #decode #WSPR #raspberryPi

Roland
 
Edited

Every now and then WSJT-X throws a Subprocess Error while WSPR RX Band hopping on a Rpi 3B+ (Buster).

 



If I click "OK" WSJT-X crashes. If I leave the Error window untouched, WSJT-X continues to run.
Any ideas?

73
Roland


locked Re: VFO B Shifts From 7074 to 7073 On Transmit When Using Split #Cat_RigControl #Yaesu

Kevin Scott Hughes
 

With me, I'm noticing just lately that the TX frequency logged is different than the dial frequency no matter what my VFO uses are (settings are). Is that correct? Thanks, Kevin, K7KSH
 
 

On Wednesday, October 6, 2021, 06:48:07 AM MDT, Philip Rose via groups.io <gm3zza@...> wrote:
 
 

Cliff,

 

The frequency that’s logged is the TX frequency PLUS the audio offset, so the actual frequency of transmission NOT the dial frequency.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Cliff Fox (KU4GW)
Sent: 06 October 2021 10:31
To: Sam W2JDB; main@WSJTX.groups.io Group Moderators
Subject: Re: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

 

Thanks so much for the clarification, Sam. Since that is normal I'm changing the settings back to split operation. I'm wondering which frequency will be saved to the log. I'll find that out in short order. I appreciate this group's patience and advice when it comes to helping newbies to WSJT-X understand how things work when learning a new mode I have barely any experience with at all. The only digital modes I had done up until recently have been Feld-Hell/Hellschreiber, Olivia, MFSK-16, & PSK31. I did help operate the W8H Feld Hell Club Special Event Station from the 62nd Dayton Hamvention in 2013 when it was still being held at Hara Arena before it moved to the Greene County Fairgrounds in Xenia, OH beginning in 2016 with the 65th Dayton Hamvention. I'm sure glad Hamvention wasn't there in 2016, the year the tornado hit Hara Arena! I've been more of a CW operator than anything else in my 25 years in the "world's greatest hobby!" 

 

Very 73!

Cliff, KU4GW

FT8-DMC # 0747

Feld Hell Club Membership # 0062

Proud Member of the ARRL A-1 Operator Club 

(Elected to full membership April 11, 2012).

 

 

 

On Tue, Oct 5, 2021 at 7:37 PM Sam W2JDB <w2jdb@...> wrote:

Hi  Cliff,

 

That is normal operation when using split = rig. It is shifting the frequency so 

that your TX audio is in the middle of the band pass.  

 

FYI, you do not have to press the "VFOA=VFOB" The program will do that for you.


73,  

 

 

Sam W2JDB

 

 

-----Original Message-----
From: Cliff Fox (KU4GW) <cliffku4gw@...>
To: main@WSJTX.groups.io
Sent: Tue, Oct 5, 2021 6:26 pm
Subject: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

I'm having an issue and I don't know why it's happening when operating on FT8 when I use the Split setting under the Settings, Radio tab. I was operating on 40 meters and set VFO A to 7074 kHz in DATA-U mode with AGC off and then pressed VFO A=VFO B  to copy the same settings to VFO B and if I'm transmitting as low as 400-800 Hz audio frequency when the FT-991A transmits it's shifting VFO B to 7073 for some reason. If I were transmitting at 1000 or above I would expect a shift up. I turned split off and chose "Fake It" in the WSJT-X settings because of it doing this. It had not been doing this until this past week it started happening, I'm thinking possibly due to operator error. Can anyone tell me what could be causing the shift on VFO B from 7074 to 7073 when I transmit and what would keep it from doing that when using the split VFO setting? Thanks in advance from a real greenhorn on a new to me mode.

Very 73 de Cliff, KU4GW



 


--
73 Phil GM3ZZA




locked Re: Rig forced to VFO A by WSJT-X #Windows 10 #Cat_RigControl #Windows10 #WSJTX_config

Carl - WC4H
 

I'm with you on this Bob.  Much ado about very little.  Goodness, we can't change the mode from USB-D or DATA-U or whatever to RTTY? 

As far as I can tell, if I use Winwarbler, FLdigi, DM780 or other program for RTTY, I can change the radio mode from the program.  This works with DXlab Commander, FLrig and HRD respectively.  

So, by setting up the radio control program and the RTTY program, one does not even have to change the mode on the radio manually.

73.

Carl - WC4H


locked Re: #Cat_RigControl #IssueReport #stopped_working #Yaesu #Cat_RigControl #IssueReport #Yaesu #Cat_RigControl #IssueReport #Yaesu #stopped_working #Cat_RigControl #IssueReport #stopped_working #Yaesu

d_ziolkowski
 

Lots of RFI issues on the forum, one solution never mentioned is loose PL259 connector. 

I had that happen to me, if only finger tight I find they tend to loosen themselves up over time.

I use a small channel-lock type wrench to snug them up a tad. Never a problem again. 

Thanks Dan KC2STA


On Wed, Oct 6, 2021 at 8:41 AM Sam Birnbaum via groups.io <w2jdb=aol.com@groups.io> wrote:
Well Jim, that lousy choke has worked wonders on multiple 
occasions and.  Won't argue too much about the ferrites, 
sometimes just a simple snap on worked, sometimes
you need multiple ferrites with multiple loops through each one.

I did forget to mention putting ferrites on speaker leads  
that go to the PC as well as on the power lines for the 
speakers. and monitor(s)

I always try the simple/easy stuff first before expending 
any more efforts.

To each their own. 

73,

Sam W2JDB



-----Original Message-----
From: Jim Brown <k9yc@...>
To: main@WSJTX.groups.io
Sent: Wed, Oct 6, 2021 12:16 am
Subject: Re: [WSJTX] #Cat_RigControl #IssueReport #protocol #stopped_working #Yaesu

On 10/5/2021 6:04 PM, John wrote:

> This is called a counterpoise.


While a counterpoise is an important part of most end-fed antennas, it
is NOT a substitute for proper grounding and bonding. It is something
that can be done IN ADDITION TO proper grounding bonding.

On 10/5/2021 7:09 PM, Sam Birnbaum via groups.io wrote:

> You might also want to connect (if possible) the chassis of the PC, ==
> FT817 and Amp to a single buss bar.

This is part of proper grounding and bonding, and it's the only part of
Sam's advice with which I agree. A coil of coax is a lousy choke, and
clamp-on ferrites for HF must be Fair-Rite #31, with multiple turns
wound through them to do much useful.

73, Jim K9YC













--
Dan Ziolkowski KC2STA
SKCC #4290T
Ubuntu LINUX


locked Re: worked before status #macOS

John Wiener
 

I did. Another file?


locked Re: worked before status #macOS

Dave Garber
 

Did you rename the rumlog to
wsjtx_log.adi.    and what about the other log file...

I forget the name of it.   Not sure which is rescanned.  

On Wed., Oct. 6, 2021, 11:23 a.m. John Wiener, <jawodms@...> wrote:
Thanks Doug
I copied (or perhaps moved and renamed by mistake) the rumlog adi file to the same directory as the original wsjtx_log.adi
and renamed the old one.  The old one had all the qsos from this year only.  I thought the rumlog would be complete...now I see ZERO worked-before when I rescan ADIF log.  However in Band Activity, I still see blue highlighting on new calls.  How can that be?
Should I just start over?  did I lose my >10 years of logging?  



locked Re: worked before status #macOS

John Wiener
 

I've read it several times.  it just isn't behaving as the manual says.  


locked Re: WSJT-X will not work with some Yaesu Radios using the Raspberry Pi due to HAMLIB incompatibility... #Yaesu #WSJTX_config #raspberryPi #linux

Michael Black
 

Is Menu 030 the same on both rigs?  Looks like they should behave the same.

You can test this yourself -- adjust com port and baud rate to suit.  See if the antenna selection follows the band change.

rigctl -m 1037 -r /dev/ttyS0 -s 9600

Rig command: w BSX;
Where the X is the band
Inline image

Hopefully there's no error shown (like ?) but you will see a timeout occur as there should be no response to this command.

Mike W9MDB

On Wednesday, October 6, 2021, 12:20:33 AM CDT, John <ve3kkqve3kkq@...> wrote:


For roughly the last year I have been only on FT8. It has only been in the last few months that I put up an end fed half wave, that is when the antenna selection problem started.
So I don't see how Band Stacking has much to do with it as I said, I have only been running FT8, nothing else.
If it were band stacking, then why does the FTdx-5000 selection work yet the FTdx-3000 not, doesn't the FTdx-5000 have Band Stacking?

John
VE7KKQ

On Tue, Oct 5, 2021 at 9:05 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Read up on Menu 031 for the Band/Stack option and elsewhere in the manual about band stack.
I think you probably want the Band option.
You should be able to set up the band and press the band button to put it in the band stack.
WSJT-X should be sending a BS band stack command so should be remembering the antenna if it's put in the band stack correctly.

Mike W9MDB




On Tuesday, October 5, 2021, 07:59:56 PM CDT, John <ve3kkqve3kkq@...> wrote:


I have problems with WSJT-X and the FTdx-3000 rig in that my antennas (two) don't get selected as the bands change.

Someone involved with HamLab was helping by sending me a file to include in WSJT-X that would record what was going on. I sent these files as requested several times and suddenly the person "helping" stopped communicating.

So, I now use the FTdx-5000 as my rig as I did before I reported my problem and have no issues.

Hope you get better support than I did.

John
VE7KKQ

On Tue, Oct 5, 2021 at 4:06 PM <regiogringo@...> wrote:

[Edited Message Follows]

Bill,

I agree that it's an issue of Rig control...

There are three tabs that need to be setup, "GENERAL," where call letters and grid square are entered, then the "RIG" section, which should contain the model number of the rig you intend to use, then there is the "AUDIO" tab section, which contains various selections.  If I am conflating Rig Control with Audio, it's because WSJT-X labels the third tab in setup as "AUDIO.  I don't know why they call the third tab "Audio," but that's what WSJT-X calls it, and that's why I refer to it as such, so the reader will know which tab I'm referring to.

So, when exclusively using WSJT-X as rig control, I enter my Rig's model number, under "RIG," and then I enter any of the selections offered under the "AUDIO" tab, which then yields the HAMLIB error message.

The model number for my rig is elementary, a Yaesu FT-991, and that's what I have entered.  I've also tried each and every selection under the "AUDIO" tab,  and I get the HAMLIB error message ("AUDIO" is their term for the tab, not mine). 

When I setup WSJT-X using FLRiG as rig control , the Yaesu (Silicon Labs) USB drivers show up under the tab entitled "AUDIO," but I have to select FLRIG under the tab entitled "RIG," and not the actual Rig's model number.  I also have to fire FLRIG first, before I fire WSJT-X, in order for WSJT-X to work. But, under this scenario, I do NOT get a HAMLIB error message, and WSJT-X works perfectly. 

So, yes, it's a matter of Rig Control, evidenced by my having to select FLRIG first as RIG Control under the tab entitled "RIG," rather than specifying my rig's actual model number under the "RIG" tab. When I select FLRIG as my rig model number under the WSJT-X "RIG" tab, and the Yaesu (Silicon Labs) USB drivers show up to be selected under the "AUDIO" tab, that suggests to me that there may be a USB driver issue as well, since the Yaesu (Silicon Labs) USB drivers do not show up for selection if I setup things solely using WSJT-X as rig control.

I can only report what I'm experiencing, and I have no comprehension as to why I'm getting these HAMLIB error messages, or why WSJT-X won't work when I designate my rig model number for rig control, and select what WSJT-X provides under their "AUDIO" tab to select from. 

Thank you!

Randy
KG0BA
73












locked Re: WSJT-X will not work with some Yaesu Radios using the Raspberry Pi due to HAMLIB incompatibility... #Yaesu #WSJTX_config #raspberryPi #linux

RichW6BOT
 

As Bill indicated, no special drivers installed.

Here are my settings in WSJT-X for the 991A, hope it helps:









locked Re: worked before status #macOS

John Wiener
 

Thanks Doug
I copied (or perhaps moved and renamed by mistake) the rumlog adi file to the same directory as the original wsjtx_log.adi
and renamed the old one.  The old one had all the qsos from this year only.  I thought the rumlog would be complete...now I see ZERO worked-before when I rescan ADIF log.  However in Band Activity, I still see blue highlighting on new calls.  How can that be?
Should I just start over?  did I lose my >10 years of logging?  


locked Re: VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

 

Cliff,

 

The frequency that’s logged is the TX frequency PLUS the audio offset, so the actual frequency of transmission NOT the dial frequency.

 

73 Phil GM3ZZA

 

Sent from Mail for Windows

 

From: Cliff Fox (KU4GW)
Sent: 06 October 2021 10:31
To: Sam W2JDB; main@WSJTX.groups.io Group Moderators
Subject: Re: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

 

Thanks so much for the clarification, Sam. Since that is normal I'm changing the settings back to split operation. I'm wondering which frequency will be saved to the log. I'll find that out in short order. I appreciate this group's patience and advice when it comes to helping newbies to WSJT-X understand how things work when learning a new mode I have barely any experience with at all. The only digital modes I had done up until recently have been Feld-Hell/Hellschreiber, Olivia, MFSK-16, & PSK31. I did help operate the W8H Feld Hell Club Special Event Station from the 62nd Dayton Hamvention in 2013 when it was still being held at Hara Arena before it moved to the Greene County Fairgrounds in Xenia, OH beginning in 2016 with the 65th Dayton Hamvention. I'm sure glad Hamvention wasn't there in 2016, the year the tornado hit Hara Arena! I've been more of a CW operator than anything else in my 25 years in the "world's greatest hobby!" 

 

Very 73!

Cliff, KU4GW

FT8-DMC # 0747

Feld Hell Club Membership # 0062

Proud Member of the ARRL A-1 Operator Club 

(Elected to full membership April 11, 2012).

 

 

 

On Tue, Oct 5, 2021 at 7:37 PM Sam W2JDB <w2jdb@...> wrote:

Hi  Cliff,

 

That is normal operation when using split = rig. It is shifting the frequency so 

that your TX audio is in the middle of the band pass.  

 

FYI, you do not have to press the "VFOA=VFOB" The program will do that for you.


73,  

 

 

Sam W2JDB

 

 

-----Original Message-----
From: Cliff Fox (KU4GW) <cliffku4gw@...>
To: main@WSJTX.groups.io
Sent: Tue, Oct 5, 2021 6:26 pm
Subject: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

I'm having an issue and I don't know why it's happening when operating on FT8 when I use the Split setting under the Settings, Radio tab. I was operating on 40 meters and set VFO A to 7074 kHz in DATA-U mode with AGC off and then pressed VFO A=VFO B  to copy the same settings to VFO B and if I'm transmitting as low as 400-800 Hz audio frequency when the FT-991A transmits it's shifting VFO B to 7073 for some reason. If I were transmitting at 1000 or above I would expect a shift up. I turned split off and chose "Fake It" in the WSJT-X settings because of it doing this. It had not been doing this until this past week it started happening, I'm thinking possibly due to operator error. Can anyone tell me what could be causing the shift on VFO B from 7074 to 7073 when I transmit and what would keep it from doing that when using the split VFO setting? Thanks in advance from a real greenhorn on a new to me mode.

Very 73 de Cliff, KU4GW



 


--
73 Phil GM3ZZA


locked Feature Request #mainscreen

Pete Ritter K5CPR
 

I'd like to see the default frequencies displayed in a distinct font in the band drop-down list, perhaps bold. This would help to identify the defaults when one has added frequencies for DXpeditions, for example. 


locked Re: VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

Cliff Fox (KU4GW)
 

Thanks so much for the clarification, Sam. Since that is normal I'm changing the settings back to split operation. I'm wondering which frequency will be saved to the log. I'll find that out in short order. I appreciate this group's patience and advice when it comes to helping newbies to WSJT-X understand how things work when learning a new mode I have barely any experience with at all. The only digital modes I had done up until recently have been Feld-Hell/Hellschreiber, Olivia, MFSK-16, & PSK31. I did help operate the W8H Feld Hell Club Special Event Station from the 62nd Dayton Hamvention in 2013 when it was still being held at Hara Arena before it moved to the Greene County Fairgrounds in Xenia, OH beginning in 2016 with the 65th Dayton Hamvention. I'm sure glad Hamvention wasn't there in 2016, the year the tornado hit Hara Arena! I've been more of a CW operator than anything else in my 25 years in the "world's greatest hobby!" 

Very 73!
Cliff, KU4GW
FT8-DMC # 0747
Feld Hell Club Membership # 0062
Proud Member of the ARRL A-1 Operator Club 
(Elected to full membership April 11, 2012).

 

On Tue, Oct 5, 2021 at 7:37 PM Sam W2JDB <w2jdb@...> wrote:
Hi  Cliff,

That is normal operation when using split = rig. It is shifting the frequency so 
that your TX audio is in the middle of the band pass.  

FYI, you do not have to press the "VFOA=VFOB" The program will do that for you.

73,  


Sam W2JDB



-----Original Message-----
From: Cliff Fox (KU4GW) <cliffku4gw@...>
To: main@WSJTX.groups.io
Sent: Tue, Oct 5, 2021 6:26 pm
Subject: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

I'm having an issue and I don't know why it's happening when operating on FT8 when I use the Split setting under the Settings, Radio tab. I was operating on 40 meters and set VFO A to 7074 kHz in DATA-U mode with AGC off and then pressed VFO A=VFO B  to copy the same settings to VFO B and if I'm transmitting as low as 400-800 Hz audio frequency when the FT-991A transmits it's shifting VFO B to 7073 for some reason. If I were transmitting at 1000 or above I would expect a shift up. I turned split off and chose "Fake It" in the WSJT-X settings because of it doing this. It had not been doing this until this past week it started happening, I'm thinking possibly due to operator error. Can anyone tell me what could be causing the shift on VFO B from 7074 to 7073 when I transmit and what would keep it from doing that when using the split VFO setting? Thanks in advance from a real greenhorn on a new to me mode.

Very 73 de 
Cliff, KU4GW





locked Re: WSJT-X will not work with some Yaesu Radios using the Raspberry Pi due to HAMLIB incompatibility... #Yaesu #WSJTX_config #raspberryPi #linux

John
 

For roughly the last year I have been only on FT8. It has only been in the last few months that I put up an end fed half wave, that is when the antenna selection problem started.
So I don't see how Band Stacking has much to do with it as I said, I have only been running FT8, nothing else.
If it were band stacking, then why does the FTdx-5000 selection work yet the FTdx-3000 not, doesn't the FTdx-5000 have Band Stacking?

John
VE7KKQ


On Tue, Oct 5, 2021 at 9:05 PM Michael Black via groups.io <mdblack98=yahoo.com@groups.io> wrote:
Read up on Menu 031 for the Band/Stack option and elsewhere in the manual about band stack.
I think you probably want the Band option.
You should be able to set up the band and press the band button to put it in the band stack.
WSJT-X should be sending a BS band stack command so should be remembering the antenna if it's put in the band stack correctly.

Mike W9MDB




On Tuesday, October 5, 2021, 07:59:56 PM CDT, John <ve3kkqve3kkq@...> wrote:


I have problems with WSJT-X and the FTdx-3000 rig in that my antennas (two) don't get selected as the bands change.

Someone involved with HamLab was helping by sending me a file to include in WSJT-X that would record what was going on. I sent these files as requested several times and suddenly the person "helping" stopped communicating.

So, I now use the FTdx-5000 as my rig as I did before I reported my problem and have no issues.

Hope you get better support than I did.

John
VE7KKQ

On Tue, Oct 5, 2021 at 4:06 PM <regiogringo@...> wrote:

[Edited Message Follows]

Bill,

I agree that it's an issue of Rig control...

There are three tabs that need to be setup, "GENERAL," where call letters and grid square are entered, then the "RIG" section, which should contain the model number of the rig you intend to use, then there is the "AUDIO" tab section, which contains various selections.  If I am conflating Rig Control with Audio, it's because WSJT-X labels the third tab in setup as "AUDIO.  I don't know why they call the third tab "Audio," but that's what WSJT-X calls it, and that's why I refer to it as such, so the reader will know which tab I'm referring to.

So, when exclusively using WSJT-X as rig control, I enter my Rig's model number, under "RIG," and then I enter any of the selections offered under the "AUDIO" tab, which then yields the HAMLIB error message.

The model number for my rig is elementary, a Yaesu FT-991, and that's what I have entered.  I've also tried each and every selection under the "AUDIO" tab,  and I get the HAMLIB error message ("AUDIO" is their term for the tab, not mine). 

When I setup WSJT-X using FLRiG as rig control , the Yaesu (Silicon Labs) USB drivers show up under the tab entitled "AUDIO," but I have to select FLRIG under the tab entitled "RIG," and not the actual Rig's model number.  I also have to fire FLRIG first, before I fire WSJT-X, in order for WSJT-X to work. But, under this scenario, I do NOT get a HAMLIB error message, and WSJT-X works perfectly. 

So, yes, it's a matter of Rig Control, evidenced by my having to select FLRIG first as RIG Control under the tab entitled "RIG," rather than specifying my rig's actual model number under the "RIG" tab. When I select FLRIG as my rig model number under the WSJT-X "RIG" tab, and the Yaesu (Silicon Labs) USB drivers show up to be selected under the "AUDIO" tab, that suggests to me that there may be a USB driver issue as well, since the Yaesu (Silicon Labs) USB drivers do not show up for selection if I setup things solely using WSJT-X as rig control.

I can only report what I'm experiencing, and I have no comprehension as to why I'm getting these HAMLIB error messages, or why WSJT-X won't work when I designate my rig model number for rig control, and select what WSJT-X provides under their "AUDIO" tab to select from. 

Thank you!

Randy
KG0BA
73









locked Re: VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

Michael Black
 

To be a little more descriptive....

In order to avoid harmonics and bandwidth limitations Rig Split and Fake It both adjust the transmit frequency so that your audio is maintained in the 1500-2000Hz range in 500Hz segments.
One major advantage is when you see somebody calling above 2500 offset you can go up there with them even if your transmit bandwidth is less than 2500Hz as your audio will still be 1500-2000Hz -- well within your bandpass.

So as you go below 1500 offset your transmit frequency will go down 500Hz so that your audio is still 1500Hz above the suppressed carrier frequency.  Above 1999 frequency will go up.

Example:
14074000 with offset of 1500
14073500 with offset of 1000
14073000 with offset of 500
14072500 with offset < 500
14074500 with offset of 2000
14075000 with offset of 2500

Mike W9MDB



On Tuesday, October 5, 2021, 06:37:19 PM CDT, Sam Birnbaum via groups.io <w2jdb@...> wrote:


Hi  Cliff,

That is normal operation when using split = rig. It is shifting the frequency so 
that your TX audio is in the middle of the band pass.  

FYI, you do not have to press the "VFOA=VFOB" The program will do that for you.

73,  


Sam W2JDB



-----Original Message-----
From: Cliff Fox (KU4GW) <cliffku4gw@...>
To: main@WSJTX.groups.io
Sent: Tue, Oct 5, 2021 6:26 pm
Subject: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

I'm having an issue and I don't know why it's happening when operating on FT8 when I use the Split setting under the Settings, Radio tab. I was operating on 40 meters and set VFO A to 7074 kHz in DATA-U mode with AGC off and then pressed VFO A=VFO B  to copy the same settings to VFO B and if I'm transmitting as low as 400-800 Hz audio frequency when the FT-991A transmits it's shifting VFO B to 7073 for some reason. If I were transmitting at 1000 or above I would expect a shift up. I turned split off and chose "Fake It" in the WSJT-X settings because of it doing this. It had not been doing this until this past week it started happening, I'm thinking possibly due to operator error. Can anyone tell me what could be causing the shift on VFO B from 7074 to 7073 when I transmit and what would keep it from doing that when using the split VFO setting? Thanks in advance from a real greenhorn on a new to me mode.

Very 73 de 
Cliff, KU4GW








locked Re: WSJT-X will not work with some Yaesu Radios using the Raspberry Pi due to HAMLIB incompatibility... #Yaesu #WSJTX_config #raspberryPi #linux

Michael Black
 

Read up on Menu 031 for the Band/Stack option and elsewhere in the manual about band stack.
I think you probably want the Band option.
You should be able to set up the band and press the band button to put it in the band stack.
WSJT-X should be sending a BS band stack command so should be remembering the antenna if it's put in the band stack correctly.

Mike W9MDB




On Tuesday, October 5, 2021, 07:59:56 PM CDT, John <ve3kkqve3kkq@...> wrote:


I have problems with WSJT-X and the FTdx-3000 rig in that my antennas (two) don't get selected as the bands change.

Someone involved with HamLab was helping by sending me a file to include in WSJT-X that would record what was going on. I sent these files as requested several times and suddenly the person "helping" stopped communicating.

So, I now use the FTdx-5000 as my rig as I did before I reported my problem and have no issues.

Hope you get better support than I did.

John
VE7KKQ

On Tue, Oct 5, 2021 at 4:06 PM <regiogringo@...> wrote:

[Edited Message Follows]

Bill,

I agree that it's an issue of Rig control...

There are three tabs that need to be setup, "GENERAL," where call letters and grid square are entered, then the "RIG" section, which should contain the model number of the rig you intend to use, then there is the "AUDIO" tab section, which contains various selections.  If I am conflating Rig Control with Audio, it's because WSJT-X labels the third tab in setup as "AUDIO.  I don't know why they call the third tab "Audio," but that's what WSJT-X calls it, and that's why I refer to it as such, so the reader will know which tab I'm referring to.

So, when exclusively using WSJT-X as rig control, I enter my Rig's model number, under "RIG," and then I enter any of the selections offered under the "AUDIO" tab, which then yields the HAMLIB error message.

The model number for my rig is elementary, a Yaesu FT-991, and that's what I have entered.  I've also tried each and every selection under the "AUDIO" tab,  and I get the HAMLIB error message ("AUDIO" is their term for the tab, not mine). 

When I setup WSJT-X using FLRiG as rig control , the Yaesu (Silicon Labs) USB drivers show up under the tab entitled "AUDIO," but I have to select FLRIG under the tab entitled "RIG," and not the actual Rig's model number.  I also have to fire FLRIG first, before I fire WSJT-X, in order for WSJT-X to work. But, under this scenario, I do NOT get a HAMLIB error message, and WSJT-X works perfectly. 

So, yes, it's a matter of Rig Control, evidenced by my having to select FLRIG first as RIG Control under the tab entitled "RIG," rather than specifying my rig's actual model number under the "RIG" tab. When I select FLRIG as my rig model number under the WSJT-X "RIG" tab, and the Yaesu (Silicon Labs) USB drivers show up to be selected under the "AUDIO" tab, that suggests to me that there may be a USB driver issue as well, since the Yaesu (Silicon Labs) USB drivers do not show up for selection if I setup things solely using WSJT-X as rig control.

I can only report what I'm experiencing, and I have no comprehension as to why I'm getting these HAMLIB error messages, or why WSJT-X won't work when I designate my rig model number for rig control, and select what WSJT-X provides under their "AUDIO" tab to select from. 

Thank you!

Randy
KG0BA
73






locked Re: Possible bug with tune button on 2.5.0 GA #IssueReport #Yaesu #Cat_RigControl #transmit

Jason B
 

Alright, problem solved. Big thanks to Mike for the debugging. Turns out it was a failure between the PC and the id10t interface, aka dying mouse. Clicked on the poor fellas left ear one too many times and it started bouncing, just coincidentally happened after my upgrade to 2.5.0 so I thought it was the software. Turns out it's dead mice. 73 to all! 


locked Re: WSJT-X will not work with some Yaesu Radios using the Raspberry Pi due to HAMLIB incompatibility... #Yaesu #WSJTX_config #raspberryPi #linux

John
 

I have problems with WSJT-X and the FTdx-3000 rig in that my antennas (two) don't get selected as the bands change.

Someone involved with HamLab was helping by sending me a file to include in WSJT-X that would record what was going on. I sent these files as requested several times and suddenly the person "helping" stopped communicating.

So, I now use the FTdx-5000 as my rig as I did before I reported my problem and have no issues.

Hope you get better support than I did.

John
VE7KKQ


On Tue, Oct 5, 2021 at 4:06 PM <regiogringo@...> wrote:

[Edited Message Follows]

Bill,

I agree that it's an issue of Rig control...

There are three tabs that need to be setup, "GENERAL," where call letters and grid square are entered, then the "RIG" section, which should contain the model number of the rig you intend to use, then there is the "AUDIO" tab section, which contains various selections.  If I am conflating Rig Control with Audio, it's because WSJT-X labels the third tab in setup as "AUDIO.  I don't know why they call the third tab "Audio," but that's what WSJT-X calls it, and that's why I refer to it as such, so the reader will know which tab I'm referring to.

So, when exclusively using WSJT-X as rig control, I enter my Rig's model number, under "RIG," and then I enter any of the selections offered under the "AUDIO" tab, which then yields the HAMLIB error message.

The model number for my rig is elementary, a Yaesu FT-991, and that's what I have entered.  I've also tried each and every selection under the "AUDIO" tab,  and I get the HAMLIB error message ("AUDIO" is their term for the tab, not mine). 

When I setup WSJT-X using FLRiG as rig control , the Yaesu (Silicon Labs) USB drivers show up under the tab entitled "AUDIO," but I have to select FLRIG under the tab entitled "RIG," and not the actual Rig's model number.  I also have to fire FLRIG first, before I fire WSJT-X, in order for WSJT-X to work. But, under this scenario, I do NOT get a HAMLIB error message, and WSJT-X works perfectly. 

So, yes, it's a matter of Rig Control, evidenced by my having to select FLRIG first as RIG Control under the tab entitled "RIG," rather than specifying my rig's actual model number under the "RIG" tab. When I select FLRIG as my rig model number under the WSJT-X "RIG" tab, and the Yaesu (Silicon Labs) USB drivers show up to be selected under the "AUDIO" tab, that suggests to me that there may be a USB driver issue as well, since the Yaesu (Silicon Labs) USB drivers do not show up for selection if I setup things solely using WSJT-X as rig control.

I can only report what I'm experiencing, and I have no comprehension as to why I'm getting these HAMLIB error messages, or why WSJT-X won't work when I designate my rig model number for rig control, and select what WSJT-X provides under their "AUDIO" tab to select from. 

Thank you!

Randy
KG0BA
73



locked Re: VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

Sam Birnbaum
 

Hi  Cliff,

That is normal operation when using split = rig. It is shifting the frequency so 
that your TX audio is in the middle of the band pass.  

FYI, you do not have to press the "VFOA=VFOB" The program will do that for you.

73,  


Sam W2JDB



-----Original Message-----
From: Cliff Fox (KU4GW) <cliffku4gw@...>
To: main@WSJTX.groups.io
Sent: Tue, Oct 5, 2021 6:26 pm
Subject: [WSJTX] VFO B Shifts From 7074 to 7073 On Transmit When Using Split On Yaesu FT-991A? #Cat_RigControl

I'm having an issue and I don't know why it's happening when operating on FT8 when I use the Split setting under the Settings, Radio tab. I was operating on 40 meters and set VFO A to 7074 kHz in DATA-U mode with AGC off and then pressed VFO A=VFO B  to copy the same settings to VFO B and if I'm transmitting as low as 400-800 Hz audio frequency when the FT-991A transmits it's shifting VFO B to 7073 for some reason. If I were transmitting at 1000 or above I would expect a shift up. I turned split off and chose "Fake It" in the WSJT-X settings because of it doing this. It had not been doing this until this past week it started happening, I'm thinking possibly due to operator error. Can anyone tell me what could be causing the shift on VFO B from 7074 to 7073 when I transmit and what would keep it from doing that when using the split VFO setting? Thanks in advance from a real greenhorn on a new to me mode.

Very 73 de 
Cliff, KU4GW





locked Re: WSJTX 2.5.0 MacOSX Issues: Memory Issue and Transmit Issue #macOS

Ted Asmus
 

Bill,

Thank you. Exactly the hint I needed and WSJT-X is running flawlessly. Now to figure out the Icom-7300 issue.

Best,

Ted
K8UKE

On Oct 5, 2021, at 1:49 PM, Bill Somerville <g4wjs@classdesign.com> wrote:

On 05/10/2021 18:26, Ted Asmus wrote:
I installed WSJTX 2.5.0 on my Mac running High Sierra 10.13.6 and followed the ReadMe.txt file to install the com.wsjtx.syscti.plist file. It worked perfectly EXCEPT I do not seem to be able to transmit through my Icom-7300.

Just for fun, I downloaded jtdx version 2.2 for my Mac and followed its ReadMe.txt file that changes the memory size down from a shmmax of 52428800 that occurred with the WSJTX 2.5.0 instructions to a shmmax of 14680064. jtdx ran and I received a lot of FT8 CQs. But when I double clicked on a CQ, jtdx would crash.

So, I went back to the downloaded WSJTX 2.5.0 dmg file that previously ran, reread the ReadMe.txt and followed the instructions to change the shmmax back to 52428800. The shmmax does not change from 14680064. Yes, I rebooted every time. Not just a restart, but a complete shut-down and reboot. Of course, I get the dreaded memory error when I try to run WSJTX.

I would appreciate any help in getting (1) WSJTX 2.5.0 back running again and (2) getting some hints on how to get my Icom-7300 transmitting from WSJTX.

By the way, I think this software is amazing!

Thanks for any advice you can provide,

Ted Asmus
K8UKE
Hi Ted,

WSJT-X will not start on macOS unless the shared memory parameters are set correctly, so that is nothing to do with your Tx issue. If you are seeing the old lower value of the shared memory size then delete the /etc/sysctl.conf used by the prior method. Note there is a typo in your plist file name above, it is com.wsjtx.sysctl.plist .

73
Bill
G4WJS.



5181 - 5200 of 34180