All Activity

Hi Dina, I hope it's not to late to reach out to you. Please send your resume to me on my email cvillanueva@volantproducts.ca

Thank you so much Richard! This is exactly what I was looking for!

I may not know exactly what is possible without FF, but i know you can use 2D and 3D curves to evaluate line profile. With FF you can create surface feature and do scan paths on selected faces of a model. Also you can recall all measured points into this feature and select which faces should be evaluated. In other words - curves has nominals inside them - FF is using model for calculations. We were told ( forged parts ) we absolutelly need curves and ff.

We're going to be investing in some Curve licenses and got offered a Curve/FF bundle option. What's the difference between Curve and FreeForm? For some context, we have one Curve license now that we've been utilizing more in recent months. We're also considering a CMM outfitted with a LineScan for surface profile inspections.

@BlueSky Well i still don't know what is going on. here are some thoughts 1) it is possible that the algorithm for drawing that graphic is just not very good. Maybe they didn't give it as much attention as we like to think they did when the wrote it. 2) Does the nominal on the feature match the nominal on the dimension? 3) I checked a few reports and had the graphic look exactly like I would expect it to look, so thought 1 seems less likely. 4) Is there something in the tolerance setting or fit algorithm that is a little odd? 5) I don't think I have any good ideas as to why this is happening and would like to know when you find the answer.

Wonder if its anything like what they do with automobiles. if you notice they will change between crazy colors and back to black,white, gray, etc.

If I'm understanding correctly, you are wanting to scan the curve, and then based on where the intersection point is calculated you want to limit the results from the start of the curve to the intersection point. I do not know of an easy way to do this without PCM, and even with PCM you might have to get creative on determining how the actual intersection point correlates to the corresponding nominal point of the curve. But once you have that "Point Number" you can place formulas on the Recall Feature Points, New Point Range - Point Range from 1 to "insert formula here". The tricky part is going to be then dynamically adjusting Limit evaluation because if you do not skip the calculation of unmeasured points, you will get incorrect results.

I have problems with understanding your problem. You can also recall measured points of a curve into another with using box selection. To keep correct origin where to start or stop you have to have one curve with features alignment where origin is your intersection point. Then recall measured points from this curve and use box - select features alignment for numbers and this box will change position according to this intersection point.

trying to evaluate the curve from the point back into the radius not the actual point. I know where the point is by intersecting but they want the evaluation up to this point every time...

I think you have to modify everything.

Looking into saving ink, can we set default colors for PiWeb reports. I would like everything to be black and white except for any OOT conditions, those I want to be RED.

Why you don't want to use pallet system? There is another way, but it's the similar way as pallet program. Only if you have some sort of similar position of that part in machine workspace, then you would need to sacrifice start system to obtain part location via simple points with big approach distance

MyVoice to the rescue! 🤣

@Benjamin Bellville It's an OD @Kevin Harold Just to make sure I'm understanding you correctly, features with ± tolerance have the center as zero and the bar progresses in the direction of the used tolerance (left for negative, right for positive usually). As you can see in the screenshot I provided earlier it is a ± feature. 1.320 should be my center in that graphic bar, correct? The measured value all the way on the left measured 1.3176 (less than what center is), so shouldn't it have gone to the left? Please let me know if I misunderstood anything. I appreciate any and all feedback. Thank you all!

Frankly, I wonder where the good old color preferences of the 90s and 00s have vanished to. Back then you could set up your Windows GUI in the weirdest colors if you wanted to, and many applications allowed the same. Making a dark mode yourself was as easy as moving a bunch of color sliders around. But then somebody (the Illuminati?) decided that every OS and every application on this planet should have no more than two color designs - bright and dark. What gives?

Hello together, i am currently have a problem with a setup and maybe some of you have a good Answer for it: The Problem: i have 2 shopfloor machines to set up only one program means that i use one program for the different machines with different positions for the adapterplate of the part on each machine. on machine 1 i measured in the basesystem of the part and referenced it to the adapter plate (machine 1) as a Startsystem and calculated the deviation and saved the program. For machine 1 i set up a autorun data and defined the startparameter on the startsystem of the adapter plate. In this situation it works without any problems. I need to put it on the other machine 2, this machine also have an adapter plate (machine 2), i did the same procedure like i did on the machine 1 and the part moved on machine 1 after i did the changes on machine 2. It means 1 program 2 machines 2 adapter plate with each on startsystem for the part 2 Autorun overlays I know that i can solve this problem if i do a palet system and use the startsystem for the palet(one for machine 1 and one for the machine 2) and the basesystem of the part in the autorun. Is there a different possibility to do this? if you have any questions please ask me and thank you all in advance

I found it—it was a bit hidden. Extras - Environment - Font - View I generally love dark mode everywhere... but here in Calypso, I don't think it looks very good; it’s not a "soft" black, but rather pitch black, and the contrast isn't well executed. Still, I suppose it’s better than nothing.

If i faced a similar case ( obtain a point where is transition from a line into a radius ), the i did bestfitting a curve: rotation in Y axis and translation in X and Z axis - this can vary in your case, but in a same way - 2 axis for translation and 3rd axis as rotation ( remaining one ). Then i made a theoretical point in place where this point should be in nominal and used feature's alignment from this bestfit. Then you can measure this point ( it will move with bestfit ) or you can recall this point into new alignment ( or base alignment ) and report it's origin.

Considering how the release of 2025 went, it's entirely possible that they added the feature, but forgot the switch 😉 Can't test it out for now, still waiting for the license update thru the portal. It was "in progress" and it switched back to "Update available".

There was one there, just hidden by the limited window size. Thank you though! Much appreciated

Thank you, Nicholas, this was it. I had a feeling it was something silly I was overlooking.

So we skipped 2026, and just went to 2027? 🤣

Where can I actually enable dark mode in 2027? I can't find the option for it anywhere.

I have been asked if it was possible to scan a curve, from a plane into a radius (the plane intersects the radius) then evaluate the profile of the radius from the intersect point. The idea is that the intersect point can float with the orientation of the radius. I have had very, very little success with recalling curves and this is the only way I can think of doing it.