hexagon logo

Pc-dims vs calypso

I have only worked with PC-DIMS for the last 6 years, but I'm currently considering a new position that is Calypso. How difficult is Calypso to learn?
  • I really like PC DMIS I just wish it wouldn't "think" for me and try to change an entire program after updating one thing...In that regard TutoRun was my favorite.
  • I really like PC DMIS I just wish it wouldn't "think" for me and try to change an entire program after updating one thing...In that regard TutoRun was my favorite.


    On the other hand having it "think"' has kept me from doing something stupid before my coffee kicks in. It's like the old saying, " The chief cause of problems is solutions."
  • I tihnk the most frustrating thing about calypso is the "Strategies".
    Autocircle as an example:
    --PCDMIS: Click autocircle feature. click the CAD. Set your numhits in one tab, start/end angles of points and voila you've got your circle ready to execute. you can edit your theos, numhits, start/end angles any time by changing lines in the edit window.

    --Calypso: Click icon at bottom to set it to autogenerate a new feature, click the CAD. Circle feature generated, with 'default strategy' for that feature. Now you have to double-click on the feature then dig another couple clicks within that feature properties window to get to edit strategy. from there you can change your number of hits, spacing etc... but if you change the strategy option from say an autocircle to a manually defined circle of hits, or scan, or segment... you start from scratch on the numhits and start/end angles.

    Say you want to override nominals?
    --PCDMIS: within edit window: key-in the nominal you want add a +0 to it to lock it in place.
    --Calypso: Double click on feature, to enter feature properties, then go into a formula tool similar looking to the assign function in pcdmis, and define a static value for the new nominal. ONE fricking nominal value at a time, and you have to do it one-by-one for each nominal value you want to ovverride/fix.

    Also, some of calypso's methods for creating generic features, theo intersects, and other things we simply take for granted in PCDMIS, is absurdly over-complicated.
  • I tihnk the most frustrating thing about calypso is the "Strategies".
    Autocircle as an example:
    --PCDMIS: Click autocircle feature. click the CAD. Set your numhits in one tab, start/end angles of points and voila you've got your circle ready to execute. you can edit your theos, numhits, start/end angles any time by changing lines in the edit window.

    --Calypso: Click icon at bottom to set it to autogenerate a new feature, click the CAD. Circle feature generated, with 'default strategy' for that feature. Now you have to double-click on the feature then dig another couple clicks within that feature properties window to get to edit strategy. from there you can change your number of hits, spacing etc... but if you change the strategy option from say an autocircle to a manually defined circle of hits, or scan, or segment... you start from scratch on the numhits and start/end angles.

    Say you want to override nominals?
    --PCDMIS: within edit window: key-in the nominal you want add a +0 to it to lock it in place.
    --Calypso: Double click on feature, to enter feature properties, then go into a formula tool similar looking to the assign function in pcdmis, and define a static value for the new nominal. ONE fricking nominal value at a time, and you have to do it one-by-one for each nominal value you want to ovverride/fix.

    Also, some of calypso's methods for creating generic features, theo intersects, and other things we simply take for granted in PCDMIS, is absurdly over-complicated.


    I don't know a lot about Calypso, but it seems to be "only" a graphical evolution of U-Mess... so really complcated Slight smile...
    I have to treat sometimes values from it, i noticed that :
    • scanning seems to use something like "snap point" of PCD : if you scan a circle at theo z = 0, all measured values on z =0 (with 10 decimal places, it's really strange !)
    • coordinates of feature are not given at the centroid, but at a projection on axes (like "coordinates at the origin " for a line in 2D) : sometimes very surprising
    Maybe those little defects can be fixed by a parameter, but here, nobody can tell me which one it is...


  • I don't know a lot about Calypso, but it seems to be "only" a graphical evolution of U-Mess... so really complcated Slight smile...
    I have to treat sometimes values from it, i noticed that :
    • scanning seems to use something like "snap point" of PCD : if you scan a circle at theo z = 0, all measured values on z =0 (with 10 decimal places, it's really strange !)
    • coordinates of feature are not given at the centroid, but at a projection on axes (like "coordinates at the origin " for a line in 2D) : sometimes very surprising
    Maybe those little defects can be fixed by a parameter, but here, nobody can tell me which one it is...


    When I am using Calypso and it gives me that problem, I do this:

    1) Uninstall Calypso
    2) Install PC DMIS
    3) Write the program in PC DMIS

    The issue goes away ! Sunglasses


  • When I am using Calypso and it gives me that problem, I do this:

    1) Uninstall Calypso
    2) Install PC DMIS
    3) Write the program in PC DMIS

    The issue goes away ! Sunglasses


    Is that what Collapse-O recommends???


  • Is that what Collapse-O recommends???


    It's buried in the help file somewhere. Has to be.


  • It's buried in the help file somewhere. Has to be.


    Or is it an undocumented enhancement???


  • Or is it an undocumented enhancement???


    You know how Facebook has Offline Activity that they track you on unless you turn it off? Wouldn't it be funny if a certain CMM software wasn't working correctly and a little pop up came up and suggested you install PC-DMIS? Sunglasses