- Users - lists.chirpmyradio.com

[chirp_users] CHIRP and the Kenwood TH-F6A; syncing with Icom
by Rich Messeder 27 May '16

27 May '16

Using the Kenwood Memory Control Program (MCP), I can create and save radio images independent of the radio. But when I use CHIRP, I get "The Kenwood TH-F6 operates in live mode. This means that any changes you make are immediately sent to the radio. Because of this, you cannot perform the Save or Upload operations. If you wish to edit the contents offline, please Export to a CSV file, using the File menu." In the first place, why the behaviour? It does not appear necessary. I have verified that a change in MCP is not written until I write it. But CHIRP is indeed live. Why? It would be nicer if it were not. And why not save an image, even if the edits are live? This leads to my current puzzle. I have downloaded from the F6A in CHIRP. I save as a *.chirp file. I wanted to copy that to my Icom IC-T8A. I followed the beginner's guide and FAQ to merge the Kenwood data with the Icom data. Of course, the Kenwood data is not a *.img file, but a *.chirp file, and I get a schema error. The error makes sense, but only to a point...I guess that I am missing how to update different radios with the same data. I tried opening both the Icom img and the Kenwood in different instances of CHIRP, but I cannot copy from one and paste to the other. I'm sure that there is a simple step that I am missing. ~R~ NE1EE Short email? No html? Here's why: http://emailcharter.org/

4 3

[chirp_users] Cut and paste issue?
by Dennis Carr 26 May '16

26 May '16

Greetings! New user here, Still getting used to the software so I can get back on the air after eight years of no radio. (It sucked.) While working the software and rearranging a few layouts (using a BF-F9V2+), I noticed that Ctrl-X seems to behave much like Ctrl-C: it will copy, but it will not delete the original memory location once I have pasted elsewhere using Ctrl-V. I'm using XFCE on Debian Jessie at this time and running the daily from 20160517. This seems to be the only program where there are issues. Any words on this? Thanks, -Dennis KE7KIF

5 7

Re: [chirp_users] Cut and paste issue?
by Rich Messeder 26 May '16

26 May '16

Do I understand correctly that this feature applies to a few Yaesus, but exists in CHIRP for all radios to accommodate those few? I tried clicking after ctrl-x, and I see that the memory is active again, and this is on a download for a Kenwood F6A. OK as a backup, but not intuitive. It works on ctrl-x, where I can recover by following up with either clicking or by pasting (as long as no other actions overwrite the buffer), but does not work for deletion. I've been in a habit of thinking that cutting is more or less permanent, and I guess that it is here, too, but only after I write to the radio and complete the process. Whether the memory is grey or zeroed, I can always paste over it or edit it, so there is no loss of generality. ~R~ NE1EE On 2016-05-25 21:45:-0700, Tom Hayward wrote: >On Wed, May 25, 2016 at 6:44 PM, Rich Messeder <rich.messeder(a)gmail.com> wrote: >> But there is a comment below that reference data on the radio that is not accessible. This is puzzling to me. Does that mean that the data exists in the radio, but there is a flag also in the radio that says not to access that memory? Or recall it? Or tune to it? What is the point? Seems to me that if I delete a memory from the radio panel or from CHIRP, it ought to be gone. It's up to me to have a backup file if I want it... > >Yes, in a few Yaesu radios, deleted (or "masked") channels are set >with a flag. I believe the design goal by Yaesu here was to allow the >opportunity to undo a delete. In addition to supporting this, Chirp >also has the capability to write zeros over the whole block of memory. >For these select few radios, Chirp supports both delete mechanisms in >a two-stage delete (as described). The goal here was to make the Chirp >support as many of the radios' features as possible, and for the >experience to be as close to the radios' interface as possible. > >When a channel is masked (the first stage of the two-stage delete on >Yaesu radios), it can be unmasked from the front panel of the radio >(see the manual) or in Chirp, just click the greyed-out text to >resurrect it. > >Tom KD7LXL

1 0

Re: [chirp_users] Cut and paste issue?
by Rich Messeder 26 May '16

26 May '16

This is a key reply for me...I had originally thought that if CHIRP knew enough to turn the entry grey, it should know enough to reset the entry to empty. Why not? It would save the confusion that I have had, and that others seemingly have had. But there is a comment below that reference data on the radio that is not accessible. This is puzzling to me. Does that mean that the data exists in the radio, but there is a flag also in the radio that says not to access that memory? Or recall it? Or tune to it? What is the point? Seems to me that if I delete a memory from the radio panel or from CHIRP, it ought to be gone. It's up to me to have a backup file if I want it... Well, that was why I gave it a +1...I found (find) it confusing (now just distracting) to delete a memory and have it turn grey, not reset to "empty". If there is a requirement of the radio that makes the grey data necessary, so be it. I am not sure that I see this in effect on any of my radios...? ~R~ On 2016-05-25 13:15:-0700, you wrote: >On Wed, May 25, 2016 at 12:30 PM, Dennis Carr ><dennisthetiger(a)chez-vrolet.net> wrote: >> On Wed, 25 May 2016 14:15:17 -0500 >> Todd Bloomingdale <tbloomingdale(a)gmail.com> wrote: >> >>> Dennis, >>> >>> Once you cut a memory it will go grey. After you have pasted your cut >>> that location is now open to add another frequency into its spot even >>> though it shows as a greyed out. >> >> I should probably rephrase. It doesn't remove the settings from the >> old memory slot - this, in my mind, would be the correct behavior. > >Are you saying that after pasting, seeing the old line greyed out, and >uploading to the radio, that channel is still usable in the radio? > >I don't know how the BF-F9V2+ works, but on many Chirp radios there is >two stage delete: the first delete or ctrl-x will mask the channel. >This is illustrated in Chirp by light gray text. The data will still >be in the radio, but you won't be able to recall or tune it (common on >Yaesu radios). The second delete will zero out the channel so there is >no evidence of it ever being there. > >Tom KD7LXL >_______________________________________________ >chirp_users mailing list >chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to WeatheredSoul at rich.messeder(a)gmail.com >To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

