February 2018 - Users - lists.chirpmyradio.com

[chirp_users] Yaesu FT-2DR and Mac OS 10.13.3 (High Sierra) Programming Cable Recommendation
by Kell Bodholt 17 Feb '18

17 Feb '18

Looking for some specific advice for a FTDI cable for use with the Yaesu FT-2DR and Mac OS 10.13.3 on McBook Air (not running Windows on a separate partition). I have reviewed the Chirp FAQ, cable sections, Activity, etc. and have searched various websites for a specific FTDI USB cable without success as most that I have located do not have the correct connection to plug into the FT-2DR. The FT-2DR came with a USB cable, but I believe this is a cable specifically for updating the firmware and not for programing via Chirp. I'm unable to find any info on the Yaesu USB cable whether it’s a FTDI and/or Prolific type cable, but I suspect that its neither as my MacBook Air does nothing when plugged in nor does Chirp recognize any available port for uploading/receiving HT data. The FT-2DR does have a SD card, and I have event tried making a backup file of the memory channels (file name created on SD card is MEMORY.dat), taking that file and loading it into Chirp, manipulating with my local repeater info, re-save as a MEMORY.dat file, and on the FT-2DR read the file with no success. I've spent way too much time trying to figure this out, and I am giving up. So can anyone recommend a FTDI cable specific for the FT-2DR that will work with Chirp on my MacBook Air or alternatively a FTDI cable specific to the FT-2DR that will work with Chirp on a Windows 10 machine. I don't want to fuss with counterfeit cables and the headache of loading appropriate drivers. The data cable that came with the FT-2DR is a std USB on one end and the end that goes into the data port on the FT-2DR I believe is a mini usb. Thank you in advance. Svenster -----Original Message----- From: <chirp_users-bounces(a)intrepid.danplanet.com> on behalf of <chirp_users-request(a)intrepid.danplanet.com> Reply-To: <chirp_users(a)intrepid.danplanet.com> Date: Saturday, February 10, 2018 at 12:01 PM To: <chirp_users(a)intrepid.danplanet.com> Subject: chirp_users Digest, Vol 110, Issue 4 Send chirp_users mailing list submissions to chirp_users(a)intrepid.danplanet.com To subscribe or unsubscribe via the World Wide Web, visit http://intrepid.danplanet.com/mailman/listinfo/chirp_users or, via email, send a message with subject or body 'help' to chirp_users-request(a)intrepid.danplanet.com You can reach the person managing the list at chirp_users-owner(a)intrepid.danplanet.com When replying, please edit your Subject line so it is more specific than "Re: Contents of chirp_users digest..." Today's Topics: 1. New Daily Build (Build System) ---------------------------------------------------------------------- Message: 1 Date: Sat, 10 Feb 2018 00:13:48 -0800 (PST) From: Build System <donotreply(a)danplanet.com> Subject: [chirp_users] New Daily Build To: chirp_users(a)intrepid.danplanet.com Message-ID: <874799113.100.1518250428614.JavaMail.jenkins(a)eagle.danplanet.com> Content-Type: text/plain; charset="utf-8" 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-20180210 A list of the changes included in this build (since the last daily) follows: Changes for Build #515 [Dan Smith <dsmith(a)danplanet.com>] Fix MURS1 radio to use validate_memory() and make edges test case tolerant This fixes one test case that should ignore memories that don't validate from the radio, and makes the MURS1 radio support said validation. This is related to #5255 [Jim Unroe <rock.unroe(a)gmail.com>] [MURS-V1] Add Support for BTech MURS-V1 This patch adds support for the BTech MURS-V1 handheld radio. #5255 [Jim Unroe <rock.unroe(a)gmail.com>] [MURS-V1] Prepare CHIRP for BTech MURS-V1 (update baofeng_common.py) The BTech GMRS-V1 and BTech MURS-V1 are very different radios but both respond to the same "magic". This patch provides checks to make sure... 1. the model selected by the user matches the physical radio model. 2. the image being uploaded matches the physical radio model. related to #5255 ------------------------------ _______________________________________________ chirp_users mailing list chirp_users(a)intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users To unsubscribe, send an email to chirp_users-unsubscribe(a)intrepid.danplanet.com End of chirp_users Digest, Vol 110, Issue 4 *******************************************

4 4

[chirp_users] Midland ml3245
by jquinn53 17 Feb '18

17 Feb '18

Will an older version of chirp program a midland ml3245 and on what windows operating system. Sent via the Samsung Galaxy S® 5 ACTIVE™, an AT&T 4G LTE smartphone

4 5

[chirp_users] Yaesu VX-6
by Garnet Robinson 14 Feb '18

14 Feb '18

