hello again it worked, not because of $08, but because of ;C
you may replace $08 with a space, or any char, and in the end file size should be 3 bytes ( the char that you used in put + end of line + new line )
i have run a few tests, in order to see if $08 works, and it failed ( attached shows files created by this code ) :
Code:
( this test checks if $08 can delete chars from current buffer )
( final content should be '123'+new_line+'45', but $08 does not work, so there is also displayed '6' and also the $08 char )
FWRITC a1.txt;C
PUT '123'
WRITE C
PUT '456'
PUT $08
WRITE C
CLOSE C
( these test checks if $08 can delete chars from existing content )
( 1st is created a file with content '123'+new_line+'456' )
FWRITC a2.txt;C
PUT '123'
WRITE C
PUT '456'
WRITE C
CLOSE C
( this tries to open the above created file, and delete a char from it's content )
( code fails, and by so, '6' still remains inside the file, and also $08 is displayed )
FWRITC a2.txt;A
PUT $08
WRITE C
CLOSE C
with okuma g-code, i recomand writing only read-able text inside a file
so far, this is it with file-operations, but if you target probing results in order to create a list of measurement, you may futher more customize it by using excel; imagine that after the measurement, an xls file is generated, with layout as you wish, and also results coments, like "ok", "towards minus", "0.02 under lower limit", etc ... this speeds up the reading&interpretation, thus imagine that you see a column that is all green : you will no longer care what values are the actual measurements, simply because you see in <1second that all are ok
okuma osp comes with excel, so such reports can be created on the machine / kindly
ps : you may use FWRITC results.txt;C instead of FWRITC MD1:RESULTS.TXT;C ... all files are written to MD1( so far i never succed in writing to a different path ), so no need to specify it, and CAPS are not a must ( at least for osp-p300 )