1
General Mach Discussion / machine running irregular on button script
« on: December 13, 2010, 03:49:30 PM »
Hi All,
I am encountering a problem when running a button script.
It is a fairly simple probing script, for measuring flatness of a surface.
There are a few dro's involved for surface size, grid size, etc.
The script uses some Do Until...Loops to scan a surface for flatness in a regular grid.
Scanned XYZ values are written to a textfile.
For instance, on a surface of 270 x 400 mm with a 20mm measuring grid about 300 points are beeing probed.
This takes about 10 minutes.
During this scan my machine sometimes acts strange, it looses steps and is running irregular.
Also, when the probe hits the surface "G4 P.25" is used, a pause to allow for writing values to the textfile.
About 1 in every 100 times the pause is skipped, the probe backs off immediately to go to the next piont.
XYZ Values are written okay though..
Is there some explanation for this strange behaviour?
I never loose steps when running g-code.
I can run complex programs without a problem.
So, is there a way to scan with a g-code file?
Can XYZ values be written to a textfile while using g-code?
I mean g-code in a .NC-file, not g-gode in a button script.
Thanks for helping!
Rich
I am encountering a problem when running a button script.
It is a fairly simple probing script, for measuring flatness of a surface.
There are a few dro's involved for surface size, grid size, etc.
The script uses some Do Until...Loops to scan a surface for flatness in a regular grid.
Scanned XYZ values are written to a textfile.
For instance, on a surface of 270 x 400 mm with a 20mm measuring grid about 300 points are beeing probed.
This takes about 10 minutes.
During this scan my machine sometimes acts strange, it looses steps and is running irregular.
Also, when the probe hits the surface "G4 P.25" is used, a pause to allow for writing values to the textfile.
About 1 in every 100 times the pause is skipped, the probe backs off immediately to go to the next piont.
XYZ Values are written okay though..
Is there some explanation for this strange behaviour?
I never loose steps when running g-code.
I can run complex programs without a problem.
So, is there a way to scan with a g-code file?
Can XYZ values be written to a textfile while using g-code?
I mean g-code in a .NC-file, not g-gode in a button script.
Thanks for helping!
Rich