[chirp_users] Linux CHIRP, ICOM 7100, "unicode strings" error
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.
My initial thoughts on this, although I am by no means an expert, is that FLRIG is a rig control application, whereas CHIRP is a programming tool, unless used in 'live mode'. G7TXU
On Tue, 26 Jul 2022 at 21:03, Michael Nadler KI7QIB < michael.nadler@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 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
I understand about "live mode" programming". I also have a Kenwood D710G that programs that way. Whatever the case, one has to start by downloading the radio's current programming prior to editing it. Downloading isn't working, either with the Linux or the Windows version.
I see in the FAQ that ICOM 7100 is a supported radio (since 2017).
So, why am I getting the error?
Does CHIRP not work via the USB Port?
I've seen a number of YouTube videos where folks use RT Systems software to program the ICOM 7100 via the USB port.
I'd like to use CHIRP...
On Tue, Jul 26, 2022 at 1:34 PM Tony Ling tonyg7txu@gmail.com wrote:
My initial thoughts on this, although I am by no means an expert, is that FLRIG is a rig control application, whereas CHIRP is a programming tool, unless used in 'live mode'. G7TXU
On Tue, 26 Jul 2022 at 21:03, Michael Nadler KI7QIB < michael.nadler@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 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Michael Nadler at michael.nadler@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Hi Michael - plug the cable into the radio and computer, turn on the radio then in a terminal window on Linux type
dmesg
On Linux you may need to have root privileges.
At the bottom of the output you should see either a USB device - or possibly a serial device - and the port you need to use assuming you have the right cable.
-- Cinaed
On 7/26/22 16:45, Michael Nadler KI7QIB wrote:
I understand about "live mode" programming". I also have a Kenwood D710G that programs that way. Whatever the case, one has to start by downloading the radio's current programming prior to editing it. Downloading isn't working, either with the Linux or the Windows version.
I see in the FAQ that ICOM 7100 is a supported radio (since 2017).
So, why am I getting the error?
Does CHIRP not work via the USB Port?
I've seen a number of YouTube videos where folks use RT Systems software to program the ICOM 7100 via the USB port.
I'd like to use CHIRP...
On Tue, Jul 26, 2022 at 1:34 PM Tony Ling tonyg7txu@gmail.com wrote:
My initial thoughts on this, although I am by no means an expert, is that FLRIG is a rig control application, whereas CHIRP is a programming tool, unless used in 'live mode'. G7TXU On Tue, 26 Jul 2022 at 21:03, Michael Nadler KI7QIB <michael.nadler@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 _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Michael Nadler at michael.nadler@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to cinaed smson atcinaed.simson@gmail.com To unsubscribe, send an email tochirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please emailchirp_users-owner@intrepid.danplanet.com Searchable archive:https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
The 3.5mm (1/8") data jack is a straight serial port, and I'd give that a try.
Ken
On Jul 26, 2022, at 15:03, Michael Nadler KI7QIB michael.nadler@gmail.com wrote:
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?
On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB michael.nadler@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
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@gmail.com wrote:
On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB michael.nadler@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
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@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@gmail.com wrote:
On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB michael.nadler@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
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@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@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@gmail.com wrote:
On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB michael.nadler@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Martin Cooper at mfncooper@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
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@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@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@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@gmail.com wrote:
On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB michael.nadler@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Martin Cooper at mfncooper@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
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@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@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@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@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@gmail.com wrote:
On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB michael.nadler@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Martin Cooper at mfncooper@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Martin Cooper at mfncooper@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
Right now my 5100 is setting on a table, I am not using it at this moment but will be, if someone can use it to do the coding I am quite willing to ship it to them so they can get on it.
I was trying to remember the Icom program, it was not much, indeed I used it to write code plugs for the radio and load them on the memory card, then shove the card into the radio.
I do recall that the radio when it was connected to the application, looked more like remote control of the radio than actual programming, but you were able to download and upload the memories, but it was all faster just to fiddle the bits on the memory card.
On Wed, Jul 27, 2022 at 12:46 PM Martin Cooper mfncooper@gmail.com wrote:
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@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@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@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@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@gmail.com wrote:
On Tue, Jul 26, 2022 at 4:04 PM Michael Nadler KI7QIB michael.nadler@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Tony Ling at tonyg7txu@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Martin Cooper at mfncooper@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@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@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Martin Cooper at mfncooper@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com To report this email as off-topic, please email chirp_users-owner@intrepid.danplanet.com Searchable archive: https://www.mail-archive.com/chirp_users@intrepid.danplanet.com
participants (7)
-
Chuck Hast -
Cinaed Simson -
Jim Unroe -
Ken Hansen -
Martin Cooper -
Michael Nadler KI7QIB -
Tony Ling