Okuma Inspection post processor

[Tomek.G]

Hi All,
we are working on a Okuma Inspection post processor and would be happy to get some feedback from you before we put it into production.
Feel free to download and test this post processor with caution and provide any feedback you might have.
Thank you.

https://cam.autodesk.com/hsmposts?p=okuma_inspection

[mdalesCRSD5]

I downloaded the inspection post today and did some tests.  Ran great, exported the results in a text file.  Was able to import that into Fusion and compare the results with the model.  HOWEVER, when I went to use my probe with a Renishaw cycle, it said my probe was not calibrated and I had to callibrate it again.  Something with the variables it uses I'm assuming overwrites my calibration values?  I'm going to have the apps guy check out the code and see what he says.

[sphennessy]

N10 IF [VSTOD[23] NE 0] N12

N11 M00(ERROR - PROBE NOT CALIBRATED OR PROPERTY ECCENTRICITY X INCORRECT)

It stops here at the m00 first. If i try to continue I get the error "2209 Alarm-b expression: local variable 545054"

Can you help with this?

[sphennessy]

I took the commissioning mode off and it ran through the cycle, touched all the points i programmed, now I'm getting "2305 Alarm-B UNTENDED: gauging impossible 43" at the CALL OO19 line. I was able to run the Renishaw probe cycle afterwards to see if it erased my initial calibration values but it did fine. 

UPDATE: I was able to use CALL O9833 and turn the probe off and the cycle works fine now. Hope this helps someone trying to use Okuma and Renishaw probe. Also, if you want the results file to overwrite the existing file

you can change this line in the post: 

writeln("FWRITC MD1:" + reniResFile + ".TXT;A");

and remove the A to be: 

writeln("FWRITC MD1:" + reniResFile + ".TXT");

[Tomek.G]

Thank you guys, we are moving forward!

@mdalesCRSD5 I've sent you a DM please give me more details on this issue.
@sphennessy I'm glad that you finally found a way to turn the probe on and off.
O9832 O9833 are Renishaw subprograms to starting and stopping the probe. If it's not working you can try to use M127
You need to make sure the probe is flashing green before it starts moving.

We need this "A" argument

Option function: “;A” Specifies the append mode added to an existing file.

• Format: FWRITC _(device-name:)file-name.extension;A

Option function: “;A” Specifies the append mode added to an existing file.

• Format: FWRITC _(device-name:)file-name.extension;A

---

The idea here is to add more information to the Renishaw results file so that Fusion can recognize it and check that it's being imported into the correct project.

Do you use Renishaw's Reporter? How have you previously checked the probe results (without Fusion)?

[mdalesCRSD5]

I use the Reporter app on the control to keep track of just a few dimension for long runs of parts.  Mainly bores/boss's and single surface features.  It would possibly come in handy to be able to check surface points in Reporter as well (I make primarily molds).  

[mdalesCRSD5]

@sphennessy Thanks for the tip with the text file.  I'll be changing that!