Locked Hamlib error whilst switching VFOs with Yaesu FT-8*7 Radio’s


Colin Hendry
 

Hello,
 I know this subject has been talked about in the past and I have searched on here but still cannot find an answer. Does anyone know exactly where the fault lies or have a fix/work around. I take it is not a WSJT software fault but that’s as much as I know. Please any help will be gratefully recieved. I am trying to use the 897 in VHF more but it still does work in HF mode.

Colin G0ODR


Jerry K6ANI
 

Colin,

I looked into the Hamlib interface for my Yaest FT-817 when I first started using WSJT-X to see if I could get Split Operation to work in the Rig mode. I came to the conclusion that there are limitations in the CAT commands of the Yaesu FT-817 that would not allow this to work.

WSJT-X uses Hamlib for its rig control. Hamlib for the Yaesu FT-8*7 and a few of the other Yaesu radios does not have the capability to change the VFO to a specific VFO (A or B). This is because the documented Yaesu CAT commands in these radios do not have commands to select a specific VFO for operation. There are only commands to swap the current VFO between A and B, but not to select the current VFO. Also, if you are trying to use WSJT-X with Split Operation set to Rig, Hamlib won't work properly, since it won't know which VFO is the Transmit VFO and which one is the Receive VFO.

If the error you are seeing in WSJT-X is what I suspect it is, you cannot use Rig for the Split Operation control. There is no documented Yaesu command to do this reliably. For instance, if you manually switch the A/B VFO from the front panel, the Transmit and Receive frequencies will switch too, and WSJT-X will get confused, probably transmitting on the wrong frequency.

I looked up in Google the following:

hamlib ft-817 split

Back in 2005, there was a whole set of discussions on whether Hamlib should include some of the unofficial, discovered "backdoor" commands, usually using EEPROM Reads/Writes to undocumented locations inside the FT-817. It was decided back then that the only reliable way of controlling these Yaesu radios from a computer was to use only the Yaesu-documented CAT commands, in case Yaesu changed the location or format of the EEPROM in other, newer Firmware for the radios. Also, since all the Yaesu CAT commands have no error checking, such as a command checksum, any writes to EEPROM could potentially corrupt an unknown address in EEPROM, possibly corrupting the EEPROM so the radio wouldn't work. There was one documented case I came across where an operator was doing EEPROM writes and the battery ran down, causing the radio to no longer work (it was "bricked").

Hamlib is Public Domain software. If you or a friend know how to program C software, you could potentially create your own version of Hamlib with some of these undocumented features in it, that would let you do some of the things you need to do, then use it in WSJT-X. However, if there are any upgrades to the original Hamlib, you would have to upgrade your version too.

I believe the best way to set up WSJT-X for the Yaesu FT-8*7 series is to set the Split Operation to Fake It. Also, verify the radio has Split turned off before you start WSJT-X. And as long as you don't switch the VFO A/B manually on the radio, this should work.

For my specific interface to my FT-817, I have used both CAT and RTS for the PTT Method. I use the default Transmit Audio Source, since I can't change it. I use the Mode set to USB.

On the CAT Control, I set it to 38400 (and configure the radio to the same), everything else default, and the Force Control Lines off.

So, if there is a problem with Hamlib, it appears the official release won't be changed in the near future. However, if you want, you can contact the Developers of Hamlib to see if they have more information on this, or if they see an error that needs to be corrected.

Hope some of this helps.

--
Jerry K6ANI


Colin Hendry
 

Thanks Jerry for the information. I am sure that I have tried all combinations of the settings but will try your suggestions.

Colin G0ODR

On 16 Oct 2019, at 19:40, Jeri <jerihara00@...> wrote:

Colin,

I looked into the Hamlib interface for my Yaest FT-817 when I first started using WSJT-X to see if I could get Split Operation to work in the Rig mode. I came to the conclusion that there are limitations in the CAT commands of the Yaesu FT-817 that would not allow this to work.

WSJT-X uses Hamlib for its rig control. Hamlib for the Yaesu FT-8*7 and a few of the other Yaesu radios does not have the capability to change the VFO to a specific VFO (A or B). This is because the documented Yaesu CAT commands in these radios do not have commands to select a specific VFO for operation. There are only commands to swap the current VFO between A and B, but not to select the current VFO. Also, if you are trying to use WSJT-X with Split Operation set to Rig, Hamlib won't work properly, since it won't know which VFO is the Transmit VFO and which one is the Receive VFO.

If the error you are seeing in WSJT-X is what I suspect it is, you cannot use Rig for the Split Operation control. There is no documented Yaesu command to do this reliably. For instance, if you manually switch the A/B VFO from the front panel, the Transmit and Receive frequencies will switch too, and WSJT-X will get confused, probably transmitting on the wrong frequency.

I looked up in Google the following:

hamlib ft-817 split

