Ok, so another just quick Q:
I think I am calling this correctly, the mosfet closest to LED1 gets extremely hot. Is this normal?
The only configuration items I can think to easily change/test would be to possibly disable all your TEMP_SENSOR_# with a 0, just to make sure an over or under temp isn’t halting your machine, though that should show up in the message log if it were. Also maybe try inverting either the enable (X_ENABLE_ON 1 in configuration.h) or step (INVERT_X_STEP_PIN true in configuration_adv.h)…while that’s unlikely to work, it’s an easy thing to try. If you had a volt meter, you could validate that the drivers are being powered, or you could potentially test the drivers off the RAMPS board if you had a breadboard and some jumpers, but beyond… The mosfets do tend to get warm in use. The one closest to LED 1 controls your hotend, so if the hotend is working, then the mosfet is likely “working”… they CAN get too hot and burn out if you’re driving them hard with too much load, but I don’t have an exact way to describe too hot…
If you could upload your marlin somewhere I would be happy to compile and flash it to one of my printers to validate the config works…
Eric, currently I am playing with this:
http://reprap.org/wiki/File:RAMPSTestCode.pde
I am pretty unfamiliar with Marlin-- this is a little easier to digest for me.
I am not getting any motor movement with this program (its supposed to jiggle them in a loop I think)
Using that file, you could test for the inverted enable by changing digitalWrite(X_ENABLE_PIN , LOW); to digitalWrite(X_ENABLE_PIN , HIGH); and see if your X axis moves…if not…then it’s sadly probably hardware.
@Mike_Kowalczyk do you have access to an oscilloscope? You could check to make sure the pulse lines to your step sticks are pulsing. I’d suggest buying some extra motor drivers anyhow. They’re cheap at geeetech if you catch their insane sales, like $5 a pop. Worth having, as hot swapping motor cables, and moving stages by hand too fast can cook the drivers. I’m just curious, as that is the only hardware you haven’t changed, although the odds of all of them breaking is pretty slim
I wish I did, now I have a reason to buy one… =)
As far as hardware:
- Had working configuration, the arduino ended up frying when I put it on top of the power supply (lesson learned)
- Bought new 2560, put old RAMPS and drivers onto it
–> no working motors, everything else seems to be fine (sensors + extruder temp) - I have ordered new RAMPS and drivers… I will figure out what it was sooner or later.
Is it possible just the motor portion of the RAMPS is fried? I know that seems weird in itself, but almost less weird then all of the drivers frying simultaneously…
I’d be a lot less confused if I had even 1 working motor… but nada
Do the motors feel energized when you power up? Or is there no power at all to them?
You can look for pulses with a LED and a resistor instead of an oscilloscope.
Hey all. Just an update and a thank you.
I replaced the steppers and all works. Who knows how I killed them, but happy I have solved the issue.
Now I am facing another issue. I assume its to do with my firmware.
When I hit any given button in pronterface (to control individual motors), all motors are activated.
IE. if I attempt to control only z motors, all motors move, and likewise for the other axis’s. Any idea? Some setting in configuration.h?
IGNORE THIS. Thanks all. I got it!