[chirp_users] linux command line

David BearSFO at PacBell.NET
Wed Feb 14 15:33:05 PST 2018


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 at pacbell.net>BearSFO at 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 at pacbell.net>BearSFO at 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 at ngunn.net>nigel at 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 at tycen.com>tycen at 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 at ngunn.net>nigel at 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 at PacBell.NET> wrote:
>>>> >
>>>> >
>>>> >
>>>> > Does chirp works on the linux command line? thanks
>>>> >
>>>> > --David
>>>> >
>>>> > _______________________________________________
>>>> > chirp_users mailing list
>>>> > 
>>>> <mailto:chirp_users at intrepid.danplanet.com>chirp_users at intrepid.danplanet.com
>>>> > http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>> > This message was sent to Nigel Gunn, W8IFF 
>>>> at <mailto:nigel at ngunn.net>nigel at ngunn.net
>>>> > To unsubscribe, send an email to 
>>>> <mailto:chirp_users-unsubscribe at intrepid.danplanet.com>chirp_users-unsubscribe at intrepid.danplanet.com 
>>>>
>>>>Nigel A. Gunn, 
>>>><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmail&source=g>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 at ngunn.net>nigel at 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 at intrepid.danplanet.com>chirp_users at intrepid.danplanet.com 
>>>>
>>>>http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>>This message was sent to Tycen at <mailto:tycen at tycen.com>tycen at tycen.com
>>>>To unsubscribe, send an email to 
>>>><mailto:chirp_users-unsubscribe at intrepid.danplanet.com>chirp_users-unsubscribe at intrepid.danplanet.com 
>>>>
>
>_______________________________________________
>chirp_users mailing list
><mailto:chirp_users at intrepid.danplanet.com>chirp_users at intrepid.danplanet.com
>http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>This message was sent to Nigel Gunn, W8IFF at 
><mailto:nigel at ngunn.net>nigel at ngunn.net
>To unsubscribe, send an email to 
><mailto:chirp_users-unsubscribe at intrepid.danplanet.com>chirp_users-unsubscribe at intrepid.danplanet.com
>
>Nigel A. Gunn, 
><https://maps.google.com/?q=1865+El+Camino+Drive,+Xenia,+OH+45385&entry=gmail&source=g>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 at ngunn.net>nigel at 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_users/attachments/20180214/bd4c081c/attachment-0002.html 


More information about the chirp_users mailing list