Nothing happens. It doesn't even display the picture of the computer on the radio.
|
What happens when you use the chirp? BF-F8HP model, as advised on the "Supported Radios" page?
I just received my UV-5RH, and I am not able to read or write from the thing. I've tried with both the T6UV and CHIRP software, but it always fails. Not only that, but I even bought two more programming cables (never hurts to have spares, amirite?) and they don't help. When I try to read/write, the picture of the computer comes up on the radio screen, but no data is transferred. In T6UV, it just says "Failure". In CHIRP, using the 5RM model, the message is "Error reading data from radio: not the amount of data we want". Any tips before I send this back?
Firmware: 1.05
Hardware: V01
|
I just received my UV-5RH, and I am not able to read or write from the thing. I've tried with both the T6UV and CHIRP software, but it always fails. Not only that, but I even bought two more programming cables (never hurts to have spares, amirite?) and they don't help. When I try to read/write, the picture of the computer comes up on the radio screen, but no data is transferred. In T6UV, it just says "Failure". In CHIRP, using the 5RM model, the message is "Error reading data from radio: not the amount of data we want". Any tips before I send this back?
Firmware: 1.05
Hardware: V01
|
Thank you Bob, i will give that a try.
73
Brian
|
Brian,
In general, regarding the RF path, I believe the same (but never really looked at it in detail), in that if VHF is working, then UHF should be working. So it does sound unusual that UHF tx is not functional.
However, I have seen a similar situation on my own HT, where it looks like TX is working, but no RF is occurring.
Mine occurred when switching from Chirp to Chirp-Next to perform the programming. Whilst I cannot say for sure that it was the change in application, the main issue was "translation" of duplex, and the line from the Wiki was
"This sets the duplex mode of the channel. If set to (None)?then the transmit and receive frequencies are the same. If set to either +?or -?(plus or minus) then the
transmit frequency will be either above or below (respectively) the receive frequency by the value of the Offset?field.
If the duplex is set to split?then the Offset?field should contain the absolute transmit frequency to be used (if the radio supports this capability).
If the duplex is set to off?then transmission on this channel will be disabled (if the radio supports this capability).
Note that for simplex channels, this should be set to (None)?and repeater channels should have this set to either +,-,?or split."
On the older application it handled the Duplex being blank, where as on the new one it had to be set to "None" otherwise it would not transmit RF.
Now we are just talking Simplex here (as if normally setup for repeater you have a + or - entered).
This may not be your issue as it does sound like you have a handle on resetting/reprogramming, but the fix for mine was
-
Factory reset?
-
Using Chirp-Next - perform a read of the "blank" Baofeng (this is important for it to have as its starting point)
-
Now perform you programming and/or imports of frequency's / channels etc (don't just reload an old image)
-
Made sure the duplex is set correctly
-
Wrote back to the Radio
The export of a base blank image of the radio model you have is important. If the previous owner had already "corrupted" the image that was on the radio, and you created a new base off that, you may have continued the issue.
Anyhow this may be of no use to you, but passing on some experience with a similar issue. Needless to say, now working without any issues.
73's
Bob (VK1ED)
toggle quoted message
Show quoted text
A UV82 has come my way as part of a silent key estate.?
It transmits on 2m but not 70cm
I’ve checked the settings to ensure it hasn’t been restricted, tried resetting and reprogramming, still no tx on 70cm. Not even enough to detect on a receiver nearby. Nothing on the display to suggest it isn’t transmitting when the ptt is pressed.
My understanding, which could be false, is that these radios are largely ‘common’ path for their RF - ie only one PA, driver, etc.?
While a bad reactive component may be the cause, if that were the case ( at least if in the PA etc), I’d expected some RF, even if just enough to detect on a nearby Rx.
Has anyone seen this before or have any ideas, please?
73
Brian
G8OSN/W8OSN
|
A UV82 has come my way as part of a silent key estate.?
It transmits on 2m but not 70cm
I’ve checked the settings to ensure it hasn’t been restricted, tried resetting and reprogramming, still no tx on 70cm. Not even enough to detect on a receiver nearby. Nothing on the display to suggest it isn’t transmitting when the ptt is pressed.
My understanding, which could be false, is that these radios are largely ‘common’ path for their RF - ie only one PA, driver, etc.?
While a bad reactive component may be the cause, if that were the case ( at least if in the PA etc), I’d expected some RF, even if just enough to detect on a nearby Rx.
Has anyone seen this before or have any ideas, please?
73
Brian
G8OSN/W8OSN
|
Re: Programming software communication issue
This is what i get when i open the file up bud, i downloaded from the group incase the zip was corrupt, but all was fine,, weird one,, lol? 
|
Re: Programming software communication issue
Hi brian, I have no idea why you cannot open the files, I have downloaded them from the group and they open fine for me, see picture, the only other thing i can suggest is go to the radioddity site and download them from there, dont ask me why radioddity have them, lol, go here??then scroll to the bottom of the page, click the DM-1701 radio picture then download the software, inside that software download is also the USB driver, Let me know how you get on bud.?
|
Re: Programming software communication issue
Nothing opens up when I open these files ?
toggle quoted message
Show quoted text
From: colin GrocuttSent: Sunday, February 25, 2024 3:02 PM To: [email protected]Subject: Re: [Baofeng] Programming software communication issue ? Hi Brian, you have to download the file, but in case you cannot open .rar files here it is as a .zip file, windows should cope with that
|
Re: Programming software communication issue
Hi Brian, you have to download the file, but in case you cannot open .rar files here it is as a .zip file, windows should cope with that
|
Anyone know about using a UV5R as an echolink hotspot and specifically what cable are you using successfully with? the UV5R and PC.
I have ordered a K2 cable that is also used for APRS from Amazon after seeing an article on this subject online - but - this cable seems to have extremely narrow audio out when I transmit. It almost sounds like a landline phone going back and out through Echolink.?
Several years ago there was a simple cable setup available that seemed to work well and I was looking to trade notes with someone who has a working setup like this because the cable from amazon doesn't seem to cut it for transmitting back through echolink.
Appreciate any thoughts on this question.
|
Re: Programming software communication issue
Hi Brian, thats the one bud, the only other thing i can think of is that you have not installed the usb driver for the radio, find it attached,, i'm not sure which one you will need, so try both 64 versions "dpinst_amd64.exe" and "dpinst_ia64.exe", Try one and if you dont get it to work, then try the other, ignore the x86 version as this is for the 32 bit operating system
|
Re: Programming software communication issue
 I bought this one the other day and it doesn’t get recognized by computer etc. Is that the one u have shown below?
