BlueMoon: Руководство по телекоммуникациям: различия между версиями

==Простое руководство по ремонту телекоммуникаций==

Радио внезапно перестало работать? Вот краткое руководство, чтобы понять, в чём проблема и как её исправить:

# '''Все цело, но машины выключены (на машинах нет мигающих огней)?'''

## Было ли объявление Центрального командования о чём-то вроде «Обнаружены ионосферные аномалии. Временные аномалии#MCi46:5.;@63-BZZZZT»? Если да, подождите несколько минут, и оборудование автоматически вернётся в рабочее состояние. Обратите внимание, что это может произойти без какого-либо предупреждения, поэтому просто подождите 5 минут.

### Click on a server.

### Go back to main menu and repeat steps for all servers.

=Quick Guide to Telecommunications=

'''If you just want to know how to fix everything incredibly easy, skip to the image.'''

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

{|class="wikitable sortable mw-collapsible" width="80%" style="background-color:#FF9D001e"

! style='background-color:#FF9D00; width:125px;'    |Machine

! class="unsortable" style='background-color:#FF9D00;|Description

![[File:Sreceiver.gif|64px|class=pixelart]]<br>Subspace receiver

|''Subspace Receivers'' are essential to a subspace telecommunication network. They have a long-term subspace window open at all times, and create the subspace-equivalent of a gravity well in its warped version of space-time. FTL signals traveling in subspace are going too "fast" to be sucked into the gravity well, but a carbon copy of the signal is produced whenever a signal passes through the pocket. This signal is then converted into a real radio wave by the Subspace Receiver and passed onto all immediately-linked machines. In a typical scenario only Bus Mainframes would receive the signal.  

![[File:Relay.gif|64px|class=pixelart]]<br>Telecommunication Relay

|''Telecommunication Relays'' are very essential creating a full network. They allow the network to expand by being able to send signals past Z levels. Meaning that when saying something in the radio, after the message is processed the HUB will locate all linked relays and add their Z level information to the signal data, which will then broadcast on the level when it reaches the broadcaster. It works by charging atoms for an almost faster than light signal. It then gets broadcasted to the hub, the only machine that can receive these almost-light speed signals and then sends them ideally to a Bus Mainframe.

![[File:Hub.gif|64px|class=pixelart]]<br>Telecommunication Hub

|''Telecommunication Hub'' is the main junction for the network. It is connected to many relays that are scattered along space, waiting to receive and send information to buses and relays. It uses a high level technology of circuits to send information as efficiently and as fast as possible.

![[File:Bus.gif|64px|class=pixelart]]<br>Bus Mainframe

|''Bus Mainframes'' regulate and handle the transfer of massive quantities of data at near instantaneous speeds. They are not essential to a network, but are required to keep data transfer instant. They usually transfer data back and forth between servers and processor units. If a Bus Mainframe is missing, network output may be unreliable or slow.

![[File:Pro.gif|64px|class=pixelart]]<br>Processor Unit

|''Processor Units'' decrypt, clean and stretch hyper-compressed radio signals. Radio signals are sent into subspace using a preset encryption hash but random seed, which makes the process of encrypting and sending very light but unpacking and decrypting heavy due to the weird nature of subspace. Processor Units can instantly make signals readable by other machines. They are not essential to a subspace network but if one is missing, network output may not be understandable.

![[File:Server.gif|64px|class=pixelart]]<br>Telecommunication Server

|''Telecommunication Servers'' log network statistics and signal traffic for easy maintenance. Each server represents a "channel" in the Nanotrasen default settings. They can listen in to multiple channels, however. For each signal that is sent to a server, a database entry is created and the signal's information is stored. The servers also help by sorting the order in which signals are transferred to subspace broadcasters, which is vital for instantaneous signal transferring.

![[File:Broad.gif|64px|class=pixelart]]<br>Subspace Broadcaster

|''Subspace Broadcasters'' are impressive pieces of hardware that are capable of opening large enough subspace windows to transfer de-compressed data bursts, in encoded radio waves, through. They are necessary for any network that is expected to output information back to receiving radio devices. They operate by directing high-powered lasers into a small subspace window and fluctuating the amplitude of radio waves through subspace, allowing the large data packets easier entering and exiting of subspace.

![[File:Message_server_anim.gif|64px|class=pixelart]]<br>Messaging Server

|''Messaging Servers'' process and route PDA and request console messages. Takes 15 minutes of calibration before it works if newly constructed. <br>Use a multitool to configure its settings and link it to the (tcommsat) network and hub. If there is no active messaging server, PDA and request console messages won't work.

![[File:Blackbox_recorder.gif|64px|class=pixelart]]<br>Blackbox Recorder

|Only used for keeping [[High-risk_items#The_Blackbox|The Blackbox]] theft objective.

[[File:SpessChart.png|640px|thumb|right|A simple visual synopsis of a basic radio telecommunication network. It shows the "route" a subspace transmission travels before it reaches its end destination(s).|class=pixelart]]

== Maintenance Guide ==  

 

If you suspect the machines aren't working properly (or at all), you should identify the cause first. Probably the most common issue is an exploded central compartment. Repair any structural damage and assess the machines. If they're still on (flashing/blinking lights, etc) then they are relatively functional. If there's been some atmospheric depressurization you're going to want to pump supercooled air into room; the machines need cold gas to survive or they will not be able to diffuse their heat into the environment, and will overheat.

 

[[File:Multitool-tcomm.png|thumb|274px|right|The multitool-telecomm interface.]]

If the machines have been overheated, you can fix them by simply reconstructing them. To do this, first unfasten the exterior bolts with a screwdriver. Next, dislodge the plating with a wrench. Next, remove the internal cables with some wirecutters. After that, you can use a crowbar to remove the internal components and circuit board. From there, you can either deconstruct the empty frame or simply rebuild it. If the machines have been completely destroyed, you're going to want to build more. You're going to have to bug R&D for some really high-tier circuit boards and stock parts, or salvage some parts from other toasted telecomm machines. Keep in mind, you don't have to reconstruct ALL the machines. At the very minimum you need 1 receiver, 1 processor, 1 bus, and 1 broadcaster. You might have to manually reconnect to relays if they are destroyed, this involves a long walk.

 

== Telecommunication Polymorphism ==

The machines can be retrofitted manually to work with other machines that normally would not be very common or wise. In the case of an emergency, however, it can be a life-saver. You can use a multitool to interface with telecommunication machines, which will allow you to modify some of the machines' properties. You can also link together machines with this interface, which is possibly the most important function.

 

In order to link two machines, access one of them with your multitool. Select [Add Machine] at the bottom of the window to store this machine in the buffer of the multitool. Now access the other machine with the same multitool. The machine previously buffered should still be in the buffer of the multitool. Select [Link] to add the machine currently buffered to the list of machine links of the machine currently accessed. This will establish a link between these two machines. (Note that it is possible to link a machine to itself; this is both harmless and pointless.)

 

=== Subspace Receivers ===

You can link Subspace Receivers to ''Processor Units'' if you are unable to link to a functional bus mainframe. This can and will create substantial network lag, because Bus Mainframes are needed for rapid information transferring and advanced port configurations.

 

You can link Bus Mainframes to ''Subspace Broadcasters'' if you are unable to link to a functional server. This will not have much of an effect besides a very miniscule performance decrease.

 

If you do not link to a Processor Unit, signals' readability will suffer substantially. It will also make it impossible to directly link to broadcasters.

 

You can link Processor Units to ''Telecommunication Servers'' if you are unable to link to Bus Mainframes. This will naturally have a significant performance cost.

 

Relays must be connected to a HUB in order to add information to the signal about the Z level it is in, and which will broadcast in. It cannot be linked to any other machine usefully.

 

This machine is essential when creating relays that allow you to send the same signal to multiple broadcasters on different space levels.

It is ordinarily connected to Relays, Servers and Buses. When it receives information from Relays it sends it to all linked Buses. If it receives information from a machine that isn't a Relay, it assumes it's ready-to-transmit data and then sends it to all linked Relays. This data is ideally received from Servers but Buses and Processors can send this information too.

 

These cannot really be linked to anything else other than a broadcaster. They are only needed to store logs and maintain sane bookkeeping.

 

These are ESSENTIAL if you want an output. There is nothing you can do with these in terms of polymorphism.

 

Now downing the radio may seem like something the captain does when he stubs his toe too hard, but downing the radios is something even the most [[Assistant|clueless trouble maker]] can do, provided they have the tools. Here are some easy ways to make nobody hear the screams of the station's inhabitants.

 

* Destroy the sub-space broadcaster. Those screams will be uttered, But not heard.

 

* Deconstruct the processor. This makes the radio blast gibberish that nobody can comprehend.

 

* Deconstruct the server and it's bus. Depending on which ones you knock out you can disable most of the command channels and such.

 

* Add Filtered Frequencies to the Hub in order to only allow people to speak on those frequencies. You can do this on any machine and department channels will also suffer from not being able to pass the filter.

 

[[file:telecom.gif|400px]]