[CRAPRS] N0CXX-5

David Peterson peterson.davidc at gmail.com
Wed Nov 21 16:22:29 CST 2012


Regarding your side note, I just saw a few packets scroll by that were
digipeated by K0HAM-9:

Port(inet-text):2012-11-21T22:15:18.830
TEXT:KC9CDS-9>T1TQ7Q,K0HAM-9*,WIDE1*,K0HAM-10*,WIDE2*:`xF*r6`>/'"7-}|!_&''m|!ww"!|3

Port(inet-text):2012-11-21T22:15:39.221
TEXT:AE0TB-5>APOT21,K0HAM-9*,WIDE1*,N0CXX-5*,WIDE2*:!4219.18N/09235.72W#PHG52606/Reinbeck
Digi ae0tb at arrl.net

Port(inet-text):2012-11-21T22:21:15.442
TEXT:W0MG-5>APOT21,K0HAM-9*,WIDE1*,N0CXX-5*,WIDE2*:!4230.82N/09218.13WoWaterloo,
Ia aprs at w0mg.net



Unfortunately I can only receive packets directly from K0HAM-9 about 70% of
the time so I can't independently confirm these.

-David, KC0ALC


--
*David Peterson*



On Wed, Nov 21, 2012 at 4:10 PM, Ron Tonneson <ron.tonneson at gmail.com>wrote:

>  OK, thanks.  Before I gave Charlie the EPROM I tested it here in a TNC-2
> with simulated WX data from a serial port and it worked OK.  Looks like the
> WX connection to the TNC and the baud rate needs to checked.
>
> Ron
>
>
> On 11/21/2012 16:06, David Peterson wrote:
>
> I have been monitoring APRS (RF) all day and have not seen any WX packets
> from N0CXX, just the 146.745-C object, the N0CXX-5 digipeater object and
> the UIDIGI beacon on it's regular schedule.
>
>  The IAn-N path shouldn't impact anything, I-Gates will gate the packets
> just like any other  (Just confirmed it)
>
> 2012-11-21 22:00:11 UTC: *KC0ALC<http://aprs.fi/?c=raw&limit=&call=KC0ALC>
> *>APWW10,IA2-1,qAR,KD0PCP <http://aprs.fi/?c=raw&limit=&call=KD0PCP>
> :@220002h/9<j%7?E{- sTAPRS-IS for Win32, kc0alc at arrl.net WLNK-1
> 2012-11-21 22:00:18 UTC: *KC0ALC<http://aprs.fi/?c=raw&limit=&call=KC0ALC>
> *>APWW10,IA2-1,qAR,KD0PCP <http://aprs.fi/?c=raw&limit=&call=KD0PCP>
> ::WLNK-1   :ack5625
>
>
>
>  -David, KC0ALC
>
> --
> *David Peterson*
>
>
>
> On Wed, Nov 21, 2012 at 3:02 PM, Ron Tonneson <ron.tonneson at gmail.com>wrote:
>
>> Posting from the CRAPRS mailing list:
>> I have been working with Charlie to get WX data on the 112 digi.  In the
>> process we also changed the call to N0CXX-5.  The new EPROM is now in and
>> the digi appears to be OK but I am not seeing any WX data on APRSIS.  There
>> could be a number of reasons for this.
>>
>> I have the WX path set to IA2-2 rather than WIDE2-1.  This is to keep the
>> packets local on RF.  It could be that none of the Igate's used, primarily
>> KD0PCP, are not putting the IA path on the APRSIS system.  The other
>> possibility is that the TNC is just not getting the data from the WX
>> properly.  The WX frame should be coming our every 444 seconds.
>>
>> I cannot hear it direct here in Williamsburg, could someone local capture
>> some data on RF direct to see what it is sending?
>>
>> On another subject K0HAM-9 at Chelsea went down a couple of days ago and
>> I just noticed it today.  I plan a trip over there as soon as I hear from
>> the site owner as to the combination to get in.
>>
>> Ron - K0QVF
>>
>> _______________________________________________
>> CRAPRS mailing list
>> CRAPRS at rf.org
>> https://rf.org/mailman/listinfo/craprs
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rf.org/pipermail/craprs/attachments/20121121/064eb1d7/attachment-0001.html>


More information about the CRAPRS mailing list