[chirp_users] Chirp program
Good day to you, I am using Chirp for programming my UV 5 R Baofeng Radio. Suddenly when I request to "Download from Radio" I receive the message " Not enough data" Why would that be please. I have used it before and had no problems.
Regards George
On Wed, Jun 24, 2020 at 4:10 AM George Piek georgepiek7@gmail.com wrote:
Good day to you, I am using Chirp for programming my UV 5 R Baofeng Radio. Suddenly when I request to "Download from Radio" I receive the message " Not enough data" Why would that be please. I have used it before and had no problems.
Regards George
Hi George,
From the information you have provided, I am going to guess that you
may be selecting the wrong model. Here's why.
There is no CHIRP driver for any radio model that provides a " Not enough data" message to the user. The word "enough" doesn't even show up in any message for any radio driver module. So looking through all of the Baofeng radio driver modules for messages that contain both "not" and "data" I find "baofeng_common.py". It contains the following message: "Error reading data from radio: not the amount of data we want." Assuming this message is the actual message that you are seeing, this allows me to get a list of all radio driver modules that use "baofeng_common.py". They are as follows.
baofeng_wp970i.py gmrsuv1.py mursv1.py uv6r.py uv5x3.py
From the above list only "baofeng_wp970i.py" and "uv6r.py" use the
Vendor: Baofeng selection. Assuming that "UV 5 R" means "UV-5R", if I hook up a UV-5R and choose Vendor: Baofeng and Model: UV-6R, I get the "Error reading data from radio: not the amount of data we want." message (screen capture attached).
Since the "UV-5R" and "UV-6R" selections are visually similar, I think you may accidentally be choosing "UV-6R" instead of choosing "UV-5R".
Jim KC9HI
Hi, yes you are correct on the actual msg. No I have made double sure in selecting the correct radio i.e. UV 5 R. As I said, cannot understand why because I had downloaded from same radio previously.
Regards George
On Wed, 24 Jun 2020, 14:14 Jim Unroe, rock.unroe@gmail.com wrote:
On Wed, Jun 24, 2020 at 4:10 AM George Piek georgepiek7@gmail.com wrote:
Good day to you, I am using Chirp for programming my UV 5 R Baofeng
Radio. Suddenly when I request to "Download from Radio" I receive the message " Not enough data" Why would that be please. I have used it before and had no problems.
Regards George
Hi George,
From the information you have provided, I am going to guess that you
may be selecting the wrong model. Here's why.
There is no CHIRP driver for any radio model that provides a " Not enough data" message to the user. The word "enough" doesn't even show up in any message for any radio driver module. So looking through all of the Baofeng radio driver modules for messages that contain both "not" and "data" I find "baofeng_common.py". It contains the following message: "Error reading data from radio: not the amount of data we want." Assuming this message is the actual message that you are seeing, this allows me to get a list of all radio driver modules that use "baofeng_common.py". They are as follows.
baofeng_wp970i.py gmrsuv1.py mursv1.py uv6r.py uv5x3.py
From the above list only "baofeng_wp970i.py" and "uv6r.py" use the
Vendor: Baofeng selection. Assuming that "UV 5 R" means "UV-5R", if I hook up a UV-5R and choose Vendor: Baofeng and Model: UV-6R, I get the "Error reading data from radio: not the amount of data we want." message (screen capture attached).
Since the "UV-5R" and "UV-6R" selections are visually similar, I think you may accidentally be choosing "UV-6R" instead of choosing "UV-5R".
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to George Piek at georgepiek7@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Jun 24, 2020 at 9:26 AM George Piek georgepiek7@gmail.com wrote:
Hi, yes you are correct on the actual msg. No I have made double sure in selecting the correct radio i.e. UV 5 R. As I said, cannot understand why because I had downloaded from same radio previously.
Regards George
Then please supply some additional information. You've supplied very little. Such as...
CHIRP version: Operating system and version (Windows, Linux, macOS): Programming cable type (which USB-to-Serial chip is inside): Attach clean debug.log file:
The "How To Report Issues" page shows how to find the debug.log file for all 3 supported operating systems. https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
A "clean" debug.log file is one where you close CHIRP, open CHIRP, cause the error and finally close CHIRP.
Jim KC9HI
My operating system is Windows 10. Version of Chirp is latest , 20200622
On Wed, 24 Jun 2020, 15:54 Jim Unroe, rock.unroe@gmail.com wrote:
On Wed, Jun 24, 2020 at 9:26 AM George Piek georgepiek7@gmail.com wrote:
Hi, yes you are correct on the actual msg. No I have made double sure in
selecting the correct radio i.e. UV 5 R. As I said, cannot understand why because I had downloaded from same radio previously.
Regards George
Then please supply some additional information. You've supplied very little. Such as...
CHIRP version: Operating system and version (Windows, Linux, macOS): Programming cable type (which USB-to-Serial chip is inside): Attach clean debug.log file:
The "How To Report Issues" page shows how to find the debug.log file for all 3 supported operating systems. https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
A "clean" debug.log file is one where you close CHIRP, open CHIRP, cause the error and finally close CHIRP.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to George Piek at georgepiek7@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
And my cable is a Boafeng cable purchased from China shop. As I said, cable worked before.
On Wed, 24 Jun 2020, 16:15 George Piek, georgepiek7@gmail.com wrote:
My operating system is Windows 10. Version of Chirp is latest , 20200622
On Wed, 24 Jun 2020, 15:54 Jim Unroe, rock.unroe@gmail.com wrote:
On Wed, Jun 24, 2020 at 9:26 AM George Piek georgepiek7@gmail.com wrote:
Hi, yes you are correct on the actual msg. No I have made double sure
in selecting the correct radio i.e. UV 5 R. As I said, cannot understand why because I had downloaded from same radio previously.
Regards George
Then please supply some additional information. You've supplied very little. Such as...
CHIRP version: Operating system and version (Windows, Linux, macOS): Programming cable type (which USB-to-Serial chip is inside): Attach clean debug.log file:
The "How To Report Issues" page shows how to find the debug.log file for all 3 supported operating systems. https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
A "clean" debug.log file is one where you close CHIRP, open CHIRP, cause the error and finally close CHIRP.
Jim KC9HI _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to George Piek at georgepiek7@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com
On Wed, Jun 24, 2020 at 10:28 AM George Piek georgepiek7@gmail.com wrote:
And my cable is a Boafeng cable purchased from China shop. As I said, cable worked before.
debug.log?
Jim KC9HI
participants (2)
-
George Piek -
Jim Unroe