<div dir="ltr">Right now my 5100 is setting on a table, I am not using<div>it at this moment but will be, if someone can use it to do</div><div>the coding I am quite willing to ship it to them so they</div><div>can get on it. </div><div><br></div><div>I was trying to remember the Icom program, it was not</div><div>much, indeed I used it to write code plugs for the radio</div><div>and load them on the memory card, then shove the card</div><div>into the radio. </div><div><br></div><div>I do recall that the radio when it was connected to the</div><div>application, looked more like remote control of the radio</div><div>than actual programming, but you were able to download</div><div>and upload the memories, but it was all faster just to fiddle</div><div>the bits on the memory card.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 27, 2022 at 12:46 PM Martin Cooper <<a href="mailto:mfncooper@gmail.com">mfncooper@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small">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.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Someone said they were working on a driver for the ID-5100A and had a functioning prototype, but that was 7 years ago ...</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small"><a href="https://chirp.danplanet.com/issues/1647" target="_blank">https://chirp.danplanet.com/issues/1647</a><br></div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">Martin.</div><div class="gmail_default" style="font-size:small">KD6YAM</div><div class="gmail_default" style="font-size:small"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 27, 2022 at 9:03 AM Chuck Hast <<a href="mailto:kp4djt@gmail.com" target="_blank">kp4djt@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I wonder how much different the format is on the ID 5100 from the 7100.<div>Sure would like to have Chirp working on the 5100. </div><div><br></div><div>I am still willing to loan the radio to someone who could work on the code</div><div>for the 5100... </div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 27, 2022 at 10:48 AM Martin Cooper <<a href="mailto:mfncooper@gmail.com" target="_blank">mfncooper@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-size:small">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.</div><div style="font-size:small"><br></div><div style="font-size:small">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.</div><div style="font-size:small"><br></div><div style="font-size:small">Martin.</div><div style="font-size:small">KD6YAM</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jul 27, 2022 at 3:03 AM Tony Ling <<a href="mailto:tonyg7txu@gmail.com" target="_blank">tonyg7txu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">CI-V Transceive OFF or ON Turns the CI-V Transceive function ON or OFF<br>Clone
Clone Mode Reads or writes the CS-7100 data to or from the
PC, and/or receives data from a Master transceiver<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 27 Jul 2022 at 10:55, Tony Ling <<a href="mailto:tonyg7txu@gmail.com" target="_blank">tonyg7txu@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">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)<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, 27 Jul 2022 at 02:58, Jim Unroe <<a href="mailto:rock.unroe@gmail.com" target="_blank">rock.unroe@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB<br>
<<a href="mailto:michael.nadler@gmail.com" target="_blank">michael.nadler@gmail.com</a>> wrote:<br>
><br>
> ICOM 7100 connected to Linux system via the mini-USB port. FLRIG can control the radio through that interface.<br>
><br>
> 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>>>".<br>
><br>
> Are there specific settings I need to have set on the ICOM?<br>
><br>
> 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?<br>
><br>
><br>
> P.S. I also tried running Windows CHIRP daily-20220408. Download from radio gets "error" in every entry.<br>
><br>
><br>
> --<br>
> Michael Nadler<br>
> KI7QIB<br>
<br>
I know that when I used CHIRP on my IC-7300, I used a different cable<br>
than I did when I used FLRIG. I also had to edit a setting in the<br>
radio for CHIRP and change it back for FLRIG.<br>
<br>
Jim KC9HI<br>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Tony Ling at <a href="mailto:tonyg7txu@gmail.com" target="_blank">tonyg7txu@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
To report this email as off-topic, please email <a href="mailto:chirp_users-owner@intrepid.danplanet.com" target="_blank">chirp_users-owner@intrepid.danplanet.com</a><br>
Searchable archive: <a href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a><br>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Martin Cooper at <a href="mailto:mfncooper@gmail.com" target="_blank">mfncooper@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
To report this email as off-topic, please email <a href="mailto:chirp_users-owner@intrepid.danplanet.com" target="_blank">chirp_users-owner@intrepid.danplanet.com</a><br>
Searchable archive: <a href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></blockquote></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Chuck Hast at <a href="mailto:kp4djt@gmail.com" target="_blank">kp4djt@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
To report this email as off-topic, please email <a href="mailto:chirp_users-owner@intrepid.danplanet.com" target="_blank">chirp_users-owner@intrepid.danplanet.com</a><br>
Searchable archive: <a href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><br></div><div dir="ltr">Chuck -- KP4DJT</div><div>HamHotline # 11259</div></div></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Martin Cooper at <a href="mailto:mfncooper@gmail.com" target="_blank">mfncooper@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
To report this email as off-topic, please email <a href="mailto:chirp_users-owner@intrepid.danplanet.com" target="_blank">chirp_users-owner@intrepid.danplanet.com</a><br>
Searchable archive: <a href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></blockquote></div></div>
_______________________________________________<br>
chirp_users mailing list<br>
<a href="mailto:chirp_users@intrepid.danplanet.com" target="_blank">chirp_users@intrepid.danplanet.com</a><br>
<a href="http://intrepid.danplanet.com/mailman/listinfo/chirp_users" rel="noreferrer" target="_blank">http://intrepid.danplanet.com/mailman/listinfo/chirp_users</a><br>
This message was sent to Chuck Hast at <a href="mailto:kp4djt@gmail.com" target="_blank">kp4djt@gmail.com</a><br>
To unsubscribe, send an email to <a href="mailto:chirp_users-unsubscribe@intrepid.danplanet.com" target="_blank">chirp_users-unsubscribe@intrepid.danplanet.com</a><br>
To report this email as off-topic, please email <a href="mailto:chirp_users-owner@intrepid.danplanet.com" target="_blank">chirp_users-owner@intrepid.danplanet.com</a><br>
Searchable archive: <a href="https://www.mail-archive.com/chirp_users@intrepid.danplanet.com" rel="noreferrer" target="_blank">https://www.mail-archive.com/chirp_users@intrepid.danplanet.com</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><br></div><div dir="ltr">Chuck -- KP4DJT</div><div>HamHotline # 11259</div></div></div>