Will allow rigctl_parse() routines access to connection data, without
reworking all of the internal and external interfaces.
(cherry picked from commit b56f8d8f8a)
Adds the missing TX modes to fix incorrect power calculation when mode
is one of PKTAM PKTFM PKTLSB PKTUSB and makes the difference between
TX and RX modes more explicit.
(cherry picked from commit 75e050889d)
The FT-710 firmware supports the targeted MD0/MD1 forms for mode
read and write. Advertising the capability lets hamlib dispatch
mode operations on the non-current VFO directly.
The FT-710 like other similar Yaesu models is a single-receiver
with multiple VFO, and thus only has a single bandpass filter
slot. So we must apply the same workaround as the FTDX10 when
refetching state after a band-select, and avoid issuing the
(unsupported) `SH1` command.
This reverts the previous change in #2055 as this is a more
direct/complete fix for the physical VFO swap reported in #2056.
Fixes#2056, #2062
(cherry picked from commit e0af6f93e5)
In struct SensorData, GLFloat was used to store 3 floats. However, the
code doesn't perform any GLSL calculation on them. More, Termux doesn't
provide GLSL headers and fails to build. This commit refactos GLFloat
to float to avoid necessary header issues, etc.
Signed-off-by: Gong BI1XJT <bi1xjt@rad1o.cn>
(cherry picked from commit c24f8fee1f)
Credit to Ladislav Vaiz (OK1ZIA) for the original 2012 Android port.
Signed-off-by: Gong BI1XJT <bi1xjt@rad1o.cn>
(cherry picked from commit bc830304a7)
- serial_stop_bits corrected from 1 to 2 per protocol documentation;
incorrect stop bits caused systematic transaction timing errors
- post_write_delay increased from 0 to 100ms to allow radio processing
time between commands
- timeout increased from 200ms to 600ms to accommodate slower responses
- retry reduced from 3 to 1 to prevent command flooding on failure
- DXSR8_LEVEL_ALL advertised RIG_LEVEL_RF but implemented ATT and
PREAMP; corrected capability flags accordingly
- set_mode NAR command acknowledgment timeout treated as non-fatal;
radio executes the command correctly but does not reliably return
OK within the timeout window — logs WARN instead of propagating error
- get_mode RR_NAR query removed; radio does not respond reliably
causing systematic timeouts — normal passband returned always
- get_level ATT case 2 returned 10 instead of 20 (copy-paste error)
- get_level RFPOWER case 3 never matched radio response of 2,
leaving val->f uninitialized in QRP mode
(cherry picked from commit b8eee851dc)
glibc implements some new parts of the C23 standard:
(Taken from https://download.opensuse.org/tumbleweed/iso/Changes.20260430.txt)
* For ISO C23, the functions bsearch, memchr, strchr, strpbrk, strrchr,
strstr, wcschr, wcspbrk, wcsrchr, wcsstr and wmemchr that return
pointers into their input arrays now have definitions as macros that
return a pointer to a const-qualified type when the input argument is
a pointer to a const-qualified type
and
* The aforementioned change in ISO C23 of the declaration of bsearch,
memchr, strchr, strpbrk, strrchr, strstr, wcschr, wcspbrk, wcsrchr,
wcsstr, and wmemchr as const-preserving macros can lead to compilation
issues in code not set up for it
This lead to some warnings about assigning returns from strchr(const, target)
to non-const pointers, and then discovering that Hamlib was modifying
those const parameters.
This commit aligns the const-ness of the offending parameters. Only affects
internal functions in ampctl_parse.c, rigctl_parse.c and rotctl_parse.c,
so API/ABI should not change.
(cherry picked from commit 7df5ae1a00)
To use the Skywatcher rotator, both motors have to by initialized. When
using the direct mode of the mounts hand control unit, this
initialization is performed by the hand control. We just need to set the
position.
When using the motor driver directly with a simple USB-RS232-adapter,
this init command must be sent before we are able to steer the mount.
This allows us to use the mount without cabeling up the whole hand
control unit.
(cherry picked from commit 5d0d5df3cf)
GCC on Debian 13 generated this warning:
CC hamgeek.lo
../../../../rigs/kenwood/hamgeek.c:71:9: warning: "BACKEND_VER" redefined
71 | #define BACKEND_VER "20260423"
| ^~~~~~~~~~~
In file included from ../../../../rigs/kenwood/hamgeek.c:35:
../../../../rigs/kenwood/kenwood.h:33:9: note: this is the location of the previous definition
33 | #define BACKEND_VER "20250515"
| ^~~~~~~~~~~
Renamimg the macro to USDX_BACKEND_VER quelled the warning.
(cherry picked from commit 07bd3b3650)
