Hi all,
As part of the transition to the new domain name, I'll be moving this list to a
new server hosted under the new domain name. As with the website, this should
have happened a long time ago, but alas ... better late than never.
The new email address to post to the list is:
> It looks like it reset the list. For me, it will after you've selected a
> file.
I recently re-wrote the algorithm that manages that list to try to make it
smarter and avoid the duplicates it likes to collect. I intended to preserve
the current list, but maybe that wasn't as successful in
> Is there a plan to update the rpttool to work with Python3 like the rest of
> Chirp? I see it hasn't been updated in a while and I am looking to use it
> with a ID-RP2000V Repeater.
I haven't used that since 2009 when I first wrote it for myself. It's been
broken long before python3 even
> This is my experience so far with CHIRP and the TM-D700A radio. The radio
> receives input from CHIRP in Live mode, with changes being in near real-time
> on the control head. Turning the radio off and on and then re-downloading the
> memory slots displays what was entered previously (of
> Additionally, I do see within the Info tab, on the Features page that the
> has_bank and has_bank_index options are set to False. Could this be related
> to the absence of the Banks tab?
Yeah, this driver doesn't implement the bank functionality, which is why
has_bank is false (and thus no
> Nothing that needs to be coded.
> A radio that is "manufactured" by 'My Emergency Radio' and available from
> prepping suppliers is actually a rebadged TYT TH-UV88 and programs fine as
> such.
> Perhaps can be added to the supported radios list.
Submit an issue and provide some links to the
Hi all,
After almost 16 years as a subdomain on my personal one, CHIRP has a proper
domain name of it's own:
https://chirpmyradio.com
This has been on my todo list for quite some time, but it has always been lower
priority than other things and it just kept slipping. Once the first decade
> Dan, you identified the problem for me. I had the radio in TNC PKT mode,
> looked up in the manual how to take it out of that mode and Chirp promptly
> populated. It did click my Flex PTT, but as you said, that was momentary
> with no ill effect. I was already using the cable I got from
> The cable I have ends in a female DB9 and physically connects to the radio
> fine.
Right, but the physical connection isn't enough - the port on the D700 is not
wired like a normal serial device intended to connect to a PC, which is the
problem.
> One thing I observed was when I entered the
> I have the Kenwood TM-D700A powered on and connected to my computer via a
> BlueMax49ers FTDI cable. Chirp correctly identifies the COM port confirmed as
> the FTDI cable in Device Manager. The Radio à Download from Radio menu
> selection opens the popup with the COM port, make, and model
> See attached image file
I see no attached img, either to the issue or this email. Please do NOT send it
to the list here, but attach it to your issue.
> - what is the purpose of the export to cvs if it is not needed?
Export to CSV is a way to get data out of CHIRP if you want to edit it
> Hi Ken, I download from the radio to chirp and then export it to a cvs file,
> make changes, modifications, additions, etc. and then import it back into
> chirp and upload into the radio. Although I am fairly new, that is how I
> understand it is supposed to work. As I mentioned, I get an
Hi Terry,
> When I try to export to a cvs file I get the error message "Tx freq 0.00
> is out of supported range", any help would be appreciated, I am considering
> send it back if I cannot program with CHIRP. Thanks - your hard work is
> appreciated!
We really can't help you here with so
> It has been my impression that Yaesu isn't exactly forthcoming about the
> programming details of their radios, so it isn't especially surprising that
> the digital modes haven't been reverse-engineered.
This is true, but also true of 99% of all the radios supported by CHIRP.
They're almost
> Doesn't program digital functions on an FT-70. Doesn't even ack that digital
> mode exists.
Yep, the FT-70 driver author has been kinda MIA for a while, and there are
issues stacking up for that radio, including these two specifically calling out
missing DN mode:
> I will probably get rocks and sticks thrown at me but I sure wish Chirp
> supported some of the common
> lower end DMR radios.
Nah Chuck, no rocks, Maybe a few sticks :) You're certainly not the first
person to ask about it.
CHIRP supports something crazy like more than 400 models and it
> According to what I found on the Baofeng website, the BF1909 is a DMR radio.
> CHIRP does not support any digital radio models.
Please be careful making authoritative-sounding statements like this to such a
wide audience. I think you meant to say "CHIRP does not support any DMR radios"
and
Guys, I love bashing on my least-favorite band (Yaesu) myself, but we're pretty
far off-topic here. Let's please respect the thousands of people who subscribed
to hear about CHIRP stuff and take this somewhere else.
(tell me where and maybe I'll follow you to throw some punches! :P)
--Dan
>
Hi all,
Today, one time only, an extra-special two-for-one sale on builds!
Thankfully a user filed bug 11198 quickly identifying a silly mistake with the
recent file handling re-work which would prevent new users from running chirp
for the first time. So, the 20240224 build was regenerated
> I suppose that could be a misprint in the Icom user's manual (one or the
> other) although that seems unlikely.
All the Icom (not just the CI-V) radios we support use the same low-level
transport, which means none of them have transposed addresses. I can't imagine
the 746Pro is an oddball in
> Thanks, Dan. That didn't work either. You mean 56h (hex) or 0x56, right?
Yes.
> When downloading from the radio, the channel numbers appear highlighted
> in red with an exclamation point ahead of each one, presumably denoting
> an error. Nothing appears in the rest of the spreadsheet.
>
> I did verify that CI-V is turned on in the radio and the address is set
> to 0x66. (Speaking of which, how do I set the address in Chirp? Maybe
> that's the problem...)
You can't change the CI-V address in CHIRP, you'll have to set it in the radio.
The CHIRP driver expects the 746 to be at
Hi Jacob,
This is a users list, and there are over 2000 people who are looking for usage
content and not stuff like this. Please, let's take this to the chirp_devel
list if you want to discuss further.
> Looking closely at the channel information starting at offset 0x4000, by my
> math each
> Getting an error message saying that I don't have the right drivers (?)
In addition to what Jim said, there's not really any error message chirp will
tell you that is even close to "don't have the right drivers." Please show a
screenshot and/or provide more detail so we can try to help you.
> Unfortunately it seems that flashing the unit causes some kind of strange
> problem with squelch.
I can't help with your issue, but I would like to point out that chirp doesn't
"flash" any radio. I assume you mean "program" instead of "flash" but to the
developers there's a huge difference.
> Just out if curiosity, has Chirp-legacy reached s complete End of Lifecycle
> and there will never be anything past chirp-legacy-20221217? I’ve migrated,
> for the most part, to Chirp-Next, but still occasionally use legacy and just
> was curious.
Yep, I should probably refresh some of the
> Wow, that's horrible.
Yep, they look fine to me and others, as Ken notes.
Before we get into a religious war about Rich's 20-year-old mail client, let's
please go ahead and take this off-list. The 2000+ people subscribed here are
looking for CHIRP discussion and not any more about this
> I'm not a CHIRP developer, I merely pointed out that they appear to
> discourage using CSV files, implying that fixing that facility may be a low
> priority issue for the team...
No, we do not discourage them, and fixing CSV issues is a priority (for me at
least) for sure. Jim and others'
Hi Chris,
> anybody on the list active in programming and can tell me, how to get
> information aboput data structures and communication protocol on serial
> tty, to understand what is happening?
>
> I want to modify code to add support for anytone at and have no
> idea how to get it.
>
>
> It seems to me this is likely something with the .python driver for this
> particular radio
Yep, please file a bug. There's another person I know of who has been
successfully using a DR235 with CHIRP-next recently, so I'm surprised you're
having trouble, but a bug and debug log will tell us.
> Dan - This is the error when trying to install today's next on a 32 bit Win
> 10 system.
Perfect, thanks for the confirmation!
--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
> the 32 bit zip file works all the time for me, and doesn't need to be
> installed. Just unzip and run.
Since this has come up a few times now and people are quite confused, I just
wanted to clarify:
There is *no* 32-bit Windows version of CHIRP-next, and there hasn't been since
we started
> No, Marc, it's not necessicarily a PC issue. We don't know yet, because when
> he responds he has yet to give us the Type of Windows 10 he is running.
The installer is 32-bit and will run just fine on even a pretty old machine
(32-bit and Windows XP), so there's really nothing about his
> hi, help me . a very espert on CHIRP Next program ?
> the two BIG problems with my handy Kenwood TH-F7 are :
> - I connect the radio, download the all Memory change and modify then
> ... at the end , NOT appare in the menu the UPLOAD , why this ?
> - in the menu in SAVE or
> I am still using the last legacy version of Chirp. I just acquired a Talkpod
> A36+ but can't find how to program it manually and hooking it up to Chirp can
> not talk to the radio but Talkpod is not in the list. I tried Baofeng UV5R
> but that did not work. Has anyone else programmed the
> I didn’t see a place for me to add a comment to ticket 10744 below so adding
> my answers.
You need to be signed in, and just click the edit link at the top right. I'll
dig into this a bit based on your data, but progress will be reported in the
bug there and I'll post a driver module there
> I’ve scanned several monthly archives for "FT-65" and separately for
> “upload”. The only reports I can find is that users are trying to upload a
> CSV tab (a common problem) and not the tab downloaded from the radio. I’ve
> added my channels to the FT-65 download tab and still no joy
> I completely re programmed all my channels. I want to print the list. I can
> get the page preview just fine. But when it goes to print, an image flashes
> on screen and disappeared. I can't see what the image is.
Sounds like a bug, but it's hard to say why. Can you open a bug and attach
> How specifically does chirp decide? For example, if I changed any of the
> files...and I don't really see that happening...the timestamp would change.
It calculates a cryptographic hash of the file contents to decide if they match
the hash of the source. It should be basically infallible for
> I changed my
> [prefs]
> stock_configs = E:\@online docs\Amateur Radio\CHIRP stock_configs
> as a test.
>
> ?? Something I did yesterday during my testing and installing the latest
> standalone version emptied out my custom stock_configs dir (or I did it by
> mistake) and cleared the [prefs]
Hi all,
I posted another "CHIRP Tips" video, this time on advanced editing techniques.
This covers a number of tools CHIRP provides for bulk editing, organizing, and
arranging memories.
https://youtu.be/9UgJjwaXlrY
Hopefully there's at least one tip in there you didn't already know about!
> It believe it would be useful for both Windows and Linux versions to be able
> to define a custom path for stock config files.
>
> I use Nextcloud extensively and I created a folder for configurations for all
> sorts of programs, Filezilla xml site definitions, mRemoteNG xml, etc. This
>
Hi Rich,
> 1. With both the installed and standalone, files can be saved anywhere, and
> don't need to be saved in %appdata%...I keep mine in radio-specific dirs,
> along with other files and docs pertaining to each radio. This includes radio
> image files saved by other programs, such as
Hi all,
There is a lot of useful content out on youtube that provides step-by-step
instructions for some general workflows with CHIRP. However, there are a lot of
other things you can do with CHIRP that never seem to get covered. Lately as I
have helped people adjust to some of the things that
> Okay, I thought I read somewhere it was recommended to post here first. Will
> do that.
Fair enough. Usage questions here, bugs there :)
> I did post a link to my debug log for the 92AD in my first post - at least,
> the file created when I ran 'chirp --log'. I don't have a 'debug.log'
> Anyone have thoughts or suggestions to try?
Yes: please fill out a bug report with a debug log, per these instructions:
https://chirp.danplanet.com/projects/chirp/wiki/How_to_report_issues
Describing the issues sounds nice, but the meat needed to actually see what is
wrong and do something
> I have one image from the KT-2140 where the memories are divided into 3
> Groups, when I want to program the radio from blank, how do I create Groups,
> cannot find any buttons or instructions.
Are you asking about the Kenwood TK-2140? Your subject and message say KT
instead of TK.
This
> Absent any first-hand experience, I think I'll try manual programming for
> local repeaters, and if that gets too tedious, I'll just order the
> BlueMax49ers cable.
I don't have first-hand experience, but I can offer second-hand experience
recently. When converting the ft90 driver for
> But the instructions as written, do not work for Ubuntu 23.04 (Lunar Lobster).
> Now, I do realize that 23.04 is not an LTS (long-term-support) version of
> Ubuntu, so it may have its quirks.
It's not just that, it's that as of 23.04, the way python applications are (or
can be) installed in a
> Yeah, sorry. I was in too much of a hurry. After I read the instructions I
> submitted a proper bug report.
Thanks, there are too many variables in play without a debug log to show the
details.
I was able to reproduce and will have a fix for tomorrow.
--Dan
Hi Michael,
> I'd like to report an issue with the program where the row height in the
> memory display is not sticky when the font size
> is changed to large font. If the large font is set and the program is exited,
> when reopened the larger font is displayed in the narrow height, cutting off
> The Windows Device Manager (you may need to open the Control Panel and search
> for that item) will give you a handy list of COM ports. Bring up Device
> Manager, note the COM ports listed, plug the cable in, refresh the DM display
> if needed, and you should see it, either under COM ports or
> On May 9, 2023, at 4:20 PM, Jerry Rector - K4OAM wrote:
>
> OK Dan -
>
> Here'tis:
>
> PIP STDOUT
> --
>
> PIP STDERR
> --
> ERROR: Could not find a version that satisfies the requirement
> chirp-20230507-py3-none-any-whl (from versions: none)
> ERROR: No matching
> I DID send details via a screenshot and error-log contents, but that
> message was rejected by the site moderator, with no reason given
> for the rejection of the reply.
Likely because of its size. There are over 2000 people on this list and sending
an image to all of them is a huge amount of
> Same problem here - will not install on 23.04 as written:
>
> $ sudo apt install git python3-wxgtk4.0 python3-serial python3-six
> python3-future python3-requests python3-pip pipx
> cd into_the_directory_with_the_whl_file_I_downloaded
> $ pipx install --system-site-packages
> I have a question. I just pulled from git. I didn't see that whl file.
> Is there a different way to install when pulling from git?
The wheel is built during the build process, so you can find them here:
https://trac.chirp.danplanet.com/chirp_next/next-20230425/
Just FYI, installing from git
> Is this a new install or an upgrade.?
>
> If an upgrade you should be able to do 'pip install --upgrade
> /path/to/chirp-20230425.tar.gz' and it should work.
> If a new install then Dan's comment above applies.
>
> If, by chance, you did an original install as a system-wide install using
>
> Any ideas?
Those instructions are not updated for 23.04, which (along with upstream
python) has fundamentally changed how installing python packages works. You can
look at this bug for more details:
https://chirp.danplanet.com/issues/10541
I have on my todo list to update that with
> I don't like the bug tracking system. Dan closed the ticket without allowing
> any further discussion or addition of additional evidence and I find it rude
> and frustrating. github.com and other issue tracking systems allow comments
> even after an issue is closed without changing the status
Hi Jonathan,
> I'd like to report some issues with the KG-UV9D Mate support.
> I have debugged some channel memory loading issues and would like to report
> my findings and suggested changes. I can report what works for my scenario
> but of course you may have more information about previously
> OK Chip, that's good to know in case I have to revert back to
> the snap-installed version.
The snap and flatpak were largely created for legacy chirp because the distros
were removing the underlying platform that we had to use, and those formats
provided us a way to bundle them. There are
> It would be nice if detailed instructions for Fedora and rpm based distros
> were included since the site only shows how to do an install on Ubuntu.
> Package names are not the same and several necessary dependencies are not
> listed.
It would be nice if users of other distros would
> Strange, I don't remember needing to do that for my FT-65. I did have a
> Yaesu cable for it and am using Ubuntu so no driver silliness.
The FT-4 derived radios (of which the FT-65 is) may be different in this
regard, as they are very different than typical Yaesus in general (and I think
> Try just turning it on without going into clone mode. Then tell chirp to
> connect. If the radio is supported by chirp and your drivers are correct it
> should connect.
No, that's not how Yaesu radios work. They have to be in clone mode and they
require the user to do a coordinated dance
> I have often wondered about the name. I sent a message to that web page
> developer. I appreciate Jim being able to post. I am still left wondering why
> it was named that...I continue to hope that someone will step up with real
> history, as trivial as this subject is...if Jim's stuff goes
> Sorry for the delay, Dan. I have used Chirp-next on the IC-7100 a few
> times now. I havnt seen any abnormal behaviour so afaic its a tick in
> the working box for the Icom IC-7100.
Excellent, thanks I'll get it marked off.
> I had a silly idea the other day,
> while the IC-7100 cannot be
> I'm using Win10 and Avast Antivirus (obviously). I'm guessing it's a false
> positive, but what other information do you need?
Yep, it's a false positive, as they all are. The builds are all sandboxed from
a fixed starting snapshot so the differences day to day are incredibly minor :)
--Dan
> Is there anything here I should file a bug report on, or am I just
> experiencing growing pains ? ;-)
All of it! It's difficult for anyone here to provide support for these kinds of
unexpected probably-not-usage-related issues. We need images, debug logs and
some back and forth. The bug
> I understand the LIVE reminder when reading the IC-7100 memory banks
> into Chirp, but how do I load a data file to program the damn thing?.
> Either I'm thick or I'm missing something, or both !
Open the data file and the radio at the same time. Then copy and paste the
memories you want
>> I was using a tidradio bluetooth programming adaptor and after programming
>> the scan feature stopped working and the programmed channels wouldn't
>> program and a lot of other issues that I assume come with a bricked radio. I
>> tried resetting both radios from the menu but it didn't help.
> It worked(chirp next-20230130), or better half worked. Worked the first time,
> but know the Radio does not show -pcp- anymore and I get an error; Error
> downloading from radio
Well, as I mentioned, a bug with a debug log is the next step. There's really
nothing anyone on the list can do
> Please advise if this is an easy fix and I will generate a bug report.
Easy or not, the appropriate place for this is a bug report, yep. I suspect the
the person that wrote the ID-80 driver didn't cover all the modes and the full
limits of the bands. If you can attach debug logs and images
> I have kenwood tk-768(n) and I use ch340 module (Prolific USB to Serial,
> Driver details; ser2pl64 (version 3.6.81.357) serenum.sys (version
> 10.0.22621.1)) I use chirp (daily-20221217) but doesn't read from radio. On
> the lcd appear -pc- and than it stays there. On the PC an error;
> Thank you Dan, the fix works exactly as expected.
Glad to hear it, thanks!
--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to
> Am I missing something on how to edit the index numbers?
Yes, you're missing the step where you click on the index in the GUI and change
it to something sensible. However, your query made me realize that this was
broken back in December and nobody noticed until now! I imagine maybe you
> After a seemingly successful Buster 64 buil and install,
> all seems OK, but I have the following in the terminal
> window:
>
> (chirp:9399): Gtk-CRITICAL **: 14:30:16.961:
> gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
>
> Is this a concern? If yes, how to fix it?
> Query RepeaterBook - Limit Band option only lists the 10m band.
> Am I missing something obvious? If not I can investigate further.
I build the list by looking at the bandplan and including any whole bands that
are named "XX Meter Band" above 27MHz. So look at your bandplan object and
either
> Was just going to open a new issue, but looks like you’ve already beat me to
> it.
> Do you want me to add any additional information to the ticket as you sort of
> already know the wxPython version is the issue?
I was able to reproduce it so I figured I'd just open it since nobody else had
> I am using Mint 20.02 based on Ubuntu 20.04 and had the same issue with old
> wxPython. I used this to successfully update wxPython and resolve the issue.
>
> pip3 install -U -f
> https://extras.wxpython.org/wxPython4/extras/linux/gtk3/ubuntu-20.04 wxPython
This will work for x86_64
> Please confirm this is in CHIRP Next?
CHIRP-next only yep!
--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to arch...@mail-archive.com at
> Chirp about info is: CHIRP-next-20230115 on Python 3.10.6 wxPython 4.0.7 gtk3
> (phoenix) Wxwidget 3.0.5
>
> Any help?
This is the same issue Lynda faced, and is likely because your wxPython is
older than what we're using in the bundled builds. Someone please file a bug
and I'll add an
Hi all,
In continuing this weekend's RepeaterBook theme, I wanted to point out that
today's build contains support for RepeaterBook's worldwide directory, That
means the list of countries in the drop-down box has gone from three to over a
hundred, with hundreds of repeaters listed for many
> (chirp:2413): Gtk-CRITICAL **: 04:58:49.028:
> gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
> ERROR: raised unexpected
> exception
> Traceback (most recent call last):
> File "/home/pi/.local/lib/python3.7/site-packages/chirp/wxui/common.py",
> line 448, in
> Silly me again Dan, sorry to have bothered you.
No worries, I was wondering where you got that old tarball until I realized it
was the oldest build dir. We can blame Rich NE1EE for *forcing* me to reverse
the sort in that directory. Just kidding Rich, it was the right call :)
So you're good
> :~/Downloads$ pip3 install chirp-py3-20221124.tar.gz
This is insanely old (in chirp-next time frames). You should be using the
latest from here:
https://trac.chirp.danplanet.com/chirp_next/
Looks like you're going to the bottom to get the first, but that's the oldest.
Purge again and get
> I did have an old version that I removed with apt and I did have a a
> flatpak version that I think I had removed some time ago. I'll check.
The flatpak would be completely isolated from this, so that's not related. And
definitely no apt package was going to be installing that super old
> I believe that I have all of the required dependencies installed but
> perhaps I've missed something.
>
> :~/.local/bin$ ./chirp
> Traceback (most recent call last):
> File "/home/phil/.local/bin/./chirp", line 33, in
> sys.exit(load_entry_point('chirp===py3-20221124',
This looks like
> Dan, dont you mean 'pip3 install'.
It depends on the system, but if you have a pip3, then yes.
> It ran ok but with the warnings below. I have no idea where is put the
> files though. I cannot see them in my 'home' directory tree.
>
> WARNING: Built wheel for chirp is invalid: Metadata 1.2
> Any answers to this request?. I'm seeking elucidation too ! 73 Mike
Try this:
$ sudo apt install git python3-wxgtk4.0 python3-serial python3-six
python3-future python3-requests python3-pip
Then grab the tarball and run "pip install" on the tarball. Let me know if that
works on the pi and
> I switched to chirp-next and I installed it with success in Linux Mint 'Vera'
> (21.1) and Debian 10 by downloading tar.gz file running sutup.
>
> The only question I have now is: how to update my installation wthi the new
> daily releases? Is it ok download the new version running, for this
> I believe others already have, at least two or three times looking at
> the bug tracker, many of which have patches. I didn't want to clutter
> it with duplicates.
>
> https://chirp.danplanet.com/projects/chirp/search?utf8=%E2%9C%93==1=DJ-G7T
Fair enough. I've never taken patches through the
> How far below "file" is "import"? I don't see it. I see "open" --
> this lets me open a CSV file, but won't let me load it into a radio.
There is no File->Import in chirp-next. Glenn is thinking about chirp-legacy.
--Dan
___
chirp_users mailing
> To even get Chirp to talk to the Alinco, I needed to patch it (I think
> this will preclude me using a pre-made "binary"):
>
> diff --git a/chirp/drivers/alinco.py b/chirp/drivers/alinco.py
> index 7bfffa39..b3350653 100644
> --- a/chirp/drivers/alinco.py
> +++ b/chirp/drivers/alinco.py
> @@
> Since you've brought up Yaesu & System Fusion... I have an FTM-400 that I
> love. (Though I haven't set it up since I moved about 6 months ago).
> Has any work been done on supporting the FTM-400 in chirp? Is it technically
> possible?
I haven't done any work but it looks like there are
> I have a 7250, so if you get YSF support for that radio, I’d be happy to test
> it!
Have you tested it at all with CHIRP? There's a bug report open that makes the
driver look super broken, but I'm wondering if it's a firmware version issue:
https://chirp.danplanet.com/issues/10251
I'd love
> [3046399+kk7ds] Add DN to mode list for Yaesu System Fusion
>
> [3046399+kk7ds] Make RepeaterBook return YSF (DN mode) repeaters
>
> [3046399+kk7ds] Add DN mode support to FT1, FT2, FT3
I'm not sure if anyone noticed this, but these are the first radios to have any
sort of Yaesu System
> I was just doing some work on my image file for a Yaesu FT-60R. I was
> assigning memories to banks, and I somehow got multiple rows in the table
> highlighted. I think I may have clicked and dragged slightly to cause this.
>
> I can not un-highlight the rows, nor do I see the point of
> Chirp doesn't recognise ANY digital repeaters and doesn't program the digital
> side of any radio.
CHIRP has supported D-STAR radios (including repeater configs) since 2008.
--Dan
___
chirp_users mailing list
chirp_users@intrepid.danplanet.com
> The check all or none selection mostly for lazy bulk selection or
> deselection. As for why I would have a selection , where I live and the
> place I’ve been traveling to tends to have a large variety of different
> bands. In the San Francisco bay area, there’s lot to pick through for
>
> My apologies, I actually meant to say RepeaterBook. Not sure what sort of
> brain dyslexia cause me to mixed the two up.
> But I guess this filter is a new feature added in the newer build . Prior
> which I think only had a latitude and longitude boxes.
> The new filters are pretty nice,
1 - 100 of 112 matches
Mail list logo
