All Activity

i dont have the standard but in AUKOM GDT AND AUKOM Level 2 datums are allways tangencial this is according the standard ISO 5459 that sould be as well activacted in calypso. i can provide some AUKOM slides and and you should consult this article!! This is a great article i recomend everyone read it https://www.xyzarchitect.com/blog/building-coordinate-systems-3d-measurements.html

Hello together, i have recently many questions about MMC and form tolerances. As example: For me it is understandable, what the meaning behind it is, but i am not sure how i can put it into calypso. do i need to use the surfaceform or different elements?. I use Calypso 2021 version 7.2.20 and cant use the surfaceform for it, or i just dont know how to describe the elements... We have some drawing designer that tolerate it like this and i am at the status that i cant insert it in our calypso and it is not possible. Please correct me if i am wrong Kind regards and forwardly thank you for your Help!!

Hello , I move cad model in free cad. Nice day

If there is no G, and no other requirements, what is the default?

Hello, which function did you use to move the part? Is this in a Scanbox with a measuring setup? When you are using a single element transformation make sure to also select the elements and keep in mind that some elements will lose their creation sequence with this function. Operations ► Elements ► Adapt Element To CAD... can help with som elements. Nanno

Thanks - saviour - that works

Well, you could modify your PCM code in a way that it does different things depending on a pallet-related variable. For example you could use the variables palletlocationnumber, firstpalletlocationnumber and lastpalletlocationnumber to call a data entry subroutine during the first run, write the parameters entered into separate parameter files and read them back in in the second and subsequent runs. It could roughly look like this: // Data Entry if getRecordHead("palletlocationnumber")==getRecordHead("firstpalletlocationnumber") then // input for part 1 var_1 = inquire(....) addToFile("PCM_1.txt", "P001 = "+var_1 ... ... // input for part 2 var_2 = inquire(....) addToFile("PCM_2.txt", "P001 = "+var_2 ... ... endif // Data Processing if getRecordHead("palletlocationnumber")==1 then runPCMFile("PCM_1.txt") endif if getRecordHead("palletlocationnumber")==2 then runPCMFile("PCM_2.txt") endif ... ... Note that the above scheme only works if the same parts are always on the same pallet positions, otherwise you'll need to develop a more sophisticated approach.

Hi, I got this answer: part = gom.app.project.parts['Part'] is_preliminary = part.part_contains_preliminary_data And for project-wide information: is_preliminary = gom.app.project.project_contains_preliminary_data

But it might become a top seller if it was true

Hi , I solved the same problem some time ago. Move to new 3d data to same global coordinates as original if permissible under the updated data or edit existing elements to new 3d data. Please advise if there is a more efficient alternative available. Many thanks Nice day.

What do you want to use it for? For example, I use the temperature sensor for compensation—though we don't actually need that, as it's irrelevant for our components—to include the current temperature in the report.

@Imrich Csonka I ended up adjusting it by hand, but I will give you suggestion a shot next time to see if it does the trick. I did switch the adapter but same issue. Thanks for the suggestion!

It's the GS1-200.

@Richard Shomaker It's on the GS1-200. I changed the mounting bracket, but I still get the same Issue. I reached out to the guys in NC and it seems to be a known problem. I ended up adjusting it by hand whiles it's still on the ScanPort. Thanks for the feedback!

You should be able to use getTemperatureCorrection().temperatureX (or Y or Z) for that. Doesn't appear to need a PCM license.

Hi, I was wondering if there is a way to pull the temperature value from "Scale" using a formula. I don't have PCM. Thanks, Wojciech

I will check into that, Thanks Martin.

You bring up a good point. At the moment, they do not.

Hello all, I have some programs set up that I am currently trying to palletize. The parts are fixtures that need to be checked on a quarterly basis per our quality policy. Some of these programs have mini plans in them that either change how tight the tolerances are on some features or changes what features are checked depending on the situation. I currently have a pcm function set up so it will ask the operator which check needs to be run and then it sets the mini plan to that. Is there a way to perform all of the PCM inquiry at the beginning of an auto run rather then it finishing one program then waiting for a user input? Thanks

I'll be attending Monday and Tuesday.

Many settings is stored in calibration - so i would say - calibrate it in this settings and it will default it in strategy. At least this is working for measuring force.

You can try to compute if there is a mesh in the program: import gom mesh_in_program = False try: print(gom.app.project.parts['Part'].actual.computation_status) mesh_in_program = True mesh_points = gom.app.project.parts['Part'].actual.num_points print(f'Mesh found in program: {mesh_points} points') except: print('No mesh in program') To get the details of the polygonization quality, you would need to record that to a json file or txt file for use later.

I have an angle probe that we made up here, but I want to keep the following: Measurement Plan Editor Features > Probing Behavior of Passive Sensors > Sensitive Measurement Plan Editor Features > Probing Dynamic (in %) > 25%

Here is the template I use for a Contura G2 with VAST XXT RDS `PROGRAM TEMPLATE.zip

Measure both as a Plane-Point. Create a Secondary Alignment that is rotated to be parallel to the distance Create either a Caliper or Simple Distance Change the active alignment from the Base Alignment to your rotated Secondary Alignment Measure the distance in whatever axis you are looking for (I'm assuming X). Just keep in mind that since you don't have a true measured feature to set the direction, you are relying on the actual angle being close to the nominal angle. The better measurement would either be a Plane to Plane measurement or a Plane to Point measurement. Even if you could do something like measuring a Plane on both surfaces, construct a Symmetry, and using that as your setting direction then you can use thing like Cartesian if wanted.