Thomas Beierlein | 2 May 21:42 2010
Picon

Re: Planning release 1.2.11 next week

Hi Stephan and gang,

I just made final tests and found a problem here.

If I run

./configure --enable-tcl-binding 
make

hamlib always tries to compile the python wrapper but crashes as it is
not configured.

./configure --enable-tcl-binding --with-python-binding 
make

works well.

I had not the time yet to look into the details. I will try it in next days.

Tom Dl1JBE.

On Fri, Apr 30, 2010 at 10:51:31AM +0200, Stephane Fillod wrote:
> Hi,
> 
> The subject says it all. It would be good to make a new release,
> hopefully in sync with the fldigi release. You still have couple
> of days left to commit/submit your patches. The exact day of the
> release is flexible.
> 
> 73
(Continue reading)

Stephane Fillod | 2 May 23:56 2010
Picon

Re: Planning release 1.2.11 next week

Hi Tom,

Sun, May 02, 2010, Thomas Beierlein skribis:
> I just made final tests and found a problem here.
> 
> If I run
> 
> ./configure --enable-tcl-binding 
> make
> 
> hamlib always tries to compile the python wrapper but crashes as it is
> not configured.

Should be fixed now in SVN repo (r2903).

Thanks for the report.

73
--

-- 
Stephane - F8CFE

------------------------------------------------------------------------------
Thomas Beierlein | 3 May 12:52 2010
Picon

Re: Planning release 1.2.11 next week

Hi Stephane,

On Sun, May 02, 2010 at 11:56:50PM +0200, Stephane Fillod wrote:
> Hi Tom,
> 
> Should be fixed now in SVN repo (r2903).

looks good so far. Thnak sfor the quick fix.

73, 
	Tom DL1JBE.

> 
> Thanks for the report.
> 
> 73
> -- 
> Stephane - F8CFE
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Hamlib-developer mailing list
> Hamlib-developer <at> lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

--

-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--
(Continue reading)

Nate Bargmann | 4 May 05:10 2010
Picon

Re: hamlib doesn't build

Since rev 2903 which changed bindings/Makefile.am, make dist fails in
the bindings directory:

