toggle quoted messageShow quoted text
Sounds good, Mark. There are lots of tradeoffs and customization
opportunities, depending on one's circumstances.
KE6BB via groups.io wrote:
Yes, I understand the bottom line, but CPU
and RAM are really inexpensive these days. The way I am set
up, I can use any computer in the house for APRS and/or for
RF. Any combination I want without reconfiguration within the
program. Sadly, I have too many computers.
I just enabled the firenet port on my
tablet, I think it is in the configuration you are
suggesting. In the scroller, I am seeing a lot of stations
scrolling by that are not RF. I tried configuring the
scroller to view RF only, and it helped, but it appeared only
partially effective. Those stations may be from firenet since
I have IS disabled. I will work with it some more, and also
try to filter non-rf at the IS server, but since the firenet
port is not my IS port, I’m not sure how to apply them. I
think filters applied by the configuration menu are applied to
the APRS-IS port only.
I will work on it more tomorrow.
Sent from Mail for Windows 10
bottom line, using two instances only gives a cosmetic
separation of the screen's data, no effect on the traffic or
That's what I was thinking. One instance is less CPU and RAM
consumed, but gives only a single filter to the screen data at
Just another hint, you know you can point both instances to
a single directory and they'll share tiles?
Even when I get MBTiles support finished in APRSIS32,
multiple instances will be able to concurrently share a
tiles database. Not so on Android or under MOAI, but
APRSISCE/32 has the advantage of invoking the SqLite C API
Lynn (D) -
KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 4/30/2020 7:59 PM, KE6BB via
I have done that in the past, and
actually found that configuration on an old Windows 8
(upgraded to Win 10) tablet (Acer W8?) that I have used
for years. I usually run that as an RF only instance
since we don’t really need additional Igates here in
southern California (they don’t hurt anything either), and
it gives me a good view of the RF environment. I know, I
can configure the scroller to see RF only, and the screen,
etc., but I have found separate instances are simply
easier for me to see and use. That old tablet is also
fanless, and 3 of my last 4 computer failures were due to
fan freeze-up. The tablet is too slow and “thermally
challenged” for much of anything else, but APRSIS32 runs
great on it.
The dual instance of APRSIS32 is what I
have settled on, and it works great. You only need one
executable, but you create a shortcut for each instance
using the .exe as the “Target” for both, and different
“Start in” directories. Each instance saves its own
aprsis32.xml in its own target directory. Works great.
Sent from Mail for Windows 10
Um, so I'm running one instance of
APRSIS32, and have both IS and Firenet ports defined.
But the Firenet port doesn't have Transmit enabled, nor
any of the iGate check boxes (RF to IS or IS to RF).
Isn't that effectively the same, but all on one screen?
that you should NOT connect an IGate to firenet. “
just isn’t what it used to be. You just reminded me
WHY I started running separate instances, one for
Amateur Radio APRS, on standard APRS tier 2 servers,
and a second instance for weather watching on
firenet. You also get weather advisories AND warnings
I set this
all up in 2016, so I think I will copy parts of your
message and put it in a file for future reference. My
mind just isn’t what it used to be, or did I mention
Sent from Mail for Windows 10
b/KJ4ERJ-15 will get you my flying satellites as will
o/ISS*/PSAT* (the * is required as they have trailing
spaces. This should work on both APRS-IS and firenet.
b/KJ4ERJ-LS will get you the individual strikes as well
as the strike zones as well o/LS-*/SZ-*. If you only
want the strike zones (a lot fewer objects, but nearly
as informative), just use o/SZ-*. This only works on
firenet. The KJ4ERJ-15 for lightning data is obsolete
and should be ignored.
Note that you should NOT connect an IGate to firenet.
I've been told that firenet's 14580 ports are not
internally flagged as "IGate" ports, so they will NOT
remember what stations you've gated and therefore you
will not receive messages addressed to those stations
nor courtesy posits from the originators of those
If I thought about it hard enough, I could probably
come up with a combination of APRSIS32 instances to pull
off gating nearby strikezone objects from the -IS to RF
without actually using firenet as the IGate connection,
but given their update frequency during a storm, I
really don't think you'd ever want to actually do this.
Lynn (D) - KJ4ERJ - Author of
APRSISCE for Windows Mobile and Win32
4/30/2020 4:52 PM, KE6BB via groups.io wrote:
for the reminder, Fred. I had forgotten about Lynns
lightning server. I noticed that I had -b/KJ4ERJ-LS
in my filters which I changed to b/KJ4ERJ-LS, and it
works! Now I remember that I used the “-“ to turn
the filter off without having to take it clear out
of the Configure menu. That keeps it handy so I can
turn lightning on or off without having to look it
an old message (#29727 dated 10/22/16 in groups.io)
that says to, “…specify a filter of b/KJ4ERJ-15 or
o/LS*…”, but that may be old info. I haven’t tried
either of them recently:
of great job of keeping me from hanging out in bars
all night 😜.
almost the same thing. I also display earthquakes
Release it! It is ready!
I've had 2 instances running most of the day...One
for "normal" APRS traffic (RF & IS), and a
second one for NWS traffic on firenet for weather
(tornado) watching. No problems so far.
love the program! Thank you.
Original message --------
4/29/20 5:38 PM (GMT-08:00)
[APRSISCE] Ready for Release?
So, according to the second
("Upgrades") telemetry graph for KJ4ERJ at
aprs.fi, it appears that the upgrades are slowing
down. So the $20,000
question is: For those of you running the latest
is it ready to be pushed out as the first General
release since 2012?
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows
Mobile and Win32
This email has
been checked for viruses by Avast