[aprssig] New-N Paradigm Works!
Ron Stordahl
ron.stordahl at digikey.com
Fri May 19 11:17:56 EDT 2006
With UIDIGI-ROM firmware you can trap these 8 'calls' using the N=3
configuration example at http://dxspots.com/FIX14439_UIDIGI-ROM.html
WIDE4-4,WIDE5-5,WIDE6-6,WIDE7-7,WIDE5-4,WIDE6-5,WIDE6-4,WIDE7-6 which
unfortunately means that a path of, for example, WIDE7-5 is acceptable.
With the KPC3+ you are limited to just 4 calls.
WIDE4-4,WIDE5-5,WIDE6-6,WIDE7-7 which unfortunately means that a path of
WIDE7-6 is acceptable.
And there are other ways to circumvent the limits with these digi's
which a few minutes of thought will reveal.
I had hoped that Marco Savegnago IW3FQG would have issued a new paradigm
version of UIDIGI so we would not have to make do with half measures,
but so far this has not happened. Ill bring it to his attention again.
But since the bulk of digipeaters are probably KPC3+'s (I am guessing
here....) new code is needed for them as well. It seems unlikely that
will happen. Could someone encourage Kantronics, or would that be hopeless?
I am speculating that one of the PC based digipeaters has been updated
to properly handle the new paradigm, but there is a need for a stand
alone digi to do this. I seem to recall that Scott N1VG is working on one?
If we had digi's that fully implemented the new paradigm users would
have to change or be left in the dark.
Ron Stordahl, N5IN
Richard Montgomery wrote:
> Stan is correct on stations in TX and OK not setup correctly. I get
> stations and digi's from those areas all the time running WIDE5 and
> greater paths. We also get lots of IN and KY stations running WIDE4 or
> greater. I have seen a few Dayton bound travelers this week with RELAY
> and other outdated paths also.
>
> The best email response I got was a digi owner in TX. He said he was
> running his digi unproto path of WIDE5-5 so his mobile stations would
> get out better. Oh well.. I sent a reply back trying to explain but
> never got a response back.
>
> Like Stan, I also keep lots of logs online. I have nearly a years
> worth so far. Just follow these links below. This is from my home
> station, running a j-pole on the corner of my house. I can usually
> hear 3 local digi's direct 95% of the time, so its a fairly good
> indicator of how much traffic is flowing through this area (West TN,
> approx halfway between Memphis and Nashville).
>
> APRS Traffic counter (today's count)
> http://richdea5.no-ip.org
>
> APRS Traffic counter history
> http://richdea5.no-ip.org/usagehistory/
>
> Hope this helps,
> Richard
> KB4YTM
>
>
> Stan - N0YXV wrote:
>> Hope I didn't come of sounding like I wanted to start a war. This is
>> not the North vs. the South all over again. :-) I did mention that I
>> haven't done a real complete investigation but so far _some_ of the
>> KS statations _seem_ to be included. If you want to look at my data a
>> little bit better I have it day by day at
>> http://filter-1.gihams.org/. The "filter" only means that I've
>> excluded several of our local stations from the log to make it easier
>> to "grep" or search through. The "find" function on most browsers
>> works well to find "wide7", "wide6"...etc. The log should reset
>> itself each day so you only get a one day look at a time but you can
>> make a copy of it over several days if you like. Log updates at the
>> top of each hour with the current data of what I've seen in our area.
>> I have about 7 days worth of data archived on the server if you'd
>> like to look through several days I could send you some of those.
>>
>> I'm not sure but if memory serves me correctly some of the WIDE7's
>> are getting through because the first hop is passing them. Therefore
>> the next station in the list which _is_ trapping WIDE7-7 is letting
>> WIDE7-6 go through. Probably should of held of making comments until
>> I've had a real good chance to look through them again. Working 50-60
>> hours a week can mess with your brain a little. :-D
>>
>> ----- Original Message -----
>> *From:* J T <mailto:w0jrt at yahoo.com>
>> *To:* TAPR APRS Mailing List <mailto:aprssig at lists.tapr.org>
>> *Cc:* Brian Short <mailto:kcshorty at gmail.com>
>> *Sent:* Friday, May 19, 2006 6:53 AM
>> *Subject:* Re: [aprssig] New-N Paradigm Works!
>>
>> I'll echo John's comment: Can you identify the Kansas digi's that
>> have bad configurations? The K0SUN network is all upgraded (at
>> least I think it is) but in most cases they are using KPC-3+ TNCs so
>> they will stop WIDE7-7, 6-6, 5-5, and 4-4 if heard directly but
>> won't stop anything with WIDE7-x that start in Texas. I see that a
>> few of the K0SUN-* stations have the paths in their own position
>> report packets screwed up. I'll let the appropriate people know.
>>
>> It appears that KC0PID-7 is not upgraded. It's still using UIFLOOD
>> instead of UITRACE for WIDE.
>>
>> -Jerome, W0JRT
>>
>> */Stan - N0YXV <n0yxv at gihams.org>/* wrote:
>>
>> I haven't done a real study of packets in my area but from what
>> I've seen
>> you have a much larger success rate. While most of what I see in
>> Nebraska is
>> New-N a lot of the WIDE digis's south of me in Kansas, and
>> Oklahoma are not.
>> Small coverage Digi's are more likely to be New-N. I'm getting
>> packets on a
>> regualar basis from Texas that start WIDE7-7 or WIDE5-5. I've
>> emailed
>> several of them but I either get no responce, email bounced
>> (because it's
>> not correct on QRZ) or a lack of understanding of why Texas
>> Packets in
>> Nebraska aren't a good thing. Good news is that I haven't gotten
>> any hate
>> mail back. :-) Oh and by the way several of the Digi's (that
>> I've seen) that
>> have icon's claiming to be New-N Digi's simply aren't New-N.
>>
>>
>>
>> ------------------------------------------------------------------------
>> Yahoo! Messenger with Voice.
>>
>> <http://us.rd.yahoo.com/mail_us/taglines/postman3/*http://us.rd.yahoo.com/evt=39666/*http://messenger.yahoo.com>
>>
>> PC-to-Phone calls for ridiculously low rates.
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at lists.tapr.org
>> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> aprssig mailing list
>> aprssig at lists.tapr.org
>> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
More information about the aprssig
mailing list