Peter - Avivi CNC Solutions
-
Posts
292 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
eMastercam Wiki
Blogs
Gallery
Events
Everything posted by Peter - Avivi CNC Solutions
-
Finding angle between WCS and user defined WCS
Peter - Avivi CNC Solutions replied to SGarofolo's topic in Industrial Forum
Well, I just started... I have everything now, I just need your help to point me on the right direction with math... I'm sure that angles are not correct now. I can read zeros, vectors from MCAM. But I'm not a math guy... Any ideas can come! -
Finding angle between WCS and user defined WCS
Peter - Avivi CNC Solutions replied to SGarofolo's topic in Industrial Forum
I did! Believe or not, I just start to work on it for fun, we'll see where it goes. ...and when... -
Finding angle between WCS and user defined WCS
Peter - Avivi CNC Solutions replied to SGarofolo's topic in Industrial Forum
A C-Hook or a NET-Hook may be...? Hmmm... Make sense for me... Let's see. -
Saving a useable STL file out of X7 Verify
Peter - Avivi CNC Solutions replied to CamMan1's topic in Industrial Forum
What is the reason of this switch? Why needed to switch between 3ax/5ax engine? I'm just curious, not blaming here. -
Rounding off post output
Peter - Avivi CNC Solutions replied to gary adams's topic in Industrial Forum
Some search in post section... http://www.emasterca...showtopic=67823 http://www.emasterca...showtopic=62826 -
Saving a useable STL file out of X7 Verify
Peter - Avivi CNC Solutions replied to CamMan1's topic in Industrial Forum
I usually make a "Base Stock" Stock Model OP for start. In your case, you can extrude a solid, as I made on level 100 for stock. Then you good to go in verify also. No need to play with STL files from outside. Just as I don't like too... -
OR do some search... http://www.emastercam.com/board/index.php?showtopic=64737 http://www.emastercam.com/board/index.php?showtopic=62826
-
Which post? In mpmaster try to change format numbers to 12: fmt "X" 12 xabs #X position output fmt "Y" 12 xabs #Y position output fmt "I" 12 iout #Arc center description in X fmt "J" 12 jout #Arc center description in Y fmt "K" 12 kout #Arc center description in Z
-
I'm not really sure... I would use abs() function: if depth$ < 0, depth$ = abs(zr$ + depth$)
-
Tolerances For 3 d toolpaths
Peter - Avivi CNC Solutions replied to ctyler's topic in Industrial Forum
Glass containers? My favorite... If you use Parallel Finish or similar toolpathes often, I also suggest to use arc filter strongly and not only in XY plane. I used on XZ and YZ planes also with lot of success on this kind of moulds and older machines. But in this case I would use I-J-K on arc moves, instead of R. Your older Okumas has OSP5000 control? -
How to set tool and offset numbers?
Peter - Avivi CNC Solutions replied to K2csq7's topic in Industrial Forum
I suggest to force regen the operation after you change anything in and even if it not goes dirty. You can setup a logic in post to check offsets and/or build a detailed toolist at begining of NC code with ALL offsets in NC code. Me too... -
Thank Josh! I have the beta, but not work. I hope, not work yet... Same here...
-
Is it worked in previous versions? X6?
-
Ohhh, where? When? Any feedback/answer? Yess, Tool/Holder length or full length at least. :S
-
Yepp, I thought that should be a problem, so today afternoon I dowloaded the latest (1.70), but no changes. Well, afternoon for me...
-
Containment boundaries don't work right?
Peter - Avivi CNC Solutions replied to Bob W.'s topic in Industrial Forum
+1 -
THX dude! Also works for me, but the problem is with 20007-7 that it's from the original tool definiton, not from the given operation. 20007-3 should be OK, but holder length not. :/ That's why I need 15832 and 15836.
-
Hi all, I made it many-many times... But today... Pfff... I'm try to dump into my favorit buffer the overall length of tool and holder from operations, but no luck... I uncommented the following line, but no luck I can't find pwrttparam$ #Pre-read parameter data "pwrttparam", ~prmcode$, ~sparameter$, e$ Yes, I did this: if prmcode$ = 15832, ToolLength = rpar(sparameter$, 1) #Szerszám teljes hossza if prmcode$ = 15836, ToolHolderLn = rpar(sparameter$, 1) #Szerszámtartó teljes hossza Any idea how can I get the 15832/15836 parameters?
-
What kind? I have one with Android, but thinkin' to change. Do you use it for....?
-
THX! Yepp, I plan to make a much simplier implementation. Keep track this topic!
-
No, not really. :/
-
Then you can use a pre-calculated variable, z_min$ it gives you de maximum depth of operation. No need to catch 10029 parameter, just simply output it. Your operation_depth variable already formatted, so, example: # operation_depth = z_min$ "( DOC =", *operation_depth, ")", e$ last_op_id = op_id$ #
-
Yes. Always almost... Need to define EXACTLY what we want. Error check during post? List from these values in header section of NC code? List from these values at tool changes in NC code? Check and compare values to given Min/Max values?
-
Good to mention this also! But now I think you need the lowest Z value (during machinig), not the operations depths... Am I right?
-
Hi Steven! Good thing that you catched this! Need some improvement, I'll work on it! I didn't think about this issue when I made it. I'll be back.