I had tried to model two-wheelers for a month, and I have made the model which is quite interesting, and Adams's view has no problems to simulate it and works fine. I have used tire model 'pac_mc_120_70R17_cross.tir' for both front and rear wheel where road profile is '3d_bump.rdf'. But the problem that I am currently facing is a warning message in the message window. It says, Long. slip exceeds validity range. And also the front wheel has no rotation motion at all. But If I remove the motorcycle chain, the front wheel will begin to rotate as the bike moves forward. Is there something that I missed because I don't have much experience in ADAMS.
The tire was tested to certain limits when it comes to normal load, camber, and lateral and longitudinal slip. These values are listed in the tire property file. So the fit is really only accurate inside these ranges. You can use a tire testrig or plotting tool to see what happens if you go outside these ranges. It is typically not recommended to do this, but the Magic Formula usually provide a smooth extrapolation, even if the values will be wrong.
Depending on implementation, the values for these quantities that are sent to the tire model might either be capped at the min/max value or the actual value might be used. In either case a warning will be issued. As you can see from your warning messages above, the implementation in Adams does cap the value to the range {min,max}. (I don't agree with that implementation, but in one way it is a safe keeping to prevent your model to explode).
The other problem is clearly something you have done wrong. How did you model the chain?
The tire was tested to certain limits when it comes to normal load, camber, and lateral and longitudinal slip. These values are listed in the tire property file. So the fit is really only accurate inside these ranges. You can use a tire testrig or plotting tool to see what happens if you go outside these ranges. It is typically not recommended to do this, but the Magic Formula usually provide a smooth extrapolation, even if the values will be wrong.
Depending on implementation, the values for these quantities that are sent to the tire model might either be capped at the min/max value or the actual value might be used. In either case a warning will be issued. As you can see from your warning messages above, the implementation in Adams does cap the value to the range {min,max}. (I don't agree with that implementation, but in one way it is a safe keeping to prevent your model to explode).
The other problem is clearly something you have done wrong. How did you model the chain?