Bug #5673

Unable to connect to WLN KD-C1 after Updating to daily-20180325

Added by Xavier Tan over 2 years ago. Updated 7 months ago.

Status:Closed Start date:03/28/2018
Priority:Normal Due date:
Assignee:Nicolas Pike % Done:

0%

Category:-
Target version:-
Chirp Version:daily Platform:MacOS
Model affected:WLN KD-C1

Description

Hello, I have been using Chirp daily-20170714 with no issue with the above radio, but when I updated to the daily-20180325 build, Chirp now returns an error message each time I try to connect to the radio, saying "The radio did not accept program mode after five tries. Check your interface cable and power cycle your radio."

Other than downloading and running Python and the latest build, there have been no other changes.

I am using a Valley Enterprises FTDI USB cable that was working with the radio through daily-20170714 just before I proceeded to update the Chirp build.

I also notice that now, with the update, when Chirp is open, it says "Python" instead of "Chirp" in the Menu bar.

Please let me know if you need more information.

Thanks!

Cheers,

Xavier

History

Updated by Jim Unroe over 2 years ago

  • Status changed from New to Feedback

If you revert back to the earlier version of CHIRP, does it work again?

Jim

Updated by Xavier Tan over 2 years ago

Hi Jim,

I have just tried to connect to my Yaesu VX-8R using daily-20170714 and it now reports an error connecting to the radio as well.

It looks like updating to the daily-20180325 has stopped my ability to connect to the radios that were working under the earlier version.

As I am not familiar with how to remove the latest version, I am now at a lost as how to get Chirp working again; both versions are installed on my macOS v10.13.3

Any assistance would be much appreciated.

Thanks!

Cheers,

Xavier

Updated by Dan Smith over 2 years ago

  • Assignee set to Nicolas Pike

Nicolas, I'm just assigning this to you so you'll see it. Maybe you could get some logs from Xavier and see if it looks related to the yaesu clone change?

Xavier, you don't need to install chirp on macos, so you absolutely can just use one build or the other at will -- there's no need to remove the old version. If the old version isn't working anymore either, I think I would look at drivers, cables, or other things that might be related other than just the new build.

Updated by Xavier Tan over 2 years ago

Hi Dan,

I specifically tested the connection with daily-20170714 before updating to daily-20180325 and they were working, but once I did the update, none of the previously working connections would work...not sure how to check for driver issues or even how to get the logs to show you - help?

Cables are all USB FTDI from Valley Enterprises.

Thanks!

Cheers,

"X"

Updated by Dan Smith over 2 years ago

  • Platform changed from Windows to MacOS

On MacOS the apps are independent. Having one on your system can't affect they other. They are sandboxed apart from each other by the operating system.

Here's how to get your debug log:

https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues

Open chirp, try to download from the radio, then close it and grab the debug log before you open chirp again. You might get it from each chirp version just to compare and post both.

Also, you might try rebooting (and un/re-plugging your USB adapter at the same time) in case your device or driver are stuck.

Updated by Nicolas Pike over 2 years ago

The WLN KD-C1 is a variant of Retevis RT22 as far as I can see it does not use any code from yaesu_clone
As Dan says need to see the debug log.
Python vs CHIRP in the Menu bar. When running CHIRP from homebrew I get the python window shell and hence python top left.

Updated by Xavier Tan over 2 years ago

Hi Nicolas,

I think I need to make some clarification here; I use the following radios with Chirp daily-20170714: Yaesu VX-8R and WLN KD-C1.

They were both accessible using their respective Valley Enterprises USB FTDI cables prior to the update to daily-20180325.

In an effort to check that the cables are working properly, I have used a Win10 Pro platform to run Chirp daily-20170714 and both radios are fully read/write accessible.

I then deleted the daily-20180325 from my Mac and tried the same two radios with the two FTDI cables and now they are both working again. As such, I am now unable to recreate the errors that were plaguing me before.

I am not sure what "homebrew" is but can confirm that when I was running daily-20180325, I did not get "CHIRP" in the menu bar, but "PYTHON".

I will reinstall daily-20180325 and retest both radios and update accordingly.

Updated by Xavier Tan over 2 years ago

I have downloaded and run daily-20180325 and tested both radios with the same FTDI cables.

Amazingly, they both now work! I am able to read from and write to both radios now.

Nothing has changed: no other adds/deletes or changes to the System, other than the previously mentioned removal of the first download of the daily-20180325.

The menu bar still shows "PYTHON", instead of "CHIRP" as per daily-20170714.

Is there any issue to keep running daily-20170714 instead of using the latest builds? Or should I only run the latest daily builds as they are published?

Updated by Nicolas Pike over 2 years ago

Hi Xavier,
Homebrew is a package and app manger for OSX [[https://brew.sh]] They have a CHIRP build, but I don't think they track daily builds.
Pleased it is now working. Can only think there was some USB driver issue.
Menu bar - May be dependent on how it is launched/packaged - hence my Homebrew comment. I would not worry.
Updates/daily builds - I would suggest - Install a recent build, check all your radios work with it. Then every few months or when you find something that does not work or you get a new radio, then update CHIRP.

Updated by Xavier Tan over 2 years ago

Hi Nicolas,

Thanks for the additional information. Good to know.

I will maintain daily-20180325 for regular use and keep daily-20170714 as a backup, since they are able to sit alongside each other without conflict, as per Dan's advice.

Thanks to you, Dan and Jim, for the assistance with my Chirp issues, and thanks to all for a really useful application to programme our various radios.

As a sidebar, just a question regarding adding other radios to the list, what is the likelihood of the various requests for new radios to be added, to be met? Just curious, so I can manage my expectations...!

Many thanks again!

Cheers,

Xavier

Updated by Nicolas Pike over 2 years ago

Xavier,

Regarding other radios. New and Radio variants are being added all the time. If there is a new Chinese radio it may well just be a variant on an existing one.
If there is a particular radio you have and would like supported just ask, and even if you cannot contribute code you can test and feedback - which is critical!

Thanks
Nicolas

Updated by Xavier Tan over 2 years ago

Hi Nicolas,

I have actually submitted a request: New Model #5671 for Vertex Standard VX-231 and Shanghai Motorola SMP 818.

Am currently using their respective programming software on a Win10 Pro platform, but would love to consolidate all the radio programming to Chirp on my Mac. Easier to manage the frequency/channel records in one place, for me at least.

Happy to help with testing and feedback; it helps us all...!

Thanks!

Cheers,

Xavier

Updated by Xavier Tan over 2 years ago

Hi Nicolas,

Here's an interesting one: I updated my macOS to 10.13.4 and moved the daily-20180325 from the Downloads folder to the Applications folder, and when I ran daily-20180325 to test, the "Python" in the menu bar has become "Chirp"...!

Everything works fine, both read/write, and I thought to share this...not that I can understand why this would be. :)

Thanks!

Cheers,

Xavier

Updated by Bernhard Hailer 7 months ago

  • Status changed from Feedback to Closed

Appears to be resolved.

Also available in: Atom PDF

prevent spam