* RTG page update * old commits from #22272 * Small fixes over most pages * TEG tweaks * Fixed a thing in airlock security * fixed an italics tag * singularity page now includes tesla * Added a burn chamber to TEG page * Prettyprinted TEG page, fixed some more issues with details * Moved ONE singular comma * Change Singularity page heading to include tesla * Singularity page pretty printing + fixes * TIL its [italic] NOT [italics] * RTG Prettyprinting * Access Config Prettyprinting + Netconfig tweak * Atmospherics prettyprinting * Construction keybind fix * Apply suggestions from code review --------- Co-authored-by: Kara <lunarautomaton6@gmail.com>
25 lines
1.3 KiB
XML
25 lines
1.3 KiB
XML
<Document>
|
|
# Networking
|
|
Some devices on the station need to communicate with each other, and they do this by utilizing device networking.
|
|
With networking, machines and devices can send arbitrary data between each other.
|
|
There are multiple networks that get used, such as the wireless and wired network.
|
|
Each network device has a frequency it receives on. PDAs for example, use the frequency: [color=green]220.2[/color]
|
|
|
|
Note: The following operations will require use of the Network Configurator to be performed:
|
|
|
|
## Device Lists
|
|
Some devices need to know which other devices to communicate with specifically.
|
|
<Box>
|
|
<GuideEntityEmbed Entity="AirAlarm"/>
|
|
</Box>
|
|
Air alarms, for example, require you to tell it which vents, scrubbers, sensors, and firelocks to interact with.
|
|
|
|
## Linking
|
|
If a device, basic or advanced, needs finer controls of how and which devices it connects to, it will generally use device linking.
|
|
<Box>
|
|
<GuideEntityEmbed Entity="SignalSwitch"/>
|
|
<GuideEntityEmbed Entity="Airlock"/>
|
|
</Box>
|
|
With linking, you can connect the outputs of a device, like [color=gray]On[/color] or [color=gray]Off[/color], with the inputs of a device, like the airlocks [color=gray]Open[/color] or [color=gray]Close[/color] inputs.
|
|
</Document>
|