Jump to content

Special Program


---
 Share

Recommended Posts

Has anyone used the "Special Program" characteristic before? Do you need a specific license to use it? It's greyed out on my end but reading about it, it looks really useful.
Link to comment
Share on other sites

[...previous wild guess deleted...]

I found something deep down in my mingle-mangle of various Calypso stuff. I had forgotten that I have it and don't remember where it came from (probably the old forum). It's a detailed description of how to use that characteristic together with a VB example.
Unfortunately the forum currently doesn't allow me to upload any attachments.

Maybe you can find it in the old forum. The file name is "testPrg.zip"
Link to comment
Share on other sites

Hum, I got curious. To me it seems like all you can use if for is exporting points from features in a chosen coordinate-system in xls-format. You can then use that for what ever, and read it back in.

Feels like this is a relic from the past that now is replaced by the options in Features/Additional Features. But that's just a guess.
[img]https://i.imgur.com/goOsH1u.png[/img]
Link to comment
Share on other sites

Hello
this function was designed as a standard user-interface to start external calulations directly by CALYPSO menue.
Some applications are the property of the respective company and therefore not part of a standard Software.

Main functions
- send results back to CALYPSO
- creation of special files for detailed analysis
- jump over limits inside CALYPSO
- special graphic tools

I've put a handout of an example into the attachment.

Hope it helps
Klaus

FFT_Manual_V1.docx

Link to comment
Share on other sites

Ah ok. I completely misunderstood what that was. I actually thought it was a way to call another measurement plan and run it within your current measurement plan and make one single report.
Link to comment
Share on other sites

Klaus Dieter introduced us to this tool some years ago, is very useful; However at the end we decided to use a combination of: addToFile, points in file (curves), systemCallWithWait & readPCMFile; due to is easier to distribute (not necessary to document installation instructions because the *.exe goes in the same inspection directory).

in case of performance, some evaluations out of calypso are much faster, thousands of points with nested loops take several minutes with calypso Features, but less than one second with visual basic.

// scanning
getActual("STA1_MX2").x
							
//delete previous parameters and results
deleteFile( getActualInspectionDir() +"\TFparam.txt")
deleteFile( getActualInspectionDir() +"\TFOP.txt")

// Input parameters
Textvar = Textvar +"Name01 =curvepoints.txt" + cr()   // Name of the text file (Actuals)

//  .... other parameters

// Generate file of paramters
addToFile(getActualInspectionDir() +"\TFparam.txt", Textvar)     

// Execute the application   	  		
systemCallWithWaitgetActualInspectionDir() +"\VBapplication.exe")	
	
// Load results into Calypso
readPCMFilegetActualInspectionDir() +"\TFOP.txt")					

Link to comment
Share on other sites

 Share

×
×
  • Create New...