I have been trying to create a system for a new version of my Logic Airlock that detects docked entities and triggers the doors to open.
Due to space/visual constraints, I am unable to place the activation module next to the actual rail itself due limited space and that screwing up the visuals (not least of which is a new integrated adapter where that would seriously not be possible), so I attempted to utilize remote rail connection. I slaved each rail to a seperate activation module which are then tied into an OR-gate, thus not breaking any logic rules that I am aware of.
The problem is that it seems to be broken. The activatiom modules must be "primed" on, and then will detect when the docker is no longer on the rail, but will not detect upon docking like it's supposed to, and must be turned on manually each time. This does not appear to be an issue with wireless modules as this occurs not only on the adapter but on the main body of the build as well.
Obviously this situation is not ideal in the slightest. Should I just give up and find some way of placing the activation modules next to the rails and hiding them, or is there a fix?
The circuit is as follows:
Rail into Activation Module
AM into OR-Gate
(From the adapter pieces, this is tied into a linked pair of Wireless Blocks that then link into the above OR-Gate on the main vessel)
OR-Gate into two seperate OR-Gates that take input from rail-timer as well and then opens the appropriate door.
Due to space/visual constraints, I am unable to place the activation module next to the actual rail itself due limited space and that screwing up the visuals (not least of which is a new integrated adapter where that would seriously not be possible), so I attempted to utilize remote rail connection. I slaved each rail to a seperate activation module which are then tied into an OR-gate, thus not breaking any logic rules that I am aware of.
The problem is that it seems to be broken. The activatiom modules must be "primed" on, and then will detect when the docker is no longer on the rail, but will not detect upon docking like it's supposed to, and must be turned on manually each time. This does not appear to be an issue with wireless modules as this occurs not only on the adapter but on the main body of the build as well.
Obviously this situation is not ideal in the slightest. Should I just give up and find some way of placing the activation modules next to the rails and hiding them, or is there a fix?
The circuit is as follows:
Rail into Activation Module
AM into OR-Gate
(From the adapter pieces, this is tied into a linked pair of Wireless Blocks that then link into the above OR-Gate on the main vessel)
OR-Gate into two seperate OR-Gates that take input from rail-timer as well and then opens the appropriate door.
Last edited: