All Activity

To make sure the command is working, you can record the creation of the element with the intended parameters used in the dialog. For most functions you can print the .__doc__ but for this it needs to be recorded since there is no list of parameters in the .doc print(gom.script.deformation.create_surface_component.__doc__)

@Richard Shomaker Thanks, I will give that a go.

Thanks for the clarification Richard!

For scanning speed/data density for our machines here, I won’t go with a step size that’s less than 0.001mm / 0.00003937”. The drive motors sometimes have trouble if I go much below that.

I am looking for a torque... even these I believe our operators will do the same thing... I think what i am going to do is fabricate on myself and see how it goes...

Sorry for pointing you in the wrong direction. You can put random stuff in for computation instead of the standard or more_points or the delete the whole line it does not produce an error. This is probably just asigning a value (text) to a keyword.

Thanks for your input Nano.

Yes, if there is an automatic qualification of the MasterProbe it will update the Reference Sphere Position.

CAD Presentation is just a screenshot, so typically I use the Dynamic Image - then set the Source to Additional data: measured value

Hello, Long time PC-DMIS user from a 9-year Calypso Hiatus. Trying to get a better understanding of how the MasterProbe works. First, I do a reference sphere position with the MasterProbe through the probing system qualification window. Next, calibrate other styli systems to that. Say I want to make a program to calibrate all stylus systems, and the sphere does not move. If I put the MasterProbe at the top in the characteristics, will this update the previous ref sphere pos. that was done? Let's just say we put the MasterProbe in the program due to the machine shutting down and having to rehome. Thanks for the help!

Unfortunately, the line error is 38. What type of computation method is selected? Also, I couldn't find any other computation methods besides the 'standard' one. I will try with this "more_points" and see if it works

I'm with Norbert. If you keep slowing it down, at some point I would think static friction comes into play. I'd love to see you run this test and see if it really happens.

When creating a custom plot protocol template, what is the protocol to show a CAD Presentation?

Hello, the kiosk is as functional as you can make it with python 🙂 It is possible to modify the start dialog and expand the functionality to your needs. As a start, there is a trend creation mode for kiosk, which will add a measured project to a project of the same type and will create a trend project in the background. Measuring in one software instance and evaluating in another is possible with the asynchronous evaluation. For the report, the flipbook option for report pages may be used. From KioskInterface_settings.cfg: [Background Trend Creation] # If enabled an additional software instance is started which creates # trend projects for all projects found within SavePath. # Default: False BackgroundTrend = False # Defines the maximum number of stages for the trend projects. # Default: 10 TrendMaxStageSize = 2 # If enabled show the trend instance fullscreen on a second monitor # Default: False ShowOnSecondMonitor = True

This was when I had to trouble shoot a similar error.

Thanks, much appreciated sometimes overthinking and being rushed. The little things you have known and done for so long gets overlooked with stress to push product out of the lab. The responses i got from this, thank you.

Strange Seems like it should work in theory and has worked for other people. Does the error message state which line of code was carried out, when crashing? Not sure if this info has any relevance, but anyway: When i run your script with "more_points" i seem to get to the line "gom.script.sys.close_project()", because i get no error and my project is closed.

Yes, we have tried that, but unfortunately, it does not work; the script crashes with an unknown error.

Interesting consideration indeed. I would assume that zeiss has some guidelines for their sensors where you might find clues. Otherwise why not take an adjustment ring or something else you know the form and size of and let a program run over night with increasing speeds. If there are relevant factors at super slow speeds you should be able to detect that and you might find the "balance point" if existing.

Hello Tarek, i have not scripted for zeiss inspect so far and i have not checked the whole code. But just having a quick look i found the following: As this seems to be the only occurance of the word "standard" (full text search) it is highly likely that changing this to the desired setting will solve your problem.

One thought that immediately comes to my mind is static friction. By default Calypso filters out the first few points of each scan, and one reason is static friction. If you scan REALLY slowly, you might come to a point where static friction comes into play again and the probe might move more or less in tiny jumps instead of a continuous smooth movement, thus impairing the results.

Let's suppose for a moment that your measuring task requires scanning very small, intricate surfaces in high density. Assume that cycle time is not a priority. You're emphasizing slow, accurate scans. You may even scan the singular workpiece overnight. How slow can a Vast XXT fixed mount probe, such as those on an O-Inspect, scan? Granted that stylus length and weight as well as probe size are considerations. Assume that the probe shaft including extensions is less than 40mm, oriented z-, and the probes are small: 0.3mm to 2.0mm. Is there an optimal range for balancing surface scan stability and point capture? Are any undesirable mechanical forces introduced at very low speeds? Industry usually focuses on cycle time optimization and fast scanning, but where are the limits of capability on the other end of the speed spectrum? I'd love to hear your thoughts on this. ✌️ Jeff Frodermann

I think I did see PCM when I was going over the error report. Can you remember at all what the setup error was?

I haven't been good at all keeping up with that stuff, so I'll do that. Thanks for the reply!

If it's about scanning around sharp edges, than insert a corner point with 45° vector, or ask for model, where will be small radius. And if you need to have as many points close to that corner, then make new segment for that area and scan it with much slower speed. In that case don't forget to select all segments and change them into one group so you can have continuous scan.