Guide: Spaceships: Difference between revisions

From Space Exploration
Jump to navigation Jump to search
imported>Grumphrey2
imported>Worloq
Line 170: Line 170:
A clamp can be disabled sending the red signal value 1 to the clamp (bottom connector).
A clamp can be disabled sending the red signal value 1 to the clamp (bottom connector).
===== Routing: =====
===== Routing: =====
*Simple back-and-forth
====== Onboard Back-and-Forth ======
*Multi-selector
 
Use two arrays of combinators located on the ship. Each array performs two functions:
:# Setting the guidance for the destination, and
:# Determining if the ship is ready to launch for the other location.
 
Note that the guidance must be a constant signal for the duration of the trip but the launch instruction only needs to be a single tick transient. See the [https://spaceexploration.miraheze.org/wiki/Spaceship#Spaceship_Console/| spaceship console] section in [[Spaceship]] for details on input/output signals.
 
First, determine how the logic will determine which destination is the next one. The most straightforward case is a ship that will load a single type of ore from one location (planet, asteroid belt, etc.) to transfer it to another location, and then return, possibly with some supplies for the mining base. Suppose the ship will carry 50,000 iron ore when fully loaded. The guidance can be set using a constant combinator outputting:
:# [[File:planet-orbit.png|x30px|link=|alt=]] '''999''', the destination ID on the correct channel (planet orbit 999)
:# [[File:anchor-using-left-clamp.png|x25px|link=|alt=]] '''222''', the ship's clamp ID to dock with (left clamp 222)
:# [[File:anchor-to-right-clamp.png|x25px|link=|alt=]] '''444''', the dock's clamp ID to be docked to (right clamp 444)
:# [[File:signal-speed.png|x30px|link=|alt=]] '''100''', the ship's target speed if less than maximum.
 
Feed the output of the constant combinator to a decider combinator that checks if the ship is full of ore, and outputs EVERY if true. Send that signal to the ship console.
 
For the launch signal, create a bank of decider combinators that check each desired signal and outputs a checkmark if true. Gang the output of the bank of combinators and check if the combined checkmark signal is equal to or greater than the number of signals being checked. For example, you might check that:
:# [[File:signal_A.png|x30px|link=|alt=]]333, the ship is at the correct location right now,
:# Rocket fuel in booster tanks is sufficient,
:# Stored bullets are sufficient,
:# Enough ore has been loaded into the ship's storage, etc.
 
The other array has the same two components for the return trip. The other destination is set by a constant combinator, which feeds into a decider combinator that checks that the ore onboard is zero, and outputs EVERY if true. Send that signal to the ship console. The console will see only one set of destination signals depending upon whether the ship is full or ore, or empty of ore.
 
Similarly, the launch logic can be specific to this location.
 
====== Onboard with Multiple Destinations ======
 
The back-and-forth logic can be used if and only if '''the destination can be determined by conditions on board the ship during flight''', because the guidance must remain constant during each leg of the trip. For example, an [[Ion_engine_(technology)|ion engine]] ship that carries a full load of ore from a mining planet back to a factory planet, but refuels at an orbital platform before returning for more ore can use the following logic to determine which constant combinator sends guidance signals to the console:
:* If the ore is full, pass the factory planet guidance to the console,
:* If the ore is empty AND rocket fuel is not full, pass the orbital platform guidance to the console,
:* If the ore is empty AND rocket fuel is full, pass the mining planet guidance to the platform.
In this case, the rocket fuel remains full during the entire trip from the orbital platform to the mining planet, so it can be used to discriminate between the second and third destinations. Here is the logic table for this example:
{| class="wikitable"
|-
!Destination !! Ore !! Rocket Fuel
|-
|Factory planet || Full || Not Full
|-
|Orbital platform || Empty || Not Full
|-
|Mining planet ||Empty || Full
|}
 
The guidance logic will require three decider combinators for each of the second and third cases. Thus, guidance for three stops requires a minimum of 7 decider combinators and 3 constant combinators.
 
 




{{Template:Guides}}
{{Template:Guides}}

Revision as of 04:54, 23 May 2024

(WIP - questions or suggestions can be directed to PeterHan5#1790 on Discord.)

Spaceship Systems

Power

Accumulator

Very short-range ships may be powered by accumulator only.

+ simple: easy to set up
- low-powered: available power is very limited.
- fragile: any event prohibiting travel or landing can leave the ship stranded and require an in-person visit
Solar + Accumulator

Adding solar panels addresses some issues of accumulators.

+ simple: easy to set up
+ low-maintenance: doesn't use any fuel or consume any items
- low-powered: available power is limited.
- bulky: uses a lot of space, and therefore hull integrity
- affected by solar yield: be careful as some areas may not have enough solar energy to power your defenses...
Rocket Fuel Engine

Switching to Fluid Isothermal Engines uses rocket fuel, but provides continuous power

+ simple: easy to set up
+ continuous power: generates constant power as long as you have fuel
- uses rocket fuel
Steam Battery

What holds a lot of energy in a small package? Nuclear steam!

+ simple: easy to set up
+ decent energy density
- uses a lot of cargo integrity
- no continuous power: must be frequently refilled with steam
Nuclear - Steam

Why carry around cans of steam when you can make it on-site?

+ good energy density
+ continuous power: good for long flights and high power usage
- bulky: uses a lot of space, and therefore hull integrity
- must be periodically refilled: condenser turbines only preserve 99% of the water used
- complicated: 2 kinds of fluid, and extra circuitry for efficiency
Antimatter - Steam

Fission Schmission, let's use ALL the energy instead of just a tiny part.

+ amazing energy density
- bulky: uses a lot of space, but at this point you have integrity to spare
- complicated: 3 kinds of fluid, and extra circuitry for efficiency

Cargo

Fluid tanks

Because you don't like having too many barrels

+ easy loading/unloading via underground pipes
+ carry twice as much fluid per stress (25K fluid for 12.5 stress, vs 20 barrels (1K fluid) for 1 stress)
- need pumps to fill or empty quickly
- may be slow depending on number of tanks
- only store fluids
Roll-on trains

Trains... burning coal... in space... what could go wrong?

+ easy input/output
- scheduling trains on multiple surfaces can be complicated
Logistic chests

Note: use buffer chests so logistic bots can both load and unload

+ easy loading/unloading via logistic robot
- may contribute to robot attrition
- may need a specialized logistic cell to load/unload completely
- may be difficult to control how many robots travel with the ship when it leaves
Normal chests - direct insertion

Direct insertion here means either long inserters over the wall or some sort of adjustable inserter mod.
(I recommend the adjustable inserter mod)

+ ...not much
- may be slow depending on inserter throughput.
Normal chests - belts

Space underground belts can tunnel through the spaceship floor and under the spaceship wall. Don't ask how that's airtight.

+ ... still not much. slightly faster than normal chests by direct insertion? maybe?
- limited belt throughput: 45 items/second with normal space belts.
- (if you're using deep space belts here, you need to think about your life choices)
- takes extra space... like 3-5 times as much space.
Static cargo cars - direct insertion

A static cargo wagon can be placed on 3 diagonal rails, and including a stack inserter, makes it a minimum of 10 tiles per wagon (if stacked next to other wagons).

+ doesn't use cargo integrity
- uses 5-6x as much space as a chest for its storage size
- can't connect to the circuit network to measure contents
Static cargo cars - belts
+ doesn't take cargo integrity
+ belts can measure I/O with some complicated combinator circuitry
- belts can measure I/O only with some complicated combinator circuitry
- throughput limited by belts
- takes even more space - like 2-3x as much as direct insertion cargo cars

Engines and Fuel

  • Spaceship rocket engine: uses liquid rocket fuel.
  • Ion engine: Uses electric power and ion stream.
  • Antimatter engine: Uses electric power and antimatter


Booster tanks and launching

Some kind of booster tank is required to launch the ship from any orbit, planet, moon, asteroid etc surface. Fuel is subtracted directly from the booster tanks when launching.

  • Rocket booster tanks: Needed to launch the ship, can take off from planets and moons.
  • Ion booster tanks: Needed to launch the ship, can only launch from orbit, asteroid belts, asteroid fields (already in space)
  • Antimatter booster tanks

The engines themselves serve for propulsion once the ship is moving. It's possible to combine different booster tanks and/or different engine types.

Rocket fuel tanks
+ simple: the standard way
- you brought enough fuel, didn't you?
Rocket fuel liquefaction

Why not bring the supply chain with us?

+ more dense fuel storage
+ can refuel with minimal planetary facilities
- the fuel plant takes space and power
Vulcanite block-> solid fuel -> liquid fuel

Why not bring the supply chain's supply chain with us?

+ even more dense fuel storage
+ can refuel with even less remote facilities
- twice the space, twice the power, unless you want to change the recipe manually

Raw vulcanite -> crushed vulcanite -> washed vulcanite -> don't even go there that's too much to put on a spaceship.

Antimatter

It's safe, I think...

+ amazing energy density
- can't refuel without a space facility and thermofluid

Defense

Note that spaceships without thrusters will not move fast enough for meteors to appear.

Repairing via Roboport
+ space efficient
+ lowest risk
- resource intense
Gun Turret
+ space efficient
- needs refilling
- longer journeys will need bullet stacks
Laser turret
+ consumes energy instead of resources
- requires a large amount of burst-able energy sources
- requires more turrets for a proper defense than gun turrets
Spidertron
+ uses no hull space
+ also allows for repairing without a roboport
- uses up chest space

Forcefield generator
+ sufficiently dense forcefields will stop anything
+ uses no ammo
- each one uses 1MW to stay on, plus 5MW or more to repair damage it takes
- max draw is 200MW (when turning on?)

Automation

Signal I/O

The spaceship clamps allow signals to be passed in and out, as well as power supply. There are two anchors to attach wires to: the top corner, which will be passed through to the docked twin clamp, and the bottom of the clamp to which it is possible to control the clamp itself.

Signals to console:
  • Speed - Tells the ship how fast to try to go. This is useful for regulating power usage on solar-powered ships to make sure there's enough power for the defenses. Recommended methods are either setting the three speeds manually or a math combinator linked to an accumulator (dynamically control speed depending on the power available).
  • Spaceship clamp # - indicates the clamp on the spaceship to use to dock

These two are the only console inputs required to be generated during the trip for automated spaceships. (Note that the example picture on the right is missing the Speed signal without which the ship won't engage.) All other signals are optional. There is no real benefit from using more than one clamp, so use one clamp and put the signal on a constant combinator attached to the console.

  • Destination

The destination signal for a surface can be found in the info box in the universe explorer - it's a signal unique to each zone or spaceship.

  • Launch signal
  1. Launch based on fuel: Useful when you want to pass a signal to take off from outside
  2. Launch based on cargo: Useful when you can wire up your cargo either directly or with a roboport
Using multiple docking clamps

It is possible to have more than one clamp on a surface with the same ID. The ship will dock to any clamp that is free and enabled. A clamp can be disabled sending the red signal value 1 to the clamp (bottom connector).

Routing:
Onboard Back-and-Forth

Use two arrays of combinators located on the ship. Each array performs two functions:

  1. Setting the guidance for the destination, and
  2. Determining if the ship is ready to launch for the other location.

Note that the guidance must be a constant signal for the duration of the trip but the launch instruction only needs to be a single tick transient. See the spaceship console section in Spaceship for details on input/output signals.

First, determine how the logic will determine which destination is the next one. The most straightforward case is a ship that will load a single type of ore from one location (planet, asteroid belt, etc.) to transfer it to another location, and then return, possibly with some supplies for the mining base. Suppose the ship will carry 50,000 iron ore when fully loaded. The guidance can be set using a constant combinator outputting:

  1. 999, the destination ID on the correct channel (planet orbit 999)
  2. 222, the ship's clamp ID to dock with (left clamp 222)
  3. 444, the dock's clamp ID to be docked to (right clamp 444)
  4. 100, the ship's target speed if less than maximum.

Feed the output of the constant combinator to a decider combinator that checks if the ship is full of ore, and outputs EVERY if true. Send that signal to the ship console.

For the launch signal, create a bank of decider combinators that check each desired signal and outputs a checkmark if true. Gang the output of the bank of combinators and check if the combined checkmark signal is equal to or greater than the number of signals being checked. For example, you might check that:

  1. 333, the ship is at the correct location right now,
  2. Rocket fuel in booster tanks is sufficient,
  3. Stored bullets are sufficient,
  4. Enough ore has been loaded into the ship's storage, etc.

The other array has the same two components for the return trip. The other destination is set by a constant combinator, which feeds into a decider combinator that checks that the ore onboard is zero, and outputs EVERY if true. Send that signal to the ship console. The console will see only one set of destination signals depending upon whether the ship is full or ore, or empty of ore.

Similarly, the launch logic can be specific to this location.

Onboard with Multiple Destinations

The back-and-forth logic can be used if and only if the destination can be determined by conditions on board the ship during flight, because the guidance must remain constant during each leg of the trip. For example, an ion engine ship that carries a full load of ore from a mining planet back to a factory planet, but refuels at an orbital platform before returning for more ore can use the following logic to determine which constant combinator sends guidance signals to the console:

  • If the ore is full, pass the factory planet guidance to the console,
  • If the ore is empty AND rocket fuel is not full, pass the orbital platform guidance to the console,
  • If the ore is empty AND rocket fuel is full, pass the mining planet guidance to the platform.

In this case, the rocket fuel remains full during the entire trip from the orbital platform to the mining planet, so it can be used to discriminate between the second and third destinations. Here is the logic table for this example:

Destination Ore Rocket Fuel
Factory planet Full Not Full
Orbital platform Empty Not Full
Mining planet Empty Full

The guidance logic will require three decider combinators for each of the second and third cases. Thus, guidance for three stops requires a minimum of 7 decider combinators and 3 constant combinators.