Anyone seen this...

[[Mi...]]

Error Message.. Object reference not set to an instance of an object

I can run the prg back to back and at times I have no issues. I cant seem to find whats its looking for in the program.

I get the same error in Auto Run also. Cant figure it out... 😡

[[Mi...]]

I get the same error message but only on the first run of a new Plan. I can regenerate the data (running from Characteristics without clearing) and for that Plan never see the error again.
Similar problem?

[[Mi...]]

Yeah but only happens on 1 of my programs. I can run a 5 part loop, and it will shytcan on 1 of the runs and show fine on 4. I'll close out the prg and restart it and it will do the same thing. Maybe its something Zeiss will look at as I have exhausted a lot of time in searching through all the menus and cant come up with anything that it might be looking for....

And wouldn't you know it, its a prg that the off shifts run through Auto Run and NO way will they be able to run w/out clearing. Some of them do good to get the machine off screen saver 🤣 🤣

So for now Ill have to go back to the custom report on that 1 prg till I can find a fix. 😱

[[No...]]

I don't know if this is helpful in any way, but the technical background of that error message is that "something" that should have a concrete value is instead "not defined" (NULL). It's a typical error in database environments (like PiWeb).
The reason may be as simple as an input field that was left empty, but can as well be a much more complex issue.

[[La...]]

Are you running Calypso 2017 lower than 6.4.08? This is a common issue in the first release of 2017 from what I've seen. If you install the service pack, it should work fine after that.

I'm still seeing a bug when using Standard Protocol and running a program where I'm ONLY executing the alignment and I have no characteristics. Then it pulls up data from some inspection plan I had run in the past. Really, really weird.

[[To...]]

Please sign in to view this quote.

Hey Laura, I see that on a regular basis in my classes. I'm guessing that we've previously collected piweb data on MeasurementPlan1 and then in the next class, when running only the base alignment on MP1, it's recalling data from a previous life. That's my story and I'm sticking to it.

[[La...]]

Tom, That..........actually makes perfect sense. It only ever happens in my classes, too. Still confuses the hell out of people when they've only run the alignment features and a report with red all over it pops up.

[[To...]]

Especially since Multiple Printout/PiWeb is ON by default, so the PiWeb database is created and working right off the bat.
Do you work with Jim York? If so, please pass my regards onto him. God knows he never answers emails. 🤣

[[Mi...]]

I loaded the Newest SP yesterday, so I will run some of the problem child parts and see if it still acts up...\

[[La...]]

Please sign in to view this quote.

Tom, yes I do work with Jim York! I will pass on your regards. If you're using his zeiss.com e-mail, that one doesn't work anymore. None of the apps people here have zeiss.com accounts any longer, they took them away. I can PM you his current e-mail address. 🙂

[[To...]]

Please sign in to view this quote.

He didn't answer my emails when he HAD a zeiss.com address. LOL I know he was always so very busy, to I'm not holding a grudge. Sure, you can PM his address to me. Thanks!

[[Mi...]]

With the upgraded SP the error does not pop up. It has been 4 days and so good so far.... 🧑‍💻

[[Ca...]]

I am trying to make a report but with our own format, and use it to complete records in our own Database system.
This my first incursion in PCM, License acquired recently.
*********************
I've followed the Jim York instructions, so I try to convert the result of each characteristic in a record on a .txt or .cvs file, but when the program run the Line Profile Characteristic, the correspondent group of codes erases the rest of information on the file.
The Presettings for the program run well, create a new file any time, but the problem is the rest of Postsettings for characteristics.
Here the problem:
But when I run only for recalculate the characteristics, then in the file only appears the DIM25_Line Profile characteristic.
Here the problem in a picture, but when I change the order of the characteristics putting this DIM25... on top, then appears all the dimensions but not in the right order of course, the problem is WHY? The Presettings is the same!

The code taken from JIM YORK here in a picture:
SOLUTION SOLUTION
As Laura Jaschke wrote, we have put the Presetting for the general Measurement Plan and all the programing section inside the characteristic in a general PCM section in Postsetting of the Measurement Plan. So when the program run with or without real part ever writes a new file with all record and right order....

[[La...]]

Please sign in to view this quote.

You should post separately in a PCM thread. This will be buried in a PiWeb thread.

[[Ca...]]

Hello community, thanks for your support.
I'm trying to access the intern values from an GD&T characteristic: Position
The codes used are similar to the used in a Line Profile, in this last case functional, but for Position ever with an error:
Here the codes:
//******Postsetting for GD&T Location True Position ***************************
//get the dataser from characteristics and store in file
THIS_CHAR="DIM40_Position1"
THIS_NOM=formatL(0,4,4)
THIS_ACT=formatL(getActual(THIS_CHAR).actual,4,4)
THIS_MAXTOL=formatL(25,4,4)
THIS_MINTOL=formatL(0,4,4)
THIS_DEV=THIS_ACT
SEND_OUT= THIS_CHAR +","+ THIS_ACT +","+ THIS_NOM +","+ THIS_MAXTOL +","+ THIS_MINTOL +","+ THIS_DEV
//add dataset to record in file
addToFile(FULL_OUT, SEND_OUT)
//**************************************************************************************
Here the error:
How to access the specifics elements of this characteristic: X position, Y position...actual usw....

[[Er...]]

I'm on Calypso 5.2
I find that Calypso is looking ahead in the feature list. If a feature is dependent on another, running it first, and putting another feature between the two solves the issue.

[[Ca...]]

Thanks,
I have still the doubt about this procedure, for Line or Surface Profile they have many dependences from Datums, I have access to the most important attributes of Line Profile (black color arrows and ellipses) but not the case for Position. In fact both Form and Location (GD&T) characteristics have the same Datums and only I need access to this 2 attributes (in red color) but no way, I did not find any documentation about the correspondent attributes in getActual()... for Position in particular.
Here the picture about my doubt and the functional code for Line Profile.
I have proofed for Flatness, Cylindricity and Parallelism the same code and all are functional too, but Position (True Position) with this problem to access attributes.

[[Ca...]]

Hello CMM Zeiss community (Calypso 7.0.02)
Here I want to share the program in Presetting and Postsetting for the general measurement Plan.
In Presetting (taken from Jim York public video...)

With this code we can create after each run or recalculation a file with the correspondent name of the program and part number at the end....
Now after the Measurement Plan ends we can obtain inside this file the correspondent records for characteristics, I must research about create an array with characteristics and then select from this array or subarray if Miniplan exists usw.
The next lines of code are inside Postsetting of general measurement Plan, the same as Jim York shows in his video but with some changes.

I have checked the codes from Line Profile in other GD&T like Parallelism, Cylindricity, Flatness and are functional, but not the case from Position.

[[Er...]]

getActual("Position1").deviation
getNominal("Position1").tolerance.upperTolerance

You should really look in to defining functions.... Who ever comes after you to maintain this will think you pro-activly hated them 🤣

I would suggest to dump all of this, and in the program post-settings loop thru all characteristics and dump the data then. Or prefferably parse the table-files.

[[Ca...]]

Super, Prima Toll,
The codes only for rapid test Eric or community, not a real programming style.
When I trying to format with formatL the getActual(...).actual was error, of course only following your instruction this works, only with .deviation, naturlich the math vor is 2*sqrt(xdev^2+....) but other GD&T have the same format (or Max-Min usw...) and we capture the current value wie .actual??? If we look the pictures all are Actual labeled, and then why .deviation?
Also, Thanks a lot Eric, that is only my first steps in PCM.
SOMEBODY KNOWS WHY .deviation and NOT .actual LIKE THE OTHER GD&T CHARACTERISTICS?