X axis binding on outline

Hi Chris,

Good to hear the first issue is gone. Sorry to hear it was only a stepping stone to the next. Oh well, lets see what can be found on grinding axis and what to do about them.

Here’s info on slb movement and cutting speeds:

And here some info on calibration inside gsender you might find interesting:

Hi Eddie, just an update. After running the calibration, specifically movement tuning. That did show the x-axis was out so changed to from 100mm to 800mm. I then attempted to run an outline which resulted in the same issues as before. So ran a diagnostic which showed a lot of interesting stuff in red but right now is all Greek to me. Will start reading the gSender manual next to try to translate all the messages into a single how to fix the problem message. At a guess I figure that all these messages show a domino effect. By the way should I be opening a new topic for this problem, maybe in another sub-category.

@Petamain I could move this to a new topic for you, but I’m not clear what the title should be as I don’t understand the nature of your latest issue. :grinning:

Is the issue now that your X axis is grinding and therefore not moving as it should?

Sorry Eddie, not used to asking for help . Was just not sure if this new problem I’m trying to address still belongs in this category and that it was just an after-thought to my update. The problem is when I’ve centered my project for a run, just before I start I always do an outline run just to make sure its reasonable. Well the problem with the zeroing out came up at the same time. So in point form

  1. I center my project
  2. Check the gcode
  3. check the outline
  4. it starts out well moving to the left on the x-axis
  5. it goes back a bit on the y-axis
  6. then it starts to move back and up on the xy-axis
  7. it starts grinding
  8. gSender reports that movement is proceeding as per the program
  9. the router bit starts losing ground
  10. the run then proceeds left on the x-axis, still grinding
  11. when I stop the run the enter point has shifted to the right because the router had lost positioning
  12. the first error comes out as “G-code words words consist of a letter and a value. Letter is not found.” several times
  13. the second error comes out as “hard limit has been triggered. machine position is likely lost due to sudden hold. Re-homing is highly recommended.” and that comes out several times
  14. then “EStop asserted, clear and reset”
  15. then “homing fail. the active homing cycle was reset”
  16. then “homing fail. pull off travel failed to
    clear limit switch. try increasing the pull-off setting or check wiring.”
  17. after all that the errors recycle

and that friend Eddie is the definition of the problem. now I would like to continue with your help as it has been excellent but I expect there are different people specializing in the various area because you knew exactly what was most likely to help with my other problem.

to tell you the truth this is the first time I have used this form of help and so I guess I have mess up a couple of times on process and have asked questions in an incomplete fashion. it will get better.

@Petamain As you can see, Chris, I’ve created a new topic and moved it to the “something’s up” category.

As an aside, there are no hard and fast rules here around asking for help. That is what this place is for. You can’t “mess up”. If I see that your question may get more interest in a category different from where you first put it, I’ll move it there. No harm. No foul.

I hope that either someone here or Sienci tech can resolve your issues.

Hi Chris,

No need for sorrys, I am sorry I came across blunt, English is not my native language and on top of that, I’m Dutch, known to be a bit wnat’s the word… oh yeah… blunt. We wear wooden shoes, what can I say.

Anyhow, a binding axis is problematic, but at least it’s prolly not caused by some mysterious electronic problem. Binding mostly is caused by mechanical deviations that results in the machine no longer able to keep up with the acceleration and/or speeds set in the controller.

Since the outline is done on high speed settings, it has a higher probability to manifest during these steps.

Maybe you can even check if you can replicate the problem by jogging around long distances to see if you can replicate the binding on high speed, vs normal speed.
If you can, you maybe be able to notice paterns. Maybe the binding is on a certain spot, or more on one side of the machine.

Points of interest are the binding axis. Anti backlash nut, v-wheels tightness, and lubrication.
The maintenance guide will mostly get you to these points. It might be a good idea to check if your binding problem is changing after each step. I would, cause, you know, something with being lazy.

If these steps don’t work, you can look into changing speeds and acceleration to see if you can get it to not binding anymore. The SLB has higher speed and accelerate settings. Maybe if you reduce these settings to what they where when you ran the longboard, you are in the clear again.

Here’s what they are on the lb

Against what they are in slb settings.

Found here

And here

1 Like