Ham Radio Control Libraries developers

Rob Frohne | 8 Aug 2007 03:09

Re: Fwd: [Fwd: New hamlib version and problems with kenwood ts-850.]

Hi Joop, et. al., 

I'm interested in getting this bug fixed.  Today I tried Anjuta and
Kdevekop trying to get an IDE that would allow me to stop at breakpoints
in the library.  With the Kenwood TS-850 (which I am using) Grig seg
faults in kenwood_transaction() in the file kenwood.c.  What are you
guys using to debug with?

Thanks,

Rob, KL7NA

On Wed, 2006-12-27 at 09:00 +0100, Joop Stakenborg wrote:
> On Tue, 26 Dec 2006 17:00:42 -0600
> Nate Bargmann <n0nb <at> bluevalley.net> wrote:
> 
> > Anyone working with the Kenwood backend(s) who can work with David?
> > 
> 
> I am to busy right now.
> Anyone interested in taking over kenwood backend maintenance?
> 
> > 73, de Nate >>
> > 
> > -- 
> >  Wireless | Amateur Radio Station N0NB          |  Successfully Microsoft
> >   Amateur radio exams; ham radio; Linux info  <at>   | free since January 1998.
> >              http://www.qsl.net/n0nb/           |  "Debian, the choice of
> >              My Kawasaki KZ-650 SR  <at>             |     a GNU generation!"
> >         http://www.networksplus.net/n0nb/       |   http://www.debian.org

(Continue reading)

Nate Bargmann | 8 Aug 2007 05:09

Re: Fwd: [Fwd: New hamlib version and problems with kenwood ts-850.]

On Tuesday 07 August 2007 20:09:08 Rob Frohne wrote:
> Hi Joop, et. al.,
>
> I'm interested in getting this bug fixed.  Today I tried Anjuta and
> Kdevekop trying to get an IDE that would allow me to stop at breakpoints
> in the library.  With the Kenwood TS-850 (which I am using) Grig seg
> faults in kenwood_transaction() in the file kenwood.c.  What are you
> guys using to debug with?

I can't speak for anyone else, of course.  When I have worked in the backend 
stuff I add plenty of calls to the rig_debug function which can be used with 
rigctl to spit out critical variable values to STDERR by passing -vvvvv (for 
TRACE debug level) to rigctl.  After I've stabilized the particular backend 
function I'm working on, I reduce the rig_debug calls to just those places 
and variables that are critical so I can know what's going on in my code in 
the future.  Crude, but it works.

For myself, this approach works well.  I'm not patient enough to learn a 
debugger or an IDE.  My editor of choice is FTE, but it uses an obtuse 
configuration system that I learned long ago so the learning curve to get it 
just so may be high.  Kate is a good editor and I have used it as well.  If I 
were to decide to use a debugger, DDD may be my package of choice.

73, de Nate >>

--

-- 
 Wireless | Amateur Radio Station N0NB          |  Successfully Microsoft
  Amateur radio exams; ham radio; Linux info  <at>   | free since January 1998.
             http://www.qsl.net/n0nb/           |  "Debian, the choice of
             My Kawasaki KZ-650 SR  <at>             |     a GNU generation!"

(Continue reading)

Rob Frohne | 8 Aug 2007 06:05

Re: Fwd: [Fwd: New hamlib version and problems with kenwood ts-850.]

Thanks for the tips Nate.  My problem is that it works just fine with
rigctl, but with grig, I get a segmentation fault.  Maybe I can still
use it, or do something similar with printing to std_err or something.

Thanks,

Rob

