1.0.4dev homing problems -CR10S (Crealty 2.1 board)
I set up the firmware on a CR10S (Crealty 2.1 board) which is a basic Ramps 1.4 configuration. I compared all the pin settings with a known working Marlin configuration and there's no surprises or variances of note.
I was able to get everything *almost* working but when I go into the homing procedure (any axis) it reaches the endstop and correctly halts, except that for the rest of the allocated steps for homing it spins the extruder in reverse! Another odd thing I've noticed is that until I home the axises the UI shows ??? followed by a large negative number. Extruder position reads -536871.00 which is very strange considering that the init code in setup() resets all coordinate systems to 0 even after reading EEPROM stuff. I've tried resetting the eeprom configuration but am still having no luck. Is there some kind of weird homing bug? Hard to see the homing sequence so I'm having a hard time debugging it.
I was able to get everything *almost* working but when I go into the homing procedure (any axis) it reaches the endstop and correctly halts, except that for the rest of the allocated steps for homing it spins the extruder in reverse! Another odd thing I've noticed is that until I home the axises the UI shows ??? followed by a large negative number. Extruder position reads -536871.00 which is very strange considering that the init code in setup() resets all coordinate systems to 0 even after reading EEPROM stuff. I've tried resetting the eeprom configuration but am still having no luck. Is there some kind of weird homing bug? Hard to see the homing sequence so I'm having a hard time debugging it.
Comments
Performed another cold start without resetting EEPROM and issue occurs again. So whatever the problem is, it must be garbage from EEPROM being loaded.
M415 S0
after enabling eeprom. Resetting does not restore host rescue system - something I fixed for next update hopefully. That may lead to wrong coordinates being read from eeprom hidden section when firmware thinks it is in rescue state. You will also see coordinates if you just send M415 before disabling the mode with above command.