Siemens 840d inspection post does ot create a results file

[Bunga777]

I am currently using a DMU50 with a Siemens 840D Inspection post.

I am slowly getting to the point where I can do a variety of tasks and am planning to do inspections using probes.

I have created a program to inspect simple shapes and run it on the DMU50.

However, although the results are displayed on the screen, the inspection results file is not created anywhere.Are there any special instructions to output the file?

The post settings for output are as shown in this image.

The following posts seem to show that the same configuration is used to output the files, so I would like to know if you can tell me what the difference is.

https://forums.autodesk.com/t5/fusion-manufacture/import-inspection-resultat-fail/td-p/10751792

The posting file I am using was previously attached to this forum by someone else.

I am attaching the post we are using and the test file for inspection just in case.

[a.laasW8M6T]

Hi

It looks Like using Probe Geometry or Probe WCS doesn't generate a results file with Siemens, The Results are saved to parameters but not to a file.

Heidenhain/Fanuc etc Will output a Log file With Probe Geometry

Parameters for Cycle 977

If you use inspect surface like in the other Forum post it will generate results files for import back into Fusion

But that may not be what you're looking for.

[Bunga777]

Thank you for your reply.

Are the inspection result files output by control devices other than Siemens output by the program generated by the post?

For example, is it possible to modify the post for 840D so that the contents of the parameters are output to a file? Or is this currently impossible with 840D? I would like to know.

If there is any way, I would like to do something about it.

Also, I understand that the surface inspection data is output to a file, but this is only for understanding the deviation from the design model, and is not suitable for applications such as measuring each dimension. Is my understanding correct? Or, if the surface inspection data is output to a file, is there a way to understand the dimensions on Fusion?

[a.laasW8M6T]

Hi

I'm sure you could get the values in the parameters into a File but I know nothing about Siemens controls so I don't know how this would be done.

As for the Inspection results they are of no use on their own, they need to be imported into Fusion to compare to the Model.

Not really the best for basic measuring of Features using Probe Geometry like what you want.

@Richard.stubley  will know more about this, but as most Autodesk staff are on Holiday at the moment he may not respond until sometime early next year.

[Bunga777]

Thank you very much.

I will wait until after the new year for an answer!

[Richard.stubley]

Hi, I think I'm following but won't pretend to have read it all word for word. 

The inspect surface is kind of long hand inspection. We write out via the post every move so are fairly flexible to do anything the controller is capable of. 
We use the function to output to a file to create the results file. Again as we are in control of the whole process we can keep writing to it incrementally throughout the cycle. If you import this back into Fusion then you can see the results overlaid on the CAD or in a table. 

For the Probe geometry and Probe WCS toolpaths these use the canned cycles/ macros already on the controller so we are at the mercy of those unfortunately. It's been a while since I was working with the Siemens post but a quick bit of searching and I found this. 
In the post there is this code.

conditional(cycle.printResults, "_CHBIT[10]=1 _CHBIT[11]=1")

Looking at the siemens manual this outputs the result of one of the macros on the screen. 

In theory yes you can get the results written in a file. 
It's not going to be super easy, but doable. 

Caveat: If you wanted this to be imported back into Fusion then that is a much higher task as there is lots of information and references we need to pass through for the import to work. I'd start with just outputting it as a human readable value to start with. 

The NC code

RESULTSFILE = "VS_code_NC_files_RESULTS"
Starts the results file. 

You will also need this at the very start of the NC code

DEF INT RETURNCODE

DEF STRING[128] RESULTSFILE

DEF STRING[128] OUTPUT

You then need to put the measured value into one of the R variables. 

This is from the manual

So you would need to do something like
R10=$AA_MW[X]
R11=$AA_MW[Y]
I'm guessing this is the centre point, I couldn't see the measured size, like diameter in my quick look. But I'm sure it will be there. 

OUTPUT = "Measured X"<<ROUND(R10*10000)/10000

WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

OUTPUT = "Measured Y"<<ROUND(R11*10000)/10000

WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

Hopefully this at least gets you on the right track. 

[Bunga777]

@Richard.stubley  

I am sorry for the delay in responding to you.

I created the following Code and tried to execute it.

It was successfully executed, but the important thing is that it does not output any files.

I am using a DMGMORI DMU50 and am running it on an EXPC hard disk, but there seems to be a problem with the output.

I am in the process of contacting DMGMORI service.

If you have any clues as to why the file is not outputting, I would appreciate it.

; %_N_1001_MPF
; T="PROBE" D=6 CR=3 - ZMIN=-6 - probe

DEF INT RETURNCODE
DEF STRING[128] RESULTSFILE
DEF STRING[128] OUTPUT
RESULTSFILE = "VS_code_NC_files_RESULTS"

G17 G710 G90 G94
G64
G0 SUPA Z-1 D0

MSG ("Rectangular Boss")
N10 T="PROBE"
M6
D1
CYCLE832()
SPOS=0
G17 G90 G94
G54
G0 X0 Y0
G0 Z65
G17
G1 Z15 F1000
_CHBIT[10]=1 _CHBIT[11]=1
_TSA=2 _PRNUM=001 _VMS=0 _NMSP=1 _FA=12 _TUL=2 _TLL=-2
_MVAR=6 _SETV[0]=60 _SETV[1]=30 _ID=-21 _KNUM=0
CYCLE977
G1 Z15
G54
G0 Z65

R10=$AA_MW[X]
R11=$AA_MW[Y]
OUTPUT = "Measured X"<<ROUND(R10*10000)/10000
WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

OUTPUT = "Measured Y"<<ROUND(R11*10000)/10000
WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

M5
G0 SUPA Z-1 D0
D1
G90 SUPA C0 B0
G0 SUPA X-645 Y-295 D0
D1
M30

[Richard.stubley]

All I can think of is the results file location.
RESULTSFILE = "/WKS_DIR/OMV_WPD/VS_code_NC_files_RESULTS"

This would go in the Works Directory, then a folder Called OMV. 

There is another way of defining the location on newer controllers that looks like this.
RESULTS FILE

FileName = "/_N_WKS_DIR/_N_OMV_WPD/VS_code_NC_files_RESULTS"

Anyway, if you don't specify the location like you are doing it normally creates the results file in the same location as the NC code is run from. 
However I'm wondering, where are you running it from?
Maybe the controller cannot create the results file there. 
Try and run it from another location or maybe specify the location trying the methods I've shown above. 

[Bunga777]

@Richard.stubley 

I am very sorry for the delay in my reply.

I spent a lot of time contacting the machine manufacturer to resolve the issues.

I found that there is a limit to the drives that can be written to.

And I found that it is possible to write to the internal drive.

For now, I would like to proceed by writing to the internal drive.

By running the following program, we have reached the point where we can measure the spigod( 60 x 30 ) and write the results to a file.

; %_N_1001_MPF
; Machine
;   vendor: DMU50
;   description: Generic 5-axis
; T="PROBE" D=6 CR=3 - ZMIN=-6 - probe

DEF INT RETURNCODE
DEF STRING[128] RESULTSFILE
DEF STRING[128] OUTPUT
RESULTSFILE = "//LOCAL_DRIVE:/TEST.DIR/RESULTSFILE_MPF"

G17 G710 G90 G94
G64
G0 SUPA Z-1 D0
CYCLE800()

MSG ("Rectangular Boss")
N10 T="PROBE"
M6
D1
CYCLE832()
SPOS=0
G17 G90 G94
G54
CYCLE800(1,"",0,57,0,0,0,0,0,0,0,0,0,1,,0)
G0 X0 Y0
G0 Z65
G17
G1 Z15 F1000
_CHBIT[10]=1 _CHBIT[11]=1
_TSA=2 _PRNUM=001 _VMS=0 _NMSP=1 _FA=12 _TUL=2 _TLL=-2
_MVAR=6 _SETV[0]=60 _SETV[1]=30 _ID=-21 _KNUM=0
CYCLE977
G1 Z15
G54
G0 Z65

R4 =_OVR[4]
R5 =_OVR[5]
R6 =_OVR[6]
R7 =_OVR[7]

OUTPUT = "Measured X Length "<<ROUND(R4*10000)/10000
WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

OUTPUT = "Measured Y Length "<<ROUND(R5*10000)/10000
WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

OUTPUT = "Measured X Center "<<ROUND(R6*10000)/10000
WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

OUTPUT = "Measured Y Center "<<ROUND(R7*10000)/10000
WRITE(RETURNCODE, RESULTSFILE, OUTPUT)

M5
G0 SUPA Z-1 D0
D1
CYCLE800()
G90 SUPA C0 B0
G0 SUPA X-645 Y-295 D0
D1
M30

The output result will look like this

Measured X Length 59.9767
Measured Y Length 29.9904
Measured X Center 0
Measured Y Center -0.0044

I will need to get this into a file format that can be read by Fusion360 after this, if you can tell me how to do that I would be happy.

[Richard.stubley]

Hi @Bunga777,

Congrats on getting the output working!
Regarding getting the values imported back into Fusion. I'm not going to pretend like it is going to be an easy feat. 
Currently we only import the Renishaw format. We have spoken about a more generic one to allow exactly this but that's still in very early conversations and not been planned in any way. 

So, if you are going to get that imported you will need to copy the Renishaw format. 
Here is a sample of it. You will see we also use the toolpath ID as identifiers to match things up. I'd take a look at the HAAS post and look at how it's done there so you can use the same properties to get the ID numbers. We also need the G330 and G331 lines to get the orientation the measurements were taken in. Again not impossible by any means but it's not going to be a quick job. 

START
RESULTSFILE Probing_run_1_no_actions_RESULTS
DOCUMENTID 3f77c33a-4b57-417b-8738-be5515cf37e6
TOOLPATHID 4
TOOLPATH X Channel
G331 N1 A0. B0. C0. X0. Y30. Z45.
G330 N1 A0. B0. C0. X0 Y0 Z0 I0 R0
CYCLEDEPTH -6.

-------------------------------------------------------------------
   COMPONENT NO 77                   FEATURE NO 1
-------------------------------------------------------------------
SIZE D12.0000   ACTUAL 11.6800   DEV -.3200
POSN X-31.0000   ACTUAL -31.0275   DEV -.0275
POSN Y7.5000   ACTUAL NaN   DEV NaN
TOOLPATHID 8
TOOLPATH X Channel with island
G331 N1 A0. B0. C0. X0. Y30. Z45.
G330 N1 A0. B0. C0. X0 Y0 Z0 I0 R0
CYCLEDEPTH -6.

-------------------------------------------------------------------
   COMPONENT NO 77                   FEATURE NO 2
-------------------------------------------------------------------
SIZE D12.0000   ACTUAL 11.6780   DEV -.3220
POSN X-31.0000   ACTUAL -31.0285   DEV -.0285
POSN Y7.5000   ACTUAL NaN   DEV NaN
TOOLPATHID 9
TOOLPATH Y channel
G331 N1 A0. B0. C0. X0. Y30. Z45.
G330 N1 A0. B0. C0. X0 Y0 Z0 I0 R0
CYCLEDEPTH -6.

[Bunga777]

@Richard.stubley 

Thank you for your reply.

I took a look at the post to see if it is possible to make changes from the Haas post.

I could see where the first part was being processed, but after that I could not see where it was being processed.

It seems that we need to generate our own for the part from line 10 down.

Upon further investigation, I found a result generator probing.cps in the post library, which reproduces the format and outputs random test results.

I have a feeling that if I could copy the contents of this library and successfully incorporate it into the Siemens post, I might be able to get it to work, but I have a feeling it will be very difficult.

I am going to try to be able to output the test results in CSV format for now.

However, it is a good feature at the time, and we would like to make it available.

[Richard.stubley]

Yeah, in that second section all of this if from the macro on the machine

-------------------------------------------------------------------
   COMPONENT NO 77                   FEATURE NO 1
-------------------------------------------------------------------
SIZE D12.0000   ACTUAL 11.6800   DEV -.3200
POSN X-31.0000   ACTUAL -31.0275   DEV -.0275
POSN Y7.5000   ACTUAL NaN   DEV NaN

Then all of this is parameters passed through from the post. 

TOOLPATHID 8
TOOLPATH X Channel with island
G331 N1 A0. B0. C0. X0. Y30. Z45.
G330 N1 A0. B0. C0. X0 Y0 Z0 I0 R0
CYCLEDEPTH -6.

It would be no mean feat to do it. 


Glad to hear you are getting somewhere with it though!