Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Black Michael via wsjt-devel
I just tested an FT-897 with a user yesterday and it's working fine in the 
latest hamlib.
So hopefully whatever problem was being experienced has been fixed for the 817 
and 897.
Mike W9MDB

 

 On Thursday, July 2, 2020, 07:45:18 AM CDT, Bill Somerville 
 wrote:  
 
  Hi Mike, 
  we have had one report of a failure which turned out to be a CAT baud rate 
setting issue. As far as I know it faithfully emulated the FT-817ND and that 
model can be used without change, surprisingly including the EEPROM reads that 
are used when being forced to use the FT-857 model backend. I would have 
thought that there are enough FT-818NDs out their with WSJT-X to say that 
there's no issue. 
  Note I cannot say much about the FT-817ND backend as in the Hamlib shipped 
with WSJT-X v2.2.2 that model is broken as is the FT-897. 
  73
 Bill
 G4WJS. 
  On 02/07/2020 13:21, Black Michael via wsjt-devel wrote:
  
   Bill..have you found the FT-818ND to be compatible with the FT-817ND 
backend? Perhaps should add that to the riglist so they don't feel like 
orphans. 
  Mike W9MDB 
   

  
  On Thursday, July 2, 2020, 07:15:04 AM CDT, Bill Somerville 
 wrote:  
  
 On 02/07/2020 13:02, Claude Frantz wrote:
  
On 7/2/20 1:27 PM, Bill Somerville wrote: 
 
 Many thanks, Bill ! 
 
 
there are several issues with that series of rigs (you can include the new 
FT-818ND in the list too), as there are with almost all rigs. All have 
workarounds, why are you asking please, that will help focus on how to answer? 
 
 
 I do not have any rig from this series. I'm only asking in order to remain 
informed. I have observed many work, in the recent past. 
 
 Thank you ! 
 
 Best wishes, 
 Claude (DJ0OT) 
 
 
Hi Claude,
 
there are a few specific issues with CAT control of these rigs, which all 
essentially have identical CAT protocols.

   - The CAT command set is small and many rig functions cannot be queried or 
set.
   - There is no easy way to determine whether VFO A, VFO B, or memory is 
current, just a CAT command swap them over. The basic queries of frequency and 
mode simply return that of the current VFO or memory.
   - The CAT command to determine if the rig is in SEND mode does not work as 
advertised.
   - CAT commands to change frequency are rejected if the rig is in SEND mode, 
despite the fact that the rig can be tuned with the front panel VFO knob when 
transmitting.
 
As I said, most rigs have a number of limitations and quirks, these ones are 
not particularly better or worse than others.
 
73
 
 Bill 
 G4WJS. 
 

 
 ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Black Michael via wsjt-devel
The FT-991 is in the list.  Is there any particular problem with the FT-991A 
that would require changes?
Mike W9MDB

 

On Thursday, July 2, 2020, 08:39:14 AM CDT, N1trk Rob 
 wrote:  
 
 Michael, sorry.  I rolled back windows 10.  Wsjt x worked fine after that.  
The "list" would be the drop down list for rig set up in wsjt x.  I also use a 
flex 6600 which has worked flawlessly with wsjt x every time.  Thank you for 
all of your hard work.Robn1trk
On Thu, Jul 2, 2020 at 9:25 AM Black Michael via wsjt-devel 
 wrote:

 "get on the list" for what?When you say you rolled back to a previous version 
you mean Windows or WSJT-X?
Mike W9MDB

 

On Thursday, July 2, 2020, 08:12:33 AM CDT, N1trk Rob 
 wrote:  
 
 I use an ft991A, yaesu's most current rig in the hf/vhf line.  I had a hamlib 
error after a windows update which of course happened Saturday morning of field 
day with no internet :).  I rolled back to a previous version and fb.  The 
yaesu ft 991 a has regularly been a bear to configure.  Perhaps we could get on 
the list as well?  (I have no programming experience worthwhile. [ I do 
remember error 19, semicolon expected] )   I truly appreciate all your hard 
and VOLUNTEER work, and graciously submit this for your consideration.73
robn1trk
On Thu, Jul 2, 2020 at 8:45 AM Bill Somerville  wrote:

  Hi Mike, 
  we have had one report of a failure which turned out to be a CAT baud rate 
setting issue. As far as I know it faithfully emulated the FT-817ND and that 
model can be used without change, surprisingly including the EEPROM reads that 
are used when being forced to use the FT-857 model backend. I would have 
thought that there are enough FT-818NDs out their with WSJT-X to say that 
there's no issue. 
  Note I cannot say much about the FT-817ND backend as in the Hamlib shipped 
with WSJT-X v2.2.2 that model is broken as is the FT-897. 
  73
 Bill
 G4WJS. 
  On 02/07/2020 13:21, Black Michael via wsjt-devel wrote:
  
   Bill..have you found the FT-818ND to be compatible with the FT-817ND 
backend? Perhaps should add that to the riglist so they don't feel like 
orphans. 
  Mike W9MDB 
   

  
  On Thursday, July 2, 2020, 07:15:04 AM CDT, Bill Somerville 
 wrote:  
  
 On 02/07/2020 13:02, Claude Frantz wrote:
  
On 7/2/20 1:27 PM, Bill Somerville wrote: 
 
 Many thanks, Bill ! 
 
 
there are several issues with that series of rigs (you can include the new 
FT-818ND in the list too), as there are with almost all rigs. All have 
workarounds, why are you asking please, that will help focus on how to answer? 
 
 
 I do not have any rig from this series. I'm only asking in order to remain 
informed. I have observed many work, in the recent past. 
 
 Thank you ! 
 
 Best wishes, 
 Claude (DJ0OT) 
 
 
Hi Claude,
 
there are a few specific issues with CAT control of these rigs, which all 
essentially have identical CAT protocols.

   - The CAT command set is small and many rig functions cannot be queried or 
set.
   - There is no easy way to determine whether VFO A, VFO B, or memory is 
current, just a CAT command swap them over. The basic queries of frequency and 
mode simply return that of the current VFO or memory.
   - The CAT command to determine if the rig is in SEND mode does not work as 
advertised.
   - CAT commands to change frequency are rejected if the rig is in SEND mode, 
despite the fact that the rig can be tuned with the front panel VFO knob when 
transmitting.
 
As I said, most rigs have a number of limitations and quirks, these ones are 
not particularly better or worse than others.
 
73
 
 Bill 
 G4WJS. 
 

 
 ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread N1trk Rob
Michael, sorry.  I rolled back windows 10.  Wsjt x worked fine after that.
The "list" would be the drop down list for rig set up in wsjt x.  I also
use a flex 6600 which has worked flawlessly with wsjt x every time.
Thank you for all of your hard work.
Rob
n1trk

On Thu, Jul 2, 2020 at 9:25 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:

>  "get on the list" for what?
> When you say you rolled back to a previous version you mean Windows or
> WSJT-X?
>
> Mike W9MDB
>
>
>
>
> On Thursday, July 2, 2020, 08:12:33 AM CDT, N1trk Rob <
> litchrob...@gmail.com> wrote:
>
>
> I use an ft991A, yaesu's most current rig in the hf/vhf line.  I had a
> hamlib error after a windows update which of course happened Saturday
> morning of field day with no internet :).  I rolled back to a previous
> version and fb.  The yaesu ft 991 a has regularly been a bear to
> configure.  Perhaps we could get on the list as well?  (I have no
> programming experience worthwhile. [ I do remember error 19, semicolon
> expected] )   I truly appreciate all your hard and VOLUNTEER work, and
> graciously submit this for your consideration.
> 73
> rob
> n1trk
>
> On Thu, Jul 2, 2020 at 8:45 AM Bill Somerville 
> wrote:
>
> Hi Mike,
>
> we have had one report of a failure which turned out to be a CAT baud rate
> setting issue. As far as I know it faithfully emulated the FT-817ND and
> that model can be used without change, surprisingly including the EEPROM
> reads that are used when being forced to use the FT-857 model backend. I
> would have thought that there are enough FT-818NDs out their with WSJT-X to
> say that there's no issue.
>
> Note I cannot say much about the FT-817ND backend as in the Hamlib shipped
> with WSJT-X v2.2.2 that model is broken as is the FT-897.
>
> 73
> Bill
> G4WJS.
>
> On 02/07/2020 13:21, Black Michael via wsjt-devel wrote:
>
> Bill..have you found the FT-818ND to be compatible with the FT-817ND
> backend?
> Perhaps should add that to the riglist so they don't feel like orphans.
>
> Mike W9MDB
>
>
>
>
> On Thursday, July 2, 2020, 07:15:04 AM CDT, Bill Somerville
>   wrote:
>
>
> On 02/07/2020 13:02, Claude Frantz wrote:
>
> On 7/2/20 1:27 PM, Bill Somerville wrote:
>
> Many thanks, Bill !
>
> there are several issues with that series of rigs (you can include the new
> FT-818ND in the list too), as there are with almost all rigs. All have
> workarounds, why are you asking please, that will help focus on how to
> answer?
>
>
> I do not have any rig from this series. I'm only asking in order to remain
> informed. I have observed many work, in the recent past.
>
> Thank you !
>
> Best wishes,
> Claude (DJ0OT)
>
> Hi Claude,
>
> there are a few specific issues with CAT control of these rigs, which all
> essentially have identical CAT protocols.
>
>- The CAT command set is small and many rig functions cannot be
>queried or set.
>- There is no easy way to determine whether VFO A, VFO B, or memory is
>current, just a CAT command swap them over. The basic queries of frequency
>and mode simply return that of the current VFO or memory.
>- The CAT command to determine if the rig is in SEND mode does not
>work as advertised.
>- CAT commands to change frequency are rejected if the rig is in SEND
>mode, despite the fact that the rig can be tuned with the front panel VFO
>knob when transmitting.
>
> As I said, most rigs have a number of limitations and quirks, these ones
> are not particularly better or worse than others.
>
> 73
>
> Bill
>
> G4WJS.
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Black Michael via wsjt-devel
 "get on the list" for what?When you say you rolled back to a previous version 
