<div dir="ltr">There's a very rudimentary ACK and NACK for a message frame built into APRS, makes your D7x0 go beep and flash the screen at you.<div><br></div><div>As Ray has suggested there is no connected mode, this is all UI.</div><div><br></div><div>73</div><div><br></div><div>Matthew</div><div>VK5ZM</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 7 November 2017 at 10:28, Glen English VK1XX <span dir="ltr"><<a href="mailto:glenlist@pacificmedia.com.au" target="_blank">glenlist@pacificmedia.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">agreed<br>
<br>
Like for the person looking at their D700 to see what is going on.<br>
<br>
They almost need a specific download channel. IE outbound only feed with<br>
continuous regional position updates on it.<br>
<br>
Surely all station to station messaging is connected mode ?<br>
<br>
As a single UI message might as well be transmitted into a dummy load.<br>
Or is there a protocol wrapped around UI ?<br>
<span class=""><br>
<br>
<br>
On 7/11/2017 10:52 AM, Matthew Cook wrote:<br>
> One of the downsides of multiple RX only iGates as has been found in<br>
> Adelaide recently is they only benefit internet based observers.<br>
><br>
> You also loose capabilities like two way messaging and create<br>
> confusion as to where users are with internet to RF gateways and delays.<br>
><br>
> There's been a few times recently where users have messaged me over<br>
> APRS in Adelaide that was gated to the net by a RX only iGate that was<br>
> then fired back onto RF, only for my reply to never be received.<br>
><br>
> A well designed Wide2-n network with good coverage and Wide1-n's to<br>
> over come terrain issues sounds like a good plan and a lot of fun.<br>
><br>
> 73<br>
><br>
> Matthew<br>
> VK5ZM<br>
><br>
> On 7 November 2017 at 08:14, Glen English VK1XX<br>
</span>> <<a href="mailto:glenlist@pacificmedia.com.au">glenlist@pacificmedia.com.au</a> <mailto:<a href="mailto:glenlist@pacificmedia.com.au">glenlist@pacificmedia.<wbr>com.au</a>>><br>
<div><div class="h5">> wrote:<br>
><br>
> Hi Ray<br>
><br>
> The stomping is a good point. it's sort of like having a diversity<br>
> receiver. Instead of an RF fade, we have channel contention.<br>
> Actually,<br>
> in theory, multiple I-gate RX around town in a dense area can provide<br>
> an increase in traffic density capability, as the n signals will<br>
> compete<br>
> at different sites and some will win/loose due to terrain<br>
> shielding and<br>
> also flat fading short delay multipath.<br>
><br>
> Since too many I gates is no problem, Ginini will have Igate as<br>
> well as<br>
> RF forwarding. The 50kbps half duplex IP link will carry that no<br>
> problem.<br>
><br>
> Being open source code, we can add / modify as required. Isaacs<br>
> will be<br>
> identical HW eventually.<br>
><br>
> glen<br>
><br>
> On 7/11/2017 8:14 AM, vk2tv wrote:<br>
> ><br>
> > Glen<br>
> ><br>
> > I wasn't thinking of the digi only responding to its real<br>
> callsign, it<br>
> > will do that in any case AFAIK. I was thinking of the case where<br>
> > (local) users specify the digis real callsign in their path to keep<br>
> > their traffic "local".<br>
> ><br>
> > There's a lot of discussion about rgi and possible effects of<br>
> outbound<br>
> > traffic from it but we also need to consider the benefits of<br>
> having a<br>
> > well-sited W2-1 (say) Igate to respond to inbound traffic that might<br>
> > have been stomped on at another system(s).<br>
> ><br>
> > Ray vk2tv<br>
> ><br>
> ><br>
> ><br>
> > On 06/11/17 20:18, Glen English VK1XX wrote:<br>
> >> yeah, I would guess addr, WIDE1-1, VK1RGI-1 would do it<br>
> >><br>
> >> another thing to change on the client .<br>
> >><br>
> >> again, pity more cannot be gleaned by the digi beacon.<br>
> >><br>
> >> alternatively, the system could have a list of locals...<br>
> >><br>
> >> cheers<br>
> >><br>
> >><br>
> >><br>
> >> On 6/11/2017 6:36 PM, vk2tv wrote:<br>
> >>> Doesn't the aprs specification provide for a station to direct<br>
> traffic<br>
> >>> via a specific digi callsign instead of the generic WIDEx-x to<br>
> >>> minimise spread?<br>
> >>><br>
> >>> Ray vk2tv<br>
> >>><br>
> >>><br>
> >>> On 06/11/17 18:03, Glen English VK1XX wrote:<br>
> >>>> All<br>
> >>>><br>
> >>>> thanks Josh,Ian, Dom, Ray for the inputs, and asking me good<br>
> questions<br>
> >>>> for me to think about.<br>
> >>>><br>
> >>>> I'll read a bit more into USA centric & written articles.<br>
> >>>><br>
> >>>> I think I will filter 1RBM (local cbr) and 1RGI from duplicating<br>
> >>>> everything. Or at least have a think about it. There really<br>
> needs to be<br>
> >>>> a setup for users if they really do want 1RGI is digipeat<br>
> their 1RBM<br>
> >>>> UIs. I guess that's what WIDE2-2 is for.<br>
> >>>><br>
> >>>> Also got to think of the reverse case... RBM hearing things<br>
> that I<br>
> >>>> expect Ginini to hear and not . That of course can happen any<br>
> time for a<br>
> >>>> mobile station, long and short delay multipath abundant.<br>
> >>>><br>
> >>>> In about 90% of canberra cases, 1RGI will hear whatever 1RBM<br>
> hears no<br>
> >>>> problem...<br>
> >>>><br>
> >>>> There there is the providing redundancy issue for other<br>
> paths. Ether<br>
> >>>> way, IP link and full control will make things flexible.<br>
> >>>><br>
> >>>> There's a double edge sword with terminals being dumb /simple<br>
> and say<br>
> >>>> unable to update their paths based on whatever they are<br>
> hearing- there<br>
> >>>> would be usefulness I would have thought in having the digi<br>
> beacon spit<br>
> >>>> out some useful information for UI stations.... or maybe<br>
> there has been<br>
> >>>> thought and it didnt catch on.<br>
> >>>><br>
> >>>> I'll put UHF on the second sound card/dire wolf TNC channel,<br>
> that will<br>
> >>>> be useful.<br>
> >>>><br>
> >>>> -glen<br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>> ______________________________<wbr>_________________<br>
> >>>> OZAPRS mailing list<br>
</div></div>> >>>> <a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a> <mailto:<a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>><br>
> >>>> <a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
<span class="">> <<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a>><br>
> >>><br>
> >>> ______________________________<wbr>_________________<br>
> >>> OZAPRS mailing list<br>
</span>> >>> <a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a> <mailto:<a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>><br>
> >>> <a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
<span class="">> <<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a>><br>
> >> ______________________________<wbr>_________________<br>
> >> OZAPRS mailing list<br>
</span>> >> <a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a> <mailto:<a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>><br>
> >> <a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
<span class="">> <<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a>><br>
> ><br>
> ><br>
> ><br>
> > ______________________________<wbr>_________________<br>
> > OZAPRS mailing list<br>
</span>> > <a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a> <mailto:<a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>><br>
> > <a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
<span class="">> <<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a>><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> OZAPRS mailing list<br>
</span>> <a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a> <mailto:<a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>><br>
> <a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
<div class="HOEnZb"><div class="h5">> <<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a>><br>
><br>
><br>
><br>
><br>
> ______________________________<wbr>_________________<br>
> OZAPRS mailing list<br>
> <a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a><br>
> <a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
OZAPRS mailing list<br>
<a href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a><br>
<a href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel="noreferrer" target="_blank">http://lists.aprs.net.au/<wbr>mailman/listinfo/ozaprs</a><br>
</div></div></blockquote></div><br></div>