make[1]: Entering directory `/home/nate/hamlib/bindings'
make[1]: *** No rule to make target `Hamlib.py', needed by `distdir'.  Stop.
make[1]: Leaving directory `/home/nate/hamlib/bindings'
make: *** [distdir] Error 1

As a result, the daily snapshot has not been updated since Sunday
morning, rev 2902.

73, de Nate >>

--

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://n0nb.us/index.html

------------------------------------------------------------------------------
Thomas Beierlein | 4 May 18:16 2010
Picon

Re: Planning release 1.2.11 next week

Hi Stephane,

just checked (after some time) the actual version on my old TS-570D.
Sorry to say but it rejects most of the commands.

A more closely inspection shows that the ';' (command termination character) gets dropped most of the
time. As result the rig does either
a) not answer at all or
b) reply with '?;' meaning command not understood.

Just rechecked that it works with 1.2.10. I will look into it and see
if I can find the reason.

73, de tom DL1JBE.

 On Fri, Apr 30, 2010 at 10:51:31AM +0200, Stephane Fillod wrote:
> Hi,
> 
> The subject says it all. It would be good to make a new release,
> hopefully in sync with the fldigi release. You still have couple
> of days left to commit/submit your patches. The exact day of the
> release is flexible.
> 
> 73
> -- 
> Stephane - F8CFE
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
(Continue reading)

Thomas Beierlein | 4 May 19:17 2010
Picon

Re: Planning release 1.2.11 next week

On Tue, May 04, 2010 at 06:16:01PM +0200, Thomas Beierlein wrote:
> Hi Stephane,
> 
> just checked (after some time) the actual version on my old TS-570D.
> Sorry to say but it rejects most of the commands.
> 
Ok. I found it. The commit to rev2885 changed kenwood.c and broke
the code. The old code sends an additional 'cmdtrm' command terminator
if the package is not already terminated by ';' or '\r'.

The new code combines the sending of the data block and the additional
character, but replaces 'cmdtrm' by sending '\r' instead.

Replacing 
	cmd[len] = '\r';
 in line 189 of kenwood.c by 
	cmd[len] = caps->cmdtrm;
fixes the problem. But I am not sure if that breaks again other rigs.
So anyone who can test on other kenwood rigs (beside TS-570D) should 
do so.

73, de Tom DL1JBE.

--

-- 
"Do what is needful!"
Ursula LeGuin: Earthsea
--

------------------------------------------------------------------------------
(Continue reading)

Stephane Fillod | 4 May 23:14 2010
Picon

Re: Planning release 1.2.11 next week (Attn: kenwood backend)

Tue, May 04, 2010 Thomas Beierlein skribis:
> On Tue, May 04, 2010 at 06:16:01PM +0200, Thomas Beierlein wrote:
> > just checked (after some time) the actual version on my old TS-570D.
> > Sorry to say but it rejects most of the commands.
> > 
> Ok. I found it. The commit to rev2885 changed kenwood.c and broke
> the code. The old code sends an additional 'cmdtrm' command terminator
> if the package is not already terminated by ';' or '\r'.
> 
> The new code combines the sending of the data block and the additional
> character, but replaces 'cmdtrm' by sending '\r' instead.
> 
> Replacing 
> 	cmd[len] = '\r';
>  in line 189 of kenwood.c by 
> 	cmd[len] = caps->cmdtrm;
> fixes the problem. But I am not sure if that breaks again other rigs.
> So anyone who can test on other kenwood rigs (beside TS-570D) should 
> do so.

Looking at the code, this should fix more rigs than it breaks.
So please, go ahead and commit.

Needless to say, can ALL owners of kenwood rigs report their testing
with Tom's fix?

73
--

-- 
Stephane - F8CFE

(Continue reading)

Alessandro Zummo | 4 May 23:57 2010
Picon

Re: Planning release 1.2.11 next week (Attn: kenwood backend)

On Tue, 4 May 2010 23:14:30 +0200
Stephane Fillod <f8cfe <at> free.fr> wrote:

> Looking at the code, this should fix more rigs than it breaks.
> So please, go ahead and commit.
> 
> Needless to say, can ALL owners of kenwood rigs report their testing
> with Tom's fix?

 will test, but the fix seems appropriate to me.

 the point is that no one should call kenwood_transaction()
 with a termination character in the buffer, so that if on line 188
 will go away and caps->cmdtrm will always be used.

--

-- 

 Best regards,

 Alessandro Zummo,
  Tower Technologies - Torino, Italy

  http://www.towertech.it

------------------------------------------------------------------------------
Stephane Fillod | 5 May 00:21 2010
Picon

Re: hamlib doesn't build

Mon, May 03, 2010, Nate Bargmann skribis:
> Since rev 2903 which changed bindings/Makefile.am, make dist fails in
> the bindings directory:
> 
> make[1]: Entering directory `/home/nate/hamlib/bindings'
> make[1]: *** No rule to make target `Hamlib.py', needed by `distdir'.  Stop.
> make[1]: Leaving directory `/home/nate/hamlib/bindings'
> make: *** [distdir] Error 1
> 
> 
> As a result, the daily snapshot has not been updated since Sunday
> morning, rev 2902.

Sigh. Should be fixed, hopefully with commit r2906.
So people will be able to test wednesday's snapshot.

Thanks for the report.

73
--

-- 
Stephane - F8CFE

------------------------------------------------------------------------------
Rob Frohne | 5 May 03:46 2010

Re: Planning release 1.2.11 next week (Attn: kenwood backend)

Hi All,

I'm testing with the TS-850SAT.  Here is what I find in general.

1)  The problem I had with hardware handshaking is gone.

2)  If I issue an f command from rigctl, it doesn't work until I set the 
VFO to VFOA (or B).  This is new behavior.  (This behavior seems 
intermittent.  It did that the first couple of times I ran rigctl, and 
now it works properly.)

3)  The "w" command of rigctl no longer works.  It seems to go picking 
daises.   (I  run rigctl, set the vfo, and send the w command, It asks 
for Cmd: I type FA; (the Kenwood command for frequency of VFOA) and it 
does nothing.

73,

Rob, KL7NA

Alessandro Zummo wrote:
> On Tue, 4 May 2010 23:14:30 +0200
> Stephane Fillod <f8cfe <at> free.fr> wrote:
>
>   
>> Looking at the code, this should fix more rigs than it breaks.
>> So please, go ahead and commit.
>>
>> Needless to say, can ALL owners of kenwood rigs report their testing
>> with Tom's fix?
(Continue reading)


Gmane