Built for automation engineers

Less repetitive work.
More engineering.

Practical Windows tools that simplify HMI, Modbus and PLC workflows—from inspecting a live device or TIA project to generating structured results you can verify. Spend less time on repetitive preparation and manual handoffs, and more time engineering.

Built by an automation engineer Focused on real-world workflows
Abstract connected industrial automation system representing PLC, HMI and communication workflows
01Focused tools
for real problems
02Simple setup.
Clear results.
03Built for industrial
workflows
BESENIX
Our products

Tools that earn their
place in your toolbox.

Focused applications for recurring engineering tasks. Each tool keeps configuration visible, preserves a clear path from test to result and produces output you can review without hiding the underlying automation logic.

Early access
COMMUNICATION & DIAGNOSTICS

Besenix
Modbus Studio

Connect to real Modbus TCP devices, inspect live traffic and validate registers before PLC code is generated. Build typed client tags or documented server address maps, test reads and writes, then create complete MB_CLIENT or MB_SERVER solutions for TIA Portal V21.

View product page
  • Live polling, write tests and frame diagnostics
  • Typed tags, server address maps and data blocks
  • Complete TIA Portal client and server import
How it works

From repetitive task
to controlled workflow.

Both tools start from the real project or device, configure only what is needed and create an inspectable result. The tested configuration remains visible so it can be reviewed in the target workflow before commissioning continues.

HMI

Screen Manager

  1. 01
    Connect

    Open the intended TIA Portal V21 project, authorize Openness and select the target HMI.

  2. 02
    Manage

    Export working examples or import prepared Classic XML, Unified JSON and static packages.

  3. 03
    Verify

    Inspect the resulting screen content in TIA Portal and retain the available backup before continuing.

Explore HMI Screen Manager
TCP

Modbus Studio

  1. 01
    Test

    Connect to the real device or configure a local server map and confirm the required addresses.

  2. 02
    Configure

    Define named tags, protocol addresses, data types, byte order, scaling, access and polling.

  3. 03
    Generate

    Create the MB_CLIENT or MB_SERVER solution, structured data blocks and commissioning address documentation for TIA Portal V21.

Explore Modbus Studio
Compatibility

Know what fits
before you start.

Early access is focused on the configurations below. Before a build is shared, the TIA Portal version, target device, firmware context and intended workflow are checked against the currently validated scope.

ProductEngineering environmentCurrent scopeStatus
HMI Screen ManagerTIA Portal V21WinCC Classic & Unified · XML · JSON · Static packages Early access
Modbus StudioTIA Portal V21Modbus TCP · MB_CLIENT V6.0 · MB_SERVER · Address maps Early access
Early access

From tested Modbus tags to working TIA Portal code.

See Modbus Studio test a live Modbus TCP device, inspect communication diagnostics, assign engineering data types and import a complete MB_CLIENT V6.0 setup into TIA Portal V21. The tested tags become the basis for the generated PLC structure.

  • Read, poll and diagnose live Modbus TCP registers
  • Generate named tags, buffers, scaling and quality signals
  • Import the communication FB, call FC and data blocks through TIA Openness
Modbus TCP Server

From register map to a working PLC server.

See Modbus Studio define and test a typed server register map with an external client, then import the generated MB_SERVER blocks into TIA Portal V21 with PLC data areas and a clear commissioning address reference.

  • Configure named and typed Holding Register values
  • Verify FC03 reads and FC06 or FC16 writes before import
  • Import the complete server structure through TIA Openness
Product demo

See HMI Screen Manager in action.

Watch the workflow from authorizing an open TIA Portal V21 project and selecting the intended HMI to importing, exporting and safely managing Classic and Unified screens, with the result kept visible for final review.

  • Controlled connection to the selected TIA Portal project
  • Classic XML, Unified JSON and reusable package workflow
  • Structured examples for AI-assisted screen creation
Why Besenix

Software should adapt
to the engineer.

Every Besenix tool starts with a recurring automation problem—not a generic feature checklist—and follows how engineers configure, test and verify working systems.

01

Purpose-built

Focused tools for specific engineering jobs, without hidden automation or bloated menus.

02

Easy to adopt

Familiar workflows that expose important configuration and keep results easy to review.

03

Engineer-led

Developed for people who program, commission, diagnose and maintain industrial machines.

Engineer-led software

Built around real
automation work.

Besenix Automation Suite is developed by automation engineer Matija Besednik around recurring PLC, HMI, communication and diagnostics tasks. Product decisions begin with steps that consume time during development, testing and commissioning.

The goal is fewer repetitive steps, clearer diagnostics and more time for engineering decisions. Generated content remains structured and visible so it can be checked, adjusted and maintained afterward.

Suggest a tool
BESENIXAUTOMATION SUITE
HHMI Tools
MModbus
PPLC Tools
DDiagnostics
Common questions

Before you request
early access.

Builds are reviewed against each engineering environment before they are shared, keeping expectations, known limitations and the intended test scope clear.

Which TIA Portal version is currently supported?

The early-access workflow, generated content and documentation are built around TIA Portal V21, where the current Openness operations are validated. Other versions must be discussed before testing.

Does Besenix use TIA Portal Openness?

Yes. Supported project operations use controlled Openness workflows. The manuals explain Windows authorization and preparation before an import begins.

What does HMI Screen Manager support?

The current version supports Classic XML, Unified JSON snapshots, backup-oriented deletion and static screen packages. Exact behavior depends on the HMI family.

What does Modbus Studio support?

The current scope includes Modbus TCP client and server tests, frame diagnostics, typed tags, address maps and generation of MB_CLIENT V6.0 or MB_SERVER solutions with diagnostic status.

How do I activate the HMI Screen Manager trial?

Download and install Version 1.3.3, start the application and send the displayed Machine ID through the contact form. A signed trial license is then issued specifically for that computer. Modbus Studio builds continue to be shared after a compatibility review.

Early access process

A short path to
a controlled trial.

  1. 01Download or request accessDownload HMI Screen Manager directly or request the current Modbus Studio build.
  2. 02Confirm compatibilityCheck the supported TIA version, device family and intended engineering workflow.
  3. 03Activate and testSend the HMI Machine ID for a signed trial license, then test first on a project copy.
Contact Besenix

Tell us what you
want to automate.

Request early access, ask for a demonstration or describe a workflow you want to simplify. A little technical context helps us give you a useful compatibility answer.

Prefer email?besenix@gmail.com