The "Display" settings control the general display format of PingPlotter’s graphs, including scaling, coloring, and other general values.
If you want to minimize on-screen color, turning this off will hide the green, yellow and red background color on the hop (first) column.
Some 256 color graphics drivers might not look very good with the colors on the graph. Turn off this switch to use a non-color background.
Changing these values sets the Green / Yellow / Red threshold for the graphs. This is dependant on your expected performance. For a modem, 200 ms might be quite good, while for a T1, it could be considered bad.
When examining current data, sometimes its handy to graph the most recent sample collected. Turn this on to see that.
When showing just a few samples, this can be really handy to see the range of latencies. As you increase your window, though, a single bad sample can make this line stretch the scale of the graph.
Normally, setting the graph scale to automatic works pretty well. Sometimes, you might get a few samples *way* out of range, though, that stretches the scale. This is especially likely as you increase the value for samples to include.
Most often, graphing the packet loss is a handy, easy way to see lost samples. 30% seems to work great for highlighting just the right of loss in most cases, but you’re certainly going to run into cases where you want to change this to something lower (as low as 1) or higher (any number is valid – even over 100).
PingPlotter Pro allows you to graph jitter correlated with the time graph. In many cases, jitter is apparent when examining the standard PingPlotter time graphs, so the jitter graph is only displayed when there is enough room. The settings here allows you to control when that is displayed, and what it will look like.
These settings are represented in milliseconds, and control the range of jitter values that will fit into the graph. Note that this also applies to the web interface, so if you want the jitter graphs to show up in the web interface, these settings need to fit the height of the web interface time graphs.