moderated #Install # #Cat_RigControl Hamlib error: Invalid parameter while testing getting current VFO #install #Cat_RigControl


Jim Pruitt
 

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use.  I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY

 


Georgina Joyce
 

Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@...> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use.  I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY

 




Georgina


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



Jim Pruitt
 

Hello Georgina.

Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.

Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@...> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use.  I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY

 




Georgina


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







Joe Subich, W4TV
 

Someone said I need to configure the USB Comm port for 9600 baud
rather than 19,200.
That "someone" was close but no cigar. The FT-840 communicates *ONLY*
at 4800 bps, 8 (data) bits, no parity and *2* stop bits. See page 35,
paragraph 2, in the FT-840 Instruction Manual. You will need to
configure File -> Settings -> Radio -> CAT Control -> Serial Port
Parameters with those settings. In addition, start with Handshake:
None and "Force Control Lines" DTR/RTS *BLANK*.

I don't know if WSJTX/Hamlib can turn the FT-840 TX On/OFF by CAT
Commands but reading the command documentation in the Instruction
Manual (pg 36) it seems that there may be a possibility of doing so.

73,

... Joe, W4TV


On 2021-01-20 4:22 PM, Jim Pruitt wrote:
Hello Georgina.
Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.
Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.
Thank you.
Jim Pruitt
WA7DUY
On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@gmail.com <mailto:jpruitt67@gmail.com>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use. I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY


Bill Somerville
 

On 20/01/2021 21:48, Joe Subich, W4TV wrote:
I don't know if WSJTX/Hamlib can turn the FT-840 TX On/OFF by CAT
Commands but reading the command documentation in the Instruction
Manual (pg 36) it seems that there may be a possibility of doing so.

73,

   ... Joe, W4TV
Hi Joe and Jim,

CAT PTT is implemented in Hamlib for the Yaesu FT-840.

73
Bill
G4WJS.


Jim Pruitt
 

Hi Joe.

Thank you for the info but using those still gives me no cigar.  I am almost convinced that this new CAT cable is defective since I can't get anything to talk to it at all.  I continue to get the same Hamlib error: Invalid parameter while testing getting current VFO no matter how I have it set.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:48 PM, Joe Subich, W4TV wrote:


Someone said I need to configure the USB Comm port for 9600 baud
rather than 19,200.
That "someone" was close but no cigar.  The FT-840 communicates *ONLY*
at 4800 bps, 8 (data) bits, no parity and *2* stop bits.  See page 35,
paragraph 2, in the FT-840 Instruction Manual. You will need to
configure File -> Settings -> Radio -> CAT Control -> Serial Port
Parameters with those settings.  In addition, start with Handshake:
None and "Force Control Lines" DTR/RTS *BLANK*.

I don't know if WSJTX/Hamlib can turn the FT-840 TX On/OFF by CAT
Commands but reading the command documentation in the Instruction
Manual (pg 36) it seems that there may be a possibility of doing so.

73,

   ... Joe, W4TV


On 2021-01-20 4:22 PM, Jim Pruitt wrote:
Hello Georgina.

Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.

Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@... <mailto:jpruitt67@...>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use.  I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY








Jim Pruitt
 

Hello Bill.

What does that mean?  Do I access Hamlib somewhere other than through WSJT-X and/or FLDigi?  I tried other option settings in the configuration for PTT and initializing/Test CAT always fails and then returns the same hamlib error: Invalid parameter while testing getting current VFO and no other functions seem to work either.  I do have the rig set to Yaesu FT840 "Radio" and "Rig" box with interval at 1 second.  "Test CAT" always turns red,  never green.

Thank you.

Jim Pruitt
WA7DUY

On 1/20/2021 1:57 PM, Bill Somerville wrote:
On 20/01/2021 21:48, Joe Subich, W4TV wrote:
I don't know if WSJTX/Hamlib can turn the FT-840 TX On/OFF by CAT
Commands but reading the command documentation in the Instruction
Manual (pg 36) it seems that there may be a possibility of doing so.

73,

   ... Joe, W4TV

Hi Joe and Jim,

CAT PTT is implemented in Hamlib for the Yaesu FT-840.

73
Bill
G4WJS.






groups@...
 

Was there a disc supplied with the cable? If so did you install the driver from the disc?

73
Roger

