FlyPT Mover

@Bastiuscha .Hey, do someone have a nice "nolimits2" Moverfile for me? Could be nice, someone with a 6DOF linear Actuator Rig

Hi sorry for the delay !!!
See it if you like !

are you using the latest mover version? when i open the file, i see the windows flash briefly and then disappear. as if the program opens briefly and then closes. but it stays open im unvisible task . then i have to kill it in the task. if you are using the latest mover version, could you limit the file to? the "poses" modules only? delete the rest. maybe it will work then.


Edit: Anyone else can open this file, with the latest flypt?

Everything is shielded, filtered, not close to anything, on different circuts and grounded so there no real reason for it. Gravity takes care of lowering and it goes down not up when it has an issue. You see a quick -400 on the actuators before it sits on 0.

If i reboot and just run it it will kick out. If i press reset on The ard and cycle on off in mover before starting it generally works. It dont make much sense.

Hi all,

I'm back on my rig after several months having to manage other priorities.

I'm currently moving away from Simtools towards a full FlyPT setup for my 3DOF + Surge + TL.

On surge I'm finally getting to a configuration I like, more on this in a few days after further testing of my solution following the discussions we had here a few months ago.

I'm also now investigating the TL, trying to move away from Simtools and its "Extra 1" solution. I understand that for TL the goal is to use "the difference in the way the car is traveling vs the the way the car is heading." but how does this actually translate into raw data collected from the RF2 source for instance? How to actually get this input as data to then go through a Mover washout filter?

Any advice/configuration detail you could share in order to avoid a pure "Yaw" input that I understand is not the best/most adequate for TL?

Thanks
Best
Alex

I get this error while opening the file.
Then all windows close but Mover continues to run.

Hi watch out, the problem of packets bust is on UDP also, not only by serial. Via serial I can catch the pachet easier with that oscilloscope but the problem is via UDP too.

Hi, been strugling here with this one.

What you saw is just hapening when we have the rig out of range / singularity?
That jump in value we spoke days ago, might be related to the fact I hold the last "good" position, and only change it if we are again in a "good" position.
I mean, "good" position is a position inside the actuators range and without singularity.
You can enable/disable this here:


Could you test to see if the problem is here.
Because the threads seem okay.

Meanwhile I added float output to the poses and rigs at the same time I verified the code for an hole in the thread.

Hi, I always leave uncheck this option in order to reach the best position the rig can reach although some actuators is at their limits. I leave furthermore the temporary configuration file of my rig.
Keep in mind that the strange behave are two, one is e continue micro burst showed in the oscilloscope which makes the rig vibrate very strongly, about this take a look at this video

where you can appreciate the vibration which is not caused by the game because this happen also from the joystick (the output is UDP), and the other behavior is the big packet burst when the singularity is reached, about this second behavior try with the joystick like in the video I showed earlier, perhaps the problem happens only with this source.
If you need other proofs just ask me
Thank you

I did another video to try to explain the burst in singularity position. Keep watch that not always the platform in singularity position freezes and then burst but seems only when is in an extreme and singularity position.

hi flypt,

Thanks for your ongoing efforts, amazing work and each version is getting better! I personally like the simple pose option as it gives me a good baseline to work from.

Couple of things though:

- I'm using thanos board V2.09. I cant update to newer version since it wont hold changed settings anymore for whatever reason so I had to revert to the older version. Its the most recent version that works on my board. To be able to modify those settings trough mover is a good idea, however it doesnt work in my case when saving those settings. Could that be related to the older firmware? No biggie just curious. Actually the only thing I would need to play with would be filters, the rest is one time setup anyway. I think if you would make an adjustable crashfilter in mover there is little need for remote thanos adjustment.

- The order in which the actuators work is now different. I saw you changed that a couple of versions ago, but its still not the most logical order. Also no big deal, I just swap connectors until it works correctly. I ended up with:
thanos 1 - actuator 3
thanos 2 - actuator 4
thanos 3 - actuator 1
thanos 4 - actuator 2
thanos 5 - actuator 5
thanos 6 - actuator 6

