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

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

Hi Wilbert,

thanks for the ideas. And when I read it, I almost thought that was the
problem.

> > Any other suggestions why it works with N1MM and
> > not with hamlib? Did I get all the parameters right?
> 
> Not quite. You should also turn RTS on (pin 7).
> 
As far as I can see rts_state and dtr_state are both set to ON in my
command. Is there another option for RTS that I missed?

> Also, check with a scope/multimeter that 'ON' means 'positive volts' on those 
> pins...perhaps they should both be 'OFF' :-)
> 
And here I thought: That's it! Because I had only checked this with
RedmondOS. So today I measured it all with rigctl setting the RTS and
DTR pins 4 and 7. For ON it is 7.7V on either and for OFF it is -5.6V.
Thus, ON means positive voltage.

> Wilbert, PE7T
> 
> PS: Some Icom rigs operate the CI-V interface factory-default in 'transceive' 
> mode...meaning that the rig fires off QRG info when you touch the dial. Maybe 
> your rig does this, which is why you get collisions on the CI-V bus when 
> Hamlib polls the rig. 'transceive mode' can probably be turned off in a menu 
> somewhere.

I checked this again and both trx and 731 mode are OFF in the 7400 menu.

When I tried setting the frequency again, because it worked all the
time, I received some echoes. Perhaps this helps anyhow:

> Rig command: F 7013000   
> TX 11 bytes
> 0000	 fe fe 66 e0 05 00 30 01 07 00 fd	..f...0....
> RX 1 characters
> 0000	 fc	.
> TX 11 bytes
> 0000	 fe fe 66 e0 05 00 30 01 07 00 fd	..f...0....
> RX 3 characters
> 0000	 07 00 fd	...
> TX 11 bytes
> 0000	 fe fe 66 e0 05 00 30 01 07 00 fd	..f...0....
> RX 4 characters
> 0000	 01 07 00 fd	....
> TX 11 bytes
> 0000	 fe fe 66 e0 05 00 30 01 07 00 fd	..f...0....
> RX 4 characters
> 0000	 01 07 00 fd	....
> Frequency: set_freq: error = Protocol error

To narrow it down again: The problem is between 7400 and laptop.
Setting works, getting doesn't! Voltages on both sides are ok.

Could it be a timing problem? SUDDENLY IT WORKS
(I'll leave the rest above for documentation purposes, hi)

What did I do? I changed the baud rate downwards! It works with 1200
and 4800 baud. Here the trace:

> Rig command: f
> TX 6 bytes
> 0000	 fe fe 66 e0 03 fd	..f...
> RX 6 characters
> 0000	 fe fe 66 e0 03 fd	..f...
> RX 11 characters
> 0000	 fe fe e0 66 03 00 30 01 07 00 fd	...f..0....
> Frequency: 7013000
> 
> Rig command: m
> TX 6 bytes
> 0000	 fe fe 66 e0 04 fd	..f...
> RX 6 characters
> 0000	 fe fe 66 e0 04 fd	..f...
> RX 8 characters
> 0000	 fe fe e0 66 04 03 02 fd	...f....
> TX 7 bytes
> 0000	 fe fe 66 e0 1a 03 fd	..f....
> RX 7 characters
> 0000	 fe fe 66 e0 1a 03 fd	..f....
> RX 8 characters
> 0000	 fe fe e0 66 1a 03 06 fd	...f....
> Mode: CW
> Passband: 350

So now, the developers: Is this common? Because I always read it should
work best at highest baud rate.

A confused, but glad, op will enjoy the weekend now!

73 de Corny
-- 
                             Cornell P Gonschior, Df6fR