Viper Wheel on Multicore Tire Test Rig

[A. Drozda]

Good evening,

I'm still new to Chrono and C++, and I'm having some trouble figuring out the interconnections- is there any instruction available, or could you give a quick explanation, of how to run a Viper Wheel using the test rig on granular terrain?

Thank you,

Alex Drozda

[Luning Bakke]

Can you provide more context? What demos are you looking at? Are you looking at the ones in demos/vehicle/terrain?  How do you plan on modeling the terrain? Different terrain modeling methods provide various fidelity levels; ranging from low fidelity to high ones, Chrono has SCM (semi empirical approach, based on Bekker's model), CRM (models terrain as a continuum) and DEM (models terrain particles discretely). When modeling particles discretely, chrono also has smooth contact vs non-smooth contact.  What kind of computation resource do you have? Do you have an NVIDIA GPU? Then you can run CRM or DEM simulation. If not, you can use Chrono::Multicore for the non-smooth discrete method.  

Thank you,

Luning

[A. Drozda]

Hi Luning,

I'm currently looking at trying to run the VEH_Multicore_TireTestRig demo, but switching from the tire to a wheel from the Viper model. I'd like to use the granular terrain, as the multicore_tiretestrig demo has. I'd like to be able to look at traction, so the cylinder model of the wheel that's associated with the "rigid tire" contact geometry doesn't work. To summarize, I want to take the Multicore_TireTestRig demo, and put a Viper wheel on the rig to look at traction information on the granular material. Please let me know if there is other information that you need; thank you for your help!

I do have an Nvidia GPU, but for some reason Chrono::GPU and Chrono::FSI don't build correctly when I've tried them; their respective .lib files aren't being created. This only seems to happen with those two modules though, and I don't know what to make of it. Other modules, such as Multicore, OpenGL, and Irrlicht build without any problems. If this is something I should send in a notice about, please let me know; I assumed I had simply set something up incorrectly.

Thank you,

Alex

--
You received this message because you are subscribed to a topic in the Google Groups "ProjectChrono" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/projectchrono/Rn8X_72rVRM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to projectchron...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/9624a026-598e-4c3b-9cca-b960f57c0f5dn%40googlegroups.com.

[Radu Serban]

Alex,

 

You should simply replace the collision geometry of the “rigid tire” used for the Viper model with a mesh and use that with the ChTireTestRig (as illustrated in demo_VEH_Multicore_TestRig for use with Chrono::Multicore and a “HMMWV” rigid tire). 

Note that you do not need to have a concrete ChTire object implemented in code (as is done in that demo which uses the existing HMMWV_RigidTire class of the vehicle models library).  Instead, you can create a rigid tire model using a JSON specification file (in which you specify all “tire” parameters, including the Wavefront OBJ file that contains your Viper wheel mesh).

 

Regarding building the CUDA-based modules, please keep in mind that those currently support only CUDA up to version 12.3.2.  They will not work with newer versions.

 

--Radu

--
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 projectchron...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/CALVGm-8kM79kxN%3DaPg8pWj%2BCNnW4prqGZzp7HqOHtPs39Mt%2Bbg%40mail.gmail.com.