Mark Perini | 5 Sep 2004 21:40
Picon
Favicon

warnings during 'make' of hamlib 1.2.2 on FC2

I'm a new user to hamlib (using 1.2.2 with KTrack)...Should I be
concerned about warnings such as the following during 'make'?:

rig.c: In function `rig_init':
rig.c:258: warning: assignment discards qualifiers from pointer target
type
serial.c: In function `ser_ptt_get':
serial.c:518: warning: passing arg 2 of `ser_get_rts' from incompatible
pointer type
serial.c:520: warning: passing arg 2 of `ser_get_dtr' from incompatible
pointer type
serial.c: In function `ser_dcd_get':
serial.c:557: warning: passing arg 2 of `ser_get_dcd' from incompatible
pointer type
...
ft100.c: In function `ft100_get_info':
ft100.c:886: warning: passing arg 2 of `read_block' from incompatible
pointer type
ft100.c:891: warning: passing arg 2 of `read_block' from incompatible
pointer type
ft100.c:896: warning: passing arg 2 of `read_block' from incompatible
pointer type
ft890.c:1072: warning: `ft890_set_split_freq' defined but not used
...
ft920.c: In function `ft920_set_mode':
ft920.c:512: warning: `cmd_index' might be used uninitialized in this
function
frg100.c:333: warning: `rig2mode' defined but not used
rpcrig_xdr_lt.c: In function `xdr_model_x':
rpcrig_xdr_lt.c:32: warning: unused variable `buf'
(Continue reading)

Ron Patterson | 6 Sep 2004 00:40
Favicon

Icom IC-756PROII

I am using hamlib 1.2.2  on fedora core 1with xlog. I noticed a few 
errors in the hamlib trace. I used rigctl to verify that they were 
indeed hamlib errors. There seems to be a problem with the mode command. 
The rig reports the correct mode but complains about the mode width. 
Here is the output from rigctl:

$ rigctl -vvvvv -r /dev/ttyS1 -m 347
rigctl, Hamlib version 1.2.2
Report bugs to <hamlib-developer <at> lists.sourceforge.net>

rig:rig_init called
rig: loading backend icom
icom: _init called
rig_register (355)
rig_register (309)
rig_register (310)
rig_register (311)
rig_register (313)
rig_register (314)
rig_register (315)
rig_register (319)
rig_register (320)
rig_register (321)
rig_register (323)
rig_register (346)
rig_register (324)
rig_register (328)
rig_register (330)
rig_register (326)
rig_register (327)
(Continue reading)

Mark J. Fine | 6 Sep 2004 01:05

Re: Icom IC-756PROII

On Sun, 2004-09-05 at 18:40, Ron Patterson wrote:
> I see that this backend is untested. I would be happy to help test it. 
> Should I check out the latest version from CVS?

The latest CVS will probably show the same response. The current
settings for most Icoms are:
 0 - Narrow
 1 - Normal
 2 - Wide

Except for the R75, they are set for:
 1 - Wide
 2 - Normal
 3 - Narrow

Is this the same for the 756ProII?

--

-- 

Mark J. Fine
Remington, Virginia, USA

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
Ron Patterson | 6 Sep 2004 01:59
Favicon

Re: Icom IC-756PROII

Mark J. Fine wrote:
On Sun, 2004-09-05 at 18:40, Ron Patterson wrote:
I see that this backend is untested. I would be happy to help test it. Should I check out the latest version from CVS?
The latest CVS will probably show the same response. The current settings for most Icoms are: 0 - Narrow 1 - Normal 2 - Wide Except for the R75, they are set for: 1 - Wide 2 - Normal 3 - Narrow Is this the same for the 756ProII?
It is not documented in the manual but it appears to be the same. Here is the output for wide, normal, and narrow.

Rig command: m
TX 6 bytes
0000     fe fe 64 e0 04 fd      ..d...
RX 6 characters
0000     fe fe 64 e0 04 fd      ..d...
RX 8 characters
0000     fe fe e0 64 04 01 01 fd        ...d....
Mode: USB
Passband: 2400
 
