June 2017 - Users - lists.chirpmyradio.com

[chirp_users] Are CHIRP img files are always backward compatible?
by Rich Messeder 03 Jun '17

03 Jun '17

For each new release of CHIRP, should I read a new file from the radio, open the latest saved file, and copy memories to the new file? The issue prompting this is that I wonder if CHIRP img files are always backward compatible? Sometimes compatible? What is the 'best practice'? 73 ~R~ NE1EE ARES AEC

2 1

[chirp_users] *.chirp files
by Rich Messeder 03 Jun '17

03 Jun '17

I saved *.chirp files from the F6A, but can't read them now. I think that they are deprecated, but didn't find that when I looked in the CHIRP rev history...not sure how to search for that specific item. If so, I suppose that I might as well delete all .chirp files? I am using CHIRP 2017-05-26. 73 ~R~ NE1EE ARES AEC

3 2

[chirp_users] Copying between the Kenwood F6A and V71A
by Rich Messeder 03 Jun '17

03 Jun '17

I'd like to copy between the F6A to the V71A, but CHIRP does not permit saving Kenwood files. With my Baofeng, I can open multiple CHIRP instances or open different files on different tabs, and copy from one to another. All I can think of is to have them both connected to the computer at the same time, and copy|paste? Or maybe use csv files? I have submitted a feature request to have CHIRP save Kenwood images. 73 ~R~ NE1EE ARES AEC

6 8

Re: [chirp_users] Copying between the Kenwood F6A and V71A
by Rich Messeder 03 Jun '17

03 Jun '17

On 2017-06-03 09:37:-0400, you wrote: >On Sat, 3 Jun 2017 13:00:33 +0000 >Rich Messeder <NE1EE(a)hotmail.com> wrote: > >> I'd like to copy between the F6A to the V71A, but CHIRP does not >> permit saving Kenwood files. With my Baofeng, I can open multiple >> CHIRP instances or open different files on different tabs, and copy >> from one to another. >> >> All I can think of is to have them both connected to the computer at >> the same time, and copy|paste? Or maybe use csv files? >> >> I have submitted a feature request to have CHIRP save Kenwood images. > >Why not open a new "tab", copy from the th-f6a into new tab, then >attach V71, read it. Copy from new "tab" into the V71 & save? > >-- >Rodney D. Myers <rdmyers.42(a)gmail.com> - kg6anx Great idea. I will give this a try at next opportunity. My "problem" was having 2 radios "connected" at the same time, because I have only 1 USB cable. But the radios are "hot-swappable", I have discovered, so this may do the trick. I'll save this thread and update w results. 73 ~R~ NE1EE ARES AEC

2 1

[chirp_users] Yaesu FTM-400XD
by Tom Henderson 03 Jun '17

03 Jun '17

Looks like there is an effort to add support for this radio to Chirp, but it appears to be stalled. How does one assist with adding support for new radios to Chirp? I have linux and windows PCs and a radio, happy to assist if I can. -- Tom Henderson

2 1

Re: [chirp_users] blocked reply to thread
by Baji Panchumarti 03 Jun '17

03 Jun '17

Rich, It is not your HOTMAIL address that has been blacklisted. The IP address, or the IP address block, or the ISP that you used to send the reply has been black listed. RBL stands for Real-Time Blackhole List http://www.webopedia.com/TERM/R/RBL.html You sent a reply from *40.92.10.77, *apparently that IP address or its IP block have been used to spam. Three different anti-spam lists have black listed the IP address from which you sent the reply, details can be found here: http://www.anti-abuse.org/multi-rbl-check-results/?host=40.92.10.77 Hotmail & yahoo publish the IP address from which an email was sent, GMail does not. Hope that helps. -baji. ~~ K 8 I I T _ On Sat, Jun 3, 2017 at 10:15 AM, Rich Messeder <NE1EE(a)hotmail.com> wrote: intrepid.danplanet.com rejected your message to the following email > addresses: > > Discussion of CHIRP (chirp_users(a)intrepid.danplanet.com) > Your message wasn't delivered because the destination email system > rejected your message for security or policy reasons. For example, the > email address might only accept messages from certain senders, or it might > not accept certain types of messages, like those larger than a specific > size. > > Contact the recipient (by phone, for example) and work with them and their > email admin to determine what policy or setting blocked your message and > what you should do to make sure that future messages from you won't be > rejected. > > For more information, see Status code 5.7.1. > > > intrepid.danplanet.com gave this error: > <chirp_users(a)intrepid.danplanet.com>: Recipient address rejected: blocked > by RBL: rbl:truncate.gbudb.net:<http://www.gbudb.com/truncate/ > [40.92.10.77]> > > > > > What happened? I replied with the same email address that I used to send > the original message. > > 73 > ~R~ > NE1EE > ARES AEC > > ________ >

1 0

[chirp_users] blocked reply to thread
by Rich Messeder 03 Jun '17

03 Jun '17

intrepid.danplanet.com rejected your message to the following email addresses: Discussion of CHIRP (chirp_users(a)intrepid.danplanet.com) Your message wasn't delivered because the destination email system rejected your message for security or policy reasons. For example, the email address might only accept messages from certain senders, or it might not accept certain types of messages, like those larger than a specific size. Contact the recipient (by phone, for example) and work with them and their email admin to determine what policy or setting blocked your message and what you should do to make sure that future messages from you won't be rejected. For more information, see Status code 5.7.1. intrepid.danplanet.com gave this error: <chirp_users(a)intrepid.danplanet.com>: Recipient address rejected: blocked by RBL: rbl:truncate.gbudb.net:<http://www.gbudb.com/truncate/ [40.92.10.77]> What happened? I replied with the same email address that I used to send the original message. 73 ~R~ NE1EE ARES AEC

1 0

[chirp_users] New Daily Build
by Build System 03 Jun '17

03 Jun '17

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20170603 A list of the changes included in this build (since the last daily) follows: Changes for Build #486 [Angus Ainslie <angus(a)akkea.ca>] [FT1D] Add support for setting backtrack targets - issue #4877 [SASANO Takayoshi <uaa(a)mx5.nisiq.net>] fix for bug #4863 Delete function cannot work when translating msgid "Loc", this is caused by "Loc" (instead of _("Loc")). And, non_editable flag in make_editor() has same problem. Both fixed.

1 0

[chirp_users] New Daily Build
by Build System 02 Jun '17

02 Jun '17

Greetings, A new daily build of CHIRP is available. This includes changes made directly to the tree yesterday, and may include additional features, bug fixes, and/or bugs. If you are interested in trying it, grab it from the following location: http://trac.chirp.danplanet.com/chirp_daily/daily-20170602 A list of the changes included in this build (since the last daily) follows: Changes for Build #485 [Dan Smith <dsmith(a)danplanet.com>] [ui] Re-focus the original path after editing is completed When editing things like a combo in the memory editor, accepting the edit will screw up the tab order by choosing something else to focus after the ephemeral widget used to do the edit is removed. This saves the current path when editing starts and restores it when editing is finished to avoid messing up the workflow. Fixes #4865

1 0