4/11/2023 8:17 AM | |
Joined: 8/12/2021 Last visit: 10/18/2024 Posts: 327 Rating: (30) |
Hi Samad649! Did you forget the error screenshot? Maybe manual of TM helps you. |
If this Information really helps, you could use the Rate function |
|
4/14/2023 12:11 PM | |
Joined: 11/4/2011 Last visit: 10/2/2024 Posts: 233 Rating: (26) |
Hi, what version of the motion control TOs do you use, and which version of the TM module? By what you describe, I'm betting on the encoder raw value, and the TO expecting something else than what is delivered. Depending on which version of the TO you have, it expects the encoder raw value to be a counter up to 32 bits, but it could be that the encoder / module does not behave this way. If this is the case, then the TO does not see the encoder's value overflow as a regular overflow, but as a position jump. See here for closer information on this (the text beneath the table, at the end of the page): https://support.industry.siemens.com/cs/ww/en/view/109812057/158541876619 Check which TO version you have, if the parameter exists there check the value of BehaviorGx_Xist1 in the TO, and check how the encoder raw value in Gx_Xist1 in the telegram behaves, especially where its overflow back to zero happens. Then do what is described in the manual linked above. |
Follow us on