: RE: [DSTAR_DIGITAL] Better Idea
Evans,
Here in Denver we use A - 1.2GHz B - 440MHz and C - 144MHz with very
little activity on A currently.
We have asked most users to keep W0CDS G in RPTR 2 so that Dongle and
Gateway users can also connect and join us.
I think about the only way to know the
Evans,
Here in Denver we use A - 1.2GHz B - 440MHz and C - 144MHz with very
little activity on A currently.
We have asked most users to keep W0CDS G in RPTR 2 so that Dongle and
Gateway users can also connect and join us.
I think about the only way to know the activity is
Hey Steve,
and good morning
Take a look at these perl scripts I run here
http://dstargw.kd4efm.org/cgi-perl/gwinfo.pl
http://dstargw.kd4efm.org/cgi-perl/k4wak_gwinfo.pl
http://dstargw.kd4efm.org/cgi-perl/k1xc_gwinfo.pl
As you see I can, from my gateway database, I see various
activities fro
Hi Evans,
There are an A, B, and C repeater in Temple. How do you discern using
the Dstar Calculator (which is a great tool) which of the 3 repeaters
has the most or any activity ? There are a number of Gateway
installations with 2 or 3 modules installed, and only one of the modules
showing
Subject: [DSTAR_DIGITAL] Better Idea
I believe the JA Dstar Repeater folks have a better idea with band
identifier. Using call sign routing, ie., UR=/JP3XYZA the Band
Identifier, 'A' represents the first repeater installed, and 'B' the
second, or at least that is my understanding.
I believe the JA Dstar Repeater folks have a better idea with band
identifier. Using call sign routing, ie., UR=/JP3XYZA the Band
Identifier, 'A' represents the first repeater installed, and 'B' the
second, or at least that is my understanding. You will most likely
find a contact on their 'A' rep
