Hi,
I've just started migrating from Mach4Hobby to MachPro.

One of the small changes I want to make is to have a <Zero (axis)> button alongside each DRO, much like the Mach4 screen set I am so familiar with.

With the scree editor open  I have located the  text axis label, "X" for example. Rather than delete it I've 'kicked it out' of the veiwable window by nominating
its location at1005, rather than at 05, when it is viewable. That works and when saved it sticks for the next MachPro session.

What does not work is when I drag the <Zero X> button from 1017 to 017. The button displays and I can try to save the screen edit but when a new screen is
drawn the button is absent. I've tried dozens of variations on editing the screen and the attempt to save it without being able to get the edit to permanently save.
The AI coach suggests that I use <F5> to ensure that a new Lua script is generated prior to saving.....and it seems that it does not work.

Has anyone had any similar experience?

Craig

Hi,

The reason for this is that the modularity of the screen is hard coded. The buttons you place there are being written and saved, but they are being overwritten. We reccomend using the Dashboards in order to get your Zero's on your main screen.

https://support.machmotion.com/books/cnc-software/page/machpro-widgets-dashboard-commands-and-function-buttons

Hi Paul,
I'me somewhat skeptical of your explanation.

If for instance the AxisPosition panel is hard coded then why is it that I can kick the AxisTextLabel out of the viewing area, and that is saved accross future MachPro sessions.
Also I have dragged the A (U)  and C(W) DROs, the AxisLoad indicator and the DistanceToGo DRO into the viewable are and they have all been saved.
Were they hard code then they too would be overwritten, but they are not.

When however  I drag a ZeroAxis button into the viewable are it is not saved?

In Mach4, say either wx4.set and wx6.set there was a ZeroAxis button alongside each DRO. It does not seem to much to ask that I be able to replicate that functionality,
and lo.......there is the button, already instantiated, coded and ready to go just by dragging it into the viewable pane, and yet it does not stick?

Actually I very much like the idea of all the different buttons/controls/DROs/LEDs/LabelTexts all be instantiated, ready to be included in a customers screen set, all you have to do
is drag them into the viewable area, but it would appear that some will not save. That means that the screen editor is broken, you could certainly do as I wish in Mach4, but now it does not work.

Craig

Hi,
discovered another failure of the same type.

I have a button included in the ControlGroup of my current installation. It is to drill location pins in PCBs which I regularly make.

Just a few moments ago I tried to increase the size of the ControlGroup (in MachPro) to accommodate and instantiate a new button. Saved the screen and exited, but
when the screen is redrawn my screen edits are gone.

One of the greatest strengths of Mach4 was that you could place a button/LED/Control DRO etc wherever you pleased and attach whatever code you pleased to achieve the
functionality you wanted. MachPro doe not permit this. It is a fault that needs be fixed.

Craig

Hi,
after some more experimenting I have found, as you suggested, that if the A and C axes are not enabled then the corresponding DROs disappear whether I deliberately
drag them into the viewable area or not.

The bottom line is that the Axis Position Group IS NOT EDITABLE........and that is faulty.

You've taken away one of the greatest strengths of Mach4.

Craig