Influence of galvannealed zinc coating on refining microstructure and enhancing mechanical performance of laser brazed DP600 and DP980 steels
Bibliographic record
Abstract
• Reveal the role of galvannealed coatings on braze microstructure and mechanical properties. • Coating thickness affects joint surface and wetting, and composition affects thermal profiles. • Lower Fe accelerates DP980 brazing cooling, refining interfacial and braze microstructure. • TEM and micro-indentation relate microstructure/precipitates to braze deformation mechanism. • DP980 braze exhibits superior strength (highest fracture load, local yield/true stresses). Laser brazing is a critical process for class-A automotive joints, with coating properties significantly affecting joint quality. However, the direct relationship between coating variations and the resulting microstructure and mechanical performance in laser-brazed advanced high-strength steels (AHSS) remains largely unexplored. This study systematically investigates how galvannealed (GA) coating thickness and Fe content within the coating influence laser brazing of DP600 and DP980 steels, including similar and dissimilar configurations. It reveals that variations in coating, rather than bulk steel chemistry, govern joint behavior. Thicker Zn coatings enhanced wetting but introduced surface imperfections, while a lower Fe content increased the cooling rate during DP980 brazing directly refining both the Cu braze microstructure and Fe(Si) interfacial reaction layer. The DP980 joint achieved the highest fracture load (4.4 kN for a 15-mm-wide strip), attributed to its refined braze grains and improved interfacial integrity. The dissimilar DP980-DP600 joint exhibited a refined microstructure compared to the DP600 braze, though the DP600/Cu boundary limited its joint strength due to incomplete wetting. Micro-indentation tests confirmed enhanced yield and tensile strengths in the DP980 braze. This study opens pathways for investigating tailored coating chemistries and thicknesses as design parameters for optimizing braze microstructure and mechanical integrity in AHSS assemblies.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".