Jump to content

Excel Reporting failing


---
 Share

Recommended Posts

For no known reason, when I attempt to use the "Excel-Report" option at runtime, the program crashes with this error.
See image: Parameter_IP #11,14e8 TP_Ø0.28_D is not defined.PNG
So I create a characteristic as named (Because it doesn't exist and has never existed in this program).
IP #11,14e8 TP_Ø0.28_D
Then I get this error:
see image: Parameter_13 is not defined.PNG
This only happens when the "Excel-Report" option is enabled. All of those files are OEM, as in unmodified.

There is no PCM anywhere in the program.

Any help is appreciated.

Parameter_IP #11,14e8 TP_Ø0.28_D is not defined.PNGParameter_13 is not defined.PNG

Link to comment
Share on other sites

There might be a formula in the Name For Output Files definition.

Make a copy, and in the copy, delete the "inspset" file. See if it still throws the error.
Link to comment
Share on other sites

I have determined this is due to Excel, or the ".xlt" and ".ini" files that come with Calypso.
I ran a non related program, and have the same issue.
It seems to select a Characteristic, appears to related to True Positions, and decides it is missing a formula that doesn't exist and shouldn't exist.

P.S.
This particular system is Calypso v2019
Link to comment
Share on other sites

Please sign in to view this quote.

Any of the named entities in the error message do not appear in the "inspset" files of any program tested.

Thank you for the suggestion.
Link to comment
Share on other sites

Opening the CMM program in Calypso v2019 on a separate system runs fine and generates the excel report.
Opening the CMM program in Calypso v2021 on a separate system runs fine and generates the excel report.
Link to comment
Share on other sites

Have you tried moving the xlt and excel INI files from the working system to the non working system(backup the existing ones just in case, of course)? I don't know that it would resolve the issue, but would at least function as a diagnostic step.
Link to comment
Share on other sites

  • 3 months later...
Follow up.
I ran a program on a system where it generates Excel file without issues. (Not PiWeb).
I had copied that program to my laptop (Which was not able to create an Excel file) and now it can create an Excel file.
🙄

Anyone who is having issues creating an Excel file and get the typical error; "object variable or with block variable not set", can you get a copy of a CMM program from a system that creates the excel file and run the data thru your failing system?
I would like to see if this is some sort of fix.
Link to comment
Share on other sites

Please sign in to view this quote.

Rick, this is totally unrelated, but go sweet talk someone up front in sales for me. I'm looking to buy a $3,500 pin gage library and the almighty Google says that MSI Viking has the best price.

I'm hearing crazy lead times of 12-weeks on these, so that sucks. I assume MSI Viking gets these directly from the manufacturer, Vermont Gage.

P.S. Congrats on the excel fix. I hope it sticks.
Link to comment
Share on other sites

Please sign in to view this quote.

Checking on this for you.
Gage Pin Set
Need to know:
Class (I will assume ZZ for now)
Minus or Plus pins (I will assume Plus for now)
Inch or Metric
Link to comment
Share on other sites

  • 1 month later...

Please sign in to view this quote.

I have primarily confirmed this as a fix.
Any CMM program that failed to generate an excel file and was ran on a system that generates an excel file seems to fix the problem.
This leads me to believe this has nothing to do with Excel or the Excel templates/INI files supplied with Calypso.
It may be some internal Calypso setting/variable we are not aware of.
Link to comment
Share on other sites

The issue is not with Excel. You likely have a PCM or configuration file somewhere that is putting legacy header data into your protocol files.

Check your C:\Users\Public\Documents\Zeiss\CALYPSO\data\config first.

I would guess you are getting data into your startfile or prothead/protocol/dictionary files. Moving to a "working Excel system" is just a false-positive for your test. That PC doesn't have the condition you are experiencing. Additionally, this particular error you are seeing is not a common Excel related issue. PCM error messages are rarely related to Excel.
Link to comment
Share on other sites

This excel issue happened on a new install of Calypso on a new laptop that was not using any PCM at all.
The fix (or work around) I found came from a system using a system that was generating an excel file without the error.
Copying the CMM program to my laptop appeared to fix the excel issue.
I have done this on several systems that had the excel issue and using a CMM program that creates and excel file, once again, fixed the other systems.
Link to comment
Share on other sites

 Share

×
×
  • Create New...