View source for Haxdb auth node

The Auth Node intermediates between a tool and AC power, determining whether the tool can be powered or not.

The tool's power cord is captured within the Auth Node, where it plugs into an integral outlet. Power to the outlet passes through a current-sensing sensor and a switching device suitable for the controlled device (eg, relay or contactor). A power cable exits the Node and plugs into wall power.

Users interact with the Auth Node via a LCD screen and illuminated Fault Button.

When a user auths with their RFID token, a configurable "warm-up" timer begins. The user has eg, five minutes to turn on the authed tool. If the timer expires without the tool being powered up, the tool de-auths automatically.

The power-up state of the tool is detected via the current-sensing sensor. The node will need to be calibrated to recognize its associated tool's characteristic running current.

When the tool powers down, a configurable "cool-down" timer begins. The user has eg, thirty seconds to turn the tool back on. If the timer expires before the tool is turned back on, the node de-auths automatically. The cool-down period could be set to be zero seconds, in which case the tool de-auths immediately on power-down. In any case, if the authed user's RFID token is scanned on any other node while the cool-down timer is active, the cool-down timer is zeroed and the cooling-down node de-auths immediately.

A slot in the bottom of the enclosure enables various RFID tokens -- card, card-in-wallet, keyfob-with-keys, etc -- to be placed inside the node and left there for a work session. In this configuration, the node auth never times out, enabling extended use without periodic re-auth. The RFID reader itself is in the very bottom of the enclosure (items in the slot sit on top of it); this means that RFID tokens can also be tapped against or swiped on the enclosure, supporting eg, implants or rings.

The Fault Button provides an affordance by which any user authorized to utilize the node can indicate a state of unusablility. To do so, the user auths on the node, then holds the Fault Button down for a configurable time - eg, one second. This extended button press is required in an effort to reject accidental button presses.

Any user who can auth on the Tool Node can clear the Fault state by authing on the node, then holding the Fault Button down for a configurable time - eg, one second. This enables any user to resolve a problem with a tool reported by any other user.

While in Fault state, the tool will not be enabled, even on auth. It is therefore impossible to use the associated tool without taking ownership of the Fault by disabling it.

Tool Nodes can also be put in Broken state by board members and czars only. This is accomplished by authing on the node, then pressing and holding the Fault Button for a configurable period - eg, five seconds. The same users can clear Broken state through the same action.

Tools Auth Nodes can be set in a Disabled state by the central HaxDB controller. This is intended to enable "quiet mode" for scheduled classes and events. Tool Auth Nodes should be designated as "loud" or "quiet," with "quiet" tools remaining enabled and "loud" tools being disabled during events. When a tool is to be disabled on schedule, it should show a countdown beginning eg, one hour beforehand. This alerts users to the tools impending unavailability. Similarly, a tool in Disabled state should show a countdown to its scheduled re-enabling.

Tool Auth Nodes can also be set in an Enabled state, in which no auth is necessary to utilize the tool. This will ease the teaching of hands-on classes, and is anticipated to be applied to a Zone at a time.

Tool Auth Nodes can also be set in Reserved mode by the central HaxDB controller. In this mode, only a pre-defined RFID token will activate the Node; all others will be rejected. The node's LCD should both indicate clearly that it is in Reserved mode and show a countdown to the time when the node will resume normal operation. This could be used to reserve a high-demand and/or long-job tool (like the laser cutter or 3D printer) for a particular user, or to permit only the instructor to activate tools during a demo session.

When idle, Tool Auth Nodes should show a variety of "screensavers." These should be contained in standalone scripts, updatable independent of the larger system. Example screensavers could include organization logo, promo of upcoming events, and tool usage statistics.

The central HaxDB controller and node firmware should cooperate to enable the creation and use of "magic" RFID tokens. These tokens would have associated actions that would apply to any node that scans them. For example, "set node Disabled" or "set node Enabled."