Google Groups

Re: [aprsfi] Packet path and line draw


OK1ALX May 16, 2012 11:14 PM
Posted in group: aprs.fi
Hi

> Well, as I said earlier (quoted below), "I'll see what I can do to fix
> that". :)
Alright, looking forward :)

I'll write tou an email about the Prague visit.

Regards,
Libor, OK1ALX

On Wednesday, May 16, 2012 8:04:30 PM UTC+2, Heikki Hannikainen wrote:
On Sat, 12 May 2012, OK1ALX wrote:

> Ok, so it looks like this has no solution, right? :)

Well, as I said earlier (quoted below), "I'll see what I can do to fix
that". :)

How about I come to Prague to discuss this in more detail on Saturday
evening, perhaps over a beer? Sunday is busy, and so is monday (scheduled
a meeting with the giraffes).

> Dne středa, 9. května 2012 10:54:55 UTC+2 Heikki Hannikainen napsal(a):
>
>       That's a completely different thing, there are variations in the monitor
>       format. Some TNCs show a star on each used path component, some TNCs show
>       a star on all used path component, and the first thing aprs.fi does (when
>       decoding that) is adding the star on all components before the one with
>       the star.
>
>       On Wed, 9 May 2012, OK1ALX wrote:
>
>       > Hi
>       >
>       > When you say that, i can see it now. The rf monitor on Digi_Ned console shows
>       > the star next to the digipeater calsigns whis has digipeated. But if i look in
>       > the rf monitor on UI-View with TNC connected directly, then i see star only at
>       > last element in digipeated path. But if i connect UI-View through the AGW PE,
>       > then i can see the stars at every element which has digipeated.
>       > Which is kind of strange, it means that there are different softwares, with
>       > different handling? Thats weird.
>       >
>       > If you don't get this information correct through APRS-IS, then i can
>       > understand you cannot process the code correctly. :-(
>       >
>       >
>       > Anyway, you will be welcome in Prague and if you'll have a spare time, we
>       > could meet if you like.
>       >
>       >
>       > Libor, OK1ALX
>       >
>       >
>       > Dne středa, 9. května 2012 9:25:55 UTC+2 Heikki Hannikainen napsal(a):
>       >
>       >       Hi,
>       >
>       >       On Tue, 8 May 2012, OK1ALX wrote:
>       >
>       >       > Second, the normal map shows the lines of the packet path, red
>       >       for normal hop,
>       >       > violet for hop heading to igate. Here, the line is shown for the
>       >       first hop
>       >       > (the digi i have on the first place in path), even if digi
>       >       doesn't hear&repeat
>       >       > the packet. So it looks like it goes over the digi everytime
>       >       (since the packet
>       >       > path is set as described above).
>       >
>       >       Yeah, you're right. The background for this is the fact that the
>       >       backend
>       >       code precompiles references to all of the known callsigns in the
>       >       path
>       >       (even if the callsigns didn't actually digi the packet). This is
>       >       right and
>       >       well, since it's good to make all of the callsigns clickable links
>       >       in all
>       >       of the views, and the links are quickly generated using those
>       >       precompiled
>       >       references.
>       >
>       >       The bug is that the path line is drawn via all known stations
>       >       referenced
>       >       in the path without paying attention to the "has digipeated" info.
>       >       The
>       >       "has digipeated" information is not currently available to the
>       >       Javascript
>       >       user interface code that draws the line in question. I'll see what
>       >       I can
>       >       do to fix that.
>       >
>       >       You're the first one to complain, since it's quite rare to do what
>       >       you're
>       >       doing (configuring specific digipeaters).
>       >
>       >       When I fix this, some other people will probably come complaining.
>       >       If I
>       >       remember right, some popular digipeater doesn't set the "has
>       >       digipeated"
>       >       bit in some situation when replacing a path element with it's own
>       >       callsign.
>       >
>       >       I'll come and test your digipeater paths in Prague in a week
>       >       (Sat-Tue
>       >       19-22th).
>       >
>       >       > The packet goes directly to igae OK1KHL-1, not even touching the
>       >       OK1ALX-2
>       >       > digi:
>       >       > 2012-03-03
>       21:05:36CET:OK1ALX>UP0R15,OK1ALX-2,WIDE2-2,qAR,OK1KHL-1,T2CZECH:`+`o |n>/]"6@}438.900MHz op.L
>       >       ibor
>       >       > =
>       >       > - on the map, the line is drawn trough the digi (nonexisting
>       >       hop)
>       >
>       >          - Hessu
>       >
>       > --
>       > You received this message because you are subscribed to the Google Groups
>       > "aprs.fi" group.
>       > To view this discussion on the web visit
>       > https://groups.google.com/d/msg/aprsfi/-/JYHHxi_WwQcJ.
>       > To post to this group, send email to apr...@googlegroups.com.
>       > To unsubscribe from this group, send email to
>       > aprsfi+un...@googlegroups.com.
>       > For more options, visit this group at
>       > http://groups.google.com/group/aprsfi?hl=en.
>       >
>       >
>
>          - Hessu
>
> --
> You received this message because you are subscribed to the Google Groups "aprs.fi" group.
> To view this discussion on the web visit https://groups.google.com/d/msg/aprsfi/-/VOobU1chTBEJ.
> To post to this group, send email to apr...@googlegroups.com.
> To unsubscribe from this group, send email to aprsfi+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/aprsfi?hl=en.
>
>

   - Hessu