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
08.03.2011, 02:05 GMT-5
Hi
if you cantilever is between one or two electrodes, and you apply a too large voltage you get the pull-in effect, at deflections above 2/3 (if I remember right) if the gap your system becomes unstable and the cantilever will pull-in and collapse on the electrode (if you have no contact the FEM model will overlap). So this might be (all depends on your model) a natural effect !
Take a look, try with a smaller step
--
Good luck
Ivar
Hi
if you cantilever is between one or two electrodes, and you apply a too large voltage you get the pull-in effect, at deflections above 2/3 (if I remember right) if the gap your system becomes unstable and the cantilever will pull-in and collapse on the electrode (if you have no contact the FEM model will overlap). So this might be (all depends on your model) a natural effect !
Take a look, try with a smaller step
--
Good luck
Ivar
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
21.03.2011, 03:09 GMT-4
Hi Ivar,
Thanks for the response. Here's what's happening: I can smoothly run my time dependent simulations just before the pull-in voltage, however, as soon as I reach pull-in (or what I believe is pull-in), the simulation freezes at certain value, which I would expect, given that the lack of convergence at that point might drive comsol crazy. However, It just stays ther for ages, and in some cases when I leave comsol computing, it closes suddenly as if it had an error. My question is if there's anyway to tell comsol: "OK, that's enough, let's end this simulation and show some no convergence error message" or something like that. Which is the maximum simulation time for comsol to "give up" ? Can I define that time to avoid this ugly freezing?
Than you.
Hi Ivar,
Thanks for the response. Here's what's happening: I can smoothly run my time dependent simulations just before the pull-in voltage, however, as soon as I reach pull-in (or what I believe is pull-in), the simulation freezes at certain value, which I would expect, given that the lack of convergence at that point might drive comsol crazy. However, It just stays ther for ages, and in some cases when I leave comsol computing, it closes suddenly as if it had an error. My question is if there's anyway to tell comsol: "OK, that's enough, let's end this simulation and show some no convergence error message" or something like that. Which is the maximum simulation time for comsol to "give up" ? Can I define that time to avoid this ugly freezing?
Than you.
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
21.03.2011, 03:46 GMT-4
Hi
in the solver settings you have different stop conditions you can add or modify, and limit the number of iterations, it's worth to take a closer look.
But its absolutely worth to use the latest version, where a lot of early issues with the first 4.0 have been solved
--
Good luck
Ivar
Hi
in the solver settings you have different stop conditions you can add or modify, and limit the number of iterations, it's worth to take a closer look.
But its absolutely worth to use the latest version, where a lot of early issues with the first 4.0 have been solved
--
Good luck
Ivar
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
09.04.2011, 09:20 GMT-4
Hi Ivar,
I managed to use the stop condition, however, my real problem is to make the contact problem work with time dependent simulation, do you know if it is feasible? I 've already seen some of the threads about it and followed the steps but I haven't got any results. As soon as I include contact and run the simulation, I get the error: segregated solver does not involve all components, even though I disabled the contact pressure from the list of variables to solve for.
I would greatly appreciate any help you can give me in this regard.
Hi Ivar,
I managed to use the stop condition, however, my real problem is to make the contact problem work with time dependent simulation, do you know if it is feasible? I 've already seen some of the threads about it and followed the steps but I haven't got any results. As soon as I include contact and run the simulation, I get the error: segregated solver does not involve all components, even though I disabled the contact pressure from the list of variables to solve for.
I would greatly appreciate any help you can give me in this regard.
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
09.04.2011, 10:13 GMT-4
Hi
normally it means that the solver segregated tree does not include all dependent variable items.
Do a manual check: open the Dependent variable node and check which variables are tagged "solved for" then open the segregated nodes and check that you have them all. If not, try to select the solver node and generate a default sequence, then check again, or update by hand.
It could well be an issue with the early v4.0. I'm using the latest version and I get very seldom such errors, it means that I have really messed up with the model and that COMSOL has not managed to follow. Then by regenerating the sequence everything is fine again ;)
--
Good luck
Ivar
Hi
normally it means that the solver segregated tree does not include all dependent variable items.
Do a manual check: open the Dependent variable node and check which variables are tagged "solved for" then open the segregated nodes and check that you have them all. If not, try to select the solver node and generate a default sequence, then check again, or update by hand.
It could well be an issue with the early v4.0. I'm using the latest version and I get very seldom such errors, it means that I have really messed up with the model and that COMSOL has not managed to follow. Then by regenerating the sequence everything is fine again ;)
--
Good luck
Ivar