Unsupported PCM functions

[[ZE...]]

Does anyone know of a way to programmatically read/write to the post-parameters of a characteristic using PCM? Until now, I�ve been using an unsupported function that works using �executeCode()�. We are planning on updating to Calypso 6.4 soon, and the unsupported code Doesn�t work in the latest version (Imagine that). Any ideas?

Paul Robinson | 30.03.2018 02:50 |

[[ZE...]]

What is it that you're trying to accomplish?

Roberto Flores | 30.03.2018 05:16 |

[[ZE...]]

I need a new way to read the post-parameters of a specified characteristic, and also a new way to write additional lines to the post-parameters of a specified characteristic.

This is all I need in order to update an external PCM file so that it will work when we update to Calypso 6.4. (Currently running 6.0.0.8).

The external PCM file that I am trying to fix is executed as inspection_pre_save_pcm.txt and basically:
- reads the post-parameters of certain characteristics
- checks if the post-parameters contain a line of PCM code
- adds the line of PCM code if it is missing.

I might need to call Zeiss to get through this one. I don�t know how much they will want to help with this though.

Paul Robinson | 30.03.2018 06:43 |

[[ZE...]]

Well if it's something that works on 6.0 and doesn't work on 6.2, ill bet they would be very interested in figuring it out.
I'm still not sure what it is that you're trying to do.

Roberto Flores | 02.04.2018 09:11 |

[[ZE...]]

Aaaaahahahaha, yeah. Im shure Zeiss love to help with a syntax they not been told about, don't understand, and you as a customer should not know about 🙂

It still work in >6.2.12. But it does not work as it did in previous versions.

How ever, it sound like you can accomplish what you are trying to do with a different approach, just a tad bit more work to do It by hand :p

Eric Moberg | 02.04.2018 10:26 |

[[ZE...]]

Yeah I had the same thought about Zeiss being able/willing to help with this.

The only alternative I can think of is to access the post-parameters by reading through the inspection file instead. But I was avoiding that. Altering the inspection file runs the risk of corrupting the measurement plan if something goes wrong. It may not even be possible if there are file access issues.

Paul Robinson | 03.04.2018 07:23 |

[[ZE...]]

Altering the inspection file while the program is running is not very clever indeed, and it will be overwritten once you save anyway.

If you give more info about what you are trying to accomplish, it will be easier to help.

Sounds to me, as you wish to do something after every characteristic. Why not do it all at the end of the inspection, just iterate thru all characteristics and perform you actions?

I don't want to update on what to do to use the syntax >6.2.12. Since last time I shared how it worked Zeiss made a totally unmotivated change in the next patch, that I can't see the use of, except preventing people from using it. (And that I can understand, cause you can literally destroy the cmm if you wish to do that, or is retarded. Some older machines use ball screws (I've heard) , and that can build up some torque, combine that with collision detection off as an example, and you have a party 🙂

Eric Moberg | 03.04.2018 08:52 |

[[Kr...]]

Hallo Paul,

to read, try this:
fff = getNominal("cfs").collection
bbb = fff.first
eee = bbb.collection
//eee = getNominal("Groupname").collection
eee.first.postParameter.parameters
But I didn´t find a way to write until now.