CHIRP

Hi Chris,

There is a problem with the uploads for the BTECH 2501+220 due to a more stable IO procedures being implemented on the driver (the first release has a resource intensive routine that lead to certain instabilities), probably the btech.py version you get from BTECH is the beta we are testing internally to fix that, and of course it may contain bugs like the one you found now with the CTCSS.

Please wait, we are working on the issue now.

73 CO7WT

Sounds great, thank you. I have discovered a work-around that has had some success. I have found that if I start with a new csv in the latest CHIRP daily, I am able to either input the frequencies manually or copy and paste them from a previous csv and upload them to the radio by first unplugging and re inserting the cable into the computer just before uploading the file to the radio. If I do this, I don't get the "Radio did not respond to magic string, check cable." error. For some reason starting with the new csv from the latest daily does not input the odd characters into the CTCSS memory.

I also received a new BTECH UV 2501+220 yesterday including Btech program cable ...radio responds with ..."Radio did not respond to magic string check cable." error....also when try to download radio shuts off and restarts ...yet responds fine when trying the Btech2501(+220)_CPS program .

also get this message ....This driver is experimental.

I just received the Btech2501+220 a few days ago.

I have a similar problem except I can not download from the radio. I have version 20160402 of the software and the latest driver 2.12.16.0. I tried Btech's program and I can download from the radio just file. I have not tried to upload with either software. I have 3 frequencies set in the radio. Chan 0,1,199

I get the following error:
An Error has occurred. Radio identification failed.

Then the radio reboots.

Thanks,
Brent

Hi to all.

This is a bug of the BTECH 2501+220 and also affects the QYT KT8900, it's about a timeouts chaining under certain circumstances and the radio timeout.

I have it solved on the dev branch, a patch will follow soon.

73 and thanks for reporting.

With today's build (4/12/16) which appeared to have at least some BTECH 2501+220 fixes in it, I still get the error:
An error has occurred. Radio Identification failed.
followed by a radio reboot ....

Is it safe to just assume that this issue will get updated when Pavel's fix mentioned above goes in ?

73's and thanks for all the hard work ...

Or am I barking up the wrong tree and is issue #3015 closer on the Radio ID failing problems ?

Sorry if I tagged on to the wrong issue ....

new build gives me same error.... BTECH 2501+220 I still get the error:
An error has occurred. Radio Identification failed.
followed by a radio reboot ....

Ken, Augie, check your emails.

I have a request for help from your side about the problem.

73, Pavel.

It's exactly as Jim mentions.

Your radio has a different ID from what we have found so far (and the count keep growing), I dare to speculate by the numbers that it's a second generation of UV2501+220, maybe the Augie is hiting the same problem.

I will include it and send a new driver to test with this ID, and once confirmed it works as expected it will be included in Chirp.

Check your inbox 73.

Pavel ...

Driver you sent today works great ... was able to read/write multiple times to radio with no issues

Thanks for the good work !

73, Ken N4CEI

Good to know Ken and thanks to you for colaborate in the Chirp community.

Changes in the driver you have are not yet on the daily, and the starter of this issue (Chris Bates) haven't the oportunity to test it and comment about.

Let's wait for the changes being official and the Chris opinon to close this issue.

73

Hello,

I just tried the newest version (CHIRP daily-20160415) and I'm still getting "Radio Identification failed". So I'm still unable to read my radio via Chirp.

I am able to program my radio with the software from BTECH so I know my cable is working.

If there is any information you need from me, please let me know.

Thank you ALL for the work you do.

John - N1PCE

I tested this on a kt-8900 and it still did not work selecting QYT KT-8900. However I was able to upload and download to and from radio if i selected Sainsonic GT-890. The only issues I see with it are having to use the Sainsonic selection (not a big deal). Also, I had to copy and paste my channels one at a time (again, not a big deal). Third issue is that when in channel mode and scanning after a short time it switches itself to frequency mode and starts scanning there. That is an issue that I would think needs addressed. Maybe all three of these issues are because of selecting Sainsonic and not QYT… But still isn't working when selecting QYT

UPDATE I turned off priority scan and its been scanning correctly for over an hour. It has been receiving good. With priority scan on, it will stop scanning and switch to freq. mode and start scanning there..

I apologize if this is posted in the wrong place, only posting here because of the beta above

The py file worked and I was able to program the radio after having the Invalid Identifier error.

But I now have two peculiar problems. Not sure if they are related to programming or just the low quality of the radio.

https://youtu.be/U8RPHYYuyvo
https://youtu.be/_hGOwl9jvyg

The current release (CHIRP daily-20160419) works for me. I'm not seeing any issues at this time.

Thank you for the hard work that you all do.

John - N1PCE

I figured out one of my issues. I imported the listings from an IMG file for another radio. Turns out it defaulted to having the scramble on for all the stations I imported.

Now to figure out why the signal gets stronger whenever I hit any button.

Also confirm today's release works without the btech.py file whereas yesterday's did not. Thank you all that helped in making this happen!

The download/upload routines for this driver are still a work in progress. I have the same issue here. I just keep trying and usually after 3 or 4 tries it will go. Using Windows 7 running in a virtual machine it goes nearly 1st time every time.

Jim KC9HI

Carlos Marquez wrote:

I hope I'm putting this in the right place. UV2501+220; Chirp 20160419 worked perfectly in windows 10 but I got "invalid header error" using Ubuntu. See log attached. Thanks.

We have possibly found a solution, please take a peek here http://chirp.danplanet.com/issues/3993#note-12 and comment about your results.

73 Pavel CO7WT