Discussion Closed This discussion was created more than 6 months ago and has been closed. To start a new discussion with a link back to this one, click here.
How to eliminate pressure gradient when modeling electroosmotic flow in a microchannel
Posted Jul 5, 2020, 11:58 p.m. EDT Electromagnetics, Low-Frequency Electromagnetics, Computational Fluid Dynamics (CFD) Version 5.5 0 Replies
Please login with a confirmed email address before reporting spam
Hi,
I am trying to model a completely electroosmotic (EO) flow in a microchannel where a miscible displacement of oil with water occurs. I believe all other set ups are correct but there is probably something wrong with the way I have st up my boundary condition (BC) which I need help with. In my model, I have used the creeping flow, transport of diluted species and electric current physics. In the creeping flow physics, I have assigned an EO velocity to the wall based on the Smoluchowski's equation and with the assumption of a small and negligible EDL, while the inlet and outlet BC were set to open boundary. In the electruc current physics, I have assigned voltages to the inlet and outlet, while the walls are electrically insulated. In the transport of diluted species physics, there is no flux at the walls while the inlet and outlet have fluxes (General inward flux for the inlet and external convection for the outlet). After running the model, I am surprisingly getting a parabolic velocity flow profile even though I have not prescribed any pressure or velocity at the inlet or outlet of my system. I would normally expect to see a plug flow profile, with a constant velocity along the channel. I am not sure exactly what to do in this case and I would appreciate any help that I can get. Thank you.
Hello Benedicta Nwani
Your Discussion has gone 30 days without a reply. If you still need help with COMSOL and have an on-subscription license, please visit our Support Center for help.
If you do not hold an on-subscription license, you may find an answer in another Discussion or in the Knowledge Base.