On Tue, 2007-08-07 at 22:09 -0500, Nate Bargmann wrote:
> On Tuesday 07 August 2007 20:09:08 Rob Frohne wrote:
> > Hi Joop, et. al.,
> >
> > I'm interested in getting this bug fixed.  Today I tried Anjuta and
> > Kdevekop trying to get an IDE that would allow me to stop at breakpoints
> > in the library.  With the Kenwood TS-850 (which I am using) Grig seg
> > faults in kenwood_transaction() in the file kenwood.c.  What are you
> > guys using to debug with?
> 
> I can't speak for anyone else, of course.  When I have worked in the backend 
> stuff I add plenty of calls to the rig_debug function which can be used with 
> rigctl to spit out critical variable values to STDERR by passing -vvvvv (for 
> TRACE debug level) to rigctl.  After I've stabilized the particular backend 
> function I'm working on, I reduce the rig_debug calls to just those places 
> and variables that are critical so I can know what's going on in my code in 
> the future.  Crude, but it works.
> 
> For myself, this approach works well.  I'm not patient enough to learn a 
> debugger or an IDE.  My editor of choice is FTE, but it uses an obtuse 
> configuration system that I learned long ago so the learning curve to get it 
> just so may be high.  Kate is a good editor and I have used it as well.  If I

(Continue reading)

Patrick Ouellette | 8 Aug 2007 13:32

Re: Fwd: [Fwd: New hamlib version and problems with kenwood ts-850.]

On Tue, Aug 07, 2007 at 09:05:53PM -0700, Rob Frohne wrote:
> 
> Thanks for the tips Nate.  My problem is that it works just fine with
> rigctl, but with grig, I get a segmentation fault.  Maybe I can still
> use it, or do something similar with printing to std_err or something.
> 

Would this not suggest that GRIG is perhaps at fault too?  While a
properly coded piece of software should gracefully handle any possible
error that might happen, anyone who has written anything more complex
than a "hello world" program knows this does not always happen.

What function in GRIG is causing the segfault?  I have noticed 
on my Kenwood TS-2000 that the current GRIG is almost non-functional with my 
rig, when it used to work reasonably well 6 or 8 months ago (I don't 
use GRIG all that much).

> 
> On Tue, 2007-08-07 at 22:09 -0500, Nate Bargmann wrote:
> > 
> > I can't speak for anyone else, of course.  When I have worked in the backend 
> > stuff I add plenty of calls to the rig_debug function which can be used with 
> > rigctl to spit out critical variable values to STDERR by passing -vvvvv (for 
> > TRACE debug level) to rigctl.  After I've stabilized the particular backend 
> > function I'm working on, I reduce the rig_debug calls to just those places 
> > and variables that are critical so I can know what's going on in my code in 
> > the future.  Crude, but it works.

FWIW, I use this method (or even cruder - just put in print statements
so I know what is happening) when working with hamlib.

(Continue reading)

Rob Frohne | 8 Aug 2007 19:08

Re: Fwd: [Fwd: New hamlib version and problems with kenwood ts-850.]

Hi Patrick,

Thanks for the helpful comments.  I guess my problems is that the deeper
I get into fixing the problem, the more I problems I find (starting with
the IDE's, etc.)  

The problem is with hamlib I'm pretty certain, in the function
kenwood_transaction in the file kenwood.c.  That is what the stack trace
says, anyway.  And last night, while I was playing with rigctl, just
leaving it running, it quit with complaints about evidence of stack
corruption.  So now, I have either found more problems, or rigctl also
can produce problems.  

I'll probably try my own crude debugging technique today, and you and
Nate suggest.

Thanks for the notes!

73,

Rob  

On Wed, 2007-08-08 at 07:32 -0400, Patrick Ouellette wrote:
> On Tue, Aug 07, 2007 at 09:05:53PM -0700, Rob Frohne wrote:
> > 
> > Thanks for the tips Nate.  My problem is that it works just fine with
> > rigctl, but with grig, I get a segmentation fault.  Maybe I can still
> > use it, or do something similar with printing to std_err or something.
> > 
>

(Continue reading)

Rob Frohne | 9 Aug 2007 13:06

S Meter Calibration (STRENGTH and RAWSTR)?

Hi All,

Does anyone know how the calibration on the S meter should be set?  I am
trying to calibrate the S meter in grig.  Both STRENGTH and RAWSTR give
me the same number for the TS-850S.  (It looks like it goes from 0 to 30
approximately.)  What is the difference between RAWSTR and STRENGTH
supposed to be?

Thanks & 73,

Rob, KL7NA

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Rob Frohne | 9 Aug 2007 15:27

Kenwood beta testers needed.....

Hi,

I just added slope tune capability for the TS-850S.  If you have another
Kenwood radio that has the slope tune feature, I would be willing to
give a try to add it into your backend, if you are willing to test it
for me.  This is a limited time offer, as I will soon forget what I
needed to do to add this feature, and I will also get busy with other
things.

73,

Rob, KL7NA

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Rob Frohne | 9 Aug 2007 15:38

How should I submit patches?

Hi,

I'm not very familiar with submitting patches, but I have some
improvements in the Kenwood backend, especially the TS-850 backend.

1)  Get_level(CWPITCH) could cause a segmentation fault.  This is now
fixed.  Grig now works with the TS-850 without crashing.  There are
still some issues, such as the S meter calibration, and filter
selection.  The calibration is a hamlib issue, and the filter selection
is probably a grig issue.
2)  The TS-850S had a few typos in the parameter lengths in the call to
kenwood_transaction.  I don't know if this was causing trouble, but it
is fixed.
3)  The TS-850S interface has been sped up at least an order of
magnitude which is nice for programs like grig.

