I am trying to extract information about the contact incidents in Adams, in order to exact the times at wich more than 1 gear tooth pair of an involute gear model come into contact. I understand that after the simulation, I can look at the contact incidents and tracks, but if possible, I'd like to be able to extract the incidents during simulation, in the form of measurements.
As you decribed in great detail, I can access and manipulate the contact incidents through the tolerance value at collate_contacts. This however means that I can only access the contact incidents only after the simulation.
To clarify, I'd like to mention my full problem, so that I may better explain it.
I am building a model with a pair of involute gears in contact. During simulation, the gears mesh in a 1-2-1 tooth manner i.e., the number of teeth during contact changes at a certain frequency. This results in the well known time varying stiffness of involute gears.
As I understand it, Adams acounts for the different number of teeth coming into contact in the form of recognizing that another part of the gear's geometry comes into contact, thus increasing the contact force. However, the contact stiffness still remains the same (even though it should also increase).
What I was hoping to achieve is to set up a contact stiffness runtime function expression, in which by measuring "something that would tell me that another tooth just came into contact" in Adams, the contact stiffness would change accordingly.
e.g. I could measure the value of the contact force and when its value increases above a certain threshold (meaning that another tooth pair just came into contact), I could have a runtime expression increasing the contact stiffness. This however is not efficient, since the contact force is directly related to the stiffness itself. As such, I am attempding to adentify the extra tooth contact in a different manner, hence the need to identify the contact incident during runtime.
To summarize, what I would like to know is if there is a way to identify the second tooth pair coming into contact during runtime, wheter it be through the contact tracks or not. Otherwise, my only option would be to examine the contact tracks, identify the frequency at which the second tooth pair comes into contact and set up a predifined contact stiffness function changing according to time only.
As you decribed in great detail, I can access and manipulate the contact incidents through the tolerance value at collate_contacts. This however means that I can only access the contact incidents only after the simulation.
To clarify, I'd like to mention my full problem, so that I may better explain it.
I am building a model with a pair of involute gears in contact. During simulation, the gears mesh in a 1-2-1 tooth manner i.e., the number of teeth during contact changes at a certain frequency. This results in the well known time varying stiffness of involute gears.
As I understand it, Adams acounts for the different number of teeth coming into contact in the form of recognizing that another part of the gear's geometry comes into contact, thus increasing the contact force. However, the contact stiffness still remains the same (even though it should also increase).
What I was hoping to achieve is to set up a contact stiffness runtime function expression, in which by measuring "something that would tell me that another tooth just came into contact" in Adams, the contact stiffness would change accordingly.
e.g. I could measure the value of the contact force and when its value increases above a certain threshold (meaning that another tooth pair just came into contact), I could have a runtime expression increasing the contact stiffness. This however is not efficient, since the contact force is directly related to the stiffness itself. As such, I am attempding to adentify the extra tooth contact in a different manner, hence the need to identify the contact incident during runtime.
To summarize, what I would like to know is if there is a way to identify the second tooth pair coming into contact during runtime, wheter it be through the contact tracks or not. Otherwise, my only option would be to examine the contact tracks, identify the frequency at which the second tooth pair comes into contact and set up a predifined contact stiffness function changing according to time only.