[Tlf-devel] Re: [Hamlib-developer] support for ten tec orion?

[Rein Couperus]

Tnx for the reaction Stephane...
According to the ten tec document the instruction set of the 565 is similar to 
the model 550. Meanwhile I have added native support for the orion in tlf 
(-0.9.18), which works o.k. (mind you, I will have to live with this trx for 
the next 20 years or so :-) 
When you send stuff to the TRX, success is 100%, but receive fails 10...50% of 
the time ( I have built a health counter into tlf to monitor this).  This is 
also related to wrong priorities in the trx software. As soon as I spin the 
fequency dial, the communication goes haywire, but it finds itself within a 
second.

Here is the dump of the trial with -m 1607:
------------%<----------------

address@hidden:~/tlf/hamlib-1.2.0/tests$ rigctl -r /dev/ttyS2 -s 57600 -m 1607 
-vvvvvvv
rigctl, Hamlib version 1.2.0
Report bugs to <address@hidden>

rig:rig_init called
rig: loading backend tentec
tentec: _init called
rig_register (1601)
rig_register (1607)
rig_register (1603)
rig:rig_open called
TX 3 bytes
0000     3f 45 0d       ?E.
RX 5 characters
0000     5a 21 3f 45 0d Z!?E.
Opened rig model 1607, 'TT-516 Argonaut V'
Backend version: 0.1, Status: Untested

Rig command: f
TX 3 bytes
0000     3f 45 0d       ?E.
RX 5 characters
0000     5a 21 3f 45 0d Z!?E.
get_freq: error = Protocol error

Rig command: m
TX 3 bytes
0000     3f 45 0d       ?E.
read_string: timedout without reading a character
get_mode: error = Protocol error

Rig command:
------------%<----------------
As you see, the Argonaut protocol is completely different, I think the 550 has 
the best potential as a template for a orion driver.

For me it was easier to write the stuff straight into tlf than to try and 
understand hamlib :). I am preparing for a longer sailing trip starting next 
week (I will take my K2 with me to activate some IOTA numbers in north sea 
and baltic...), but as soon as I come back I will be available for testing 
the hamlib orion driver, which I am sure will be ready by then :-)

I have implemented set_frequency, set_mode,  set_RIT, get_frequency, get_mode, 
set_cw_speed, send_cw. Actually, it uses the built-in keyer of the orion 
instead of cwdaemon as well :) This was a bit awkward as the orion wants the 
cw one character at-a-time... so I had to calculate the length of each 
character in order to know when to send the next one. But the result is that 
you cannot hear the difference now, even at 50 wpm. This is definitely 
something you should think about as a hamlib function...
I will upload tlf-0.9.18 today, look in sendqrg.c and write_keyer.c if you 
want to steal the code.... (By the way, I want to do the same for the K2 
later this year, which also has CW send capability).

73, and keep the good work coming...

Rein Pa0R

P.S.: the protocol document for the 565 is on www.rfsquared.com



On Tuesday 04 May 2004 02:33, Stephane Fillod wrote:
> Hi Rein!
>
> On Thu, Apr 29, 2004, Rein Couperus wrote:
> > How do I switch rigctl into 8N2?
>
> Simply pass along this option:  -Cstop_bits=2
>
> To list all the available conf:   rigctl -L -m 1601
>
> > Here is the debug info for my first test... it uses the model 550
> > routine, which is according to ten tec the same as for the 585.
>
>                                                     ^^^
> I guess you meant the 565 (Orion). IMHO, the 565 protocol is closer to the
> Argonaut 516 protocol than the 550. Anyway, I've added basic Orion support
> in CVS tonight. Let me know what you need particulary (set_freq,
> set_mode, set_rit, anything else special?) and I'll try to make it
> before I release a version of Hamlib end of this week.
>
> > This works only 10% of the time, most of the time the RX info is garbled.
> >
> > address@hidden:~/tlf/hamlib-1.2.0/tests$ rigctl -m 1601 -s 57600 -r
> > /dev/ttyS2 -vvvvvvvv
> > rigctl, Hamlib version 1.2.0
> > Report bugs to <address@hidden>
> >
> > rig:rig_init called
> > rig: loading backend tentec
> > tentec: _init called
> > rig_register (1601)
> > rig_register (1607)
> > rig_register (1603)
> > rig:rig_open called
> > TX 3 bytes
> > 0000     58 58 0d       XX.
> > RX 14 characters
> > 0000     20 20 4f 52 49 4f 4e 20 53 54 41 52 54 0d        ORION START.
> > TX 3 bytes
> > 0000     58 58 0d       XX.
>
>                           ^^^
>
> > RX 14 characters
> > 0000     20 20 4f 52 49 4f 4e 20 53 54 41 52 54 0d        ORION START.
> > rig_open: error = Protocol error
>
> Indeed, the Pegasus (550) has an init sequence, and stops if handshake
> fails. Have a try with the Argonaut (id 1607) before 1.2.1 releases.
>
>
> 73
> Stephane
>

> _______________________________________________
> Hamlib-developer mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer

-- 
address@hidden or address@hidden
http://www.couperus.com
http://savannah.nongnu.org/projects/tlf