FEA Setup & Tool

Published Reviewed Next review

Axial Halbach Array COMSOL Model Setup

Screen a sector candidate, then validate and set up its COMSOL 3D model with the actual geometry and field pattern.

Scope: this is a setup guide and relative planner, not a downloadable axial-flux .mph file. For a starting reference, see the COMSOL segmented Halbach rotor model; its geometry is not a validated axial-flux design.

COMSOL Scope Planner
Sector candidate and relative scope index only. No RAM or solve-time prediction.
Planning only

Changes the relative index; the planner assumes other dimensions stay fixed.

200 mm

Even number. The displayed pole-pair sector still needs validation.

16

Use first to check static fields, force, or torque.

Controls the planning mesh density target before the first solver pass confirms real element counts.

CoarseNormalFine

Planning Output

Relative scope proxy for comparing inputs in this tool; not a COMSOL benchmark or hardware recommendation.

Planning only

Candidate Sector

1/8

Relative Planning Index

1.00×

Model Angle

45.0°

Study Type

3D magnetostatic

Index reference: 200 mm outer diameter, 16 poles, Normal mesh = 1.00×. The candidate sector assumes a valid pole-pair repeat; confirm it against the complete geometry and field pattern.
16 poles45.0 degree sectorcut-plane boundariesrelative scope index

Treat the pole-pair sector as a candidate only. Choose periodicity and field transformations from the actual geometry, excitation, and magnetization pattern, then compare the result with a larger sector.

Recommended next action

Start with a magnetostatic pilot to verify field direction and mesh convergence. Record actual degrees of freedom and RAM before sizing a larger run.

Relative index only: it uses OD², the candidate sector fraction, and uncalibrated mesh weights. It omits inner diameter, axial length, detailed geometry, DOFs, solver settings, and hardware. It cannot predict elements, RAM, or solve time.

Build the Model Around a Verified Repeat

The planner helps compare a pole-pair sector candidate and relative model scope before building the COMSOL Multiphysics 3D study. It does not predict elements, degrees of freedom, RAM, or solve time. Verify symmetry with field plots, then measure resource use on a pilot model with the same physics.

Reduce the model only at a proven repeat

A pole-pair sector is a candidate based on pole count, not proof of symmetry. The full geometry, excitations, magnetization sequence, and resulting field must repeat across the cut faces.

COMSOL symmetry guidance

Prove mesh adequacy with the decision metric

Track the air-gap field, force, torque, or loss that drives the design. Refine the relevant regions and compare results; a generic element count or skin-depth rule cannot establish convergence for every material and physics setup.

COMSOL mesh-refinement guidance

Size memory from a project-specific pilot

Record actual degrees of freedom, peak RAM, solver, and physics on a smaller model using the same setup. Extrapolate from those measurements; element count alone does not predict memory or solve time.

COMSOL memory guidance

Audit every segment magnetization

Assign the vector direction from the assembly drawing in a suitable local coordinate system. Plot the vectors and verify them before adding motion or using field, force, or torque results.

COMSOL Halbach rotor model
sector cut planespole-pair sectorvector audit before transient solve

Key Setup Checklist

1. Geometry & SymmetryCut the model into the smallest repeatable sector that preserves pole polarity, magnetization rotation, slots, sleeves, and any mechanical asymmetry. Do not assume a one-pole sector is valid for every Halbach pattern.
2. Coordinate SystemsCreate local coordinate systems for magnet segments, then plot vector arrows. This catches reversed radial, tangential, or axial directions before a clean but wrong solve is used for decisions.
3. Mesh & Motion SetupFirst prove the magnetostatic field. Add motion, time steps, eddy-current domains, and loss outputs only after boundary repeatability and air-gap mesh controls are stable.
4. Material & Temperature InputsReplace generic magnet data with supplier BH curves, conductivity, density, coating thickness, and operating temperature before using the model for procurement or design release.

Engineering Evidence

COMSOL sources explain how symmetry, degrees of freedom, and memory depend on the model setup. They do not provide a universal element, RAM, or solve-time benchmark for axial Halbach rotors; the tool therefore shows only a relative planning index and directs users to measure a representative pilot model.

Need an engineering review?

Share the geometry, magnetization map, and output you need to validate with the FEA team.

Discuss model assumptions

Planner Assumptions and Limits

