Help. . . All dimensions are doubled!
Posted: Sun Aug 17, 2014 2:58 pm
I finally got everything wired up and attempted to run "mydual2.gcode". That didn't get very far as it ran off of the back right side of the plate. Poking around, I discovered that when I jog any value, such as X or Y or Z, by some amount, the actual movement is twice that amount. So where the gcode is supposed to make a move to the middle of the plate, it ends up at the far back and right. The extruders extrude twice as much as they should and everything is a big mess.
I am tempted to suspect that this has to do with my 8-microstep motor drivers. However, I worked my way through the Marlin code, and I can't find any significant difference between the stepper code for my last working firmware (from Ketil) and the current one (the M2_Dual firmware from the MakerGear wiki site). The new code appears to be missing five lines that initialize the microcontroller pins connected to the stepper drivers' MS1 pins to "output", but apparently "output" is the default state for these pins because adding those lines back in doesn't make any difference.
One odd aspect of the stepper motor driver chips is that the older chips (the A4984) uses MS1, MS2 = 1, 1 to encode 8 microsteps, while the newer chip (the AD4982) uses the same pin states to encode 16 microsteps. So changing the "MICROSTEP_MODES" in the Configuration_adv.h file from all "16" to all "8" values has absolutely no effect. It's not clear to me that this has any bearing at all on my problem. Anybody have any ideas?
I am tempted to suspect that this has to do with my 8-microstep motor drivers. However, I worked my way through the Marlin code, and I can't find any significant difference between the stepper code for my last working firmware (from Ketil) and the current one (the M2_Dual firmware from the MakerGear wiki site). The new code appears to be missing five lines that initialize the microcontroller pins connected to the stepper drivers' MS1 pins to "output", but apparently "output" is the default state for these pins because adding those lines back in doesn't make any difference.
One odd aspect of the stepper motor driver chips is that the older chips (the A4984) uses MS1, MS2 = 1, 1 to encode 8 microsteps, while the newer chip (the AD4982) uses the same pin states to encode 16 microsteps. So changing the "MICROSTEP_MODES" in the Configuration_adv.h file from all "16" to all "8" values has absolutely no effect. It's not clear to me that this has any bearing at all on my problem. Anybody have any ideas?