After an initial issue with being stupid, I set the printer type from 1 to 2, cleared the eeprom and reloaded the software. First off matter control said the eeprom was empty, I repeated the above steps. Had the eeprom come back with some crazy numbers. Cleared and started again. Also go a few errors about a accelerometer send i2c error, being that I don't have one... Makes sense, lol. Found something here about that and setting FEATURE_Z_PROBE 0. I have hotend type set to 1 and the following says that it should already be FEATURE_Z_PROBE 0
Code: Select all
if HOTEND == 3
#define FEATURE_Z_PROBE 1
#define FEATURE_Z_PROBE 0
Do I just ignore this?
Next issue I think is matter control running inside virtual box, reading the eeprom gives stupid results. Sometimes the charters are transposed ect.... I never use it for anything other than setting z height anyway. but I'm sure it's probably not safe to edit the PID numbers with it acting buggy.... So I'll put them in config.h and reload.
Here are a couple of the things that are bothering me.
Old X and Y max length 350, new 250
Old Z max length 290 now 350
So is this just the firmware is now figuring something different?
Things like PID drive max being set down to 180 and used to be 105.
Can this be turned back up?
Is there a way to edit the eeprom without mattercontrol? If not I'll edit the values in config.h and reload. I've fought matter control in Linux before and just use slic3r now.