FlyPT Mover 3.5.3

Server problems (3.5.2)

It's now running again. Soon 3.7 will have the server enabled hopefully solving this problems.

version 3.5.3 still does not work, "unable to connect to remote server" does not connect via Thanos

Cick on Continue, wait a while then click on Continue again.

Sorry for not going trough whole FlyPT posts as there alot, where to find how to run 2dof guide....do i need new script for my arduino

sorry for a nob questions

How do I reverse motor directions? I'm building a 6DOF rig and half of my 6DOF motors are rotating the wrong way. 3 motors have "swap" enabled - so the 3D viewer looks correct. I tried disabling "swap" on one motor, then the crank went to a crazy position in the viewer, so I corrected the "crank vert. angle" (from 120 to 300) but then the motor is still rotating the wrong way. I'm missing something simple...

In the pose from motion - in gain/flip make the number a negative.

No, the problem was that some actuators moved in reverse, in the RIG, before the pose etc. I solved it by inverting one motor of the motor pair in SMC3.

You could do it in swap direction bellow the crank vertical angles

It made the motors flip in the viewer and crank would be on the opposite side. To make it visually tight, I had to change the angle by adding 180 degrees, but it didn't behave right anyway. Could be some other problem with my setup. Anyway, SMC3 change worked.

Can you write something more? I understand that the engines are working properly now after uploading another version of smc3.ino ?

Yes, I reversed the second motor on each board. That fixed the issue.
Checking/unchecking "swap" checkbox in FlyPT results in motor flipping to the outside of the frame (it was inside on my design), and so the crank reverses not only the direction, but an angle by 180 degrees. And if I then corrected the angle so it appeared normal in 3D View, the rig itself behaved incorrectly. But fixing it in SMC3 did the trick.

How do I match the range of motor arms movement to the FlyPT model? I have a DIY hall angle sensors that return arbitrary angle data, so the 6DOF system motors have a certain range (about 90 degrees) from min to max values (clip to clip), let's say 94 degrees (+47/-47). In the FlyPT rig model I specify certain sizes, and it expects to send a certain movement (2 degree for example) and get a 2 degree movement from the rig. But how do I make sure the actual movement conforms to expected movement? I think there's supposed to be a scale multiplier somewhere that's supposed to match the actual movement to expected movement, but I'm not sure where...

There's a scale option (in red) you can adjust to make it match.
The problem (just an example) is if you had 8 bits resolution and map them for a range of -90 to 90º, Mover doesn't know that. So you need to adjust the scale:



Now scale can be adjusted from zero degrees (middle) or the minimum position like -90.
This makes you match 5º in Mover to 5º in reality.

In the new Mover, you can map the bits to positions (in the controls near the one in red):


allowing any mapping or still use scale

Thanks for the quick reply! So I'll use the scale to reduce the range to fit the model.

Does anybody know how to get this rig design into FlyPT Mover?

It's a 4DOF linear actuator design, like the D-Mover H4:
Compact Motion Racing Simulator, 4DOF with Traction Loss, long stroke flight sim rig, high immersive G-force seat

I'm working on that rig for the new release.
And some other stuff. Might take some days yet.
Keep an eye here: https://www.xsimulator.net/community/threads/flypt-mover-3-7-0-9.19016/

Thank you for your swift reply and your efforts! Thank you so much!

With a 6DOF it's getting really annoying that FlyPT doesn't save the ports and they have to be reassigned on every launch. I vaguely remember there was an explanation for this. Why does it sometimes remember the ports, and other times doesn't save them? Is there a way to force it to save? I have assigned fixed ports to my Arduinos.

Share the setup. I will help you with a setup for the new Mover.

Thank you so much! Here's the file link: https://we.tl/t-BAKKmO24cy
Do you think the new Mover is stable enough to try on a real rig? I guess as long as it wouldn't send the random motion commands to random motors and crashes the rig physically, it should be fine...