Bug #763: Radio -> Download From Radio Does Nothing - CHIRP

Actions

Copy link

Bug #763

closed

Radio -> Download From Radio Does Nothing

Added by Sean Begley over 11 years ago. Updated over 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Dan Smith

Category:

Target version:

0.4.0

Start date:

04/06/2013

Due date:

% Done:

Estimated time:

Chirp Version:

daily

Model affected:

(All models)

Platform:

Windows

Debug Log:

I read the instructions above:

Description

Hello,

I'm running the latest daily build (daily-20130405) on a 64-bit Windows 7 laptop. I caveat my error submission with this: This is my 1st time using the CHIRP software.

When I click Radio -> Download From Radio (or Alt-D) nothing happens. No pop-up window, no error, no crash, no nothing. I installed CHIRP daily-20130405 on a 2nd laptop (also running 64-bit Windows 7) and the Radio -> Download From Radio option brought up a pop-up window as expected.

There is a callback stack at the end of the attached debug.log. I'm not familiar with your code but it looks like the software is erroring whilst trying to get the list of COM ports.

Thanks,
Sean, K4SMB

Files

debug.log (4.02 KB) debug.log

CHIRP debug log file 2013-04-06

Sean Begley, 04/06/2013 08:39 AM

Actions

Copy link

Updated by Jim Unroe over 11 years ago

Sean,
I believe I read where there is some work being done com port enumeration and it may not be working on windows.

Drop back to v20130404 to see if that works for you.

Jim KC9HI

Actions

Copy link

Updated by Sean Begley over 11 years ago

Thanks for the quick reply. I reverted the Thursday's build as suggested and was unsuccessful: same results. I also tried out the 0.3.0 stable build with the same results.

As I mentioned I am on 64-bit Win7 Laptop where I'm getting the failures. I tried it on another 64-bit Win7 laptop and was successful so the issue, unfortunately, appears to be a bit more nuanced than just "it doesn't work in Windows", "it doesn't work in Windows 7", or "it doesn't work in 64-bit Windows 7."

Sean, K4SMB

Actions

Copy link

Updated by Dan Smith over 11 years ago

Status changed from New to Feedback
Assignee set to Dan Smith
Target version set to 0.4.0

Sean, it looks like this is a bug in pyserial, but in some error path. Not sure what the failure is, but chirp can (and should) fall back to the older method of detecting ports if any such failure occurs.

Just to confirm, on the system where this happens, do you have at least one serial port showing up in device manager?

Actions

Copy link