Have a look at rs274ngc_interp.hh:L233

The functions starting comp_get_current(...) appear to get and set the values in the initial settings struct.
Initialised in rs274ngc_pre:L113 and struct detail in interp_setup.cc / interp_internal.hh

I haven't looked much at it, but assuming this struct is updated throughout, to hold the current values for all the settings, it may be of use.

If you have a sim which can switch kinematic modes using your components, I may be able to assist more.

I don't have any machines that use anything other than trivkins.

On 24/04/18 14:12, [email protected] wrote:
I believe I found the culprit. While everything seems to be in order in the motion controller, I believe the GCode interpreter still believes it's at the previous position after a kinematics mode change. Manually executing a g0 to the currently displayed coordinates after a change and then executing another command seems to work perfectly. Now to find where to change that...
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

--
website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to