Loading ...
Sorry, an error occurred while loading the content.
 

Re: [aprsisce] Re: TNC timestamps (was: Log time zone)

Expand Messages
  • Lynn W Deffenbaugh (Mr)
    That s more in line with what I would have expected. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
    Message 1 of 7 , Oct 3, 2011
      That's more in line with what I would have expected.

      Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32

      On 10/3/2011 3:39 PM, kf4lvz wrote:
      > Looks like I was wrong. While the program does pick up on the call sign of the originating station, the embedded timestamp blows up the parser so it's never plotted on the map presumably because the payload is after the timestamp and the parser has given up.
      >
      > I was watching things more closely last night and noticed that the station names that show up in the TNC log also showed up in the station list in the upper left but they never plotted on the screen. When I turned off the KPC3's time stamping, everything that was heard by the TNC was plotted.
      >
      > --- In aprsisce@yahoogroups.com, "kf4lvz"<agcme2002@...> wrote:
      >>
      >>
      >> --- In aprsisce@yahoogroups.com, "Lynn W Deffenbaugh (Mr)"<kj4erj@> wrote:
      >>> A TEXT port expects only TNC2 formatted APRS packets with no
      >>> encumberances. The new CONVerse port might be able to do what you're
      >>> after, but it all depends what the TNC actually sends and what the
      >>> timestamp would look like. I have no direct experience with this so if
      >>> you can tell me what the TNC is and a sample of timestamped packets, I'd
      >>> appreciate it.
      >>
      >> I guess it works after all. I forgot I had timestamps enabled on my KPC3-plus. I use it for logging in Xastir because Xastir's TNC monitor doesn't timestamp. Apparently you are able to process it, too. I just wasn't reading closely enough because I saw the timestamp at the very beginning of the line and missed the embedded timestamp entirely.
      >>
      >> Problem solved. :)
      >>
      >> In case you still want it, a KPC3-plus timestamps in square brackets just after the path and before the payload like this (line wraps not withstanding):
      >>
      >> W6MES>STQUPX,W6SCE-10*,WIDE2-1 [09/30/2011 13:16:31]:`.-um*5>/"99}
      >> KT6JA>S42YXU,W6SCE-10*,WIDE2-1 [09/30/2011 13:17:34]:`.@lT"k/]"7c}=
      >>
      >
      >
      >
      > ------------------------------------
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.