Thanks for the video. I'm having com problems with trying to get my vx5 to communicate with Chirp. I"m using windows pc and usb cable. Any tips or tricks? Thx.
I know the VX-5 is on the CHIRP list of supported radios. If Windows isn't recognizing your programming cable, then it could be a driver issue (you can look in the Windows Device Manager, and see if it is visible under the COM ports). Not sure what programming cable you're using, but if it's a driver, then you may want to try downloading a FTDI USB VCP Driver. Here is a link to Valley Enterprises where you can download the driver: www.valley-ent.com/store/yaesu-usb-ftdi-radio-programming-cable-ft-60-vx-1-vx-2-vx-5.html. I'm not sure if this will solve the issue or not? But, you can give it a shot while you're troubleshooting. If you get it working, then the first thing you will want to do is to download from your radio, and create a template that is compatible with your radio.
I don't have a dog in the Yaesu vs CHIRP fight. However, I addressed this topic in Episode 3, and I have heard this rumor before, and prior to doing Episode 3 I researched this subject. Allegedly there was a Yaesu rep who said it may be possible for CHIRP to brick a radio through somehow modifying the firmware. However, the developers at CHIRP have responded to this a couple of times stating their software does not modify the firmware. In Episode 3 I referenced a CHIRP support ticket #6671 (a link is in the description of that video) which also addressed this concern. In their response to the ticket, CHIRP stated they know of no circumstances where CHIRP has bricked a radio, and they know of no situation where anyone has approached their team with a bricked radio, and demonstrared a process by which their software caused a radio to become inoperable. From personal experience, I can say I have used CHIRP on all of my Yassu radios and have never encountered that situation. I guess in theory anything is possible when it comes to potential software issues / bugs. But, if no one to date has been able to produce a bricked radio and explained either (1) how it happened, or (2) was able to reproduce the issue, then I think its fair to assume that claim is invalid.
I use both CHIRP and RT Systems. Some of the differences are, CHIRP is free and covers a wide range of radios. With RT Systems the software is specific to a given radio, and you have to purchase it. I don't think you can go wrong with either, but RT Systems seems to have more features. RT Systems also has on screen instructions to guide you through the programming process. This is something the legacy version of CHIRP (CHIRP Daily) didn't have, but has included in their latest vsrsion of their software called CHIRP-Next. I tend to use RT Systems for my Yaesus because I think their software is more robust, but that isn't a knock on CHIRP. Both support MacOS, but you'll want to visit their websites to confirm they support your specific radio.
Thanks for the video. I'm having com problems with trying to get my vx5 to communicate with Chirp. I"m using windows pc and usb cable. Any tips or tricks? Thx.
I know the VX-5 is on the CHIRP list of supported radios. If Windows isn't recognizing your programming cable, then it could be a driver issue (you can look in the Windows Device Manager, and see if it is visible under the COM ports). Not sure what programming cable you're using, but if it's a driver, then you may want to try downloading a FTDI USB VCP Driver. Here is a link to Valley Enterprises where you can download the driver: www.valley-ent.com/store/yaesu-usb-ftdi-radio-programming-cable-ft-60-vx-1-vx-2-vx-5.html.
I'm not sure if this will solve the issue or not? But, you can give it a shot while you're troubleshooting. If you get it working, then the first thing you will want to do is to download from your radio, and create a template that is compatible with your radio.
@@PartisanCommsGroup awesome. I’ll try it out. Thanks so much!!
Nicely done.
Thank you.
YAESU says not to use Chirp with their radios or you risk bricking them and they wont support it.
I don't have a dog in the Yaesu vs CHIRP fight. However, I addressed this topic in Episode 3, and I have heard this rumor before, and prior to doing Episode 3 I researched this subject. Allegedly there was a Yaesu rep who said it may be possible for CHIRP to brick a radio through somehow modifying the firmware. However, the developers at CHIRP have responded to this a couple of times stating their software does not modify the firmware. In Episode 3 I referenced a CHIRP support ticket #6671 (a link is in the description of that video) which also addressed this concern. In their response to the ticket, CHIRP stated they know of no circumstances where CHIRP has bricked a radio, and they know of no situation where anyone has approached their team with a bricked radio, and demonstrared a process by which their software caused a radio to become inoperable. From personal experience, I can say I have used CHIRP on all of my Yassu radios and have never encountered that situation. I guess in theory anything is possible when it comes to potential software issues / bugs. But, if no one to date has been able to produce a bricked radio and explained either (1) how it happened, or (2) was able to reproduce the issue, then I think its fair to assume that claim is invalid.
@@PartisanCommsGroup Thanks for the reply. Is there an advantage to using chirp vs adms? Im on mac if that matters.
I use both CHIRP and RT Systems. Some of the differences are, CHIRP is free and covers a wide range of radios. With RT Systems the software is specific to a given radio, and you have to purchase it. I don't think you can go wrong with either, but RT Systems seems to have more features. RT Systems also has on screen instructions to guide you through the programming process. This is something the legacy version of CHIRP (CHIRP Daily) didn't have, but has included in their latest vsrsion of their software called CHIRP-Next. I tend to use RT Systems for my Yaesus because I think their software is more robust, but that isn't a knock on CHIRP. Both support MacOS, but you'll want to visit their websites to confirm they support your specific radio.
@@PartisanCommsGroup Thanks for the breakdown !
You're welcome.