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:

André Lapointe@In-House Soluti

In-House Solutions
  • Posts

    125
  • Joined

  • Last visited

Everything posted by André Lapointe@In-House Soluti

  1. quote: Variables: fmt Q 2 shftdrl$ #Fine bore tool shift fmt I 2 shftdrl_i #Fine bore tool shift I Value fmt J 2 shftdr1_j #Fine bore tool shift J Value Then, I have this in the common drill postblock: shftdrl_i = shftdrl$ shftdrl_j = shftdrl$ I don't know if it's a typo but one of the reason might be that your variable definition name doesn't match the name you are calling out. Take a look at this and see if it helps.
  2. Using Cimco V5.6 I have had this locking issue when posting at the same time the NCI and the NC file. Cimco opens up with the NCI, then MC waits for me to close cimco then post out the NC code. I went back to the given version of cimco in Mastercam and all works fine now. HTH
  3. In the MPmaster post there is a switch that you should look for to disable the tool table and it is called : tool_table, set it to 0 and no more tool table will appear. It will be located in the general output settings section of the post around the line 200-220. HTH
  4. Good morning all! I have a question here, does anyone of you knows how to change the metric feed unit from mm/min to m/min in the active report setup sheet? All of this in order to have more accurate cycle time. Thanks in advance for any and all inputs you can share! André
  5. You can set-up your rapid feed rate in the Machine definition file, by looking in the edit general machine parameter button.
  6. Has anyone been able to switch the feed unit shown and/or used to calculate the time estimate. For example, if I need my feed to be in meter/min instead of millimeter/min as it is right now, how would I do this? Thanks
  7. Look for one of the lines where there is a *sm00. that might be where is the line that you want to get rid of. HTH
  8. in fact you would have to set gcode$ = 0 in order to get the proper output. the way the string table works is the following, you assign a string a value (like sgcode could be either G00-G01-G02-G03, etc...) based on the value of a numerical variable (like gcode$ or absinc$) So depending on the value or the numerical variable the string will output different things. The strings have to be manipulated in another way from the numerical variables. Hope it is clear enough!
  9. The error comes from the fact that the sgcode value is affected in the string table, for the range usually from 0 to 5, to be able to get G00 to G04. This string is define by the value of the variable gcode$ which have more that 5 possibilies. For example, gcode$ = 1003 means you have reach the end of file. So if you call out the sgcode string when the value of the gcode$ variable is not within the 0 to 5 range, you will, get the error message you see plus the post will output the first value of the table in this case G00. Hope it is clear enough, one thing you can do to understand this is to following, on the line above the one causing the error message write this: ~gcode$, "value of gcode$", e$ save the post and generate the code, in the Nc file you should see the following line or something very simmilar: gcode$ 81 value of gcode$ then you will see that the value is really out of range for the string table defined. To get rid of this message you can manually assign gcode$ the value 0 at the beginning of your section or output the sg00 string instead of calling the sgcode string. HTH
  10. The " ` " means it is forced with a condition, it will come out only if something else on the line has to be outputed otherwise it won't come out. As for the "*sgcode" you found in the pcircout1 block this one is only for the arc moves. You probably have one also into plinout, prapidout, and maybe a few other places. HTH
  11. You can control those values from operation default files located into the files section of the machine properties. You can create yourself a vertical default file and an horizontal default file this way you can link into the control file of your machines the default file you want to use. HTH
  12. You probably need to put the same condition into the ptlchg$ and the ptlchg0$ block as well because psof$ is only read at the beginning of the program so if the first operation has the mis value turn off it will never be read again. By copying this condition in the 2 other post block I mentionned you will be able to read the value of your misc value at every operation. HTH
  13. Look in the control def file in the arc section and make sure you have the check marks in the boxes relative to the arc on another plane than XY, something like allows arc on XY planes, on XZ plane or on YZ plane. HTH
  14. I don't know of any Wait function, but it doesn't mean it doesn't exist. So far, without the wait function it should work the way you wrote it. Let me know.
  15. yes there is this function. it could be part of a condition like this: q1 #question call while (sanswer = snull), [ q1 counter = counter + 1 if counter = 15, exitpost$ #put the value you want here for the counter ] same idea for the other solution I gave you earlier. HTH
  16. if you are using a string, you could define a string snull "" to which you can compare the value of the answer and then ask again the question if needed. something like this maybe: q1 #question call while (sanswer = snull), [ q1 ] sanswer being the answer from the prompt screen this way as long as the answer is null, you stay in the loop. Just make sure you don't create an infinite loop. Another way could be the following: q1 #question call if swanswer = snull, q1 this way if the answer is null, it will ask again the question. HTH
  17. In facts, <> means "different" in the post. If the value of auto_hood doesn't change from the previous time it was assigned a value, it won't output unless you put a * before it to force it out. Maybe try that... HTH
  18. Well, you can still look for the same parameters, they might be there even if you are not using MPMASTER.
  19. In-House Solutions has a Biesse post that I'm pretty sure would fit your need. You should try and contact them or talk to your reseller. HTH
  20. The control def is read from within the post, and initialize a lot of the predefined variables. So it won't really effect the NCI, but will give guidelines to the post as to how to use the information given by the NCI. Barely the same with the Machine defintion files. HTH
  21. Hi welcome to the forum, A lot of the post I've seen, have a misc value that you can choose to either output the code in absolute or in incremental. Maybe start by trying this, usually the second misc integer. HTH
  22. @Cannon It is already possible to do this. In your chainning window, click on the small blue arrows on the top left corner of the window to expand it. You should have the control to change the starting point as well as the end point and also the dynamic start point option that will become available. HTH
  23. If you are doing different operations on every side, it would be easier to position every part, IMO. PLus it will be easier if you want to setup a work origin for each side. Otherwise you might have to messed up with a lot of different planes in order to get your B value to come out properly. I don't say it is impossible but it is going to be a lot of work. HTH

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