Missing support for Yeasu FT 991 in Hamlib

[Hveem]

The support for Yeasu FT-991 appears to be missing in Hamlib.

This GIT does include the mentioned radio, it works if hamlib is compiled and installed from the mentioned GIT.
https://github.com/N0NB/hamlib

The C file that includes the radio is here:
https://github.com/N0NB/hamlib/blob/master/yaesu/ft991.c

[FanJun Kong - ( BH1SCW ) (fjkong)]

I will take this bug

[FanJun Kong - ( BH1SCW ) (fjkong)]

hi Hveem,

I check the changelog and sourcecode, the Yeasu FT-991 ｈａs been supported in it. could you double check again?

[Hveem (krbjhvee)]

On 09. des. 2016 03:02, FanJun Kong - ( BH1SCW ) wrote:
> hi Hveem,
>
> I check the changelog and sourcecode, the Yeasu FT-991 ｈａs been
> supported in it. could you double check again?
>
> ** Changed in: hamlib (Ubuntu)
> Status: New => Incomplete
>

The command rigctld -l does not show it on the list, this is from the
standard repositories in Ubuntu.
rig: loading backend dummy
dummy: _init called
rig_register (1)
rig_register (2)
rig: loading backend yaesu
yaesu: initrigs2_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: loading backend kenwood
initrigs2_kenwood called
rig_register (213)
rig_register (201)
rig_register (225)
rig_register (203)
rig_register (204)
rig_register (216)
rig_register (224)
rig_register (205)
rig_register (207)
rig_register (209)
rig_register (210)
rig_register (222)
rig_register (214)
rig_register (230)
rig_register (221)
rig_register (229)
rig_register (202)
rig_register (211)
rig_register (206)
rig_register (208)
rig_register (215)
rig_register (226)
rig_register (217)
rig_register (233)
rig_register (220)
rig_register (223)
rig_register (227)
rig_register (234)
rig_register (231)
rig_register (231)
rig_register (228)
rig_register (219)
rig_register (232)
rig: loading backend icom
icom: _init called
rig_register (355)
rig_register (309)
rig_register (310)
rig_register (311)
rig_register (313)
rig_register (314)
rig_register (315)
rig_register (319)
rig_register (320)
rig_register (321)
rig_register (322)
rig_register (367)
rig_register (323)
rig_register (346)
rig_register (324)
rig_register (328)
rig_register (330)
rig_register (326)
rig_register (327)
rig_register (347)
rig_register (357)
rig_register (363)
rig_register (329)
rig_register (362)
rig_register (345)
rig_register (356)
rig_register (360)
rig_register (361)
rig_register (331)
rig_register (312)
rig_register (316)
rig_register (332)
rig_register (334)
rig_register (344)
rig_register (368)
rig_register (335)
rig_register (369)
rig_register (336)
rig_register (358)
rig_register (337)
rig_register (338)
rig_register (339)
rig_register (340)
rig_register (341)
rig_register (342)
rig_register (343)
rig_register (366)
rig_register (303)
rig_register (304)
rig_register (306)
rig_register (307)
rig_register (302)
rig_register (352)
rig_register (353)
rig_register (351)
rig_register (364)
rig_register (365)
rig_register (354)
rig: loading backend pcr
pcr: init called
rig_register (402)
rig_register (401)
rig_register (403)
rig_register (404)
rig: loading backend aor
aor: _init called
rig_register (516)
rig_register (508)
rig_register (501)
rig_register (502)
rig_register (513)
rig_register (504)
rig_register (506)
r...

[Hveem (krbjhvee)]

Altso, it is not possible to choose the right radio in wsjtx.

This problem affects both the ubuntu hamradio ppa and the standard
repository.

