FlyPT Mover 3.5.3

Try to change the USB port on the pc for one of the Arduinos
Some usb ports share the same bus and might be saturated. That's strange, because this would be a problem in old hardware, not what we have today.
You could try the latest build to see if this works better.
Download here: https://github.com/FlyPTMover/Releases

Setup is not compatible, you have to make a new one and I will have a new build this week (2 more days)

I still don't see some controls even with scaling.
Do you have any plan when you are going to update the Rotating 2DOF rig?
Thanks.

Thanks again for your help.

There is some progress and maybe now there is more useful information.

I was able to get it all to work... but then one set of motors stopped responding after about 10 seconds. I don't get any errors on the screen. Also no errors on the drivers which are connected to the motors.

Next release It's done, but need to solve some bugs in the Recorder/Player, I'm in the middle of that one...
Hope to have it tomorrow.

After an afternoon of searching I'm still sort of stumped. FlyPT is pretty easy to integrate with Thanos or M4S boards. What i need to do is control a single BLDC with a Direct output from FlyPT. Is there a motor controller such as the VESC Minim Odrive etc. that can accept the serial stream from Mover and output a proportional torque? If not I assume I need to have an interface board between mover and my driver?

Updated to 3.7.0.15, rotating 2DOF looks good now.
Thank you so much!

Hi.
Noticed another small bug in 2DOF rotating rig.
The L1/L4 tooltips say "distance between two crank/rod joints" but it really draws the distance from the ujoint zero plane to the crank/rod points (and I suspect it calculates that internally the same way).
It does not cause any issue, I've just entered 0.5x value here.

Also the Actuators yaw/zero/tilt value fields are shifted up a bit, but it is just a cosmetic issue.

Corrected for next release, L1 and L4 are the distance between rods. You need to change your setup on the next release (no 0.5x)

sorry

No problem at all, will be glad to have it fixed, thank you for your work.

Hope I'm not annoying.. )
Found another a bit more serious bug - the 2DOF rotating rig doesn't save several actuator-related settings:

Independently on how you set states of these checkboxes and save as a local or a default setup - when you load your setup later they will be in this state.
Unfortunately I need another state of them so I have to fix it each time I load my config.
It would be also very good to include into the next release if it is possible, thank you in advance.

Just came back from a year abroad and i had to reinstall due to some errors. I noticed FlyPT_SimTools_to_Mover_InterfacePlugin.dll dosent seem to work with simtools 2.6.1 Not a valid interface plugin. Looks to be the same on 2.5.1


I need it for traction loss. Any quick fix for this and is a Simtools 3 interface plugin out there somewhere?

I used chatgp to figure it out and i had to right click the dll choose properties and unblock it from a check box. Now its working as it should

"That error means the FlyPT → SimTools interface DLL is incompatible or blocked.
Most common causes: wrong SimTools version (v2.x vs plugin build), missing VC++ runtimes, or Windows blocking the DLL.
Fix: install the exact plugin version for your SimTools build, install VC++ 2015–2022 x64, right-click the DLL → Properties → Unblock, then restart SimTools as admin."

Been getting intermittent fail on startup. I assume it has to do with the cloud .mover server as when I click continue it goes to a dialog to share/update unshare setups........

Happen on all pc's I have mover 3.5.3 on.



See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 85.247.73.169:80
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
--- End of inner exception stack trace ---
at System.Net.WebClient.UploadValues(Uri address, String method, NameValueCollection data)
at Mover.Setups.SaveSharedSetup.Exists()
at System.Windows.Forms.Control.OnVisibleChanged(EventArgs e)
at System.Windows.Forms.Form.OnVisibleChanged(EventArgs e)
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at Mover.BaseForm.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9323.0 built by: NET481REL1LAST_25H2_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
FlyPT Mover
Assembly Version: 3.3.4.0
Win32 Version: 3.3.4.0
CodeBase: file:///C:/Users/erik5/OneDrive/Desktop/FlyPT%20Mover.exe
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9321.0 built by: NET481REL1LAST_25H2_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9319.0 built by: NET481REL1LAST_25H2_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
MySqlConnector
Assembly Version: 1.0.0.0
Win32 Version: 3.3.4.0
CodeBase: file:///C:/Users/erik5/OneDrive/Desktop/FlyPT%20Mover.exe
----------------------------------------
System.Data
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Transactions
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/System.Transactions/v4.0_4.0.0.0__b77a5c561934e089/System.Transactions.dll
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9221.0 built by: NET481REL1LAST_25H2
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.