2 1

[chirp_users] Success w/Linux
by Jack Schlachter 26 May '16

26 May '16

I want to thank the guys that help me with my Baofeng HH. Chirp loaded fine in Linux but I had trouble picking the right port the USB cable was on. One of you suggested USB0 and I did that "ls" command and it added it to the drop down list or it was always there at the very bottom. Then I ran that permissions command sudo usermod -aG dialout username and then logged out and back in and it finally worked. Now to get my Luiton working. Does anyone know if there is a radio on the Chirp list that would be compatable with the model LT- Luiton 588UV? Failing that does anyone know of any plans to add this radio. TIA I was wondering if you could tell me where I can get a list of commands to use in terminal with explanations of what they do, I know there's one out there somewhere if you could just point me. Again thank you for your help. Jack KM4TDJ

1 0

Re: [chirp_users] Problem reading memory on my UV5R
by S Allan Wilson 26 May '16

26 May '16

I am hoping this gets to the correct thread. I am using a Prolific Cable to interface with my Rugged Radios RH-5R. I think this is a clone of the Baofeng UV5R (?). I also run Windows 10. I found a discussion about Code 10 on Family Software (http://www.ifamilysoftware.com/news37.html). I read this article and then down loaded the file PL2303_64bit_Installer.exe. I run this first and follow onscreen instructions about when to plug in the cable. This has worked at allowing me to communicate with my radios. Maybe this will help someone here. Al Wilson -- Home is where the RV is *Home is where the RV is.* *Our Current Location <http://map.datastormusers.com/user1.cfm?user=1487> * *"OUR MISSION STATEMENT"* *Life's journey is not to arrive at our grave safely in a well preserved body, * *but to skid in sideways totally worn out, shouting * *"Holy Crap", what a ride!"*

1 0

[chirp_users] Baofeng UV-6R
by Geoff Hicks 25 May '16

25 May '16

Will CHIRP support this radio anytime soon? Is there some way that I can assist with the process? Thanks for creating this application! Sent from my iPad

2 1

[chirp_users] now using Linux
by Jack Schlachter 25 May '16

25 May '16

Hi - I'm the one trying to use chirp with my Luiton radio. Still same problem as per last post. So I had an idea. I was reading about the Linux part on danplanet and decided to pull out my Linux machine and give my Baofeng a try and maybe if I can get that to work it would work on my Luiton. So I loaded chirp on Linux as per instructions and everything went fine. Plugged my radio in and got : An error has occurred; could not open port /dev/ttyS0: [Errno13] Permission denied:'/dev/ttyS0' So I read further on your site and ran "sudo usermod -aG dialout username" replacing username with mine, closed chirp reopened and tried again with same results. I have to admit I'm not real Linux savvy. I don't really understand how you pick a port. When I click the down arrow there's a whole list of /dev/ttyS? so I took the default chirp pulled up which is obviously /dev/ttyS0 How do I find out which port my cable is on? thanks again, Jack

3 2

Re: [chirp_users] now using Linux
by Ted Roby 25 May '16

25 May '16

You can verify which group /dev/ttyS0 belongs to by running: ls -l /dev/ttyS0 Add yourself to whichever group it belongs. You will also have to logout and login again to refresh your permissions. On May 24, 2016 7:47 PM, "Jack Schlachter" <km4tdj(a)gmail.com> wrote: Hi - I'm the one trying to use chirp with my Luiton radio. Still same problem as per last post. So I had an idea. I was reading about the Linux part on danplanet and decided to pull out my Linux machine and give my Baofeng a try and maybe if I can get that to work it would work on my Luiton. So I loaded chirp on Linux as per instructions and everything went fine. Plugged my radio in and got : An error has occurred; could not open port /dev/ttyS0: [Errno13] Permission denied:'/dev/ttyS0' So I read further on your site and ran "sudo usermod -aG dialout username" replacing username with mine, closed chirp reopened and tried again with same results. I have to admit I'm not real Linux savvy. I don't really understand how you pick a port. When I click the down arrow there's a whole list of /dev/ttyS? so I took the default chirp pulled up which is obviously /dev/ttyS0 How do I find out which port my cable is on? thanks again, Jack _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Ted Roby at ted.roby(a)gmail.com To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com

1 0

[chirp_users] Problem reading memory onmy UV5R
by Bill Skinner 24 May '16

24 May '16

Hi All I am back after many months---I want to read the memory on my UV-5R. I am using a USB cable I purchased with the radio (4/20/13). I follow the instructions but when I try and download from the radio I get a message indicating the program can't read the radio. When I plug in the cable, the red transmit light turns on. I am using Windows 10---help please.

4 4