OWTAP details details

annotated OWTAP detail window

 There is a lot of information in the Detail Window.

  1. Packet sent from client to owserver.
    Two lines for header, raw values on top
    Interpreted values underneathe (see 6,7,10)
    Data included is under that (see 11)
  2. Packet(s) returned from owserver to client
    Two packets in this case (see 3 and 4)
    Again two lines for header, raw and interpreted (see 8,10,13)
    Data follows header for each packet, if any
  3. First returned packet
    Note (0-indexed) number in first column
    This is a "keep-alive" packet, used to let client know that owserver is still working on the answer, don't despair (see 9)
  4. Second packet
    Labeled 1 in upper left
    Format of data depends on type of request
  5. Request data
    Not shown, but the data for the request can take two lines for WRITE messages, the path and the data.
  6. Version
    Shows number of Tokens (for loop suppression) and owserver protocol Version (still 0)
    Return packets have similar information (always 0 tokens)
  7. Message type
    DIRALL (full directory in one big list)
    Other types include READ, WRITE, DIR, ...
    The format of the data (see 11) and the responses depends on the message type.
  8. Return code
    Responses return 0 for successful processing of request, and various negative numbers on error.
  9. PING
    Special packet to show that owserver is still working on the request (to distinguish from a owserver or network failure).
    Indicated by the special -1 payload.
    No other data in the packet is important.
  10. Flags
    Used to format the responses
    C is temperature scale (Centigrade).Others F, K R.
    f.i is 1-wire device format (10.801754000800 for example)
    bus means that entries like System, Statistics, bus.x,... should be included
    persist (not shown) shows whether a persistent tcp connection was requested, and granted
  11. Path
    The request data always starts with a 1-wire path ("/uncached" in this case).
    There is a null (0) byte at the end
    Payload shows the total length (including null byte)
    See 5 about WRITE messages that have another string following that gives the data to write to that path.
  12. Return data
    DIRALL includes a comma separated list of directory entries.
    size shows the length of the string (2771 chars) and payload includes a null byte at the end.
    The format of the return data depends on message type -- none for WRITE.
  13. Directory flags
    DIR and DIRALL include some special flags in the offset field of the last packet -- a logical union of the flags for each individual entry.
    resume and ovdr -- some of the devices support overdrive speed of the RESUME command (not too useful to a remote client)
    alarm -- some devices can trigger an alarm (like over-temperature) and so include the alarm directory
    temp -- some devices can support simultaneous temperature conversions, so incldue the simultaneous directory