Input / AssumptionHow the Tool Uses ItWhat It Cannot Prove
Rotor outer diameterScales a relative planning index with OD² while treating other dimensions as unchanged.Not an element-count estimate. It omits inner diameter, axial length, slotting, end turns, bolt holes, sleeve details, and cooling channels.
Pole countDisplays a pole-pair sector candidate for review.The candidate is valid only when geometry, excitation, and field behavior repeat; skew, slots, and magnetization pattern can require a larger sector.
Solver typeChanges the recommended modeling sequence and pilot measurements.The page does not predict solve time. Transient effort depends on motion, time steps, physics, and enabled loss domains.
Mesh targetApplies an uncalibrated relative weight to compare planning scenarios.The index does not represent elements or DOFs. Establish mesh adequacy by convergence of the chosen output.
Review dateAssumptions and public source labels were reviewed on October 4, 2026.COMSOL release behavior, solver hardware, and supplier BH curves can differ by project. Next review is scheduled for February 4, 2027.
1Sector2Vectors3Mesh4Solve5MeasureDo not jump to transient motion until static field direction is proven.

Validation Workflow

A useful COMSOL Multiphysics model is not the file that solves fastest. It is the model where sector choice, magnetization, mesh, material inputs, and measured data can be defended separately. Use the workflow below as the handoff checklist before quoting tooling or hardware.

CheckEvidence to CaptureFailure SignalRecovery Action
Magnetization auditVector arrows match the drawing for every segment in the sector.Flux points to the wrong rotor face, or adjacent Halbach segments repeat as plain N-S poles.Export a vector plot before torque, force, or field-map comparisons.
Boundary repeatabilityField lines and normal flux density are continuous or sign-flipped as expected at sector cuts.Torque changes materially when the same model is rerun with a larger sector.Move from one-pole to one-pole-pair or larger symmetry until the repeat is valid.
Air-gap mesh convergenceThe tracked torque, force, or B-field metric stabilizes across progressively finer meshes within a project-set tolerance.Ripple or peak flux changes after each refinement pass.Add surface mesh controls at magnet edges, gap faces, sleeve interfaces, and probe paths.
Demagnetization marginWorst-case operating point remains inside the supplier BH curve at temperature.Corners or side segments enter the knee region after temperature and reverse-field loading.Review SH/UH/EH-class NdFeB, SmCo, thicker magnets, or lower operating temperature.
Measured prototype closureGauss map, torque stand, or force fixture agrees with the model inside acceptance limits.A clean simulation cannot reproduce measured assembly data.Update gaps, magnet tolerances, Br distribution, adhesive thickness, and fixture materials.

Risks, Trade-offs & Boundaries

Simulating an axial Halbach array in 3D carries computational, material, and interpretation risk. The biggest mistake is to treat a converged solver status as proof that the sector, vector directions, and material data are physically correct.

1Sector cutsProve field repeat2VectorsMatch drawing3MeshCheck convergenceReview each check with project evidence
Simulation StrategyRecommended ConditionRisks / LimitationsAlternative Solution
Full 3D TransientUse when end effects, eddy currents, motion, or sleeve losses are decision-driving.High compute cost and high setup sensitivity. Timing can vary by hardware, time-step count, mesh, and enabled loss domains.Prove field direction in magnetostatic first, then add transient motion to only the shortlisted geometry.
2D / 2.5D ApproximationUse as an early sizing shortcut at an average radius or for topology exploration.Cannot close axial end effects, inner/outer radius leakage, sleeve interactions, or local demagnetization.Treat as a pre-filter, then verify finalists in COMSOL 3D with the real annular geometry.
Single Sector SymmetryUse when the full geometry, winding, slot, and Halbach vector sequence truly repeat across the cut faces.Wrong periodicity can produce believable fields with incorrect torque, force, or leakage.Compare against a larger sector and keep screenshots of boundary field continuity.
Default Mesh SettingsUseful for a first pass after geometry import and material assignment.May miss sharp air-gap, magnet-edge, and sleeve-interface gradients.Add mesh controls and report convergence against the metric used for the design decision.

Scenario Guidance

ScenarioStarting PointWatchoutNext Step
Coreless axial-flux rotorUse the planner to review a pole-pair sector candidate and begin with magnetostatic field mapping.Eddy currents in sleeves and magnets can dominate transient cost once motion is enabled.Validate field waveform, then add transient motion only for candidate geometry.
Halbach generator prototypeScreen pole count and rotor diameter before building a full transient voltage model.Electrical load, rectifier assumptions, winding resistance, and speed profile are outside this planner.Connect COMSOL outputs to circuit or system simulation after geometry is stable.
Sourcing a magnetized rotor assemblyUse the output as an RFQ brief for sector size, model complexity, and validation expectations.Supplier quotes need magnet grade, coating, sleeve, balance grade, and inspection method.Send model assumptions, drawings, target temperature, and acceptance metrics to the supplier.
Troubleshooting a divergent solveCheck field directions, invalid symmetry cuts, poor air-region setup, and over-broad eddy domains.A smaller mesh is not always a safer model if boundary physics are wrong.Return to a magnetostatic sector, prove field direction, then reintroduce motion and losses.

