mirror
/
Hamlib
kopia lustrzana https://github.com/Hamlib/Hamlib
1
0
Forkuj 0
Kod Zgłoszenia Projekty Wydania Wiki Aktywność

Remove "$Id:" CVS tag as it is no longer used.

Hamlib-1.2.15
Nate Bargmann 2011-08-22 21:32:35 -05:00
rodzic bff9f17f7e
commit c3e9dfd93f
8 zmienionych plików z 28 dodań i 38 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

1
kenwood/ts2k.c
Wyświetl plik

@ -62,7 +62,6 @@
* Hamlib Kenwood backend - main file * Hamlib Kenwood backend - main file
* Copyright (c) 2000-2002 by Stephane Fillod * Copyright (c) 2000-2002 by Stephane Fillod
* *
* $Id: ts2k.c,v 1.8 2009-02-03 23:22:58 azummo Exp $
*/ */

3
kit/fifisdr.c
Wyświetl plik

@ -1,5 +1,4 @@
/* $Id: $ /*
*
* Hamlib KIT backend - FiFi-SDR Receiver(/Tuner) description * Hamlib KIT backend - FiFi-SDR Receiver(/Tuner) description
* Copyright (c) 2010 by Rolf Meeser * Copyright (c) 2010 by Rolf Meeser
* *

5
microtune/microtune.cc
Wyświetl plik

@ -2,7 +2,6 @@
* Hamlib Microtune backend - main file * Hamlib Microtune backend - main file
* Copyright (c) 2003 by Stephane Fillod * Copyright (c) 2003 by Stephane Fillod
* *
* $Id: microtune.cc,v 1.3 2003-10-20 20:34:02 fillods Exp $
* *
* This library is free software; you can redistribute it and/or modify * This library is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by * it under the terms of the GNU General Public License as published by
@ -139,7 +138,7 @@ int microtune_set_freq(RIG *rig, vfo_t vfo, freq_t freq)
{ {
double actual_freq; double actual_freq;
bool status; bool status;
struct microtune_priv_data *priv = (struct microtune_priv_data *)rig->state.priv; struct microtune_priv_data *priv = (struct microtune_priv_data *)rig->state.priv;
status = priv->board->set_RF_freq((double)freq, &actual_freq); status = priv->board->set_RF_freq((double)freq, &actual_freq);
@ -153,7 +152,7 @@ int microtune_set_freq(RIG *rig, vfo_t vfo, freq_t freq)
int microtune_get_freq(RIG *rig, vfo_t vfo, freq_t *freq) int microtune_get_freq(RIG *rig, vfo_t vfo, freq_t *freq)
{ {
struct microtune_priv_data *priv = (struct microtune_priv_data *)rig->state.priv; struct microtune_priv_data *priv = (struct microtune_priv_data *)rig->state.priv;
*freq = priv->actual_freq; *freq = priv->actual_freq;

1
microtune/microtune.h
Wyświetl plik

@ -2,7 +2,6 @@
* Hamlib Microtune backend - main header * Hamlib Microtune backend - main header
* Copyright (c) 2001-2003 by Stephane Fillod * Copyright (c) 2001-2003 by Stephane Fillod
* *
* $Id: microtune.h,v 1.4 2003-10-20 20:34:02 fillods Exp $
* *
* This library is free software; you can redistribute it and/or modify * This library is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by * it under the terms of the GNU General Public License as published by

1
microtune/module_4702.c
Wyświetl plik

@ -2,7 +2,6 @@
* Hamlib microtune backend - 4702 file * Hamlib microtune backend - 4702 file
* Copyright (c) 2003 by Stephane Fillod * Copyright (c) 2003 by Stephane Fillod
* *
* $Id: module_4702.c,v 1.1 2003-10-20 20:34:02 fillods Exp $
* *
* This library is free software; you can redistribute it and/or modify * This library is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by * it under the terms of the GNU General Public License as published by

1
microtune/module_4937.c
Wyświetl plik

@ -2,7 +2,6 @@
* Hamlib microtune backend - 4937 file * Hamlib microtune backend - 4937 file
* Copyright (c) 2003 by Stephane Fillod * Copyright (c) 2003 by Stephane Fillod
* *
* $Id: module_4937.c,v 1.5 2003-10-20 20:34:02 fillods Exp $
* *
* This library is free software; you can redistribute it and/or modify * This library is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by * it under the terms of the GNU General Public License as published by

8
yaesu/README.ft890
Wyświetl plik

@ -1,8 +1,6 @@
Quirks, known bugs, and other notes. Quirks, known bugs, and other notes.
==================================== ====================================
$Id: README.ft890,v 1.1 2003-04-05 04:13:52 n0nb Exp $
In this document I'll try to describe the behavior of the Yaesu FT-890 In this document I'll try to describe the behavior of the Yaesu FT-890
transceiver with Hamlib. Some of these are limitations of the radio transceiver with Hamlib. Some of these are limitations of the radio
while others are programming trade-offs with Hamlib. while others are programming trade-offs with Hamlib.
@ -13,10 +11,10 @@ behavior with each call.
rig_set_rit rig_set_rit
* RIG_VFO_* value is respected so the rig VFO may be changed with * RIG_VFO_* value is respected so the rig VFO may be changed with
this call. this call.
* To "zero" the RIT pass a value > 0 or < 10 with this call. The * To "zero" the RIT pass a value > 0 or < 10 with this call. The
digit will be dropped as resolution is 10 Hz minimum and the digit will be dropped as resolution is 10 Hz minimum and the
clarifier offset set to 0 Hz. clarifier offset set to 0 Hz.
General notes. General notes.
As with most all Yaesu radios the radio must be polled by the application As with most all Yaesu radios the radio must be polled by the application
for status updates, i.e. no transceive mode in CAT. for status updates, i.e. no transceive mode in CAT.

46
yaesu/README.ft920
Wyświetl plik

@ -1,8 +1,6 @@
Quirks, known bugs, and other notes. Quirks, known bugs, and other notes.
==================================== ====================================
$Id: README.ft920,v 1.3 2003-01-19 04:47:59 n0nb Exp $
In this document I'll try to describe the behavior of the Yaesu FT-920 In this document I'll try to describe the behavior of the Yaesu FT-920
transceiver with Hamlib. Some of these are limitations of the radio transceiver with Hamlib. Some of these are limitations of the radio
while others are programming trade-offs with Hamlib. while others are programming trade-offs with Hamlib.
@ -11,13 +9,13 @@ This document is organized by Hamlib function calls and documents observed
behavior with each call. behavior with each call.
rig_set_mode rig_set_mode
* No matter the status of the main display, MEM or VFO, display * No matter the status of the main display, MEM or VFO, display
will be set to VFO mode if RIG_VFO_A or RIG_VFO_VFO is passed. will be set to VFO mode if RIG_VFO_A or RIG_VFO_VFO is passed.
* If radio is in MEM or MEM TUNE state, main display mode can be * If radio is in MEM or MEM TUNE state, main display mode can be
changed when RIG_VFO_MEM or RIG_VFO_MAIN is passed. changed when RIG_VFO_MEM or RIG_VFO_MAIN is passed.
* When RIG_VFO_CURR is passed, the display will be set per the VFO * When RIG_VFO_CURR is passed, the display will be set per the VFO
stored by the last rig_get_vfo call. stored by the last rig_get_vfo call.
* Modes DATA USB and DATA FM cannot be set at this time * Modes DATA USB and DATA FM cannot be set at this time
(Hamlib limitation). See below. (Hamlib limitation). See below.
* My FT-920 does not support USB/LSB narrow so attempting to * My FT-920 does not support USB/LSB narrow so attempting to
set a narrow passband with these modes will return an Invalib set a narrow passband with these modes will return an Invalib
@ -29,34 +27,34 @@ rig_get_mode
* DATA LSB is mapped to RIG_MODE_RTTY. * DATA LSB is mapped to RIG_MODE_RTTY.
* I would like to hear from anyone who gets a narrow passband * I would like to hear from anyone who gets a narrow passband
value in USB/LSB mode returned. value in USB/LSB mode returned.
rig_set_freq rig_set_freq
* When passed RIG_VFO_A or RIG_VFO_VFO the main display is forced * When passed RIG_VFO_A or RIG_VFO_VFO the main display is forced
to VFO mode and then the frequency is set. to VFO mode and then the frequency is set.
* When passed RIG_VFO_B or RIG_VFO_SUB, the sub display frequency * When passed RIG_VFO_B or RIG_VFO_SUB, the sub display frequency
is set. is set.
* When passed RIG_VFO_MEM, or RIG_VFO_MAIN, the main display * When passed RIG_VFO_MEM, or RIG_VFO_MAIN, the main display
frequency is set regardless of whether the main display is in frequency is set regardless of whether the main display is in
memory (thus activating MEM Tune) or VFO mode. memory (thus activating MEM Tune) or VFO mode.
* When RIG_VFO_CURR is passed, the display will be set per the VFO * When RIG_VFO_CURR is passed, the display will be set per the VFO
stored by the last rig_get_vfo call. stored by the last rig_get_vfo call.
* RIG_TARGETABLE_ALL is properly handled (I think). * RIG_TARGETABLE_ALL is properly handled (I think).
rig_get_freq rig_get_freq
* When passed RIG_VFO_A or RIG_VFO_VFO, the radio returns the * When passed RIG_VFO_A or RIG_VFO_VFO, the radio returns the
frequency in the main VFO, even if the main display is in MEM or frequency in the main VFO, even if the main display is in MEM or
MEM Tune. MEM Tune.
* When passed RIG_VFO_B or RIG_VFO_SUB, the sub-display frequency * When passed RIG_VFO_B or RIG_VFO_SUB, the sub-display frequency
is returned. is returned.
* When passed RIG_VFO_MEM or RIG_VFO_MAIN, the current main display * When passed RIG_VFO_MEM or RIG_VFO_MAIN, the current main display
frequency is returned regardless of main display mode. frequency is returned regardless of main display mode.
* When passed RIG_VFO_CURR, the display will be read per the VFO * When passed RIG_VFO_CURR, the display will be read per the VFO
stored by the last rig_get_vfo call. stored by the last rig_get_vfo call.
rig_set_vfo rig_set_vfo
* When called with RIG_VFO_A or RIG_VFO_VFO, the radio appears to * When called with RIG_VFO_A or RIG_VFO_VFO, the radio appears to
do nothing, however, rig_state->current_vfo will be updated. do nothing, however, rig_state->current_vfo will be updated.
* When called with RIG_VFO_B, the radio will swap the main and sub * When called with RIG_VFO_B, the radio will swap the main and sub
displays, the same as if the front panel A<>B button is pressed. displays, the same as if the front panel A<>B button is pressed.
* No provision exists to make VFO-B (sub display) the active RX * No provision exists to make VFO-B (sub display) the active RX
through CAT. through CAT.
@ -66,7 +64,7 @@ rig_get_split
but Hamlib only supports an indication that the radio is split. but Hamlib only supports an indication that the radio is split.
* The VFO value passed is not used by the ft920 backend lib. * The VFO value passed is not used by the ft920 backend lib.
FIXME: Is this a problem? FIXME: Is this a problem?
rig_set_split rig_set_split
* When called with RIG_SPLIT_OFF the radio will make TX A active if * When called with RIG_SPLIT_OFF the radio will make TX A active if
TX B was active, otherwise no change. TX B was active, otherwise no change.
@ -74,15 +72,15 @@ rig_set_split
TX A was active, otherwise no change. TX A was active, otherwise no change.
* The FT-920 has no capability to change the active RX to RX B (sub * The FT-920 has no capability to change the active RX to RX B (sub
display) through CAT. Thus if VFO-B is active RX/TX the setting display) through CAT. Thus if VFO-B is active RX/TX the setting
RIG_SPLIT_ON will make no visible change on the radio. RIG_SPLIT_ON will make no visible change on the radio.
* The VFO value passed is not used by the ft920 backend lib. * The VFO value passed is not used by the ft920 backend lib.
FIXME: Is this a problem? FIXME: Is this a problem?
rig_set_split_freq rig_set_split_freq
* Backend simply wraps rig_set_freq--calling app needs to specify * Backend simply wraps rig_set_freq--calling app needs to specify
target VFO to set frequency. Should backend determine split target VFO to set frequency. Should backend determine split
and set "proper" VFO? and set "proper" VFO?
rig_get_split_freq rig_get_split_freq
* Backend simply wraps rig_get_freq--calling app needs to specify * Backend simply wraps rig_get_freq--calling app needs to specify
target VFO to set frequency. Should backend determine split target VFO to set frequency. Should backend determine split
@ -92,7 +90,7 @@ rig_set_split_mode
* Backend simply wraps rig_set_mode--calling app needs to specify * Backend simply wraps rig_set_mode--calling app needs to specify
target VFO to set frequency. Should backend determine split target VFO to set frequency. Should backend determine split
and set "proper" VFO? and set "proper" VFO?
rig_get_split_mode rig_get_split_mode
* Backend simply wraps rig_get_mode--calling app needs to specify * Backend simply wraps rig_get_mode--calling app needs to specify
target VFO to set frequency. Should backend determine split target VFO to set frequency. Should backend determine split
@ -101,14 +99,14 @@ rig_get_split_mode
rig_set_rit rig_set_rit
* Hamlib specificies that passing 0 as the RIT frequency disables * Hamlib specificies that passing 0 as the RIT frequency disables
RIT. Thus there is no way to meet the spec and mimic the front RIT. Thus there is no way to meet the spec and mimic the front
panel RIT off function whilst keeping the RIT offset on the panel RIT off function whilst keeping the RIT offset on the
display. The Hamlib spec causes behavior analogous to shutting display. The Hamlib spec causes behavior analogous to shutting
RIT off and then pressing the Clear button. RIT off and then pressing the Clear button.
* There is no direct way to set RIT offset of VFOB/SUB. However, * There is no direct way to set RIT offset of VFOB/SUB. However,
rig_set_vfo can be used to swap VFO B and main, then set RIT, then rig_set_vfo can be used to swap VFO B and main, then set RIT, then
call rig_set_vfo to swap VFO B and main. call rig_set_vfo to swap VFO B and main.
FIXME: Should backend do this automatically? FIXME: Should backend do this automatically?
rig_get_rit rig_get_rit
* Backend returns clarifier offset regardless of whether RIT is on. * Backend returns clarifier offset regardless of whether RIT is on.
* vfo is honored and stored RIT is returned. * vfo is honored and stored RIT is returned.
@ -116,7 +114,7 @@ rig_get_rit
rig_set_xit rig_set_xit
* Hamlib specificies that passing 0 as the XIT frequency disables * Hamlib specificies that passing 0 as the XIT frequency disables
XIT. Thus there is no way to meet the spec and mimic the front XIT. Thus there is no way to meet the spec and mimic the front
panel XIT off function whilst keeping the XIT offset on the panel XIT off function whilst keeping the XIT offset on the
display. The Hamlib spec causes behavior analogous to shutting display. The Hamlib spec causes behavior analogous to shutting
XIT off and then pressing the Clear button. XIT off and then pressing the Clear button.
* There is no direct way to set XIT offset of VFOB/SUB. However, * There is no direct way to set XIT offset of VFOB/SUB. However,