Setting of the extrusion blow molding machine formula management system

Recipe Management System Configuration for Extrusion Blow Molding Machines

A recipe is not just a list of temperatures and speeds. In extrusion blow molding, a recipe is a complete behavioral description of the machine — it tells the extruder how fast to turn, the traction how hard to pull, the parison programmer when to pinch, and the mold when to close and blow. Get the recipe wrong and you get thin walls, off-center parisons, or parts that will not sit flat on the shelf. Configuring the recipe management system to handle this complexity — dozens of part numbers, multiple materials, shift handovers, and continuous process drift — is one of the most underrated engineering tasks on a blow molding floor.

What a Recipe Actually Contains

Most people think a recipe is barrel temperatures plus screw speed. That covers maybe 15 percent of what matters. A complete blow molding recipe has to coordinate at least six subsystems simultaneously.

The extrusion section defines zone temperatures, screw RPM, torque limit, back pressure, and die gap. The traction section sets take-off speed, belt pressure, and the ratio between extruder output and parison pull rate. The parison programmer controls segment pressures, timing offsets, pinch point location, and blow-back pressure. The mold section holds clamp force, close time, blow pressure curve, cool time, and eject sequence. Cooling water flow and temperature sit in their own group. And then there are global settings — material type, target part weight, estimated cycle time, and quality tolerance bands.

A typical machine running 30 part numbers with 3 material variants each ends up with 90 active recipes. Each recipe contains 200 to 500 individual parameters. The management system has to store, protect, version, and deploy all of this without turning the operator into a data entry clerk.

Building the Recipe Hierarchy

Material Profiles as the Foundation

Start at the bottom of the hierarchy with material profiles. A material profile is not a recipe — it is a set of inherent properties that do not change regardless of part geometry. Melt temperature range, recommended shear rate, viscosity curve, drying temperature, and maximum allowable die pressure all live here.

When the operator selects HDPE 5000S for a new part, the system pulls the material profile and auto-populates sensible defaults for barrel zones, screw speed limits, and torque thresholds. The operator never touches these unless they have a specific reason. This prevents the classic mistake of setting zone 4 to 260 degrees for a resin that degrades above 240 — the material profile caps it at 235 and flags a warning if the operator tries to override.

Material profiles also carry lot-specific data. If the resin supplier sends a new batch with a melt flow index 10 percent higher than the previous lot, the process engineer updates the material profile once. Every recipe that references that material inherits the new baseline automatically. No need to open 30 recipes and adjust screw speed manually.

Part Recipes and Inheritance Chains

Above the material layer sit the part recipes. Each part recipe inherits from a material profile and then adds or overrides values specific to that geometry. A 500 ml bottle and a 2 liter jug made from the same HDPE share the same material profile but have completely different parison programming, mold timing, and blow pressure curves.

The inheritance model saves enormous amounts of storage and reduces configuration errors. When you create a new part recipe, the system copies all values from the parent material profile and marks them as inherited. You only enter the values that actually differ — maybe 40 parameters out of 300. The rest stay linked to the material profile. If the material profile updates later, the inherited values update too, unless you explicitly locked them at a fixed number.

Locking is important. If you found that zone 3 needs to run 10 degrees hotter for this particular part due to a die geometry quirk, you lock that value so future material profile updates do not overwrite your hard-won tuning. The system should show a small padlock icon next to any locked parameter so the operator knows it is deliberate and not an oversight.

Version Control and Change Tracking

Why Simple Save-and-Load Is Not Enough

The naive approach — edit a recipe, hit save, done — works until it does not. Someone changes a traction speed by accident. The parts look fine for two hours. Then the wall thickness drifts out of spec and nobody can figure out why because the recipe history is gone.

A proper recipe management system treats every save as a new version. The old version stays readable and restorable. Each version carries a timestamp, an operator ID, a free-text comment field, and a checksum of the full parameter block. The comment field is where discipline lives — "increased die temp 5 deg to fix sag on bottom" tells the next person exactly what happened and why.

Version branching helps when you run the same part with two different resins. Start from version 3.2 of the bottle recipe. Create a branch for the new resin lot, adjust temperatures and screw speed, save as version 3.2-R2. The original 3.2 stays untouched for the standard resin. When the new lot runs out, you switch back to 3.2 without any merging or confusion.

Rollback Procedures and Fail-Safe Defaults

Every machine should have a factory default recipe loaded at power-up. This is not a production recipe — it is a safe-state set of parameters that keeps the extruder running at low speed, all heaters off, and all motions disabled. If the operator selects a corrupted recipe or the HMI crashes mid-load, the machine falls back to this safe state instead of lurching into full production with unknown values.

The rollback process itself should be fast. Operator selects the part, taps "show history," picks the version from two days ago that was known good, confirms, and the machine reloads in under 10 seconds. If rollback takes more than 30 seconds or requires a controller reboot, operators will not use it — they will try to tweak the bad recipe live, which almost always makes things worse.

Access Levels and Permission Architecture

Separating Operator, Engineer, and Maintenance Roles

A blow molding machine has three distinct user types and they should not share the same login. The operator needs to start cycles, adjust speed override, load recipes, and acknowledge alarms. That is it. They should not see PID gains, servo feedforward terms, or die pressure calibration offsets.

The process engineer needs full recipe edit access, including locked parameters, material profile management, and trend review. They should also be able to create new recipes from scratch or clone an existing one with a new name.

The maintenance technician needs a different view entirely — motor currents, encoder feedback, drive fault logs, and mechanical limit switches. They do not need to change temperatures or blow pressures. Giving them access to process parameters creates risk without benefit.

Implement this with role-based login on the HMI. Each role maps to a permission set that the controller enforces, not just the screen. Even if the operator somehow navigates to the engineering screen through a back door in the menu, the controller rejects any command that falls outside their permission set. Screen-level hiding is not enough — the command parser has to know who is talking.

PREVIOUS：Automatic lubrication control system for extrusion blow molding machine NEXT：Parameter storage and retrieval function for extrusion blow molding machine