Machine access

With MakerOps machine controllers on your equipment, the access rules you set in the platform are enforced at the machine itself: scan, verify, power. This page covers the platform side; the device itself has its own manual.

Connect a controller

1. Get the controller online — see Connecting to Wi-Fi in the controller manual.
2. Bind it to a machine: open the controller’s admin menu, select SHOW BINDING QR, scan it with the MakerOps app, and pick the machine.

The controllers page in the platform lists every unit with its online state, firmware version, and the machine it runs.

Session rules

Per machine (or per fleet, inherited), staff configure how sessions behave:

• Start mode — power immediately on approval, wait for a GREEN press, or require an on-screen safety checklist first.
• Session length — default duration, and whether sessions bind to reservations on the machine’s calendar.
• Warnings — when the end-of-session warnings fire.
• Buddy requirement — machines that need a second person before they start; the second person scans and attests on their own phone.
• Presence checks — periodic “still there?” prompts, and whether a missed check alarms or cuts power.

Settings sync to the controller over the air; the controllers page shows each unit’s sync state, so you can see when a device has picked up a change.

Who gets in

A scan is approved only when everything lines up: the required credentials (see Training & credentials), signed waivers, machine service state, and any schedule rules — machines can have bookable windows and reservations, so a scan during someone else’s slot is refused with a reason the member sees in their app.

Every session is recorded: who, which machine, when, how it ended. Usage rolls up on machine records and reports.

Firmware

Controller firmware updates ship from the platform over the air — there’s nothing to walk around and flash. Units check in on their own, staff can push from the platform, and anyone at the device can trigger a check from its admin menu.