[ICOM] IC-706MKIIG - It cannot be this difficult

Ekki Plicht (DF4OR) ep at plicht.de
Wed Jun 14 13:57:36 EDT 2006


On Wednesday 14 June 2006 03:41, N5PA wrote:
> I cannot believe that it is this difficult to connect an IC-706MKIIG to
> DX4WIN and WriteLog.  

Indeed, it shouldn't be :-)

[...]

> I cannot control the radio at all in WriteLog but when I spin the VFO the
> Radio Button goes from "No Rig!" to "50000 kHzUSB".

That fact alone is telling us something - something arrives. Usually, when a 
software _does_ receive something but print's rubbish (i.e. wrong 
frequencies) it's either the wrong baudrate or wrong framing. Can you set the 
number of stop bits with Writelog or DX4Win? If so, have you tried to change 
it from 1 to 1.5 to 2?

> When I run CI-V Test by DF4OR, it communicates with the 706.  The
> configurations are as follows:
>
> COM: COM2
> Baudrate: 9600
> Fm adr: E0
> To adr: 48, 706
> Command: 1a
> Subcmd: 03
> Next Field: 00
>
> I hit the send button and then spin the dial and it shows the correct
> frequency as I spin the dial.  I am totally baffled by this.  The radio
> definitely communicates with the computer using the test program but DX4WIN
> and WriteLog do not work.  Any Help will be appreciated.

This only shows that the communication is working in one way, from radio to 
computer. Please try the following with CIVTEST:

Make sure you receive good data when you wiggle that dial. That makes sure you 
have got a good comport and baudrate.

In CIVTEST select 
- fm adr: EO (although it does not really matter)
- to adr: 48 (THIS really matters, MUST be the same as your 706 is set to)
- cmd: 2 
- subcmd: empty and checkbox above unchecked (important)
- all other inputs and checkboxes empty/unchecked

Now hit "send".

Does the radio reply in any way? If yes - brilliant, then you know that the 
other way (computer to radio) is working as well. If not - tough. Back to 
square one.

If the rig emits data like when tuning the dial but does not react to 
commands, it can have (at least) two reasons: the level converter or the rig. 

The level converter can be quite easily checked with a volt meter (better with 
an oscilloscope). See my website on the CI-V protocol for hints on trouble 
shooting a level converter.

Or indeed the rig can be malfunctioning. But that is quite rare, in all my 
life I have seen only one Icom rig where the CI-V interface was faulty in 
this manner.

Oh, a third reason could be a faulty (halfways) COM port. Rare but happens.

Let me know what you find, I am happy to help.

73,
Ekki, DF4OR


More information about the Icom mailing list