Showroom FlyPT - 6DOF Brushless DIY Actuators

Many thanks to you ...
I have my road map for my g seat !
As I got for the moment just one actuator I will setup it for acceleration as you propose and test .
And after will try to use an electro valve ... but I can’t supply it for the moment ...

If you get the valve, tell me, we can make the code for the Arduino/ESP32 together.

Thanks for your help !

one question Flypt ,
I 'm trying to setup as you described in the previous post .
i use milti direct and my question is about the name of the actuator . In your exemple you give the name of the actuator '' right '' and ''left '' . My question is about the communication with esp32
As i want to test acceleration i setup longitundinal acceleration which I named '' Acc '' .

Did i put in the string <255><255><Acc> or did i name the multi direct '' Axis1a '' ? because in the arduino program you gave the string inside the program as <255><255><Axis1a>

With multi direct I didn't understand how you make the relation between the multi direct key name used and the Axis1a or other if there are other axis2a axis3a etc . I not yet understood this clearly .

And if i use Multidirect i don't need the actuator as rig pose right ? I have to delete it ?

Thx

yes ok understood . The solution works with :

- multi direct axis name : Axis1a
- deleted actuator rig pose .

And yes it works ... You're hardware and software are so amazing so so amazing

No, you don't need the pose.
When you change the name, if you have an output, it will change there also.
Names should be unique.
The output string should have the name you gave to the actuator.
Imagine you had 2 directs, onw for sway and one for surge.
You can give them any name.
But it should be unique.
The in the string you select wich one you want to use.

Answered after your last post.
But just to reinforce, axis1a, axis2a... Are default names, you can change them.
Use small names, it's faster to identify the actuator that way.

Ok will test !

tested ! yes cool

And it's so easy and simple when you explain !!

tested with LFS and great . It's works really great as wanted for acceleration Perfect !!
Fir the setup i diden't use the cubic 3 because nothing happens on output .
So range in multidirect for acceleration from 0 to 10 m/s2 .A littlr bit strange but in telemetry the acceleration is in this order of values (may by scale down 1/10 ? ).
And for the filter i used so mincrop ( to avoid braking as you setup ) and classic Emalp for smoothing ( my screw won't support if no smoothing ahah ) .
If you have an idea to smooth gear changes it would be welcome . During gear changes a little bit harsh .

I'm really happy because it works as expected . Will give a try soon on my 6 dof with headset etc .... very anxious to test !!

and here the test , not with LFS but the test before with loop function .

Ok got it , you will find attached the setup for only acceleration with LFS and which works pretty well . I reduced the harsch gear change using EMABS as proposed into the great manual for filters given by Flypt software .
MINCROP(EMALP(EMABS(VALUE;10.000;100.000);200.000);0)
The feeling is really great !
Thx

hi flypt ,i 'm trying to test my actuatyor on my 6dof.
- i installed driver 212x VCP
-setup the serial
- launched the connection

when i switch on my actuator (psu unit ) the calbration sequence runs well but as soon i switch on the power this error comes in mover and app freezes ! any idea ?
Look at the pic

... Oh, just told someone in PM that he was the first complaining...

He had a bad serial cable.
Are you sure the Thanos board is connected to COM7? Please verify.
Same for the pneumatic actuator, verify the port.

I have an usb extender ... I know that is not really great .... will try without it if it’s possible and report !
Yes sure for the comport because in device manager com7 is identified as silicon vcp driver .

Tested without the usb extender and with usb2 or usb3 plug and the error comes !
The cable I use was the same I used to test my actuator on my laptop !
Now I’m plugged on my pc tower with all stuff , Thanos board , direct drive wheel and more .
Edit : I don’t use a powered usb hub , I tested with a direct to pc usb connection

If it's not powered, it can be the cause if you have to many devices on the same port.
Try with direct connection

EDIT: Sorry did not read as I should. It's not working with direct also?

As I said I don’t use a powered usb hub .
But I tried with an another usb cable and i got no error after calibration and a few seconds after ... an improvement because with the other usb cable the error comes quickly !
But same result error comes , a little bit later but comes ( 7 seconds ) !
And Mover freezes and after you can close it .
And when mover stops to freeze and you try to connect the error comes immediately . I have to close it .

I’ve got an another Thanos board .
Tomorrow I will use my laptop ( with one I tested the actuator ) and connect Thanos board and esp32 , and watch if I’ve got the same issue .

Hi Flypt ,

So i tested with the following conditions with my pc tower used for my sim rig with following equipment :

- thanos board , usb serial ( the one i have in reserve , it's a newer comparating the one i usually pluged to my sim rig) , so i tested the 2 pc with this new one thanos board
- direct drive pluged also usb serial
- esp32 usb serial and the power for the actuator switched on
- win10
- rift headset (only plugged not used )
- mover 295 programed with esp32 and thanos board and test driven with loop function to generate movements
- direct connection for usb serial ( no powered hub)

My laptop :

- thanos board , usb serial ( the one i have in reserve , it's a newer comparating the one i usually pluged to my sim rig) , so i tested the 2 pc with this new one thanos board
- esp32 usb serial and the power for the actuator switched on
- win10
- mover 295 programed with esp32 and thanos board and test driven with loop function to generate movements

i used the same usb cable .

It works with my laptop ,and not with my tower , today the actuator made one or two cycles and after communication error happened !!

I don't really know how to solve this ... any ideas / help are welcome !

I could unplugged my direct drive and test ok ... try to remove the maximum devices and watch if there is an improvement but after what to do ??