Project

General

Profile

Actions

Bug #3869

open

Yaesu Ft-7900 Failed to download data

Added by David Pello over 8 years ago. Updated over 4 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
-
Target version:
-
Start date:
07/30/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
Yaesu FT-7900
Platform:
Linux
Debug Log:
I read the instructions above:

Description

When I try to download data from the radio, following all the steps, just after pressing V/M to start transmitting, the download fails with the following error:

ERROR: -- Exception: --
ERROR: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/chirp/ui/clone.py", line 249, in run
    self.__radio.sync_in()
  File "/usr/lib/python2.7/site-packages/chirp/drivers/ft7800.py", line 327, in sync_in
    self.check_checksums()
  File "/usr/lib/python2.7/site-packages/chirp/drivers/yaesu_clone.py", line 229, in check_checksums
    if checksum.get_existing(self._mmap) != \
  File "/usr/lib/python2.7/site-packages/chirp/drivers/yaesu_clone.py", line 175, in get_existing
    return ord(mmap[self._address])
TypeError: ord() expected a character, but string of length 0 found

ERROR: ----------------
ERROR: Clonado fallido: ord() expected a character, but string of length 0 found
ERROR: --- Exception Dialog: ord() expected a character, but string of length 0 found ---
ERROR: None

ERROR: ----------------------------

The cable works as I downloaded the data a moment ago using the FTB7900 program under wine.

System is Arch Linux using Python 2.7.12

Actions #1

Updated by Jakub Strzepa almost 8 years ago

Experienced same issue, also as described in SR#4273, difference is FTB7900 is not working as well and replies error message:

"The rig identifier expected was x'414830313624' but identifier received was X'E8A4BEEBFB2' We cannot continue wtih the read process".

Can we expect any update from Support side? Please let us know if we should reach for another solution supplier?
Best regards
Kuba

Actions #2

Updated by Bernhard Hailer over 4 years ago

Have you been able to resolve this on your own since you submitted this?
Have you tried with a recent version since you submitted this?
If you haven't, and if you're still having this issue, please refer to the Wiki "How To Report Issues" and provide a full debug log. Thanks!

Please understand that we're not a company with support department. Chirp is entirely maintained by volunteers.

Actions

Also available in: Atom PDF