Project

General

Profile

Actions

Bug #2939

closed

Can't import into Chirp .img file

Added by Don Dorward about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/23/2015
Due date:
% Done:

0%

Estimated time:
Chirp Version:
0.4.0
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Using latest Chirp to download and upload to the VV-898, no problem.
However, when trying to import either another .img file or a .csv file I get an error message.
Message says error on import and 63. not in valid list.
See attached photo.


Files

screenshot_3.jpg (116 KB) screenshot_3.jpg Don Dorward, 10/24/2015 07:45 AM
screenshot_4.jpg (493 KB) screenshot_4.jpg Don Dorward, 10/24/2015 07:45 AM
vv8982015_10_23.img (8 KB) vv8982015_10_23.img Don Dorward, 10/24/2015 07:45 AM
UV82_18Nov2014.img (6.32 KB) UV82_18Nov2014.img Don Dorward, 10/24/2015 07:45 AM
UV82_18Nov2014.csv (6.11 KB) UV82_18Nov2014.csv Don Dorward, 10/24/2015 07:45 AM
Actions #1

Updated by Jim Unroe about 9 years ago

  • Status changed from New to Feedback

Don,

There are no attached photos.

Why not attach the .img and .csv files that you are trying to import along with the "master" .img file so we can try to replicate the problem?

Also, what is the CHIRP version you are using and which computer operating system.

Jim KC9HI

Updated by Don Dorward about 9 years ago

Error message screenshots are attached.
The master .img file is the VV8982015_10_23.img downloaded from the radio.
The .img file I was trying to import was UV82_18Nov2014.img
Similarly the .csv file was UV82_18Nov2014.csv

The chirp version I was using was chirp-daily-20151023-installer.

I tried using separate computers, first one with Win10, then an older one with XP, with the same resuilts.

73
va3ddn
Don

Actions #3

Updated by Don Dorward about 9 years ago

Correction, ignore screenshot_3 sent in error.
chirp_error.jpg is correct.

Actions #4

Updated by Jim Unroe about 9 years ago

Don,

The picture pretty much tells the story. You have channels with non-standard tones programmed into them.

The image that you have provided contains the factory channels. Channel 4 and channel 13 has a non-standard 63.0 Hz CTCSS tone. You probably shouldn't be using these channels. I would get rid of them and put legitimate frequencies. Then you problem will be solved.

Jim KC9HI

Actions #5

Updated by Don Dorward about 9 years ago

Hi Jim
I think I am missing something along the line. Where do you see the the 63.0 Hz in that picture?
(I didn't program these channels - thats how the radio was received.)
I was assuming I would just over -write them all with my imported data from previously used files.

Also I see now location 5 and 14 on the picture have the tone mode as DTCS.
Are these what you are calling ch 4 and 13?

I probably should clear all of them and start fresh.
Don va3ddn

Actions #6

Updated by Jim Unroe about 9 years ago

See where it says "'63.0' not in valid list:" and then proceeds to list the valid values?

Also look closely at LOC 4 and LOC 14. They both have "ERROR" in the Name column. These are the "bad" channels with the 63.0 Hz tone.

Just click on LOC 4 and hit the [Delete] key. Then do the same on LOC 13. Then you will will have removed the incompatible channels. Save that off as a different name and use it as your "working" file.

Jim KC9HI

Actions #7

Updated by Don Dorward about 9 years ago

Thanks Jim
I deleted all the OEM frequency listings originally downloaded from the radio.
I have now been able to import my frequency listings from other files without any problem.
Case closed I think.
Perhaps an idea to warn other users about this issue.
73
Don
va3ddn

Actions #8

Updated by Jim Unroe about 9 years ago

  • Status changed from Feedback to Resolved
Actions #9

Updated by Jim Unroe about 9 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF