Hi Colten,
you are right.
When I downloaded a fresh copy of MachPro I downloaded a DEMO version. I have a license and I applied that, whereon MachPro changed to 'Licensed'.
I downloaded a fresh copy of the ESS plugin, but that's where I stalled. I could not get MachPro to open and recognise the ESS plugin. The latest ESS plugin is 320,
at least according to the Warp9 website.
This morning in a fit of desperation I downloaded a new copy of MachPro, but this time at your advice made sure that it was a 'Normal' copy rather than DEMO.
That in turn bought up the dialogue about setting the ESS as motion control and it automatically installed ESS v326. But that is not the same v320 as recommended
by Warp9. I can only assume that v326 is for MachPro whereas v320 is for Mach4???
Anyway, MachPro is successfully installed, the license file applied, a suitable ESS plugin installed and the ESS as the active motion control. ALL GOOD!!!!
This whole episode has rather been my own fault.
Several days ago I downloaded MachPro for the first time, and it installed correctly, with license and ESS plugin.
I had tried editing the AxisPositionsGroup using the screen editor, but found much to my frustration that I could not get the edits to 'stick'. Indeed this forms the core of another
thread about that exact same subject. Paul Stephens has very adequately answered that enquiry.......but in my effort to edit that group had screwed it up to the extent that the
AxisPositionGroup failed to load at all. Bugger!!! That's when I decided to download a fresh copy of MachPro.
The take-away lesson is do not try to screen edit those hard coded groups lest you succeed in screwing up the functionality therein.
Thanks for your help. I'm now back to configuring MachPro to suit my machine.
Craig