Ivar KJELBERG
COMSOL Multiphysics(r) fan, retired, former "Senior Expert" at CSEM SA (CH)
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Mar 23, 2013, 2:44 p.m. EDT
Hi
if you have only MF running and get out the force on the central magnet you need to add somehow the rigid body physics to define the rest position of the magnet (with or without gravity). I would also choose ALE for the air in the tube around the floating magnet, but then "solid" is not the physics for rigid body motion, its mainly for flex motion, so I would say use rather PDE physcs and solve the Newton law F = m*a.
You can use some of the "solid" equations as baseline
--
Good luck
Ivar
Hi
if you have only MF running and get out the force on the central magnet you need to add somehow the rigid body physics to define the rest position of the magnet (with or without gravity). I would also choose ALE for the air in the tube around the floating magnet, but then "solid" is not the physics for rigid body motion, its mainly for flex motion, so I would say use rather PDE physcs and solve the Newton law F = m*a.
You can use some of the "solid" equations as baseline
--
Good luck
Ivar
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Mar 26, 2013, 4:04 p.m. EDT
Ivar, thanks for your fast answer!
We did manage to get some things to work in our design, but we've encountered another problem.
Just a basic question actually, and I couldn't find an answer here at the forum. Is it possible to use a 'derived value' in the parameters section?
In our case, we want to use the force applied on the middle magnet ('mfnc.Forcex_middleMag') again to calculate the displacement of this magnet. We want to do this by using the calculated force on the middle magnet in a formula set in the parameters section, to calculate the displacement of the middle magnet. we are using parametric sweep to sweep the time value (time dependent solver didn't work somehow).
If we try it, the line in the parameters section containing 'mfnc.Forcex_middleMag' turns red and when we try to run a study, comsol gives an error.
Thanks in advance
Dirk
Ivar, thanks for your fast answer!
We did manage to get some things to work in our design, but we've encountered another problem.
Just a basic question actually, and I couldn't find an answer here at the forum. Is it possible to use a 'derived value' in the parameters section?
In our case, we want to use the force applied on the middle magnet ('mfnc.Forcex_middleMag') again to calculate the displacement of this magnet. We want to do this by using the calculated force on the middle magnet in a formula set in the parameters section, to calculate the displacement of the middle magnet. we are using parametric sweep to sweep the time value (time dependent solver didn't work somehow).
If we try it, the line in the parameters section containing 'mfnc.Forcex_middleMag' turns red and when we try to run a study, comsol gives an error.
Thanks in advance
Dirk
Ivar KJELBERG
COMSOL Multiphysics(r) fan, retired, former "Senior Expert" at CSEM SA (CH)
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Mar 26, 2013, 4:28 p.m. EDT
Hi
Normally Parameters are evaluated at program/solver start, once, or in the Parameter call, your force value should be rather used in a variable definition.
I'm not sure you can use it for a parameter and have the parameter to change your geometry (nice and interesting try anyhow, pls check, perhaps it works)
normally the force would act on a "solid" physics, it might then displace the "solid" and you use ALE to map the air around to have the mesh deform along the solid motion and hence to be able to refalculate the foce based on the new position.
There is somewhere a falling magnet in a tube example, this gives one way to handle "solid" motion and MF
--
Good luck
Ivar
Hi
Normally Parameters are evaluated at program/solver start, once, or in the Parameter call, your force value should be rather used in a variable definition.
I'm not sure you can use it for a parameter and have the parameter to change your geometry (nice and interesting try anyhow, pls check, perhaps it works)
normally the force would act on a "solid" physics, it might then displace the "solid" and you use ALE to map the air around to have the mesh deform along the solid motion and hence to be able to refalculate the foce based on the new position.
There is somewhere a falling magnet in a tube example, this gives one way to handle "solid" motion and MF
--
Good luck
Ivar
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Mar 26, 2013, 4:33 p.m. EDT
Ivar, thanks again.
I've just looked up the falling magnet in the tube example, which seems very useful.
It somehow has great similarities with our own design.
Dirk
Ivar, thanks again.
I've just looked up the falling magnet in the tube example, which seems very useful.
It somehow has great similarities with our own design.
Dirk
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Mar 26, 2013, 6:02 p.m. EDT
Hi
Normally Parameters are evaluated at program/solver start, once, or in the Parameter call, your force value should be rather used in a variable definition.
I'm not sure you can use it for a parameter and have the parameter to change your geometry (nice and interesting try anyhow, pls check, perhaps it works)
Ivar,
When I use a parameter and make it dependent on t (time) and use a time-dependent solver, I see no change in geometry whatsoever. However, when I use a parametric sweep, and solve for 0t to 1t in steps of 0.1, I do see change in geometry. Pretty weird.
Another problem: when I use a variable definition for my variable and use it for the x position of the middle magnet, Comsol doesn't accept it. Comsol apparently only wants parameters used in geometry and doesn't like variables?
Dirk
[QUOTE]
Hi
Normally Parameters are evaluated at program/solver start, once, or in the Parameter call, your force value should be rather used in a variable definition.
I'm not sure you can use it for a parameter and have the parameter to change your geometry (nice and interesting try anyhow, pls check, perhaps it works)
[/QUOTE]
Ivar,
When I use a parameter and make it dependent on t (time) and use a time-dependent solver, I see no change in geometry whatsoever. However, when I use a parametric sweep, and solve for 0t to 1t in steps of 0.1, I do see change in geometry. Pretty weird.
Another problem: when I use a variable definition for my variable and use it for the x position of the middle magnet, Comsol doesn't accept it. Comsol apparently only wants parameters used in geometry and doesn't like variables?
Dirk
Ivar KJELBERG
COMSOL Multiphysics(r) fan, retired, former "Senior Expert" at CSEM SA (CH)
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
Mar 27, 2013, 3:57 p.m. EDT
Hi
I do not think it's so "weird", in programming too you have "static variables" = Parameter or constants, evaluated at compiler time, and true variables (memory storage) that update with solution. Just do not mix them
Now geometry does only update on parameters, not on running solver variables, but Parameters (only exception I know about) might be updated by a "parameter solver statement"
Consider then rather deformed geometry, that could work with variables (I haven't used it recently, check the doc)
You have different types of variables, and in COMSOL scalars or fields look similar (the (x,y,z,t) dependence is implicit and not written out, except via the element reference (Domain, Boundary, Edge or Point). You need to understand this difference for local or global variables, dependent or not on the spatial coordinates and/or time. This is a notation issue, its all in the doc, but you might need to reread it a few times (I had too ;)
--
Good luck
Ivar
Hi
I do not think it's so "weird", in programming too you have "static variables" = Parameter or constants, evaluated at compiler time, and true variables (memory storage) that update with solution. Just do not mix them
Now geometry does only update on parameters, not on running solver variables, but Parameters (only exception I know about) might be updated by a "parameter solver statement"
Consider then rather deformed geometry, that could work with variables (I haven't used it recently, check the doc)
You have different types of variables, and in COMSOL scalars or fields look similar (the (x,y,z,t) dependence is implicit and not written out, except via the element reference (Domain, Boundary, Edge or Point). You need to understand this difference for local or global variables, dependent or not on the spatial coordinates and/or time. This is a notation issue, its all in the doc, but you might need to reread it a few times (I had too ;)
--
Good luck
Ivar