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


Jason B
 

Hey y'all, I'm running a Dell Optiplex, Windows 8.1, WSJT 2.5.0 to a FT1000MP and when I try to click on the tune button I have to click on it several times before it will stay transmitting. It will key in the software then immediately drop out. Any idea what's going on?


Michael Black
 


Are you in Rig Split, Fake It, or None?
If Rig Split try one of the others and see if it behaves.

Mike W9MDB



On Thursday, September 30, 2021, 01:24:45 PM CDT, Jason B <sydbowen@...> wrote:


Hey y'all, I'm running a Dell Optiplex, Windows 8.1, WSJT 2.5.0 to a FT1000MP and when I try to click on the tune button I have to click on it several times before it will stay transmitting. It will key in the software then immediately drop out. Any idea what's going on?




Jason B
 

I think I'm in fake it because the rig split wouldn't work correctly with the FT1000MP. Not at home at the moment, will update after I get home. 


Jason B
 

I'm on fake it. Rig split doesn't work with the FT1000MP. It doesn't consistently mess up when I hit the tune button, only a few times it will key the transmitter then drop out of tune, then the third or so time it stays on like it's supposed to.


George J Molnar, KF2T
 

I've noticed a similar problem. Running the "Pwr" slider down and up seems to remedy it for the session. 


Jeff Townsend
 

It must be a dirty virtual slider pot. Get out the virtual contact cleaner George and give it a spray. 
<Grin>


On Oct 1, 2021, at 7:23 PM, George J Molnar, KF2T <george@...> wrote:

I've noticed a similar problem. Running the "Pwr" slider down and up seems to remedy it for the session. 



Jeff Townsend
WB8LYJ





Reino Talarmo
 

>I've noticed a similar problem. Running the "Pwr" slider down and up seems to remedy it for the session. 

 

Hi Jason,

Have you tested possible RFI? Turning down power or using dummy load?

73, Reino OH3mA

 


Jason B
 

No problem with regular transmissions, only with the tune button. Everything else seems to work fine except for every once in a while for some reason when I click to log a QSO it starts trying to contact someone else.


Jason B
 
Edited

I'll try that Jeff. It's the special formula W1ND3x right?


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!