Good morning Ervin,
I use latest stable hamlib 12.15.3 from sf
My rig capability dump:
rigctl -m 122 -u | grep VFO (I wonder what the result of this command
would show the version you use)
Has targetable VFO: N
VFO list: VFOA VFOB
VFO Ops: TOGGLE
Can set VFO: N
Can get VFO: N
Can set Split VFO: Y
Can get Split VFO: Y
Can ctl Mem/VFO: Y
Somehow happened that pre1.2.0 tlf's somehow were able to get frequency...
If tlf needs this "Has targetable VFO: Y or set/get VFO" then... either
one need to implement it in hamlib or do some exception in tlf for
FT-8x7 (-m 120 122 and 123 and probably 2?) rigs.
On 02/03/14 10:03, Ervin Hegedüs wrote:
Hello Zilvinas,
On Sat, Mar 01, 2014 at 11:41:16PM +0200, Zilvinas, AUGMA wrote:
And yes - rigctld and m=2 isn' related
rigctl -r /dev/ttyUSB0 -m 122 -s 9600 -vvvvv
ft857:ft857_open called
Opened rig model 122, 'FT-857'
Backend version: 0.4, Status: Beta
Rig command: v
get_vfo: error = Feature not available
well, that bad news:
http://sourceforge.net/p/hamlib/code/ci/master/tree/yaesu/ft857.c
In line 82., there is the yaesu_cmd_set_t array, which doesn't
contain the get vfo...
And in line 267.:
.get_vfo = NULL,
:(
I'll see, how can we handle the "not implemented" response in
Tlf.
73,
Ervin
HA2OS
_______________________________________________
Tlf-devel mailing list
Tlf-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tlf-devel
