Soft limits exceeded with Continuous jogglng

Hi Brrian, Increase your soft limits ("x,y,z Max Travel" setting $130 - $132) or turn them off ($20=0)
Cheers
Gary

 

It should, is your steps per mm set correctly?
Cheers
Gary

 

You found a "bug" hehe! Our bad!

The way continuous jog work is we send like "move 1000mm" and then when you lift off the button, we send a Cancel Jog Now!
So 1000mm is a bit much! Give me an a day or two and I'll release a new version of CONTROL with a fix
For now, disable Soft Limits or use Incremental Jogging till the next version: See newly logged Github Issue for progress reports: Continuoes Jog: the 1000mm predefined jog is bigger than some machine profiles's Max Travel · Issue #109 · OpenBuilds/OpenBuilds-CONTROL

 

Appreciate it and yeah bring those issues to our attention! we can't fix what we don't know about (;

 

Did a little testing and its actually going to take some work to support soft limits, so for now, if you can live without soft limits (or maybe wire up hard limits on the other end of the axes) it would buy me some time

- Check if Soft limits is enabled or not and depending on whether it is, the command to send changes a little
- If it is, track Machine Position all the time so we know where we are in Machine coordinates too
- Also check the settings and know if we are homing to min or max, so we know where we can go
- for every continuous jog move, subtract current position and direction from the current Machine position and send move just long enough not to exceed machine coordinates - even relative moves have to comply with the max travel boundary so we have to do the math

 

Please post your Grbl settings

 

Thanks, will drop it on a controller later today and test with your settings in place

 

Cool.
Yeah will check, with 1.0.202 on the test bench here I can jog now with Soft Limits on, so will test with your settings and see if I can see why it still errors for you

 

Right so:

1. I copy pasted your settings and loaded it onto a controller here
2. Noticed Soft Limits is disabled, so Enabled it
3. Reset the board so settings all take effect
4. Tested continuous Jog and all works here

 

The code looks at whether soft limits is enabled:

Code:

var distance = 1000; // Default to 1000 works fine for machines without soft limit
if (Object.keys(grblParams).length > 0) { // have we already connected and pulled the Grbl parameters
        if (parseInt(grblParams.$20) == 1) { // If we have, lets check if $20 is set to 1
          // Soft Limits is enabled so lets calculate maximum move distance 
          // (calculated from mPos and Max Travel values)
          var mindistance = parseInt(grblParams.$130)
          var maxdistance = 0; // Grbl all negative coordinates
          // Negative move:
          distance = (mindistance + (parseInt(laststatus.machine.position.offset.x) + parseInt(laststatus.machine.position.work.x))) - 1
  }
}

So if $20 was 0 at the time of the test, it would send 1000

 

Pasted your settings again, ran up and down on all three axes for a couple minutes (making sure I am in Continuous Jogging mode) and no issue

Any other thoughts on something that could be different?

Can you check that F12 -> Console Tab -> Type in "grblParams.$20" and press Enter is "1" (image below)

(as its still sending 1000 and not a calculated value - the IF statement expects Grbl Settings tab to be populated and grblParams.$20 to be "1" so maybe one of these are different on yours)

 

man i hate cropped screenshots (; i cant get the big picture hehe pun intended. In this case i see a little green below the port dropdown. Did you not connect yet? I assume from the green bit there, it should be red when connected (uncropped screenshot would confirm)
Cant read the controller parameters till you connect (; therefore undefined.

And jokes aside dont crop, you never know what else may be a clue onscreen

 

Yes that is bug, dont tap too fast
Only in Continuous (incremental jog is all round the stable, oldie, logical one)

 

Havent seen any other reports yet, but Soft Limits are not widely used, which might explain why no one else has stumbled across this yet.

I will look at the code again next week

 

May I ask for a couple quick tests, maybe we see something your PC does differently with the data/code

Connect to the controller: make sure Soft Limits is enabled, make sure toggle switch under the jog buttons is set to Continuous

1) Press F12 to open Dev Console -> go to Console tab and Execute

Code:

Object.keys(grblParams).length

3) While we are in there, again check:

Code:

parseInt(grblParams.$20) == 1

(Last time I asked you to check you forgot to connect, so we havent actually seen yours (; yet

2) In the same console execute

Code:

allowContinuousJog

and check whether it says True or False (just to make sure the part of the code that checks the toggle switch is working right)

 

Correct! don't just love having fun in the dev console, watch out it gets addictive and in no time you want to develop your own stuff when you see how easy it is!

Distance is set to 1000 first (default state), then we check if Soft Limits are enabled, if it is, then:

It looks at current Machine position (not shown in the DRO, but you can find it by taking laststatus.machine.position.work.<axis> and adding to it laststatus.machine.position.offset.<axes> and subtracts the min or max distance depending on which way you are going and sets Distance to that.

Thus changing Distance to the calculated value.

As yours is still sending 1000 it means we didnt pass that "is soft limits enabled" part of the code yet else Distance wouldve been some non-1000 number

Sadly all your tests are EXACTLY the same results as mine, 34, true, true
Time for some serious head scratching....

And PS: A million thanks for the patience of sticking with me and helping me debug it. Issues like this that only happen on someone elses setup is always hardest and slowest to debug. If ONLY it was replicated here!