|
Locked
Re: Yaesu wont connect
#hamlib
#signalink
Rod Greene <w7zrc@...>
Thanks Mike and all! I’ll advise my friend and see if we can implement a better solution.
toggle quoted message
Show quoted text
73 Rod/w7zrc On Wednesday, May 25, 2022, 9:26 PM, SteveO via groups.io <sollmann22@...> wrote:
Mike, I agree. I’ve tried splitting a COM port and what happens is that WSJT-X is sending commands and the “other” application also sends commands. Sometimes at the same time, corrupting the data. To be honest, I don’t even know why the virtual serial port vendors even offer this solution to its customers. For me the solution was to have a dedicated port to the radio from my application and have a dedicated port to WSJT-X (or SDR radio) using a virtual cable to connect. The application then sends one message at a time to the rig thus preventing contention/corruption in the serial messages. Although even with this method, WSJT-X doesn’t like unsolicited message responses. So you still have to filter responses from the rig only providing WSJT-X “safe” command responses back to the WSJT-X serial interface. “Safe” commands means only send responses to WSJT-X that would be for a CAT command that WSJT-X would send to the radio. Flooding WSJT-X with unsolicited or unexpected messages will cause it to fail and stop working. Just passing along my experiences from writing my own CAT control program for the FT-891/FT-991a radios. Best regards, Steve KC5NK Sent from Mail for Windows From: Michael Black via groups.io Sent: Wednesday, May 25, 2022 10:10 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] Yaesu wont connect #hamlib #signalink Using a rig with a split com port is a crap shoot. Sometimes works...sometimes not. There are solutions that work 100%. #1 You can use rigctld with WSJT-X and then use rigctlcom (a TS-2000 emulator) on a VSPE pair. ACLog then connect to the TS-2000 emulator.#2 You can use FLRig with WSJT-X and the same rigctlcom program will talk to FLRig and ACLog connects to the TS-2000 emulator. Mike W9MDB On Wednesday, May 25, 2022, 05:27:31 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: Yes, a Navigator creates a com port and VSPE provides a split On Wednesday, May 25, 2022, 3:22 PM, Michael Black via groups.io <mdblack98@...> wrote: Does he have ACLog connected to the rig too somehow? Maybe trying to use a splitter? Mike W9MDB On Wednesday, May 25, 2022, 04:16:41 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: Now that this problem is solved my friend has another one. After WSJT-X and ACLog are running for a bit, he gets another HamLib error: HamLib error:Protocol error3256 :newcat.c(10025):newcat_get_vfo_mode returning(-8) And then dame as above with: 3255:newcat:c(1623):newcat_get_vfo returning(-8) This repeats several times and then: 3254:rigrig_get_vfo: elapsed=164ms and on with more of the same. Any suggestions? Thanks and 73, Rod/w7zrc On Saturday, May 21, 2022, 02:11:28 PM MDT, Michael Black via groups.io <mdblack98@...> wrote: New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk Mike W9MDB On Saturday, May 21, 2022, 01:51:45 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: On Saturday, May 21, 2022, 12:46:39 PM MDT, Rod Greene via groups.io <w7zrc@...> wrote: I have a friend with a Yaesu FTDX3000; Win10; latest WSJT-X; and Navigator interface. This combo worked fine for a long time, then he recently updated Windows and WSJT-X and then started getting the "HamLib error: Command rejected by the rig". Basically, HamLib won't control the rig CAT and WSJT-X doesn't recognize CAT so won't go into transmit, etc.. I suspect this may be similar to what others have been experiencing. I also suspect it's a problem between Windows 10 and HamLib. Does anyone have a solution that we can try? Thanks and 73, Rod/w7zrc |
|
|
|
Michael Black
It's not supposed to be -- this line in the decode function is supposed to turn off the lft8opon flag.The AP button is hidden when in Hound mode.
toggle quoted message
Show quoted text
if(m_mode=="FT8") dec_data.params.lft8apon = ui->actionEnable_AP_FT8->isVisible () && ui->actionEnable_AP_FT8->isChecked (); Mike W9MDB On Thursday, May 26, 2022, 08:52:25 AM CDT, The Greene Family <cvgreene@...> wrote:
Is AP automatically activated when you're in Hound mode on FT8? For the first time yesterday I had a "? a3" added to the end of the "RR73" message from a Fox. Came as a surprise. A search of the documentation did not yield an obvious answer, but perhaps I missed it. Feel free to abuse me appropriately if I didn't do a thorough enough search. 73, Clarke K1JX |
|
|
|
Locked
Re: #Cat_RigControl #Yaesu
#Cat_RigControl
#Yaesu
Thanks for the script name, I'll have a look at that.
The FT990 CAT spec is different between ROM v1.2 and v1.3. For v1.2 CAT always sends 1492 bytes from the UPDATE command which takes about 3s to return. The story goes that a 3s delay was no good for contest work so v1.3 was released where the UPDATE command has a parameter and returns 1508, 32 or 16 bytes depending whether you want all the data or parts like just the VFO etc which would be back in milliseconds. So the rig spec doesn't work for rigs on ROM v1.2 and I'm trying to hack my local rig files to fix it. 73 David |
|
|
|
The Greene Family
Is AP automatically activated when you're in Hound mode on FT8?
For the first time yesterday I had a "? a3" added to the end of the "RR73" message from a Fox. Came as a surprise. A search of the documentation did not yield an obvious answer, but perhaps I missed it. Feel free to abuse me appropriately if I didn't do a thorough enough search. 73, Clarke K1JX |
|
|
|
Locked
Re: #Cat_RigControl #Yaesu
#Cat_RigControl
#Yaesu
Michael Black
Why do we need a 1.2 rig? What's different?
toggle quoted message
Show quoted text
The src folder is set in build-hamlib.sh which will be in your home bin directorySRCD="$HOME/src/hamlib" On Thursday, May 26, 2022, 03:11:42 AM CDT, David via groups.io <m0ezp@...> wrote:
Hi Mike, Thanks again. I've made progress and tracked down the cause of not seeing changes come through. I've been changing ft990.c and ft990.h where I'd put the repository locally \Hamlib-master but source was being taken from \JTSDK64-Tools\tools\msys64\home\David\src\hamlib\src\ - where is the source folder set? Also, if I wanted to create a new rig eg ft990v12 what's the file or process to do that please? Many thanks David |
|
|
|
Ellis Birt (G7SAI)
I am sure you are right, but from June 1st, some UK stations will be using the optional /70, with or without the regional indicator 'Q' to celebrate the Platinum Jubilee.
For example, G7SAI/70, GQ7SAI and GQ7SAI/70 are all valid during June. Similarly MQ and 2Q prefixes. 73 de Ellis G7SAI |
|
|
|
Dave Garber <ve3wej@...>
I have seen others that add a state or something similar and it will treat
it as portable operation. also it may affect the log ( are we supposed to remove that suffix in our log, or is lotw/eql going to include that suffix Dave Garber VE3WEJ / VE3IE On Thu, May 26, 2022 at 4:00 AM Pietro Molina <pietro@...> wrote: I'm not sure that that call is completely legal... |
|
|
|
Locked
Re: #Cat_RigControl #Yaesu
#Cat_RigControl
#Yaesu
Hi Mike,
Thanks again. I've made progress and tracked down the cause of not seeing changes come through. I've been changing ft990.c and ft990.h where I'd put the repository locally \Hamlib-master but source was being taken from \JTSDK64-Tools\tools\msys64\home\David\src\hamlib\src\ - where is the source folder set? Also, if I wanted to create a new rig eg ft990v12 what's the file or process to do that please? Many thanks David |
|
|
|
I'm not sure that that call is completely legal...
In Italy we can't invent a suffix as GIRO and I think that has not been asked for permission, The special callsign could be similar to IQ3GIRO (asking to ministry) but not something/GIRO Pietro I2OIM Il giorno mer 25 mag 2022 alle ore 21:31 Alan via groups.io <g4gvb= aol.co.uk@groups.io> ha scritto: Running the latest WSJT version and Win 7 : Is anyone else seeing this. A |
|
|
|
Reino Talarmo
I do not use Enable AP but I do use Deep.What do I loose when I change Deep to Normal? Hi Amos AP potential false decodes are indicated by "?" mark. AP as such increases false decodes only during a QSO including messages that are decoded to start with "CQ" or "MyCall". See User Guide 12.1. AP Decoding. A total removal of false decoded would require an implementation of Artificial Intelligence as Regulatory Authorities could allocate almost any call sign construction or a message structure based filtering would prevent or make difficult to design new contest messages. Humans are still luckily much better in recognizing suspicious call signs and other contructions! 73, Reino OH3mA |
|
|
|
Locked
Re: Yaesu wont connect
#hamlib
#signalink
SteveO - KC5NK
Mike,
I agree. I’ve tried splitting a COM port and what happens is that WSJT-X is sending commands and the “other” application also sends commands. Sometimes at the same time, corrupting the data. To be honest, I don’t even know why the virtual serial port vendors even offer this solution to its customers. For me the solution was to have a dedicated port to the radio from my application and have a dedicated port to WSJT-X (or SDR radio) using a virtual cable to connect. The application then sends one message at a time to the rig thus preventing contention/corruption in the serial messages. Although even with this method, WSJT-X doesn’t like unsolicited message responses. So you still have to filter responses from the rig only providing WSJT-X “safe” command responses back to the WSJT-X serial interface. “Safe” commands means only send responses to WSJT-X that would be for a CAT command that WSJT-X would send to the radio. Flooding WSJT-X with unsolicited or unexpected messages will cause it to fail and stop working. Just passing along my experiences from writing my own CAT control program for the FT-891/FT-991a radios. Best regards, Steve KC5NK Sent from Mail for Windows From: Michael Black via groups.io Sent: Wednesday, May 25, 2022 10:10 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] Yaesu wont connect #hamlib #signalink Using a rig with a split com port is a crap shoot. Sometimes works...sometimes not. There are solutions that work 100%. #1 You can use rigctld with WSJT-X and then use rigctlcom (a TS-2000 emulator) on a VSPE pair. ACLog then connect to the TS-2000 emulator.#2 You can use FLRig with WSJT-X and the same rigctlcom program will talk to FLRig and ACLog connects to the TS-2000 emulator. Mike W9MDB On Wednesday, May 25, 2022, 05:27:31 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: Yes, a Navigator creates a com port and VSPE provides a split On Wednesday, May 25, 2022, 3:22 PM, Michael Black via groups.io <mdblack98@...> wrote: Does he have ACLog connected to the rig too somehow? Maybe trying to use a splitter? Mike W9MDB On Wednesday, May 25, 2022, 04:16:41 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: Now that this problem is solved my friend has another one. After WSJT-X and ACLog are running for a bit, he gets another HamLib error: HamLib error:Protocol error3256 :newcat.c(10025):newcat_get_vfo_mode returning(-8) And then dame as above with: 3255:newcat:c(1623):newcat_get_vfo returning(-8) This repeats several times and then: 3254:rigrig_get_vfo: elapsed=164ms and on with more of the same. Any suggestions? Thanks and 73, Rod/w7zrc On Saturday, May 21, 2022, 02:11:28 PM MDT, Michael Black via groups.io <mdblack98@...> wrote: New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk Mike W9MDB On Saturday, May 21, 2022, 01:51:45 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: On Saturday, May 21, 2022, 12:46:39 PM MDT, Rod Greene via groups.io <w7zrc@...> wrote: I have a friend with a Yaesu FTDX3000; Win10; latest WSJT-X; and Navigator interface. This combo worked fine for a long time, then he recently updated Windows and WSJT-X and then started getting the "HamLib error: Command rejected by the rig". Basically, HamLib won't control the rig CAT and WSJT-X doesn't recognize CAT so won't go into transmit, etc.. I suspect this may be similar to what others have been experiencing. I also suspect it's a problem between Windows 10 and HamLib. Does anyone have a solution that we can try? Thanks and 73, Rod/w7zrc |
|
|
|
Locked
Re: Yaesu wont connect
#hamlib
#signalink
Michael Black
Using a rig with a split com port is a crap shoot. Sometimes works...sometimes not.
toggle quoted message
Show quoted text
There are solutions that work 100%. #1 You can use rigctld with WSJT-X and then use rigctlcom (a TS-2000 emulator) on a VSPE pair. ACLog then connect to the TS-2000 emulator.#2 You can use FLRig with WSJT-X and the same rigctlcom program will talk to FLRig and ACLog connects to the TS-2000 emulator. Mike W9MDB On Wednesday, May 25, 2022, 05:27:31 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote:
Yes, a Navigator creates a com port and VSPE provides a split On Wednesday, May 25, 2022, 3:22 PM, Michael Black via groups.io <mdblack98@...> wrote: Does he have ACLog connected to the rig too somehow? Maybe trying to use a splitter? Mike W9MDB On Wednesday, May 25, 2022, 04:16:41 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: Now that this problem is solved my friend has another one. After WSJT-X and ACLog are running for a bit, he gets another HamLib error: HamLib error:Protocol error3256 :newcat.c(10025):newcat_get_vfo_mode returning(-8) And then dame as above with: 3255:newcat:c(1623):newcat_get_vfo returning(-8) This repeats several times and then: 3254:rigrig_get_vfo: elapsed=164ms and on with more of the same. Any suggestions? Thanks and 73, Rod/w7zrc On Saturday, May 21, 2022, 02:11:28 PM MDT, Michael Black via groups.io <mdblack98@...> wrote: New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk Mike W9MDB On Saturday, May 21, 2022, 01:51:45 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: On Saturday, May 21, 2022, 12:46:39 PM MDT, Rod Greene via groups.io <w7zrc@...> wrote: I have a friend with a Yaesu FTDX3000; Win10; latest WSJT-X; and Navigator interface. This combo worked fine for a long time, then he recently updated Windows and WSJT-X and then started getting the "HamLib error: Command rejected by the rig". Basically, HamLib won't control the rig CAT and WSJT-X doesn't recognize CAT so won't go into transmit, etc.. I suspect this may be similar to what others have been experiencing. I also suspect it's a problem between Windows 10 and HamLib. Does anyone have a solution that we can try? Thanks and 73, Rod/w7zrc |
|
|
|
Evan Smith
My logs from WSJT-X go to Notepad. I can then find log entries when I use the following:
C:\Users\YOUR NAME\AppData\Local\WSJT-X\wsjtx_log.adi I have Windows 11. The C: is the Driver. (I think that is what it is called,) My name appears after Users\. If you have a Windows you can find all the info when you hit the Windows +R and find the info you need. I hope this helps. Evan KB2AMY |
|
|
|
Locked
Re: Yaesu wont connect
#hamlib
#signalink
Rod Greene <w7zrc@...>
Yes, a Navigator creates a com port and VSPE provides a split
toggle quoted message
Show quoted text
On Wednesday, May 25, 2022, 3:22 PM, Michael Black via groups.io <mdblack98@...> wrote:
Does he have ACLog connected to the rig too somehow? Maybe trying to use a splitter? Mike W9MDB On Wednesday, May 25, 2022, 04:16:41 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: Now that this problem is solved my friend has another one. After WSJT-X and ACLog are running for a bit, he gets another HamLib error: HamLib error:Protocol error3256 :newcat.c(10025):newcat_get_vfo_mode returning(-8) And then dame as above with: 3255:newcat:c(1623):newcat_get_vfo returning(-8) This repeats several times and then: 3254:rigrig_get_vfo: elapsed=164ms and on with more of the same. Any suggestions? Thanks and 73, Rod/w7zrc On Saturday, May 21, 2022, 02:11:28 PM MDT, Michael Black via groups.io <mdblack98@...> wrote: New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk Mike W9MDB On Saturday, May 21, 2022, 01:51:45 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: On Saturday, May 21, 2022, 12:46:39 PM MDT, Rod Greene via groups.io <w7zrc@...> wrote: I have a friend with a Yaesu FTDX3000; Win10; latest WSJT-X; and Navigator interface. This combo worked fine for a long time, then he recently updated Windows and WSJT-X and then started getting the "HamLib error: Command rejected by the rig". Basically, HamLib won't control the rig CAT and WSJT-X doesn't recognize CAT so won't go into transmit, etc.. I suspect this may be similar to what others have been experiencing. I also suspect it's a problem between Windows 10 and HamLib. Does anyone have a solution that we can try? Thanks and 73, Rod/w7zrc |
|
|
|
Locked
Re: No USB Input Audio to WSJT
#stopped_working
#Yaesu
#macOS
#AudioIssues
#ftdi
Mostly for my own record (and anyone else reading this)....
I got WSJT-x working on an old, Intel-based Mac today running MacOS Catalina. The old Mac did not require a USB hub to connect the two cables needed - USB Audio and CAT. WSJT-x "just worked" showing me that my audio cable is not the issue and, I suspect, neither is WSJT-x. The new suspects are MacOS Monterey and/or the hubs or how Monterey deals with hubs or USB overall. I can see numerous complaints online a bout M1 Macs and USB Audio through USB-C hubs... Hmm, we will see. My text test is to place the USB Audio cable on it's own, non-Hub based USB-C -> USB2/3 dongle (no hub involved for that cable). The other USB 2/3 cables (CAT as well as one for a WinKeyer) work fine through the hub. Stay tuned. -- Scott, W1MVY |
|
|
|
Locked
Re: Yaesu wont connect
#hamlib
#signalink
Michael Black
Does he have ACLog connected to the rig too somehow?
toggle quoted message
Show quoted text
Maybe trying to use a splitter? Mike W9MDB On Wednesday, May 25, 2022, 04:16:41 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote:
Now that this problem is solved my friend has another one. After WSJT-X and ACLog are running for a bit, he gets another HamLib error: HamLib error:Protocol error3256 :newcat.c(10025):newcat_get_vfo_mode returning(-8) And then dame as above with: 3255:newcat:c(1623):newcat_get_vfo returning(-8) This repeats several times and then: 3254:rigrig_get_vfo: elapsed=164ms and on with more of the same. Any suggestions? Thanks and 73, Rod/w7zrc On Saturday, May 21, 2022, 02:11:28 PM MDT, Michael Black via groups.io <mdblack98@...> wrote: New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk Mike W9MDB On Saturday, May 21, 2022, 01:51:45 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: On Saturday, May 21, 2022, 12:46:39 PM MDT, Rod Greene via groups.io <w7zrc@...> wrote: I have a friend with a Yaesu FTDX3000; Win10; latest WSJT-X; and Navigator interface. This combo worked fine for a long time, then he recently updated Windows and WSJT-X and then started getting the "HamLib error: Command rejected by the rig". Basically, HamLib won't control the rig CAT and WSJT-X doesn't recognize CAT so won't go into transmit, etc.. I suspect this may be similar to what others have been experiencing. I also suspect it's a problem between Windows 10 and HamLib. Does anyone have a solution that we can try? Thanks and 73, Rod/w7zrc |
|
|
|
Locked
Re: Yaesu wont connect
#hamlib
#signalink
Rod Greene <w7zrc@...>
Now that this problem is solved my friend has another one. After WSJT-X and ACLog are running for a bit, he gets another HamLib error:
toggle quoted message
Show quoted text
HamLib error:Protocol error3256 :newcat.c(10025):newcat_get_vfo_mode returning(-8) And then dame as above with: 3255:newcat:c(1623):newcat_get_vfo returning(-8) This repeats several times and then: 3254:rigrig_get_vfo: elapsed=164ms and on with more of the same. Any suggestions? Thanks and 73, Rod/w7zrc On Saturday, May 21, 2022, 02:11:28 PM MDT, Michael Black via groups.io <mdblack98@...> wrote:
New hamlib for Windows installation directions #1 Shut down WSJTX/JTDX #2 Download either the 32-bit or 64-bit DLL matching the 32/64-bit version of WSJTX/JTDX -- hopefully your browser doesn't block it but may warn you multiple times. If you can do a "Save As" you can save it directly in \WSJT\WSJTX\bin and replace the libhamlib-4.dll that is there. http://n0nb.users.sourceforge.net/dll32/libhamlib-4.dll http://n0nb.users.sourceforge.net/dll64/libhamlib-4.dll #3 If you don't save directly you need to open a file browser and move the file that way. If you're not familiar with that here's a video on the file browser - https://www.youtube.com/watch?v=AyVqCJrs9dk Mike W9MDB On Saturday, May 21, 2022, 01:51:45 PM CDT, Rod Greene via groups.io <w7zrc@...> wrote: On Saturday, May 21, 2022, 12:46:39 PM MDT, Rod Greene via groups.io <w7zrc@...> wrote: I have a friend with a Yaesu FTDX3000; Win10; latest WSJT-X; and Navigator interface. This combo worked fine for a long time, then he recently updated Windows and WSJT-X and then started getting the "HamLib error: Command rejected by the rig". Basically, HamLib won't control the rig CAT and WSJT-X doesn't recognize CAT so won't go into transmit, etc.. I suspect this may be similar to what others have been experiencing. I also suspect it's a problem between Windows 10 and HamLib. Does anyone have a solution that we can try? Thanks and 73, Rod/w7zrc |
|
|
|
Joe Subich, W4TV
Those are typical "false decodes" from using "deep". Go to Normal and
toggle quoted message
Show quoted text
the incidence of false decodes will be significantly reduced. 73, ... Joe, W4TV On 2022-05-25 4:47 PM, Amos Sobel 4X4MF wrote:
Another one that just came in: |
|
|
|
Michael Black
Yes...false decodes are possible.
toggle quoted message
Show quoted text
Mike W9MDB On Wednesday, May 25, 2022, 03:48:08 PM CDT, Amos Sobel 4X4MF <asobel@...> wrote:
Another one that just came in: 203915 -22 0.6 992 ~ Z28YNB P66LCC 579 4023 Amos 4X4MF -----Original Message----- From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Michael Black via groups.io Sent: Wednesday, May 25, 2022 10:24 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] Phony calls #decode You will lose some decodes but CPU usage will be less. Mike W9MDB On Wednesday, May 25, 2022, 02:20:28 PM CDT, Amos Sobel 4X4MF <asobel@...> wrote: Willie I do not use Enable AP but I do use Deep. What do I loose when I change Deep to Normal? Amos 4X4MF -----Original Message----- From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of William Smith Sent: Wednesday, May 25, 2022 9:57 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] Phony calls #decode What is “Decode” set to across the top menu bar? If it’s not ’Normal’ try backing off, and don’t use AP, see if that solves the problem. 73, Willie N1JBJ On May 25, 2022, at 2:39 PM, Amos Sobel 4X4MF <asobel@...> wrote: |
|
|
|
Amos Sobel 4X4MF
Another one that just came in:
toggle quoted message
Show quoted text
203915 -22 0.6 992 ~ Z28YNB P66LCC 579 4023 Amos 4X4MF -----Original Message-----
From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of Michael Black via groups.io Sent: Wednesday, May 25, 2022 10:24 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] Phony calls #decode You will lose some decodes but CPU usage will be less. Mike W9MDB On Wednesday, May 25, 2022, 02:20:28 PM CDT, Amos Sobel 4X4MF <asobel@...> wrote: Willie I do not use Enable AP but I do use Deep. What do I loose when I change Deep to Normal? Amos 4X4MF -----Original Message----- From: main@WSJTX.groups.io <main@WSJTX.groups.io> On Behalf Of William Smith Sent: Wednesday, May 25, 2022 9:57 PM To: main@WSJTX.groups.io Subject: Re: [WSJTX] Phony calls #decode What is “Decode” set to across the top menu bar? If it’s not ’Normal’ try backing off, and don’t use AP, see if that solves the problem. 73, Willie N1JBJ On May 25, 2022, at 2:39 PM, Amos Sobel 4X4MF <asobel@...> wrote: |
|
|