// How I work

First I simulate it,
then I put it into production.

One single method for plants and software: it is described, generated, automatically tested, then tried on the bench with real hardware.

// How I work

First I simulate it,
then I put it into production.

Same method for software and PLC logic: it is written, tested, and only after that does it touch the real plant.

01 / SOFTWARE
Automatic tests, not by eye.
Python, test suite that runs on every modification. No release without green tests — applies to Telegram bots, webapps, and backend in the same way.
02 / PLC LOGIC
Written and tested on plcsim before the real PLC.
plcsim It is a soft-PLC that emulates a real PLC (IEC 61131-3: ST and Ladder) via browser. I write and verify the logic — valves, timers, alarms, state machines — without risking a plant shutdown or an incorrect command on real hardware.
03 / HARDWARE
Same logic, physical PLC.
Once verified in simulation, the logic moves to the real PLC (Delta or compatible) via Modbus — same protocol, same addresses, no rewriting required.
04 / TELECONTROL
Then Vedetta takes remote control.
Once on-site, Vedetta it reads and writes to the same Modbus tags: live dashboard, history, alerts via Telegram. The same plant, controllable from anywhere.
05 / MULTI-BRAND
One plant, any PLC brand.
The plant is described only once in a text file: valves, motors, instruments, alarms. From there I generate the program for Siemens TIA Portal and for Delta ISPSoft, with identical functions and addresses. Changing brands does not mean rewriting everything.
06 / AI + TESTING
AI writes, tests decide.
I use AI agents for repetitive tasks, but nothing enters a project unless it passes automatic testing: hundreds of test cases compared against specifications, followed by bench testing with real PLCs. Faster, without lowering standards.

Do you have a project
in mind?

Write an email, no complicated forms. Tell me what you do, what isn't working or what you would like to work. I will reply within 24 hours.