Verified Members
  • Content count

  • Joined

  • Last visited

Community Reputation

116 Excellent

About SlaveCam

  • Rank
    Advanced Member


  • Location

Recent Profile Visitors

2,571 profile views
  1. If I edit local machine or control definition, every operation's program numbers are reset back to "default program number" under Tool menu. Can I stop that from happening using some hidden checkbox somewhere?
  2. I did some testing and it seems no matter what's selected in the abovementioned setting, the program number of a transform operation that uses another transform operation as source does not have its program number written to NCI. So in this case program number seems to be kind of a special case. In 4 axis work it's common that I use the same source operations for different tombstones and the fixture positions may wary as well, so there is no avoiding nested transforms, unless you love useless extra repetitive work. G54.2 would be a huge help, so maybe I'll get it one day.
  3. No, I'm not sure. Didn't even think about the existence of such a switch. I'm going to check it out tomorrow, thank you for this tip!
  4. Hi, This hack is due to this problem Program numbers are not written at all to NCI for transform operations, so I have to use a transform operations's misc integer. Furthermore, trans_mi$ does not contain the "latest" mi-value in case of nested operation. If you know a better way, I am all ears
  5. Got it: atest : 0.0 stest : "" pheader$ #Call before start of file stest = opinfo(1032, 0) atest = rparsngl(stest, 1) "Test:", *atest, e$
  6. A NCI file has the following lines: 1031 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 1032 3000 0 0 0 0 0 0 0 0 0 These are transform operation's custom parameters, where 3000 is the value of trans_mi1$ (or actually in case of nested transform, it is not, thus my attempt at opinfo) The following code outputs the following string Test:3000 0 0 0 0 0 0 0 0 0 stest : "" pheader$ #Call before start of file stest = opinfo(1032, 0) "Test:", *stest, e$ However, I don't know how to capture the "3000" part of the NCI line; if I change the code to test : 0 pheader$ #Call before start of file test = opinfo(1032, 0) "Test:", *test, e$ the result is always 0 or -99999, no matter what I enter into the second and third parameter. How Do I Use Opinfo Correctly?
  7. Because all post processors seem to ignore the program number assigned to a transfer operation, I've had to add a line to pheader post block: if trans_mi1$ <> 0, progno$ = trans_mi1$ so that the program number outputted is the same as transform operation's first custom parameter. However, in case of nested transforms, like in the file attached, it is not working. The aim is that (see the attached file) If you post only operation #1, it would output O1000 If you post only operation #2, it would output O2000 If you post only operation #3, it would output O3000 How do you do that? EDIT: This was supposed to go to the post processor forum! Sorry. PROGNO.mcam
  8. SlaveCam

    Enter pivot distance box

    Yes. Is this a common dialog in CNC Software's post processors? If someone from CNC could confirm if there is something in the encrypted section that can be set in non-encrypted post block to bypass this. What kind of encryption do these files use? (no, I'm not going to try crack one, just curious) AES? CNC's own? Are mill-turn posts still completely encrypted in year 2022?
  9. This is an older MT640 Pro post processor from CNC Software. I want to get rid of this message and use a post variable. Unfortunately part of the post is encrypted and so is this message. File name is "Mazak Integrex Fusion 5X Single_Turret MT_Lathe.pst" Is there a way around this?
  10. That was FAR too easy. Thanks.
  11. I've been wondering about this for a while When I try to enter 02 or 03, they get converted to 2.0 and 3.0 respectively. Why do I have to go through the trouble of creating a custom tool just to use these not-so-uncommon radiuses? Or is there another way?
  12. SlaveCam

    Function arguments

    Thanks to all. Maybe it sounded too good to be true. I wasn't aware of regex function. Good to know that at least it is there. My replacement function works without regex, but works only for Ä and Ö, which are the most common #region replace_scandics stmpstr : "" stmpstr2 : "" stmpstr3 : "" ival : 0 preplace_scandics #stmpstr is both input and output. input must be in upper case. #Replace Ä->A ival = strstr("Ä", stmpstr) while ival > 0, [ stmpstr2 = brksps(ival, stmpstr) stmpstr3 = brksps(2, stmpstr2) stmpstr = stmpstr + "A" + stmpstr3 ival = strstr("Ä", stmpstr) ] #Replace Ö->O ival = strstr("Ö", stmpstr) while ival > 0, [ stmpstr2 = brksps(ival, stmpstr) stmpstr3 = brksps(2, stmpstr2) stmpstr = stmpstr + "O" + stmpstr3 ival = strstr("Ö", stmpstr) ] #endregion
  13. I remember reading that MP post now finally supports function arguments (Hooray!), "function" here being the same as "post block", assumedly. Is there any examples of usage? I want to apply this neat feature to a post block called "replace scandic characters with non scandic ones" that takes a global temporary variable as input. Does it support return values yet?
  14. Nevermind... please delete
  15. SlaveCam

    View ports in main graphics area

    Winforms is (still) great for business and data oriented apps

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