QUESTION:
How to setup a constant external magnetic field in Emag LF?
ANSWER:
The procedure for creating a constant external magnetic field depends upon which element technology you need to use.
Please see the attached input files that define a free space permeable domain and impose boundary conditions giving rise to uniform B field. I created 4 files; one for each of the formulations currently available in ANSYS.
1) 2D_MVP.inp: 2D PLANE53 mesh, uniform B field acting in y direction. Exploits fact that B = curl A.
2) 3D_MVP.inp: 3D SOLID97 mesh, uniform B field acting in the y direction. Exploits fact that B = curl A.
3) 3D_MSP.inp: 3D SOLID96 mesh, uniform B field acting in the y direction. Uses fact that H = grad MAG and B = mu*H.
4) 3D_edge.inp: 3D SOLID117 mesh, uniform B field acting in the y direction. Uses undocumented DREC command.
drec_docu.txt: DREC ('dirichlet rectangle') command documentation
Ps. For some reason, the DREC model will NOT run unless element type 36 is defined in the database (even though no SOURC36 elements are defined).
|
QUESTION: How to setup a constant external magnetic field in Emag LF? ANSWER: The procedure for creating a constant external magnetic field depends upon which element technology you need to use. Please see the attached input files that define a free space permeable domain and impose boundary conditions giving rise to uniform B field. I created 4 files; one for each of the formulations currently available in ANSYS. 1) 2D_MVP.inp: 2D PLANE53 mesh, uniform B field acting in y direction. Exploits fact that B = curl A. 2) 3D_MVP.inp: 3D SOLID97 mesh, uniform B field acting in the y direction. Exploits fact that B = curl A. 3) 3D_MSP.inp: 3D SOLID96 mesh, uniform B field acting in the y direction. Uses fact that H = grad MAG and B = mu*H. 4) 3D_edge.inp: 3D SOLID117 mesh, uniform B field acting in the y direction. Uses undocumented DREC command. drec_docu.txt: DREC (`dirichlet rectangle`) command documentation Ps. For some reason, the DREC model will NOT run unless element type 36 is defined in the database (even though no SOURC36 elements are defined). |
||
|