Use the absolute value of any negative value that may be passed in via
the width parameter to set_mode.
If RIG_PASSBAND_NORMAL is passed in, call rig_passband_normal() to
determine the normal width for the mode before setting the bandwidth.
The width parameter is tested against wide and narrow filter values and
set to the returned values as upper and lower limits if width falls out
of those bounds.
Use the absolute value of any negative value that may be passed in via
the width parameter to set_mode.
If RIG_PASSBAND_NORMAL is passed in, call rig_passband_normal() to
determine the normal width for the mode before selecting the correct
filter (needs testing).
Similar to c78952310a, and
as described in page 15 of the user manual for the Yaesu GS-232A,
remove the extra line feed when sending commands.
(cherry picked from commit 8b41f25aa8)
From Paul:
" ... I am using the Win32 hamlib program, rotctl.exe
version 1.2.15.1 with a Yaesu GS-232B antenna rotator controller interface
device. Rotctl.exe is not operating as expected however. It frequently
hangs on some of the commands. I have successfully commanded the
controller using a dumb terminal and I have watched the characters that are
sent with a scope. It appears that the hamlib rotctl.exe is sending
incorrect line termination characters when sending out commands. It should
send carriage return only ("\r") and not carriage return and line feed
("\r\n") as it is currently doing.
I have attached page 15 from the user manual for the Yaesu GS-232B
controller interface device (also found at
http://gatorradio.org/Manuals/Yaesu_GS-232B_Manual.pdf) which shows the
proper line terminators."
Signed-off-by: Paul Lafferty <plaff65@gmail.com>
Signed-off-by: Stephane Fillod <fillods@users.sf.net>
(cherry picked from commit c78952310a)
Like other Kenwood rigs of its vintage, the TS-950 series provides the
mode information in the IF command response. Filter bandwidth is
set/read using the FL command.
(cherry picked from commit 1d6a7249fb)
From Michal:
"I have been playing a lot recently with PSK modes using fldigi. I have
noticed that the yaesu ft-857 backend doesn't distinguish between upper
and lower sideband digital mode (menu item 38). This causes lot of
trouble on bands where USB is used (when QSY button is pressed in
fldigi, or when calculating the real QSO frequency).
With some use of undocumented CAT features and some research I have
put together small patch, that reads EEPROM data. When SW asks hamlib
what mode is being used, hamlib will also consider the
value from eeprom.
When changing the mode in the menu, new value will become available in
the EEPROM _after_ pressing the "FUNC" button.
Setting mode from SW is left untouched, as writing to EEPROM is
potentially dangerous (and I don't feel like destroying my rig, yet)"
Signed-off-by: Nate Bargmann <n0nb@n0nb.us>
(cherry picked from commit de329c1ed7)
Implemented hash table to temporarily store and sort the rig models by ID
to print the --list by model numbers. Hash is implemented using
uthash.h, see http://uthash.sourceforge.net/
Suppressed rig backend register output by setting rig_debug_level to 0
for list output.
(cherry picked from commit 417cb98d2e)
Implemented hash table to temporarily store and sort the rot models by ID
to print the --list by model numbers. Hash is implemented using
uthash.h, see http://uthash.sourceforge.net/
Suppressed rot backend register output by setting rig_debug_level to 0
for list output.
(cherry picked from commit c3bc66eafc)
I should have done more testing on my last patch for you. I found a
bug, in that it wouldn't rotate for [0,-180). That is now fixed in
this hd1780.c enclosed.
Signed-off-by: Nate Bargmann <n0nb@n0nb.us>
(cherry picked from commit 62a4bd8363)
"Patch to make the HD-1780 obey the limits of rotation and make those
defaults correct. At my location, I need to set them a bit before
+/-180 to ensure that the rotor doesn't get torn up because the beam
will coast it past the stops."
Signed-off-by: Nate Bargmann <n0nb@n0nb.us>
Frank had originally released the files to us under "Creative Commons
License." After contacting him, he agreed to allow it to be changed to
LGPL:
Date: Tue, 10 Jan 2012 09:16:07 +0100
From: Frank Goenninger <frgo@me.com>
To: Nate Bargmann <n0nb@n0nb.us>
Subject: Re: Hamlib Backend for the ADAT ADT-200A
Hi Nate,
sure - change it to LGPL. Do you do this or should I do and resend the
files?
Tnx!
73 Frank
----------------8<------------------
I have now done so.
Only other change is stripping of trailing white space.
Implement several simple shell scripts to exercise various aspects of
Hamlib. The previous implementation relied on the installation of
DejaGNU and the tests/config and tests/*.test directories were not
distributed. Also, later Autotools documenation seems to suggest that
DejaGNU is to be replaced by Autotest. The generation and use of simple
scripts was chosen to provide a usable check target until Autotest can
be supported.
Various strncpy operations could result in a port pathname that is not a
NULL terminated string as the allowed string length is the same size as
the buffer per the strncpy manual page. This is corrected by assuring
that the allowed length is FILPATHLEN - 1.
Various strncpy operations could result in a port pathname that is not a
NULL terminated string as the allowed string length is the same size as
the buffer per the strncpy manual page. This is corrected by assuring
that the allowed length is FILPATHLEN - 1.
Various strncpy operations could result in a port pathname that is not a
NULL terminated string as the allowed string length is the same size as
the buffer per the strncpy manual page. This is corrected by assuring
that the allowed length is FILPATHLEN - 1.
Various strncpy operations could result in a port pathname that is not a
NULL terminated string as the allowed string length is the same size as
the buffer per the strncpy manual page. This is corrected by assuring
that the allowed length is FILPATHLEN - 1.
Various strncpy operations could result in a port pathname that is not a
NULL terminated string as the allowed string length is the same size as
the buffer per the strncpy manual page. This is corrected by assuring
that the allowed length is FILPATHLEN - 1.
Various strncpy operations could result in a port pathname that is not a
NULL terminated string as the allowed string length is the same size as
the buffer per the strncpy manual page. This is corrected by assuring
that the allowed length is FILPATHLEN - 1.
Nate Bargmann