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:

Robert Brower

Verified Members
  • Posts

    33
  • Joined

  • Last visited

    Never

Recent Profile Visitors

296 profile views

Robert Brower's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I cannot say much about Easy-Rob but here's a link. http://www.easy-rob.com/indexx.htm Robert
  2. Ok. Is there a way by looking at the NC, to see if the misc reals I am setting via the SDK are considered in the NC? I'm using MPFAN.PST. Does the operation need to be rewritten to the database after the misc reals are set, before using postOps() for them to take effect? Thanks. Robert
  3. I guess what I am asking is, I see them listed in the PST file. If I set these values through the sdk, are the values I set reflected in the post?
  4. Hello again. Another CHOOK related question regarding misc reals. I don't understand how they are used. I'd like to set the Misc Real values that are used in a post. Is editing a PST file the only means to do this or can one modify the misc reals in an operation and expect to see these used in the post? I guess what I want to do is override the ones in the PST file with ones that my chook comes up with. Thanks again, Robert
  5. Is there a way to use the import_operations() function in a CHOOK so that it keeps the NCI filenames of the library operations that you're importing? When I use this function, my operation's NCI filenames which are unique for each operation, seem to all change from their unique names to D:program filesmcam9millnciT.NCI. Has anyone seen this? Thanks in advance! Robert
  6. I made an observation. If you get the link error complaining that DLLMain is already defined then remove the 2 chook dev OBJ files from your project, click build (you will get errors), then readd the OBJ files and build again (you will not get errors), save your project and solution. It's because of the order in which things are linked. This is a workaround. Robert
  7. 9.1 but it actually does work when you use the correct file attributes. I mistakenlyused "r" when it should have been "r+b". I wish I could delete this post. Also, in the m_db.h for get_db() it says: boolean *succf); /* O: TRUE = error storing in the database */ I mistakenly thought when succf was true there was an error because of my literal translation of the comment. When succf is true the function has succeeded, otherwise it is false. Thank you though.TGIF. Robert
  8. Up until now I've been importing parasolids, and iges files into mastercam. Now I need to open an MC9 file but I can find no function to do so in the SDK examples or documentation. Would I use open_file() and get_db() to do this? I can see there is a VB Script method for doing so, but I'd like to know how to do it in C. Does anyone know of a sample for this? Thanks, Robert
  9. To post each operation one at a time with postOps() using a WHILE exactly what i am doing. I am in fact using the same code you pasted in above to do that and what I am saying is that for all 4 different operations, the resulting 4 NCI files are identical. maybe mastercam just doesnt see the differences in the operations that I have made. i am for example for operation one cutting a slot with a slot cutter along a chained series of splines and arcs. I am doing this by turning the vertical tool onto its side via CPlane, and in the copies of the original toolpath i am adding an offset by adding half the width of my tool to the DEPTH parameter. backplot looks sweet, but the NCI files are no different from on another. Robert "mastercam hates me"
  10. No, one operation, the first... every time, even though as in your code, we're going to the next op before we loop. I guess I must be getting confused as to how to combine postOps() with run_post_exe_dll() to avoid all the file dialogs, etc.
  11. I don't understand. If all of the operations use the same NCI and NC filename, and I postOps() on each of them one at a time, and after I postOps() I copy the NCI file to another location and rename it, then I wind up with 4 identical NCI files. Why is postOps() creating the same exact NCI file for 4 different operations? Sure, the original filesnames are the same, but i am copying them off and renaming them. The sequence works like this: count = 1 while not done get operation postOps() copy myfile.NCI to myfile.count.nci increment operation count ++ end while In the end, the contents are the same. and this is the problem.
  12. Yes they are, but in that loop, I am copying each file to another location and renaming it before looping back for another postOps(), e.g. MYFILE_OPERATION_1.NCI, MYFILE_OPERATION_2.NCI, etc. It is these NCI files that are identical for all 4 operations.
  13. Bullines, I am using the code snippet you pasted here but I am finding that for all 3 operations that I loop over, the NCI files are identical. This results in identical NC files also. I imported operation 1. Then I chained it, and copied it to operation 2. I changed the tool of operation 2. I copied operation 1 to operation 3 and I changed the tool on that one too. Do you know why I might be getting identical NCI files for 3 different operations in that loop? Thanks a lot. Robert

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...