This is where we will share what's happening behind the scenes, including new products, development progress, software updates and ideas we're currently working on.

TegridyFarm started with a simple goal: make automation and monitoring easier without turning every installation into a completely custom engineering project.

A large part of our work currently revolves around the TBOX platform and its associated devices.

Here on the blog, we'll occasionally share:

• Development progress
• New products and prototypes
• Firmware and software updates
• Technical background information
• Interesting problems we encountered during development
• Things that didn't work quite as planned

The detailed technical information will remain in the documentation. The blog is intended to be a more informal look at what we're building and where things are heading.

Thanks for following along.

Ricardo & Dennis

But the goal was never to create just another controller.

From the beginning, the idea has been to combine the functions that are commonly spread across several individual devices into one central platform.

The TBOX handles automation, monitoring and communication while additional devices extend the system where required.

That includes products for sensor inputs, pumps, valves and user interfaces.

One of our main priorities during development is keeping the system flexible without making configuration unnecessarily complicated.

This means a lot of time goes into things users hopefully never have to think about:

• Communication between devices
• Configuration and commissioning
• Firmware updates
• Error handling
• Network connectivity
• Hardware protection
• Diagnostics

There is still plenty to do, but the platform is gradually reaching the point where the individual pieces start feeling like one system rather than separate prototypes.

Turning it into a product that should work reliably every day is something completely different.

During development, even seemingly small details can lead to another PCB revision, another enclosure change or another round of testing.

Connections need to be accessible, components need sufficient thermal margins and the device still has to remain practical to manufacture and assemble.

And then there are all the things you only discover after using the hardware for a while.

That's why our development process usually looks something like this:

Prototype → Test → Find problems → Change things → Test again.

Not particularly glamorous, but very effective.

We'll use this blog to occasionally show some of that process instead of only presenting the finished product.