I might of missed this in the video, but did you use the supplied short head unit cable? I haven't seen or really taken a look, but I'm assuming the head unit attaches to the main body and it comes with a cable for that attachment?
It does not come with a separation cable, Just the sort cable from the factory (3-4 inches), I started out using the cable that I was using for the FTM-300 (flat cat-5 cable, which worked well for the FTM-300) So I ordered the Yaesu FTM-500 extension cable from Gigaparts and I used it also in this video and it made no difference.
Yaesu knows about this and has a firmware fix, not released yet.
ruclips.net/video/0wy1gr176nU/видео.html
No matter which connection cable is used, short or long, this Problem is inside Radio.
I might of missed this in the video, but did you use the supplied short head unit cable? I haven't seen or really taken a look, but I'm assuming the head unit attaches to the main body and it comes with a cable for that attachment?
It does not come with a separation cable, Just the sort cable from the factory (3-4 inches), I started out using the cable that I was using for the FTM-300 (flat cat-5 cable, which worked well for the FTM-300) So I ordered the Yaesu FTM-500 extension cable from Gigaparts and I used it also in this video and it made no difference.
@@HamRadioCrusader That's what I mean, you have tried it with that short 3-4 inch separation cable with the same results?
@@AA0Z I have not, Thank You for the idea. It needs to be done,
Is anybody else with a 500 having the same issue?
Jason Johnston over at Ham Radio 2.0 was also having a similar issue and another RUclipsr that I referenced in the Part 2 Description.
@@HamRadioCrusader I will not watch his stuff anymore.
Same issue with my FTM-500.