Re: [Hamlib-developer] HamLib 4.5.5 Problems (Windows version MSVC)

[Black M. <mdb...@ya...>]

VFO_B on the 7610 and 7300 can both be read with 0x25.
I don't know how you are running DXDozer but you can test this with rigctl to see that reading VFOB does not cause a VFO swap if you use the --vfo option.Are you using Hamlib calls or rigctld?
If a user wants VFOB freq/mode they get the right answer -- even if VFO swapping is needed (on older Icom rigs).
If you don't want VFOB swapping on those older rigs one has to disable reading VFOB.This is can Icom problem the finally fixed with 0x25 and 0x26.
Mike W9DMB

 

    On Tuesday, April 11, 2023 at 01:55:34 AM CDT, Yahoo (sv2agw) via Hamlib-developer <ham...@li...> wrote:  
 
 
Hi

the 32b dll worked only once when the 4 version first published. After that no success. Think it has to do with "structure member alignement".

The x64 works as advertised. The problem/Bug is with Icom IC-7610 and IC-7300.

DxDozer uses Hamlib to get the Frequency for VFO_A and VFO_B. In IC-7610 you cannot read the VFO_B (SubVFO). The right response from Hamlib when someone tries to read VFO_B(SubVFO) should be an error. Instead it switches momentarily the TRX to VFO_B (SubVFO) and then back to main. This is problem and annoying because it happens every sec (the polling interval).




The same happens with IC-7300. Momentarily switches to VFO_B and then Back to VFO_A. If IC-7300 is in Memory no switch happens.




73


(SV2AGW)George Rossopoulos
Anakreontos14
GR-54250 Thessaloniki
GREECE

www.sv2agw.com
www.frinos.com
www.agwtracker.com
AGWPE on Facebook



_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer