Synnax

Clear visibility into system conditions is critical for safety. In the latest Synnax release, we've introduced a real-time table with color gradients that clearly indicate when sensor values exceed expected thresholds. The result: fast, informed operator decisions that prevent costly, dangerous mistakes.

We just released Synnax 34! This marks our 17th major release in just 6 months. This version brings our newest integration for LabJack Corporation devices. You can record from sensors and control actuators on any T-Series device in just a few clicks. We've also developed a new log component for displaying real-time control sequence data. Release notes available here: https://lnkd.in/e8c-3W9z

Excited to preview Python based calculated channels, the most powerful and challenging feature we’ve implemented in Synnax so far. We’re often asked: How can I implement sensor voting? What if I want to calculate a flow rate on the fly? How can I raise a warning when a calculated value exceeds a threshold? Instead of requiring engineers to learn SQL or a custom math query language (looking at you InfluxData), we decided to embed a Python interpreter for calculating complex values in real-time. Signal processing? Use Scipy. Fluid calculations? Use REFPROP. Matrix transformations? Use Numpy. The full power of Python at your fingertips, all while capable of churning through kilohertz rate data. Here's the simplest sensor voting algorithm you've ever seen - it's like magic.

Sometimes the simplest features are the most satisfying. Instant split and multi-monitor display of a plot that updates 60 times a second.

Pytest and Google's OpenHTF have gained popularity for validating hardware components. The problem? OpenHTF has little to no documentation, Pytest is built for software, and neither of them provide a real-time view into how components are behaving. This makes it challenging to debug subtle issues that require quick access to sensor data. Synnax's Pytest extension let's you visualize tests as they run, clearly associate test cases with telemetry, and identify issue as they arise. Here's a demo of Synnax running a pressurization test suite. It automatically labels a failed pressure stability test, and permanently records the cause of failure for later access.

“We added another temperature sensor for this component test, can you put it in the GUI?” is a common exchange between test/operations engineers and control software engineers. Test engineers waste time waiting on a limited pool of developers, and software engineers fill their day with trivial changes instead of making large improvements. Synnax’s low-code tools were built with both of these groups in mind. Test engineers accelerate setup time by making changes themselves, and software engineers get those precious, uninterrupted hours to make quality progress. Here’s a time-lapse of me setting up a fully controllable, real-time mission control GUI in five minutes without any code:

"I'd rather just use a CSV file!" is one of the common objections I get from engineers who consider putting their sensor data in a database. It's pretty easy to understand why. Convincing a Mechanical Engineer to learn SQL just so they can run a Python script is a really hard sell. With Synnax, loading any data set is as simple as copying a line of code. Then it's just like working with a file. No strange connection parameters and no foreign query languages. P.S. If you're extra stubborn, Synnax also exports CSV files.