| | |

AGT BLOK Robotic Welding Programming

Overview

Choose a BLOK programming path by testing it on representative weldments against your shop’s CAD and weld information, staff responsibilities, and program-proofing needs—not by assuming any option is ready to weld every assembly.

  • Compare teach-pendant, offline, and auto-programming workflows using both typical and difficult parts; confirm what data each uses and who reviews, adjusts, and proves programs.
  • Cortex auto-programs large, complex assemblies, but some non-structural applications may need custom modules for weld-position and weld-size data, plus additions to the weld-schedule database.
  • Check weld access against the proposed configuration: BLOK 400 uses X and Y movement; BLOK 500 adds Z plunge, and rotation is optional. These system movements are separate from the robot’s movement.
  • Plan safe program testing, safeguarding, training, and weld-quality review; generated programs alone do not establish safe production or application fit.

Choose an AGT BLOK programming path by testing representative weldments against the shop’s available CAD and weld information, staff responsibilities, and program-proofing needs—not by assuming a named option means a ready-to-weld program for every assembly. The decision matters for Indiana fabricators evaluating robotic arc welding of large frames, skids, trailers, and similar assemblies.

BLOK is a modular robotic-welding system intended for large, complex weldments. Its configurable system movement and positioner options can be assessed against the workpiece’s joint locations and access needs; the fit depends on the actual assemblies and the configuration being considered. ([mac-tech.com](https://mac-tech.com/equipment/agt-blok-robotic-welding-systems/))

Compare programming paths using real assemblies

The BLOK programming range includes teach-pendant, offline, and auto-programming approaches. Compare them using the same representative parts, including a typical assembly and one that is difficult to program or access. Ask what information each proposed path uses, who creates and changes programs, how the work is reviewed, and how the resulting program and weld are proven before production. ([agtrobotics.com](https://agtrobotics.com/app/uploads/2025/03/blok_brochure-r02-en.pdf))

For a teach-pendant path, establish who will make and maintain programs at the cell and how those changes fit the production routine. For offline programming, confirm which CAD and weld details the offered workflow can use and how its program will be checked against the actual workpiece and cell setup. For auto-programming, confirm what the software generates from the shop’s data and what review, adjustment, or application work remains.

Cortex is presented as auto-programming software for large and complex assemblies. Some non-structural applications may require custom modules to retrieve weld-position and weld-size information, as well as additions to the weld-schedule database. Bring representative CAD files, drawings, weld annotations, and schedules so the proposed workflow can be assessed against the shop’s actual information rather than an idealized model. ([agtrobotics.com](https://agtrobotics.com/app/uploads/2025/06/cortex_brochure-r04-en.pdf))

Match BLOK movement to weld access

The documented BLOK 400 arrangement uses X and Y movement, while the BLOK 500 adds Z plunge; rotation is optional. These are system-movement choices, distinct from the welding robot’s own movement. Review joint locations, part dimensions, fixtures, workpiece presentation, and required rotations against the specific configuration and positioner options in the proposed package. A family-level description cannot establish access to every weld on a buyer’s assembly. ([agtrobotics.com](https://agtrobotics.com/robotic-welding/blok-heavy))

BLOK materials also position the system for large parts and small-batch production. That makes changing assemblies a reasonable use case to evaluate, but it does not establish a particular programming time, throughput, labor reduction, or weld-quality result. Compare the effort and proofing needs across several actual variants before selecting a path. ([agtrobotics.com](https://agtrobotics.com/app/uploads/2025/03/blok_brochure-r02-en.pdf))

Include proofing, safeguarding, and training

Program creation is only one part of the operating workflow. Plan who reviews and proves programs, who confirms the resulting weld against the application’s quality requirements, and how operators and technical staff will be trained. AWS D16 publications cover robotic arc-welding safety, risk assessment, personnel qualification, and training; include safeguarding and safe program testing in the application discussion rather than treating an automatically generated program as proof of safe production. ([aws.org](https://www.aws.org/About/Get-Involved/Committees/D16-Committee-on-Robotic-and-Automatic-Welding/))

I’m Adam Quoss, Mac-Tech’s Vice President of Sales for Illinois and Indiana. My automation-adoption work includes software and data flow, training, and implementation planning, and I can help assess how a BLOK programming workflow fits your assemblies, information, and staff. Bring representative weldments, drawings or CAD files, weld schedules, batch frequency, fixture and positioning details, and the roles of the people who will program, review, prove, and operate the cell so I can help assess application fit and adoption needs.

Sources

Get Weekly Mac-Tech News & Updates