Hello Zilvinas,
On Sat, Mar 01, 2014 at 09:22:57AM +0200, Zilvinas, AUGMA wrote:
>
> Good morning All,
>
> Oops.. Ervin, I only this morning noticed your work announcement on
> the list...
> Quickly compiled and it works as promised! I quickly grepped log
> with earlier QSOs (so far 445 lines) a
On 01/03/14 11:23, Hegedüs Ervin wrote:
> What's the second question?
Oh... Sorry. My questions where what's wrong with my tlf-rigctld link
and maybe this is somehow related with compile warnings I attached
earlier (but now I am not sure).
So here's some research.
Until now I was using:
V
o.k. here's the results with another cable (YASEU CAT cable clone bought
from ebay. I can use only USB cables for my netbook)
lsusb
067b:2303 Prolific Technology, Inc. PL2303 Serial Port
All the same behaviour - I can switch bands, change frequency but no
frequency displayed.
tlf -v -d
Hello Zilvinas,
On Sat, Mar 01, 2014 at 07:29:44PM +0200, Zilvinas, AUGMA wrote:
>
> On 01/03/14 11:23, Hegedüs Ervin wrote:
> > What's the second question?
>
> Oh... Sorry. My questions where what's wrong with my tlf-rigctld
> link and maybe this is somehow related with compile warnings I
> att
hi,
thanks for the report,
On Sat, Mar 01, 2014 at 08:36:07PM +0200, Zilvinas, AUGMA wrote:
>
> o.k. here's the results with another cable (YASEU CAT cable clone
> bought from ebay. I can use only USB cables for my netbook)
>
> lsusb
> 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
>
>
Hello,
On Sat, Mar 01, 2014 at 08:44:05PM +0100, Ervin Hegedüs wrote:
>
> So, based on this I think that's rigctld problem. I'll see that
> soon.
sorry - the problem would be on hamlib's side too. May be the
RIGMODEL 2 can't handle correctly the rig_get_vfo() - but may be
the problem is in the r
On 03/01/2014 03:06 PM, Ervin Hegedüs wrote:
Hello,
On Sat, Mar 01, 2014 at 08:44:05PM +0100, Ervin Hegedüs wrote:
So, based on this I think that's rigctld problem. I'll see that
soon.
sorry - the problem would be on hamlib's side too. May be the
RIGMODEL 2 can't handle correctly the rig_get
Ervin,
As I said - the same problem if I connect to rig directly from tlf via
USB port, omitting rigctld (hence RIGMODEL=2 isn't the reason)
This might be some hamlib and/or tlf condition.
When I run rigctl -v I see some disturbing warnings with every 'f'
request regarding 'invalid cach
On 03/01/2014 03:06 PM, Ervin Hegedüs wrote:
Hello,
On Sat, Mar 01, 2014 at 08:44:05PM +0100, Ervin Hegedüs wrote:
So, based on this I think that's rigctld problem. I'll see that
soon.
sorry - the problem would be on hamlib's side too. May be the
RIGMODEL 2 can't handle correctly the rig_get
1.2.0
Here's rigctld -v after running tlf -v -d (otherwise I can't force
tlf to use hamlib)
After setting 140 (tlf diagnostic?) tlf tries to get currVFO ?
Connection opened from 127.0.0.1:46843
rigctl(d): 'currVFO' '' '' ''
rigctl(d): v 'currVFO' '' '' ''
rigctl(d): v 'currVFO' ''
And yes - rigctld and m=2 isn' related
rigctl -r /dev/ttyUSB0 -m 122 -s 9600 -v
ft857:ft857_open called
Opened rig model 122, 'FT-857'
Backend version: 0.4, Status: Beta
Rig command: v
get_vfo: error = Feature not available
___
Tlf-devel maili
Ed,
On your request
rigctl -r /dev/ttyUSB0 -m 122 -s 9600 -v
First time
Rig command: f
ft857: cache invalid
write_block(): TX 5 bytes
00 00 00 00 03 .
read_block(): RX 5 bytes
00 70 16 24 82 .p.$.
write_block(): TX 5 bytes
00 78 00 00 bb .x...
read_block(): RX 2
Hello Zilvinas,
On Sat, Mar 01, 2014 at 11:38:52PM +0200, Zilvinas, AUGMA wrote:
> 1.2.0
>
> Here's rigctld -v after running tlf -v -d (otherwise I can't
> force tlf to use hamlib)
> After setting 140 (tlf diagnostic?)
yes, now I just checked the code, and if you start Tlf with "-d",
t
13 matches
Mail list logo
