Overview
On printers running Marlin firmware, the EEPROM (Electrically Erasable Programmable Read-Only Memory) stores key user-configuration settings so they persist after power cycles. This includes motion calibration values, temperature tuning, and other firmware settings that you may adjust during tuning or routine maintenance.
Using EEPROM commands correctly ensures your Gigabot remembers those tuned values and behaves consistently from session to session.
What EEPROM Stores:
Marlin’s EEPROM holds settings such as:
Motion parameters (steps per millimeter for X, Y, Z, and extruder axes)
Feed-rates, acceleration, and jerk limits
PID tuning values
Calibration offsets and other configured parameters
EEPROM saves configurable values only - not the core firmware code.
Store Current Settings to EEPROM:
After making any new configuration changes, save the new values to EEPROM so they are retained after reboot.
-
G-code command:
M500 From the controller interface:
-
Using the Viki navigate to: Control > select: Store Settings
This action writes current live settings into EEPROM.
Recall Stored Settings from EEPROM:
If your printer has been restarted, you can reload the last saved settings from EEPROM.
G-code command:
M501This pulls the saved values back into the active configuration.
Reset EEPROM to Firmware Defaults:
If EEPROM data becomes corrupted, or you want to revert to factory defaults, you can reset EEPROM first and then re-save.
-
Restores defaults from firmware:
M502 -
Saves defaults to EEPROM:
M500
Note: Resetting EEPROM will erase previously calibrated values. Re-calibration may be required afterward.
When to Use These Commands:
Use EEPROM commands when:
You adjust configuration parameters (steps/mm, PID values, etc.)
You flash new firmware and want to ensure settings align
You’re troubleshooting unexpected motion or temperature behavior
Questions or Additional Support?
If you run into issues or have questions about EEPROM behavior on your Gigabot, reach out to our support team at support@re:3D.org, or open a support ticket.
Comments
0 comments
Please sign in to leave a comment.