Re: [Hamlib-developer] Where does the data for certain lists come from?
Library to control radio transceivers and receivers
Brought to you by:
n0nb
From: David B. <da...@ba...> - 2025-04-18 11:30:57
|
The parameters for a radio are stored in the radio Hamlib backend as you can't query a radio for its supported parameters, those have to be gleaned from the CAT listing for the radio. There is no explicit "list supported modes" command. Using rigctl and the -u command you can extract the modes from the Bandwidth list. You can do the same with the Hamlib API. Looking at a the Hamlib listing for a radio, there is a differentiation between TX modes and RX modes, but not VFO. If you want to check the if a mode is supported by a particular VFO, you could try and set the mode and see if the return is an error. No error it is supported, error not supported. 73 de David M0DGB/G8FKH -----Original Message----- From: Richard Emling <DO...@ho...> Sent: 17 April 2025 23:18 To: Hamlib Developers Mailingliste <ham...@li...> Subject: [Hamlib-developer] Where does the data for certain lists come from? Hi everyone, I've been exploring some list commands and I'm wondering where exactly the information returned by these commands originates. Currently, I retrieve all necessary details using the --caps-dump command, which works fine. However, it would be great if I could use for example get_modes and get_vfo_list instead. My main question is: are these lists generated based on data from the backend (e.g., the Raspberry Pi), or are they fetched directly from the connected radio each time the command is issued? The distinction is important, since not all radios are capable of reporting their supported modes or VFO combinations. If the radio is queried every time, this would make the commands less reliable across diverse hardware. Additionally, is there any way to generate these lists dynamically depending on the currently selected VFO? For instance, We've come across radios where for example VFOA supports FM, AM, and Digital, but VFOB supports only FM and Digital. It would be very useful if the command could reflect these distinctions based on actual capabilities. Thanks a lot in advance! -- 73 Richard, DO9RE _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |