Partially Solved Now I can't print at all - Time to throw in the towel.

Thats what I hate about EEPROM Think of it like memory, what gets saved to EEPROM typically over writes what you have saved in the firmware (the main program for the machine) the issue I have with EEPROM is you have to rely on the fact that it never gets changed and what changed got saved. I find it more "fool proof" (I'm the fool not you just to be clear lol) to change the firmware and never store anything in EEPROM unless I must

 

Yes. It is drastic, but if you have the correct measurements of filament once its changed its in there and you cant adjust it without reflashing. I'm not telling you you have to do it that way, just suggesting how I go about doing it and why I dont use EEPROM. You can do it either way you'd like but EEPROM causes headaches for alot of people.

In either way you need to get your numbers for the formula by conducting the test multiple times (10?) average the number and thats what you use in the equation for calculating your E STEPS. Once you have that number you can certainly upload to EEPROM and test. Just never clear or send the command to upload esteps to eeprom again otherwise you'll pull out all your hair

 

In addition to the firmware (which is 'permanent') the printer has something called flash EPROM (EEPROM) memory that is used to hold data between reboots/power cycles. It is an easy way to change settings that would normally require a firmware reload and not having to reload the firmware. However... it is NOT permanent. It is more semi-permanent

 

If you do use the flash EPROM to do your data then if something ever wipes it out you are up the proverbial creek...

 

EEPROM use is a bit odd. The way Marlin works is that if you have EEPROM enabled and you have an actual value in it (not null values) it uses this priority for execution.

1. Firmware settings are moved from Flash memory to user memory at boot time.
2. If there is an EEPROM value it is read and overwrites the user memory value, no if's and's or but's.
3. If there is a null value the Firmware setting is retained in the user memory

Here is what happens when you flash a new version with all new settings.

1. Firmware is burned to Flash memory
2. EEPROM is NOT cleared or initialized in any way, so existing information is still there from flash to flash.
3. It then behaves like the sequence mentioned previously.

Marlin doesn't even care if the values in EEPROM are correct, it just treats it as data that needs to be moved to user memory.

EEPROM can only store values in user memory, It cares nothing for Firmware settings. If you change user settings using G or M codes and do not explicitly save those to EEPROM your modifications are only used until the Arduino is power cycled.

 

Yep. The EEEPROM will survive power off, but it is easy for a host program to overwrite it or for a glitch in the machine to reset values (or the reset button getting pressed on the Arduino for example... not a normal thing, but that will also reset it).

This is why I said it is not 'permanent'. It will survive a power cycle, but unlike the EPROM it is not really permanent.

 

Good idea

 

Reset the flash eprom after every real eprom update.
That way you are certain there is no stale/corrupt data in the flash eprom

 

I am shocked yours is so low. In general every Robo R1 I have seen under-extrudes at 723.38 steps. In my experience the EStep value should be somewhere near 800.

Every time you flash a new firmware and you want to make sure your firmware settings are used, you must do the following before any printing whatsoever.

Code:

M502
M500

The M502 will restore all firmware settings to user memory, the M500 will save all the user memory to EEPROM. Why EEPROM works the way it does in Marlin is anybody's guess. But one good reason to use it is there are a few settings that are not defined in Configuration.h that can be set with M-codes and stored for future use.

 

How are you setting the steps?
Exact workflow please...