On 20/01/2021 21:22, Jim Pruitt wrote:
Hello Georgina.
Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.
Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.
Thank you.
Jim Pruitt
WA7DUY
On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@gmail.com <mailto:jpruitt67@gmail.com>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use. I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY




Georgina


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





Jim Pruitt
 

Hello Roger.

Yes, there was a mini cd provided with the cable...but it had no Windows drivers on it!  It looked like a Chirp installer to me as Windows found no drivers to install from that disc.  For that reason I went to the Prolific support sight and grabbed the driver from there.

Thank you.

Jim Pruitt
WA7DUY

On 1/20/2021 2:41 PM, groups@... wrote:
Was there a disc supplied with the cable?  If so did you install the driver from the disc?

73
Roger

On 20/01/2021 21:22, Jim Pruitt wrote:
Hello Georgina.

Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.

Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@... <mailto:jpruitt67@...>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use. I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY






Georgina


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

















Georgina Joyce
 

Hello Jim,

With my FT-818 I need to use 2 cables and I am not sure if you will do too. You might need to get an interface of some kind like a SL USB. See this thread:


Was your cable listed as a cloning cable?

73

On 20 Jan 2021, at 22:45, Jim Pruitt <jpruitt67@...> wrote:

Hello Roger.

Yes, there was a mini cd provided with the cable...but it had no Windows drivers on it!  It looked like a Chirp installer to me as Windows found no drivers to install from that disc.  For that reason I went to the Prolific support sight and grabbed the driver from there.

Thank you.

Jim Pruitt
WA7DUY

On 1/20/2021 2:41 PM, groups@... wrote:
Was there a disc supplied with the cable?  If so did you install the driver from the disc?

73
Roger

On 20/01/2021 21:22, Jim Pruitt wrote:
Hello Georgina.

Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.

Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@... <mailto:jpruitt67@...>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use. I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY






Georgina


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



















Georgina


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



Joe Subich, W4TV
 

On 2021-01-20 4:22 PM, Jim Pruitt wrote:

I want my money back on the cable since the listed it as a FTDI chip
cable
If the cable is listed as an FTDI cable why was it installed as a
Prolific 2303 cable? Did you manually specify the driver or did
Windows select the driver?

Have you tried going to the FTDI web site:
<https://ftdichip.com/drivers/vcp-drivers/>
and downloading/installing the appropriate 32 bit or 64 bit drivers?

73,

... Joe, W4TV


On 2021-01-20 4:22 PM, Jim Pruitt wrote:
Hello Georgina.
Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.
Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.
Thank you.
Jim Pruitt
WA7DUY
On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@gmail.com <mailto:jpruitt67@gmail.com>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use. I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY


Jim Pruitt
 

It is NOT a FTDI chip even though the seller listed it as such.  It is a Prolific PL2303 chip.  The mini cd that came with it had installers for Kenwood, Motorola, Baofeng, and Standard but no Icon or Yaesu and no extracted windows drivers.  I got the latest Prolific driver for Windows 7 from the Prolific site.  I selected the driver.  Windows did not select it.

Thank you
Jim Pruitt
WA7DUY

On Wed, Jan 20, 2021, 4:07 PM Joe Subich, W4TV <lists@...> wrote:
On 2021-01-20 4:22 PM, Jim Pruitt wrote:

> I want my money back on the cable since the listed it as a FTDI chip
> cable

If the cable is listed as an FTDI cable why was it installed as a
Prolific 2303 cable?  Did you manually specify the driver or did
Windows select the driver?

Have you tried going to the FTDI web site:
    <https://ftdichip.com/drivers/vcp-drivers/>
and downloading/installing the appropriate 32 bit or 64 bit drivers?

73,

    ... Joe, W4TV


