Jump to content

jholbert

Members
 View Profile  See their activity

  • Posts

    14

  • Joined

  • Last visited

 Content Type 

Posts posted by jholbert

    Rev Control and file management

    in General Discussion

    Posted

    Tom

    jd here

    We do a lot of work for a company that I feel Has this under control. The work we do is in pro_e, and it may contain hundreds of parts( standard fixture components) Let me define the word standard.When one does work for this company one purchases a copy of their company's integration package.which contains a their standard lib ect. once a week we get an updated lib which we then install. If your famillar with pro-e then

    you know that if you have the latest lib then you can call up the fixture.

    And all of it's fixture components will be there.But if we alter a std. lib component or design some thing new it also must be included eather in the working dir. or in the lib. We like the way ptc puts on the .#at the end of it's

    pt# as it contains a list of it's assets. No mater who does a rework on it.they

    get a complete file with all of the custom components,if they have the latest lib then they have every thing to do the work.the lib puts every one on the same page. The lib contains every thing that they purchase, or make or alter from a purchased item.It then recieves a catalog # and is put into a sort group.(dir.) like (bushings,keys,nuts,bolts,etc) 10's of thousands of items.

    The point I'm tring to make is it really does not matter what the weldments or what ever it is you have in the way as a standard lib, the only things that are custom in my world are the thing's we put standard components into. It would be nice if I.C. would give us a way to do the same thing with our assem's. In

    the way of an auto save as .#for a give'n saved state. The way I do it now is save as xxxxxxx.ics in a dir. of it's own, then if there is another version I use the.# at the end. Then if there is a rework to this fixture I then start with a new dir. with an _a or _ b or _c etc. after it. I then copy all the related files to it and work it from there. Why we do it this way is that at any time we can revert the fixtureback to any change level we want, without much ta do about it.The company that I'm speaking of is doing this with their parts asem's. also. They keep sep. dir's. for parts also. They too are kept as a part of their lib.

     

    hope this helps you in some small way

    your friend

    jd

     

    CAM Track Design question

    in General Discussion

    Posted

    Tom

    it seems to me that using a slide might not work as is shown.

    have you given any consideration that ,as you have shown it, the cam is locked, as you move the slider there would not be any movement to the cam? The slider would just ride in the slot. how do you plan to give rotational

    force to your cam. maybe if you used a hollow thumb wheel.with an internal

    spline,over an external one on the cam. leaving you blue bar as is,solid.

     

     

     

     

    Custom Designed Machines & Machine Tools

    in Services/Educational

    Posted

    I am one of a group of Mechanical Design engineers,specializing in tool design.We have a long and distinguished history in the following fields.

    Automotive (Delco Delphi,A.O.Smith,Detroit Diesel Allison,Solvay.Suhner,National Standard) Die design,jigs,fixtures,gauging and assembly.

    Heavy Equipment (Caterpillar,Clark,Crown,Hyster,LinkBelt, Timber Jack,Minster Press,Aida,John Deer,Detriot Diesel Electromotive,Allison) asem.tack & weld,robotic finish weld,machining fixtures,inspection.

    Areonautical (Allison GasTurbine, Garrett Turbine,General Electric) Manufacture,assem,gauging of turbine blades and assemblies, spec. machines, edm /lasers etc.

     

    These are just a few of the firms we have worked for, as for the list of projects, its too large to list here.

     

    interested?

    We are!

     

    I can contacted at jd8@Verizon.com

     

    smile.gif

×
×
  • Create New...