Thank you for your response. My current task involves simulating a tire. I want to define the specific parameters of this tire myself. For example, the demo provided by your Chrono library features a rigid tire with a radius of 0.5, but for my simulation, I would like a rigid tire with a radius of 0.5 and a weight of 10 kg. I couldn't find any definition related to weight in the rigid tire settings. Could you please inform me where I can find parameter definitions for tires (or other components) such as mass, radius, friction coefficient, etc.? Is it in the mentioned "chxxxxtire.h" header file?
在2023年8月11日星期五 UTC+8 20:03:05<Radu Serban> 写道： > There are several types of tire models implemented in Chrono::Vehicle: > > - Rigid tire (simplest possible model) is based solely on rigid body > contact. This “tire” model is defined by its geometry and contact material > properties. > - FEA tires (arguably the most complex) are defined by their geometry > (FEA mesh), elastic material properties, and contact material properties. > - Handling tires (also called “force element” tires in Chrono) depend > on a large number of parameters, specific to the particular model > implemented (Pacejka, Fiala, TMeasy, TMsimple). Parameters for these > models must be consistent and are typically obtained as a complete set for > a particular tire. TMeasy provides some utility functions to estimate the > model parameters based on a standard tire specification and tire type > (passenger car or truck). Best way to understand what parameters mean for > these tire models is to look up the respective formulas online or in > publications. Chrono::Vehicle uses variable names close to what you’ll > find > there. > > > > In general, you can find out about the meaning and purpose of various > model parameters (whether for tires or other Chrono::Vehicle subsystems) by > looking at the comments in the implementation header files (for tires, > these will be files with names Ch***Tire.h) or else looking at the JSON key > names in the associated JSON specification files for a concrete subsystem > (you will find examples of such JSON files in the Chrono data directory, > under data/vehicle/) > > > > --Radu > > > > > > > > *From:* '马浩楠' via ProjectChrono <[email protected]> > *Sent:* Friday, August 11, 2023 10:49 AM > *To:* ProjectChrono <[email protected]> > *Subject:* [chrono] Re: Questions about the usage of the vehicle library > > > > Thank you for your response. > I want to define this tire more specifically, not limited to just its > radius and width. For example, attributes like the tire's mass should also > be included. How extensive can this customization be? > > 在2023年8月11日星期五 UTC+8 15:07:16<[email protected]> 写道： > > you can refer to demo_VEH_WheeledJSON.cpp, this is an example of how to > use templated vehicle dynamics > > 在2023年8月11日星期五 UTC+8 14:47:36<[email protected]> 写道： > > Hello, I'm a beginner and I've been using the vehicle library for about > two days. I want to modify the JSON data for certain vehicles in the > vehicle library, such as "Maximum Torque". However, I'm not familiar with > cars and I don't know which JSON nodes correspond to specific value ranges. > Is there any related development documentation available? > > -- > 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/669534d0-7ee3-4945-a5cb-60c60b7f0b88n%40googlegroups.com > > <https://groups.google.com/d/msgid/projectchrono/669534d0-7ee3-4945-a5cb-60c60b7f0b88n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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/e6760774-fc80-4a89-98f5-bee149116113n%40googlegroups.com.
