Inscreva-se para baixar
Airlock Controller

This script provides automatic control for airlocks by performing the following functions:

• Automatically recognizes collections of blocks as airlocks, by analyzing block names
  
• Depressurizes and Repressurizes the airlock from isolated oxygen tanks, so no oxygen is lost (unless you breathe some)
  
• Prevents Interior doors from being open when the airlock is not fully pressurized (unless there's no more oxygen available in the tanks)
  
• Prevents Exterior doors from being open when the airlock is not fully depressurized (unless there's no more room in the tanks)
  
• Uses lights to indicate the current state of the airlock (Depressurized = Red, Filling/Draining = Blinking Red, Pressurized = White)
  
• Pressurizes an airlock from a Programmable Block "Run" command, which can be assigned to a button.
  
• Automatically depressurizes the airlock after 3 seconds of being pressurized, to keep the airlock in a depressurized state, when idle, so it's quicker to enter the ship/station than exit (in case you're in a hurry to not suffocate)
  
• Provides a global Lockdown command to shut and lock all airlocks.

After loading the script into a Programmable Block, configure it by modifying the values of the following readonly variables near the top of the script:

AirlockTag

• This is the text tag that must be placed in the name of every block you want the script to manage. The default is "Airlock"

DoorTimeout

• The time, in seconds, that doors will stay open before auto-closing.

LightColor_Pressurized
LightColor_Depressurized
LightColor_Lockdown

• The light colors that will be used to indicate the current status of each airlock.

LightBlinkInterval

• The blink rate, in Hz, that will be applied to lights when an airlock is filling or draining.

The rest of the settings deal with reducing script complexity, to avoid the "Script is too complex" exception. You will have to adjust these experimentally, based on your specific setup.

RecollectBlocks

• Indicates whether the script should collect lists of blocks to managed on every run, or only on the first run. If false, any changes made to managed blocks, or addition of new blocks, will require a "reboot" of the script (by selecting "Edit", "Check Code", and "Remember & Exit") before the changes take effect.

OpsPerRun

• Indicates how many "operations" will be performed during each run of the script. Reducing this number too far may cause airlocks to become unresponsive or sluggish, unless the update rate of the script is increased.

DebugEnable

• Enables the printing of debug messages to the Programmable Block's "Detailed Info" section.

Once configured, the Programmable Block must be triggered to run (with no argument) periodically.
The most effective way to do this is with Digi's "Loop Computers" mod, by adding the tag [repeat 0.16] to the name of the Programmable Block. This causes the script to run 6 times per second.

Triggering of the script can also be done by attaching the "Run" action of the block to a Timer Block
which triggers its own "Start" action. DO NOT attach the script to a Timer Block that triggers its own
"Trigger Now" action. This will run the script 60 times per second, which will cause it to malfunction,
as there are certain properties of blocks that do not update that quickly.



To configure blocks to be managed by the script, you must first pick a name for each group of blocks that will form an airlock. The name must contain only alphanumeric characters, and all references will be case-sensitive.

Once a name is picked, the following tag (including the brackets) must be added to the name of each block to be managed: [Airlock AirlockName]. The first word "Airlock" can be changed by modifying the AirlockTag variable, described above.

The following block types should be assigned this tag

• Doors
  
• Air Vents
  
• Oxygen Tanks
  
• Lights

Additionally, for doors on the exterior of the airlock (adjacent to unpressurized space),
the tag must be [Airlock AirlockName Exterior].


The script implements the following commands (not case-sensitive):

"disable [AirlockName]"
"off [AirlockName]"

• Disables management of the given airlock, or (if no airlock name is given) the entire script.

"enable [AirlockName]"
"on [AirlockName]"

• Enables management of the given airlock, or (if no airlock name is given) the entire script.

"pressurize [AirlockName]"

• Pressurizes the given airlock, or (if no airlock name is given) all airlocks.

"lockdown"

• Places all airlocks into "Lockdown" mode, where all doors are shut and locked.

"release"
"allclear"

• Releases all airlocks from "Lockdown" mode, and returns them to previous operational status.

Each of these commands can be executed from the Programmable Block GUI, or by assignment to a button or sensor.