FlyPT 6DOF/Stewart/Hexapod Interface for linear and rotating actuators

I really hope that my problem is only because I'm too stupid to set it out correctly. Here what I have:

And when I click the little orange button for the filters:



I've tried many values for the washout. Both at 100, one 80 one 20, vis versa... No change.

I did what you told me. Of course, it resolved my yaw problem (no yaw).
But when I tried it, something felt totally off. I got the feeling of sliding the wrong way. So I reverse the extra 1. It felt much better.
After a few run and a lap improved by 8 min (no joke), I stopped just to find out I had forgotten to adjust the center of forces to my seat. I will have to test it again later. It felt really different, and I did not feel dizzy.


Anyway, thanks for the info @yobuddy .

@Pierre Lalancette
I don't really understand the 3 Extras in Assetto Corsa. Seems traction loss is in the 3.
Like youbuddy said, better keep it simple in this case.
That trick to make rotation around the front with traction loss doesn't seem to work in AC.
I have to take a better look to see what's happening.

Version 1.6.6

Download in the first post of this topic.
Corrected some problems, like saving the center of rotation.
Added graphics for pose components.
Now you can see the effect of filters in the pose, before calculating the actuators position.

On the next image, we can see heave.
Gray, value received from Simtools.
Black, a high pass filter applied.

Gain is not represented on the graphic.
Hope I didn't broke something with those changes. Had not much time to test...

Ok, I'll be more causious about the extras in Asseto Corsa, or any game for that matter.

Great! A new version of hexapod, on Monday! I will have to wait the whole week before testing it.

Can't wait.

@pmvcda just got a quick suggestion if you can or cant do it. Is there a way we can turn each DOF off so we can tune each DOF individually through the FlyPT interface rather than going into simtools and turning the DOF's off ? like a check box to tick or untick ?

Just put zero in the range values.

I know I'm just being lazy , pain in VR to use the keyboard

Edit: I could just use the mouse but it's a lot of clicks up and down

I will just set to zero

I can add a button to lock the axis.

Yes, a mute for each forces.

Version 1.6.7

Well, you asked, you have it

- Lock the pose components. You can lock in the position you want and reset after locking if you want.
- Made some internal changes for future updates, so any error, please report.
- Flip pose components changed internally also, but output should be the same. In the graphics we can see the inversion.



Download in the first post of this topic.

Awesome work dude !!! I was fiddling for ages clicking away last night this makes it loads easier

Does it work in minimized now aswell can't say I've tried it on last version

... Don't know, I'm not near the rig to test if minimised is working ...
I think (hope) so.

I forgot to try I minimized lol

Did you change anything else as it was like none of the filters were working tonight I had to tune it by the tuning centre and raise all the settings quite high to smooth it out, changing the gain and filters did nothing in hexpod interface

Sorry,
I'm taking a look at it.
I made some changes and I'm still making. Found some errors.
So we are going to have version 1.6.8 today.

Version 1.6.8

Download on the first post of this topic.

-Corrected some bugs.
-Made some internal changes.
-Added roll over. It's working like we have in Simtools.
-Added washout.
We should use washout in combination with roll over in the rotating axis but we can try all the combinations, they are available for all pose components.

Hope it's not messing everything.
I'm starting to feel that instead of getting better, it's getting worse...

Bellow picture, shows graphic for yaw.
Black the result of the washout on the gray signal.




Explaining the filters

I will put this in the first page, but for now, and since I'm going to make some changes, let's keep it here.
Also I hope I'm not making any error. Sometimes, I get lost on those things, so if you think something is wrong, please say so.

In the interface you can apply filters to input and output.
Input is the pose components, like sway, heave or yaw.
Output is the actuators position.

There are multiple types of filters, but let's ignore the DEMA and TEMA ones (I might remove them, there's no benefit to use them here).

EMA filters are Exponential Medium Average filters.
What they do is pick the last n values received and calculate an exponential average of them.
Older the value, less weight he as on the result.

LOW PASS FILTER
So, if you pick a EMA low pass with a value of 20, you are using the last 20 values received, including the new one, to calculate the filtered value.
The result of this filter is to soften the signal.
A low pass filter will look like this (surge input in LFS with low pass filter using 20 samples):

Gray is the original value and black the filtered one.
The result is softened, but you get a delayed response.
If you think that road texture in a car sim is to harsh on your rig, you can use this filter to soften the road texture.

HIGH PASS FILTER
The high pass filter is the removal of the low pass filter from the original value.
high pass value = original value - low pass value.
The result is the high frequency values and the removal of the low ones.
The value you set on the interface is the number of samples used to calculate the low pass that we remove from the original signal.
A high pass filter will look like this (surge input in LFS with high pass filter using 10 samples):

You get the small details, but low frequency value changes are removed from the signal.
Use this to get only the small details, like road texture in heave.
If heave is for example the car location in height, you don't want the car go up a mountain and your rig goes out of range.
What you want is the road detail, so let's use the high pass filter in that situation.

BAND PASS FILTER
Band pass filter is the combination of a low pass with an high pass filter
In a low pass we let pass only the low frequencies.
In a high pass, only the high ones.
In the band pass, we let pass the frequencies between those two filters.
band pass value = original value - low pass value - high pass value
In the interface you set the number of samples to use in the low pass filters used to calculate both filters.
A band pass filter will look like this (surge input in LFS with band pass filter using 40 samples for low pass and 3 samples for high pass):

What we can see is that we preserve the small details and the large amplitude peaks.
If you take a closer look, it works similar to a washout filter.

BAND STOP FILTER
Also a combination of the low pass and high pass filter.
But the opposite to band pass.
band stop = original value - band pass value
A band pass filter will look like this (surge input in LFS with band stop filter using 20 samples for low pass and 10 samples for high pass):


WASHOUT
It's a Low pass filter combined with a high pass one.
The low pass smooths the last values and the high pass get's high frequency from the new ones.
The result is the addition of the two, making the signal go near zero (not zero but the result of the high pass that gets values near zero) constantly.

Im going on now so will give it a try.

I have been using bandstop filters so i can get the longer ranges and then the jerks but not too much jerks if you know what I mean

Oh, my God! Oh, my God! Can't wait to test it!
I'm already so busy this weekend. Damn!
I'll be loosing sleep.