Hi @chuck126,
If see you already read that thread, and while it does workaround the crashing issue, there seems to be a side effect on Z travel, probably because of a hardcoded Z limit inside Carbide Motion when HDZ is not selected (but it would be much better is @robgrz or @Luke could confirm if this is really the case?)
Anyway, in that thread we temporarily concluded that one option for now was to use a different G-code sender (e.g. CNCjs, it will let you jog as low as you want). But of course there is a small learning curve, it’s not ideal, however my understanding is that right now it’s either that or using CM but not using the rapid position (which you don’t seem to see as an acceptable solution).
No sure what it’s worth to you, but another workaround could be to use CM, enable HDZ, NOT use the rapid positions, but instead use manual MDI commands corresponding to rapid positions that you would determine manually (i.e. jog there once manually, make a note of the absolute coordinates, and then coming back to that position from anywhere boils down to using one MDI command like G0 X[value] Y[value] and click send). I’m not elaborating on that option right now, but if it makes sense to you I can.