On 2021-01-20 4:22 PM, Jim Pruitt wrote:
> Hello Georgina.
>
> Sorry about that.  I am using a Windows 7 desktop.  The cable installs
> as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have
> matched in WSJT-X but the only thing that sort of worked was putting the
> FT840 in tune mode which emits a low tone from the FT840 but does not
> put it in tune.  No other function works and it does not read the VFO
> and I suspect that is why hamlib gets upset but I see no way to do
> anything with hamlib.  If I check the "use hamlib" checkbox and hit
> initialize it kicks the error and then unchecks the checkbox no matter
> what parameters I have set.
>
> Someone said I need to configure the USB Comm port for 9600 baud rather
> than 19,200.  For the record, FLDigi would not work with it either so I
> notified the ebay seller that I want my money back on the cable since
> the listed it as a FTDI chip cable.  I do have the right Prolific
> drivers but have tried 3 different version.  I do also use Chirp and
> those prolific cables work so I am pretty sure my problem is probably
> the new CAT cable but wanted some way to verify that.
>
> Thank you.
>
> Jim Pruitt
> WA7DUY
>
>
> On 1/20/2021 1:15 PM, Georgina Joyce wrote:
>> Hello Jim,
>>
>> You haven't stated what operating system you are using. You mention
>> chirp which leads me to linux but chirp can be run on other operating
>> systems.
>>
>> So you need to identify what port the cable is assigned. Under Windows
>> device manager comm ports. Or Linux lsusb. Then you need to match port
>> settings. Cat control is different to the audio settings.
>>
>> 73
>>> On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@...
>>> <mailto:jpruitt67@...>> wrote:
>>>
>>> I have had a version of WSJT-X installed for a while but haven't used
>>> it.  I have version 2.2.2 installed now.  I finally bought a CAT
>>> cable for my Yaesu FT840 that arrived a few days ago but I am not
>>> able to do anything with it.  The cable was described as a FTDI cable
>>> (not sure when Prolific started making FTDI chips).  Since I have
>>> Chirp installed I had the Prolific driver but the cable will not work
>>> no matter which version of the Prolific PL2303 driver  I try to use. 
>>> I am decoding FT8 signals so WSJT-X works but it keeps constantly
>>> kicking the error:
>>> Hamlib error: Invalid parameter while testing getting current VFO
>>>
>>> No matter what settings I use or change it kicks that error about
>>> every 30 seconds and selecting OK or cancel will kick me out of
>>> WSJT-X program and closes it.  Picking "configurations" just leaves
>>> me in the config settings.  It will not read or change the VFO or
>>> mode or anything else about the rig.  The cable is a Prolific2303
>>> cable with a cat plug on the end that matches (I assume) the FT840,
>>> or rather it will plug into the CAT jack.
>>>
>>> I have not found where Hamlib gets called or used and not sure how to
>>> fix the problem.  The CAT cable appears to sort of work but not
>>> really.  The only thing that seems to do anything is the "Tune"
>>> option which causes the Yaesu FT840 to emit a low tone indicating
>>> that it is in tune mode but it is not in tune mode.
>>>
>>> What am I missing?
>>>
>>> Thank you.
>>>
>>> Jim Pruitt
>>> WA7DUY






Jim Pruitt
 

The cable was listed as a CAT cable but the mini cd looked like it was a cloning cable or a Chirp cable.  I will have 3 cables, one for speaker, one for mic, and the CAT cable.

Thank you
Jim Pruitt
WA7DUY

On Wed, Jan 20, 2021, 3:52 PM Georgina Joyce <gena@...> wrote:
Hello Jim,

With my FT-818 I need to use 2 cables and I am not sure if you will do too. You might need to get an interface of some kind like a SL USB. See this thread:


Was your cable listed as a cloning cable?

73

On 20 Jan 2021, at 22:45, Jim Pruitt <jpruitt67@...> wrote:

Hello Roger.

Yes, there was a mini cd provided with the cable...but it had no Windows drivers on it!  It looked like a Chirp installer to me as Windows found no drivers to install from that disc.  For that reason I went to the Prolific support sight and grabbed the driver from there.

Thank you.

Jim Pruitt
WA7DUY

On 1/20/2021 2:41 PM, groups@... wrote:
Was there a disc supplied with the cable?  If so did you install the driver from the disc?

73
Roger

On 20/01/2021 21:22, Jim Pruitt wrote:
Hello Georgina.

Sorry about that.  I am using a Windows 7 desktop.  The cable installs as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched in WSJT-X but the only thing that sort of worked was putting the FT840 in tune mode which emits a low tone from the FT840 but does not put it in tune.  No other function works and it does not read the VFO and I suspect that is why hamlib gets upset but I see no way to do anything with hamlib.  If I check the "use hamlib" checkbox and hit initialize it kicks the error and then unchecks the checkbox no matter what parameters I have set.

