All Activity
This stream auto-updates
- Today
-
Joshua Mathew joined the community
- Yesterday
-
iztrizi changed their profile photo
-
mward649 joined the community
-
If raster to vector doesn’t work try Inkscape. It is a free software similar to Adobe Illustrator. Make sure the photo file is high resolution, if it isn’t the results might not be great. watch this video. Once you get a dxf you will need to make it into a solid.
-
Try filling in the solid color areas with white perhaps. I think there is some tweaking in the settings also Im on my phone so I cant check
-
I tried raster to vector. I didn't have much look getting the full detail that I wanted. I don't know a lot about raster to vector.
-
Rast2vec chook will get you the wireframe in mastercam, from there you could solid extrude, you would have to clean up the wireframe a bit
-
Is there a way to transform my logo into a 3d solid that i can 3d print? See attached file.
-
TScott-Postability joined the community
-
Appalachianspirit joined the community
-
My Pham joined the community
-
There is something going on in 2019 that is causing the tool to feed down from who knows where. It does it even with the Clearance and retract turned completely off. I've pulled the file in to both 2021 and 2022 and the issue goes away without having to change anything. Rons solutions works in 2019. I should add, it also works (works better anyway) if you change the feed plane to associative and select the chained geometry.
-
Brandonblack0 joined the community
-
In 2022 BETA, I added the check shown and I think it what you're looking for?
-
Sharon Moyer joined the community
-
Lst1standg joined the community
-
*Be careful about using G98 versus G99. If you use G99, it *should* return to the Initial Point, after finishing the G83 Peck Drill. G81, with those parameters, starts at Z0.1, then drills to Z-.64, then returns to Z.1 G83 starts at the Initial Point (Z.1), should rapid to the R Plane (Z-.6), then peck from there. (Note: It won't rapid out of the hole, due to the R plane, so it is kind of more like a chip-break cycle. When the cycle finishes, the G99 tells it to return to the Initial Point. It wouldn't hurt to make this little modification: % O5001 G00 Z0.1 G99 G81 Z-0.64 R.1 F20. G99 G83 Z-1.1 R-0.6 Q.1 Z0.1 G80 M99 %
-
Tyler Caldwell joined the community
-
Hello , Okuma gurus ,please help! We got the alarm "1704 alarm a stroke end over " . Problem is non of the axis not on limit switch physically as i can see. How i can check in the machine control diagnostic ( e100 control ) which limit switch is activated ? Thank you
-
OKUMA V4020 ALARM 5003 DNC-T ERROR 3 HELP PLS!!!!
mig replied to keenzo's topic in Machining, Tools, Cutting & Probing
Are you sure you need the % marks ? This is Okuma not Fanuc -
postingtechnique joined the community
-
Yes, I had been assuming that the <> was the same as the ≠ sign. I got it sorted out, I didn't initially see where it was defined, so I was worried it might be in the binned portion. I'm a little slow on the draw some days. That was where I was brain-farting for a bit. I don't know why it took me 20 minutes to decide to do the simple search, that I should have thought of 1st thing. Meh, like I said, 'some days I'm a little slow'.
-
Syntax question
Colin Gilchrist replied to So not a Guru's topic in Post Processor Development Forum
So this allows you to skip turning off HSM (mode remains on), unless there is a new value detected in MR1. When there is a new MR1 value, the HSM Off block gets called here. There will be other logic, to output the HSM On block. Search for both 'mr1$', and 'mr1flg', using Code Expert Editor, and use CTRL + B to set a bookmark at each location where those variables are used. mr1flg is user defined, so there should be a variable initialization somewhere. It may be in the PSB, depending on who built the Post. mr1$ is predefined, so the Post Developer can just 'use it', without having to format or initialize the variable. Have you attempted to watch my Post Processor Development Class on YouTube yet? 28 videos for basic MP... -
Syntax question
Colin Gilchrist replied to So not a Guru's topic in Post Processor Development Forum
Zeek, Based of my reading: Someone created a variable (mr1flg), that tracks the state of MR1. If the value of the current Operation has a value that is different from the value programmed in the last Operation, then don't turn off HSM. If the value of MR1 is different from the last Operation's value, turn off HSM. It makes more sense, if you are aware that each depth-cut or Multi-pass, is coded as 'an operation', in the NCI Data. -
Syntax question
Colin Gilchrist replied to So not a Guru's topic in Post Processor Development Forum
In MP those characters represent the "Not Equal To" Logic Operator. (<> is NOT EQUAL) If 'the current value of MR1$' is not equal to the 'value of MR1 Flag', then do something... -
That may just work! Thankyou I'll try it out... Thanks a bunch!!!
-
VERISURF TOOLS For MASTERCAM
Verisurf - Ernie Husted replied to Verisurf - Ernie Husted's topic in Industrial Forum
Got Verisurf Tools! Yes, there will be Verisurf tools for 2022. Ernie -
On his original file, in 2019, I switched everything and even removed the clearance all together. For some reason the tool wants to feed from some where in space. When I opened the file in 2021 it was fixed without having to modify anything. Edit: scratch that - the one thing that I didn't do is exactly what you said. Set the feed plane to absolute. This is 2021 without adjusting anything. If you remove the clearance all together, for some reason its feeding from outer space.
-
No it is a Absolute to incremental issue. Switched all the values to absolute and problem went away.
-
I've got it. The flag is set in the phsm2_on or phsm_off sections. phsm2_on #High speed functions after G43 if opcode$ = 3 | opcode$ = 16, [ mr1$ = 0 mr2$ = 0 mr3$ = 0 ] if fmtrnd(mr2$) & not(mr2flg), [ pbld, pn, *mr2$, pe #M821 - Accuracy Level 1 through M830 - Accuracy Level 10 mr2flg = 1 ] if mr1$ & not(mr1flg), [ shapecomp_r = mr5$ pbld, pn, "G61.1", [if shapecomp_r, *shapecomp_r], pe mr1flg = 1 ] if mr3$ & not(mr3flg), #you can't call any G codes inside this [ if dyndatum <> 1, [ pbld, pn, "G5", "P2", pe mr3flg = 1 ] ] phsm_off #High speed functions off if mr3flg, [ pbld, pn, "G5", "P0", pe mr3flg = 0 ] if mr1flg | mr2flg, [ #pbld, pn, "G64", pe pbld, pn, "G61.1 P0", pe mr1flg = 0 mr2flg = 0 ] hsmflg = 0
-
I haven't tinkered with this much in 2019, but when I pull it in to 2021 it fixes the issue. I know that doesn't help you right now, but either something is wrong with the file, or something is bugged in 2019.
-
From my post
-
Where is that from?
-
Here's a sample t.mcam
-
201. Default miscellaneous real variable 1 (mr1)? 0.0 mr1_flg : 0 #Flag to indicate whether look ahead function is active or not phsm1_on #High speed functions before G43 if opcode$ = 3 | opcode$ = 16, [ mr1$ = 0 mr2$ = 0 ] if mr1$ = 1 & mr1_flg <> 1, #Advanced Preview (look-ahead) control - G08 P1 ..... phsm2_on #High speed functions after G43 if opcode$ = 3 | opcode$ = 16, [ mr1$ = 0 mr2$ = 0 ] # HPCC is working when called before G43.4 on Fanuc 31i, see phsm_1 above .... phsm_off #High speed functions Off if mr1_flg = 1, #Advanced Preview (look-ahead) control - G08 P1 [ ...
-
Yes, I understand that, I am saying I don't "speak" Mp
