All tools →

Tools · SciSpinner Max

Run setup

Prepare an instrument from your computer. Set the motor speeds, the run plan, the lighting presets, the camera and the display settings here, download scispinner-config.json, and put it on the instrument's USB drive. The settings are loaded the next time the Control Module starts. Everything runs in your browser; nothing is uploaded.

Motors Control screen

Frame
rpm
Core
rpm

0.050–5.000 rpm per axis in 0.001 rpm steps; 0 holds the axis still. Direction is as seen from the axis's motor end. These are the values the dials show at start-up; the motors stay off until Run is pressed on the instrument.

Check these speeds in the simulator ↗

Run plan Experiment screen

Folder name on the USB drive: sessions/<name>/. Letters, digits, dash and underscore.

Duration
Time-lapse interval

Lighting schedule

Up to 4 steps; they repeat for the whole run. “Off” is darkness. Each step holds at least one minute.

Lighting presets Lighting screen

Each preset is a whole-strip scene: the 90-pixel ring (pixels 1–90) and the 40-pixel halo (91–130), RGBW, 0–255 per channel, with one brightness for the scene. Later zones paint over earlier ones. The firmware keeps the strip under its 3000 mA budget by dimming an over-budget scene; the estimate below uses the controller's arithmetic.

Camera Camera screen

Focus
auto
Exposure
EV 0.0
Contrast
1.0
Sharpness
1.0
Digital zoom
1.0×
Chamber fan
0%
IR illumination

Flash: IR on only during capture.

Orientation
Still resolution

2592 × 1944

Still format

Display Sensors screen and theme

Temperature and humidity graph
Gravity graph
Acceleration graph
Rotation graph
Screen theme
scispinner-config.json
What the file contains

The Control Module keeps its settings in a small JSON file, scispinner-config.json, on the module and on the USB drive. At start-up it reads the USB copy if there is one, and afterwards every change made on the screens is written to both. This page produces the same file from the same rules as the instrument's own screens:

A file that is missing a key, or has an unusable value, falls back to the instrument's default for that key, so a partial or older file is safe to load. The page only writes keys it knows; anything else in a loaded file is passed through unchanged.