Project

General

Profile

Actions

Bug #4273

closed

"Download from the radio" - FT7800

Added by Jakub Strzepa almost 8 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
12/01/2016
Due date:
% Done:

0%

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

Description

Hi, I'm executing following procedure:

  1. Turn radio off.
  2. Connect cable to DATA jack.
  3. Press and hold in the [MHz(PRI)] key while turning the radio on.
  4. Rotate the DIAL job to select "F-7 CLONE".
  5. Press and hold in the [BAND(SET)] key. The display will disappear for a moment, then the "CLONE" notation will appear.
  6. After clicking OK, press the [V/M(MW)] key to send image.

After step#6 application is reporting following error:
"ord() expected a character, but string of length 0 found"
and transceiver displays ERROR

Application is running on Windows 7 SP1
port is successfully detected as COM8


Files

debug.log (23.9 KB) debug.log Erik K, 05/08/2020 05:47 AM
Actions #1

Updated by Bernhard Hailer over 4 years ago

  • Tracker changed from Feature to Bug
  • Status changed from New to Feedback
  • Target version set to chirp-legacy
  • Chirp Version changed from 0.4.0 to daily
  • Model affected changed from (All models) to Yaesu FT-7800
  • Platform set to Windows

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 debug log. Thanks!

Actions #2

Updated by Erik K over 4 years ago

I get the same problem with FT7800. Ubuntu 19.10, chirp daily from today . Is there a PySerial problem?

Attaching debug.log

@
$ chirpw --version
CHIRP daily-20200430 on Linux - Ubuntu 19.10 (Python 2.7.17)
@

@
[2020-05-08 14:45:05,950] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,950] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,950] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,950] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,950] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,950] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,950] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,951] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,951] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,951] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,951] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,951] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,951] chirp.ui.mainapp - INFO: Skipping existing stock config
[2020-05-08 14:45:05,952] chirp.ui.reporting - DEBUG: Checking for updates
[2020-05-08 14:45:06,893] chirp.ui.reporting - DEBUG: Server reports version daily-20200430 is latest
[2020-05-08 14:45:21,843] chirp.ui.mainapp - DEBUG: User selected Yaesu FT-7800/7900 on port /dev/ttyUSB0
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/chirp/ui/mainapp.py", line 1641, in mh
self.do_download(*args)
File "/usr/lib/python2.7/dist-packages/chirp/ui/mainapp.py", line 733, in do_download
except serial.SerialException, e:
AttributeError: 'module' object has no attribute 'SerialException'
@

Actions #3

Updated by Bernhard Hailer over 4 years ago

I think these are actually two different problems.
The originally reported problem was under Windows, and I would suspect a cable, connector, or USB-to-Serial driver issue.
The problem in the post above under Linux is probably a port assignment issue: is that cable really on port /dev/ttyUSB0, and does the application have access to it?

Anyhow, perhaps one of the following documents might help:
CableGuide
CableGuide FTDI OEM Cables
[RTSystemsCablesAndMavericks]

Actions #4

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed

No more feedback by submitters.

Actions

Also available in: Atom PDF