Frequently Asked Questions

Does this page include an axial Halbach .mph model file?

No. This page is a setup guide and relative scope planner, not a downloadable axial-flux COMSOL model. The linked COMSOL Application Library example is a segmented Halbach rotor reference for magnetization setup; it is not a validated axial-flux performance model.

Why do I need COMSOL Multiphysics 3D instead of 2D for an axial Halbach array?

Axial flux machines have meaningful 3D flux paths at the inner radius, outer radius, magnet edges, and sleeve interfaces. A 2D or unfolded model can be useful for early screening, but final torque, force, demagnetization, and leakage decisions need a 3D check.

How do I model the Halbach magnetization directions in COMSOL?

Create a relative cylindrical or segment-local coordinate system. For each magnet segment, assign the magnetization vector from the actual magnetization-angle drawing, then plot the vectors before relying on field or torque output.

What boundary conditions should I use?

Use paired periodic or sector-symmetry conditions only when the complete geometry and excitation repeat across the cut faces. Choose continuity or anti-periodicity from the field transformation and the COMSOL physics interface; pole count alone does not determine it. Compare the result with a larger sector before using it for a design decision.

How do I reduce solve time for a 3D transient model?

Use the smallest valid symmetry sector, start with a magnetostatic model, control the mesh around the air gap and magnet edges, and enable transient motion only after the static field makes sense. Limit eddy-current domains to conductive parts that matter for the design question.

Should I include the retention sleeve in the model?

Include it geometrically when it affects the air gap or mechanical envelope. Enable eddy-current loss only if the sleeve is conductive enough to matter for the operating frequency and the simulation objective.

Can this planner replace a COMSOL solve?

No. It suggests a pole-pair sector for review and compares a relative scope index. It does not calculate field distribution, torque, force, voltage, demagnetization, thermal rise, element count, degrees of freedom, RAM, or solve time.

What does a higher planning index mean?

It means the selected inputs produce a larger relative scope proxy than the reference case in this tool. The index is not calibrated to COMSOL element counts, memory, or solve time, so do not use it to select hardware or promise a delivery time.

How should I validate the mesh?

Track one decision metric such as average air-gap flux, peak demag field, cogging torque, or force. Refine the air gap, magnet edges, and sleeve interfaces until that metric changes less than the tolerance your project can accept.

When is one-pole symmetry unsafe?

One-pole symmetry is unsafe when the Halbach vector pattern, skew, slots, winding phase, sensor placement, or mechanical features do not repeat over one pole. In those cases, use one pole pair or a larger sector.

What important inputs does the planner omit?

It intentionally omits magnet thickness, grade, air gap, axial length, stator slots, sleeve material, conductivity, winding data, speed, load, and temperature. Those belong in the actual COMSOL model or RFQ package.

How do I use this for a supplier RFQ?

Send the planning output with drawings, pole count, magnetization direction map, target field or torque metric, operating temperature, sleeve and coating requirements, and the planned prototype validation method.

Does COMSOL Multiphysics choose the right Halbach pattern automatically?

No. The solver follows the geometry, material data, coordinate systems, and vector assignments you provide. Wrong magnetization directions can produce a clean-looking but physically wrong result.

What should I do if the model disagrees with a Gauss map?

First check probe height, coordinate alignment, segment polarity, magnet grade scatter, gaps, adhesive thickness, and temperature. Then update the model before changing the magnetic design.

RFQ Handoff Minimum

  • Geometry: OD, ID, active axial length, magnet thickness, air gap, pole count, and sector repeat assumption.
  • Magnet data: grade, supplier BH curves, magnetization-angle map, coating, tolerance, and maximum operating temperature.
  • Solver objective: field map, torque, force, voltage, eddy-current loss, demagnetization margin, or prototype correlation.
  • Validation plan: probe path, fixture, torque stand, acceptance threshold, and the measured data that will update the COMSOL model.

Need Help Validating Your Halbach Design?

We offer complete COMSOL Multiphysics 3D FEA services, from static proof-of-concept to full 3D transient thermal-electromagnetic co-simulation.

Engineering RFQ Inbox

[email protected]

Include target torque/speed, quantity, and delivery location.

Direct Engineer Chat

WhatsApp Engineering Support

Use for drawing, specification, and RFQ clarification.