Configuration

Most of what you need day to day is on the touchscreen. The enclosure also reads two plain text files from the SD card, and that is where you change the things the screen does not expose: servo angles, alarm thresholds, the temperature at which the flap forces itself open, and so on.

Both files are ordinary text. Edit them in any text editor.

File	What it does	Direction
`data.clu`	Around 27 tuning values	You write, the enclosure reads
`filament.clu`	Your spool library	Both ways
`log.csv`	Sensor history	The enclosure writes

The SD card

FAT32, in the mainboard slot. Cards larger than 32 GB are often formatted exFAT, which is not supported, so reformat them.

Both .clu files are read once, at boot. Inserting a card into a running enclosure does nothing until you power cycle it. Logging is different, since it re-opens the card on every write, so you can pull the card out mid-print, copy log.csv off, and put it back.

There is no harm in leaving the card in permanently. That is the intended setup, since it keeps logging and your settings are re-applied automatically if a firmware update ever resets them.

How settings get applied

Both .clu files use a revision number. The enclosure remembers the last revision it applied and ignores the file until it sees a higher one.

This is what makes it safe to leave the card in. Without it, every boot would wipe out changes you had made on the touchscreen and put the file’s values back. With it, the file only acts on the one boot after you raise the number.

So the routine for any change is always the same:

Edit the value
Raise the revision number
Power cycle the enclosure

If you forget step 2, nothing happens. That is the single most common reason a change does not work.

Where your settings actually live

Inside the mainboard, in memory that survives both power cuts and firmware updates. The SD card is only a way to get values in.

That means your calibration, brightness, fan speeds and filament library are not lost when you update firmware, and are not lost if you take the card out.

Getting the files

If data.clu is not on the card, the enclosure runs on its built-in defaults. It does not create the file for you. Download a copy to start from:

data.clu, an annotated template with every value at its default
filament.clu, the 16 pre-loaded spools

Firmware downloads are on the Software Upgrades page.

filament.clu is different. If it is missing, the enclosure writes it for you from its own library on the next boot. So an easy way to get a correct starting file is to put a blank card in and power on.