Skip to content

inoGUI · inoCORE

HMI and PLC for small machines

Draw the screens, wire the control logic, deploy to an ESP32. One project file holds the visualisation, the program and every bus the machine speaks — and the panel keeps running when the network does not.

What it is Documentation

In development — not on sale yet.

  • 0 €

    per deployed device, at every level

  • 13 €

    a year for the entry licence

  • 24 µs

    control cycle with the network down

  • < 1 ms

    to load a screen on the panel

Three parts, one project file

  • Panel


    The firmware. Runs the control logic on its own core, drives the touch display, talks to the buses. It never parses text and is never recompiled because you changed a screen.

  • Editor


    A desktop application holding the whole project: tags, screens, logic, devices, boards. It draws the canvas with the same code the panel uses, so what you place is what appears on the glass.

  • WebVisu


    The same visualisation in a browser, served by the panel itself. Included at every licence level, on the phone in your pocket as readily as on the cabinet door.

What it does differently

  • Screens and logic are data


    Everything you draw is compiled into one versioned package that the panel executes. Changing a machine means uploading kilobytes, not building firmware and not sending an engineer.

  • No fee per machine


    The licence belongs to the editor, not to the panel. Deploy to as many machines as the job needs — and when a licence lapses, every panel already in the field keeps running. A licence cannot switch off a customer's machine.

  • The network is optional


    Logic, timers and the buttons on the glass work with the server dark, the broker unreachable and the Wi-Fi gone. Telemetry is a window out, never a condition of running.

  • Mistakes surface on your desk


    The project is checked against the board before anything is deployed: display, buses, free pins, package size, product limits. You find out where it is cheap to find out.

What the panel talks to

  • Fieldbuses


    Modbus RTU on RS485 and Modbus TCP on Ethernet or Wi-Fi, each as master or slave. CANopen as manager or as a node. Raw CAN frames for the devices that never learned CANopen — batteries, solar inverters, chargers.

    Modbus · Raw CAN

  • Drives


    Frequency inverters over CANopen, with the CiA 402 state machine wrapped in blocks so it is not your problem. Motion blocks carry the names a machine builder already knows.

    Axes and drives

  • Supervisory systems


    MQTT telemetry to a dashboard, or one topic per tag so the panel behaves as a process data server. Home Assistant creates its entities by itself.

    MQTT and Home Assistant

  • Chips on the board


    Analogue inputs, port expanders, a real-time clock, retentive values in FRAM or EEPROM. Added by picking them from a catalogue, not by writing drivers.

    Peripherals

Start reading

  • New here


    What the system is walks through the whole system in one page.

  • Building something


    Getting started is the shape of a project from an empty editor to a running panel.

  • Working out the cost


    Pricing is four levels, from 13 € a year. There are no per-device fees.