[chirp_users] New member with a couple questions
Hi, My name is Glenn, I live in Nebraska. I have a UV-5R, and my son has a BF 8HP by Baofeng. I should mention that I am using Chirp on computers with a screenreader for the visually impaired. One computer is running Windows 7, and the other is running Ubuntu 16.04. I tried to connect the BF8HHP to my Ubuntu with the hopes of uploading all my programming from my 5R to it, and I keep getting the message:
an error has occurred failure to communicate with radio serial object has no attribute 'setTimeout'
I am using USB0 with a Baofeng cable.
So with this issue, I switched to doing this on my Windows computer, but I don't like that much, because it is quite difficult using the program with a screenreader in Windows. But I successfully exported my 5R to a CSV file. Then I connected the 8HP and imported the 5R file, and then tried to upload it to the 8HP, and in the radio list, the make and model selections are grayed out, and it only shows the UV-5R. I tried to proceed with the upload anyway, but it would not let me. This is the steps for this procedure in the on-line help, even for two different radios. Maybe I missed something?
Thanks for any assistance.
Glenn
Hi All, I got it to work by reading the list archives. I did the removal and install of the chirp-daily and it recognized the radio. It works so well in Linux, I don't think I will be messing with it in Windows. Glenn ----- Original Message ----- From: Glenn To: chirp_users@intrepid.danplanet.com Sent: Sunday, August 14, 2016 11:25 PM Subject: [chirp_users] New member with a couple questions
Hi, My name is Glenn, I live in Nebraska. I have a UV-5R, and my son has a BF 8HP by Baofeng. I should mention that I am using Chirp on computers with a screenreader for the visually impaired. One computer is running Windows 7, and the other is running Ubuntu 16.04. I tried to connect the BF8HHP to my Ubuntu with the hopes of uploading all my programming from my 5R to it, and I keep getting the message:
an error has occurred failure to communicate with radio serial object has no attribute 'setTimeout'
I am using USB0 with a Baofeng cable.
So with this issue, I switched to doing this on my Windows computer, but I don't like that much, because it is quite difficult using the program with a screenreader in Windows. But I successfully exported my 5R to a CSV file. Then I connected the 8HP and imported the 5R file, and then tried to upload it to the 8HP, and in the radio list, the make and model selections are grayed out, and it only shows the UV-5R. I tried to proceed with the upload anyway, but it would not let me. This is the steps for this procedure in the on-line help, even for two different radios. Maybe I missed something?
Thanks for any assistance.
Glenn
------------------------------------------------------------------------------
_______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Glenn at glennervin@cableone.net To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Hi Glenn,
I am glad to hear that you resolved your issue with Ubuntu. Unfortunately the Ubuntu repository installs a very old version of CHIRP (over 3 years old). As you found out you must remove this old version and then add the CHIRP snapshot PPA to your Ubunty (per the instructions on the CHIRP download page) so the latest CHIRP daily build can be installed.
But I successfully exported my 5R to a CSV file. Then I connected the 8HP and imported the 5R file, and then tried to upload it to the 8HP, and in the radio list, the make and model selections are grayed out, and it only shows the UV-5R.
You have download from the BF-F8HP or (load a previously saved file that was previously downloaded from the BF-F8HP) so that the tab label starts with "Baofeng BF-F8HP:". Only a tab labeled this way can be uploaded to the BF-F8HP.
Only a tab with a label that starts with "Baofeng UV-5R:" can be uploaded to the UV-5R.
Also note that it is not necessary to save the UV-5R tab to a CSV file. The CHIRP import feature will import CHIRP Radio Images (*.img) files. It is the selection in the drop-down list just above CSV Files (*.csv). The import process is exactly the same.
Jim KC9HI
Getting the Debian folks (and thus other downstream distros like Ubuntu, Mint, etc) to take a new version of Chip is pretty strait forward. All that needs to be done is a new OFFICIAL version needs to be published and the maintainer be notified. If Dan and team can do the release, I can work with the package maintainers for Debian, Fedora, etc.
--David KI6ZHD
On 08/15/2016 03:15 AM, Jim Unroe wrote:
Hi Glenn,
I am glad to hear that you resolved your issue with Ubuntu. Unfortunately the Ubuntu repository installs a very old version of CHIRP (over 3 years old). As you found out you must remove this old version and then add the CHIRP snapshot PPA to your Ubunty (per the instructions on the CHIRP download page) so the latest CHIRP daily build can be installed.
On Mon, Aug 15, 2016 at 12:19 PM, David Ranch chirp@trinnet.net wrote:
Getting the Debian folks (and thus other downstream distros like Ubuntu, Mint, etc) to take a new version of Chip is pretty strait forward. All that needs to be done is a new OFFICIAL version needs to be published and the maintainer be notified. If Dan and team can do the release, I can work with the package maintainers for Debian, Fedora, etc.
--David KI6ZHD
This latest daily build is the now the "new OFFICIAL version".
Jim KC9HI
Hi Jim & David,
David, the development cycle in Chirp is like a rolling release, with every new daily being the latest stable.
The official download page for the releases is:
http://trac.chirp.danplanet.com/chirp_daily/LATEST/
73 Pavel CO7WT
El 15/08/16 a las 12:52, Jim Unroe escribió:
On Mon, Aug 15, 2016 at 12:19 PM, David Ranch chirp@trinnet.net wrote:
Getting the Debian folks (and thus other downstream distros like Ubuntu, Mint, etc) to take a new version of Chip is pretty strait forward. All that needs to be done is a new OFFICIAL version needs to be published and the maintainer be notified. If Dan and team can do the release, I can work with the package maintainers for Debian, Fedora, etc.
--David KI6ZHD
This latest daily build is the now the "new OFFICIAL version".
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to M.Sc. Pavel Milanes Costa at pavelmc@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
Ha.. yeah.. I saw that recent thread but that generally doesn't fly with package maintainers. They want something tagged and rev'ed as something official. Maybe if we take today's daily, tag it as 0.4.1 and make all future commits as a pending 0.4.2 release, I bet I can get them to work with that.
--David KI6ZHD
On 08/15/2016 09:52 AM, Jim Unroe wrote:
On Mon, Aug 15, 2016 at 12:19 PM, David Ranch chirp@trinnet.net wrote:
Getting the Debian folks (and thus other downstream distros like Ubuntu, Mint, etc) to take a new version of Chip is pretty strait forward. All that needs to be done is a new OFFICIAL version needs to be published and the maintainer be notified. If Dan and team can do the release, I can work with the package maintainers for Debian, Fedora, etc.
--David KI6ZHD
This latest daily build is the now the "new OFFICIAL version".
participants (4)
-
David Ranch -
Glenn -
Jim Unroe -
Pavel Milanes (CO7WT)