On 09. des. 2016 09:11, Hveem wrote:
> On 09. des. 2016 03:02, FanJun Kong - ( BH1SCW ) wrote:
>> hi Hveem,
>>
>> I check the changelog and sourcecode, the Yeasu FT-991 ｈａs been
>> supported in it. could you double check again?
>>
>> ** Changed in: hamlib (Ubuntu)
>> Status: New => Incomplete
>>
> The command rigctld -l does not show it on the list, this is from the
> standard repositories in Ubuntu.
> rig: loading backend dummy
> dummy: _init called
> rig_register (1)
> rig_register (2)
> rig: loading backend yaesu
> yaesu: initrigs2_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: loading backend kenwood
> initrigs2_kenwood called
> rig_register (213)
> rig_register (201)
> rig_register (225)
> rig_register (203)
> rig_register (204)
> rig_register (216)
> rig_register (224)
> rig_register (205)
> rig_register (207)
> rig_register (209)
> rig_register (210)
> rig_register (222)
> rig_register (214)
> rig_register (230)
> rig_register (221)
> rig_register (229)
> rig_register (202)
> rig_register (211)
> rig_register (206)
> rig_register (208)
> rig_register (215)
> rig_register (226)
> rig_register (217)
> rig_register (233)
> rig_register (220)
> rig_register (223)
> rig_register (227)
> rig_register (234)
> rig_register (231)
> rig_register (231)
> rig_register (228)
> rig_register (219)
> rig_register (232)
> rig: loading backend icom
> icom: _init called
> rig_register (355)
> rig_register (309)
> rig_register (310)
> rig_register (311)
> rig_register (313)
> rig_register (314)
> rig_register (315)
> rig_register (319)
> rig_register (320)
> rig_register (321)
> rig_register (322)
> rig_register (367)
> rig_register (323)
> rig_register (346)
> rig_register (324)
> rig_register (328)
> rig_register (330)
> rig_register (326)
> rig_register (327)
> rig_register (347)
> rig_register (357)
> rig_register (363)
> rig_register (329)
> rig_register (362)
> rig_register (345)
> rig_register (356)
> rig_register (360)
> rig_register (361)
> rig_register (331)
> rig_register (312)
> rig_register (316)
> rig_register (332)
> rig_register (334)
> rig_register (344)
> rig_register (368)
> rig_register (335)
> rig_register (369)
> rig_register (336)
> rig_register (358)
> rig_register (337)
> rig_register (338)
> rig_register (339)
> rig_register (340)
> rig_register (341)
> rig_register (342)
> rig_register (343)
> rig_register (366)
> rig_register (303)
> rig_register (304)
> rig_register (306)
> rig_regi...

[FanJun Kong - ( BH1SCW ) (fjkong)]

I am not sure if this works for you, but I can select Ft 991 in configure menu of wxjtx. I took a screenshot here.

[Hveem (krbjhvee)]

I too can that now, but i have tried to set the correct communication
speed, 38400 , and tried different ports, dev/ttyUSB0 and /dev/ttyUSB1
, datadabits seven or 8, one or two stop bits, different regimes of
handshake etc, but i am getting

Hamlib error: IO error while opening connection to rig

Den 09. jan. 2017 16:58, skrev FanJun Kong - ( BH1SCW ):
> I am not sure if this works for you, but I can select Ft 991 in
> configure menu of wxjtx. I took a screenshot here.
>
> ** Attachment added: "ft991.png"
> https://bugs.launchpad.net/ubuntu/+source/hamlib/+bug/1648397/+attachment/4801968/+files/ft991.png
>

[FanJun Kong - ( BH1SCW ) (fjkong)]

oh, I don't have ft991 here, only kenwood ts590s.

[Ervin Hegedüs (airween)]

Hveem,

the IO error could be by the permission problem, eg. the ttyUSB* ports owned by root:dialout, but you aren't member of dialout group. You can fix it that you added yourself to group dialout:

sudo usermod -aG dialout YOURUSER

then after the next login you will be able to use the ports.

Please check it again - the newest versions of Hamlib (3.0, 3.1) suports your RIG.