22884Re: [aprsisce] Object Paths
- May 12, 2013On 5/12/2013 12:18 PM, James Ewen wrote:
> When APRSISCE/32 sends packets directly to the APRS-IS stream, the RFPer http://www.aprs-is.net/Connecting.aspx
> path is not included. I'm not sure if that happens with other programs
> or not. I've never spent the time to see if it is true. Regardless,
> that might be the source of Bob's observation.
> Packets originating from the client should only have TCPIP* in theNothing in there about "unless you're also transmitting on RF". So
> path, nothing more or less (AE5PL-TS>APRS,TCPIP*:my packet).
client-generated packets directly injected to the APRS-IS will only
contain a path of TCPIP*. The same packet transmitted on RF will
contain the configured RF path. Eventually, each RF port will have the
ability to specify its own path for transmitted packets and the Chat
interface will also allow a local override of the default RF path.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
PS. And that's yet another reason to run single-RF-port instances. If
you override the path in the Chat, which port did you intend it to use
that path on? Or just how complicated are we going to make this?
- << Previous post in topic Next post in topic >>