Use explicit networks when the exercise depends on electrical switching, failures, fuel routing, or cross-spacecraft transfer.
Defining a power bus
"power": {
"monitor": true,
"bus": [
{
"source_component": "Solar Panel",
"source_terminal": "out",
"target_component": "Battery",
"target_terminal": "out"
},
{
"source_component": "Battery",
"source_terminal": "out",
"target_component": "Transmitter",
"target_terminal": "in"
}
]
}Each component name must exactly match a component in the spacecraft’s components array.
When power.bus is empty or omitted, Space Range can create a simple default network for common sources, batteries, and a jammer. An explicit bus replaces that automatic wiring.
Use Power Bus with:
as well as switches, fuses, diodes, sinks, current limiters, and voltage regulators when required.
Defining a fuel bus
Fuel networks use the same source and target connection pattern:
"fuel": {
"bus": [
{
"source_component": "Fuel Tank",
"source_terminal": "out",
"target_component": "Thruster",
"target_terminal": "in"
}
]
}Use Fuel Bus with fuel sources, valves, pumps, thrusters, and Fuel Interconnect.
Set fuel capacity and desired flow values explicitly. A valid-looking network can transfer nothing when a source is empty, a valve is closed, a receiving flow is zero, or a pump has no electrical supply.
Cross-spacecraft networks
To join power or fuel networks across spacecraft:
- add the appropriate interconnect component to both spacecraft
- connect each interconnect to its local bus
- link the pair in the top-level
dockingarray
See Neutral Assets and Docking for endpoint addressing.
Testing networks
- inspect the Console for missing component names or terminals
- verify generation, storage, loads, and flow
- trigger one switch or fault at a time
- test reset behavior
- test cross-spacecraft transfer only after both local networks work
WARNING
Network definitions refer to component names. Renaming a component without updating the bus can silently remove an intended connection.