Space Engineers

Space Engineers

30 ratings
SCAM miner guide for XU-3 (and not only)
By pro100tv
This guide will allow you to take the most out of SCAM miner script.
You can find the full list of commands in the argument reference guide by cheerkin: https://steamhost.cn/steamcommunity_com/workshop/filedetails/discussion/2572154209/4263206669447526543/
   
Award
Favorite
Favorited
Unfavorite
Initial setup
This guide will get you through the setup process of the XU-3 mining drone but most of the elements also apply to any SCAM-based drones.

You can find the drone over here: XU-3 Auto mining drone
The dispatcher is needed for the drone to work. You can find the basic dispatcher over here: Basic Dispatcher.
You can transfer the green parts to your own ship or station and make the mobile mining carrier out of it.

Initial setup:
  1. Spawn the station Basic Dispatcher
  2. Spawn one or more XU-3 Auto mining drone
  3. Take control over the drone using "k-menu" -> remote access -> control
  4. Press "3" on the toolbar to switch to control camera view
  5. Press "1" to enable mouse movement in the interactive menu
  6. Using "E" on your keyboard select the following: Menu -> Take control -> Take control
  7. Be careful, the drone will turn off it's dampeners!
  8. Quickly press "Z" to turn them back on
  9. Press "1" to disable interface
  10. Dock the drones to the connectors
  11. After docking press "Z" to turn the dampeners OFF

Upon world reload
Upon world reload or copy/paste operation you may notice that drones try to use thrusters to compensate for the mothership movement.
To prevent that select "Recall" from the main graphical interface.
Setting up the mining job
Now, when the system is ready, let's set up the mining job:
  1. Get to the mining area of your interest
  2. Align the station/ship/dispatcher perpendicular to the mining area
  3. Control any "autopillock-remcom" (sub-grid, marked on color in k- menu (yellow or orange for instance))
  4. Press "1" to disable interaction with the interface
  5. Press "4" to undock
  6. Fly the drone low, over the mining area
  7. Press "3" to select bottom camera view
  8. Press "1" to enable interaction with menu
  9. Select "Menu" -> "Start mining job"
  10. The job is set
Those steps are needed to be done only on 1 of all your drones, the rest will follow automatically.
Adding more drones
  1. Make sure that you have enough connectors named "docka-min3r" to accommodate new drones
  2. Recall currently working drones
  3. Spawn or print the drone (when spawning - make sure that it is low, over the flat surface)
  4. Repeat steps from "Initial setup" (from point no. 3).
  5. To plug the new drone into the network it is needed to set up a new mining job. To do that follow the steps from Setting up the mining job.
Do/Do not list
Do:
  • Preferably adjust any mining job parameters before the job starts. Doing otherwise will apply changes after the finished shaft.
  • After using the interactive menu on the drone with the mouse control function, press 1 on the toolbar to disable it. Otherwise, you won't be able to fully control the drone.
  • While installing connectors on your carrier, install them in a line, only on one side of the ship. Doing otherwise will cause collisions.
  • When starting a new job align the carrier's connectors horizontally with the entry of the shaft.
  • While starting a new mining job, align the carrier's connectors perpendicular to the shaft.
  • After changing the mining area or copy/paste in different location, set up a new mining job first. Otherwise while recalling the drones will try to get to the old location first.
  • If the drone gets damaged during the mining job, after fixing it, recompile a-min3r PB block on the drone
    Originally posted by cheerkin:
    That's not needed unless you absolutely lost one of crucial blocks (main gyro, remote, connector). Otherwise the drone would resume work as soon as you fix everything.
  • If you see any weird behavior, like a drone just hanging in the air, clear custom data of the empty "docka" connectors, if that won't help execute "command:clear-storage" and "purge locks" (the latter may cause collisions)
  • If you can't control the drone after undocking it from the station, turn off the gyro override (it's on the toolbar of the drone)
  • If completely changing the set of drones, recompile the station's PB block. It will update the list of active drones.
