W6TCP looks like a digi you might be trying to use. I
can't tell if it is listening on 144.390 or not.
Here's what it is listening to on a regular basis.
The graphs of activity make me wonder what's going
This shows even fewer users which makes me think it's
not on 144.390.
WA6ODP-2 looks like it is on 144.390 and hears far
You can see from the graphs that it regularly hears
stations out to 100 miles away.
Here's another look at all the digi users.
If you are trying to use these digipeaters to
support your event, perhaps you can look at placing
digipeaters at these sites on an alternate frequency
temporarily and using that instead.
If it hasn't worked for the past two years and you
are doing nothing to change the way you are operating,
chances are it won't work again this year.
On Wed, May 22, 2019 at
5:52 PM James Ewen <ve6srv@...
the view from an outsider looking in with little
If you are wanting to transmit onto 144.390 from a site
overlooking SAN Fransisco at 4300 feet ASL, you will
need to ignore the input. Easy way to do so is to not
connect a receiver to the APRSISCE/32 instance. Transmit
blind.. You will clobber other stations and make people
mad, but you will never find a quiet time to be able to
If you need to receive information from other stations
and they are on 144.390, then you’re out of luck for
transmitting, unless somehow no one is operating on
An alternate solution is to use a frequency that is not
over saturated and run all operations on that frequency
you will have an empty channel to transmit into, and
will likely find that you have far better success with
hearing other stations in the quiet rather than trying
to pick them out of the noise.
Simple radio concepts that people seem to forget when
they work in digital.
If there’s a pile up on HF, do you try to rag chew with
your buddy overtop of the pile up, or do you look for a
quiet frequency and have a nice chinwag with each other?
You are not locked on 144.390 unless you’re still using
a crystal controlled radio.
On May 22, 2019, at 5:21 PM, 'Michael Wright' mfwright@...
>> Read about PERSIST and SLOTTIME for your TNC to
understand how a KISS TNC determines if the channel is
> I read that this morning, I was wondering if I set
these in config file to zero and Direwolf will transmit
no matter what. At 4300 feet Mt Hamilton overlooks
entire SF bay area plus Monterey bay area and a good
portion of central calif. Last year I tried putting
squelch to maximum but the radio still would not
transmit. At that altitude even an FRS radio will have
> Before I left for work, I fired up my laptop to see
how well it holds up during the day. And appears to do
quite well, I probably should widen times between
beacons and remove telemetry transmissions so not be one
to congest 144.39.
> For this Sunday's Mt Hamilton Classic bike race, I
will not beacon and will not have Ack checked for
messaging. We can always say a brief "got data" by
> thanks, Mike K6MFW
> Posted by: "Michael Wright" <mfwright@...>
> Yahoo Groups Links
> <*> To visit your group on the web, go to:
> <*> Your email settings:
> Individual Email | Traditional
> <*> To change settings online go to:
> (Yahoo! ID required)
> <*> To change settings via email:
> <*> To unsubscribe from this group, send an
> <*> Your use of Yahoo Groups is subject to: