On 07/04/2016 23:43, Michael Black wrote: > But why couldn't you just remember the bw from get_mode and keep using > that rather than wholesale changes to hamlib? > And allowing the user to put bandwidth in the rig settings too so, for > examle, you don't have to reset all the bands on your rig when > changing operating modes? > If bandwidth is added as an option and it's not filled in then you > just keep whatever the current bandwidth is. Hi Mike,
that is a large can of worms I do not want to open. Many rigs do not have a bandwidth query so it gets complicated very quickly. I'd rather address the ambiguous Hamlib set_mode concept and leave bandwidth to the rig user. IMHO bandwidth is something you change according to conditions and band occupancy, not set once and forget. Also most rigs automatically recall the last bandwidth used for a mode so there is usually no need to set it. I believe that the few rigs that appear not to have a way of setting mode without touching bandwidth actually do. For example early CI-V Icoms have the 06 command to set mode and bandwidth but the bandwidth part can be omitted which is not documented. I fear that this poorly documented command is the whole reason for mode and bandwidth being conflated in Hamlib. 73 Bill G4WJS. ------------------------------------------------------------------------------ _______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