you mean Windows or WSJT-X?
Mike W9MDB

 

On Thursday, July 2, 2020, 08:12:33 AM CDT, N1trk Rob 
 wrote:  
 
 I use an ft991A, yaesu's most current rig in the hf/vhf line.  I had a hamlib 
error after a windows update which of course happened Saturday morning of field 
day with no internet :).  I rolled back to a previous version and fb.  The 
yaesu ft 991 a has regularly been a bear to configure.  Perhaps we could get on 
the list as well?  (I have no programming experience worthwhile. [ I do 
remember error 19, semicolon expected] )   I truly appreciate all your hard 
and VOLUNTEER work, and graciously submit this for your consideration.73
robn1trk
On Thu, Jul 2, 2020 at 8:45 AM Bill Somerville  wrote:

  Hi Mike, 
  we have had one report of a failure which turned out to be a CAT baud rate 
setting issue. As far as I know it faithfully emulated the FT-817ND and that 
model can be used without change, surprisingly including the EEPROM reads that 
are used when being forced to use the FT-857 model backend. I would have 
thought that there are enough FT-818NDs out their with WSJT-X to say that 
there's no issue. 
  Note I cannot say much about the FT-817ND backend as in the Hamlib shipped 
with WSJT-X v2.2.2 that model is broken as is the FT-897. 
  73
 Bill
 G4WJS. 
  On 02/07/2020 13:21, Black Michael via wsjt-devel wrote:
  
   Bill..have you found the FT-818ND to be compatible with the FT-817ND 
backend? Perhaps should add that to the riglist so they don't feel like 
orphans. 
  Mike W9MDB 
   

  
  On Thursday, July 2, 2020, 07:15:04 AM CDT, Bill Somerville 
 wrote:  
  
 On 02/07/2020 13:02, Claude Frantz wrote:
  
On 7/2/20 1:27 PM, Bill Somerville wrote: 
 
 Many thanks, Bill ! 
 
 
there are several issues with that series of rigs (you can include the new 
FT-818ND in the list too), as there are with almost all rigs. All have 
workarounds, why are you asking please, that will help focus on how to answer? 
 
 
 I do not have any rig from this series. I'm only asking in order to remain 
informed. I have observed many work, in the recent past. 
 
 Thank you ! 
 
 Best wishes, 
 Claude (DJ0OT) 
 
 
Hi Claude,
 
there are a few specific issues with CAT control of these rigs, which all 
essentially have identical CAT protocols.

   - The CAT command set is small and many rig functions cannot be queried or 
set.
   - There is no easy way to determine whether VFO A, VFO B, or memory is 
current, just a CAT command swap them over. The basic queries of frequency and 
mode simply return that of the current VFO or memory.
   - The CAT command to determine if the rig is in SEND mode does not work as 
advertised.
   - CAT commands to change frequency are rejected if the rig is in SEND mode, 
despite the fact that the rig can be tuned with the front panel VFO knob when 
transmitting.
 
As I said, most rigs have a number of limitations and quirks, these ones are 
not particularly better or worse than others.
 
73
 
 Bill 
 G4WJS. 
 

 
 ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Claude Frantz

On 7/2/20 2:11 PM, Bill Somerville wrote:

there are several issues with that series of rigs (you can include 
the new FT-818ND in the list too), as there are with almost all rigs. 
All have workarounds, why are you asking please, that will help focus 
on how to answer?


Many thanks again, Bill !

Just an additional question: Is the FT-991(A) concerned too ?

Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread N1trk Rob
I use an ft991A, yaesu's most current rig in the hf/vhf line.  I had a
hamlib error after a windows update which of course happened Saturday
morning of field day with no internet :).  I rolled back to a previous
version and fb.  The yaesu ft 991 a has regularly been a bear to
configure.  Perhaps we could get on the list as well?  (I have no
programming experience worthwhile. [ I do remember error 19, semicolon
expected] )   I truly appreciate all your hard and VOLUNTEER work, and
graciously submit this for your consideration.
73
rob
n1trk

On Thu, Jul 2, 2020 at 8:45 AM Bill Somerville 
wrote:

> Hi Mike,
>
> we have had one report of a failure which turned out to be a CAT baud rate
> setting issue. As far as I know it faithfully emulated the FT-817ND and
> that model can be used without change, surprisingly including the EEPROM
> reads that are used when being forced to use the FT-857 model backend. I
> would have thought that there are enough FT-818NDs out their with WSJT-X to
> say that there's no issue.
>
> Note I cannot say much about the FT-817ND backend as in the Hamlib shipped
> with WSJT-X v2.2.2 that model is broken as is the FT-897.
>
> 73
> Bill
> G4WJS.
>
> On 02/07/2020 13:21, Black Michael via wsjt-devel wrote:
>
> Bill..have you found the FT-818ND to be compatible with the FT-817ND
> backend?
> Perhaps should add that to the riglist so they don't feel like orphans.
>
> Mike W9MDB
>
>
>
>
> On Thursday, July 2, 2020, 07:15:04 AM CDT, Bill Somerville
>   wrote:
>
>
> On 02/07/2020 13:02, Claude Frantz wrote:
>
> On 7/2/20 1:27 PM, Bill Somerville wrote:
>
> Many thanks, Bill !
>
> there are several issues with that series of rigs (you can include the new
> FT-818ND in the list too), as there are with almost all rigs. All have
> workarounds, why are you asking please, that will help focus on how to
> answer?
>
>
> I do not have any rig from this series. I'm only asking in order to remain
> informed. I have observed many work, in the recent past.
>
> Thank you !
>
> Best wishes,
> Claude (DJ0OT)
>
> Hi Claude,
>
> there are a few specific issues with CAT control of these rigs, which all
> essentially have identical CAT protocols.
>
>- The CAT command set is small and many rig functions cannot be
>queried or set.
>- There is no easy way to determine whether VFO A, VFO B, or memory is
>current, just a CAT command swap them over. The basic queries of frequency
>and mode simply return that of the current VFO or memory.
>- The CAT command to determine if the rig is in SEND mode does not
>work as advertised.
>- CAT commands to change frequency are rejected if the rig is in SEND
>mode, despite the fact that the rig can be tuned with the front panel VFO
>knob when transmitting.
>
> As I said, most rigs have a number of limitations and quirks, these ones
> are not particularly better or worse than others.
>
> 73
>
> Bill
>
> G4WJS.
>
>
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Bill Somerville

Hi Mike,

we have had one report of a failure which turned out to be a CAT baud 
rate setting issue. As far as I know it faithfully emulated the FT-817ND 
and that model can be used without change, surprisingly including the 
EEPROM reads that are used when being forced to use the FT-857 model 
backend. I would have thought that there are enough FT-818NDs out their 
with WSJT-X to say that there's no issue.


Note I cannot say much about the FT-817ND backend as in the Hamlib 
shipped with WSJT-X v2.2.2 that model is broken as is the FT-897.


73
Bill
G4WJS.

On 02/07/2020 13:21, Black Michael via wsjt-devel wrote:
Bill..have you found the FT-818ND to be compatible with the FT-817ND 
backend?

