//rad1=(getProbe("1",line[I]).diameter*25.4)
//rad2=(getProbe("2",line[I]).diameter*25.4)
//rad3=(getProbe("3",line[I]).diameter*25.4)
//rad4=(getProbe("4",line[I]).diameter*25.4)
//rad5=(getProbe("5",line[I]).diameter*25.4)

//std1=(getProbe("1",line[I]).stdProbeDev)
//std2=(getProbe("2",line[I]).stdProbeDev)
//std3=(getProbe("3",line[I]).stdProbeDev)
//std4=(getProbe("4",line[I]).stdProbeDev)
//std5=(getProbe("5",line[I]).stdProbeDev)

//px1=(getProbe("1",line[I]).probeVector.x)
//px2=(getProbe("2",line[I]).probeVector.x)
//px3=(getProbe("3",line[I]).probeVector.x)
//px4=(getProbe("4",line[I]).probeVector.x)
//px5=(getProbe("5",line[I]).probeVector.x)

//py1=(getProbe("1",line[I]).probeVector.y)
//py2=(getProbe("2",line[I]).probeVector.y)
//py3=(getProbe("3",line[I]).probeVector.y)
//py4=(getProbe("4",line[I]).probeVector.y)
//py5=(getProbe("5",line[I]).probeVector.y)

Problem is if the probe does not have the tip given, it will error.  I am trying to find PCM code to ONLY use the tips in a given probe cofiguration.  All I have found so far to do this is with the Active probe, but I am doing all this before the probes are active. 

The way I am doing it right now is to have a running list of each probe and tips, and only evaluate certain ones... trying to get this simplified so that with new programmers in training, it will be less to update and make errors when a new configuration is made.

Any and all help is greatly appreciated. 

Hi All,

How do you pull the sub-values from a true position characteristic with PCM?

I have a true position of a Ø (-H-) to a datum scheme (-A-B-C-), and it reports the calculated value. I need to report the correction values for pulling the true position in spec. 

I know that you can enable an additional printout to get these values, but I would prefer to pull this into a standalone characteristic (Result element) using PCM.

When I attempt to cheat the software with "getActual("-H- Position1").y" I receive the following error. 

Any help is appreciated!

Is this due to an issue on my end? My other variables and formulas work perfectly.
Could this be related to the version of Calypso?

Has anyone else experienced this issue?

*"variable" will be a set parameter inside of a parameter file.

Actualx = getActual("circle").x

Actualy = getActual("circle").y

Actualz = getActual("circle").z

if "variable" == 1 then

positionCMM(Actualx, Actualy, Actualz)

endif

As soon as the program is done running the probe will just go straight up. Not sure what I'm doing wrong. Any help would be appreciated, thanks!

• whether a characteristic table file was generated and exported (i.e. if the table file option was activated in the start window AND if the custom path setting was set and activated)
• where (custom path and file name) it was exported to.

I think this would need a few "undocumented" commands. Does anyone happen to know some? 🙂

Has anyone can help me with this issue? I tried different method but it is not working, I always get the graphic when the program ends.

Thanks in advance!!!

I am bypassing Calypso's normal input screen "Input Parameter" for header data to control what gets entered.

I am using vb.net in an interface where the Serial number, Mach center, operator and WOID will be collected for strict control of what is entered.

Current para file variables to write to PiWeb.

OpSerNo="SC-999"
OpMachCtr=K999
OpOper=M999
OpWOID=45009999

Using OpSerNo for this exercise (Solve one should solve all) with PCM.

u_SerNumb=OpSerNo (works and resolves to "SC-999")

But this resolves to nothing

OpSerNumb=getRecordHead("u_SerNumb")

Once that is solved, how do I pass the OpSerNumb to Piweb's "Incremental Counter"? (I use the Incremental Counter as a Counter and or Serial Number)

(Interface shown in the image)

Is there any property of getProbe or any other way to check probe's qualification status?

It is green when qualified (qual. date and time are updated and all other data)

It is red when is was NOT qualified (qual. date and time stay from the previous qualification and all other data)

I have been told I need to use PCM for this. I have tried creating my PCM program two different ways: first is by placing the code in a .txt file and then placing it in the root of the measurement plan program. I have also tried placing the code in the pre-settings with a global scope. 