The files patched are: rig.h, misc.c, kenwood.c, and ts850.c

Please provide explicit instructions on how to create the patches I
should submit from these files.

Thanks & 73,

Rob, KL7NA

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

(Continue reading)

Alexandru Csete | 9 Aug 2007 16:27

Picon

Picon

Re: S Meter Calibration (STRENGTH and RAWSTR)?

Quoting Rob Frohne <frohro <at> wwc.edu>:
> Hi All,
> 
> Does anyone know how the calibration on the S meter should be set?  I am
> trying to calibrate the S meter in grig.  Both STRENGTH and RAWSTR give
> me the same number for the TS-850S.  (It looks like it goes from 0 to 30
> approximately.)  What is the difference between RAWSTR and STRENGTH
> supposed to be?
> 

RAWSTR is the raw value, which is usually rig specific. In this case it can be 0
to 30.

STRENGTH is the signal strength in dB with S9 corresponding to 0dB. I don't know
if there is any standard yet for how many dB per S-unit, but many rigs use 6dB,
so S0 = -54dB. Grig (and I think xlog too) uses 6dB per S-unit.
Note that the scaling between RAWSTR and STRENGTH is not necessarilly linear.

73
Alex OZ9AEC

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Nate Bargmann | 10 Aug 2007 01:05

Re: S Meter Calibration (STRENGTH and RAWSTR)?

On Thursday 09 August 2007 09:27:50 Alexandru Csete wrote:
> Quoting Rob Frohne <frohro <at> wwc.edu>:
> > Hi All,
> >
> > Does anyone know how the calibration on the S meter should be set?  I am
> > trying to calibrate the S meter in grig.  Both STRENGTH and RAWSTR give
> > me the same number for the TS-850S.  (It looks like it goes from 0 to 30
> > approximately.)  What is the difference between RAWSTR and STRENGTH
> > supposed to be?
>
> RAWSTR is the raw value, which is usually rig specific. In this case it can
> be 0 to 30.
>
> STRENGTH is the signal strength in dB with S9 corresponding to 0dB. I don't
> know if there is any standard yet for how many dB per S-unit, but many rigs
> use 6dB, so S0 = -54dB. Grig (and I think xlog too) uses 6dB per S-unit.
> Note that the scaling between RAWSTR and STRENGTH is not necessarilly
> linear.

As I understand it, the commonly accepted value between S units is 6dB.  Very 
few radios meet that.  The radios I have placed on the bench and checked with 
a service monitor have not come any where close to a 6dB stepping nor have 
they been anywhere close to linear across the range.  They are, of course, 
refered to as "relative" signal strength meters.

