MArmOS (Mechanical Arm Operating System) v3.1

MArmOS means Mechanical Arm Operating System and it is a script made to simplify the coding needed to properly control your mechanical arm. It allow to take any complex arm configuration and bind it on a ( X, Y, Z ) reference frame. Using MArmOS should make it way easier to control ground based machines like mobile mining rig. Since version 3.0, MArmOS has been completely rewritten from scratch to become as user friendly as possible while still offering the same functionalities and even more. Defining your arm is now as easy as to write a grocery list. There is now two way to define your arm: basic and advanced. The basic setup only requires you to define your hardware in order. It is perfect for fast and easy general use configurations. Note that the basic mode is sensible to the order in which you declare your hardware, it will not consider parallelism and it can only manage a single arm. In the advanced setup, you can assemble one or multiple arms manually and define precisely how you want the pieces to be linked.

Steam guide:

Clic here to see the steam guide.

Example collection:

Clic here to see a collection of examples.

Turnkey collection:

Clic here to see a collection of turnkey arms.

Features:

- Totally modfree - Easy to setup - basic and advanced definitions - ready to go default settings - Documentation inside the script - Welcoming ascii interface - Can read keyboard inputs - Can read mouse inputs - Control position - Control Orientation - Argument command interpreter - Compatible with the easy automation script - Allow serial arms - Allow parallel arms - Allow compound arms - Allow multiple arms - Allow custom relative reference frame - Rotor and piston override - Control rotors (also moded rotors) - Control pistons (also moded pistons) - RotorWheel settups - Control Hydraulic settups - Soft movements - linear Movements - MoveTo target command - GoHome command - automatic ingame tips and debug tools - Event Logs for debugging - abstracted structure to allow moding - Small grids - Large grids - Ready to use examples - Complete steam guide (WIP) - workzone Limitations ( eventual feature )

Control Module note:

This script once was compatible with Digi's Control Module. This is no longer the case since there is now a vanilla way to get inputs to the BP. Still, MArmOS wouldn't have seen the light without Digi's great mod. Here is a link to Digi's Control Module. Go give him your love.

Timer block note:

Before the 1.185 update of space engineer, scripts needed timer blocks to run. This is no longer the case. MArmOS will now start to execute itself automaticaly as soon as you compile it. I may update the tutorial to encounter this change someday.

Known bugs:

I tend to fix bugs has soon as I find them. But some bugs can be tough to fix or just not worth the effort. When it happen, I list them here. - [MP][spoiler]It seems MArmOS can't control anything that is not on the main grid in MP. Nothing was changed from my side and the rotor API was not altered according to @rexxar. I will make researches to find the source of this bug.[/spoiler] - [FIXED][spoiler]Congratulation to @Abou for finding the first bug. It look's like the script can crash if you run an incomplete command via argument. I'll fix it as soon as possible.[/spoiler] - [HOTFIXED][spoiler]When using parallel Joints, a blueprint will often "jump" when pasted. This is apparently caused by the new physic multitreading causing some rotors to load after some others. The hotfix was to add a "loading" timer into the script to allow the blueprint to fully load before starting the script execution.[/spoiler] - [WORKAROUND FOUND]The script won't receive any inputs from cockpits on a static grid. For some reasons, static grids will not produce any inputs informations. To work around this issue, place your cockpit on a rotor head or any subgrid.

Beta testers:

Special thanks to @Wrench and @Kristov Keen who acted as beta tester for version 3.0. Their feedback helped me to get MArmOS to it's best before release. Thank you both!