Ten Tec Pegasus Software

by

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. * On 2012 03 Aug 21:11 -0500, Martin Ewing wrote: > Hello, > > I've committed some upgrades for the TT Jupiter into a new branch > 'aa6e-jupieter'. I hope that's the right way to make them available? That's a good way, Martin, especially if you want others to test it firt before committing it to master or the stable branch. I will probably push 1.2.15.2 out this weekend. I have an update to hiqsdr and will apply that and release.

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. Thanks, St=E9phane, for your info. On Wed 08-Sep-04 at 1732 EDT, Stephane Fillod wrote: > > Then make sure the Jupiter is set to 57600 bauds, 8N1, *with* hardware > handshake (ie. Buku20manajemen20pemasaran20pdf. The cable must have CTS/RTS signals wired).

Thanks to Paul at Ten-Tec for providing the paper copies of the Pegasus. Ten-Tec provides a software together with the transceiver, so hooking it up is quite. N4PY Pegasus Plus Program for Flex, Yaesu, Ten Tec, Elecraft and Kenwood Radios. This allows the software to export a pegasus file interface to any.

> If you have some doubts on Hamlib, you can use a serial terminal like > minicom to make sure the previous parameters are okay by entering > manually some basic commands of the protocol (which is ASCII). I did this just to be certain I could talk with the Jupiter: sh-3.00# minicom jupiter [I type: XX] RADIO START [I type:?A] A.k@ [I type:?B] Bb=FA=E0 So success while communicating with the Jupiter. Siva putrudu movie naa songs free download.

Tentec

> Then proceed with the 'rigctl' program, and test each of the implemente= d > functions (more to come as time permits): > set_freq, get_freq, set_vfo, get_vfo, set_mode, get_mode, > set_split_vfo, get_split_vfo, set_ptt, reset, get_info I had less luck with rigctl: rigctl -vvvvv -m 1602 -s 57600 rigctl, Hamlib version 1.2.2 Report bugs to rig:rig_init called rig: loading backend tentec tentec: _init called rig_register (1601) rig_register (1607) rig_register (1608) rig_register (1602) rig_register (1603) rig_register (1604) rig_register (1605) rig:rig_open called TX 3 bytes 0000 3f 45 0d?E. Read_string: timedout without reading a character Opened rig model 1602, 'TT-538 Jupiter' Backend version: 0.1, Status: Untested Rig command: f TX 3 bytes 0000 3f 45 0d?E. Read_string: timedout without reading a character get_freq: error =3D Protocol error Rig command: v TX 3 bytes 0000 3f 45 0d?E. Read_string: timedout without reading a character get_vfo: error =3D Protocol error Rig command: m TX 3 bytes 0000 3f 45 0d?E. Read_string: timedout without reading a character get_mode: error =3D Protocol error Rig command: l Level: ALC get_level: error =3D Invalid parameter Rig command: reset get_rptr_shift: error =3D Feature not available Rig command: get_mem: error =3D Feature not available TX 3 bytes 0000 3f 4f 0d?O.

RX 3 characters 0000 4f 30 0d O0. Rig command: Split mode: 1 TxVFO: Rig command: get_mem: error =3D Feature not available Rig command: get_ptt: error =3D Feature not implemented Rig command: q rig:rig_close called rig:rig_cleanup called It looks like '?E' is being sent for many of the commands? That's not listed as a Jupiter command in the current Jupiter Programming Reference Guide at Ten-Tec's rfsquared site. And there are actually a few discrepancies in the tiny manual that I emailed Ten Tec about but haven't heard back yet. In any case, while I'm a long time C programmer, I've only just begun looking at the code and am not certain how it all hangs together yet. I thought I'd pass along my findings, though, and will see if I can work on a patch after figuring out the structure of the code. Thanks, Mike AB3AP.