Rig command: m
TX 6 bytes
0000     fe fe 64 e0 04 fd      ..d...
RX 6 characters
0000     fe fe 64 e0 04 fd      ..d...
RX 8 characters
0000     fe fe e0 64 04 01 02 fd        ...d....
Mode: USB
Passband: 0
 
Rig command: m
TX 6 bytes
0000     fe fe 64 e0 04 fd      ..d...
RX 6 characters
0000     fe fe 64 e0 04 fd      ..d...
RX 8 characters
0000     fe fe e0 64 04 01 03 fd        ...d....
icom: Unsupported Icom mode width 0x03
Mode: USB
Passband: 0

Ron W6FM

------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click

Ron Patterson | 6 Sep 2004 02:19
Favicon

Re: Icom IC-756PROII

Seems to be a problem with the ptt command as well.

Opened rig model 347, 'IC-756PROII'
Backend version: 0.2, Status: Untested

Rig command: t
TX 6 bytes
0000     fe fe 64 e0 1c fd      ..d...
RX 6 characters
0000     fe fe 64 e0 1c fd      ..d...
RX 6 characters
0000     fe fe e0 64 fa fd      ...d..
icom_get_ptt: wrong frame len=0
get_ptt: error = Command rejected by the rig

Rig command: T
PTT: 0
TX 7 bytes
0000     fe fe 64 e0 1c 01 fd   ..d....
RX 7 characters
0000     fe fe 64 e0 1c 01 fd   ..d....
RX 6 characters
0000     fe fe e0 64 fa fd      ...d..
icom_set_ptt: ack NG (0xfa), len=1
set_ptt: error = Command rejected by the rig

Rig command: T
PTT: 1
TX 7 bytes
0000     fe fe 64 e0 1c 00 fd   ..d....
RX 7 characters
0000     fe fe 64 e0 1c 00 fd   ..d....
RX 8 characters
0000     fe fe e0 64 1c 00 00 fd        ...d....
icom_set_ptt: ack NG (0x1c), len=3
set_ptt: error = Command rejected by the rig

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
Stephane Fillod | 7 Sep 2004 23:30
Picon
Favicon

Re: warnings during 'make' of hamlib 1.2.2 on FC2

On Sun, Sep 05, 2004, Mark Perini wrote:
> I'm a new user to hamlib (using 1.2.2 with KTrack)...Should I be

Hey, nice! What kind of rotator are you using?

> concerned about warnings such as the following during 'make'?:

Don't worry about the warnings. I'm simply either too lazy or have not
found yet a smart way to silence them :-)

> rig.c: In function `rig_init':
> rig.c:258: warning: assignment discards qualifiers from pointer target
> type

This is because of a hack on the rig_caps const qualifiers. 
One day the const in rig.h may go away.

> serial.c: In function `ser_ptt_get':
> serial.c:518: warning: passing arg 2 of `ser_get_rts' from incompatible
> pointer type
> serial.c:520: warning: passing arg 2 of `ser_get_dtr' from incompatible
> pointer type
> serial.c: In function `ser_dcd_get':
> serial.c:557: warning: passing arg 2 of `ser_get_dcd' from incompatible
> pointer type

This is okay on common platforms. I'll do some typecasting one day.

> ...
> ft100.c: In function `ft100_get_info':
> ft100.c:886: warning: passing arg 2 of `read_block' from incompatible
> pointer type
> ft100.c:891: warning: passing arg 2 of `read_block' from incompatible
> pointer type
> ft100.c:896: warning: passing arg 2 of `read_block' from incompatible
> pointer type
> ft890.c:1072: warning: `ft890_set_split_freq' defined but not used
> ...
> ft920.c: In function `ft920_set_mode':
> ft920.c:512: warning: `cmd_index' might be used uninitialized in this
> function
> frg100.c:333: warning: `rig2mode' defined but not used
[..]
I'm not the maintainer of most Yaesu backend, but these warnings are
harmless, except one in a piece of code that is not used actually :-)

