|
Thanks in advance! New FT-857 owner, learning the radio, and was hoping to use CHIRP to do some programming of channels etc. but a get an error.
Using chirp-next.
I'm able to get the radio into "clone mode" and when I press send I get the error in the image below. I've tried various baud rates 4800, 38400, etc. and both the FT-857 ad FT-857 (US), no luck!
Any suggestions? Any way to debug? Thanks Again.
Slats - N2VYG
|
One thing I ran into was that there were a couple options for the FT-857 I have. I forget what they were, maybe Japanese, European and US. But I had picked the wrong one. I do know my radio is not Japanese but maybe it wanted to use the European version for the software? Anyway, once I had the correct one selected, it worked.
73, Zack W9SZ
Thanks in advance! New FT-857 owner, learning the radio, and was hoping to use CHIRP to do some programming of channels etc. but a get an error.
Using chirp-next.
I'm able to get the radio into "clone mode" and when I press send I get the error in the image below. I've tried various baud rates 4800, 38400, etc. and both the FT-857 ad FT-857 (US), no luck!
Any suggestions? Any way to debug? Thanks Again.
Slats - N2VYG
|
Thank you Zack, I tried all the variants that are listed in CHIRP which only have two. FT-857 and FT-857 US. No luck with either. 73 - Slats - N2VYG
|
What computer are you using. Windows 10 on some computers will not work with Chirp. There is a driver issue that was fixed in Windows 11. Don Dodge Cell 714-271-7888 W6SNX
On Nov 5, 2024, at 7:36 AM, michael.john.slattery via groups.io <michael.john.slattery@...> wrote:
Thank you Zack, I tried all the variants that are listed in CHIRP which only have two. FT-857 and FT-857 US. No luck with either. 73 - Slats - N2VYG
|
Interesting. I have been using Windows 7 with CHIRP for my rigs. It works fine.
73, Zack W9SZ
What computer are you using. Windows 10 on some computers will not work with Chirp. There is a driver issue that was fixed in Windows 11. Don Dodge Cell 714-271-7888 W6SNX Thank you Zack, I tried all the variants that are listed in CHIRP which only have two. FT-857 and FT-857 US. No luck with either. 73 - Slats - N2VYG
|
I've tried two computers, one Windows 10, other one is Windows 11.
|
I have usually found that Com ports and baud rate is what trips up Chirp, and most programming/communication software when using Windows. There is also an R-pi build that I have used with no problems on a pi-4. Selection of the correct radio type is also important.
You should be able to watch Device Manager ports list when plugging in a programming cable. An alert and a new com port number should pop up. If not, your programming cable chip drivers may not be installed or there is a driver problem. Not all programming cables are created equal either.
On Nov 5, 2024, at 8:32 AM, Zack Widup <w9sz.zack@...> wrote:
Interesting. I have been using Windows 7 with CHIRP for my rigs. It works fine.
73, Zack W9SZ
What computer are you using. Windows 10 on some computers will not work with Chirp. There is a driver issue that was fixed in Windows 11. Don Dodge Cell 714-271-7888 W6SNX Thank you Zack, I tried all the variants that are listed in CHIRP which only have two. FT-857 and FT-857 US. No luck with either. 73 - Slats - N2VYG
|
Yes, in both computers I do see the Com port correctly. Testing various baud rates and settings has not yielded better results.
73 N2VYG
|
Can you give more info on how you got CHIRP to run on a Raspberry Pi? I have a Pi 4 that I have been putting ham radio applications on.
Zack W9SZ
I have usually found that Com ports and baud rate is what trips up Chirp, and most programming/communication software when using Windows. There is also an R-pi build that I have used with no problems on a pi-4. Selection of the correct radio type is also important.
You should be able to watch Device Manager ports list when plugging in a programming cable. An alert and a new com port number should pop up. If not, your programming cable chip drivers may not be installed or there is a driver problem. Not all programming cables are created equal either.
de KM6WWY Interesting. I have been using Windows 7 with CHIRP for my rigs. It works fine.
73, Zack W9SZ
What computer are you using. Windows 10 on some computers will not work with Chirp. There is a driver issue that was fixed in Windows 11. Don Dodge Cell 714-271-7888 W6SNX Thank you Zack, I tried all the variants that are listed in CHIRP which only have two. FT-857 and FT-857 US. No luck with either. 73 - Slats - N2VYG
|
переключити цитоване повідомлення
Показати цитований текст
On Nov 5, 2024, at 10:00 AM, Zack Widup <w9sz.zack@...> wrote:
Can you give more info on how you got CHIRP to run on a Raspberry Pi? I have a Pi 4 that I have been putting ham radio applications on.
Zack W9SZ
I have usually found that Com ports and baud rate is what trips up Chirp, and most programming/communication software when using Windows. There is also an R-pi build that I have used with no problems on a pi-4. Selection of the correct radio type is also important.
You should be able to watch Device Manager ports list when plugging in a programming cable. An alert and a new com port number should pop up. If not, your programming cable chip drivers may not be installed or there is a driver problem. Not all programming cables are created equal either.
de KM6WWY Interesting. I have been using Windows 7 with CHIRP for my rigs. It works fine.
73, Zack W9SZ
What computer are you using. Windows 10 on some computers will not work with Chirp. There is a driver issue that was fixed in Windows 11. Don Dodge Cell 714-271-7888 W6SNX Thank you Zack, I tried all the variants that are listed in CHIRP which only have two. FT-857 and FT-857 US. No luck with either. 73 - Slats - N2VYG
|
I can read and look at individual photos much faster than watch a video on Youtube. I'd rather have info in printed form. And Youtube has an awful loot of false info on it.
Zack W9SZ
Zack,
YouTube is your friend: https://www.youtube.com/watch?v=FpeuE19torw
de KM6WWY Can you give more info on how you got CHIRP to run on a Raspberry Pi? I have a Pi 4 that I have been putting ham radio applications on.
Zack W9SZ
I have usually found that Com ports and baud rate is what trips up Chirp, and most programming/communication software when using Windows. There is also an R-pi build that I have used with no problems on a pi-4. Selection of the correct radio type is also important.
You should be able to watch Device Manager ports list when plugging in a programming cable. An alert and a new com port number should pop up. If not, your programming cable chip drivers may not be installed or there is a driver problem. Not all programming cables are created equal either.
de KM6WWY Interesting. I have been using Windows 7 with CHIRP for my rigs. It works fine.
73, Zack W9SZ
What computer are you using. Windows 10 on some computers will not work with Chirp. There is a driver issue that was fixed in Windows 11. Don Dodge Cell 714-271-7888 W6SNX Thank you Zack, I tried all the variants that are listed in CHIRP which only have two. FT-857 and FT-857 US. No luck with either. 73 - Slats - N2VYG
|
Just to close this one out, I had success with another cable.
this one. https://www.amazon.com/gp/product/B0854BDCNR/ref=ppx_yo_dt_b_asin_title_o00_s01?ie=UTF8&psc=1
|
Have you tried FDBasicMMO software by G4HFQ (silent key) ?? It's free and should work with the Ft-857
dwight
|
Jim