Back in 2005, there was a whole set of discussions on whether Hamlib should include some of the unofficial, discovered "backdoor" commands, usually using EEPROM Reads/Writes to undocumented locations inside the FT-817. It was decided back then that the only reliable way of controlling these Yaesu radios from a computer was to use only the Yaesu-documented CAT commands, in case Yaesu changed the location or format of the EEPROM in other, newer Firmware for the radios. Also, since all the Yaesu CAT commands have no error checking, such as a command checksum, any writes to EEPROM could potentially corrupt an unknown address in EEPROM, possibly corrupting the EEPROM so the radio wouldn't work. There was one documented case I came across where an operator was doing EEPROM writes and the battery ran down, causing the radio to no longer work (it was "bricked").

Hamlib is Public Domain software. If you or a friend know how to program C software, you could potentially create your own version of Hamlib with some of these undocumented features in it, that would let you do some of the things you need to do, then use it in WSJT-X. However, if there are any upgrades to the original Hamlib, you would have to upgrade your version too.

I believe the best way to set up WSJT-X for the Yaesu FT-8*7 series is to set the Split Operation to Fake It. Also, verify the radio has Split turned off before you start WSJT-X. And as long as you don't switch the VFO A/B manually on the radio, this should work.

For my specific interface to my FT-817, I have used both CAT and RTS for the PTT Method. I use the default Transmit Audio Source, since I can't change it. I use the Mode set to USB.

On the CAT Control, I set it to 38400 (and configure the radio to the same), everything else default, and the Force Control Lines off.

So, if there is a problem with Hamlib, it appears the official release won't be changed in the near future. However, if you want, you can contact the Developers of Hamlib to see if they have more information on this, or if they see an error that needs to be corrected.

Hope some of this helps.

--
Jerry K6ANI
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#4364): https://groups.io/g/WSJTX/message/4364
Mute This Topic: https://groups.io/mt/34534651/902438
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/2897073/2073172639/xyzzy [colin.hendry23@...]
-=-=-=-=-=-=-=-=-=-=-=-


Colin Hendry
 

Hello again Jerry,

                Justtried the settings and re read your email several times. I am not trying to use split mode so its a shame that we can not disable the option in WSJT or I guess more importantly hamlib. I have just tried to find the hamlib file on the PC and it does not appear in a search. Don’t suppose you can remember what it is called and or where it would be saved?

 

Thanks again for replying,

 

Colin G0ODR

 

From: Jeri
Sent: 16 October 2019 21:12
To: WSJTX@groups.io
Subject: Re: [WSJTX] Hamlib error whilst switching VFOs with Yaesu FT-8*7 Radio’s

 

Colin,

 

I looked into the Hamlib interface for my Yaest FT-817 when I first started using WSJT-X to see if I could get Split Operation to work in the Rig mode. I came to the conclusion that there are limitations in the CAT commands of the Yaesu FT-817 that would not allow this to work.

 

WSJT-X uses Hamlib for its rig control. Hamlib for the Yaesu FT-8*7 and a few of the other Yaesu radios does not have the capability to change the VFO to a specific VFO (A or B). This is because the documented Yaesu CAT commands in these radios do not have commands to select a specific VFO for operation. There are only commands to swap the current VFO between A and B, but not to select the current VFO. Also, if you are trying to use WSJT-X with Split Operation set to Rig, Hamlib won't work properly, since it won't know which VFO is the Transmit VFO and which one is the Receive VFO.

 

If the error you are seeing in WSJT-X is what I suspect it is, you cannot use Rig for the Split Operation control. There is no documented Yaesu command to do this reliably. For instance, if you manually switch the A/B VFO from the front panel, the Transmit and Receive frequencies will switch too, and WSJT-X will get confused, probably transmitting on the wrong frequency.

 

I looked up in Google the following:

 

   hamlib ft-817 split

 

Back in 2005, there was a whole set of discussions on whether Hamlib should include some of the unofficial, discovered "backdoor" commands, usually using EEPROM Reads/Writes to undocumented locations inside the FT-817. It was decided back then that the only reliable way of controlling these Yaesu radios from a computer was to use only the Yaesu-documented CAT commands, in case Yaesu changed the location or format of the EEPROM in other, newer Firmware for the radios. Also, since all the Yaesu CAT commands have no error checking, such as a command checksum, any writes to EEPROM could potentially corrupt an unknown address in EEPROM, possibly corrupting the EEPROM so the radio wouldn't work. There was one documented case I came across where an operator was doing EEPROM writes and the battery ran down, causing the radio to no longer work (it was "bricked").

 

Hamlib is Public Domain software. If you or a friend know how to program C software, you could potentially create your own version of Hamlib with some of these undocumented features in it, that would let you do some of the things you need to do, then use it in WSJT-X. However, if there are any upgrades to the original Hamlib, you would have to upgrade your version too.

 

I believe the best way to set up WSJT-X for the Yaesu FT-8*7 series is to set the Split Operation to Fake It. Also, verify the radio has Split turned off before you start WSJT-X. And as long as you don't switch the VFO A/B manually on the radio, this should work.

 