Someone said I need to configure the USB Comm port for 9600 baud rather than 19,200.  For the record, FLDigi would not work with it either so I notified the ebay seller that I want my money back on the cable since the listed it as a FTDI chip cable.  I do have the right Prolific drivers but have tried 3 different version.  I do also use Chirp and those prolific cables work so I am pretty sure my problem is probably the new CAT cable but wanted some way to verify that.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:15 PM, Georgina Joyce wrote:
Hello Jim,

You haven't stated what operating system you are using. You mention chirp which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows device manager comm ports. Or Linux lsusb. Then you need to match port settings. Cat control is different to the audio settings.

73
On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@... <mailto:jpruitt67@...>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.  I have version 2.2.2 installed now.  I finally bought a CAT cable for my Yaesu FT840 that arrived a few days ago but I am not able to do anything with it.  The cable was described as a FTDI cable (not sure when Prolific started making FTDI chips).  Since I have Chirp installed I had the Prolific driver but the cable will not work no matter which version of the Prolific PL2303 driver  I try to use. I am decoding FT8 signals so WSJT-X works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30 seconds and selecting OK or cancel will kick me out of WSJT-X program and closes it.  Picking "configurations" just leaves me in the config settings.  It will not read or change the VFO or mode or anything else about the rig.  The cable is a Prolific2303 cable with a cat plug on the end that matches (I assume) the FT840, or rather it will plug into the CAT jack.

I have not found where Hamlib gets called or used and not sure how to fix the problem.  The CAT cable appears to sort of work but not really.  The only thing that seems to do anything is the "Tune" option which causes the Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY






Georgina


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



















Georgina


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






Joe Subich, W4TV
 

The mini cd that came with it had installers for Kenwood, Motorola,
Baofeng, and Standard but no Icon or Yaesu and no extracted windows
drivers.
That is concerning. The Yaesu TTL interface is "inverted TTL" - that
is the MARK/SPACE sense is inverted from normal (Mark is logic (0)
and Space is logic (1)). Kenwood TTL is "normal TTL". While the TTL
cables for Kenwood and Yaesu use the same connector and pin-out -
the logic states are reversed *AND* Kenwood transceivers need RTS/CTS
handshake. Further, in some Yaesu transceivers the serial out line
is "open emitter" (the transceiver sources +5V for logic high and is
high impedance for logic low) and requires a pull-down resistor in
the USB to TTL cable to make the "open emitter" configuration compatible
with the modern USB to TTL converters.

Given that you have an "installer" for Kenwood, I would be concerned
that you were sold/shipped a "Kenwood" cable instead of a proper Yaesu
cable.

73,

... Joe, W4TV


On 2021-01-20 7:16 PM, Jim Pruitt wrote:
It is NOT a FTDI chip even though the seller listed it as such.  It is a Prolific PL2303 chip.  The mini cd that came with it had installers for Kenwood, Motorola, Baofeng, and Standard but no Icon or Yaesu and no extracted windows drivers.  I got the latest Prolific driver for Windows 7 from the Prolific site.  I selected the driver.  Windows did not select it.
Thank you
Jim Pruitt
WA7DUY
On Wed, Jan 20, 2021, 4:07 PM Joe Subich, W4TV <lists@subich.com <mailto:lists@subich.com>> wrote:
On 2021-01-20 4:22 PM, Jim Pruitt wrote:

> I want my money back on the cable since the listed it as a FTDI chip
> cable
If the cable is listed as an FTDI cable why was it installed as a
Prolific 2303 cable?  Did you manually specify the driver or did
Windows select the driver?
Have you tried going to the FTDI web site:
    <https://ftdichip.com/drivers/vcp-drivers/
<https://ftdichip.com/drivers/vcp-drivers/>>
and downloading/installing the appropriate 32 bit or 64 bit drivers?
73,
    ... Joe, W4TV
