It will be all what I want because of using ;C parameter, yes?
yup, ;C simply vanishes current file content ... is like the file was never there
So, if I want to add to beginning of the measures file for each part something like this:
that code looks ok at the bottom, you may find a futher development ...
I exactly work on OSP-P300SA
most of my time goes into p300
this is tempting vision to use
using an xls works nice, but there is possible to create a custom file also by g-code : thus, you may check and comment your measurements through g-code, and create a report that is fast to inspect; imagine that you see a column full of "okeys", or "go", etc, and simply no longer care about absolute measurements values
thus is possible to read results.txt, analyze it's data, and create a report, by using g-code
ultimately in neerest future we won't have access to machine eccept basic function (the keys will be taken)
protection is ok for proofed setups, but still is needed to analyze each reason of downtime, thus is needed to analyze the feed-back from the machine ... protection without feed-back is not ok
there are methods to :
... protect, even if keys are still there
... edit, even if keys are gone
* so is relative
i think that is all fine as long as you are able to test whatever you wish
Once again thanks for all Your advices
Code:
(
you can write A-Z and a-z, thus smalls and CAPS
i like to indent code
)
FWRITC results1.txt;C
PUT ' detail'
WRITE C
PUT ' operation'
WRITE C
PUT ' series : '
WRITE C
PUT ' part : '
WRITE C
CLOSE C
(
PUT handles 16chars maximum, but is
possible to write longer lines, by using
at least 2 PUT's
next code output's same text as
previous, only that it will all be
on a single line
however, there is a line length limit
last time i checked, it was :
- 1000 chars for p300
- 160 chars for p200
* earlier p300's couldn't handle more than 160,
but that was fixed among the way
)
FWRITC results2.txt;C
PUT ' detail'
PUT ' operation'
PUT ' series : '
PUT ' part : '
WRITE C
CLOSE C
(
next code outputs same result as the 1st
one, only that it performs noex-faster
)
FWRITC results3.txt;C
NOEX PUT ' detail'
WRITE C
NOEX PUT ' operation'
WRITE C
NOEX PUT ' series : '
WRITE C
NOEX PUT ' part : '
WRITE C
CLOSE C
(
this one performs even faster
because WRITE C is used only once, even
if there will be written multiple lines
WRITE C writes the buffer to the file
and creates a new line; you may create a
new line also by using PUT $0D0A
in the end is still required a WRITE C
in order to write the buffer to the file
WRITE C performs slower than PUT,
because it needs to print the buffer to
the file-phisical-path, while PUT only
writes chars to the buffer-virtual-variable
final result, thus the file, may look
to have separate lines, or maybe 1 single
line, depending how your text-editor behaves
also, file layout may change from
multiple lines to single line only after
it had been opened with a text editor; it
sounds a bit weird, like file may get messed
only if it is opened, so why would one create
a file that is not stable ? but the purpose
is to shorten g-code duration, and use a 3rd
application to read the output file, thus to
avoid file handling by a person; this trick
may be too much for a few probing results, but
it comes in handy when you record many data from
the machine, in order to create time-charts
i use timecharts, in order to detect anomalies
when a program runs, thus i may locate a donwtime
even if an operator is not noticing it; it's a nice way
to play it smooth, non-intrusive
)
FWRITC results4.txt;C
NOEX PUT ' detail'
NOEX PUT '$0D0A'
NOEX PUT ' operation'
NOEX PUT '$0D0A'
NOEX PUT ' series : '
NOEX PUT '$0D0A'
NOEX PUT ' part : '
WRITE C
CLOSE C
(
last but not least, a few
cosmetic tips :
- you may write tabs : PUT ' ' that's a tab, not many spaces :]
- you may use more than 1 put / line of code : PUT ' this ' PUT ' is ' PUT ' sparta !!! '
)