You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a phenomenon where the racing wheel is connected and auto-centering is interrupted.
After taking the right peak and the left peak, it stops when you have to go back to the center.
So, in this case, we solved the problem by giving 100 auto center, but when I checked the raw data printed afterwards, there was a new problem that the RAW data came out differently from the case of turning off the program and running it again.
If you check immediately after auto-centering (not being centered) mapping to -430 to +430, it comes out well as RAW data that is not close to center value 0. Depending on the intensity, RAW data that usually yields -1 to -2 results are checked.
However, if you turn off the program and run it again (in a centered state), mapping from -430 to +430 will work well with RAW data close to the center value of zero.
I'm attaching it as an execution screen photo in case you don't understand.
1.First Situation
2.Second Situation
So we solved the problem by calling the initialize sequnence function of the device again.
Is this a characteristic of Racing Wheel itself?
Do you have any advice on this matter?
The text was updated successfully, but these errors were encountered:
Product Model is G29
There is a phenomenon where the racing wheel is connected and auto-centering is interrupted.
After taking the right peak and the left peak, it stops when you have to go back to the center.
So, in this case, we solved the problem by giving 100 auto center, but when I checked the raw data printed afterwards, there was a new problem that the RAW data came out differently from the case of turning off the program and running it again.
If you check immediately after auto-centering (not being centered) mapping to -430 to +430, it comes out well as RAW data that is not close to center value 0. Depending on the intensity, RAW data that usually yields -1 to -2 results are checked.
However, if you turn off the program and run it again (in a centered state), mapping from -430 to +430 will work well with RAW data close to the center value of zero.
I'm attaching it as an execution screen photo in case you don't understand.
1.First Situation
2.Second Situation
So we solved the problem by calling the initialize sequnence function of the device again.
Is this a characteristic of Racing Wheel itself?
Do you have any advice on this matter?
The text was updated successfully, but these errors were encountered: