Gabor Pittner build thread

I have 3 interfaces with 2 motors per interface. Every motor is an axis, but how can I setup the correct order of 6 motors/axes on my stewart platform? And witch one has to be the first, (front left for example)
Is there any tutorial or manual of that? Point me please there.
(I designed the rig for Thanos AMC1280USB board, but its not relieable with analog output to sabertooth yet.)

Since DIY has almost endless possibilities so does Simtools. So there is not a "correct order" so to speak. But however you do it Simtools can work with it.

But yes this is off topic so start a new thread or ask on another thread if you want additional info.

I have mine setup so axis 6 and 1 are on COM1 (Front left and Right) , 3 and 4 are on COM2 (Middle Left and Right) , 4 and 5 are on COM6 (Rear Left and Right)

Like @BlazinH says everyone is different and they can all be setup up however you want If you have yours setup the same as mine I can share you my profiles if you like

Of cource I would like it I have another barrel of beer for you too...
But how can you tell simtools that wich axes/motors wich side located on your rig? And how can you tell simtools the dimensions and parameters of your rig? Have I missed something?

@BlazinH I've been thinking if there is a chance to make an SMC6-SPS code for Arduino Mega with 6 motors. I think we need another utility to configure those 6 motor's though. Unfortunately I don't know much about arduino code, so Im just curios if an arduino can control more motors than 2 like @zigzag49 setup.

When Sabertooths are using packet serial mode like SMC3-SPS uses you can run 16 motors from one serial port. So a Mega can run up to 48 motors and still have one uart left to communicate with Simtools. It can do 16 more motors if you use software serial also. But note I said run, not control. It one thing to send packets to make 48 motors move but quite another to have robust PID control of them.

The original SMC3 sketch controls three motors in total and was optimized for doing that. Adding SPS support made the sketch work even harder though. Therefore one motor was removed to give time for serial communications to operate. Also since the sketch technically supports Sabertooths only, and they are dual motor controllers, it doesn't make a lot of sense to have a third motor without a forth also. So instead of adding more and more motors to the same sketch and degrading the PID for each motor its much better to use multiple arduinos and therefore use much more computing power since Simtools doesn't make you use a single output interface.

SOrry totally messed up with what I set my axis lol I must of been on aanother planet ..............this is how they are


[A<Axis6a>][B<Axis1a>] are on COM1 (Front left and Front Right) ,
[A<Axis2a>][B<Axis3a>] are on COM2 (Middle Right and Rear Right) ,
[A<Axis4a>][B<Axis5a>] are on COM3 (Rear Left and Middle Left)


All this might not be of any use if this all works out well https://www.xsimulator.net/communit...rface-for-linear-actuators.12859/#post-169502

I am about to test very soon

Thank you for your explanation. It's clear now.

Ahhaa, there is a FlyPT interface I haven't noticed yet. Im jumping to dive in it Maybe it helps to understand how it works. Thank you too!!!! Im getting to fill the barrel

I can see your axis6a is your front left motor/actuator, but how does simtools know that? What if I wanted to axes1a to be front left motor? How can I tell it to simtools... Sorry Im getting confused

Like this

OK I get it, but what I don't understand, where is axis6a declared to front left? What if I want to axis6a to be the middle right? How can I do this? Sorry for confuse you

You just use axis assignments to send which dofs and how much you want to axis6a, no declaration is needed.

@Gabor Pittner sorry I forgot to post my axis settngs. This is what I use for car games, hopefully maybe of some use

I just asked because you use 1ms delay. Can arduino uno work with 1ms delay? If I remember well 10ms is suggested delay with uno.

10ms will give 100 telemetry updates per second which should be enough but you can send more if you wish. The arduino will only process what it can keep up with though.