On 2021-01-20 4:22 PM, Jim Pruitt wrote:
> Hello Georgina.
>
> Sorry about that.  I am using a Windows 7 desktop.  The cable
installs
> as a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I
have
> matched in WSJT-X but the only thing that sort of worked was
putting the
> FT840 in tune mode which emits a low tone from the FT840 but does
not
> put it in tune.  No other function works and it does not read the
VFO
> and I suspect that is why hamlib gets upset but I see no way to do
> anything with hamlib.  If I check the "use hamlib" checkbox and hit
> initialize it kicks the error and then unchecks the checkbox no
matter
> what parameters I have set.
>
> Someone said I need to configure the USB Comm port for 9600 baud
rather
> than 19,200.  For the record, FLDigi would not work with it
either so I
> notified the ebay seller that I want my money back on the cable
since
> the listed it as a FTDI chip cable.  I do have the right Prolific
> drivers but have tried 3 different version.  I do also use Chirp and
> those prolific cables work so I am pretty sure my problem is
probably
> the new CAT cable but wanted some way to verify that.
>
> Thank you.
>
> Jim Pruitt
> WA7DUY
>
>


Steve marsh (M0NMA)
 

Jim

The issue with Prolific chips is that there are a lot of copies around and Prolific changed their driver so that it won’t work with copy chips. If you look at device manager and see an exclamation mark by the com port then that is likely to be your issue. The last driver that worked reliably with clone chips is 3.2.0.0 - the best place to get a copy is Miklor’s site : https://www.miklor.com/COM/UV_Drivers.php

it may be worth trying the older driver anyway as it could help - it is a 2 minute job and you can always switch back if it doesn’t help. 

Steve M0NMA


Bill Somerville
 

On 21/01/2021 08:58, Steve marsh (M0NMA) wrote:
Jim

The issue with Prolific chips is that there are a lot of copies around and Prolific changed their driver so that it won’t work with copy chips. If you look at device manager and see an exclamation mark by the com port then that is likely to be your issue. The last driver that worked reliably with clone chips is 3.2.0.0 - the best place to get a copy is Miklor’s site : https://www.miklor.com/COM/UV_Drivers.php <https://www.miklor.com/COM/UV_Drivers.php>

it may be worth trying the older driver anyway as it could help - it is a 2 minute job and you can always switch back if it doesn’t help.

Steve M0NMA
Hi Steve,

it should be noted that FTDI also suffered from outbreaks of cloning their firmware and chips by disreputable manufacturers, AFAIK both companies followed a strategy of crippling clones by using special code in the official drivers to inject garbage into the serial data of detected clone implementations. FTDI may have stopped doing that. Either way it is not really the fault of the official manufacturers.

73
Bill
G4WJS.


groups@...
 

Since Chirp uses CAT to perform its functions I see no reason why your cable should not work with WSJTX. A cloning cable is unlikely to have a USB-A socket at one end. Normally I would expect it to have two identical connectors for the two rigs you are using to clone.

I use the same cable with my IC 7100 for both Chirp and WSJTX.

Can you look through the CD again and double check there are no installation instructions or files with driver? You must use the drivers supplied with CAT cables for reasons I wont go into on this forum.

73
Roger
G#4HZA

On 21/01/2021 00:19, Jim Pruitt wrote:
The cable was listed as a CAT cable but the mini cd looked like it was a
cloning cable or a Chirp cable. I will have 3 cables, one for speaker, one
for mic, and the CAT cable.
Thank you
Jim Pruitt
WA7DUY
On Wed, Jan 20, 2021, 3:52 PM Georgina Joyce <gena@gena-j.me.uk> wrote:

Hello Jim,

With my FT-818 I need to use 2 cables and I am not sure if you will do
too. You might need to get an interface of some kind like a SL USB. See
this thread:

https://www.eham.net/article/2800

Was your cable listed as a cloning cable?

73

On 20 Jan 2021, at 22:45, Jim Pruitt <jpruitt67@gmail.com> wrote:

Hello Roger.

Yes, there was a mini cd provided with the cable...but it had no Windows
drivers on it! It looked like a Chirp installer to me as Windows found no
drivers to install from that disc. For that reason I went to the Prolific
support sight and grabbed the driver from there.

Thank you.

Jim Pruitt
WA7DUY

On 1/20/2021 2:41 PM, groups@thebluecastle.org.uk wrote:

Was there a disc supplied with the cable? If so did you install the
driver from the disc?

73
Roger

On 20/01/2021 21:22, Jim Pruitt wrote:

Hello Georgina.

Sorry about that. I am using a Windows 7 desktop. The cable installs as
a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched
in WSJT-X but the only thing that sort of worked was putting the FT840 in
tune mode which emits a low tone from the FT840 but does not put it in
tune. No other function works and it does not read the VFO and I suspect
that is why hamlib gets upset but I see no way to do anything with hamlib.
If I check the "use hamlib" checkbox and hit initialize it kicks the error
and then unchecks the checkbox no matter what parameters I have set.

