Bug #5023
closedIcom IC-7100 writes wrong repeater offset
100%
Description
It looks like Chirp is writing repeater frequencies for UHF with a 0.6 Mhz offset. Two meter repeaters are OK, but all the UHF repeaters also get a .6 mhz offset.
To test the software, I entered a UHF repeater manually in the radio with a valid 5 Mhz offset. I verified the offset on the manually entered memory was 5 mhz. I downloaded the data from the radio, edited the entry to only add a channel name, and Chirp changed the repeater offset to .6 Mhz offset.
I exported a generic .CSV file, pasted my frequencies and channel names and entered the offsets as 5 for UHF and .6 for VHF repeaters. Once imported all the repeater offsets were .6 mhz.
Files
| Set20171202_01.icf (285 KB) Set20171202_01.icf | ICF | ||
| Screen Shot 2017-12-02 at 3.13.41 PM.png (294 KB) Screen Shot 2017-12-02 at 3.13.41 PM.png | 440.000 picture | ||
| Screen Shot 2017-12-02 at 3.13.49 PM.png (243 KB) Screen Shot 2017-12-02 at 3.13.49 PM.png | 442.700 picture | ||
| ic-7100.csv (918 Bytes) ic-7100.csv | CSV | ||
| imported-radio-ref.csv (7.26 KB) imported-radio-ref.csv |
Updated by Bob Cheek about 7 years ago
I guess no one has looked at this problem.
Looks like if I want to program my IC-7100 I need to find another software package.
Updated by kevin N3LGA almost 7 years ago
- File Set20171202_01.icf Set20171202_01.icf added
- File Screen Shot 2017-12-02 at 3.13.41 PM.png Screen Shot 2017-12-02 at 3.13.41 PM.png added
- File Screen Shot 2017-12-02 at 3.13.49 PM.png Screen Shot 2017-12-02 at 3.13.49 PM.png added
I've been able to recreate this issue and per a side conversation on reddit I'm attaching some example files.
Memory location information:
Manually entered:
A05 (slot 6?) 145.230 -600khz offset
A06 (slot 6?) 442.900 +5mhz offset
CHIRP entered:
C04 (slot 200? 204?) - 440.000 -5mhz offset (based on chirp screen) -- Actual Freq programmed in live mode: 440.600
If you need more detail let me know
A06 (slot 6?) 442.900 +5mhz offset
Updated by kevin N3LGA almost 7 years ago
- File ic-7100.csv ic-7100.csv added
While I was doing the updates, I also saved a CSV file and noticed that the CSV also sets -ALL- offsets to .600 khz (look at the HF freqs as well, etc)
This also should help with memory locations for the last ICF :)
Updated by kevin N3LGA almost 7 years ago
kevin N3LGA wrote:
While I was doing the updates, I also saved a CSV file and noticed that the CSV also sets -ALL- offsets to .600 khz (look at the HF freqs as well, etc)
This also should help with memory locations for the last ICF :)
Chrip Daily Build 2017-11-26 Mac OS X High Sierra
Updated by kevin N3LGA almost 7 years ago
- File imported-radio-ref.csv imported-radio-ref.csv added
Full CSV dump with the imported items via chirp for memory location settings for the ICF attached.
Updated by Tom Hayward almost 7 years ago
- Status changed from New to Blocked
Developer will need hands on a radio to fix this, since it's a live mode driver.
Updated by Bob Cheek almost 7 years ago
Do you need me to test something for you? Give me the info and I will help.
Updated by James Trt almost 7 years ago
Also a problem for me. I'm glad I am not the only one. I programmed my IC7100 with the +5.0 offsets. Then did a Download from Radio. Chirp reset all of the memories back to +0.6 offset. I guess because it is a Live download. Lost an hour's work. Makes Chirp not usable for this application.
Updated by Archie Brentano over 6 years ago
Another IC7100 with the same problem.
Updated by Martin Cooper over 4 years ago
I don't have an IC-7100 to check, but looking at the code, it seems that the memory layout spec is incorrect, which may be at least part of the problem. If someone could run the following for a memory that has a non-default offset, and then paste the result here, that might be helpful.
$ chirpc -r Icom_IC-7100 -s (your serial port) -raw (your memory number)
Updated by Bob Cheek over 4 years ago
That won't run on a windows machine. Got another suggestion? (chripw.exe)
Updated by kevin N3LGA over 4 years ago
I’ll try on a Mac here over the weekend if I can
Updated by Martin Cooper over 4 years ago
Under the Help menu, you should see "Enable Developer Functions". Once you do that, you'll find a Developer submenu under the View menu and also on the right-click context menu on a memory in the list. On the Developer menu, you'll see "Show Raw Memory". That's what I'm looking for. Select a memory with a non-default offset, and then select "Show Raw Memory". It'd also be helpful to know whether or not the correct offset shows up when you select Properties for that memory. Thanks.
Updated by Anonymous over 4 years ago
- Status changed from Blocked to Closed
- % Done changed from 0 to 100
Applied in changeset commit:7e13a0456850.