For my specific interface to my FT-817, I have used both CAT and RTS for the PTT Method. I use the default Transmit Audio Source, since I can't change it. I use the Mode set to USB.

 

On the CAT Control, I set it to 38400 (and configure the radio to the same), everything else default, and the Force Control Lines off.

 

So, if there is a problem with Hamlib, it appears the official release won't be changed in the near future. However, if you want, you can contact the Developers of Hamlib to see if they have more information on this, or if they see an error that needs to be corrected.

 

Hope some of this helps.

 

--

Jerry K6ANI

 


Jerry K6ANI
 

Colin,

Yes, I was assuming you were asking about the Split Mode. So my reply was addressed to that question.

I couldn't find any more information on using Hamlib with WSJT-X, so I don't think I can help you further. Maybe some of the Developers here can answer your question.

--
Jerry K6ANI


les bannon <wf5e@...>
 

Mmkm

Sent from my iPhone

On Oct 18, 2019, at 4:13 AM, Colin Hendry via Groups.Io <colin.hendry23@...> wrote:

Hello again Jerry,

                Justtried the settings and re read your email several times. I am not trying to use split mode so its a shame that we can not disable the option in WSJT or I guess more importantly hamlib. I have just tried to find the hamlib file on the PC and it does not appear in a search. Don’t suppose you can remember what it is called and or where it would be saved?

 

Thanks again for replying,

 

Colin G0ODR

 

From: Jeri
Sent: 16 October 2019 21:12
To: WSJTX@groups.io
Subject: Re: [WSJTX] Hamlib error whilst switching VFOs with Yaesu FT-8*7 Radio’s

 

Colin,

 

I looked into the Hamlib interface for my Yaest FT-817 when I first started using WSJT-X to see if I could get Split Operation to work in the Rig mode. I came to the conclusion that there are limitations in the CAT commands of the Yaesu FT-817 that would not allow this to work.

 

WSJT-X uses Hamlib for its rig control. Hamlib for the Yaesu FT-8*7 and a few of the other Yaesu radios does not have the capability to change the VFO to a specific VFO (A or B). This is because the documented Yaesu CAT commands in these radios do not have commands to select a specific VFO for operation. There are only commands to swap the current VFO between A and B, but not to select the current VFO. Also, if you are trying to use WSJT-X with Split Operation set to Rig, Hamlib won't work properly, since it won't know which VFO is the Transmit VFO and which one is the Receive VFO.

 

If the error you are seeing in WSJT-X is what I suspect it is, you cannot use Rig for the Split Operation control. There is no documented Yaesu command to do this reliably. For instance, if you manually switch the A/B VFO from the front panel, the Transmit and Receive frequencies will switch too, and WSJT-X will get confused, probably transmitting on the wrong frequency.

 

I looked up in Google the following:

 

   hamlib ft-817 split

 

Back in 2005, there was a whole set of discussions on whether Hamlib should include some of the unofficial, discovered "backdoor" commands, usually using EEPROM Reads/Writes to undocumented locations inside the FT-817. It was decided back then that the only reliable way of controlling these Yaesu radios from a computer was to use only the Yaesu-documented CAT commands, in case Yaesu changed the location or format of the EEPROM in other, newer Firmware for the radios. Also, since all the Yaesu CAT commands have no error checking, such as a command checksum, any writes to EEPROM could potentially corrupt an unknown address in EEPROM, possibly corrupting the EEPROM so the radio wouldn't work. There was one documented case I came across where an operator was doing EEPROM writes and the battery ran down, causing the radio to no longer work (it was "bricked").

 

Hamlib is Public Domain software. If you or a friend know how to program C software, you could potentially create your own version of Hamlib with some of these undocumented features in it, that would let you do some of the things you need to do, then use it in WSJT-X. However, if there are any upgrades to the original Hamlib, you would have to upgrade your version too.

 

I believe the best way to set up WSJT-X for the Yaesu FT-8*7 series is to set the Split Operation to Fake It. Also, verify the radio has Split turned off before you start WSJT-X. And as long as you don't switch the VFO A/B manually on the radio, this should work.

 

For my specific interface to my FT-817, I have used both CAT and RTS for the PTT Method. I use the default Transmit Audio Source, since I can't change it. I use the Mode set to USB.

 

On the CAT Control, I set it to 38400 (and configure the radio to the same), everything else default, and the Force Control Lines off.

 

So, if there is a problem with Hamlib, it appears the official release won't be changed in the near future. However, if you want, you can contact the Developers of Hamlib to see if they have more information on this, or if they see an error that needs to be corrected.

 

Hope some of this helps.

 

--

Jerry K6ANI

 

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#4376): https://groups.io/g/WSJTX/message/4376
Mute This Topic: https://groups.io/mt/34534651/365855
-=-=-
Moderated by Andy K3UK and Roger G4HZA
-=-=-
Group Owner: WSJTX+owner@groups.io
Unsubscribe: https://groups.io/g/WSJTX/leave/4276938/734291875/xyzzy  [wf5e@...]
-=-=-=-=-=-=-=-=-=-=-=-