-
Posts
447 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Posts posted by Zoffen
-
-
how about a mastercam install on a ramdisk....anyone think that might be faster than an ssd?
or any software on a ramdisk....wonder if this would make things faster.
really tempted to try it.
-
Cool! thanks a bunch!
Don't have time to play around with the machine untill the end of the week so we'll see if i can't get it figured out.
Man those machines are sweet!
Does anyone have any info on the 5 axis post writing. I figured alot out by sheer determination and time in front of the monitor but i would really like more info on how all the vector functions work. Any info on using the vector functions to calculate/map WCS's to the top plane and then post correctly would be awesome. I know this is very complicated stuff, but having minimal documentation makes it alot harder.
-
yes. 5 axis with g43.4
-
-
I'm trying to get TCP to work on an 2012 Mazak Integrex i-150 and am wondering if anyone can post up a code sample of entry and exit into TCP.
I tried to use the examples from the manual but as we all know they are very weak.
Any help would be much appreciated.
Thanks!
-
Its different for educational posts....not sure why....
They have a guy who writes all the education posts.
-
They are getting a post from mastercam for it.
-
In the public world they buy things one piece at a time. I'll have them look into that. Seems to be working out with the generic Matrix control.
-
The local tech school just got an Integrex i-150 (and A VF3SS w TR210) (and a DMS 5 axis router) and i'm helping them out get it going programming (Mastercam) and verification wise(Vericut).
I'm wondering if the Matrix control file for the Integrex Mk IV series will work for the I series machine?
I can modify control files but it would be great if the control file provided with Vericut would work out of the box with minor tweaks.
Or would the standard Generic Matrix control just work fine?
Thanks!
-
Cool thanks. Ill check that out.
-
This can be adressed automatically with the post processor file. The programmed feedrate can be adjusted by comparing tool radius and interpolated radius. So, whenever the cutter enters a tight corner, it is slowed down automatically. Conversely, if it is interpolating around an outside contour, feedrate is increased. This maintains constant chip load at point of contact.
How does the post know if its an inside or outside corner?
-
In windows 7 when i right click on an icon there is a render openGL on... option.......
I am running a Quadro 4000 and a GTX 55TI,
My original thinking was i would hook my nice monitors up to the quadro outputs; but it still drags on the quadro when i move the window onto a monitor driven by the GTX card.
Not an expert by any means, this is just my experience.
-
hello,
I am new to c-hooks and i'm wondering if i could get some sample code to get all tool data for each tool in the machine group.
Thanks!
-
I just got the system in my siggy up and running and it has been awesome so far.
H100, no problem!
Can't wait to start pushing this thing....need to water cool my graphics card first. thos 4000's sure do run hot!
the bigger the better. build your system so you don't have to upgrade in a year.
-
oh i see what ur trying to do now....probably should re-read before i post stuff! DOH!
Ya i would go with what yoDoug is saying by incorporating the renishaw macros into it:
Something like this maybe
- Basically moves the probe in X+,Y+ to set Z then moves back past original X,Y position to probe edges
O0001(X+,Y+ Corner Set)
(Sets Z then sets X and Y)
(Jog Probe to .25 above corner you wish to probe)
#1= .5 (Distance to move in X&Y to probe Z surface relative to routine start position)
#2= -.5 ( Z position to measure X and Y relative to probe routine start position)
#3= 1 (Work offset to update)
G91 G65 P9510 X#1 Y#1 F100. (Protected Position)
G90 G65 P9511 Z0.0 S#3 (Measure Z Surface)
G91 G65 P9510 X[-#1-.25] F100. (Move to X probe location
G65 P9510 Z#2 (Move to probe depth
G90 G65 P9511 X0.0 S#3 (Measure X+)
G91 P9510 Z[-#2] F100. (Move to clearance)
G65 P9510 X[-#1+.25]
G65 P9510 Y[-#1-.25] (Moves to Y Probe position
G65 P9510 Z#2 (Move to probe plane)
G90 P9511 Y0. S#3(Measure y)
G91 G65 P9510 Z-#2 (Move to clearance)
G90
M30
Just banged that out in a few minutes so some stuff may be wrong. But hopefully this is something that will lead you down the right path.
-
if the macro looks up what work offset is active and cal the positio it wont matter what offset is active. Or u could use a work offset just for work setting using the probe.
Also if ur probe is always the same number u can modify the tool change routine to active the comp?
Or can u do an incremental g43 move?
G91 g43 h# z0.0
-
Could u grab the active work offset and calc what position it would be in that active work offset then apply a g43 move to that position which would net in a move of nothing....then ur tool comp would be applied properly and u can probe away. Hope this is what ur looking for!
-
Yes sir.....look for the only guy in a green hat that looks too young to be here lol! Prolly be in the software and machine halls.
Cnc apps guy and others, would be nice to meet u all face to face and shake ur hand in thanks for all the help! Wheres the emastercam meet up!???
-
Hotel 71 anyone....
-
Im here. Any way to tell emastercammers from ur average show folk? I would like to thank some of u in person for your help!
Overwhelmed by the awesomeness of this show!
-
Going for the whole week!
BOOYAY!
-
figured it out.
gotta use a string selection table!
-
i've put some feed 0 and speed 0 checks in my post and now i want to output a message saying "0 feedrate/speed found in op#"
I've got it all figured out except for combining my string with the opnum variable. how would i do this?
thanks!
-
updated to the latest ODE Graphics driver and it still has this problem
Custom Mastercam PC Build
in Industrial Forum
Posted
I have basically that same setup but got the i7-3930 (Hex core) and i love this system.
with OC (2400mhz) ram you need to setup a bunch of stuff in your bios to actually get it to run at that speed.