I have tried every possible variation of code. Below are some I have tried. I always get an error like u_Work_Order is not defined or Temp_Variable is not defined. 

u_wo_number = ""
repeat
  u_wo_number = inquireText("Please enter 10-digit WO Number")
  if len(u_wo_number) != 10 then
    message("Error: Must be 10 characters. You entered: ", len(u_wo_number))
  endif
until len(u_wo_number) == 10

u_wo_number = ""
while len(u_wo_number) != 10 do
  u_wo_number = inquire( "Please enter 10-digit WO Number" )
  if len(u_wo_number) != 10 then
    display( "Error: Must be 10 characters. You entered: ", len(u_wo_number) )
  endif
endwhile

u_wo_number = ""
while len(u_wo_number) != 10 do
  u_wo_number = inquireText("Please enter the 10-digit WO Number:")
  
  if len(u_wo_number) != 10 then
    message("Error: The WO number must be exactly 10 characters. You entered ", len(u_wo_number))
  endif
endwhile

message("WO ", U_wo_number, " accepted. Starting measurement.")

The CNC is disabled and the PIWeb report will not print. Where do I access PostSettings in Calypso2025 so I can change this file path? There is no X Drive mapped to this PC.

Calypso 2025

I do a lot of offline programming and use notepad++ for ease of use and formatting

unfortunately, when doing the same with Calypso, I lose the colour coding

with other platforms, like Renishaw's Modus or similar, I found an .xml file that i could import into Notepad++ as user defined language 

I had built up one myself years ago that was very close, but my pc died and i lost all my settings

I am sure one of you geniuses here has something that can share,

please and thank you 🙂

Is there a PCM command in witch I can get the status of an element or feature?

I search for a query for a feature/element not can be calculated. (magenta one)

Is there a way to check ? (maybe true or false)

Best greetings

Sven

I'm looking to see if anyone has a PCM command list they could share.

I appreciate the help!

Thanks,

JG

The great Eric Moberg wrote this snippet of code for me, and I have used it for years with no issues. Recently I have one measurement plan that it just doesn't work on. I get the following error. 

The code is loaded in, and ran via runPCMFile(preSettings), so this code lives inside of a txt file that is read by every measurement plan. 

Like I said, no other measurement plan is having issue with this, but apparently this measurement plan is. I just don't know what would cause it. 

Any thoughts?

This is what it contains:

With this code:

offtsetCoordinates = readListFile(offsetFile)
ballFinderOffsetX = (val(getParameterNamed(offtsetCoordinates,1))/1000)
ballFinderOffsetY = (val(getParameterNamed(offtsetCoordinates,2))/1000)
ballFinderOffsetZ = (val(getParameterNamed(offtsetCoordinates,3))/1000)
coordsys = getParameterNamed(offtsetCoordinates,4)

I get the two "0" values correctly because i guess they are integers and the rest is just "".

I could make the file comma seperated and then use 

offSetStuff=offsetFile.asFilename.contentsOfEntireFile
xOffset = val(strElement(1,",",offSetStuff)))
yOffset = val(strElement(2,",",offSetStuff)))
zOffset = val(strElement(3,",",offSetStuff)))
coordSys = val(strElement(4,",",offSetStuff)))

But i dont want that tbh. 

Is there a way to use getParamteterNamed() for that?

From the post settings of a characteristic I can get the substring I want with the following command:

strElement(1," ",getActual().identifier)

But of course this doesn't work anywhere else as getActual().identifier then no longer returns a valid name.

In the end my code needs to run from an external PCM file, so I need a different way to get that characteristic name. Any ideas?

i have a file that contains point coordinates (file is attached)

• i read the list
  • A = readListFile(MS_Curve_Points_Temp)                // read NX output

• then i use subStr to seperate teh lines into individual string that i can easily phrase
  • D1 = subStr(A,1,1)

this was working up until we upgraded, now i am getting an error

can someone please tell what has happened and what can i do to address this issue

i tried to convert "A" to text, but it didn't help

Greeley appreciate all the help 🙂

13382673_10_fof_zeiss_20_ms_x_Temp.para

Is this possible?