Material Settings Glitch

snowgoer540 wrote: But python might as well be moon man language. Maybe it's a mental block.

It often is to me as well...

So I’m afraid the glitch has reared its head again. On v .131. Today when I clicked save after changing settings, the first time it would go back to the original setting. I’d change it again and the second time it took. *shrugs*

Which settings?

I'ved noticed this too., I thought It saved the settings but then retrieved the old settings from memory and put them back in the field. eg. feed rate for a given material

I haven't been able to emulate that here.

Is it only the Default material or all materials?

Is it Gmoccapy and/or Axis?

gmoccappy and all materials

I have tried and tried but cannot duplicate the issue yet.

Is there a specific procedure I need to follow?

Is it related to machine state or something?

phillc54 wrote: I have tried and tried but cannot duplicate the issue yet.

Is there a specific procedure I need to follow?

Is it related to machine state or something?

Sorry, I was sleepy when I wrote the first post, I posted, and then promptly fell asleep...

Materials settings, and I am on Axis. I am unsure of machine state, but I can describe where I was when it happened....

Machine homed, touched off x and y at the corner of my plate, added a new material. It did it here the first time, I thought I just forgot to add a setting though. Then I was messing around with trying to get a marker to work during torch disable mode, so I set my cut height to .000, which didnt take the first time, so I changed it again, and saved and it stayed. Then PlasmaC gave me an invalid height error, so I changed it to .004, clicked saved, and clicked cycle start, and got the same error, when I looked, it was at .000. Changed it to .004, clicked save, and it took the second time.

This also happened going back to a normal height for cutting after I was done with my marker marking.

I can take a video this evening if necessary.

Anything will help. I haven't been able to duplicate it in Axis or Gmoccapy.

I changed one today and it seemed to stick without any problems so there might be a sequence. I'll keep an eye out.

There is one long standing bug I saw again today and I think its because my float switch is not working.
If the Ohmic probe fails and the float switch does not trigger and the end of travel is reached, the Z axis goes into a continuous never ending probing loop. My limit is set just below the material so generally what happens is my torch partly dislodges from the breakaway just before the end of travel is reached, but clips back into place on the up travel. Or probing over a void will cause it.