hexagon logo
Register Sign in
  • Replies 6 replies
  • Subscribers 221 subscribers
  • Views 66 views
  • Users 0 members are here
Options
Related

Dual Arm Bravo and scanning issue...

FOG_Carter
Hello,

We have a dual arm Bravo with laser scan heads and we run PC-DMIS 2021.1 in imperial mode, not metric. The scanners work quite well from what we can tell with one major issue. When we take a subset (cleaned up to remove spill over and such, in PC-DMIS) of the point cloud we can't use it in any evaluation, more precisely, the subset of data doesn't even show up in the list of available features to analyze although the full set does.

The Hexagon rep seemed shocked when he saw it but have heard nothing since and that's been months ago, perhaps a year ago. Has anyone else run into this issue? Not sure if this is a imperial vs metric mode issue...I say that as we had another scanner issue in 2018R1 where we couldn't marry up the data between arms and it turned out that it worked in metric mode but not imperial mode.

This Bravo has been a bag of problems since we got it. Hexagon got most of the issues resolved, thank you Tim O! But there are a couple large issues that have not, scanning is one of them. Going on three years now.

Regards,
The FOG
  • Hey FOG,

    You don't mention what kind of evaluation you are looking for, but It sounds like you are trying to evaluate points separated from the main cloud... points without nominals. You'll need to compare the points to CAD by doing a point colormap, or construct a feature, etc. so that the points have nominals... Once you have a this, you'll see that the data or feature, is available for evaluation.

    If this is not what you are seeing let me know and I'll try and help if I can.
  • Hi portable,

    Thank you for the reply! The evaluation is a surface profile. Of course, we have CAD in the program. The 'subset' of points are those points that lie on the surface in question. The entire cloud of points is those points that lie on the surface and those points that spill over the edges of that surface. I'll admit that we've had no training on scanning but we did have two Hexagon reps there while testing and they seemed bewildered by the behavior, the unfortunate thing is that no one from Hexagon has gotten back to us about this. Also, the person in charge of heading up this project where I work retired just after this testing. No one else was assigned the task to follow up, etc. So me, being the team lead, has started to making queries and trying to revitalize the project, I mean. we have spent quite a bit of money on licenses, scanners, etc.
    We are hoping to use scanning to get greater throughput on the CMM as we are currently near 100% capacity with more load coming for it very soon. We think we can get a 40-60% reduction in time on part inspection in the CMM using scanning.

    Regards,
    The FOG
  • You will need to use legacy dimensioning to report profile of a surface. The Geometric Tolerance command does not support pointcloud data directly, only features that have been extracted from the COP/mesh (laser auto-features or constructed extracted features). PC-DMIS 2023.1 will introduce a brand new "constructed extracted surface" command which will allow you to segregate pointcloud data belonging to a particular surface / surfaces. The 2023.1 tech preview is currently underway if you'd like to try it, just click this link( https://go.hexagonmi.com/l/49752/2015-04-09/zkk3) from the top of the main forum page to sign up.
  • Hey Again Fog,

    Note that inside of the pointcloud colormap command you can select individual surfaces to colormap. This means you don't have to segment the cloud do inspect the profile.

    If you haven't had any training I would reach out to your local Hexagon office and get into the 201 class for scanning on CMM. It'll make your journey a LOT easier.

    Best.
    Doug.
  • in reply to Neil Challinor
    Neil,

    Thank you! That explains a lot! Unfortunately we are only now getting 2021.1 accredited and 2023.1 will be a very long way off.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement