All Activity

@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.

@Richard Stanich Absolutely. The roller contacts sit in the grooves and are held in place lightly with the toeclamps. Then, I can either tip the block on it's side to balance systems like a cross, star, 2_4 or 3_5 setup or when I have angled setups like Tom showed in his original post I'd use a sine vise and some gauge blocks to set my desired angle and sweep the stylus (or in rare cases the extension) with an indicator. If I have a compound angle I use a combination of a sine vise and a sine plate.

Hi @Keith Forche, how do you ensure the printout is perfectly straight?, like making sure 90 degrees lines up exactly with the y-axis

I am looking for that too. I saw some info inside mesh, but it's enviroment dependant - in other words it's translated. There was info about used memory and stuff

Addendum: Is there a way to query the post-processing of an actual mesh with which its polygonization has been carried out? So adaptive, low resolution, less detail, standard, more detail, none?

Is there a function or a variable in the scripting that can be used to determine whether the currently open project contains a so-called preliminary actual mesh? Thank you in advance for any help!

Hello, I need your help, please. I had to modify my fixture so that I could scan the lower area of my part. Now when I change the 3D of the fixture and move the part to the new position, the alignments (I'm using local best fit) and the features (like points surfaces) don't move with the part.

Is there a function or a variable in the scripting to query whether the currently open project is completely calculated? Or do you have to make do with it, e.g. to go through all the actual elements and check them to see if they are calculated or not? Thank you in advance for any help!

Hi Roy , try moving the first starting position of the calibration plate up by about 1 cm so that there’s still space to move at position 12, then it should work. A similar problem occurred for us when calibrating the GOM Scan 1, of course make sure to check if you have the correct adapter installed (different one for the Atos Q and a different one for the GOM Scan 1).

😎 The same problem on the other side of the Moon. 🤣

You could move the plate ... Which sensor and MV are we talking about?

Hi, I attached a clearer drawing. To get my 2D line, I created an other point(Ubis) close to pointU, and by point recall of U and Ubis i created my 2D line. I'm looking to measure the distance between U and U1 according to the drawing. The dimensions of the part are approx. 2/3 cm on each axis and the thickness 2mm. I hope that's clearer now