Re: [Hamlib-developer] hamlib 1.2.8 and IC-7400

[Corny, D. <df...@gm...>]

Hi Lada,

thanks for your questions. Here are my first answers. I have to check
some tonight.

Am Thu, 4 Dec 2008 14:41:13 +0100 (CET) schrieb Ladislav Vaiz
<sp...@na...>:

> Hi,
> what is power supply for radio side (+8V on schematics) ?

The 8V come from ACC2 of the 7400.

> If you use terminal program like minicom, does it echo typed characters?

I didn't use minicom yet, because I thought I need to type CIV
commands. And that's what hamlib does as well. I am not sure what
exactly to do with minicom, but I'll fool around tonight.

> What voltage is on cannon pins 4 and 7 ?

What does 'cannon' mean? Pins 4 and 7 are DTR and RTS and they are
actually set to ON. So I have my laptops RS-232 level on these pins,
this is something about 7V.

> Do you have oscilloscope to see signal shapes?

I have one, but I didn't record the signal shapes.

> And my favorite mistake: do you have cannon connected to the right 
> connector? :-)

I don't understand the question, sorry. But it is the same hardware
configuration N1MM works without any problems (I only have one serial
port on the laptop).

> Is the /dev/ttyS0 opened only by rigctl (as root lsof /dev/ttyS0)

Didn't check yet, but this is the first time I use the RS-232 on my
laptop, so no other program should be using it. I'll tell you tonight.

tks es 73 de Corny
> 
> 73 Lada, OK1ZIA
> 
> 
> 
> On Wed, 3 Dec 2008, Corny, Df6fR wrote:
> 
> > Hi,
> >
> > a few weeks ago I got my new radio, a IC-7400, and I thought it would
> > be useful for contests to connect it to a laptop via CIV. So I built
> > the opto-isolated converter: http://www.plicht.de/ekki/civ/if-gary.html
> >
> > Since I want to use N1MM as contest logger, I first tested it on
> > RedmondOS with N1MM and it worked out of the box. So I thought it
> > should be no problem to run it with hamlib for my everyday logging on
> > Debian Lenny. I installed lihamlib2 and libhamlib-utils, version
> > 1.2.7..., but I had some problems. So I installed 1.2.8 from source.
> >
> > I adjusted the rigctl parameters to the values N1MM uses, but it does
> > not work as expected. Here is my command used:
> > $ rigctl --model=346 --rig-file=/dev/ttyS0 --serial-speed=9600
> > --civaddr=0x66 --set-conf=data_bits=8,stop_bits=1,serial_parity=None,
> > rts_state=ON,dtr_state=ON -vvvvv
> >
> > The thing is, hamlib only receives rubbish, but can send commands to
> > the IC-7400 which are executed, i.e. setting frequency and mode. If I
> > want to get the frequency with f: "get_freq: error = Communication bus
> > collision".
> >
> > Here is a complete copy of the trace, including successful set commands:
> >
> > rigctl, Hamlib version 1.2.8
> > Report bugs to <ham...@li...>
> >
> > rig:rig_init called
> > rig: loading backend icom
> > icom: _init called
> > rig_register (355)
> > rig_register (309)
> > rig_register (310)
> > rig_register (311)
> > rig_register (313)
> > rig_register (314)
> > rig_register (315)
> > rig_register (319)
> > rig_register (320)
> > rig_register (321)
> > rig_register (323)
> > rig_register (346)
> > rig_register (324)
> > rig_register (328)
> > rig_register (330)
> > rig_register (326)
> > rig_register (327)
> > rig_register (347)
> > rig_register (357)
> > rig_register (329)
> > rig_register (345)
> > rig_register (356)
> > rig_register (360)
> > rig_register (331)
> > rig_register (312)
> > rig_register (316)
> > rig_register (332)
> > rig_register (334)
> > rig_register (344)
> > rig_register (335)
> > rig_register (336)
> > rig_register (358)
> > rig_register (337)
> > rig_register (338)
> > rig_register (339)
> > rig_register (340)
> > rig_register (341)
> > rig_register (342)
> > rig_register (343)
> > rig_register (303)
> > rig_register (304)
> > rig_register (306)
> > rig_register (307)
> > rig_register (352)
> > rig_register (353)
> > rig_register (351)
> > rig_register (354)
> > rig:rig_open called
> > Opened rig model 346, 'IC-746PRO'
> > Backend version: 0.4, Status: Untested
> >
> > Rig command: f
> > TX 6 bytes
> > 0000	 fe fe 66 e0 03 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > TX 6 bytes
> > 0000	 fe fe 66 e0 03 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > TX 6 bytes
> > 0000	 fe fe 66 e0 03 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > TX 6 bytes
> > 0000	 fe fe 66 e0 03 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > get_freq: error = Communication bus collision
> >
> > Rig command: m
> > TX 6 bytes
> > 0000	 fe fe 66 e0 04 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > TX 6 bytes
> > 0000	 fe fe 66 e0 04 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > TX 6 bytes
> > 0000	 fe fe 66 e0 04 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > TX 6 bytes
> > 0000	 fe fe 66 e0 04 fd	..f...
> > RX 1 characters
> > 0000	 fc	.
> > get_mode: error = Communication bus collision
> >
> > Rig command: M LSB 0
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 00 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 00 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 00 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 00 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > Mode: Passband: set_mode: error = Communication bus collision
> >
> > Rig command: M CW 0
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 03 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 03 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 03 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > TX 7 bytes
> > 0000	 fe fe 66 e0 06 03 fd	..f....
> > RX 1 characters
> > 0000	 fc	.
> > Mode: Passband: set_mode: error = Communication bus collision
> >
> > Rig command: F 7025000
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 00 50 02 07 00 fd	..f...P....
> > RX 1 characters
> > 0000	 fc	.
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 00 50 02 07 00 fd	..f...P....
> > RX 1 characters
> > 0000	 fc	.
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 00 50 02 07 00 fd	..f...P....
> > RX 1 characters
> > 0000	 fc	.
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 00 50 02 07 00 fd	..f...P....
> > RX 1 characters
> > 0000	 fc	.
> > Frequency: set_freq: error = Communication bus collision
> >
> > Rig command: F 7026001
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 01 60 02 07 00 fd	..f...`....
> > RX 1 characters
> > 0000	 fc	.
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 01 60 02 07 00 fd	..f...`....
> > RX 1 characters
> > 0000	 fc	.
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 01 60 02 07 00 fd	..f...`....
> > RX 1 characters
> > 0000	 fc	.
> > TX 11 bytes
> > 0000	 fe fe 66 e0 05 01 60 02 07 00 fd	..f...`....
> > RX 1 characters
> > 0000	 fc	.
> > Frequency: set_freq: error = Communication bus collision
> >
> >
> > I would be very glad if someone could point me in the right direction,
> > where I should take a closer look at. I am not a subscriber to the list,
> > so please put me in the Cc.
> >
> > Thanks a lot and 73,
> > Corny, Df6fR
> > --
> >                             Cornell P Gonschior, Df6fR
> >


-- 
                             Cornell P Gonschior, Df6fR