On 14/01/2016 1:57 PM, Theodore Vaida wrote:
>
>> On Jan 14, 2016, at 2:46 PM, Dan Newman <
dan.n...@mtbaldy.us> wrote:
>>
>> Did you use the stepper driver cards that came with the new board or did you
>> use old ones? Some or all of the old ones may have died when the old main board
>> died.
>
> The Wanhao came with all new stepper drivers which I left in place, as far as I can tell all of the connections are
> made the same as on the MBot original for the end stops. Since the X-Y gantry does move during the power-on and homing
> sequence, the board does seem to be able to drive them it just doesn’t want to do so when issued G codes.
For homing, an unaccelerated but slow motion command is issued within
the firmware. Your actual X3G may be using accelerated motion commands
but if the EEPROM values of acceleration settings are bad/inapt then
it's hard to predict what might happen.
Also, it's possible that your gcode is setting stepper motor currents ("VREF" values). There
could be a problem with that occuring and faulty digital potentiometers on your board. (Keep
in mind, these Asian clone boards see no QA. It's when an Asian manufacturer puts them into
a printer they are assembling that QA/testing actually happens.)
> As for the extruder steppers, I did let the heater cores get up to 230 before trying to engage the extruder steppers,
> and I can manually force filament to extrude on both sides when the cores are hot, so it’s just a matter of getting
> the MightyBoard to drive the motors.
Likely the same issue as the XY steppers then.
As to junk in the EEPROM, I've seen the Asian boards come with firmware loaded and absolute
random trash in the EEPROM. Bone fide Atmel AVRs come with the EEPROM all initialized to 0xFF
which firmwares then recognize as uninitialized EEPROM. But when the EEPROM is all arbitrary
values, that then necessitates doing an EEPROM reset. Moreover, when the bootloader and initial
firmware was loaded, it's possible to tell the ISP AVR programmer to wipe the EEPROM clean and
set it all back to 0xFF. My conclusion has been that some of these clone boards are coming with
non genuine Atmel parts or factory seconds or something that doesn't have the EEPROM all set
to 0xFF. AND, the Asian board fabs, when doing an initial firmware load, can't be bothered to
tell the programmer to first reset the EEPROM. Mind you, I do NOT know for a fact that your
EEPROM was loaded with arbitrary junk. I'm just mentioning what I've seen in the past with
some Asian clone boards from FlashForge and MBot3D.
Dan