Just tried 1.1f on my xc (old). Jogging completely wrong…speeds changed, and all jogging directions opposite to what they should be. Went back to earlier grbl file 1.0.
When you installed 1.1f did you update the grbl parameters that you changed to tune your machine for the earlier release?
All I did was update the hex file. I didn’t change anything within as I never had to with any previous version. (did put new easel driver 3.3 on however)
I think that 1.1f has changes that will cause the EEPROM to be set to defaults for grbl. Depending on which 1.1f you got the defaults may not match your machine setup.
Is there more than one version of 1.1f? And not sure what EEPROM is…
Yes, there are different builds for 1.1f just like there are for 1.0c and 0.9j. Inventables did their own build of 1.0c for the Xcarve people. The main difference was the choice of default values.
If you used the .hex file from Github it was most likely built with the generic defaults, not the Inventables defaults.
EEPROM is the memory device on the Atmega328P (Arduino/X-controller processor) where the grbl parameters are stored.
That makes sense then. Should I input the Inventable defaults fro previous version on 1.1f or where can I find Xcarve default version of the hex file other than Github?
You can use the defaults from the previous version if that version is 1.0c.
Don’t know that there is a specific build for the Xcarve.
Some of the parameters could be different on your machine if you did any tuning changes.
The differences for the 1000mm from the 500mm are $130 and $131. If any of the axes move in the wrong direction that can be changed with $3.
Here is an example for the 500mm Xcarve.
$0=10
$1=255
$2=0
$3=3
$4=0
$5=0
$6=0
$10=115
$11=0.020
$12=0.002
$13=0
$20=1
$21=0
$22=1
$23=3
$24=25.000
$25=750.000
$26=250
$27=1.000
$30=255
$31=0
$32=0
$100=40.000
$101=40.000
$102=188.947
$110=8000.000
$111=8000.000
$112=500.000
$120=500.000
$121=500.000
$122=50.000
$130=290.000
$131=290.000
$132=100.000
Thank you sir…once again you’re a gentleman!
I had “zero” issues updating I just re ran machine setup in easel , I’ve used UGS platform and Easel to run about 6, 3-4 hour jobs with only a few small issues with UGS loosing zero if I stop the job and try to recstart.
That is one thing I didn’t do … I will try that first before downgrading…
Thanks
R
Edit: Just ran the setup… no change…
Hello Everyone,
It looks like someone at Inventables gave @FatKatOne early access to test a new feature that will be released in the near future. Apparently that person either made a mistake in doing that, or forgot to let @FatKatOne know that was the case.
So to clarify, the feedrate override is not publicly available yet. We are doing some internal testing of it, but it should be available for release soon. Please stay tuned!
Jeff
It works good !! I know a while back I was talking with someone about grbl 1.1f not working with easel and they troubleshot with me I’m guessing that’s when it was activated, please don’t take it away from me I love it ! I’ll be happy to keep testing it !
We will not take it away from you 

I feel so special!
Like a fat kat 