Mekanism QIO Drive Array Input Source

telem.input.mekanism.qioDriveArray (
  peripheralID: string,
  categories?: string[] | '*'
)

Mod Dependencies

Requires Mekanism.

See the Usage section for a complete list of the metrics in each category.

Name	Type	Default
peripheralID	string	nil
Peripheral ID of the QIO Drive Array
categories	string[] | "*"	{ "basic" }
List of metric categories to query. The value "*" can be used to include all categories, which are listed below. { "basic", "advanced", "storage" }

Usage

local telem = require 'telem'

local backplane = telem.backplane()
  :addInput('my_qioDriveArray', telem.input.mekanism.qioDriveArray('right', '*'))
  :cycleEvery(5)()

Given a QIO Drive Array peripheral on the right side of the computer, this appends the following metrics to the backplane (grouped by category here for clarity):

Basic

Name	Value	Unit
mekqioarray:frequency_selected	0 or 1
mekqioarray:item_filled_percentage	0.0 - 1.0
mekqioarray:type_filled_percentage	0.0 - 1.0

Advanced

DRIVE_STATUSES = { READY = 1, NONE = 2, OFFLINE = 3, NEAR_FULL = 4, FULL = 5 }

Name	Value	Unit
mekqioarray:drive_status_N Indexed per drive	DRIVE_STATUSES value

Storage

Name	Value	Unit
mekqioarray:item_count	0 - inf	item
mekqioarray:item_capacity	0 - inf	item
mekqioarray:type_count	0 - inf
mekqioarray:type_capacity	0 - inf

Storage

Frequency Scope

Due to Mekanism limitations, only the items in the specified drive array peripheral are exposed as metrics. To see the full contents of a frequency, use a separate peripheral/adapter per drive array.

If the drive array contains items in its drives, a storage metric is added for each item. Given a drive array with the following contents (as shown in a QIO Dashboard):

The following metrics would be added:

Name	Value	Unit
storage:minecraft:glowstone_dust	48	item
storage:minecraft:redstone	459	item