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:

samysnes

Verified Members
  • Posts

    14
  • Joined

  • Last visited

Everything posted by samysnes

  1. Oh, that's a great idea! I didn't think of that. I will ask them ASAP. Thanks for the insight
  2. I can confirm that the variable is not present. I looked at what I had available line by line last night. My reseller finally got back to me and they are gonna change the PSB. I wish it wasn't such a bother to do something so trivial. My operators are getting impatient haha
  3. Thank you for clarifying. I incorrectly assumed that the only part of the post processor's code that would be encrypted would be the part that's binding it to my HASP number. I thought I could edit it as a whole but that if someone else tried to run it, it would just refuse to post. But yes it makes sense that some part of the code would be locked to prevent someone from creating their own post processor from it. I guess I just consider adding a tool to the code to be something that I should be able to do on my own and it's frustrating that the part that shows the M codes with a comment of which tool triggers them is open but not the way to change said tools... I mean, I could just create a script that adds M418 and M419 for every T9 operations at this point so why make me go through the hassle. Am I making sense or am I just coming across as an entitled whiner? I guess working with Linux has clouded my judgement on open vs closed source. Thank you for your time Colin!
  4. No hard feelings, my man! It was just a rhetorical question because I was disappointed to find out that such a basic function (adding tools to coolant logic) is not part of the "open" portion of the post processor code. I do apologize if I came across the wrong way. I just wanna take the time to thank you again for trying to help me though. It is much apreciated.
  5. I am not sure why you felt attacked by my comment but you need to relax. I was never implying you were being mean and I have nothing against you, I am in fact very grateful you took the time to comment. I am fully aware how software license ownership works. Don't be condescending and telling me I need to educate myself. Maybe you mistook me for some clueless dunce and your frustrations came out. I never said that I should own Mastercam and its source code. You are putting words in my mouth. I can't believe you felt the need to remind me that I don't own Windows... I do not equate owning a post processor to owning Mastercam in its entirety, that's a ludicrous statement. They are two separate things. The post processors I can purchase from my reseller is a standalone purchase and not a recuring subscription, therefore I assumed it would be DRM free. Also, english is not my first language so sometimes I use the wrong words trying to convey something. Still, not sure how you got the feeling I was claiming I should own Mastercam and Windows.
  6. Wait so you are telling me we can't properly edit our own post processor?? That sucks! I'll wait on the call from my reseller then... Again thank you very much for your time!
  7. Yes, I have tried opening that .PSB file to no avail. Do you know of any software that can read that PSB file? I have tried Notepad++, no luck. Yes I reached out to my reseller. Waiting on a call back.
  8. Thank you for your reply. That was my first thought as well but I scoured the entire file and didn't find anything relating to that. Would it be in the same .PST file or could it be in another file somewhere?
  9. Hi, I'm having an issue with an old post processor for an AXYZ router with an A2MC controller. Ever since the post processor was created, we have added a tool to our library. The router has 3 heads and each head has its own M code for mister coolant On/Off. Head #2 & #3 have exclusive tools that we leave in there and head #1 is where we swap the rest of the tools. So basically we need the post to go "if Tool #4 is called, activate mister for head #3, if tool #2 is called, activate mister for head #2, etc. I looked up the post in notepad and I found the following: # Coolant M code selection sm09 : "M09" #Coolant Off sm08 : "M418" #Mister tool On # 1-5-6-7 sm08_1 : "M420" #Mister tool On # 2 sm08_2 : "M424" #Mister tool On # 4 sm09_1 : "M419" #Mister tool Off # 1-5-6-7 sm09_2 : "M421" #Mister tool Off # 2 sm09_3 : "M425" #Mister tool Off # 4 scoolant : "" #Target for string fstrsel sm09 coolant$ scoolant 7 -1 As you can see, each head has its own set of M code. Head #1 is M418/419, Head #2 is M420/421 and Head #3 is M424/425. We now have a tool #9 and I don't know how to add it to head #1's pool of available tools (it currently triggers on tool #1-5-6-7). How do I tell the post processor to trigger M418/419 on tool #9 as well? I looked everywhere and couldn't find anything. Thank you very much for your time
  10. Oh I assumed that the add-ins would be done in VB like the custom setup sheets. I will try my best to get familiar with these C hooks. Thanks to everyone for your time!
  11. Haha! Got a chuckle out of this one
  12. I have very limited knowledge of VB sadly but I've been experimenting with adding the path in our DWG in Autocad before importing in Mastercam. We use routers to engrave giant sheets of aluminium so our programs are always flat and 3-axis only. Therefore, we are able to add lines of text in Autocad before importing in Mastercam. However, when I try to import a DWG that has a filepath written in it, Mastercam looks like it cannot convert the backslash \ character properly. It just produces a garbled mess... See pictures. Also, exploding the text into geometry isn't really an option because the text in Autocad has to remain in text form for the filepath to be generated automatically when we "save as". I have tested a dozen different fonts both in Acad and Mcam and nothing has worked so far...
  13. Unfortunately we were looking to have something that automatically puts the filepath on the printed page. We frequently dish out hundreds of programs a day so manually adding a note isn't really a solution. Printing the filepath worked flawlessly in X7 so it's mind boggling why they would reduce the font size this much.
  14. Hello all! I have recently upgraded our team's PCs to Mastercam 2020 and we are having an issue with the printed Name/Date that appears at the top of a print (see picture) Once on paper it is laughably tiny. So much so that our operators in the warehouse are complaining that they can barely read the program number. Is there a way to make it bigger?

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