See the screen print.? Can anyone tell me where the time in the upper left-hand corner comes from?? It appears to be counting down.? Is that the time to the next beacon transmission?

How about the time from one of my logs from this entry:
Port(APRS-IS):2024-04-30T11:52:19.541 TOO LONG:# logresp AB9NN-48 verified, server T2POLNW

The time seems to be 11:52:19 -? is that UTC time?? I was nowhere near my PC at that time Eastern time.

Thanks!

The times do not seem to match my PC system clock time which is accurate from a utility which keeps it synced to an accurate time source.

开云体育

Send yourself a ?aprss and see what time is shown in that response.?? I just did it and it shows 04-30 07:52:19 and my local time is 10:45:xx, so not even the minutes is correct.?? Unless, of course, the timestamp in the ?aprss response isn't actually the current time.? I didn't think of that until just now.

开云体育

Ok, I just double-checked the source and the timestamp in the ?APRSS response is actually the timestamp that the port entered the current state.?? I now remember doing this so that you can see if your RF or -IS port is going through state transitions.?? So the following lines

04-30 07:52:19 APRS-IS OK 497 493 480 65 /hr
04-30 07:52:19 FT857d OK 192 59 189 32 /hr

mean that those ports became "OK" at that (localtime) timestamp.?? My apologies for crying wolf when there was no need.

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

Send yourself a ?aprss and see what time is shown in that response.?? I just did it and it shows 04-30 07:52:19 and my local time is 10:45:xx, so not even the minutes is correct.?? Unless, of course, the timestamp in the ?aprss response isn't actually the current time.? I didn't think of that until just now.

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

On 4/30/2024 9:31 AM, AB9NN - Jon Kreski wrote:

The times do not seem to match my PC system clock time which is accurate from a utility which keeps it synced to an accurate time source.

On Tue, Apr 30, 2024 at 09:29 AM, AB9NN - Jon Kreski wrote:

See the screen print.? Can anyone tell me where the time in the upper left-hand corner comes from?? It appears to be counting down.? Is that the time to the next beacon transmission?

Yes, the upper left corner shows the time until your next beacon.

Lynn was answering the other portion, but I didn't see a response to that part of your post.

-------
Robert Giuliano
KB8RCO

开云体育

The Time in the upper left corner is actually the Transmit Pressure.?? You can read about it at:

The thin colored bars at the bottom of that pane are also documented that that wiki page.

And yes, the trace logs are UTC time, hence the T separator although technically I should also have a Z or Z+00:00 but that seemed a bit verbose.? ()?? The "TOO LONG" indicates that additional data was received from the TCP/IP stack beyond the # logresp packet, which is likely normal depending on the speed of your PC and the Internet connection.? It's part of the wonders of CR/LF delimited packets being parsed from a TCP/IP streaming socket.

In fact, this is a frequent newb TCP/IP programming misteak (sic) where they "assume" (with all the connotations of that word) that a single read will only and always get a single packet (line of text, in the case of the APRS-IS) from a socket.?? In local testing with fast loopback or Ethernet connections, it seems to work, the read always returns just the data that was written in a single write.? But when deployed to the field with the vagaries of actual Internet connections and traffic routing, a single read may have a partial packet, a full packet (which is all they expected), a full packet plus part of the next packet, or even multiple packets possibly ending with a partial packet.