Someone said I need to configure the USB Comm port for 9600 baud rather
than 19,200. For the record, FLDigi would not work with it either so I
notified the ebay seller that I want my money back on the cable since the
listed it as a FTDI chip cable. I do have the right Prolific drivers but
have tried 3 different version. I do also use Chirp and those prolific
cables work so I am pretty sure my problem is probably the new CAT cable
but wanted some way to verify that.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:15 PM, Georgina Joyce wrote:

Hello Jim,

You haven't stated what operating system you are using. You mention chirp
which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows
device manager comm ports. Or Linux lsusb. Then you need to match port
settings. Cat control is different to the audio settings.

73

On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@gmail.com
<mailto:jpruitt67@gmail.com> <jpruitt67@gmail.com>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.
I have version 2.2.2 installed now. I finally bought a CAT cable for my
Yaesu FT840 that arrived a few days ago but I am not able to do anything
with it. The cable was described as a FTDI cable (not sure when Prolific
started making FTDI chips). Since I have Chirp installed I had the
Prolific driver but the cable will not work no matter which version of the
Prolific PL2303 driver I try to use. I am decoding FT8 signals so WSJT-X
works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30
seconds and selecting OK or cancel will kick me out of WSJT-X program and
closes it. Picking "configurations" just leaves me in the config
settings. It will not read or change the VFO or mode or anything else
about the rig. The cable is a Prolific2303 cable with a cat plug on the
end that matches (I assume) the FT840, or rather it will plug into the CAT
jack.

I have not found where Hamlib gets called or used and not sure how to fix
the problem. The CAT cable appears to sort of work but not really. The
only thing that seems to do anything is the "Tune" option which causes the
Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is
not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY






Georgina


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



















Georgina


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






James Anderson
 

I have a fake PL2303 USB to serial lead for the FT857.
I didn't know it at the time as it ran fine for several years until the update stuffed it for me.

I followed these instructions to install the drivers for this lead.
http://www.totalcardiagnostics.com/support/Knowledgebase/Article/View/92/20/prolific-usb-to-serial-fix-official-solution-to-code-10-error

If I don't do this "procedure"  then in device manager it tells me in very bold writing, that this isn't a prolific device etc etc etc...

It's the only way that I've found to over come this with the current lead that I have.

It's the only way I have found to get the correct driver installed.

Windows updates will bugger this up for you so keep this install handy as you will have to do it every now and then.

It basically installs the driver for the Prolific USB to serial Comm port Version 3.3.2.102 (24/09/2008) and is the only one that I've found to work.

I've literally just used this download and installed this driver again to verify that it works but please don't flame me if things go wrong on your machine. I only say this to cover myself but It has just worked for me.

Run the installer with the lead unplugged and then follow the prompts.

Hope this helps.


James Anderson
 

Jim take a look at this site.

http://www.totalcardiagnostics.com/support/Knowledgebase/Article/View/92/20/prolific-usb-to-serial-fix-official-solution-to-code-10-error

It's how I resolved my issue with a fake lead that I use.

Kind regards, James.


Jim Pruitt
 

Hello Roger.

Even though the ebay seller listed it as a FTDI CAT cable for Yaesu FT900 and others it windows finds it as a Prolific PL2303 which most CAT cables on ebay are saying they are also PL2303 and not FTDI and I found it interesting that there are no YAESU installers on the cd.  The only what I consider name brand was Kenwood and all were for model numbers starting with TK (commercial rigs?) and no amateur radio rigs in the list and all installers including the Baofeng were in packaged "setup.exe" files within each directory so no, there were no "drivers" on the cd, at least none that were not inside of a packaged compressed CAB file.  The seller is telling me to return the cable at my own expense.

Thank you.

Jim Pruitt
WA7DUY


On 1/21/2021 3:01 AM, groups@... wrote:
Since Chirp uses CAT to perform its functions I see no reason why your cable should not work with WSJTX.  A cloning cable is unlikely to have a USB-A socket at one end.  Normally I would expect it to have two identical connectors for the two rigs you are using to clone.

I use the same cable with my IC 7100 for both Chirp and WSJTX.

