hexagon logo

How long does it take you to program?

Let’s say someone gives you a metal part with 150 dimensions. How long would it take you to study the print, figure out fixturing, create a setup sheet, and program it? You’ve never seen this part before and it’s somewhat complex. Assume the print makes complete sense to you after studying the print—so you don’t need to ask the designer any questions.

Also, would the program run perfectly the first time? If not, how long would “proving out” the program (making adjustments) take you?

I ask these questions because I get them a lot being the only programmer at a significantly large company with 3 machines. I’m curious what other people’s experiences are, and I’m open to any tips. I will state my answers to these questions in one week. Hopefully I get a lot of responses.

Parents
  • hi,

    Example 1:
    for a rotor shaft of a wind turbine (About 3m long). Simple A-B pattern, including drilling pattern, grooves and other details, around 75 positions I need about 2 hours depending on whether a 3D model is available or not. Runs smoothly the first time

    Example 2:
    High pressure pump housing with approx. 300 positions, 3D model available, 7 drawings, datums from A to G, a cube with approx. 500mm x 500mm. including test run on the machine About 8-12 hours, based on how often the boss looks over your shoulder.

    Example 3:
    Prototype drill bit for an oil drill, 1.2m long, approx. 200 positions, complicated freeform contour, 12 different sized pockets in a variety of angles, 3D model available, about 6-8 hours including test run.

    ---------------
    I have very good experience with collision detection. I almost never have any problems during the test run.

    I don't use the clearance cube, just clearance plane

    I use prepared standard programs for all axes so I just have to see which direction I want to start from

    We have prepared enough Probes, I don't have to build any new ones in the examples

    We have enough standard prisms and fixtures, including the 3D models for them, which saves a lot of time when collision detection knows where the fixture is

    ---------------

    Unfortunately, it happens all too often that a drawing is not clear or the required geometric tolerances simply do not make sense.

    Asking the customer or making the associated changes that need to be implemented take a lot of additional time

  • Sounds like you’re a pretty fast programmer! Legacy or GeoTol? Hmmm maybe I should give clearance planes a shot again. I use move points. Not a fan of clearance cubes at all. Do clearance planes give less false collisions (compared to clearance cubes) when running collision detection?

  • Very few people can really concentrate on the same thing for hours, when I say 8 hours that's usually 2 shifts for one person.

    So actually not really faster than Ocean Zhu example. As I said, we have enough standard fixtures, programs and probes.

    All the header data is copied from a database into the measurement program. I can start with the first details in minutes, which saves a lot of time

    I use 99.9% GeoTol



    clearance planes work great. Of course, there are a few things you have to take into account, but I personally find it very reliable

    I can hardly remember whether I ever received a false collision,

    Except for one thing: star probs always give false collisions when you change the tip without clearence move near a wall,

    You learn this exception pretty quickly, so it doesn't matter

  • Very few people can really concentrate on the same thing for hours, when I say 8 hours that's usually 2 shifts for one person.

    So true.  I know I can't run on all cylinders all day every day.  And, it seems like there are always interruptions.  

Reply Children
No Data