Currently, the backend server serializes data and serves it via REST. This can cause significant delays due to serialization of large data arrays, which results ultimately in dropping of inbound stream frames. Utilizing tide-websockets will allow us to avoid serialization of this data (since we can use a TypedArray around the binary data in Javascript.

Add support for decimating the data server-side. This will allow us to immediately decimate in-bound data.

Decimation may either be done automatically, or via input provided from the UI.

This may help resolve #6 by limiting the number of samples sent to the frontend.

When requesting a capture for 10ms of data, the server will provide 10ms worth of samples. If samples are dropped in the middle, this means that there may be data spanning an undefined amount of time.

This is undesired because it means that we cannot consistently display the data with a fixed time window, as the maximum timestamp changes based on whether or not data was dropped.

Add support for triggering captures based on a single edge trigger mechanism.

The edge trigger should allow the following:

• Edge trigger time support (e.g. set the edge to 0-100% of the capture window)
• Support rising/falling triggers on a specific trace label
• Utilize the standard 30%/50%/70% edge trigger mechanism, where the waveform must rise from below 30% max, cross 50%, and then exceed 70% to define a valid "edge". The trigger time is defined as the point that crosses 50%.

Hello,

This looks like a very useful project, but I didn't find any documentation on how to use it. Specifically, it'd be very useful for me to know what the required steps are to recreate the interface shown in the video in the readme.

If you could share / point me to that, that would be much appreciated!

When running with a basic help config in Powershell, no output is displayed to the user. The script simply exits.

For capture periods longer than ~150ms, the capture doesn't appear at all. Investigation of the console log indicates that Javascript hits a memory exception and drops the serialized data.

This should be resolved either by limiting the size of the data sent to the front end (limiting number of points) or by drawing the display in chunks of a specific size.