Editing Essay: BattleMech Technology

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 258: Line 258:
  
 
====Manager====
 
====Manager====
The DI computer manages all of the systems in a BattleMech. All 'Mech components have their own controlling sub-computers which are brought together by the DI system. The DI, for example, sends commands to actuator MCUs in order to promote smooth limb motions. Each weapon system sub-computer will send its state of readiness or malfunction to the DI computer. More advanced DI computers will indicate to the MechWarrior what the cause of the problem is and try to fix the malfunction, all with no input from the MechWarrior. The DI also keeps the 'Mech from damaging itself. For instance, it will cut back on systems that generate heat when the 'Mech suffers from heat sink damage or is in a very hot environment. It is also capable of overriding the "common sense" programming of the component level systems. When the MechWarrior demands it, the DI will run the engine hot even if the engine control computer is trying to keep the engine cool. It is the DI computer, as manager, that coordinates all the systems called for when a MechWarrior pushes the throttle forward{{m}}it is the DI that controls the engine power, the gyro, and coordinates the actuators. When a BattleMech takes damage, the DI is what re-configures leaking heat sinks and coolant lines, bypasses severed myomers, and tries to re-route power to disconnected weapons.
+
The DI computer manages all of the systems in a BattleMech. All 'Mech components have their own controlling sub-computers which are brought together by the DI system. The DI, for example, sends commands to actuator MCUs in order to promote smooth limb motions. Each weapon system sub-computer will send its state of readiness or malfunction to the DI computer. More advanced DI computers will indicate to the MechWarrior what the cause of the problem is and try to fix the malfunction, all with no input from the MechWarrior. The DI also keeps the 'Mech from damaging itself. For instance, it will cut back on systems that generate heat when the 'Mech suffers from heat sink damage or is in a very hot environment. It is also capable of overriding the "common sense" programming of the component level systems. When the MechWarrior demands it, the DI will run the engine hot even if the engine control computer is trying to keep the engine cool. It is the DI computer, as manager, that coordinates all the systems called for when a MechWarrior pushes the throttle forward{{m}}it is the DI that controls the engine power, the gyro, and coordinates the actuators. When a BattleMech takes damage, the DI is what re-configures leaking heat sinks and coolant lines, bypasses severed myomers, and tries to reroute power to disconnected weapons.
  
 
====Security====
 
====Security====

Please note that all contributions to BattleTechWiki are considered to be released under the GNU FDL 1.2 (see BattleTechWiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)

Advanced templates:

Editing: {{Merge}}   {{Moratorium}}   {{Otheruses| | | }}

Notices: {{NoEdit}}   {{Sign}}   {{Unsigned|name}}   {{Welcome}}

Administration: {{Essay}}   {{Policy}}   {{Procedure}}