Hello All, Where can I buy a programming cable that will work with CHIRP, Windows 10, and my Yaesu VX-6? Thanks. Sent with the help of my cat. 🐱

7 7

Re: [chirp_users] linux command line
by David 14 Feb '18

14 Feb '18

Thanks, this definitely helps, I will take another look and give it a try if I can get it set up --David At 02:57 PM 2/14/2018, Tycen Stafford wrote: >Well, that's what I though, but hey look at >that.. I did just see that command line chirp >can do some editing!Â You can list the >settings, list the memory channels, set a memory >channel, clear a memory channel and copy a >memory channel. So about the only thing you >can't do is edit settings. I was only looking >for something to upload to the radio so I hadn't >paid attention to the rest of the README. I just >tired it out on on of my images and it seems to >work. From the README page on github: > > >List Settings >------------- > >For radios that support settings, you can list the current settings >in a saved image: > > chirpc --mmap=<file> --list-settings > > >Show Memory Channels >-------------------- > >You can list all current memory channels in a saved image: > > chirpc --mmap=<file> --list-mem > >That command only lists the currently programmed channels. To see the >complete list (including empty channels), add '--verbose'. > >To view only a single channel, use the --get-mem option: > > chirpc --mmap=<file> --get-mem <channel> > > >Set a Memory Channel >-------------------- > > chirpc --mmap=<file> --set-mem-name=<name> ... <channel> > >See the --help text for a complete list of options that can be used >to configure the channel. Any settings that are not configured using >a command option will be left unchanged. > > >Clearing a Memory Channel >------------------------- > >You can clear a memory channel, discarding all settings: > > chirpc --mmap=<file> --clear-mem <channel> > > >Copying a Memory Channel >------------------------ > >You can copy a memory channel: > > chirpc --mmap=<file> --copy-mem <source_channel> <destination_channel> > >Note: The contents of <destination_channel> will be overwritten with >the contents from <source_channel> > > >On Wed, Feb 14, 2018 at 1:08 PM, David ><<mailto:BearSFO@pacbell.net>BearSFO(a)pacbell.net> wrote: > >So, from what you just described, the edits >would still need to be done inside chirp GUI? > >--David > > >At 10:48 AM 2/14/2018, Tycen Stafford wrote: >>Good question. chirp certainly works in a Linux >>GUI (I've used it on Ubuntu and it works >>great!). But as for the command-line, editing >>is not an option as documented in the chirp.hg >>software link I sent. I tried vim'ing the img >>file but it looks like it's binary. Quick >>command-line edits would be handy though, for >>sure - although I imagine it would be one of >>those things that would be really easy to mess >>up if you put in the wrong type of >>character/data or whitespace. It would probably >>need a validator command with it to validate >>the img file before trying to upload it to your >>radio. I think it's one of things where it's >>not an option because no one's developed it >>yet. The user-base would probably be a fraction >>of the users who use the GUI so all the time and focus goes to the GUI.Ã >> >>Also, I mentioned that my implementation uses >>Dropbox to sync the img files around - you of >>course use scp or rsync or some other filesync >>utility. I just used Dropbox because my radio >>files were already there and it was quick and >>easy to generate a public (yet obscure) URL and just do a wget. >> >>On Wed, Feb 14, 2018 at 10:09 AM, David >><<mailto:BearSFO@pacbell.net>BearSFO(a)pacbell.net> wrote: >>My linux implementation have no GUI set up, and >>I just want to be able to read/write from/to my >>radios.ÃÂ I can certainly edit the file >>somewhere else, dump it in, and then run chirp. >>Having said that, is there a reason why it cannot be edited on linux? >>--David >> >>At 09:36 AM 2/14/2018, Tycen Stafford wrote: >>>Nah, I'd have to disagree, Nigel.Ã I don't >>>need tto create/edit radio config files every >>>time I use chirp, often times I just need to >>>update a radio with a config I already have.Ã >>>It's 100% usable from the command line for me >>>for the scenario I described. Having the >>>ability to have a pocket-sized headless radio >>>updater is completely useful for me. I can >>>think of other applications, too - if you had >>>a dozen (or a hundred) radios that needed the >>>same config applied repeatedly then you could >>>add a button to that raspberry pi that >>>triggered the command line update script and >>>update your radios as fast as you could unplug >>>and plug them from the programming cable >>>(without having to click through the GUI). >>>They don't all have to be the same radio, >>>either. My script cycles through my 4 >>>different radio types automatically until it >>>finds the right one to update. If I were using >>>the GUI I would have to open 4 different files >>>and click through all the update confirmation >>>dialogs. With my headless updater I just plug >>>in whatever radio I want updated and kick off >>>the update command and then wait for it to finish.Ã >>>So, I understand that a command line chirp >>>would not be useful to some (maybe even most), >>>but that doesn't mean it's not usable to others.Ã >>>David, what application were you looking for? >>> >>>On Wed, Feb 14, 2018 at 6:18 AM, Nigel A. Gunn >>>G8IFF/W8IFF <<mailto:nigel@ngunn.net>nigel(a)ngunn.net> wrote: >>>If you have to create/edit your radio config >>>files from the GUI on your desktop then Chirp >>>is not fully usable from the command line. >>> >>> >>>>On 14 February 2018 at 02:51 Tycen Stafford >>>><<mailto:tycen@tycen.com>tycen(a)tycen.com> wrote: >>>>Yes, you can use Chirp on the command >>>>line:ÃÃÂ >>>><https://github.com/tylert/chirp.hg>https://github.com/tylert/chirp.hg >>>>I use a Raspberry Pi Zero W as a headless >>>>chirp updater (for my mobile radio). I keep >>>>my chirp files saved in a Dropbox folder with >>>>public URLs - this way I can edit from the >>>>GUI on my desktop and then fire up the >>>>Raspberry Pi in the car (using my phone's >>>>hotspot feature) so it can pull the latest >>>>chirp images from Dropbox (via wget) and >>>>update the radio using command line chirp. >>>>I'm still working on the README but here's my >>>>files for putting it all >>>>together:ÃÃÂ >>>><https://github.com/tycen/chirpi>https://github.com/tycen/chirpi >>>>I just call the updater script from cron on reboot. >>>>-Tycen >>>>On Tue, Feb 13, 2018 at 5:27 PM, Nigel A. >>>>Gunn G8IFF/W8IFF <<mailto:nigel@ngunn.net>nigel(a)ngunn.net> wrote: >>>>You can start it from the command line >>>>(chirpw) but it is not usable without a GUI. >>>> > On 13 February 2018 at 20:24 David <BearSFO(a)PacBell.NET> wrote: >>>> > >>>> > >>>> > >>>> > Does chirp works on the linux command line? thanks >>>> > >>>> > --David >>>> > >>>> > _______________________________________________ >>>> > chirp_users mailing list >>>> > >>>> <mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >>>> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>>> > This message was sent to Nigel Gunn, W8IFF >>>> at <mailto:nigel@ngunn.net>nigel(a)ngunn.net >>>> > To unsubscribe, send an email to >>>> <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com >>>> >>>>Nigel A. Gunn, >>>><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>1865 >>>>El Camino Drive, Xenia, OH 45385-1115, USA. tel <http://??>+1 937 825 5032 >>>>Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), >>>>e-mail >>>><mailto:nigel@ngunn.net>nigel(a)ngunn.net www >>>><http://www.ngunn.net>http://www.ngunn.net >>>>Member of ARRL, QRPARCI #11644, SOC #548, >>>>Flying Pigs QRP Club International #385, >>>>Ã Dayton ARA #2128, AMSAT-NA LM-1691, GCARES,, EAA382. >>>>______________________________ _________________ >>>>chirp_users mailing list >>>><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >>>> >>>>http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>>>This message was sent to Tycen at <mailto:tycen@tycen.com>tycen(a)tycen.com >>>>To unsubscribe, send an email to >>>><mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com >>>> > >_______________________________________________ >chirp_users mailing list ><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >http://intrepid.danplanet.com/mailman/listinfo/chirp_users >This message was sent to Nigel Gunn, W8IFF at ><mailto:nigel@ngunn.net>nigel(a)ngunn.net >To unsubscribe, send an email to ><mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com > >Nigel A. Gunn, ><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>1865 >El Camino Drive, Xenia, OH 45385-1115, USA. tel ><tel:(937)%20825-5032>+1 937 825 5032 >Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), >e-mail <mailto:nigel@ngunn.net>nigel(a)ngunn.net >www <http://www.ngunn.net>http://www.ngunn.net >Member of ARRL, QRPARCI #11644, SOC #548, Flying >Pigs QRP Club International #385, >Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. >