> rpcrig_xdr_lt.c: In function `xdr_model_x':
> rpcrig_xdr_lt.c:32: warning: unused variable `buf'

I cannot do much for that, rpcgen generates stupid code at times..

Thanks for the report anyway.

Best 73,
Stephane - F8CFE

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
Stephane Fillod | 8 Sep 2004 00:04
Picon
Favicon

Re: Icom IC-756PROII

Hi Ron,

Thanks for the report on the IC-756PROII. This rig has much much
setting ability. Only a tiny fraction has been implemented so far.
Anyway the most useful are there. Feel free to test the one you need,
and we'll try to make them work. Patches are welcome too :-)

Mark and you are right about modes. c.f. http://www.plicht.de/ekki/civ/civ-p33.html
Patches have been pushed in CVS by Mark, and I've (hopefully) fixed the
set_ptt. You can check out the Hamlib CVS to test these changes.
I've also attached a patch against 1.2.2 (icom subdir) for your convenience,
saving you the burden of cvs.

73
Stephane - F8CFE

Attachment (ic756.patch.gz): application/octet-stream, 5081 bytes
Mark J. Fine | 8 Sep 2004 00:32

Re: Icom IC-756PROII

Stephane Fillod wrote:
> Mark and you are right about modes. c.f. http://www.plicht.de/ekki/civ/civ-p33.html
> Patches have been pushed in CVS by Mark, and I've (hopefully) fixed the

...and was more than happy to do it.

One of the things I was wondering on his ptt debug output was that it 
looked like the typical "get" query was failing.

One of the things I'm suspicious in some Icoms is the ability to "set" 
things, but not "get" them. For example, the R75 has no way to get the 
currently active memory channel, or whether it's in VFO or MEMO mode.

Incidentally, these are hardware and firmware limitations of the rig 
itself - not hamlib.

--

-- 

Mark J. Fine
Remington, Virginia, USA

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
Ron Patterson | 8 Sep 2004 03:42
Favicon

Re: Icom IC-756PROII

Stephane Fillod wrote:

>Hi Ron,
>
>Thanks for the report on the IC-756PROII. This rig has much much
>setting ability. Only a tiny fraction has been implemented so far.
>Anyway the most useful are there. Feel free to test the one you need,
>and we'll try to make them work. Patches are welcome too :-)
>  
>
Thanks for the response Stephane. I am afraid I am not much of a 
programmer so don't look for patches from me anytime soon :-) I have 
attached a spec file that I hacked to build 1.2.2 rpms. I am afraid that 
is the limit of my abilities for now.

>Mark and you are right about modes. c.f. http://www.plicht.de/ekki/civ/civ-p33.html
>Patches have been pushed in CVS by Mark, and I've (hopefully) fixed the
>set_ptt. You can check out the Hamlib CVS to test these changes.
>I've also attached a patch against 1.2.2 (icom subdir) for your convenience,
>saving you the burden of cvs.
>  
>
Thanks for the patch. That is much easier for me than CVS. I applied the 
patch and I am no longer getting errors. I can set the bandwidth with no 
problem but when I get the bandwidth, rigctl returns 0 for 1.8 and 
3.0khz filters. The 2.4khz filter reports ok. See below:

Rig command: m
TX 6 bytes
0000     fe fe 64 e0 04 fd      ..d...
RX 6 characters
0000     fe fe 64 e0 04 fd      ..d...
RX 8 characters
0000     fe fe e0 64 04 01 01 fd        ...d....
Mode: USB
Passband: 0

Rig command: m
TX 6 bytes
0000     fe fe 64 e0 04 fd      ..d...
RX 6 characters
0000     fe fe 64 e0 04 fd      ..d...
RX 8 characters
0000     fe fe e0 64 04 01 02 fd        ...d....
Mode: USB
Passband: 2400

Rig command: m
TX 6 bytes
0000     fe fe 64 e0 04 fd      ..d...
RX 6 characters
0000     fe fe 64 e0 04 fd      ..d...
RX 8 characters
0000     fe fe e0 64 04 01 03 fd        ...d....
Mode: USB
Passband: 0

As far as getting the ptt state, the Icom documentation doesn't seem to 
indicate that this function  is available. Perhaps I should talk to Joop 
PG4I and pose this problem to him. I am not sure why xlog wants the ptt 
state anyway.

>73
>Stephane - F8CFE
>
>  
>
Thanks again for all the help.

73,

Ron W6FM
%define ver 1.2.2
%define prefix	/usr

Summary: Run-time library to control radio transcievers and receivers.
Name: hamlib
Version: %ver
Release: 2
Copyright: LGPL
Group: Ham/Libraries
Packager: Stephane Fillod <fillods <at> users.sourceforge.net>
Source: ftp://ftp.sourceforge.net/pub/sourceforge/hamlib/hamlib-%{ver}.tar.gz
BuildRoot: /tmp/hamlib-%{ver}-buildroot
URL: http://hamlib.sourceforge.net
BuildRequires: binutils >= 2.9.4, gcc >= 2.95, glibc-devel >= 2.1
BuildRequires: /bin/sh, fileutils, findutils, flex
BuildRequires: gzip, make >= 3.77, patch >= 2.5, rpm >= 3.0, sed
BuildRequires: textutils
BuildRequires: /bin/sh, automake >= 1.4, libtool >= 1.4, fileutils, findutils

%changelog

* Tue Jan 20 2004 Tomi Manninen
- Fix for 1.1.5pre2
- Better use of rpm macros
- Disable all bindings

* Tue Oct 08 2003 Joop Stakenborg
- Fix 'make rpm' again by disabling c++ bindings.
- rotclass.h and rigclass.h go into the devel package for now (FIXME)

* Wed Jan 15 2003 Joop Stakenborg
- Fix the spec file for 1.1.4CVS
- 'make rpm' should work now

* Thu Jun 17 2002 Stephane Fillod
- Added rotator support
- Added RPC daemon, hamlib.m4
- Upstream version 1.1.3

* Mon Jul 18 2001 Stephane Fillod
- Made initial "working" SPEC file

%description
 Most recent amateur radio transceivers allow external control of their
 functions through a computer interface. Unfortunately, control commands are
 not always consistent across a manufacturer's product line and each
 manufacturer's product line differs greatly from its competitors.
 .
 This library addresses that issue by providing a standardised programming
 interface that applications can talk to and translating that into the
 appropriate commands required by the radio in use.
 .
 This package provides the run-time form of the library. If you wish to
 develop software using this library you need the 'hamlib-devel' package.
 .
 Also included in the package is a simple radio control program 'rigctl',
 which let one control a radio transceiver or receiver, either from
 command line interface or in a text-oriented interactive interface.

%package devel
Summary: Development library to control radio transcievers and receivers.
Group: Development/Libraries
Requires: hamlib

%description devel
 Most recent amateur radio transceivers allow external control of their
 functions through a computer interface. Unfortunately, control commands are
 not always consistent across a manufacturer's product line and each
 manufacturer's product line differs greatly from its competitors.
 .
 This library addresses that issue by providing a standardised programming
 interface that applications can talk to and translating that into the
 appropriate commands required by the radio in use.
 .
 This package provides the development library. If you wish to run applications
 developed using this library you'll need the 'hamlib' package.

#%package c++
#Summary: Hamlib radio control library C++ binding
#Group: Development/Libraries
#Requires: hamlib

#%description c++
#C++ Binding.

#%package c++-devel
#Summary: Hamlib radio control library C++ binding headers and static libs
#Group: Development/Libraries
#Requires: hamlib, hamlib-devel

