April 2017 - Users - lists.chirpmyradio.com

[chirp_users] QYT KT-8900RE
by PETER COYLE 18 Apr '17

18 Apr '17

I just receiver my new QYT KT-8900RE and to my surprise CHIRP has NO listing for that radio, is there a plan in the near future to add the QYT KT-8900RE to your listings? Thanks, Pete-KA6OZS

2 1

[chirp_users] Yaesu FT-857D
by Doc Stevens 18 Apr '17

18 Apr '17

Using CHIRP for Yaesu FT-857D. Noticed when I reprogram radio display defaults to 'Tag' which shows station name. I use frequency instead. I find no option in CHIRP to change this default. Has anyone found this option in CHIRP? Thanks.

4 5

Re: [chirp_users] chirp_users Digest, Vol 100, Issue 15
by M Noivad 18 Apr '17

18 Apr '17

On 2017-04-17 06:35:-0500, Ken wrote: > If its at the end, why not just quit reading after you have read the latest response? It’s not that simple—though I wish it was. Conversation are fluid, some people quote full blocks and interleave their comments and trim, while others hit reply without selecting anything which by default will place the cursor above the entire email they’re replying to with all the sigs at each end of all text underneath rather than this interwoven style. Each email, I have to “hop” down to look for new content and screen carefully that I don’t miss something. Switch to a daily digest for a few days, and you can see what I see. On Apr 17, 2017, at 12:00 PM, Rich Messeder wrote: > > At any rate, I support emails courtesies, and though I appreciate that there may be more programming on the mail list end to remove all the repeated footers, I support that, too. OTOH, >>> if responders simply select the part of the message they are responding to, and reply, then the earlier footers are gone. Problem solved, at the cost of a few seconds on behalf of each sender. And, I opine, a good email habit to have, anyway. > > Though it may not be relevant for this list --- I have not paid attention, partly because there is so much fog in each thread here --- I often get emails that are replies that also include the attachment sent with the original post, and all because the sender simply hit reply or reply all. I think we’re on the same wavelength. I try to keep things simple & only quote what’s needed—thus my list member suggestion (#2: highlight & respond to small chunks) that was after the more scripting intensive #1 suggestion. I do not want to leave the list because I can find out about new features and see issues as they develop. However, simple troubleshooting can create a lot of noise that forces me to skim some digests. I don’t want to curtail anyone’s freedom of expression either—some of the .sigs still crack me up. Unfortunately, short of setting up a phpBB bulletin board for developments, troubleshooting/help along with this channel I see no way around these long chains. BTW, some daily digests contain 20+ emails with complete threads repeated each time which can make for 30+ pages of scrolling. If you want to see it, switch to digest & wait for a busy day (or just copy a full day’s worth of emails into one long text document. I recall one week where I was interested in a thread about support for a new radio, but I gave up trying to follow it after a day or two of it popping up with increasingly long emails. Either way, the noise (or “fog”) actually discourages me from following things here closer—but it’s not like most people have a ton of free time anyway. :) Thanks, M

2 1

Re: [chirp_users] chirp_users Digest Excessive Length
by M Noivad 17 Apr '17

17 Apr '17

I make this request as a person who only received a single email a day since my involvement with this group is more of an issue/application state monitor end-user, that prefers receive concise emails that will take up less time to read. With that in mind I am requesting either admins or end users to take a more active role is reading the raw emails that do not hide repeated copy. Is there any way (A) the mailing list manager could scrub signatures & boilerplate text added at the end of each message when sent in daily digest format? this block: > _______________________________________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com id repeated in every message even in digest form. Also, not truncating .sigs longer than 80(chars)x4(lines) after the first mention make for a very long email when sent in digest form which could be scripted out of creating reams of text. I noticed even the long .sig asking people to consider not printing goes beyond the 4 line .sig guideline established on the UUNET/newsgroups* which tells me others may see this as an issue to. (*Prior to WWW gaining inline images, email lists & newsgroups—like phpBB—was the main method most people used to communicate bidirectionally w/o having to register a domain name, in case some do not know.) If you notice, I do not intentionally add a .sig for this reason. (But I do own all typos & editing mistakes:) This is merely a suggestion. Do with it what you will. Members of this list could also highlight sections they wish to reply to & hit reply in most email applications to trim (semi-)automatically. (For instance: I just hit reply with my setup here.) Thanks CHIRPers, M —anything below this line was added by the software on my end or from the mailing list manager—

3 2

[chirp_users] New Daily Build
by Build System 14 Apr '17

14 Apr '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-20170414 A list of the changes included in this build (since the last daily) follows: Changes for Build #476 [Jim Unroe <rock.unroe(a)gmail.com>] [UV-5R] Fix pep8 Issue This patch fixes a pep8 issue that I thought I has already fixed. releated to issue #4445 [Jim Unroe <rock.unroe(a)gmail.com>] [KT8900D] Add Alias for Surecom S-KT8900D Owners of the Surecom S-KT8900D mobile radio can easily be confused as to which vendor/model to choose in order to program their radio because it is a variant of the QYT KT7900D mobile radio and not the QYT KT8900D as you would assume. This patch adds an alias for the Surecom KT-8900D which will automatcally choose QYT KT7900D as the vendor/model. related to issue #4697

1 0

[chirp_users] kenwood to baofeng
by Jim McIver 13 Apr '17

13 Apr '17

In the attached are kenwood (top) and baofeng column names. Which columns in baofeng do I put the kenwood QT/DQT Enc & QT/DQT Dec numbers that are circled? Do I also have to change Tone Mode to TSql, DTCS, or Cross? thx in advance, -- --Jim McIver

5 9

[chirp_users] baofeng_kenwood
by Jim McIver 12 Apr '17

12 Apr '17

The kenwood program has some different stuff in the QT/DQT Enc, like D032N and it won't let me type it in the Chirp Tone or Tone Sql column. How do I enter the information into chirp? See attached. Also, I guess it's normal when you put codes in Tone & Tone Sql, it changes the Tone Mode to TSQL? thx, -jm

2 2

[chirp_users] kenwood to baofeng
by Jim McIver 11 Apr '17

11 Apr '17

In the attached are kenwood (top) and baofeng column names. Which columns in baofeng do I put the kenwood QT/DQT Enc & QT/DQT Dec numbers? Do I also have to change Tone Mode to TSql, DTCS, or Cross? thx in advance, -- Jim McIver

1 0

[chirp_users] Questions regarding packaging
by David Thurstenson 10 Apr '17

10 Apr '17

Hi, I manage chirp-hg on the Arch User Repository[1], and there has been some discussion about how things should be packaged going forward. My main question is regarding chirpc. I'm aware that the release tarball (chirp-daily-20170406 as of the time of writing) does not currently include chirpc and it's documentation, but I'm not clear on why. What is the reason for it's exclusion? I ask as we are deciding whether or not to include chirpc in the release package. The Arch Packaging Guidelines for Python packages[2] strongly suggests using the setup.py installer that is released by upstream, and the exclusion of chirpc from this installer seemingly indicates that it shouldn't be included in a downstream package. Since some users might like the option of using chirpc, I want to include it, but if it's not release-worthy, I'll include it as a separate optional package instead. Thanks, David [1]: https://aur.archlinux.org/ [2]: https://wiki.archlinux.org/index.php/Python_package_guidelines

2 1

[chirp_users] What I did...
by ronmaxkaraoke＠aol.com 09 Apr '17

09 Apr '17

I have been fighting with the Chirp Program to get it to work on my computer. I tried everything that you told me to do and even order a another cable that has the FIDI chip in it and it still did not work, then I thought about (PC MATIC) that I had just installed and it was stopping part of the Chirp Program from being loaded. So I turned off (PC MATIC) and reloaded Chirp Program and wa-la it worked. So for those that are having a problem with getting Chirp to work tell them to check there Anti-Virus program. Thanks Ronald Burns

2 1