<div dir="ltr"><div><div><div>Hi Liz<br><br></div>Just looking at all the other stations that VK2RGF-1 have heard this month on <a href="http://aprs.fi" target="_blank">aprs.fi</a> and the all have the path WIDE 1-1, WIDE2-1 or (2-2). Maybe the digi sysop has changed the digi to a WIDE1 digi and therefore your packets are ignored. Also that would explain also why its not repeating packets from other digis.<br><br></div>Cheers<br><br>Dom<br></div>VK2HJ<br><div><div><br><br><br><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 14, 2014 at 6:44 PM, Peter VK2MPJ <span dir="ltr"><<a href="mailto:vk2mpj@yahoo.com.au" target="_blank">vk2mpj@yahoo.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I did forget about the voice interference..<br>
<br>
Do you know if the digi was rebooted, or just the radio? If the Digi has been rebooted, then it is a possibility that there have been changes previously made OTA which have now been lost.<br>
UIDIGI is great in that you can modify the config OTA, but it is not written into the EEPROM, which results in all changes being lost upon reboot.<br>
<br>
Just out of sheer curiosity on my behalf, can you modify your path in your 710 to WIDE 1-1, WIDE 2-1 (or WIDE 2-2, either should work, but 2-1 would be preferable to prevent excessive packets) and see what happens. It may work, or it may not, I am just curious as to what , if anything the Digi will do with such packets.<br>
<br>
I certainly do not think it would be possible for call signs to be in the bud list without some sort of external input. So I do not think that is the issue in this case.<br>
<br>
Pete<div class="HOEnZb"><div class="h5"><br>
<br>
On 14/10/2014 6:34 pm, Liz VK2XSE wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
QTR Tue, 14 Oct 2014 18:14:34 +1100 Peter VK2MPJ QTC<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Liz,<br>
<br>
I have just had a look at the logs available on APRS.fi for RGF-1 and<br>
it has heard at least 7 mobile stations direct over the last month<br>
VK2HLT-8<br>
VK2KAW-9<br>
VK5ATN-8<br>
VK2TRB-9<br>
VK2ACT-8 (Heard Today)<br>
VK4QC-9<br>
VK2KNV-9 (Heard today)<br>
</blockquote>
agreed<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You say that your mobile set up has worked on every other digi you<br>
have passed in the last year, but I wonder have you recently (as in<br>
since you noticed this anomaly)<br>
</blockquote>
which is at least one month, but probably since 21 Aug 14<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
passed any other digis to verify<br>
correct operation.<br>
</blockquote>
Yes, been heard by 2RWG, 2KAW, 2RGI, 3RAW<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What are your current path and beacon settings?<br>
</blockquote>
smart beaconing, standard settings on the Kenwood 710, WIDE 2-2<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It is possible for a digi to ignore an individual call sign, but that<br>
would require that call sign to be added to the "budlist" but this<br>
can only be done by the sysop. It is not something that can randomly<br>
happen without a config change.<br>
But, if you believe it to be ignoring your call sign, have you<br>
attempted to use your mobile set up but with someone elses call<br>
programmed in?<br>
</blockquote>
ready to go this evening with the OM in the vehicle<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
As for why you do not appear to be hearing packets from other Digis,<br>
without seeing the missing packets and their associated paths<br>
</blockquote>
which is an impossibility<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
it is<br>
hard to comment. I have been in discussion with Alan, about the<br>
state of the APRS system in the Riverina. I do not have access to<br>
the digis to have a look at local logs / configs etc. I may see if I<br>
can get access and have a look.<br>
<br>
Without further testing it is hard to speculate as to the root cause.<br>
</blockquote>
Others on this list aren't aware that RGF was actually transmitting<br>
packet over the voice repeater system at the end of last month, so it<br>
hasn't been "well". At that stage it wasn't even transmitting its<br>
idents on 145.175, but after restart I started to hear its idents<br>
again, but no digipeating behaviour.<br>
<br>
I started off asking if the UIDIGI could be capable of misconfiguration<br>
(cosmic rays of course) which would actually put me in the "badlist",<br>
along with all wide area packets.<br>
Is this actually possible?<br>
<br>
<br>
<br>
-+-+-+-+-+-+-+-+-+-+-+<br>
Liz<br>
VK2XSE<br>
______________________________<u></u>_________________<br>
OZAPRS mailing list<br>
<a href="mailto:OZAPRS@aprs.net.au" target="_blank">OZAPRS@aprs.net.au</a><br>
<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" target="_blank">http://lists.aprs.net.au/<u></u>mailman/listinfo/ozaprs</a><br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
OZAPRS mailing list<br>
<a href="mailto:OZAPRS@aprs.net.au" target="_blank">OZAPRS@aprs.net.au</a><br>
<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" target="_blank">http://lists.aprs.net.au/<u></u>mailman/listinfo/ozaprs</a><br>
</div></div></blockquote></div><br></div>