2 1

[chirp_users] Answer: where to buy a programming cable for VXt6r
by James Gustanski 14 Feb '18

14 Feb '18

Garnet I have had good luck on on both Mac OS and Windows 10 computers and my VX6r with the cable I purchased from Mark Dunkle KJ6ZWL. His company is BlueMax49ers. Here’s a link to the one you need on Ebay. https://www.ebay.com/itm/FTDI-USB-Programming-Cable-Yaesu-VX-6E-VX-6R-VX-7E… <https://www.ebay.com/itm/FTDI-USB-Programming-Cable-Yaesu-VX-6E-VX-6R-VX-7E…> Cheers and 73 Jim KJ6TRT

3 2

Re: [chirp_users] linux command line
by Tycen Stafford 14 Feb '18

14 Feb '18

Well, that's what I though, but hey look at that... I did just see that command line chirp can do some editing! You can list the settings, list the memory channels, set a memory channel, clear a memory channel and copy a memory channel. So about the only thing you can't do is edit settings. I was only looking for something to upload to the radio so I hadn't paid attention to the rest of the README. I just tired it out on on of my images and it seems to work. From the README page on github: List Settings ------------- For radios that support settings, you can list the current settings in a saved image: chirpc --mmap=<file> --list-settings Show Memory Channels -------------------- You can list all current memory channels in a saved image: chirpc --mmap=<file> --list-mem That command only lists the currently programmed channels. To see the complete list (including empty channels), add '--verbose'. To view only a single channel, use the --get-mem option: chirpc --mmap=<file> --get-mem <channel> Set a Memory Channel -------------------- chirpc --mmap=<file> --set-mem-name=<name> ... <channel> See the --help text for a complete list of options that can be used to configure the channel. Any settings that are not configured using a command option will be left unchanged. Clearing a Memory Channel ------------------------- You can clear a memory channel, discarding all settings: chirpc --mmap=<file> --clear-mem <channel> Copying a Memory Channel ------------------------ You can copy a memory channel: chirpc --mmap=<file> --copy-mem <source_channel> <destination_channel> Note: The contents of <destination_channel> will be overwritten with the contents from <source_channel> On Wed, Feb 14, 2018 at 1:08 PM, David <BearSFO(a)pacbell.net> wrote: > > So, from what you just described, the edits would still need to be done > inside chirp GUI? > > --David > > > At 10:48 AM 2/14/2018, Tycen Stafford wrote: > > Good question. chirp certainly works in a Linux GUI (I've used it on > Ubuntu and it works great!). But as for the command-line, editing is not an > option as documented in the chirp.hg software link I sent. I tried vim'ing > the img file but it looks like it's binary. Quick command-line edits would > be handy though, for sure - although I imagine it would be one of those > things that would be really easy to mess up if you put in the wrong type of > character/data or whitespace. It would probably need a validator command > with it to validate the img file before trying to upload it to your radio. > I think it's one of things where it's not an option because no one's > developed it yet. The user-base would probably be a fraction of the users > who use the GUI so all the time and focus goes to the GUI.Â > > Also, I mentioned that my implementation uses Dropbox to sync the img > files around - you of course use scp or rsync or some other filesync > utility. I just used Dropbox because my radio files were already there and > it was quick and easy to generate a public (yet obscure) URL and just do a > wget. > > On Wed, Feb 14, 2018 at 10:09 AM, David <BearSFO(a)pacbell.net> wrote: > > My linux implementation have no GUI set up, and I just want to be able to > read/write from/to my radios.Â I can certainly edit the file somewhere > else, dump it in, and then run chirp. > > Having said that, is there a reason why it cannot be edited on linux? > > --David > > > At 09:36 AM 2/14/2018, Tycen Stafford wrote: > > Nah, I'd have to disagree, Nigel.Ã‚ I don't need to create/edit radio > config files every time I use chirp, often times I just need to update a > radio with a config I already have.Ã‚ > > It's 100% usable from the command line for me for the scenario I > described. Having the ability to have a pocket-sized headless radio updater > is completely useful for me. I can think of other applications, too - if > you had a dozen (or a hundred) radios that needed the same config applied > repeatedly then you could add a button to that raspberry pi that triggered > the command line update script and update your radios as fast as you could > unplug and plug them from the programming cable (without having to click > through the GUI). They don't all have to be the same radio, either. My > script cycles through my 4 different radio types automatically until it > finds the right one to update. If I were using the GUI I would have to open > 4 different files and click through all the update confirmation dialogs. > With my headless updater I just plug in whatever radio I want updated and > kick off the update command and then wait for it to finish.Ã‚ > > So, I understand that a command line chirp would not be useful to some > (maybe even most), but that doesn't mean it's not usable to others.Ã‚ > > David, what application were you looking for? > > > On Wed, Feb 14, 2018 at 6:18 AM, Nigel A. Gunn G8IFF/W8IFF < > nigel(a)ngunn.net> wrote: If you have to create/edit your radio config > files from the GUI on your desktop then Chirp is not fully usable from the > command line. > > > On 14 February 2018 at 02:51 Tycen Stafford <tycen(a)tycen.com> wrote: Yes, > you can use Chirp on the command line:Ã‚Â https://github.com/tylert/ > chirp.hg > I use a Raspberry Pi Zero W as a headless chirp updater (for my mobile > radio). I keep my chirp files saved in a Dropbox folder with public URLs - > this way I can edit from the GUI on my desktop and then fire up the > Raspberry Pi in the car (using my phone's hotspot feature) so it can pull > the latest chirp images from Dropbox (via wget) and update the radio using > command line chirp. I'm still working on the README but here's my files for > putting it all together:Ã‚Â https://github.com/tycen/chirpi > I just call the updater script from cron on reboot. > -Tycen > > On Tue, Feb 13, 2018 at 5:27 PM, Nigel A. Gunn G8IFF/W8IFF < > nigel(a)ngunn.net> wrote: You can start it from the command line (chirpw) > but it is not usable without a GUI. > > On 13 February 2018 at 20:24 David <BearSFO(a)PacBell.NET> wrote: > > > > > Does chirp works on the linux command line? thanks > > --David > > > _______________________________________________ > chirp_users mailing > list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/ > mailman/listinfo/chirp_users > This message was sent to Nigel Gunn, W8IFF > at nigel(a)ngunn.net > To unsubscribe, send an email to > chirp_users-unsubscribe(a)intrepid.danplanet.com > Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385 > <https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>-1115, > USA. tel +1 937 825 5032 <http://??> Amateur Radio G8IFF W8IFF (was > KC8NHF 9H3GN), e-mail nigel(a)ngunn.net www http://www.ngunn.net Member of > ARRL, QRPARCI #11644, SOC #548, Flying Pigs QRP Club International #385, Ã‚ > Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. ______________________________ > _________________ chirp_users mailing list chirp_users@intrepid. > danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This > message was sent to Tycen at tycen(a)tycen.com To unsubscribe, send an > email to chirp_users-unsubscribe(a)intrepid.danplanet.com > > > _______________________________________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Nigel Gunn, W8IFF at nigel(a)ngunn.net > To unsubscribe, send an email to chirp_users-unsubscribe@ > intrepid.danplanet.com > > Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385 > <https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>-1115, > USA. tel +1 937 825 5032 <(937)%20825-5032> > Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), e-mail nigel(a)ngunn.net www > http://www.ngunn.net > Member of ARRL, QRPARCI #11644, SOC #548, Flying Pigs QRP Club > International #385, > Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. > >