Perhaps should add that to the riglist so they don't feel like orphans.

Mike W9MDB




On Thursday, July 2, 2020, 07:15:04 AM CDT, Bill Somerville 
 wrote:



On 02/07/2020 13:02, Claude Frantz wrote:

On 7/2/20 1:27 PM, Bill Somerville wrote:

Many thanks, Bill !

there are several issues with that series of rigs (you can include 
the new FT-818ND in the list too), as there are with almost all 
rigs. All have workarounds, why are you asking please, that will 
help focus on how to answer?


I do not have any rig from this series. I'm only asking in order to 
remain informed. I have observed many work, in the recent past.


Thank you !

Best wishes,
Claude (DJ0OT)


Hi Claude,

there are a few specific issues with CAT control of these rigs, which 
all essentially have identical CAT protocols.


  * The CAT command set is small and many rig functions cannot be
queried or set.
  * There is no easy way to determine whether VFO A, VFO B, or memory
is current, just a CAT command swap them over. The basic queries
of frequency and mode simply return that of the current VFO or memory.
  * The CAT command to determine if the rig is in SEND mode does not
work as advertised.
  * CAT commands to change frequency are rejected if the rig is in
SEND mode, despite the fact that the rig can be tuned with the
front panel VFO knob when transmitting.

As I said, most rigs have a number of limitations and quirks, these 
ones are not particularly better or worse than others.


73


Bill

G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Black Michael via wsjt-devel
Bill..have you found the FT-818ND to be compatible with the FT-817ND 
backend?Perhaps should add that to the riglist so they don't feel like orphans.
Mike W9MDB

 

On Thursday, July 2, 2020, 07:15:04 AM CDT, Bill Somerville 
 wrote:  
 
  On 02/07/2020 13:02, Claude Frantz wrote:
  
On 7/2/20 1:27 PM, Bill Somerville wrote: 
 
 Many thanks, Bill ! 
 
 
there are several issues with that series of rigs (you can include the new 
FT-818ND in the list too), as there are with almost all rigs. All have 
workarounds, why are you asking please, that will help focus on how to answer? 
 
 
 I do not have any rig from this series. I'm only asking in order to remain 
informed. I have observed many work, in the recent past. 
 
 Thank you ! 
 
 Best wishes, 
 Claude (DJ0OT) 
 
 
Hi Claude,
 
there are a few specific issues with CAT control of these rigs, which all 
essentially have identical CAT protocols.

   - The CAT command set is small and many rig functions cannot be queried or 
set.
   - There is no easy way to determine whether VFO A, VFO B, or memory is 
current, just a CAT command swap them over. The basic queries of frequency and 
mode simply return that of the current VFO or memory.
   - The CAT command to determine if the rig is in SEND mode does not work as 
advertised.
   - CAT commands to change frequency are rejected if the rig is in SEND mode, 
despite the fact that the rig can be tuned with the front panel VFO knob when 
transmitting.
 
As I said, most rigs have a number of limitations and quirks, these ones are 
not particularly better or worse than others.
 
73

 Bill
 G4WJS.
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
  ___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Bill Somerville

On 02/07/2020 13:02, Claude Frantz wrote:

On 7/2/20 1:27 PM, Bill Somerville wrote:

Many thanks, Bill !

there are several issues with that series of rigs (you can include 
the new FT-818ND in the list too), as there are with almost all rigs. 
All have workarounds, why are you asking please, that will help focus 
on how to answer?


I do not have any rig from this series. I'm only asking in order to 
remain informed. I have observed many work, in the recent past.


Thank you !

Best wishes,
Claude (DJ0OT)


Hi Claude,

there are a few specific issues with CAT control of these rigs, which 
all essentially have identical CAT protocols.


 * The CAT command set is small and many rig functions cannot be
   queried or set.
 * There is no easy way to determine whether VFO A, VFO B, or memory is
   current, just a CAT command swap them over. The basic queries of
   frequency and mode simply return that of the current VFO or memory.
 * The CAT command to determine if the rig is in SEND mode does not
   work as advertised.
 * CAT commands to change frequency are rejected if the rig is in SEND
   mode, despite the fact that the rig can be tuned with the front
   panel VFO knob when transmitting.

As I said, most rigs have a number of limitations and quirks, these ones 
are not particularly better or worse than others.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Claude Frantz

