ad: elecraft

Icom ID-5100 and CIV control

Discussion in 'Computers, Hardware, and Operating Systems' started by N8SHA, Aug 27, 2021.

ad: L-HROutlet
ad: l-rl
ad: L-MFJ
ad: MessiPaoloni-1
ad: L-Geochron
ad: abrind-2
ad: Left-3
ad: Left-2
ad: HRDLLC-2
  1. N8SHA

    N8SHA Ham Member QRZ Page

    Has anybody out there successfully connected and controlled an Icom ID-5100 using CIV? I've tried a couple of options, and no luck. I've even used a serial port monitor / sniffer to send commands direct, and view commands being sent. I can see the data going out, but nothing coming back.

    The serial port monitor do, however, show the data back and forth from the CS-5100.

    Matt
    N8SHA
     
  2. K7MEM

    K7MEM Ham Member QRZ Page

    I don't have a ID-5100, but I do use the CI-V communications on a much older Icom unit.

    What are you using as a interface between the computer and the radio?

    I use a USB to RS-232 Converter cable that connects into a home brew RS-232 to CI-V level converter. But I built that a long time ago and they have since produced a cable that goes directly from USB to CI-V. The ad says it works with all CT-17 compatible radios.

    BTW, hi from Schwartz Creek.
     
  3. N8SHA

    N8SHA Ham Member QRZ Page

    I've tried a couple of different USB cable adapters. One from RT systems, the other from BlueMaxx49ers. No luck so far and have not found anybody who has done it successfully. I'd like to tinker with it little but, but I'm just not willing to soak the money into a $50+ Icom cable to find out it doesn't work.

    And greetings from Fenton!
    -Matt
     
  4. W5UAA

    W5UAA Ham Member QRZ Page

    Ah! Looks like another case of... the computer's USB power is not enough. Try a "powered" USB hub--one that comes with a 5 volt / 2 Amp wall wart between your computer and your radio.

    Computer -> USB A/B cable -> "powered" USB hub -> USB A/B cable that converts to RS-232 -> Radio

    Remember, that special cable is trying to convert a 0 and 5 volt level to the bare minimum requirement of RS-232. The standard for RS-232 is +3 to +15 volts (logic 0), and -3 to -15 volts (logic 1). But some RS-232 receivers need more than plus AND MINUS 3 volts and some need more than plus AND MINUS 5 volts. (I was an expert with RS-232 back in the 80's.)
     
  5. K7MEM

    K7MEM Ham Member QRZ Page

    Oops! Sorry I spelled Swartz Creek wrong. I'm not sure why I always try to spell it wrong. I have only been living here for a year and am not use to the area yet.

    The fact that the CS-5100 works with the IC-5100 says a few things. It indicates that you have all of the menu settings correct. And it indicates that the ID-5100 should work with a different interface cable.

    Unless the radio receives a valid command that requests information, the radio will not respond. This can mean several things. I would first double check the baud rates in both the computer and the radio. The simplest would be to set the radio to "auto". Then check the address for the radio. Unless the command address is correct, the radio will reject the command and not respond. If I read the manual correctly, the radio also has a setting that will echo your commands. Turn on that setting and see what you get back.

    Next I would check the hardware. CI-V communication is handled over a 2-wire bidirectional line. But your ID-5100 has a three conductor jack (SP2) that doubles as a speaker output and a CI-V communication line. I would double check that the CI-V signal, from the interface cable, is correct. The manual shows that the CI-V signal should be on the "ring" and "sleeve". The speaker uses the "tip" and "sleeve". If the interface cable uses the "tip" there could be a problem.

    If you had a scope available, you should be able to see the CI-V signal, even with the cable disconnected from the radio. Although, you might have to add a pull-up resistor.

    Just keep trying. You will happen on the solution, sooner or later.
     
  6. N8SHA

    N8SHA Ham Member QRZ Page

    Monitoring the serial port, this is what I seen when I run the CS-5100 and retrieve "Information" from the radio:

    [29/08/2021 16:21:31] - Open port COM7 (C:\Program Files (x86)\Icom\CS-5100\CS5100.exe)
    [29/08/2021 16:21:31]Changed baudrate: 9600
    [29/08/2021 16:21:31]Enabled RTS
    [29/08/2021 16:21:31]Disabled DTR
    [29/08/2021 16:21:31]Changed line control: Databits 8, Parity none, StopBits 1
    [29/08/2021 16:21:31]Changed flow control: ControlHandShake 0x00, FlowReplace 0x80000040, XonLimit 16000, XoffLimit 24000
    [29/08/2021 16:21:31] Written data (COM7)
    fe fe ee ef e0 34 84 00 00 fd þþîïà4„..ý
    [29/08/2021 16:21:31] Read data (COM7)
    fe fe ef ee e1 34 84 00 01 2d 03 20 20 20 20 20 þþïîá4„..-.
    20 20 20 20 20 20 20 20 20 20 20 00 03 00 00 01 .....
    00 00 00 00 00 00 00 00 30 44 39 43 30 35 30 30 ........0D9C0500
    30 30 32 32 37 34 fd 002274ý
    [29/08/2021 16:21:31] - Close port COM7

    I can also emulate this by sending opening a connection on the com port and sending the commands:

    fe fe ee ef e0 34 84 00 00 fd

    Interestingly, the Address for the radio is set to 8c, and the CS-5100 seems to be using "ee"

    I've tried sending various of reading the current frequency, but no luck getting anything back:
    fe fe 8c ef 03 00 fd
    fe fe ee ef 03 00 fd
    fe fe 8c ef 03 fd
    fe fe ee ef 03 fd


    Matt - N8SHA
     
  7. W5UAA

    W5UAA Ham Member QRZ Page

    Well, the first thing I notice in the serial port monitoring software is that you're getting garble:

    [29/08/2021 16:21:31] Written data (COM7)
    fe fe ee ef e0 34 84 00 00 fd þþîïà4„..ý <----------GARBLE

    Second thing I see in the above command is "fe fe" is the preamble--this is good so far. The next (controller to radio) is the transceiver address. Default CI-V address for the ID-5100 is 8C. I see "ee" in the above command. It goes downhill from there. The next hex number should be the controller address. Default is E0. Then the major command should come next. Major commands for the ID-5100 are from 00 to 24. ...25 and above are invalid.

    I also see more garble and wrong CI-V addresses in what you're getting back from the radio:

    [29/08/2021 16:21:31] Read data (COM7)
    fe fe ef ee e1 34 84 00 01 2d 03 20 20 20 20 20 þþïîá4„..-. <-------GARBLE
    20 20 20 20 20 20 20 20 20 20 20 00 03 00 00 01 .....
    00 00 00 00 00 00 00 00 30 44 39 43 30 35 30 30 ........0D9C0500
    30 30 32 32 37 34 fd 002274ý <--------GARBLE
    [29/08/2021 16:21:31] - Close port COM7

    And more importantly, in the first line:
    fe fe ef ee etc. should start with
    fe fe E0 8C etc.


    Commands TO the radio should be:
    FE FE 8C E0 followed by a major command, sub command, and data that follows the format for that command and ending in FD.

    Commands FROM the radio should be:
    FE FE E0 8C followed by a major command, sub command, and data that follows the format for that command and ending in FD.

    And all the other commands you listed are just as hosed up.

    fe fe ee ef e0 34 84 00 00 fd
    and
    fe fe 8c ef 03 00 fd
    fe fe ee ef 03 00 fd
    fe fe 8c ef 03 fd
    fe fe ee ef 03 fd

    I'd start by resetting your ID-5100 to factory defaults. Page 17-3 of the full manual. and then get familiar with the CI-V setup areas in your radio's menu and double check what the defaults are.

    And then what ever software you're using, make sure it's set to communicate with CI-V address 8C, baud rate, start bit, stop bit(s), parity, hardware or software control, etc.
     
  8. NQ4T

    NQ4T XML Subscriber QRZ Page

    The first thing a CI-V will do is echo the command back. If I send my IC-7100 those bytes, it bounces them right back. It doesn't modify this either; so the fact it returned exactly what it sent is correct.

    But it doesn't get any better from there. Rather than the last two bytes being 00 FD on the echo, they're 01 2D, then some garbage, then he gets an FD at the very end. I'm starting to wonder if his CI-V adapter/converter isn't really screwed up...that or his radio is messed up. The fact the echo got messed up could go either way.

    Actually, fe fe 8c ef 03 fd is valid. Controller does not have to be E0. If I send fe fe 88 ef 03 fd to my 7100, it spits out the VFO. In fact I can put whatever I want for the controller address as long as it's not a reserved character.

    What actual hardware interface does this come with? Everything I see for CS-5100 specifically says it's cloning software.

    I know the 0x00 address works for rigs with CI-V transcieve; which the 5100 is new enough it should...so you can always use that as a "universal" radio address.
     
    Last edited: Sep 6, 2021

Share This Page