New Features in WDServer V3

WDServer optionally distribute setup sheet XML files to connected clients

  • A setup sheet file can be configured for each stream/car.
  • If a new client (WinDarab) connects to a WDServer stream, the setup sheet is sent to the client.
  • WDServer observes the setup sheet files for changes/updates. If WDServer receives an update notification the changed setup sheet is distributed to all clients without stopping/restarting the stream.
  • WinDarab v7.10.059 is required to support the WDServer distributed setup sheets.
  • WinDarab can handle changed values and also newly added setup sheet channels. Deleted setup channels are not applied; they will disappear if WinDarab reconnects to the WDServer stream
  • The setup sheet can be viewed and edited in WinDarab. Nevertheless, updates aren’t applied unless the changed setup sheet folder is stored in the folder that is configured/observed in/by WDServer.

New page “Client Monitor”

A new page “Client Monitor” was added to WDServer. On this page WDServer lists all clients that are “seen” by WDServer:

  • A client is listed as soon as a lookup or client info message is received by WDServer.
  • A client is unlisted if WDServer doesn’t receive a client info message for more than 1 minute. In case a WinDarab client send only a lookup message and no client info the time until unlisting is extended to 15 minutes.
    • Starting with WinDarab v7.10.056 client info messages are sent periodically by WinDarab.
    • Up to WinDarab v7.10.055 WinDarab sends a lookup message once after startup. A client info message is sent only if WinDarab connects to a WDServer stream.

The “Client Monitor” page shows additional information about detected clients:

  • Online/Offline indicator
  • Last Seen time
  • Streams a client is connected to (on this WDServer)

Additional properties if a client info message was received:

  • Application Name
  • Application Version

Optional laptime limit to force file export

  • A laptime limit can be set on the “Configure” page. If the current lap exceeds the given limit WDServer starts to export the lap in multiple WinDarab files using the given timespan.
    • By default, the laptime limit is set to <empty> (or 0), meaning that this feature is disabled.
    • The laptime limit can be set globally only and not per stream.
  • Placeholder [Fragment] and [n] were added to avoid duplicated filenames.
    • [Fragment]: Is the fragment counter of a lap (starting at 1)
    • [n]: Is a unique number to avoid any kind of duplicated filename (startsint at 1)
    • [Fragment] or [RecTime] can be used to distinguish the files, if they belong to the same lap.

Internet connection monitor added

  • At the bottom of the sidebase WDServer shows a internet connection monitor now. That shows the ping/http roundtrp times of the past
  • The connection monitor uses a simple ping to googles nameserver (8.8.8.8).
  • Because some firewalls or network configurations may prevent successful pings, WDServer will fall back to (slower) sending http-request to the WinDarab Update server.

External Telemetry – New interface for incoming data

  • External Telemetry is a new data interface for incoming data. The interface is designed to accept data in a well-documented manner. This allows 3rd party software to generate telemetry data that is accepted by WDServer v3 and delivered to any WinDarab v7.10 client.
  • External telemetry streams are only supported by WinDarab v7.10 clients and requires an addon license for “External Telemetry”.
Additional information