#Disabling multiblock controller when a maintenance issue occurs (EV+)

6 messages · Page 1 of 1 (latest)

peak elk
#

This tip is useful if you hate having machines void recipes due to a power fail that happend because of a maintenance issue.

Material used:

Step 1 : Place a Wireless Needs Maintenance cover and an Advanced Redstone Receiver (Internal) on your controller. I placed mine on the bottom and top side of an EBF for example (See picture 1)

Step 2: Choose a frequency to use on both covers. Any conflict between multiple covers will end in disabling all multiblocks using the same frequency until all maintenance issues are resolved.

Step 3: Set the frequency to use on the Maintenance cover, the issue detection to ">= 1 Issue" and Normal redstone mode. (See picture 2)

Step 4 : Set the frequency to use on the Advanced Redstone Receiver (Internal) and the Gate Mode on "NOR Gate". (See picture 2)

Step 5 (Optional) : Place a Advanced Redstone Receiver (External) on a frame box for example and configure it to the same frequency and in Gate Mode "OR Gate". This step allows you to retrieve a redstone signal for your control room for that specific multiblock in case of a maintenance issue.

Step 6: Repair any maintenance issue on your multiblock to activate it. Even with only one maintenance issue the multiblock will stay deactivated (See picture 3). Once the issue is repaired the multiblock automatically starts up again (See picture 4)

PS: If you see any english mistakes feel free to tell me so i can correct them and make this guide better for everyone else.

mystic gazelle
#

Is there any way to detect actual machine efficiency. Cleanroom maintenance cover will instantly emit signal right after a repair, while cleanroom efficiency is still under 100%

peak elk
#

The redstone signal emmitted is at 14 in my case when the cleanroom is at 100% efficiency (see 2nd picture above) and it drops in strength with each maintenance issue.
So i just built a simple comparator to make sure i have a functionnal cleanroom (if there is a single maintenance issue then the signal on the bottom part of the 1rst picture bellow goes under 14 then the comparator emmits 0 redstone and thus disables every machine)
I have setup a second redstone conduit (see 1rst picture bellow above the comparator) paired with machine controller covers on the machines (see 2nd picture bellow). That second redstone conduit handles the actual enabling/disabling of the machines. Hope it helps you

opal cloak
#

Can’t you just use a needs maintenance cover along with a machine controller cover ?

ionic salmon
#

it wouldn't stop machines from running after you have fixed all issues but efficiency is not at 100% yet