FlyPT Mover 3.5.3

Hi Guy’s ,
Need to restart an old 2 dof sim and would like to know the serial to enter in the software .
It’s for an old Thanos board amc1.6 aahah lol my first tries for a sim !!
The serial string was to comunicate with xsim : AB~255~~a01~~a02~
If Thanos could confirm if it will work with fly mover software ?
Thx

From a post in the forum (here) :



@Thanos could confirm.

I have a slightly jerky behavior with @Thanos dedicated interface.

It’s all right when “high precision” is checked.

If I want to avoid a high load consumption I have to uncheck the “high precision” mode and increase the interval loops to 2. (4ms) in the regular serial interface.

That’s what I am observing;-)

Are you sure that in the low resolution it keeps showing the 2 or 4 ms?
I'm working on the new build, making some optimisations and changes. Might have the new build ready for tomorrow,

I have a slightly jerky behavior with @Thanos dedicated interface.

It’s all right when “high precision” is checked.

If I want to avoid a high load consumption I have to uncheck the “high precision” mode and increase the interval loops to 2. (4ms) in the regular serial inter

I saw there 1.6 but after some manipulation it went to 4. I am talking about serial interface timings

Ok, will take a look.
There's some bugs in the current build. Think I solved them, but needs more testing and some cleanup.

Wait it seems fine if you restart

Ah, ok, that's just a visual problem.
But you say that you notice a jerky behaviour in the rig.
Are you using rpm?

There's some problems with transitions that I'm working on right now.
I'm making them softer and trying to optimize them.
I'm also thinking better on how to make them... Some doubts.

Edit: sorry, do you notice it only in transitions or also after the transitions?

Oh yes jerky transitions are a good symptom if you went to low with the timings. I didn’t know that the serial interface and mover timings are interdependent.

But actually it seems there is always a way to avoid them by not going to low with them.

Timings are related.
The frequency that data is sent on serial, is a multiplier of the calculation speed.
That's what you set in the output module.
So if you have a calculation time of 0.8 ms
And use a multiplier of 2, it means data is sent on serial at 1.6 ms.

The idea here is that there's no need to send the same data two times if the serial is faster than the calculation (abnormal situation). So you cant set serial under calculation speed.
Also the opposite, what Mover does is if you use a multiplier of two, it sends data in first calculation. Doesn't sent in the second, and sends again in the 3rd.

Now, I can make it send at any rate if you find it better, but the frequency of the value sent is not the same of the calculation and values sent can be "old" or "new" in the time of calculation.
Exaggerating, with a calculation time of 10 and sent time of 12:
0 to 9 - 0 delay 0
10 to 19 - 12 delay 2
20 to 29 - 24 delay 4
30 to 39 - 36 delay 6
40 to 49 - 48 delay 8
50 to 59 - Missed value
60 to 69 - 60 delay 0
70 to 79 - 72 delay 2
80 to 89 - 84 delay 4
90 to 99 - 96 delay 6
.....

Here you see the delay of the sent data relative to it's calculation. You reach calculation made at 40 ms and she's sent at 48, 8ms after calculation, when in 2 ms we are getting a new value.
In my thinking, I want to keep rates and delays, but could be wrong.

Oh it’s a bit complex. It definitely helps understanding whats going on there.

Maybe something useful to put in the manual.

No idea which config is supposed to work better.
All two settings seems valid in my setup.

Tested with rpm code I am getting similar results.

Maybe I like better 2ms interval loops / 0.1 calculation rate.

Hard to say. One has to test it with a scope.

@Thanos, maybe you could give it a try to see which config is more suitable. (experimental 2.8 build)

@hexpod ,
In my opinion, you don't need to make more calculations between serial updates @ 2ms rates. It's already fast.

What I am sure about is that if you set the loop interval to 1, you may not go below 1.1 in calculation rate and vice versa, if you want for some reason to set the calculation rate below 1.1, you may want to set the loop interval below 2.

Otherwise you destroy the motion smoothness.

Thanks

I don't know how the board works internally, but she might not get all the data or may have the data corrupted bellow the 2ms. I know @Thanos talks about 2ms as the minimum to be on the safe side.
And that's pretty fast. Now you can have 0.5ms calculation (only in high precision) and send info at each 4 calculations.

Low precision works in 1 ms steps, so minimum there is 1ms even if we set it to 0.1. The value is rounded to the next integer.

If you transmit faster than 2ms, the AMC controller might still be processing the last position, and will miss the start on the data packet. Essentially will skip the whole packet, until it reads the ID bytes once again.

Thanks
Thanos

I currently have a DOFreality 2 dof sitting idle as AFS2 flight sim no longer communicates with sim tools.

I want to be able to mimick turbulence effects when flying airliners, and was wondering if this software would provide a solution?

Thanks in advance.

Hi,

For now, we have direct connections to X-Plane and dcs. X-Plane is more advanced, but still wip.

You can now add noise for vibration, but maybe not how you want it. But I can try to generate something random.

Xplane has noise fir stall, air brakes, landing gear deployed, engine rpm...
So any ideas are welcome and I can try to add it.