In the backend code, the coder can only map to what the radio the coder has 
provides for values.  One unit of a given model is certainly not 
representative of a production run and certainly not indicative of an entire 
model series.

(Continue reading)

Group

gmane.linux.hams.hamlib.devel.

Project Web Page

Ham Radio Control Libraries developers

Search Archive

Page

1 | 2 | 3 | 4 | 5

Articles in period: 41

August 2007

Language

Change language

Options

Current view: Threads only / Showing only 20 lines / Not hiding cited text.
Change to All messages, whole messages, or hide cited text.

Post a message
NNTP Newsgroup
Classic Gmane web interface
XML

XML

RSS Feed
List Information

About Gmane

Recent entries

Bindings modification (20 May 2013)
Windows builds now have threads! (18 May 2013)
[TS-590S] Hamlib command functionality with the TS-590S (13 May 2013)
Successful compilation on Cygwin (10 May 2013)
Debian CLang build success (7 May 2013)
[TS-590S} TS-590S archives? (7 May 2013)
[Joe Taylor] [Wsjt-devel] Blocking calls to hamlib (2 May 2013)
Bug in Win32 tcflush (1 May 2013)
hamlib.mk for MXE ? (24 Apr 2013)
Building Hamlib with MXE (16 Apr 2013)
rig_init question (14 Apr 2013)
2nd Call For Papers, 20th Annual Tcl/Tk Conference 2013 (9 Apr 2013)
Odd Behaviour Controlling IC-910 With Gpredict/hamlib (27 Mar 2013)
Perseus Support (25 Mar 2013)
Building Hamlib with MXE (26 Mar 2013)
Error trying to set hamlib PTT in soundmodem (25 Mar 2013)
Error trying to set hamlib PTT in soundmodem (25 Mar 2013)
Wouxun support (24 Mar 2013)
FreeDV project integrating Hamlib (24 Mar 2013)
Still building hamlib with MEX (3 Mar 2013)
Cross-building hamlib with MXE (2 Mar 2013)

Archives

61	May 2013
24	April 2013
37	March 2013
64	February 2013
36	January 2013
41	December 2012
65	November 2012
25	October 2012
21	September 2012
18	August 2012
61	July 2012
46	June 2012
62	May 2012
19	April 2012
52	March 2012
4	February 2012
59	January 2012
45	December 2011
21	November 2011
27	October 2011
11	September 2011
40	August 2011
50	July 2011
66	June 2011
61	May 2011
42	April 2011
42	March 2011
94	February 2011
74	January 2011
39	December 2010
43	November 2010
45	October 2010
49	September 2010
61	August 2010
37	July 2010
36	June 2010
51	May 2010
55	April 2010
58	March 2010
79	February 2010
43	January 2010
71	December 2009
50	November 2009
16	October 2009
41	September 2009
4	August 2009
11	July 2009
9	June 2009
50	May 2009
34	April 2009
49	March 2009
91	February 2009
99	January 2009
66	December 2008
59	November 2008
88	October 2008
44	September 2008
18	August 2008
10	July 2008
17	June 2008
36	May 2008
39	April 2008
25	March 2008
20	February 2008
23	January 2008
10	December 2007
27	November 2007
21	October 2007
20	September 2007
41	August 2007
48	July 2007
15	June 2007
25	May 2007
5	April 2007
20	March 2007
20	February 2007
51	January 2007
49	December 2006
49	November 2006
87	October 2006
39	September 2006
8	August 2006
23	July 2006
6	June 2006
17	May 2006
31	April 2006
38	March 2006
26	February 2006
13	January 2006
22	December 2005
26	November 2005
9	October 2005
4	September 2005
26	August 2005
8	July 2005
48	June 2005
31	May 2005
120	April 2005
62	March 2005
26	February 2005
69	January 2005
36	December 2004
26	November 2004
16	October 2004
31	September 2004
5	August 2004
18	July 2004
1	June 2004

Design

Zawodny | Right Menu | Left Menu

Your Own Design

Paste the URL of your CSS below. Download CSS template