Close-to-process compensation of geometric deviations on implants based on optical measurement data

Sorry you have no rights to view this entry!

5 Comments

  1. Dear Mr. Kaiser,

    thank you for your very interesting presentation dealing with the development of a manufacturing cell endowed with an optical measuring system for the manufacture of medical implants.

    If this approach is applied to the manufacture of other kinds of industrial products (i.e. non medical) would the cost of the system represent an issue, especially if the quality of the optical measurement data needs to be high?

    Thanks and kind regards.

    Roberto Teti

  2. sebastian.kaiser

    Dear Prof. Teti,
    thank you for your comment.
    The cost of this system is definitely an issue. The use of the system is currently only economically practical for high-priced products, such as in medical technology or aviation.
    However, the optical measurement systems are becoming more and more powerful and also cheaper due to further developments. Therefore, I can well imagine that in the future, new applications in other technical fields will gradually emerge that can also be manufactured economically with this system.

    Best regards
    Sebastian Kaiser

  3. Hello Sebastian,
    thank you very much for the interesting presentation of your optical data based process compensation.
    I’ve got a question concerning slide 9: Who is your data process chain managed? Are you getting the error vectors directly from the Zeiss Software and could you please explain a little bit more about your data process chain. I assume you need several in-/ and outputs from meassurement to the final compensated G-Code.

    Thanks a lot,
    Lukas

  4. sebastian.kaiser

    Hello Lukas,
    thank you for your question. I can devide the box “opt. meas.” and “data processing” in some more detailled steps for you:
    1. The opt. measurement is done in the software “Colin3D”. This software is only for measurement and the measurement options. The measurement data are processed here for the first time and are then available in STL format.
    2. The STL data is then imported into GOM Inspect. In addition, the CAD model and also a matrix with nominal coordinates (blue Points on the slide) are imported.
    3. In GOM Inspect then the calculation of the error vectors and the compensation vectors (compensation matrix) is done. This matrix is the only result of the calculation, so only the matrix must be transferred.
    4. The adaption of the G-Code is done in Matlab.

    For automation and data transfer between the systems Colin3D–>GOM–>Matlab I use Phython interfaces.

    I hope I could answer your question a little bit. otherwise you can also contact me by mail.

    Best regards
    Sebastian

  5. Hello Sebastian,
    thanks a lot for your explanation. I’m quite interested in your python interfaces, since we want to automate the data transfer between differrent software as well. In our hybrid process chain we need a link between measurement system (e.g. GOM) and the slicing software (e.g. Netfabb). Right now we are trying out solutions like openRPA. I’ll send you an eMail in the next days. I’m looking forward to connect.

    Best regards,
    Lukas

Leave a Reply

Your email address will not be published. Required fields are marked *