CHIRP

I have a BTECH UV-2501 and would be willing to help.

Hi Jim and others.

I have he skill, the willingness, the hardware interface & the time, but not the radio.

:-(

73.

Just let me know what I need to test or play around with.
The file I uploaded contains the ident string to look for. The magic code seems to work.

The only thing that needs work is the timing of the data download.

----Script first run----
Good Ident it's a BTECH UV-2501, ident follows
000: 01 03 00 01 07 09 04 00   ........
008: 00 05 02 00 57 48 4b 4a   ....WHKJ
016: 31 36 38 4d 49 4e 4d 32   168MINM2
024: 39 32 30 34 55 38 38 30   9204U880
032: 30 30 30 30 30 30 30 30   00000000
040: 30 30 30 30 30 30 30 30   00000000
048: 55 00 00 00 00 00 00 00   U.......

 
Radio Found!!!, downloading image to uv2501.img
BAD ACK (0x58) for block: 0x0000
Traceback (most recent call last):
  File "uv2501.py", line 258, in 
    d = dump_mem(radio)
  File "uv2501.py", line 197, in dump_mem
    raise Exception, "Problem receiving block %s" % addr
Exception: Problem receiving block 0

----Script ran again----
Radio Found!!!, downloading image to uv2501.img
Correct ACK (0x05) for block: 0x0000
Header received:
000: 58 00 00 40 00 00 00 00   X..@....
----etc...----

I can get you remote access to a windows machine with logmein and a uv-2501 connected to the serial interface. The only issue that I see in this is that the radio likes to timeout, but I suspect that we can change a setting to adjust this.

@Jim Tuit:

If the fault you found in the 2501 about running the second not the first time is consistent then we can talk about a communication bug (or feature) and keep that into account in the code.

Than make me think, the \x58 is the char "X" the first on the header... humm...

Is the 2501 missing the ACK of the first packet?
Is the 2501 having another trick like the "\x05" on the first packet as the 5001.

Just the testing and playing will have the truth, wait for my emails to work it out and build a bare-bone driver.

Keep mapping the mem and +1 to the one radio at a time.

73

Brad S wrote:

I can get you remote access to a windows machine with logmein and a uv-2501 connected to the serial interface.
The only issue that I see in this is that the radio likes to timeout, but I suspect that we can change a setting to adjust this.

Brad, thanks for the offering, but unfortunately this is Cuba.

I have a 64Kbps link on my workplace shared with another 11 users; and at home (believe it or not) just a 9600 baud packet radio link on VHF and everything has to be done with much patience, like writing this post, for example.

So technically is impossible to me to user such solution, but thanks for the offering.

It's not much yet, but this is what I've got on the uv2501 radio memory so far.
Hopefully I've got the memory numbers and types right so far.

#mem-start 0x0000
--- Start Ch Freqs (16b/entry)
lbcd[4]         RX Freq
lbcd[4]         TX Freq
Unk[2]          unknown
Unk[2]          T-CTCS
Unk[2]          unknown
Unk[2]          unknown
--- End Ch Freq
#ENDseek 0x0c1f

#seekto 0x0e00
Unk [??]        0x0e00-0x0ebf - Unknown
--- Start Settings
Char[6] 0ec0    Power on MSG - Line 1
Char[6] 0ec6    Power on MSG - Line 2
--- End Settings
Unk [??]        0x0ecc-0x0fff - Unknown
#ENDseek 0x0fff

#seekto 0x1000
--- Start Ch Names (16b/entry)
Char[6]         Ch Name
    [10]        "FF FF FF FF FF FF FF FF FF FF"
--- End Ch Names
#ENDseek 0x1c20

#seekto 0x1c20 
--- Blank FF's to 0x1fff
#seekto 0x2000         
??? UNKNOWN
#ENDseek 0x23f0

#seekto 0x23f0         
--- Blank FF's to 0x2aef
#seekto 0x29f0         
Unk[8]          03 03 ff ff ff ff ff ff
#seekto 0x29f8         
--- Blank FF's to 0x2aef
#seekto 0x2af0 
Unk[8]          ??? Unknown
#seekto 0x2af8
--- Blank FF's
#ENDseek 0x2fff

#seekto 0x3000
--- FM Freqs - Start 3000
Unk [4] 0000    (8b)    FM 1 Freq (01 00 01 05 for 101.5Mhz)
Char[6] 0008    (10b)   FF FF FF FF FF FF
Char[6] 0020    (6b)    FM 1 Name
Char[4] 0026    (2b)    FF FF
--- End FM Freqs
#mem-end 0x3200

I just purchased a UV-5001 and would be willing to help out any way I can to get CHIRP working with it. I'm not up on code or anything but if I can be of help let me know.

I have a BTECH UV-5001 and would be willing to help
i have no programming skills but i have the radio and USB data cord

I have a 5001, and am a senior firmware engineer, so what can I do to help?
What is the easiest way to test the "beta"?

I also have a BTECH UV-5001. I'm also willing to help any way I can. I'm completely disappointed in the software it currently uses. CHIRP is an awesome resource and I greatly appreciate your work.

Hi, This night I was provided with a serial logs for the UV-2501+220 thanks to Jim Unroe.

So far so good, I found that the comm procedure is essentially the same but they make a double check to see if the radio at the end of the interface is really a 2501+220 and not a 5001 or a simple 2501.

That lead to review the drivers and serial logs to found that with the factory softwares for this radios read up to 0x3200 and in the write just to 0x3100, but our driver can reach beyond up to 0x4000 and in that "hidden" area reside the ID Codes for each radio model and the second id the 2501+220 ask for.

That will allow us to improve the aim in the detection of the specific models, and it's the solution for a problem we had already with the upload in the developing driver.

Just a note to keep you informed.

i have a btech uv-2501+220 if anyone would like it send me a message ill send it to you or send me the stuff and how to integrate it with my most up to date chirp and ill try it out and let you know

We are facing problems with the behavior of the driver in windows (timing issues), it's working ok on Linux & Mac. As windows is the most used OS we have to fix this before releasing the driver.

Just to keep you informed, 73.

Pavel Milanes wrote:

We are facing problems with the behavior of the driver in windows (timing issues), it's working ok on Linux & Mac. As windows is the most used OS we have to fix this before releasing the driver.

Just to keep you informed, 73.

I do have a windows machine if you want an outsider to test it.

I have a 2501+220 and use a CP2102 programming cable (if that matters). I have Windows 7 and a Mac (OSX 10.6.8), so I can do some testing or send some data if you would like some assistance.

I also have a 2501+220, but also have a QYT KT8900R which is an identical radio with slightly different firmware in that the 220 range is higher (for asian market rather than US). Note, that both radios are able to be programmed across the same range (221-270MHz) using software. When attempting to program them on the radio themselves, you are restricted to the local market ranges (but can still tune the entire range using channels programmed from software).

Would you be interested in data from the QYT KT8900R? (Also can do anything with the 2501+220 if you need).

Please wait for us, I have the idea for a way to dynamically determine the delay times in the windows version, I have to test it (when I get to home), this can also help on the problems with Kenwood radios.

This way we must manage uneven delay found on windows for every case, that (to me) is the root of the problem.

About other radios like the BTECHS, yes, +we will test that radios to give support in Chirp+, but always after the BTECH driver is stable enough.

The actual BTECHs (3 models to you and at least 5 model to us internally) is a mess to deal with all together, so we are addressing a radio at a time, that way we are getting out of the problem.

73.

how is it going with this radio i really need the software

Pavel and Jim, I sincerely appreciate the time and effort going into adapting CHIRP to the UV2501/5001 radios.
As always, if there is any way I can assist, please let me know.
John 'Miklor' - http://www.miklor.com

i just wanted to say thank you for all your hard work

Thanks to John, Kevin and all others that have supported us.

Today we managed to get reading consistency for all BTECH radios in the three major OS (Linux/Windows/Mac) and also the WACCOM Mini 9800plus. The new approach in the driver is paying the invested time.

We are working to have ready the upload procedure for all models, the release is close folks!

73

Thank you so much!
I noticed that the cps software for BTECH UV5001 is actually fully compatible with QYT KT-UV980.
73
Robin

Robin Pierre wrote:

Thank you so much!
I noticed that the cps software for BTECH UV5001 is actually fully compatible with QYT KT-UV980.
73
Robin

Yes we have found that at the chirp level, but also is a note about the bad programming practices of the OEM software authors, because both radios respond to the same magic code, but the radio ID are different, so they don't care much about validation in the software...

That is the bigger issue we have found, as we build in reverse engineering mode from the OEM software serial communications and they don't care to validate we have to put the validation (and timing) for our self and more than one time this have got us chasing our tails for a while...

Finally las night came into light the first pre-alpha release, the early test showed full download/upload with all all BTECH and the Waccom Mini8900plus...

So that was a big step forward the release.

73.

Nice work that you guys are doing. Thanks Pavel for the updates for the progress.
I enjoy the UV-2501 radio.

I admire CHIRP for its capability and function across all of the radios that I own. For me it is simple if I can use only CHIRP.

Best wishes to your progress and eventual success adopting the UV-2501 radio.

Thank you in advance,
Craig K.

We have the release candidate basic driver on the test bench now. Stay tuned. 73.

Thanks Dan and the gang for CHIRP! I've had loads of success across multiple platforms for years! You really do add value to the amateur products that we buy!

We are looking for some volunteers with BTECH radios for a closed test. Because these radios seem to be very picky with Widows, we want to get some "real data" to see if we need to make any additional tweaks before this driver is submitted for general use.

If you have one or more of the following BTECH radios (UV-5001, UV-2501 or UV-2501+220) and wish to volunteer, contact Pavel or myself at the following email addresses:

Jim rock.unroe@gmail.com
Pavel pavelmc@gmail.com

Include the following in your email:

• Radio models available
• Operating systems available (Windows, Linux, Mac and the version)
• Programming cable chip types available (Prolific, FTDI, etc)

Just to let everyone know the beta software works was able to download and upload to radio with no issues
Operating System: windows 10 pro x64 bit build 10586
Baofeng (BTECH) new programing cable
Driver: FTDI
thanks for all your hard work

kevin humphrey wrote:
Radio: BTECH UV-5001

Just to let everyone know the beta software works was able to download and upload to radio with no issues
Operating System: windows 10 pro x64 bit build 10586
Baofeng (BTECH) new programing cable
Driver: FTDI
thanks for all your hard work

BTECH UV-5001

I've just tested the beta for uv 5001. download, upload to radio just fine. Added channels via RadioRef and
Repeater Book. Works great so far.Thanks guys so much for your hard work. I think you nailed it.

windows 8 x64bit
Baofeng FTDI cable

I had a failure on OS X, debugging information sent to Pavel and Jim.
The radio gets a positive ident and then errors out.

Success on Windows 10, FTDI, Repeater Book import

Brad S wrote:

I had a failure on OS X, debugging information sent to Pavel and Jim.
The radio gets a positive ident and then errors out.

Success on Windows 10, FTDI, Repeater Book import

Yes brad, we are aware, it appears that the FTDI chips are slower to respond and need more room.

Jim has instructions to make some test with your help to fine tune the issue, wait for Jim emails.

So far so good, just about a few failures and all related with the driver being to fast, we have climbed from out internal default of 0.008 sec/char to about 0.020 sec/char now with Brad findings, or another trick that Jim will test with your help.

That's the real data we was looking for before release, thanks to all you that have volunteered to help up tune the driver.

73 CO7WT

I can confirm that the updated drivers worked for me on OS X - no timeouts.

The testing period is over. Some timing values were adjusted due to volunteer feedback. The driver will be submitted soon. Thank you all for you participation.

Jim KC9HI

Hi,
BTECH UV 2501 and 5001 are both supported by the new chirp version, but what about the QYT KT8900 and QYT KT-UV980?
Robin

Robin,
Those radios are being tracked under another issue (#2673). Doing this is a lot of work. We are not finished with this issue yet plus we do not have possession of the radios that you mention. When we are finished here we plan on moving over to the other radios.
Jim KC9HI

Robin Pierre wrote:

Hi,
BTECH UV 2501 and 5001 are both supported by the new chirp version, but what about the QYT KT8900 and QYT KT-UV980?
Robin

Your wish come true: http://chirp.danplanet.com/issues/2673#change-9629 the ball is on your park now.

73 CO7WT

Jim and Pavel, thank you for your work.

I succeeded to use Chirp with my UV-2501 on OS-X with the BTECH FTDI cable.

Best Wishes,
Craig K

Just purchased a new UV-2501. Using CHIRP I was able to read the data only a handful of times. Writing seemed to have no issue. Is there any data I can gather to help the cause?

Information about my setup which I failed to put in the last update.

UV-2501
Model: 168MIN
MCU-Version: BT.G2.1.4

FTDI based cable from Baofeng Tech US

Ubuntu Linux - Has trouble reading
Windows 7 - Seems to work fine

The 4/19 version is working fine with my BTECH-2501-220.

It would fail to identify on earlier versions but worked with my BTECH-5001.

Pavel,

If I recall, our initial submission was only accepted with an understanding that the download/upload routines would be reworked per Dan's recommendations/guidelines? Unless I missed it, I don't think this has been done yet. If it hasn't, then we need to leave this open for an issue to apply it to (unless you want to open a new issue just for that purpose).

Jim

Hi,
Just downloaded and uploaded to Gen 3 radio with new daily, worked perfectly! Seems to have kept all info.

I have no issues with the G3 UV-2501 or UV-5001 here when using Windows. Linux mostly fails. It is still a work in progress.

Jim KC9HI

apologies jim,
but i cant second that statment^

ive tried multiple times on my 64 bit windows 10 pro..

nada :(

mike

good news it does work^ im a fool apologies :?