From: Stephane F. <f8...@fr...> - 2012-01-15 22:47:33
|
Hallo Jürgen, dim, Jan 15, 2012, Jürgen Hochwald skribis: > I'am trying to communicate with my Ten-Tec Omni 6. > > The connection is done with a simple serial cable and an adapter from 25 to 9 > pins, because the pc has only a 9 pin port. Is it a self-made cable? Does the Ten-Tec Omni 6 have a standard serial interface (DB9?) or a jack interface like many of (Icom) CI-V rigs? > The communication itself seems to be corrcet, when I display the transferred > bits with the -v option, but then I get an 'Protocol error'. > > When I use hamlib inside another app (cqrlog), then trx unusabe itself. The > displayed frequency is quickly switching between two digits in the 10 Hz > display (some display segments are simply less bright). When I adjust the > frequency, it is always moving to lower values when I rotate the knob clock > wise (to higher frequencys) > > --------------->8============ > cfjh@wilhelm:~> rigctl -r /dev/ttyS0 -s 9600 -m 319 -c 04 > -vvvvvvvvvvvvvvvvvvvv f BTW, why aren't you using the rigID 351 instead ? It is for the OmniVI+ but is OK for the Omni VI. The CI-V address would already be setup appropriately (0x04). [...] > Opened rig model 319, 'IC-735' > Backend version: 0.7.1, Status: Beta > TX 6 bytes > 0000 fe fe 04 e0 03 fd ...... > RX 11 characters > 0000 fe fe 00 04 00 90 94 82 01 00 fd ........... [...] > get_freq: error = Protocol error According to the CI-V protocol, the request sent by the PC should be echoed by the bus, because the TXD signals and RXD signals are tied together. Hamlib is complaining because of that unexpected protocol. If you want to make a quick check, tie together both signals. On top of that, the IC-735 exchanges frequency data on 4 bytes, while later rigs, including the Omni6, exchanges data on 5 bytes. Could you please try your tests with the rigID 351 ? Martin, AA6E, might want to give advices since he is our expert on the topic. 73 -- Stephane - F8CFE |