General:
What radios does CHIRP currently support?
CHIRP currently supports the following radios:
- IC-91AD
- IC-92AD
- IC-2820H
- IC-V82
- IC-U82
- IC-2200H
- ID-800H.
- As from version 0.1.9 CHIRP also supports limited operation with the Icom ID-RP* D-STAR DV and DD repeaters.
What operating systems does CHIRP run on?
CHIRP currently operates on Linux and MS Windows. There are plans to support operation on MacOSX.
What formats can CHIRP read / write?
CHIRP supports:
its own native .chirp format (eg: radio.chirp);
CSV files. .csv files can have their memory contents manipulated with a text editor, or programs such as MS Excel, and then imported into a radio through CHIRP. To export a file in CSV format, simply add ".csv" as the file extenstion (eg: radio.csv); and
the ability to import .icf files. Currently, (as at version 0.1.9) CHIRP cannot import .icf files for the IC-9X series of radios as they use "rig control" rather than a "memory map" format of controlling the radio and its memories.
How do I change the font and font size in CHIRP (tested on MacOS only so far)?
This can be done by create a file in your home directory called .gtkrc-2.0 (note the "dot" in front of the "g" in gtkrc-2.0), and placing the following line:
- gtk-font-name = "Sans 18"
Of course you can pick a different font and font size than I have for my 1920x1200 display.
Serial Port Notes:
Can I use a COM port other than the ones listed?
Yes! Although the common ports are listed in the drop-down box, you can type in any port you like. For example, on Windows just choose COM1 and change the 1 to the number you need.
What baud rate should I choose?
If you're using a mobile radio, choose 9600. If you're using a handheld, choose 38400.
Troubleshooting:
CHIRP won't read the contents of my IC-91AD or IC-92AD.
1. Check to ensure that GPS TX Mode is set to DISABLED and that GPS AUTO TX is set to OFF.
2. Ensure that the radio is set to Band B and the mode is set to DV.
Reporting and dealing with BUGS!:
How do I file a bug?
To file a bug, go here:
Please be sure to follow the instructions provided on the page to open a new ticket.
What do I do if I think I've found a bug or a problem?
The best thing you can do is reproduce the issue and capture it in a debug log. Ideally, you should keep the debug log as concise as possible by starting CHIRP fresh, reproducing the problem, and immediately capturing the log. The general steps involved are:
- Figure out what actions cause the problem. Examples are: "Every time I try to read a radio's memories, the transfer fails" or "When I send upload new memories to my radio CHIRP crashes".
- Close CHIRP if it's running
- Start CHIRP fresh
- Reproduce the problem (do whatever it takes to manifest the bug)
File a bug with a detailed description of the problem and what you were doing at the time. Attach the debug log to the bug.
How do I get the debug log if CHIRP has crashed?
CHIRP cleans the debug log each time it starts, so restarting CHIRP to get the debug log will NOT work. After a crash, the debug log will be located in the following location, depending on your operating system:
Windows: %APPDATA%\CHIRP\debug.log
Linux/MacOS: ~/.d-rats/debug.log
On Windows, you can type the above string into the Start->Run box to bring up the file. Save it somewhere and send it to the CHIRP mailing list or file a bug and attach it.
CHIRP is crashing on startup
This is usually due to a breakage in the configuration file. File a bug and include your configuration file and a description of the last few things you were doing before you were unable to start CHIRP (if you can remember). The method for finding your configuration file varies by operating system:
Windows: %APPDATA%\CHIRP\d-rats.config
Linux/MacOS: ~/.d-rats/debug.log
On Windows, you can type the above string into the Start->Run box to bring up the file. Save it somewhere and attach it to the bug you're filing.