FlyPT Mover 3.7

So after successfully getting a gear motion as suggested by @GTakacs, I am trying to get a more lean curve as my current acceleration is too harsh. My actuator range is from 118 to 164 in bits. Still using post from motion, my question is:-
1) how can get more lean curve when accelerate, and remain normal speed when braking. In which motion should i insert the filter? Surge/pitch/ both surge & pitch( as I am combining them in post from motion section).
P/s : I've tried something like IF((Value>0;Emalp(2000,0),Value))
I cant remember the exact syntact, but i tells when my surge(motion) > 0 indicate accelerate, emalp the surge value, else, the value remains.
Im not sure if my understanding in mover's IF statement is correct.

Without using IF, when I just put emalp 2000 in the some of those filters, i can get the slow and lean movement, but it is for both acceleration and deceleration, which is not what I want.

Just some news...

Been strugling with the serials for some days, but I think I got it working finally...
So the idea was to reuse the received data and for example have an output sending data to the rig and a source receiving data from the rig (for those more into this, you might know what I want to do...)
Resuming, have the serial port used in multiple modules

So there's no Thanos or M4S yet because of this...

Some more days and we have the new release with many bugs solved, updates and features... Please be patient.

][C]

I don't get movement, what else should I adjust or change compared to the previous version 3.5.3?

thanks for your help">
I already changed the smc3 code to adjust the speed, change the output to the other format, exactly like this:
[A<R0.A1.B>][B<Ro.A2.B>][C<Ro.A3.B>]

I don't get movement, what else should I adjust or change compared to the previous version 3.5.3?

thanks for your help

I already changed the smc3 code to adjust the speed, change the output to the other format, exactly like this:
[A<R0.A1.B>][B<Ro.A2.B>][C<Ro.A3.B>]

I don't get movement, what else should I adjust or change compared to the previous version 3.5.3?

thanks for your help

Hi,
Sorry, there's a bug on the the output when using bit values, specially in decimal/ascii format.
It's solved for the next release, but i also changed some of the serial code for optimization, feedback and multi module use. The next release is almost ready, but need those changes working to achieve the pretended results.


Edit: Really sorry for making you change the code, but i detected the error recently while testing the odrive output

Thank you very much for your prompt response, I will be attentive to the new settings

Sorry for my late reply!
Yes, we need the two << before the actuator value. Think about an actuator with 10mm pitch ballscrew and 400mm stroke. So we need 40 turns! This is higher than 10

The links in the google drive for 3.7.0.4 has a virus and google drive won't let you download the file.
Good work i look forward to the actual release after all the features are added.
Keep up the good work.

Can confirm, I can no longer download it either, it was downloading before.

The whole automatic virus protection is getting more and more rediculous! I develop software myself. I had to stop using the latest compiler because Windows complained about EVERY compiled program to be (alledgedly) infected by a virus. I had to switch to an older version of which the "footprint" of the compiled executables was already known to the virus scanners.

Some years ago it only costed ~$40 to get a digitally signed certificate to mark every released executable as safe. Now the "highwaymen" want >$200 and every single executable costs extra.

Ok guys, any idea how to work around this problem?
The antivirus are becoming a nightmare...
I'm 99% sure the files are clean. What can I do? Don't have much experience with this.

Edit: They are all marked with virus now...

Put them in a password protected zip file and share the password. Automated tools won't be able to unzip and scan them. We just have to trust you

Results from online testing on 3.7.0.4:

Mover 3.7.0.5 BETA

First of all, sorry for the delay.
Got many problems with serials, seems solved, still some small bugs.
Also, due to false virus warnings in Google drive, we now need a password to extract the files from the download.
Use: Mover

Release notes:

General:
New menu code to avoid the Windows default shortcuts behaviour (interfering with hot keys).
Most of the diagram connections are now enabled (ui is slower and needs optimization).
Added custom variables. We can now define an operation or variable and give it a short name to reuse it in multiple places (Menu->Edit->Custom variables).

Solved several nasty bugs in hot keys.
Solved several small bugs.
Enabled Mover version verification on startup (adds item to the menu to download the latest release).
New serial code allowing when possible the use of the same port in multiple modules (sources and outputs).


Sources:
Added F1 24.
Added slip angle to sources (angle between vehicle dislocation and vehicle direction, good for traction loss).
Added Condor 3.


Reworked the WIT source with new serial code a better error handling.


Poses:
Work on the rpm source to solve vibration on disconnect transition. Still not solved!

Rigs:
Added linear 2DOF rig.

Transducers:
Multiple internal changes in transducers, preparing the new dedicated modules.

Outputs:
Solved bug while generating byte array sent to the hardware
Added Thanos output (1st iteration with new serial code)
Added Motion4Sim output (1st iteration with new serial code)


Online manual:
Started compiling the info for the updated manual.

Know problems/bugs:
Slow and unresponsive UI with many diagram connections
New bugs somewhere
Old bugs somewhere
Still missing many modules

Download link is same as first 3.7.0 release.

"No access to download"

Sorry...
Should be working now.

Ok for download, but always no 500000 baud and no swap for only one motor in 2 Dofs.... i can't test for my platform....

Oh I missed the swap... sorry.

The baud rate is now editable. You can manually insert the desired value or select one of the most usual defaults:



...Kept speed in the label. I wanted to change it to baud rate...

Some things i am finding with 3.7.0.5:

• RWASH filter is gone
• Missing: Pose From noise generated by value
• Arrow from Rig to VR Motion comp doesnt draw, with rig selected
  
• When connecting an output, the corner does not turn red until the module's window is shown
• It can't find my COM6 arduino for wind (mover 3.5.3 finds it)
• Pose: from RPM should have a selectable source (engine rpm, prop rpm, or any other var)
• Options: Transition times, UI darkness do not save

Just a note: Wasn't able to update to 3.7.0.6 on two systems. On Win11 the slider runs to 100%, but that's the end. I had to manually closing the window without seeing any change.
On Win10 the updater window and the app window actually close, but no automated restart. Nor do I see new or updated files.
Edit: Obviously I'd need that UDP fix...