Just fired up my workbee 1010 tonight to do some engraving and out of nowhere the machine is binding up when trying to jog in any direction on all 3 axis. It will move aprox 20mm then dead stop until I let off the jog button ( both using the keyboard or the button on the screen). I also tried running a small g-code file and it binds up everywhere. I used this machine last week with no issues, nothing has changed at all with the machine, no software updates, no hardware changes, nothing. has anyone seen this before? here is a video of what its doing, hopefully it works
Sounds like acceleration settings set too high (most likely from the noises in the video) Check gnea/grbl (Our Workbee 1010 Profile sets that to 150mm/s2: See OpenBuilds/OpenBuilds-CONTROL) so check if yours is way off? If that doesn't help, report back with: 1) Grbl Settings output (Send "$$" and copy/paste the output of Grbl Settings gnea/grbl from Serial Log ) To determine if its mechanical: 2) Disconnect motors from controller (because spinning motors by hand turns them into generators that can and likely will fry your stepper drivers in the next step)| 3) Spin them by hand and see if you feel resistance as well? 4) Investigate closer if thats the case Or electronic 5) What Power supply are you using
All settings look normal for axis acceleration, all 3 are set to 150mm/sec2 I am using the 24v Meanwell supply that is sold with the Workbee bundle here is the log: [11:04:01] [ $$ ] $0=255 ;Step pulse time, microseconds [11:04:01] [ $$ ] $1=255 ;Step idle delay, milliseconds [11:04:01] [ $$ ] $2=0 ;Step pulse invert, mask [11:04:01] [ $$ ] $3=7 ;Step direction invert, mask [11:04:01] [ $$ ] $4=1 ;Invert step enable pin, boolean [11:04:01] [ $$ ] $5=0 ;Invert limit pins, boolean [11:04:01] [ $$ ] $6=0 ;Invert probe pin, boolean [11:04:01] [ $$ ] $10=1 ;Status report options, mask [11:04:01] [ $$ ] $11=0.020 ;Junction deviation, millimeters [11:04:01] [ $$ ] $12=0.002 ;Arc tolerance, millimeters [11:04:01] [ $$ ] $13=0 ;Report in inches, boolean [11:04:01] [ $$ ] $20=0 ;Soft limits enable, boolean [11:04:01] [ $$ ] $21=1 ;Hard limits enable, boolean [11:04:01] [ $$ ] $22=1 ;Homing cycle enable, boolean [11:04:01] [ $$ ] $23=3 ;Homing direction invert, mask [11:04:01] [ $$ ] $24=100.000 ;Homing locate feed rate, mm/min [11:04:01] [ $$ ] $25=1000.000 ;Homing search seek rate, mm/min [11:04:01] [ $$ ] $26=250 ;Homing switch debounce delay, milliseconds [11:04:01] [ $$ ] $27=5.000 ;Homing switch pull-off distance, millimeters [11:04:01] [ $$ ] $30=1000 ;Maximum spindle speed, RPM [11:04:01] [ $$ ] $31=0 ;Minimum spindle speed, RPM [11:04:01] [ $$ ] $32=0 ;Laser-mode enable, boolean [11:04:01] [ $$ ] $100=196.814 ;X-axis steps per millimeter [11:04:01] [ $$ ] $101=197.881 ;Y-axis steps per millimeter [11:04:01] [ $$ ] $102=199.500 ;Z-axis steps per millimeter [11:04:01] [ $$ ] $110=2500.000 ;X-axis maximum rate, mm/min [11:04:01] [ $$ ] $111=2500.000 ;Y-axis maximum rate, mm/min [11:04:01] [ $$ ] $112=2500.000 ;Z-axis maximum rate, mm/min [11:04:01] [ $$ ] $120=150.000 ;X-axis acceleration, mm/sec^2 [11:04:01] [ $$ ] $121=150.000 ;Y-axis acceleration, mm/sec^2 [11:04:01] [ $$ ] $122=150.000 ;Z-axis acceleration, mm/sec^2 [11:04:01] [ $$ ] $130=824.000 ;X-axis maximum travel, millimeters [11:04:01] [ $$ ] $131=780.000 ;Y-axis maximum travel, millimeters [11:04:01] [ $$ ] $132=122.000 ;Z-axis maximum travel, millimeters [11:04:01] [ $$ ] ok disconnecting the motors and spinning them by hand and everything feels fine. no hard spots or excessive drag on any axis. As I stated I used this machine a week ago with no issues what so ever, ran flawlessly through a 2 hour G-code. flash forward to last night and it starts doing this as soon as I hook up and try to jog forward to my work location. nothing changed between then and now. the only thing that I can think is that a few months ago I had an issue with the blackbox losing connection and not responding after I tried running my tig welder while the machine was running a g-code. I somehow got it back and its ran dozens of times since with no issues. I have made sure that the machine and the tig are never being used at the same time since, but last time I used the machine the tig welder did get run while the black box was powered up and connected to the laptop. it was sitting idle not doing anything but the laptop and blackbox was still on and connected.
Do test with a lower acceleration, that wheeeep whoop sounds are accel/decel, and it does sound a little fast, maybe Grbl EEPROM got corrupted from the EMI from the TIG. Saving the lower value should overwrite the current settings, as they don't sound like 150mm/s (well, still hard via video) (There is also a reset EEPROM button on the toolbar on Grbl Settings tab, then load settings again) - refer gnea/grbl
bumped them down to 100 and its not doing it anymore. any idea what would have caused it to work fine at 150 before and not now? maybe EMI from the welder garbled it a bit or caused something to freak out? I will leave them at 100 and see what happens. from now on I will make sure the entire machine is off before the welder gets used.
Probably, high voltage EMI can certainly flip bits in the EEPROM, and the video didnt sound like 150mm/s^2 so possible it was corrupted.
