@tomm77 It is very likely your “Zero Point Configuration” is not correctly set. What CNC machine are you working with?
If you go to Device Settings (wrench/screwdriver icon) → Basic Settings tab you can see the zero point configuration. Zero point origin is not the same as the home location on all CNC machines, depending on how they are configured.
(If you have limit switches and can home your machine) We have a new feature that might help with this, the “Ignore Automatic Zero Point Detection” toggle in that same screen. If you toggle that off, click okay, and then home the machine, it can detect the zero point on most direct control machine we support. After homing, go back into the Device Settings → Basic Settings tab and see if the zero point changed.
If you do not have limit switches or just want to ignore this automatic functionality, you can toggle the “Ignore Automatic Zero Point Detection” on and set the Zero Point manually. If you have this Zero Point Configuration set wrong you will be able to jog but Goto will not work properly and likely ($J) Continuous jog will not operate correctly either.
Hope this helps. Reply back with what machine you have, curious what you are working with.
If you can share a screenshot of the Device Settings → Basic Settings Page. Also what corner does your machine home to?
Here is a screenshot of a Lunyee 3018 Pro Max Device Settings → Basic Settings page. Not sure if it will be the same, it all depends on the firmware configuration but my best guess is that it would be either a back right zero point like the 3018 or a front left zero point.
Maybe to add here: after upgrading to the last RC, MM selected the incorrect origin (back right instead of front-left). I changed it in device settings, and MM complained, “I got this from the machine information; do you really want to change it?” (I don’t remember the exact phrase). It seems this is not working correctly, seems it also affects others.
I checked mine today and it had the same problem. Auto detect chose the back right for zero. It should be the front left on my LowRider4 running Fluidnc.
hmmmm my lowrider hasn’t had that issue in 3 days or RC 19, which board do you have , I got JP1
I do get a message that my y axis doesn’t match it has always been 2900 since i built my lowrider , but now its showing 2480 in fluid NC ??, when i change it back to 2900 it says accepted , but each day i turn it back on its gone back to 2480, will check it again in couple days as rebuilding my table so its not hooked up at present
If you are having issues with the origin setting inconsistent with your machine config, you can ignore the auto zero point detection and then set your origin, it will remain static on that device.
Can you share what the position is immediately after homing completed?
If you can turn on show all in the console, then right click on ‘Clear Console’, clear all and then home, then copy all the output and share it I can check what’s happening there.
I’d recommend turning that on as default. It seems it’s not really working for most machines, so it will cause fewer support requests when turning it off
On our internal machine pool it worked about 80% of the time… It works often enough to be worth it. But we’re working on better documentation and I’m happy to double check it to see where it’s going wrong.
To be able to better check, I’d appreciate the console output with show all enabled, after you clear it, and then press home, then Get Positions. It will help me a lot in understanding where the problem lies. @misken@tomm77@bperc
