12/19/2023 0 Comments Barotrauma automatic doors![]() ![]() What I am describing is just a mere annoyance. Such design seems unfinished to me.īut if you want to save on parts, it doesn't hurt the functionality. But since I am naturally a perfectionist I dislike the fact that you can spam open/close the doors and create a state conflict by pressing the button when the motion sensor wants to keep it open. There is some truth to the fact that you can solve this with one relay by simply having the buttons toggled on at all times. The motion sensor is connected to an array whose set_state is connected to the waterdetector (water yes=0)This is not what I meant as doing that will keep the door closed ALL THE TIME when there is WATER. You probably mis-understood what meant and what I suggested as a solution. But you still do not want to exclude the possibility to open those doors manually in order to be able to do field repairs.ĭuring normal function, you want to move through the sub as fast as possible so the doors are only an obstruction - Thus they open automatically. The whole point of the design I use is to have an override switch which toggles only when there is water, since during a breach you want to seal off rooms to prevent flooding or hostiles from accessing vital areas of the sub. You to go primitive or over engineeringCan you elaborate what you mean by that? It makes no sense because primitive/simple design is a contrast to an over engineered / complex design.Īlso what you are describing doesn't solve the problem that someone in this thread mentioned. What do you mean by "Let motion sensor do all the work"? Aren't having two motion sensors twice as bad? How is what what you are describing not over engineering? You do realize you only need one motion sensor to close the doors right? One sensor which has two states, sending 0 on false, which is when there are no people detected? And you wire it to the set state. I implemented the doors on my sub if you want to see how I solved it. ![]() No need to let the motion sensor do all of the work. And if no people are arround the door closes seperatly. Thus I just take two motion sensors, one that checks for people and one that checks for "no people". I almost never make "state" constructions, because they force you to go primitive or over engineering. Everything I construct is done on a toggle basis. I didn't disable, because there was no need. It's absolutely disgusting and only seems to work for this case, but it's cheaper and faster to set up.How exactly did you solve disabling the buttons when automatic mode is enabled with a single relay? The moment you open the door, the comparison becomes True = False and the stream will stop, then the Delay component will eventually fire a single pulse with "False" value to close the door.While the door is closed, the door state_out spams False value signals which evaluates (False = Undefined) which in turn returns True, causing a stream of False value signals to come from the comparator to the Delay component, which will reset its timer indefinitely and output nothing because of the option we ticked.The confusing part was why the whole thing worked at all and it became clear to me when slipped in the shower box and hit my head on the sink counter last night and figured out why that circuit works: Both the Integer 0 and an Undefined object tend to be evaluated to False when cast to boolean in plenty of specifications, so if it's making a boolean comparison then the logic is actually correct and this is the only way you can do it without memory. This instance probably only works because the default signal is zero, but in true logic it would be undefined / null and therefore the circuit would fail. ![]() Where logic is concerned one should always aim for zero ambiguity, always provide an input, and don't put two signals to one input unless you know 100% that only one of those signals can trigger or be active at a time. Originally posted by Buggy Boy:The only problem with leaving one of the equals inputs disconnected is that you're leaving that input unknown, so if at any time the way components work is changed in the future, this may break the circuit. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |