Hi Michael and Bill
A quick "lunch time" compile and here below are the result , not yet there
but we are on the right path !:-)
Applied patch provided by Michael and recompiled hamlib3 , then compiled
WSJT-X at this morning version 5640 .
1/ WSJT : Hamlib error : invalid parameter while getting current frequency
2/ rigctl requesting frequency , see result below ( same parameter error)
3/ rigctl requesting mode , seems all ok !
So not yet 100% but some interesting progress ... I have put also below the
link to the FT991 CAT documentation released by Yaesu and I will have a look
at the code tonight , but being totally unfamiliar with it , I might rather
rely on your expertise ! :-) it looks the answer is not what is expected .
https://www.yaesu.com/downloadFile.cfm?FileID=8715
<https://www.yaesu.com/downloadFile.cfm?FileID=8715&FileCatID=158&FileName=F
T%2D991%5FCAT%5FOM%5FENG%5F1502%2DB0.pdf&FileContentType=application%2Fpdf>
&FileCatID=158&FileName=FT%2D991%5FCAT%5FOM%5FENG%5F1502%2DB0.pdf&FileConten
tType=application%2Fpdf
Best regards and thanks for your help
Jean Louis F5DJL
PS : I am not an expert on SVN but despite the svn version giving me 5640 as
checkout version , I get the result of the QT-SDK compilation as in the in
about box at 5636 ? totally unrelated but noticed this today !
**********************************************************************
Request frequency NOT OK
C:\hamlib3\bin>rigctl -vvvv -m 135 -r com5 -s 38400 f
rigctl, Hamlib 3.0~git
Report bugs to <[email protected]>
rig:rig_init called
yaesu: initrigs3_yaesu called
rig_register (121)
rig_register (127)
rig_register (110)
rig_register (105)
rig_register (106)
rig_register (107)
rig_register (109)
rig_register (120)
rig_register (101)
rig_register (122)
rig_register (123)
rig_register (111)
rig_register (115)
rig_register (113)
rig_register (114)
rig_register (128)
rig_register (131)
rig_register (116)
rig_register (103)
rig_register (124)
rig_register (104)
rig_register (125)
rig_register (129)
rig_register (132)
rig_register (130)
rig_register (117)
rig_register (119)
rig_register (118)
rig_register (126)
rig_register (133)
rig_register (134)
rig_register (135)
ft991_init called
newcat_init called
rig:rig_open called
newcat_open called
newcat_set_trn called
newcat_valid_command called
newcat_get_vfo called
newcat_valid_command called
Opened rig model 135, 'FT-991'
Backend version: 0.22.1, Status: Alpha
newcat_get_freq called
newcat_valid_command called
get_freq: error = Invalid parameter
rig:rig_close called
newcat_close called
rig:rig_cleanup called
newcat_cleanup called
C:\hamlib3\bin>
************************************************************************
Request Mode OK
C:\hamlib3\bin>rigctl -vvvv -m 135 -r com5 -s 38400 m
rigctl, Hamlib 3.0~git
Report bugs to <[email protected]>
rig:rig_init called
yaesu: initrigs3_yaesu called
rig_register (121)
rig_register (127)
rig_register (110)
rig_register (105)
rig_register (106)
rig_register (107)
rig_register (109)
rig_register (120)
rig_register (101)
rig_register (122)
rig_register (123)
rig_register (111)
rig_register (115)
rig_register (113)
rig_register (114)
rig_register (128)
rig_register (131)
rig_register (116)
rig_register (103)
rig_register (124)
rig_register (104)
rig_register (125)
rig_register (129)
rig_register (132)
rig_register (130)
rig_register (117)
rig_register (119)
rig_register (118)
rig_register (126)
rig_register (133)
rig_register (134)
rig_register (135)
ft991_init called
newcat_init called
rig:rig_open called
newcat_open called
newcat_set_trn called
newcat_valid_command called
newcat_get_vfo called
newcat_valid_command called
Opened rig model 135, 'FT-991'
Backend version: 0.22.1, Status: Alpha
newcat_get_mode called
newcat_valid_command called
newcat_get_rx_bandwidth called
newcat_valid_command called
USB
1800
rig:rig_close called
newcat_close called
rig:rig_cleanup called
newcat_cleanup called
-----Message d'origine-----
De : Michael Black [mailto:[email protected]]
Envoyé : mardi 30 juin 2015 06:14
À : [email protected]
Objet : Re: [wsjt-devel] WSJT-X and FT991 CAT issue - rigctl-wsjtx results
I think (i.e. hope) the attached fixes the problem.
73
Mike W9MDB
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
