About: Subspace transporter   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

In the 24th century, a normal Federation transporter system, that sent its signal through normal space, was limited to a range of about 40,000 kilometers. The range of a subspace transporter was several light years. The matter that was transported needed to be in a state of quantum flux, which was highly unstable. It was possible to attempt to stop a subspace transporter beam-out with another transporter system tied into subspace field coils. The other transporter had to maintain pattern lock on the matter that was about to be beamed away with the the subspace transporter. Deflector shields could not stop a subspace transport.

AttributesValues
rdfs:label
  • Subspace transporter
rdfs:comment
  • In the 24th century, a normal Federation transporter system, that sent its signal through normal space, was limited to a range of about 40,000 kilometers. The range of a subspace transporter was several light years. The matter that was transported needed to be in a state of quantum flux, which was highly unstable. It was possible to attempt to stop a subspace transporter beam-out with another transporter system tied into subspace field coils. The other transporter had to maintain pattern lock on the matter that was about to be beamed away with the the subspace transporter. Deflector shields could not stop a subspace transport.
dcterms:subject
dbkwik:memory-alph...iPageUsesTemplate
abstract
  • In the 24th century, a normal Federation transporter system, that sent its signal through normal space, was limited to a range of about 40,000 kilometers. The range of a subspace transporter was several light years. The matter that was transported needed to be in a state of quantum flux, which was highly unstable. It was possible to attempt to stop a subspace transporter beam-out with another transporter system tied into subspace field coils. The other transporter had to maintain pattern lock on the matter that was about to be beamed away with the the subspace transporter. Deflector shields could not stop a subspace transport. Under normal circumstances, a subspace transport could not be detected with sensors. However, if the signature of a subspace transporter was known, it was possible to detect when a particular subspace carrier wave was approaching and focusing. This made it possible to determine where the source and target coordinates of the transporter beam were. A person who had used a subspace transporter would leave this distinct subspace signature on anything they came in contact with. This contact needed to be more than brief though. Depending on the type of transporter, the subspace signature might decay faster than normal. Standard Federation transporters could be modified to transport via subspace by aligning the field coils tied into the system and synchronizing the phase dampers, after which the transport pattern was modulated. The transport sequence itself was longer than normal because the pattern needed to be shunted through the subspace field coils. (TNG: "Bloodlines" )
is wikipage disambiguates of
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software