Hi Dr. Radu, I'm using the old version of Chrono. I have implemented the tire class, and it works well. It is indeed a feasible approach to model the tires into a single mesh. Thanks for your answer and your team's efforts!
Best regards, Alex 在2024年3月14日星期四 UTC+8 15:04:49<Radu Serban> 写道： > Alex, > > > > You are correct that you do not need to specify a collision shape for the > tire in order to capture the interaction between the tire and the CRM > terrain. You would need one if you also wanted the tire to interact with > other potential rigid objects in the environment. > > > > You can certainly try to implement a tire class to work around the current > Chrono::FSI limitations, but it may be better to wait until we get to the > Chrono::FSI refactoring I mentioned before. > > > > Radu > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Alex Lan > *Sent:* Thursday, March 14, 2024 3:54 AM > *To:* ProjectChrono <[email protected]> > *Subject:* Re: [chrono] Only one mesh is allowed in FSI module? > > > > Hi, > > I'm going to implement a new tire class for the vehicle in this condition. > I would ask if the collision or contact model of tires is not used for MBD > or FSI system update in the SPH environment? Because the tire interacts > with terrain through BCE markers. > > > > Best regards, > > Alex > > 在2024年3月13日星期三 UTC+8 21:16:49<Radu Serban> 写道： > > That’s correct. For something like demo_FSI_Flexible_Toroidal_tire, it’s > easy to build the meshes for all flexible tires within the same ChMesh > object. But that’s not the case if you want top use a vehicle model with > its own flexible tire models (as those encapsulate their own ChMesh > objects). > > --Radu > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Alex Lan > *Sent:* Wednesday, March 13, 2024 2:02 PM > *To:* ProjectChrono <[email protected]> > *Subject:* Re: [chrono] Only one mesh is allowed in FSI module? > > > > Oh, I implement it with a single mesh. Thank you for pointing out! > > Best regards, > Alex > > 在2024年3月13日星期三 UTC+8 17:28:20<Alex Lan> 写道： > > Thank you Dr. Radu. > > > These tires are associated with different wheels. How can I model > multiple flexible tires with a single mesh? Can I implement it with the > implementation of demo_FSI_Flexible_Toroidal_Tire? > > > > Best regards, > > Alex > > 在2024年3月13日星期三 UTC+8 16:04:57<Radu Serban> 写道： > > Alex, you are correct. Currently Chrono::FSI is limited to working with a > single FEA mesh. To model multiple flexible tires, you would need to put > all nodes and elements into a single mesh. > > Better support for FEA in Chrono::FSI, including allowing multiple meshes, > is something that is on the todo list and will be worked on soon. > > > > Best, > Radu > > > > *From:* [email protected] <[email protected]> *On > Behalf Of *Alex Lan > *Sent:* Wednesday, March 13, 2024 8:40 AM > *To:* ProjectChrono <[email protected]> > *Subject:* [chrono] Only one mesh is allowed in FSI module? > > > > Hi everyone, > > > > I tried to model vehicle with four flexible wheels in a CRMTerrain. I > referenced demo_VEH_CRMTerrain_WheeledVehicle > and demo_FSI_Flexible_Toroidal_Tire. However, the simulation was stopped at > the step of terrain.Initialize(). I tried to modelled two flexble wheel in > demo_FSI_Flexible_Toroidal_Tire, and the simulation also stopped at the > stage of terrain.Initialize(). So, is only one mesh allowed in the CRM-FEM > cosimulation? > > > Best regards > > -- > You received this message because you are subscribed to the Google Groups > "ProjectChrono" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/projectchrono/92fb2e48-8716-49a4-8460-d855c4717b55n%40googlegroups.com > > <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/92fb2e48-8716-49a4-8460-d855c4717b55n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!PXic4_ARUKimGBttc5psa41ewFvl81hXYOH-c4wBi-TM4KYNZKO9zgp4kb_bC0GVpApUpchjRQCP4RrEHuI$> > . > > -- > You received this message because you are subscribed to the Google Groups > "ProjectChrono" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/projectchrono/c0971deb-5038-4d5c-ad3d-97391d3317b9n%40googlegroups.com > > <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/c0971deb-5038-4d5c-ad3d-97391d3317b9n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!NaqZjM2I2KtDC8SJRdwwERuBYlFES1LJ0hp6wutwEHfs3zsgVu045O82e2kXr6iDeI5IjgibHfHl_8vPRRI$> > . > > -- > You received this message because you are subscribed to the Google Groups > "ProjectChrono" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/projectchrono/6f855c0c-43f9-4baf-92bb-e812b6043895n%40googlegroups.com > > <https://urldefense.com/v3/__https:/groups.google.com/d/msgid/projectchrono/6f855c0c-43f9-4baf-92bb-e812b6043895n*40googlegroups.com?utm_medium=email&utm_source=footer__;JQ!!Mak6IKo!P0eh7VKUm39ZIcgFseU1uFho-fq6pgcdJITZZ_4hzy8C1VuOSDNNiDZUNJPM0kglVAu00g8XFxTbirU5Qko$> > . > -- You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/4ab75e5f-307f-4487-bcee-7bd20c60cd95n%40googlegroups.com.
