I think the new board should be able to protect itself from damaged drivers. The smoked one should be discarded.
i dont think that the driver needs to be the same brand. The BTT ones are Chinese manufacture, too. They are the same driver, with the same polulo pin configuration, I think the local replacements will be fine. A heat sink may be a good idea, youâll still be using it for the same duty cycle and current settings.
I can move the gantry around the table successfully
I can home X/Y axes
I can start some gcode and have the machine âmillâ it in the air (didnât attach the spindle yet)
What I am having problems with:
Homing Z axis seems to be working incorrectly. It is actually quite tricky: When I select âHome Zâ on the TFT, both Z motors start moving up the gantry. When the 1st end stop is reached (doesnât matter which one - left or right - whichever is closer), the corresponding motor stops, and the other motor keeps moving. I think this is expected. When the 2nd end stop is reached, the 2nd motor doesnât stop ⌠it keeps spinning and the gantry keeps hitting the top of the cutout in the YZ plate and dropping back a bit. So I end up with a clicking cycle which basically never ends until I reset.
It seems that sometimes homing Z works fine. It also seems that the same problem happens to Y axis every once in a while, but not often. Generally homing Z works 20% of the times and homing Y works 80-90% of the times. Very strange.
That must mean a loose connection, or the triggers have some interference? Watch them super close to see if something odd happens when it does not trigger.
I think it looks more like a firmware issue. When the motor doesnât stop during homing, I can see the related endstop LED light up on the board. So the board knows the endstop is reached, but ignores it for some reason and keeps trying to move the stepper motor.
I also tried triggering the endstops manually while the gantry is somewhere midway through the Z axis. If I press both Z endstops at the same time, one Z motor stops and the other keeps moving, even thought both LEDs light up. If I trigger left side first, the left side will stop and the right side will keep moving. If I trigger right side first, the right side will stop and the left one will keep moving. As if the board is only able to register one endstop at a time.
Maybe I will try to recompile the firmware and update it. I need to set the correct bed size and Z distance anyway.
Iâll bet that the second stop isnât triggering sometimes because of the angle.
Try bending the switch arms a bit to make sure that theyâre centered on the Z stop tabs.
If youâre using metal XZ plates, I think Doug (design8studio) has made little stops for the metal plates that make sure thereâs enough area on them for the switch arms.
Well. I can hear it click. I can see the endstop LED light up on the board. I think are 2 good indicators that the board received the endstop signal. The motor keeps spinning.
@vicious1 , I have wired the board exactly as per instructions on this site:
Try reflashing the board firmware, it takes 3 seconds.
When you try trigger by hand be sure to trigger twice while testing. The firmware hits the trigger, holds until the next one hits, then backs off both and re-homes both. (autoleveling)
Very funny things happen when the motors and endstops donât line up. If you have them backwards, then one endstop will stop the other motor. Itay be you have the endstops right and theogors backwards?
That really doesnât sound like what you are talking about. Donât get mad at me . I just have to mention it, in case some of these things are red herrings.
In the marlin builds from the last few years, if M119 is correct, and your motors move the right way, and you have the correct motor associated with the correct endstop, then the firmware will be perfect. Ryan is right, software does the same thing every time.
Dunno, I tried to make a video of the problem, and then it suddenly worked fine 20-25 times in a row (of course). Now my phone is full of very amusing videos showing how everything works perfectly I havenât changed anything. I even reset the board to factory settings, still works fine.
The only thing I can think of is that I did power down the board recently, while previously I used to only reset it using the TFT reset button. I am not sure if I had any failures afterwards, been playing it for too long now.
@jeffeb3, that was the first thing that came to my mind as well, but when I click the endstop manually, I can kinda see that the corresponding leadscrew stops spinning. Well, one of them Also tried swapping the endstop ports⌠dunno why, probably hoping for a miracle Didnât help much!
You really should not be changing these, but they should not affect it as the homing settings are different. Unless you are playing with the touch screen side then all bets are off.
Please do any testing in Marlin mode, or over USB with repetier. Touch mode is not the same as marlin mode it sends itâs own things that I can not control.
The pins are bent in the same way on all the drivers, including the ones with the oversized heatsinks. I also have some tape on the capacitors below them to make sure they are not touching the pins directly.
The issue happens on Y axis sometimes as well, which is connected to the regular 2209v1.2 driver.
I was using marlin mode all the time.
It seems to me as if changing settings somehow messes up the board memory and it starts this weird behavior. Will do some more tests.
Between each home command I did G0 X50 Y50 Z150 to move the gantry away from the endstops.
After fresh booting a cold board in the morning:
tests: 10
success: 7
fail: 3 (2xZ1, 1xZ2)
After reflashing firmware without powering down the board:
tests: 10
success: 0
fail: 10 (3 resolved on its own after clicking and making noise for some seconds, 7 times had to reset)
After power down for 10+ seconds:
tests: 10
success: 0
fail: 10 (6 resets, 4 resolved on its own but didnât have proper home position)
Sometimes it looks as if the machine has homed properly (only a small click on one of the leadscrews in the 2nd phase, then goes on with homing), but the fact that the leadscrew clicks means that the motor didnât stop on time and the homing position is inaccurate.
The Z axis fails more often than Y, but this is probably because Z is homed first. Sometimes Z homes fine, and then Y axis fails.
Never had this issue on X axis yet, but it only has one endstop.