Control Definition problems in X

[calnet42]

Here goes.. my first post to this group.

I am trying to edit the misc. int/real values screen and the edits don't seem to stay.

I am editing them from the"machine def. manager" then choosing "edit control def.".

When I save, exit and reenter, the edits have disappeared.

[gcode]

Are you starting your edits from Files/Edit in the

Operations Manager or from the "Machine Type"

dropdown on the main screen??

[calnet42]

from the "machine type" dropdown

[Paul Decelles]

To permanently change any settings in control definition you need to make the change in the global copy of the control definition. This is accessed via the Machine Type dropdown. When you select a machine to use and create a Machine Group in the operations manager, you create a local copy (a "snapshot") of the global CD. Any changes made in that machine group only effect that machine group. They are not saved to the global copy.

 

One more thing I need to point out. The miscellaneous integer and real default values are written to and read from the post processor file along with any custom post text that you may set in the control definition. Because of this, you cannot set your post to read only and then make any changes to these values.

[calnet42]

Thanks Paul,

The changes to misc. int/real values which are stored in the post do not seem to be updating in the control definition when acessed through the machine type dropdown.

[Paul Decelles]

#1 - Make sure the .pst and ,control files are not set as read only.

#2 - Open X (in Design mode), load your control definition via the Machine Type drop down.

#3 - Make sure your post is displayed in the Post processor selection area.

#4 - Change to the misc value.

#5 - Save the control - Green check out.

#6 - Reopen the control, load it as above and make sure you have the post selected. Is the value there?

 

If it is, great. If it isn't, zip to go everything and send it over to me... [email protected]

[calnet42]

Thanks to gcode and Paul for responding to this post.

 

I believe the issue is resolved now.