1 0

Re: [chirp_users] linux command line
by David 14 Feb '18

14 Feb '18

So, from what you just described, the edits would still need to be done inside chirp GUI? --David At 10:48 AM 2/14/2018, Tycen Stafford wrote: >Good question. chirp certainly works in a Linux >GUI (I've used it on Ubuntu and it works >great!). But as for the command-line, editing is >not an option as documented in the chirp.hg >software link I sent. I tried vim'ing the img >file but it looks like it's binary. Quick >command-line edits would be handy though, for >sure - although I imagine it would be one of >those things that would be really easy to mess >up if you put in the wrong type of >character/data or whitespace. It would probably >need a validator command with it to validate the >img file before trying to upload it to your >radio. I think it's one of things where it's not >an option because no one's developed it yet. The >user-base would probably be a fraction of the >users who use the GUI so all the time and focus goes to the GUI.Â > >Also, I mentioned that my implementation uses >Dropbox to sync the img files around - you of >course use scp or rsync or some other filesync >utility. I just used Dropbox because my radio >files were already there and it was quick and >easy to generate a public (yet obscure) URL and just do a wget. > >On Wed, Feb 14, 2018 at 10:09 AM, David ><<mailto:BearSFO@pacbell.net>BearSFO(a)pacbell.net> wrote: > >My linux implementation have no GUI set up, and >I just want to be able to read/write from/to my >radios.Â I can certainly edit the file >somewhere else, dump it in, and then run chirp. > >Having said that, is there a reason why it cannot be edited on linux? > >--David > > >At 09:36 AM 2/14/2018, Tycen Stafford wrote: >>Nah, I'd have to disagree, Nigel.Ã I don't >>need to create/edit radio config files every >>time I use chirp, often times I just need to >>update a radio with a config I already have.Ã >> >>It's 100% usable from the command line for me >>for the scenario I described. Having the >>ability to have a pocket-sized headless radio >>updater is completely useful for me. I can >>think of other applications, too - if you had a >>dozen (or a hundred) radios that needed the >>same config applied repeatedly then you could >>add a button to that raspberry pi that >>triggered the command line update script and >>update your radios as fast as you could unplug >>and plug them from the programming cable >>(without having to click through the GUI). They >>don't all have to be the same radio, either. My >>script cycles through my 4 different radio >>types automatically until it finds the right >>one to update. If I were using the GUI I would >>have to open 4 different files and click >>through all the update confirmation dialogs. >>With my headless updater I just plug in >>whatever radio I want updated and kick off the >>update command and then wait for it to finish.Ã >> >>So, I understand that a command line chirp >>would not be useful to some (maybe even most), >>but that doesn't mean it's not usable to others.Ã >> >>David, what application were you looking for? >> >> >>On Wed, Feb 14, 2018 at 6:18 AM, Nigel A. Gunn >>G8IFF/W8IFF <<mailto:nigel@ngunn.net>nigel(a)ngunn.net> wrote: >>If you have to create/edit your radio config >>files from the GUI on your desktop then Chirp >>is not fully usable from the command line. >> >> >>>On 14 February 2018 at 02:51 Tycen Stafford >>><<mailto:tycen@tycen.com>tycen(a)tycen.com> wrote: >>>Yes, you can use Chirp on the command >>>line:ÃÂ >>><https://github.com/tylert/chirp.hg>https://github.com/tylert/chirp.hg >>>I use a Raspberry Pi Zero W as a headless >>>chirp updater (for my mobile radio). I keep my >>>chirp files saved in a Dropbox folder with >>>public URLs - this way I can edit from the GUI >>>on my desktop and then fire up the Raspberry >>>Pi in the car (using my phone's hotspot >>>feature) so it can pull the latest chirp >>>images from Dropbox (via wget) and update the >>>radio using command line chirp. I'm still >>>working on the README but here's my files for >>>putting it all >>>together:ÃÂ <https://github.com/tycen/chirpi>https://github.com/tycen/chirpi >>>I just call the updater script from cron on reboot. >>>-Tycen >>> >>>On Tue, Feb 13, 2018 at 5:27 PM, Nigel A. Gunn >>>G8IFF/W8IFF <<mailto:nigel@ngunn.net>nigel(a)ngunn.net> wrote: >>>You can start it from the command line >>>(chirpw) but it is not usable without a GUI. >>> > On 13 February 2018 at 20:24 David <BearSFO(a)PacBell.NET> wrote: >>> > >>> > >>> > >>> > Does chirp works on the linux command line? thanks >>> > >>> > --David >>> > >>> > _______________________________________________ >>> > chirp_users mailing list >>> > >>> <mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >>> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>> > This message was sent to Nigel Gunn, W8IFF >>> at <mailto:nigel@ngunn.net>nigel(a)ngunn.net >>> > To unsubscribe, send an email to >>> <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com >>>Nigel A. Gunn, >>><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>1865 >>>El Camino Drive, Xenia, OH 45385-1115, USA. tel <http://??>+1 937 825 5032 >>>Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), >>>e-mail <mailto:nigel@ngunn.net>nigel(a)ngunn.net >>>www <http://www.ngunn.net>http://www.ngunn.net >>>Member of ARRL, QRPARCI #11644, SOC #548, >>>Flying Pigs QRP Club International #385, >>>Ã Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. >>>______________________________ _________________ >>>chirp_users mailing list >>><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >>> >>>http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>>This message was sent to Tycen at <mailto:tycen@tycen.com>tycen(a)tycen.com >>>To unsubscribe, send an email to >>><mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com >>> >> >>_______________________________________________ >>chirp_users mailing list >><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >> >>http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>This message was sent to Nigel Gunn, W8IFF at >><mailto:nigel@ngunn.net>nigel(a)ngunn.net >>To unsubscribe, send an email to >><mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com > > >Nigel A. Gunn, ><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>1865 >El Camino Drive, Xenia, OH 45385-1115, USA. tel ><tel:(937)%20825-5032>+1 937 825 5032 >Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), >e-mail <mailto:nigel@ngunn.net>nigel(a)ngunn.net >www <http://www.ngunn.net>http://www.ngunn.net >Member of ARRL, QRPARCI #11644, SOC #548, Flying >Pigs QRP Club International #385, >Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. >

1 0

Re: [chirp_users] linux command line
by Tycen Stafford 14 Feb '18

14 Feb '18

Good question. chirp certainly works in a Linux GUI (I've used it on Ubuntu and it works great!). But as for the command-line, editing is not an option as documented in the chirp.hg software link I sent. I tried vim'ing the img file but it looks like it's binary. Quick command-line edits would be handy though, for sure - although I imagine it would be one of those things that would be really easy to mess up if you put in the wrong type of character/data or whitespace. It would probably need a validator command with it to validate the img file before trying to upload it to your radio. I think it's one of things where it's not an option because no one's developed it yet. The user-base would probably be a fraction of the users who use the GUI so all the time and focus goes to the GUI. Also, I mentioned that my implementation uses Dropbox to sync the img files around - you of course use scp or rsync or some other filesync utility. I just used Dropbox because my radio files were already there and it was quick and easy to generate a public (yet obscure) URL and just do a wget. On Wed, Feb 14, 2018 at 10:09 AM, David <BearSFO(a)pacbell.net> wrote: > > My linux implementation have no GUI set up, and I just want to be able to > read/write from/to my radios. I can certainly edit the file somewhere > else, dump it in, and then run chirp. > > Having said that, is there a reason why it cannot be edited on linux? > > --David > > > At 09:36 AM 2/14/2018, Tycen Stafford wrote: > > Nah, I'd have to disagree, Nigel.Â I don't need to create/edit radio > config files every time I use chirp, often times I just need to update a > radio with a config I already have.Â > > It's 100% usable from the command line for me for the scenario I > described. Having the ability to have a pocket-sized headless radio updater > is completely useful for me. I can think of other applications, too - if > you had a dozen (or a hundred) radios that needed the same config applied > repeatedly then you could add a button to that raspberry pi that triggered > the command line update script and update your radios as fast as you could > unplug and plug them from the programming cable (without having to click > through the GUI). They don't all have to be the same radio, either. My > script cycles through my 4 different radio types automatically until it > finds the right one to update. If I were using the GUI I would have to open > 4 different files and click through all the update confirmation dialogs. > With my headless updater I just plug in whatever radio I want updated and > kick off the update command and then wait for it to finish.Â > > So, I understand that a command line chirp would not be useful to some > (maybe even most), but that doesn't mean it's not usable to others.Â > > David, what application were you looking for? > > > On Wed, Feb 14, 2018 at 6:18 AM, Nigel A. Gunn G8IFF/W8IFF < > nigel(a)ngunn.net> wrote: > > If you have to create/edit your radio config files from the GUI on your > desktop then Chirp is not fully usable from the command line. > > > On 14 February 2018 at 02:51 Tycen Stafford <tycen(a)tycen.com> wrote: > > Yes, you can use Chirp on the command line:Â https://github.com/tylert/ > chirp.hg > > I use a Raspberry Pi Zero W as a headless chirp updater (for my mobile > radio). I keep my chirp files saved in a Dropbox folder with public URLs - > this way I can edit from the GUI on my desktop and then fire up the > Raspberry Pi in the car (using my phone's hotspot feature) so it can pull > the latest chirp images from Dropbox (via wget) and update the radio using > command line chirp. I'm still working on the README but here's my files for > putting it all together:Â https://github.com/tycen/chirpi > > I just call the updater script from cron on reboot. > > -Tycen > > > On Tue, Feb 13, 2018 at 5:27 PM, Nigel A. Gunn G8IFF/W8IFF < > nigel(a)ngunn.net> wrote: > You can start it from the command line (chirpw) but it is not usable > without a GUI. > > > On 13 February 2018 at 20:24 David <BearSFO(a)PacBell.NET> wrote: > > > > > > > > Does chirp works on the linux command line? thanks > > > > --David > > > > _______________________________________________ > > chirp_users mailing list > > chirp_users(a)intrepid.danplanet.com > > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > > This message was sent to Nigel Gunn, W8IFF at nigel(a)ngunn.net > > To unsubscribe, send an email to chirp_users-unsubscribe@ > intrepid.danplanet.com > > Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385 > <https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>-1115, > USA. tel +1 937 825 5032 <http://??> > Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), e-mail nigel(a)ngunn.net www > http://www.ngunn.net > Member of ARRL, QRPARCI #11644, SOC #548, Flying Pigs QRP Club > International #385, > Â Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. > ______________________________ _________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Tycen at tycen(a)tycen.com > To unsubscribe, send an email to chirp_users-unsubscribe@ > intrepid.danplanet.com > > > _______________________________________________ > chirp_users mailing list > chirp_users(a)intrepid.danplanet.com > http://intrepid.danplanet.com/mailman/listinfo/chirp_users > This message was sent to Nigel Gunn, W8IFF at nigel(a)ngunn.net > To unsubscribe, send an email to chirp_users-unsubscribe@ > intrepid.danplanet.com > > > > Nigel A. Gunn, 1865 El Camino Drive, Xenia, OH 45385 > <https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>-1115, > USA. tel +1 937 825 5032 <(937)%20825-5032> > Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), e-mail nigel(a)ngunn.net www > http://www.ngunn.net > Member of ARRL, QRPARCI #11644, SOC #548, Flying Pigs QRP Club > International #385, > Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. > >

1 0

Re: [chirp_users] linux command line
by David 14 Feb '18

14 Feb '18

My linux implementation have no GUI set up, and I just want to be able to read/write from/to my radios. I can certainly edit the file somewhere else, dump it in, and then run chirp. Having said that, is there a reason why it cannot be edited on linux? --David At 09:36 AM 2/14/2018, Tycen Stafford wrote: >Nah, I'd have to disagree, Nigel.Â I don't need >to create/edit radio config files every time I >use chirp, often times I just need to update a >radio with a config I already have.Â > >It's 100% usable from the command line for me >for the scenario I described. Having the ability >to have a pocket-sized headless radio updater is >completely useful for me. I can think of other >applications, too - if you had a dozen (or a >hundred) radios that needed the same config >applied repeatedly then you could add a button >to that raspberry pi that triggered the command >line update script and update your radios as >fast as you could unplug and plug them from the >programming cable (without having to click >through the GUI). They don't all have to be the >same radio, either. My script cycles through my >4 different radio types automatically until it >finds the right one to update. If I were using >the GUI I would have to open 4 different files >and click through all the update confirmation >dialogs. With my headless updater I just plug in >whatever radio I want updated and kick off the >update command and then wait for it to finish.Â > >So, I understand that a command line chirp would >not be useful to some (maybe even most), but >that doesn't mean it's not usable to others.Â > >David, what application were you looking for? > > >On Wed, Feb 14, 2018 at 6:18 AM, Nigel A. Gunn >G8IFF/W8IFF <<mailto:nigel@ngunn.net>nigel(a)ngunn.net> wrote: > >If you have to create/edit your radio config >files from the GUI on your desktop then Chirp is >not fully usable from the command line. > > >>On 14 February 2018 at 02:51 Tycen Stafford >><<mailto:tycen@tycen.com>tycen(a)tycen.com> wrote: >> >>Yes, you can use Chirp on the command >>line:Â <https://github.com/tylert/chirp.hg>https://github.com/tylert/chirp.hg >> >>I use a Raspberry Pi Zero W as a headless chirp >>updater (for my mobile radio). I keep my chirp >>files saved in a Dropbox folder with public >>URLs - this way I can edit from the GUI on my >>desktop and then fire up the Raspberry Pi in >>the car (using my phone's hotspot feature) so >>it can pull the latest chirp images from >>Dropbox (via wget) and update the radio using >>command line chirp. I'm still working on the >>README but here's my files for putting it all >>together:Â <https://github.com/tycen/chirpi>https://github.com/tycen/chirpi >> >>I just call the updater script from cron on reboot. >> >>-Tycen >> >> >>On Tue, Feb 13, 2018 at 5:27 PM, Nigel A. Gunn >>G8IFF/W8IFF <<mailto:nigel@ngunn.net>nigel(a)ngunn.net> wrote: >>You can start it from the command line (chirpw) >>but it is not usable without a GUI. >> >> > On 13 February 2018 at 20:24 David <BearSFO(a)PacBell.NET> wrote: >> > >> > >> > >> > Does chirp works on the linux command line? thanks >> > >> > --David >> > >> > _______________________________________________ >> > chirp_users mailing list >> > >> <mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users >> > This message was sent to Nigel Gunn, W8IFF >> at <mailto:nigel@ngunn.net>nigel(a)ngunn.net >> > To unsubscribe, send an email to >> <mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com >> >>Nigel A. Gunn, >><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>1865 >>El Camino Drive, Xenia, OH 45385-1115, USA. tel +1 937 825 5032 >>Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), >>e-mail <mailto:nigel@ngunn.net>nigel(a)ngunn.net >>www <http://www.ngunn.net>http://www.ngunn.net >>Member of ARRL, QRPARCI #11644, SOC #548, >>Flying Pigs QRP Club International #385, >>Â Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. >>______________________________ _________________ >>chirp_users mailing list >><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >> >>http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>This message was sent to Tycen at <mailto:tycen@tycen.com>tycen(a)tycen.com >>To unsubscribe, send an email to >><mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com >> >> >> >>_______________________________________________ >>chirp_users mailing list >><mailto:chirp_users@intrepid.danplanet.com>chirp_users(a)intrepid.danplanet.com >> >>http://intrepid.danplanet.com/mailman/listinfo/chirp_users >>This message was sent to Nigel Gunn, W8IFF at >><mailto:nigel@ngunn.net>nigel(a)ngunn.net >>To unsubscribe, send an email to >><mailto:chirp_users-unsubscribe@intrepid.danplanet.com>chirp_users-unsubscribe(a)intrepid.danplanet.com > > >Nigel A. Gunn, ><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmai…>1865 >El Camino Drive, Xenia, OH 45385-1115, USA. tel ><tel:(937)%20825-5032>+1 937 825 5032 >Amateur Radio G8IFF W8IFF (was KC8NHF 9H3GN), >e-mail <mailto:nigel@ngunn.net>nigel(a)ngunn.net >www <http://www.ngunn.net>http://www.ngunn.net >Member of ARRL, QRPARCI #11644, SOC #548, Flying >Pigs QRP Club International #385, >Dayton ARA #2128, AMSAT-NA LM-1691, GCARES, EAA382. >

1 0

[chirp_users] linux command line
by David 14 Feb '18

14 Feb '18

Does chirp works on the linux command line? thanks --David

3 4