Steve Biehl - Cimquest Inc
-
Posts
1,386 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Everything posted by Steve Biehl - Cimquest Inc
-
dan, do you have a post that output mill turn code? do you know how to do milling surface machining? have you done other lathe face and cross milling? without seeing the part, you should be able to go into the face or cross plane and just do the surfacing toolpath you need. in the ops rotary settings, you can set it to C or Y axis code.
-
along the angle of the swarf
-
Problem running X3 MU1
Steve Biehl - Cimquest Inc replied to Thee Rickster ™'s topic in Industrial Forum
goldorak, can't reproduce that here. sorry -
Mastercam X3 MU1 is Released
Steve Biehl - Cimquest Inc replied to Chris Bell CNC Software's topic in Industrial Forum
quote: Can you directly open Solid Works 09 files after install of MU1? Thanks- still haven't pulled the trigger on X2 to X3.... figured on waiting til the SW09 thing came out. Greg gms, yes X3 MU1 opens SW2009 files -
how is inverse feed calculated?
Steve Biehl - Cimquest Inc replied to Joeyls319's topic in Industrial Forum
Inverse Feed is the inverse of the amount of time necessary to make the move, and since each move has a different distance, the corresponding time varies for each block as well. F(code) = 1(minute) / (time = 3D distance move) -
Update
-
Tony, when the post calculates out inverse time it makes it non-modal. The post and/or the MMD needs to setup that you get inverse for rotary motion.
-
quote: mastercamguru: I haven't seen you in years.(back when v8 came out you came to my shop and did some post magic for me) Nice to see you in the forum. welcome to the forum, you'll find that a few of my guys and myself are here quite often. Give the office a call if there is anything we can help you with.
-
post may need to be modified to output correctly. Most generics will output that as an axis rotation.
-
if you have or had maintenance in thru 01/2005 then install the V9 MR0105. There is also a V9 patch for getting the hasp to work on XP SP2 - http://www.mastercam.com/Support/Downloads...aspx#V9.1%20SP2
-
in lathe, always define stock and then tool will retract out of id before going home
-
then run the nethasp utility and confirm that the maintenance expires in '09
-
Columbo, did you check your HASP info to confirm that the current licensing is set in HASP? In the X3 program folder, run the haspx utility and 'Read' the info from the sim.
-
do you know that you can add folder shortcuts in the area on the left of the file open? browse to your folder and right click in the left area
-
Mastercam and Multitask Lathes
Steve Biehl - Cimquest Inc replied to camathome's topic in Industrial Forum
MMT = Mastercam Multi Tasking -
Verisurf WCS
Steve Biehl - Cimquest Inc replied to Verisurf - Ernie Husted's topic in Industrial Forum
James, ug read and other features of Verisurf are purchased items. Check with your dealer to find out about them. -
Mastercam and Multitask Lathes
Steve Biehl - Cimquest Inc replied to camathome's topic in Industrial Forum
MMT has nothing to do with having or using Solidworks. MMT will be a module for Mastercam Lathe for syncing and simulating Multi tasking toolpath. We have just started Alpha testing but it is looking very good. -
+10000 on 10k hd, big big difference on MC performance
-
Jim, problem with 'correct' way is that you keep getting the warning dialog of same work offset used for multiple planes. If that could be turned off I opt for the WCS value variable.
-
not a simple edit but... - setup a misc integer to flag that you want to lock on first wcs - save value of first wcs - use saved wcs if flagged to lock to 1st wcs
-
check the 'Misc values' in your operations. Integer 10 allows for biasing the secondary axis to the positive or negative.
-
John, it is because you are in X and not X2. Chooks are not usually compatible between version and need to be compiled for that version. I don't know if there is an X version of that chook still around.
-
No, the third axii is always there.
-
quote: couldn't you just change the pxout to pfxout and pyout to pfyout, etc Would work fine but you may have to do a bunch of digging to find all the pxout/pyout/pzout that you would need to change. Change the format statement in one place and all outputs using that format are effected.
-
a quick, dirty way to force the G-codes out is to use the post variable force out symbol. In your rapid, line and arc output sections force the sgcode variable. Example with the line output section: code: plinout #Output to NC of linear movement - feed pcan1, pbld, n$, sgfeed, sgplane, *sgcode, sgabsinc, pccdia, pxout, pyout, pzout, pcout, feed, strcantext, scoolant, e$ The * on the sgcode variable will force it out every time.