On 7/2/20 1:27 PM, Bill Somerville wrote:

Many thanks, Bill !

there are several issues with that series of rigs (you can include the 
new FT-818ND in the list too), as there are with almost all rigs. All 
have workarounds, why are you asking please, that will help focus on how 
to answer?


I do not have any rig from this series. I'm only asking in order to 
remain informed. I have observed many work, in the recent past.


Thank you !

Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Bill Somerville

On 02/07/2020 09:28, Claude Frantz wrote:

Hi all,

Can anyone here give us a short but precise description of the 
problems related to the equipment mentioned in the subject, please ?


Thanks you !

Best wishes,
Claude (DJ0OT)


Hi Claude,

there are several issues with that series of rigs (you can include the 
new FT-818ND in the list too), as there are with almost all rigs. All 
have workarounds, why are you asking please, that will help focus on how 
to answer?


73
Bill
G4WJS.



___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


Re: [wsjt-devel] CAT problems with FT817, FT857 and FT897

2020-07-02 Thread Stephen VK3SIR
Claude,

There issues in some cases are wide and various but based primarily around some 
"byte dropouts" and acknowledgement-of-commands. 

As an example, an issue that is currently being investigated relates to 
acknowledgement of commands (i.e. intermittently 3 bytes returned rather than 
the expected 5).

To quote Mike, he is like 'a dog with a bone' when it comes to understanding 
and resolving issues. Some issues may just be hardware and may only be possibly 
resolved by reporting issues to Linux and hardware developers too ! Great 
technicians and engineers are working on issues but working through issues 
can and does take time especially when you are maintaining generic libraries.

If you are having concerns with the FT-8x7 range of radios (and it seems to be 
limited at this stage to non-Windows builds) then pull Hamlib from the "master" 
repo at Github rather than the WSJTX-standardised G4WJS distribution that the 
developers here have mated the release to. 

It is critical that any issues/concerns be reported via the Hamlib lists.

Here are the build scripts needed (based on the INSTALL file packaged in 
wsjtx.tar) that just worked 100% (after dependencies were resolved for Ubuntu 
Linux 20.04:

For HAMLIB based off the MASTER Hamlib Repo (and for the intent of this forum 
use this repo ONLY if you are experiencing issues with Hamlib comms) as a test:

mkdir ~/hamlib-prefix
cd ~/hamlib-prefix
git clone https://github.com/Hamlib/Hamlib.git src  <<== Change here
cd src  <<== There is no "integration" 
distro to checkout so this is removed
./bootstrap
mkdir ../build
cd ../build
../src/configure --prefix=$HOME/hamlib-prefix \
   --disable-shared --enable-static \
   --without-cxx-binding --disable-winradio \
   CFLAGS="-g -O2 -fdata-sections -ffunction-sections" \
   LDFLAGS="-Wl,--gc-sections"
make
make install-strip

For WSJTX based off the SourceForge Repo:

mkdir -p ~/wsjtx-prefix/build
cd ~/wsjtx-prefix
git clone git://git.code.sf.net/p/wsjt/wsjtx src
cd ~/wsjtx-prefix/build
cmake -D CMAKE_PREFIX_PATH=~/hamlib-prefix -DWSJT_SKIP_MANPAGES=ON 
-DWSJT_GENERATE_DOCS=OFF ../src
cmake --build .
sudo cmake --build . --target install

Also for the core developers: For the next source release, can the INSTALL 
files packaged at the top level of the tarball/within the "wsjtx.tar" tarball 
also be made consistent across the entire package i.e. update/incorporate the 
changes in the WSJT-X Linux build script shown above - referenced in the TOP 
LEVEL INSTALL file but not appearing in the INSTALL file packaged in wsjtx.tar? 

Further to this, can some of the references in these valuable INSTALL documents 
please also be updated and made consistent with current releases (and PM me 
back developers if you would like me to assist)?

Thanks to all developers, and 73.

Steve I
VK3VM / VK3SIR


-Original Message-
From: Claude Frantz  
Sent: Thursday, 2 July 2020 6:28 PM
To: WSJT software development 
Subject: [wsjt-devel] CAT problems with FT817, FT857 and FT897

Hi all,

Can anyone here give us a short but precise description of the problems related 
to the equipment mentioned in the subject, please ?

Thanks you !

Best wishes,
Claude (DJ0OT)


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel


___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel