userfields.ini

[[Da...]]

One thing that bothers me is that no matter if I set

defaultValue=3

or leave it blank

defaultValue=

always shows input from previous measurement.
At least that is the case with u_fields containing lists, I'm not sure of those that don't.

Anyone else?

Also, is it a must to keep u_field entries lower case only?

; Now defining the first userfield named u_field1

; is the comment, right?

What about "REM", comment also?

[[No...]]

Please sign in to view this quote.

It gets even better! If you use the same measurement plan on different CMMs over a network, it displays the last input from the current CMM. If you then save the plan, this -perhaps outdated - value makes it into the inspection file.
No big deal, you say. Well, we use some kind of revision suffix at the end of a u_field entry which is important for our SPC software. Wrong suffix means data ends up in wrong location. This behavior can lead to a situation where an outdated suffix magically makes it back into the protocol header.

The culprit is the file "protheadpara", which stores the last input values. It exists in two locations for each plan, but IIRC only the one in the results folder is important. If protheadpara is present, it overrides any default values or values stored in the inspection file. I made a batch that's called whenever a plan is opened, which deletes all protheadpara files. Unfortunetaly this doesn't work in Autorun.

Please sign in to view this quote.

I recommend you just test if it works. I guess it won't, but what do I know? 🤠

[[Ri...]]

You do not have to directly edit the userfields.ini file anymore.

Go to Resources - Design custom printout - Editor for use-defined printout header variables.

[[Da...]]

Please sign in to view this quote.

Thanks Richard, I'm aware of that editor. The reason I don't like to use it is, because it leaves a mess inside userfields.ini file if you ever look at it later.

[[Ri...]]

Please sign in to view this quote.

I can agree with that.