CHIRP

Same error on Mac OS

Failed to communicate with radio: Traceback (most recent call last):
File "/Users/wojtek/Downloads/chirp-0.4.0.app/Contents/Resources/chirp/chirp/ft90.py", line 323, in sync_in
self._mmap = self._clone_in()
File "/Users/wojtek/Downloads/chirp-0.4.0.app/Contents/Resources/chirp/chirp/ft90.py", line 265, in _clone_in
data += self._read(blocksize, blocknum)
File "/Users/wojtek/Downloads/chirp-0.4.0.app/Contents/Resources/chirp/chirp/ft90.py", line 249, in _read
(blocknum, blocksize+2, len(data)))
Exception: Unable to read blocknum 00 expected blocksize 4 got 0.

Gil Wojtek wrote:

Hi,

I have read about similar issue which was resolved however in my case I can't read from the radio nor upload. I tried chirp 4.0 and daily built. I get the error shown in attached file.

Hi,

Update:
I've got the same error with Chirp 0.4 + Prolific drivers 1.8.12 + Usb cable bought on Ebay.

Best regards.

For mac and pl2303 cables, I suggest trying the opensource pl2303 driver I packaged:

http://chirp.danplanet.com/projects/chirp/wiki/MacOS_Tips#-Generic-PL-2303-cables-counterfeit-andor-%E2%80%9CGeneric%E2%80%9D-If-you-arent-sure-what-kind-of-inexpensive-cable-you-have-try-this-one-first

I've got the same error with Chirp 0.4 + Prolific drivers 1.8.12 + Windows 7 or Windows Xp.

for prolific pl2303 and windows 7, you should be using the 3.2.0 version and nothing later will work with non-genuine pl2303.

see http://www.miklor.com/COM/UV_Drivers.php

3.4.xx tried unsuccessfully.
Downgrade to 3.2.0.
Problem still present.

I've tried a different cable. Instead of USB, I've tried a regular RS232 cable.

The result is the same:

Failed to communicate with radio: Traceback (most recent call last):
File "chirp\ft90.pyo", line 323, in sync_in
File "chirp\ft90.pyo", line 265, in _clone_in
File "chirp\ft90.pyo", line 249, in _read
Exception: Unable to read blocknum 00 expected blocksize 4 got 1.

I've made a hard reset to the radio and I've made a new try. The result is the same.

The problem should be in Chirp software... no?

What was the solution for the problem?
RC

Gil, Rui, have you been able to crack this problem?