Do not:
  • Do not press "resume" or "recall" more than once. It will break the system.
  • Avoid recalling when some of the drones are docked. There's an issue with that function that may cause problems.
  • Do not resume while still mining
  • Do not copy/paste the drones during their task running
    Originally posted by cheerkin:
    Regarding dont's, resume/recall spam is getting handled better in latest versions. I totally see reasons for running resume if you have some drones that you are tinkering with, while having a task in progress. It's better to run commmand:mine for specific drone though.

    If you are copying a drone, execute "command:clear-storage" before that. The state is the part of the blueprint (it's stored inside PB).
Optional configuration
Optional
Setting mining job parameters
Before setting up the job it is worth to set up mining job parameters. It will help to increase the efficiency of the drones.
  1. Take control of the control seat
  2. Press "1" - now you have access to mouse-control the interface
  3. On the screen you can choose maximum shaft depth, skip-depth (the distance during which the drone won't collect anything to its cargo containers), max and min battery charge values, max fill of the cargo container, etc.
  4. Select the values that you find the most suitable for the job. You will see confirmation of the changes on the log-LCD.
  5. Now follow the steps from "let's set up the mining job"

My favourite configs:
  1. Max depth to x
  2. Skip depth to x
  3. Turn on adaptive mining (Drone's interactive menu -> timers -> adaptive mining)

Changing the drone display color on interactive GUI
You can change the color in which the main display shows your drones.
To do that take control over the particular drone, find the group that contains lights and change its color according to your preferences.
That will automatically apply changes to the GUI.

Changing parameter values
If you want to change the default values presented in the interactive menu, you can.
It's useful if you want to mine deeper than 50m or set maximum cargo fill for less than 50% for instance.

To do that:
  • In the drone's or dispatcher's "k-menu" find PB block "a-menucommand"
  • In the Custom Data of the block, on the left side of the line, after "DisplayName=" there's an argument description. For example: "DisplayName=skip 0m", skip 0m - will be shown on the display.
  • On the right side of the line there's an argument passed to the programmable block that will set the value for the drones. For example: "command:set-value:skip-depth:0" - will set the skip-depth value to 0
  • So let's say that we found uranium at 90 meters. We will add two more options to our default menu.
  • Add (important to keep the spaces): " DisplayName=Depth 90m;command:set-value:depth-limit:90" under "Depth limit" where marked values may be changed to your needs.
  • And " DisplayName=skip 80m;command:set-value:skip-depth:80" - to skip stone layer straight to the uranium deposit.
  • You can change or add any other values from this list: Arguments and values for SCAM
  • To know more about the menu configuration check out: Tree Menu Command NET
47 Comments
Lightbringer 11 Jul, 2024 @ 7:26pm 
Tried making my own carrier ship with scam capabilities, and the left most lcd (operating system) on my dispatcher doesn't display the menu.

Also when using multiple drones I've had to rename the drones menu screen (gave it a number at the end) then change the drones command block to match. Otherwise drones wig out after some time.
DeVice Null 25 Jan, 2024 @ 3:08am 
Could this work in 0.0G environment (i.e. Asteroid far enough from a planet) ?
WhiteWolf 27 Nov, 2023 @ 7:39pm 
Subscribed to the xu-3 drone and basic dispatcher. Having a few issues. The biggest is when controlling the drone the keys assigned to the PB show syntex error. On camera "menu view" and selecting "take control" nothing happens. It's my understanding i should get a new menu to select "take control" again. When flying the drone, dampners on, the drone slowly tilts and trying to turn the drone requires lots of mouse movement. Basically pushing the mouse right or left, to spin the drone, spines the drone half a degree or less. On both PB units I have tried to check code and recompile. Same issue. I have also rebuilt the drone just to try. Same issue. Not sure if anyone is still helping with this script after so many years but any help would be appreciated. Thank you.
Captain_Shadow10 18 Feb, 2023 @ 8:55pm 
Lol love the name
MaximalCrazy 19 Sep, 2022 @ 12:27pm 
I cant interact with the full side menu.
Timer not work and help not work.
If I paste it in the space, it work.
If I paste it directly to a station, it doesnt work.
Hardware group contains the "scam-gui" + "Wide LCD Panel".
correct?
pro100tv  [author] 18 Sep, 2022 @ 3:19am 
It's for the side menu to detect the LCD and cockpit properly
MaximalCrazy 17 Sep, 2022 @ 2:30pm 
For what is the "Hardware" group?
DimmyR 7 Sep, 2022 @ 5:15pm 
How do I prevent the drone from pushing the atmo carrier down when docked?
CobraJr._BOMSF 10 Aug, 2022 @ 10:09am 
Yes! They absolutely do help a tremendous amount. I'll give the XU-3's another try sometime later on. They just require a little more maintenance than I'm willing to put in them for the time being I think. Other than a few collisions with the XU-1's that were user error, they've been VERY helpful thus far. I can't thank you enough for working on these projects.
pro100tv  [author] 10 Aug, 2022 @ 5:39am 
The problem may be related to the fact that the interactive menu script is sometimes taking over different blocks than it is intended to. Undocking the drone and recompiling should fix the issue (probably till the next world reload).
I'm sorry to hear that you have issues with this drone. XU-1's are less problematic when it comes to configuration, and I hope they will help you to achieve your goals