Program architecture
Routines, cycle logic, sequences, states, reset strategies and the relationship between automatic and manual operation.
Practical J-TECH training
Program industrial robots with a method, not just points and instructions.
Practical support on software structure, parameterisation, comments, debugging and maintenance in real robotic cells.
01Software architecture
02Useful parameterisation
03Comments and maintainability
04Debugging and restarts
Training developed on the shop floor, not from generic slides.
The goal is not to memorise a sequence of commands. It is to understand how to build readable, maintainable software that fits production and lets the next technician find their way without reconstructing the entire program.
- Programs that have grown over time without a clear structure.
- Duplicated routines, unclear names and logic that is hard to follow.
- Parameters used where they add complexity, or missing where they would help.
- Comments that are either too scarce or too abundant to remain useful.
- Fragile restart and alarm strategies during production.
- Poorly documented interfaces with PLCs, vision systems or peripherals.
What we work on together
The programme is adapted to the team's level and the actual cell: maintenance, programming, commissioning, production support or technical handover.
Parameterisation
When recipes, registers, offsets and variable data provide real value, and when a simpler solution is more robust.
Comments and readability
How to make software understandable without filling it with unnecessary text: names, notes, conventions and critical points.
Industrial debugging
Reading symptoms, separating causes, controlled tests, restart logic, intermittent faults and safe production changes.
Who benefits
This is not an abstract lesson. It works when there is a real cell, a concrete requirement or a technical team that needs greater autonomy.
01
Maintenance and in-house technicians
To understand programs, intervene with judgement and reduce dependence on external support for every minor anomaly.
02
Junior programmers
To move from making the robot move to building software that is structured, diagnosable and sustainable over time.
03
Integrators and manufacturers
To align methods, documentation and cell logic before or after a complex commissioning phase.
The real value is leaving sound judgement, not just instructions.
Good industrial software is not software that works once during acceptance. It remains readable months later, supports fast diagnosis and can be changed without turning every intervention into a new risk.
Before commissioning
Define structure, naming, variant management and interfaces before the software grows in a disorderly way.
During production
Help technicians understand what is really happening when alarms, rejects or intermittent stops appear.
After handover
Document, rationalise and transfer knowledge on systems that are already running but difficult to maintain.
Training and on-the-job support
Would you like the people working on the cell to become more independent?
Describe the system, the team's current level and the goal: programming method, maintenance, parameterisation, debugging or technical handover.
info@j-tech.it
+39 348 3098257
LinkedIn - Lennart Jr Sillen
Corso Susa 189A, 10040 Caselette (TO), Italy