Re: [wsjt-devel] Hamlib error with GA release

2020-06-03 Thread Black Michael via wsjt-devel
I just pushed a commit that has a new dummy device without set_vfo or get_vfo. I was able to patch it to work with this situation so this should apply to any older Icom rigs and Yaesu rigs that don't have set_vfo capability and/or get_vfo capability. I'm still waiting for my tester to get a curre

Re: [wsjt-devel] Hamlib error with GA release

2020-06-03 Thread Bill Somerville
Hi Mike, thanks for chasing this down. I have some confusion whether there are two issues, one with direct rig control and another when using rigctld. I would be good to test both, let me know if a test version of WSJT-X is needed with your patch for any platform required? Although in this cas

Re: [wsjt-devel] Hamlib error with GA release

2020-06-03 Thread Black Michael via wsjt-devel
I've got a patched version that I sent to one of the testers On Wednesday, June 3, 2020, 06:26:20 AM CDT, Bill Somerville wrote: Mike, I believe it is quite reasonable to implement rig_get_vfo for the FT-891, FT991, and similar. In this case it may be that a implementation

Re: [wsjt-devel] Hamlib error with GA release

2020-06-03 Thread Bill Somerville
Mike, I believe it is quite reasonable to implement rig_get_vfo for the FT-891, FT991, and similar. In this case it may be that a implementation that always returns VFO A is correct as I don't believe these rigs use VFO B for anything other than SPLIT Tx transmit frequency. That aside, what i

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Black Michael via wsjt-devel
The FT-991 is one that doesn't have the ability to query which VFO is active and doesn't have the ability to query "current VFO" either. Since we allow currVFO to pass through to the Icoms it's also now passing through to all rigs.   So it seems the only choice here would be to set the current VF

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Bill Somerville
Mike, OK, WSJT-X checks for both of those return codes when it makes its first attempt to get the current VFO. So Hamlib must not lie about that capability and return a success status, otherwise WSJT-X continue on the basis that rig_get_vfo() works for the current rig. Is this error because

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Black Michael via wsjt-devel
Don't know for sure...but it's been that way since version 3.3 As the error codes say in rig.h     RIG_ENIMPL,     /*!< 4 function not implemented, but will be */     RIG_ENAVAIL,    /*!< 11 Function not available */ On Tuesday, June 2, 2020, 05:35:42 PM CDT, Bill Somerville wrote:

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Gary Rogers
gt; To: WSJT software development > Subject: Re: [wsjt-devel] Hamlib error with GA release > > Folks, > > I am observing the same issue on Windows 10 (pre 2001 release) with the > FT-991 here but also on a FT-897D using a CT-17. > > I have also noted the same issues in

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Bill Somerville
Mike, don't do that, the whole point of that query is to find out if the rig can be queried for the current VFO, the result determines how the rig is handled via the Hamlib API. Hamlib should return "not implemented", why is an "invalid parameter" error being returned? 73 Bill G4WJS. On 02/

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Bill Somerville
@lists.sourceforge.net] *Gesendet:* Dienstag, 2. Juni 2020 21:21 *An:* 'WSJT software development' *Cc:* Black Michael *Betreff:* Re: [wsjt-devel] Hamlib error with GA release I need one of the Yaesu owners to follow the directions in this youtube video and send me their debug.txt file. https://www.y

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread DG2YCB, Uwe
wsjt-devel] Hamlib error with GA release I need one of the Yaesu owners to follow the directions in this youtube video and send me their debug.txt file. https://www.youtube.com/watch?v=0yZG1-v-BXA Mike W9MDB C:\Programme 2\wsjtx\bin>rigctl-wsjtx -l | find "991" 1035 Ya

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Kim gross
OK. I figured out my mistake with following the video. When I run the rigctl-wsjtx.exe,   and I try to test with F to get frequency I get the get_freq: error = Invalid Parmeter. On 6/2/2020 1:45 PM, Kim gross wrote: Thanks for the help Mike For my setup com3 is primary port, and com  is

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Scott Boutwell
evelopment Date: Tuesday, June 2, 2020 at 1:47 PM To: 'WSJT software development' Subject: Re: [wsjt-devel] Hamlib error with GA release Hi Bill and others, I have the same error here at my PC: WSJT-X v2.2.0 GA cannot communicate with my FT991 via normal Com Port. Audio works nor

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Kim gross
Thanks for the help Mike For my setup com3 is primary port, and com  is the secondary. I am trying to follow the directions but when I run the rigcrtl -m 1035 -r com3 -R com -s 38400 it never comes back.  If I don't do both -r and -R I get an error.  If I set both -r and -R to come3, it drops

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Black Michael via wsjt-devel
I need one of the Yaesu owners to follow the directions in this youtube video and send me their debug.txt file. https://www.youtube.com/watch?v=0yZG1-v-BXA Mike W9MDB___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread DG2YCB, Uwe
, DG2YCB Von: Bill Somerville [mailto:g4...@classdesign.com] Gesendet: Dienstag, 2. Juni 2020 19:25 An: wsjt-devel@lists.sourceforge.net Betreff: Re: [wsjt-devel] Hamlib error with GA release Hi Jay, is this issue also associated with no receive audio to WSJT-X? 73 Bill G4WJS. On 02

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Jay Hainline
helps. Let me know what else you might need.73 Jay. KA9CFDSent from my U.S.Cellular© Smartphone Original message From: Bill Somerville Date: 6/2/20 12:34 (GMT-06:00) To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Hamlib error with GA release Hi Jay

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread brett williams
<mailto:g4...@classdesign.com> Sent: Tuesday, June 2, 2020 10:29 AM To: wsjt-devel@lists.sourceforge.net<mailto:wsjt-devel@lists.sourceforge.net> Subject: Re: [wsjt-devel] Hamlib error with GA release Hi Jay, is this issue also associated with no receive audio to WSJT-X? 73 Bill G4WJS. O

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Bill Somerville
message From: Bill Date: 6/2/20 11:44 (GMT-06:00) To: WSJT software development Subject: Re: [wsjt-devel] Hamlib error with GA release I have run into the same issue. Just installed the 2.2.0 GA on Windows 10 and receive "Hamlib error: Invalid parameter while getting current freq

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Jay Hainline
Same issue with my FT991.Hamlib error: Invalid parameter while getting current frequency.Jay KA9CFDSent from my U.S.Cellular© Smartphone Original message From: Bill Date: 6/2/20 11:44 (GMT-06:00) To: WSJT software development Subject: Re: [wsjt-devel] Hamlib error with GA

Re: [wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Bill
I have run into the same issue. Just installed the 2.2.0 GA on Windows 10 and receive "Hamlib error: Invalid parameter while getting current frequency". Radio - FT991A. Also, no display on the waterfall but shows activity in the decode list. Previous versions worked fine and JTDX still works normal

[wsjt-devel] Hamlib error with GA release

2020-06-02 Thread Kim gross
Windows  64 bit, upgraded to GA release I get a hamlib error and can not do anything.   Reinstalled RC3, system works fine. FT991A. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel