Jump to content

Welcome to eMastercam

Register now to participate in the forums, access the download area, buy Mastercam training materials, post processors and more. This message will be removed once you have signed in.

Use your display name or email address to sign in:

TomSanders

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by TomSanders

  1. I am new to NetHook, but have a decent amount of programming experience. I am only two days in and I already have hit limitations with the NETHook API. Can you share a more specific example of how you leveraged C++ library into .NET? I would like to access the 'Full Set Of Features" without having to change platforms or languages....
  2. So making some good headway... Are there any user fields available to store header info strings that save with the file? IE: Customer PartNum Sequence DocumentationPath Etc.... I can use a comment field with a delimited string, but looking for a more elegant and robust solution, preferably something that is not easily edited from MCX Gui.
  3. Mick, I have started the process of compiling all the resources, samples and documentation. I hopefully will be "swimming in the deep end of the pool" in the near future, after I do a mind meld with all the material. I will certainly utilize this forum as questions arise. Thank You! Tom
  4. I just downloaded the Mick George NetHook stuff from the VS Gallery. I have not explored it as of yet. I have several years experience with VBA and VB.NET. My MCX related goals: A. Write a POST or a VB NETHook to export setup info. B. Use the SQLite tool database as a master to drive other copies in our facility (we have 4-5 variations of a tool db that are manually synced for different apps) Goal B will be most likely accomplished with an external utility and not directly from the MCX Gui. Goal A: Currently I have a parser that reads tool changes and station information from the GCode files, and imports them into Excel sheets. The Excel sheets are linked to an Excel datasource that looks up the tool specifics. This is an inherited legacy system, that is fragile and has many shortcomings, but also has great flexibility. Excel is still on the table as a container, but needs an overhaul if it stays in the equation. We use three main CAM packages MCX9, ESPRIT, GIBBS for MILL, LATHE and PROTO respectively. PROTO does not use standardized setup sheets. LATHE uses ESPRIT. In ESPRIT I was able to write VBA extensions that do the following: 1. Pull Job Header Info From MRP And Attach to CAM File 2. Loop through Operations and make list of Tools/Stations/Comments etc 3. Export list to standardized XML document text file 4. Launch Excel to automatically consume XML and do it's magic. I want to do the same thing in MCX9. Using NETHook: Item 1 requires a few unused fields, or user defined fields to be available in the file structure. The rest is handled by a .dll of my making. Item 2 requires a knowledge of the MCX structure and functions available to retrieve data. 3&4 are all on me and are not MCX specific or as an alternate MP POST: Generate standardized XML document text file directly via POST Handle header and etc later in process. ESPRIT had great inline help for VBA and their data structure. That was a great aid in reducing the time to deliverable. Is there a resource that would get me a jump start on Item 1 and 2 above? Tutorials? Searchable Code Examples? Thanks!

Join us!

eMastercam - your online source for all things Mastercam.

Together, we are the strongest Mastercam community on the web with over 56,000 members, and our online store offers a wide selection of training materials for all applications and skill levels.

Follow us

×
×
  • Create New...