CHIRP

Can you try the latest daily version to see if that works? I see something in your log that looks wrong, so we'll need to get 0.2.2 fixed for sure, but if you could check the latest daily build for MacOS, that would help:

http://trac.chirp.danplanet.com/chirp_daily

Thanks!

The daily build app did not crash on start-up now, but comes up with a blank screen (see WindowImage.jpg). The console.log shows the following messages:

4/18/12 9:20:28 AM [0x0-0x92092].com.danplanet.chirp[1428] ** (chirpw:1428): WARNING **: Invalid borders specified for theme pixmap:
4/18/12 9:20:28 AM [0x0-0x92092].com.danplanet.chirp[1428] /opt/kk7ds/share/themes/OSX-theme/gtk-2.0/Buttons/button-default.png,
4/18/12 9:20:28 AM [0x0-0x92092].com.danplanet.chirp[1428] borders don't fit within the image

I have included the debug.log from the run. Hope that helps.

Your screenshot looks like it's fine to me. Try going to File->New, or Radio->Download to get started.

I'll mark this as a bug in the 0.2.2 Mac package.

Thanks!

Did as you said (File/New followed by File/Import). The import was a CSV file that was exported by ADMS-2I (the RT Systems/Yeasu app for Windows to manage the FT-8800). CHIRP produced a No Channels Found error (see NoChannelsFound.jpg). I have included a scaled down version of the exported file (see ADMS-2I-Export) and the debug.log.

Regards

I was able to download FT-8800 data using the RT Systems CT29B Radio Cable. I received 2 tabs of data. I assume one is the Right Transceiver and one is the Left transceiver (looking at Columns did indicate which was which). In addition, the transceiver can transmit and receive on different frequencies, but only one frequency is shown. The offset seems to indicate the transmit frequencies or offset. It is not clear to me how an Rx/Tx with an offset is handled. However, at least two channels have receive and transmit frequencies (159.225, 153.785 and 151.625, 151.625), but they seem to show an in valid frequency (8153.780000) rather than the actual transmit frequency. Both are labeled as split Duplex, but there are a couple of others that seem to show split and correct transmit frequency.

Apparently Chirp does not capture the Banks or the Skip HM data memory information. Is that information thrown on the floor?

I have provided the debug.log file for your review.

I'm changing the name of this bug again, because (a) I've checked and the 0.2.2 MacOS package seems to be fine to me and (b) you have unrelated issues. In the future, please create a new issue for each actual issue.

CHIRP supports split TX/RX memories by indicating a duplex of "split" and showing the TX frequency in the offset field. It sounds like that's what you're seeing. Most amateur radios (the FT-8800 included) default to a single frequency with a duplex and offset, which is how CHIRP natively shows it. Normally you would have a frequency of something like 146.900, a duplex of "-" and an offset of 0.600MHz.

Please attach your .img file with the broken frequencies in it and I'll take a look.

CHIRP does not support the hyper memory functions of these radios. The information is not "dropped on the floor", it's just ignored. Editing your memory image with CHIRP will not erase this data, and it will still be present when you upload back to the radio.

Please direct any future discussion on how to use CHIRP to the mailing list.

Thanks!

Not sure, do you want me to start a new problem report for this information or should I put the IMG file here. I am assuming you want it here. Sorry, I did not create separate problem report for each issue. I assumed that one led to the other, but I guess they didn't really go one after the next.

0.2.2 may work on your machine, but it still will not start on mine - same problem as initially stated with the same console.log entries. Your call.

The IMG file is attached. Channels 19 and 98 have the problem.

Got it, thanks for the image. This is fixed for tomorrow's daily build.

Regarding the 0.2.2 package, I've tested it on a couple machines without any trouble, but am also hoping to get some confirmation from a more MacOS-y person than myself. I'll follow up on it and open a new issue if we find something wrong.

Thanks!