I’ve used many CAM systems - from MeshCAM to those costing tens of thousands of US$ - and I’ve found MeshCAM to be wonderfully useful for many small to medium complexity jobs.
Although I recently found what looks like a serious bug in MeshCAM:
I’ve never found another bug in it despite more hours than I can remember working with it (not to be compared to @Randy however!).
That said, it is quite different than every other CAM package I’ve used (there are some similar but I’ve not used them). I found MeshCAM… unusual at first. Every CAM package has “CAM think” and MeshCAM is no different. MeshCAM definitely takes some getting used to.
CAM for CNC is not 3D printing and there are a few somewhat non-obvious things to get right. That said, the steps of a work flow are consistent and make sense once all of them are grasped.
MeshCAM generates G code; it doesn’t send it to the Nomad, Carbide Motion (CM) does. Is CM giving you the problem? If so, I do understand as it takes some getting use to - and there isn’t any good documentation to study as yet.
My first few hours with CM were quite frustrating - I do sympathize - as it just didn’t make sense to me. Now that I see the approach, I like it.
We’re here to help.
mark
P.S.
I use Tormach’s and setting them up isn’t much different than using a Nomad. MeshCAM on a Tormach is no different than the Nomad.
@Randy actually owns a Tormach - of many years of use - and can talk about MeshCAM in detail.