[chirp_users] Icom ID-5100A (was Re: Linux CHIRP, ICOM 7100, "unicode strings" error)

[Martin Cooper]

Apparently quite different. Looking at the "full" manual for the ID-5100A,
the entire command set (0x1A) that's used by Chirp's Icom live mode driver
for programming is missing, and there are no commands to retrieve or set
memories. It would appear that the CI-V interface on the ID-5100A is
focused on control and not programming. Unless the command is implemented
but just omitted from the CI-V documentation, that means the ID-5100A would
need a clone mode driver, and not a variant of the IC-7100 driver.

Someone said they were working on a driver for the ID-5100A and had a
functioning prototype, but that was 7 years ago ...

https://chirp.danplanet.com/issues/1647

Martin.
KD6YAM


On Wed, Jul 27, 2022 at 9:03 AM Chuck Hast <kp4djt at gmail.com> wrote:

> I wonder how much different the format is on the ID 5100 from the 7100.
> Sure would like to have Chirp working on the 5100.
>
> I am still willing to loan the radio to someone who could work on the code
> for the 5100...
>
>
> On Wed, Jul 27, 2022 at 10:48 AM Martin Cooper <mfncooper at gmail.com>
> wrote:
>
>> Assuming it's the same as for the IC-910H, the CI-V Transceive function
>> is like a real-time updating facility, whereby when you tune the radio
>> manually, it continually sends CI-V data to the computer. You do not want
>> this enabled while running Chirp. FLRIG quite likely does want this
>> enabled, so this may be the setting that Jim was referring to.
>>
>> The Chirp driver for the IC-7100 is a live mode driver. As such, Chirp
>> uses the CI-V interface to talk to, and receive data from, the radio. I
>> don't know about the connectors on that radio, but make sure you're
>> connecting to the CI-V interface.
>>
>> Martin.
>> KD6YAM
>>
>> On Wed, Jul 27, 2022 at 3:03 AM Tony Ling <tonyg7txu at gmail.com> wrote:
>>
>>> CI-V Transceive OFF or ON Turns the CI-V Transceive function ON or OFF
>>> Clone Clone Mode Reads or writes the CS-7100 data to or from the PC,
>>> and/or receives data from a Master transceiver
>>>
>>> On Wed, 27 Jul 2022 at 10:55, Tony Ling <tonyg7txu at gmail.com> wrote:
>>>
>>>> Two COM port numbers are assigned to the [USB] connector. One of them
>>>> is “USB1,” used for cloning and CI-V operation. The other one is “USB2,”
>>>> whose function is selected in “USB2 Function” item of the “Connectors” Set
>>>> mode. (p. 6-8)
>>>>
>>>> On Wed, 27 Jul 2022 at 02:58, Jim Unroe <rock.unroe at gmail.com> wrote:
>>>>
>>>>> On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB
>>>>> <michael.nadler at gmail.com> wrote:
>>>>> >
>>>>> > ICOM 7100 connected to Linux system via the mini-USB port.  FLRIG
>>>>> can control the radio through that interface.
>>>>> >
>>>>> > Running CHIRP 0.3.0dev, when I try to download from the radio via
>>>>> /dev/ttyUSB0, I get a pop-up error message: unicode strings are not
>>>>> supported, please encode to bytes: <<gibberish characters>>>".
>>>>> >
>>>>> > Are there specific settings I need to have set on the ICOM?
>>>>> >
>>>>> > Is CHIRP able to interact with the ICOM-7100 via the mini-USB port?
>>>>> Do I have to use the RT-Systems FTDI cable into the audio port?
>>>>> >
>>>>> >
>>>>> > P.S. I also tried running Windows CHIRP daily-20220408.  Download
>>>>> from radio gets "error" in every entry.
>>>>> >
>>>>> >
>>>>> > --
>>>>> > Michael Nadler
>>>>> > KI7QIB
>>>>>
>>>>> I know that when I used CHIRP on my IC-7300, I used a different cable
>>>>> than I did when I used FLRIG. I also had to edit a setting in the
>>>>> radio for CHIRP and change it back for FLRIG.
>>>>>
>>>>> Jim KC9HI
>>>>> _______________________________________________
>>>>> chirp_users mailing list
>>>>> chirp_users at intrepid.danplanet.com
>>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>>> This message was sent to Tony Ling at tonyg7txu at gmail.com
>>>>> To unsubscribe, send an email to
>>>>> chirp_users-unsubscribe at intrepid.danplanet.com
>>>>> To report this email as off-topic, please email
>>>>> chirp_users-owner at intrepid.danplanet.com
>>>>> Searchable archive:
>>>>> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>>>>>
>>>> _______________________________________________
>>> chirp_users mailing list
>>> chirp_users at intrepid.danplanet.com
>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>> This message was sent to Martin Cooper at mfncooper at gmail.com
>>> To unsubscribe, send an email to
>>> chirp_users-unsubscribe at intrepid.danplanet.com
>>> To report this email as off-topic, please email
>>> chirp_users-owner at intrepid.danplanet.com
>>> Searchable archive:
>>> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>>
>> _______________________________________________
>> chirp_users mailing list
>> chirp_users at intrepid.danplanet.com
>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>> This message was sent to Chuck Hast at kp4djt at gmail.com
>> To unsubscribe, send an email to
>> chirp_users-unsubscribe at intrepid.danplanet.com
>> To report this email as off-topic, please email
>> chirp_users-owner at intrepid.danplanet.com
>> Searchable archive:
>> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
>
>
>
> --
>
> Chuck -- KP4DJT
> HamHotline # 11259
> _______________________________________________
> chirp_users mailing list
> chirp_users at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
> This message was sent to Martin Cooper at mfncooper at gmail.com
> To unsubscribe, send an email to
> chirp_users-unsubscribe at intrepid.danplanet.com
> To report this email as off-topic, please email
> chirp_users-owner at intrepid.danplanet.com
> Searchable archive:
> https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20220727/bdf9faf2/attachment.html