- For instance in F1-2020 you have flying laps. The moment you appear on track, the rig jumps. The transition for sources doesnt apply for this situation because the source is active, but just transmitting zeros while in the garage. Using thanos crashfilter with aggressive settings for it is a poor workaround with undesirable results elsewhere so I dont do that. Possibly you could make a soft start for x seconds when an active source which hovers around zero becomes suddenly active. Of course I can just disconnect the rig with the switch, it will move down to park. Then push button to go back to standby position and then flip the switch again to connect. Then it will have x sec transition and all is good, its just an elaborate procedure. Also not a must have obviously, but a suggestion.

- With buttons the main gain in "rig" can be adjusted. However there are no limits on that and it also can go negative. I would like it to be maximized with an (adjustable) value and it should not allow negative values. I had a kid getting a hold of the keyboard and my rig almost jumped trough the window......

I noticed similar unpleasant jumps in fs2020 while coming back and forward from menu to the game.

concerning the Thanos order, I think we should move back from :


thanos 1 - actuator 3
thanos 2 - actuator 4
thanos 3 - actuator 1
thanos 4 - actuator 2
thanos 5 - actuator 5
thanos 6 - actuator 6

to:

thanos 1 - actuator 3
thanos 2 - actuator 4
thanos 3 - actuator 5
thanos 4 - actuator 6
thanos 5 - actuator 1
thanos 6 - actuator 2

in order to keep the compatibility with BBF software.

I remember talking about the issue you have with newer firmware and I remember seeing the screen showing some of the buttons or the force offline was acting up... did I arrange replacement board for this issue? Remind me...

@Thanos No we didnt talk about this, I was just in the process of updating yesterday and encountered this issue. I have board V1.1 date 6/28/2019 and it works fine on software v2.09. With V2.11 it doesnt hold stroke and pitch. It doesnt show the "save settings" anymore. When reverting back to v2.09 its all fine again.

Can this software drive IBT-2 boards? 2 of them, maybe? Or is it just for the Monster Moto shield?

Anything controlled by serial, udp or shared memory, with decimal or binary output.

When will the FlyPT new version come out?

Still working on it (version 3). Trying to solve a bunch of bugs and user requests.
It's taking more time than what I want. Last months made be travel quite a bit, so everything is delayed.
Really sorry.

Mover 4 will take some more time.
Last work was on transducers and I think it's already good on that area.

Hello FlyPt,
After tests, I noticed some bugs (maybe I just misunderstood some things) into Mover, sorry per advance if someone already reported them. Have a look of my mover file.

When you uncheck boxes of a loop when it is not connected, and the pose motion does not get the loop, the platform moves.

The output string in the "output thanos" module is badly configured when using the "rig rotary hexapod”.

« We filter the received pose values and send them to the rig, what we have extra here, is that we mix the longitudinal and lateral accelerations with pitch and roll.

Why? Because it's a way to cheat the brain, to make us feel constant accelerations. »

I’m pretty sure it’s not working on BeamNG Drive. If I go straight, the rig will just move in the beginning and then, nothing at all.

Hi @pmvcda its a silly one to ask but , for some reason i can no longer get Mover to import the FS2020 data, Has something chnaged? am in the only one with this issue ,, the system has been working fine but not used for a while , thier have been a few Microsoft update so im wondering if this has created a problem with FS2020 and Mover , i also noticed that Now for a reason i dont Know , when i plug in the Thanos AMC controller the it Kills the Saitek Yoke the LCDust wont allow both to be connected without thus screen on the Yoke flahes on and off sorrta indicating that the usb Line is dropping out ? if i connect each device individually they work perfectly they just wont play nice if both are connected ( im using a Powered USB hub so assume the Problem should not be supply related)
im Gonna Post this on Thanos's Discord as well just for some feedback .. Mover works Fine with all my other Programs so dont think its an issue with Mover just FS2020 in this case Cheers