B
toggle quoted message
Show quoted text
On Feb 24, 2024, at 8:06?PM, colin Grocutt <colingrocutt@...> wrote:
?Don, you are using the wrong cable, the dm-1801 and dm-1701/ 1702 use a cable that does not have a prolific chip on it, the standard baofeng programming cable for the analogue type radios is not the one to use, this is the cable you need, (see picture <cable.png>
|
Re: Programming software communication issue
Thanks Don for tips. I will do
more work on this during the week. Let u all know findings.
Brian
toggle quoted message
Show quoted text
On Feb 24, 2024, at 7:10?PM, Donald Hellen <donhellen@...> wrote:
?Brian . . .
On Sat, 24 Feb 2024 17:34:59 -0500, "Brian Malone via groups.io"
<w2brm@...> wrote:
Update. Was able to load the 2007 driver that allows the prolific cable to be recognized without error to computer.
This evening, I was thinking of asking you what type of cable you were using.
You say it's Prolific, and that it's recognized. My first thought would be to
ask around in your local club and see if anyone has an FDTI cable, or even a
CH340 type I've used the CH340 cable with 8 "heads" to match with different
radios successfully. I had to search for the driver but it works.
I found out recently that there's also available a PL2303 cable for Windows
systems only (I think it does not require a driver) and a K-Plug cable (also
sold by Baofeng). So there's a plethora of cables out there for these radios to
choose from. When asked, I recommend an FDTI type cable unless the person wants
to be set up to program other brands of radios. In the latter case, I suggest
one of the CH340 cables that have a bunch of different connectors to mate with
multiple radio brands.
Back to your problem. For right now, let's assume your Prolific cable actually
does work and doesn't just report to the OS that it's working. Do you have the
volume control wide open when you're trying to read from or write to the radio?
The programming system uses part of the audio system, and if the volume control
isn't open enough, some have reported that it won't work until you open the
volume control enough for it to allow the signal to get through. Just give it a
try and see if that makes a difference. If it doesn't, try and get a cable from
someone in your local club or another ham you know has the same radio,
preferably NOT one that has a Prolific chip in it. But give this a try and see
if it then works (with the volume control wide open). Also, please let us know
if this changes things for you and it works. Some claim it makes no difference,
while some say it does. I'm inclined to think it does make a difference. I don't
have mine right now but I always have had the volume wide open.
Almost everyone who buys a Chinese HT finds it's not easy to program from the
front panel, so they buy the programming software from RT Systems with their
cable, or use CHIRP with a programming cable they buy somewhere. The cable from
the BTech store on Amazon works (I believe it's an FDTI cable). It's not just
Chinese radios, though. Some Japanese radios are difficult to program from the
front panel.
Donald KX8K
----------------------------------------------------
Some ham radio groups you may be interested in:
/g/ICOM /g/Ham-Antennas
/g/HamRadioHelp /g/Baofeng
/g/CHIRP
|
Re: Programming software communication issue
You are using the wrong cable, the baofeng DM-1701/1702/1801? all use a cable that is passive, there is no prolific chip or FDTI chip on the cable, the programming chip is built into the radio, you will need a programming cable that looks like this. Dont get the DR series radio confused as these do use a prolific/FTDI cable, EG: DR-1801 as you say, you have the DM-1801 so that will need the cable in the picture, just go on ebay and search for baofeng DM-1701 programming cable, you will find plenty on there, not sure if amazon will have them. 
|
Re: Programming software communication issue
Brian . . . On Sat, 24 Feb 2024 17:34:59 -0500, "Brian Malone via groups.io" <w2brm@...> wrote: Update. Was able to load the 2007 driver that allows the prolific cable to be recognized without error to computer. This evening, I was thinking of asking you what type of cable you were using. You say it's Prolific, and that it's recognized. My first thought would be to ask around in your local club and see if anyone has an FDTI cable, or even a CH340 type I've used the CH340 cable with 8 "heads" to match with different radios successfully. I had to search for the driver but it works. I found out recently that there's also available a PL2303 cable for Windows systems only (I think it does not require a driver) and a K-Plug cable (also sold by Baofeng). So there's a plethora of cables out there for these radios to choose from. When asked, I recommend an FDTI type cable unless the person wants to be set up to program other brands of radios. In the latter case, I suggest one of the CH340 cables that have a bunch of different connectors to mate with multiple radio brands. Back to your problem. For right now, let's assume your Prolific cable actually does work and doesn't just report to the OS that it's working. Do you have the volume control wide open when you're trying to read from or write to the radio? The programming system uses part of the audio system, and if the volume control isn't open enough, some have reported that it won't work until you open the volume control enough for it to allow the signal to get through. Just give it a try and see if that makes a difference. If it doesn't, try and get a cable from someone in your local club or another ham you know has the same radio, preferably NOT one that has a Prolific chip in it. But give this a try and see if it then works (with the volume control wide open). Also, please let us know if this changes things for you and it works. Some claim it makes no difference, while some say it does. I'm inclined to think it does make a difference. I don't have mine right now but I always have had the volume wide open. Almost everyone who buys a Chinese HT finds it's not easy to program from the front panel, so they buy the programming software from RT Systems with their cable, or use CHIRP with a programming cable they buy somewhere. The cable from the BTech store on Amazon works (I believe it's an FDTI cable). It's not just Chinese radios, though. Some Japanese radios are difficult to program from the front panel. Donald KX8K ---------------------------------------------------- Some ham radio groups you may be interested in: /g/ICOM /g/Ham-Antennas/g/HamRadioHelp /g/Baofeng/g/CHIRP
|
Re: Programming software communication issue
Update. Was able to load the 2007 driver that allows the prolific cable to be recognized without error to computer. However, when I go to read from radio, it looks like it’s ready to work and says ‘times out.
Could it now be a problem with radio?
Brian
toggle quoted message
Show quoted text
On Feb 24, 2024, at 1:22?PM, Donald Hellen <donhellen@...> wrote:
?I'm not sure where you do this in Windows, possibly in Device Manager, but if
you assign a high number for the COM port for the driver, Windows won't reassign
it. (Choose a number higher than 15.) That should make it stay put. :-)
Donald KX8K
On Sat, 24 Feb 2024 02:00:34 +0000, "Doug J" <vk2xlj@...> wrote:
Prog your radios on another PC that doesn't have Win10/11. As Win 10/11 will automatically update drivers, the previous editions don't.
----------------------------------------------------
Some ham radio groups you may be interested in:
/g/ICOM /g/Ham-Antennas
/g/HamRadioHelp /g/Baofeng
/g/CHIRP
|
Programming software communication issue
? Hi all. I purchased a baofeng dm 1801 a couple of years ago as a backup to my Anytone. I wanted to add some frequencies to it this week, which I haven’t done in a couple of years, and it won’t communicate with my windows PC. It used to work fine with the programming software. The only thing that has changed is my computer has had Window updates over the years and now running Windows 10. I saw some info about old divers or cables not working on newer Window versions? Any thought on fix? Brian W2BRM
|
Re: Programming software communication issue
I'm not sure where you do this in Windows, possibly in Device Manager, but if you assign a high number for the COM port for the driver, Windows won't reassign it. (Choose a number higher than 15.) That should make it stay put. :-) Donald KX8K On Sat, 24 Feb 2024 02:00:34 +0000, "Doug J" <vk2xlj@...> wrote: Prog your radios on another PC that doesn't have Win10/11. As Win 10/11 will automatically update drivers, the previous editions don't. ---------------------------------------------------- Some ham radio groups you may be interested in: /g/ICOM /g/Ham-Antennas/g/HamRadioHelp /g/Baofeng/g/CHIRP
|
Re: Programming software communication issue
Thanks all. I don’t know anyone that may have older window versions, so will install the driver Colin provided.? Where do I look for drivers to remove?? ?Is that also in remove and add programs?? Would appreciate steps.? I will keep u all posted on results.?
Brian
toggle quoted message
Show quoted text
On Feb 24, 2024, at 8:03?AM, VK1ED <bob@...> wrote:
?
Brian,
I concur with Doug's (VK2XLJ) statement with recent experience with the same issue.
Before Christmas, the workstation I used for programming was working fine. This workstation is Windows 10, but is generally only used for radio Ham related work / logging / etc, so nothing new had been installed (other than a major Windows update coming through)
In February, I ran into USB driver hell with both the Chirp Software and the DMR software, both not working correctly with the comm port. I was fortunate here with both apps not working, and using different methods/drivers of using the USB ports, it gave me
a clue that a Windows update had clobbered the driver. I believe it was the last major Windows 10 update (not one of the smaller patch Tuesday updates)
Main thing was to locate the remove the broken driver, various reboots and re-installing the original working driver(s) - once I did this software was working again, but it was several hours that I won't get back.
Now it is very possible these drivers may be poorly written, or they are not being kept up to date with Microsoft's security or framework requirements (remember many of these drivers hail from 2018 or earlier), so it may not just be Microsoft's fault, but this
sort of issue is pushing more and more people to setup Linux PC's for this sort of work.
Regards
Bob
(VK1ED)
Prog your radios on another PC that doesn't have Win10/11. As Win 10/11 will automatically update drivers, the previous editions don't.
Hi all. I purchased a baofeng a couple of years ago as a backup to my Anytone. I wanted to add some frequencies to it this week, which I haven’t done in a couple of years, and it won’t communicate with my windows PC. It used to
work fine with the programming software. The only thing that has changed is my computer has had Window updates over the years and now running Windows 10.
I saw some info about old divers or cables not working on newer Window versions? Any thought on fix?
Brian
W2BRM
|
VK1ED
W2BRM Brian