Can you look through the CD again and double check there are no installation instructions or files with driver?  You must use the drivers supplied with CAT cables for reasons I wont go into on this forum.

73
Roger
G#4HZA

On 21/01/2021 00:19, Jim Pruitt wrote:
The cable was listed as a CAT cable but the mini cd looked like it was a
cloning cable or a Chirp cable.  I will have 3 cables, one for speaker, one
for mic, and the CAT cable.

Thank you
Jim Pruitt
WA7DUY

On Wed, Jan 20, 2021, 3:52 PM Georgina Joyce <gena@...> wrote:

Hello Jim,

With my FT-818 I need to use 2 cables and I am not sure if you will do
too. You might need to get an interface of some kind like a SL USB. See
this thread:

https://www.eham.net/article/2800

Was your cable listed as a cloning cable?

73

On 20 Jan 2021, at 22:45, Jim Pruitt <jpruitt67@...> wrote:

Hello Roger.

Yes, there was a mini cd provided with the cable...but it had no Windows
drivers on it!  It looked like a Chirp installer to me as Windows found no
drivers to install from that disc.  For that reason I went to the Prolific
support sight and grabbed the driver from there.

Thank you.

Jim Pruitt
WA7DUY

On 1/20/2021 2:41 PM, groups@... wrote:

Was there a disc supplied with the cable?  If so did you install the
driver from the disc?

73
Roger

On 20/01/2021 21:22, Jim Pruitt wrote:

Hello Georgina.

Sorry about that.  I am using a Windows 7 desktop.  The cable installs as
a Prolific2303 cable on Com3 (USB) at 19,200 baud. That part I have matched
in WSJT-X but the only thing that sort of worked was putting the FT840 in
tune mode which emits a low tone from the FT840 but does not put it in
tune.  No other function works and it does not read the VFO and I suspect
that is why hamlib gets upset but I see no way to do anything with hamlib.
If I check the "use hamlib" checkbox and hit initialize it kicks the error
and then unchecks the checkbox no matter what parameters I have set.

Someone said I need to configure the USB Comm port for 9600 baud rather
than 19,200.  For the record, FLDigi would not work with it either so I
notified the ebay seller that I want my money back on the cable since the
listed it as a FTDI chip cable.  I do have the right Prolific drivers but
have tried 3 different version.  I do also use Chirp and those prolific
cables work so I am pretty sure my problem is probably the new CAT cable
but wanted some way to verify that.

Thank you.

Jim Pruitt
WA7DUY


On 1/20/2021 1:15 PM, Georgina Joyce wrote:

Hello Jim,

You haven't stated what operating system you are using. You mention chirp
which leads me to linux but chirp can be run on other operating systems.

So you need to identify what port the cable is assigned. Under Windows
device manager comm ports. Or Linux lsusb. Then you need to match port
settings. Cat control is different to the audio settings.

73

On 20 Jan 2021, at 19:43, Jim Pruitt <jpruitt67@...
<mailto:jpruitt67@...> <jpruitt67@...>> wrote:

I have had a version of WSJT-X installed for a while but haven't used it.
I have version 2.2.2 installed now.  I finally bought a CAT cable for my
Yaesu FT840 that arrived a few days ago but I am not able to do anything
with it.  The cable was described as a FTDI cable (not sure when Prolific
started making FTDI chips).  Since I have Chirp installed I had the
Prolific driver but the cable will not work no matter which version of the
Prolific PL2303 driver  I try to use. I am decoding FT8 signals so WSJT-X
works but it keeps constantly kicking the error:
Hamlib error: Invalid parameter while testing getting current VFO

No matter what settings I use or change it kicks that error about every 30
seconds and selecting OK or cancel will kick me out of WSJT-X program and
closes it.  Picking "configurations" just leaves me in the config
settings.  It will not read or change the VFO or mode or anything else
about the rig.  The cable is a Prolific2303 cable with a cat plug on the
end that matches (I assume) the FT840, or rather it will plug into the CAT
jack.

I have not found where Hamlib gets called or used and not sure how to fix
the problem.  The CAT cable appears to sort of work but not really.  The
only thing that seems to do anything is the "Tune" option which causes the
Yaesu FT840 to emit a low tone indicating that it is in tune mode but it is
not in tune mode.

What am I missing?

Thank you.

Jim Pruitt
WA7DUY






Georgina


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



















Georgina


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