#%description c++-devel
#This package contains all of the headers and the static libraries 
#for C++ binding of Hamlib.

#You'll only need this package if you are doing development.

#%package perl
#Summary: Hamlib radio control library Perl binding
#Group: Development/Libraries
#Requires: hamlib
#
#%description perl
#Perl Binding.

%prep
%setup
%build

%configure --without-cxx-binding   \
	   --without-perl-binding  \
	   --without-kylix-binding \
	   --without-tcl-binding   \
	   --without-python-binding
make CFLAGS="$RPM_OPT_FLAGS" CXXFLAGS="$RPM_OPT_FLAGS" all

%install
rm -rf $RPM_BUILD_ROOT
(umask 077 && mkdir -p $RPM_BUILD_ROOT)
chmod go= $RPM_BUILD_ROOT
%makeinstall

chmod 644 $RPM_BUILD_ROOT%{prefix}/lib/*.la
#strip $RPM_BUILD_ROOT%{prefix}/lib/*-%{version}.so

%clean
rm -rf $RPM_BUILD_ROOT

%post -p /sbin/ldconfig

%postun -p /sbin/ldconfig

%files
%defattr(644, root, root, 755)
%doc COPYING

#%doc doc/*.html
#%doc doc/*.sgml
#%doc doc/*.txt

%defattr(755, root, root, 755)
%{_libdir}/libhamlib-%{ver}.so.2
%{_libdir}/libhamlib-%{ver}.so.2.0.1
%{_libdir}/libhamlib.la
%{_libdir}/hamlib-alinco.so
%{_libdir}/hamlib-alinco.la
%{_libdir}/hamlib-aor.so
%{_libdir}/hamlib-aor.la
%{_libdir}/hamlib-drake.so
%{_libdir}/hamlib-drake.la
%{_libdir}/hamlib-dummy.so
%{_libdir}/hamlib-dummy.la
%{_libdir}/hamlib-easycomm.so
%{_libdir}/hamlib-easycomm.la
%{_libdir}/hamlib-flexradio.so
%{_libdir}/hamlib-flexradio.la
%{_libdir}/hamlib-fodtrack.so
%{_libdir}/hamlib-fodtrack.la
%{_libdir}/hamlib-icom.so
%{_libdir}/hamlib-icom.la
%{_libdir}/hamlib-jrc.so
%{_libdir}/hamlib-jrc.la
%{_libdir}/hamlib-kachina.so
%{_libdir}/hamlib-kachina.la
%{_libdir}/hamlib-kenwood.so
%{_libdir}/hamlib-kenwood.la
%{_libdir}/hamlib-lowe.so
%{_libdir}/hamlib-lowe.la
%{_libdir}/hamlib-microtune.so
%{_libdir}/hamlib-microtune.la
%{_libdir}/hamlib-pcr.so
%{_libdir}/hamlib-pcr.la
%{_libdir}/hamlib-rft.so
%{_libdir}/hamlib-rft.la
%{_libdir}/hamlib-rotorez.so
%{_libdir}/hamlib-rotorez.la
%{_libdir}/hamlib-rpcrig.so
%{_libdir}/hamlib-rpcrig.la
%{_libdir}/hamlib-rpcrot.so
%{_libdir}/hamlib-rpcrot.la
%{_libdir}/hamlib-sartek.so
%{_libdir}/hamlib-sartek.la
%{_libdir}/hamlib-tapr.so
%{_libdir}/hamlib-tapr.la
%{_libdir}/hamlib-tentec.so
%{_libdir}/hamlib-tentec.la
%{_libdir}/hamlib-uniden.so
%{_libdir}/hamlib-uniden.la
%{_libdir}/hamlib-winradio.so
%{_libdir}/hamlib-winradio.la
%{_libdir}/hamlib-yaesu.so
%{_libdir}/hamlib-yaesu.la
%{_bindir}/rigswr
%{_libdir}/hamlib-kit.a
%{_libdir}/hamlib-kit.la
%{_libdir}/hamlib-kit.so
%{_libdir}/hamlib-skanti.a
%{_libdir}/hamlib-skanti.la
%{_libdir}/hamlib-skanti.so
%{_mandir}/man1/rigswr.1.gz
%{_bindir}/rigctl
%{_sbindir}/rpc.rigd
%{_mandir}/man1/rigctl.1.gz
%{_mandir}/man8/rpc.rigd.8.gz
%{_bindir}/rotctl
%{_sbindir}/rpc.rotd
%{_mandir}/man1/rotctl.1.gz
%{_mandir}/man8/rpc.rotd.8.gz
%{_bindir}/rigmem
%{_mandir}/man1/rigmem.1.gz

%files devel
%defattr(644, root, root, 755)

%{_includedir}/hamlib/rig.h
%{_includedir}/hamlib/rigclass.h
%{_includedir}/hamlib/rotclass.h
%{_includedir}/hamlib/rig_dll.h
%{_includedir}/hamlib/riglist.h
%{_includedir}/hamlib/rotator.h
%{_includedir}/hamlib/rotlist.h
%{_datadir}/aclocal/hamlib.m4
%{_libdir}/pkgconfig/hamlib.pc
%{_libdir}/libhamlib.a
%{_libdir}/libhamlib.so
%{_libdir}/hamlib-alinco.a
%{_libdir}/hamlib-aor.a
%{_libdir}/hamlib-drake.a
%{_libdir}/hamlib-dummy.a
%{_libdir}/hamlib-easycomm.a
%{_libdir}/hamlib-flexradio.a
%{_libdir}/hamlib-fodtrack.a
%{_libdir}/hamlib-icom.a
%{_libdir}/hamlib-jrc.a
%{_libdir}/hamlib-kachina.a
%{_libdir}/hamlib-kenwood.a
%{_libdir}/hamlib-lowe.a
%{_libdir}/hamlib-microtune.a
%{_libdir}/hamlib-pcr.a
%{_libdir}/hamlib-rft.a
%{_libdir}/hamlib-rotorez.a
%{_libdir}/hamlib-rpcrig.a
%{_libdir}/hamlib-rpcrot.a
%{_libdir}/hamlib-sartek.a
%{_libdir}/hamlib-tapr.a
%{_libdir}/hamlib-tentec.a
%{_libdir}/hamlib-uniden.a
%{_libdir}/hamlib-winradio.a
%{_libdir}/hamlib-yaesu.a

#%files c++
#%defattr(755, root, root, 755)
#%{_libdir}/libhamlib++-%{version}.so

#%files c++-devel
#%defattr(644, root, root, 755)

#%{_includedir}/hamlib/rigclass.h
#%{_includedir}/hamlib/rotclass.h

#%{_datadir}/aclocal/hamlib++.m4
#%{_libdir}/libhamlib++.a
#%{_libdir}/libhamlib++.la

#%files perl
#%defattr(755, root, root, 755)
#/usr/local/lib/perl/5.6.1/Hamlib.pm
#%dir /usr/local/lib/perl/5.6.1/auto/Hamlib
#%doc /usr/local/man/man3/Hamlib.3pm

Mike Markowski | 8 Sep 2004 15:23
Picon
Favicon

Ten-Tec Jupiter

Hi all,

I've been using hamlib for a year or so now, but have just
today subscribed to the list.  I'm a little slow...  :-)

Till now I've had no problems using my ICOM 706 MkIIg with
hamlib but have just upgraded rigs to a Ten-Tec Jupiter.  I
see from the web page that the Jupiter is in need of testers.
Is anyone else using it at all yet?

I hooked up a serial cable, but there seems to be no data
transferred when, e.g., I use xlog with hamlib enabled.  I'm
happy to be a tester for this rig but hope someone is able to 
get me pointed in the right direction.

	Thanks!
	Mike  AB3AP

-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click

Gmane