As do I. Anyway, how are calling the surfaces from solids command? Are you using the external apps mananger? ExternalAppsManager.PostFTCommand("sld_convert_to_surfs")

We moved all of our Mastercam files into our PDM system. This had a few benefits. One is that the files are saved to a local drive, but still synced to the server. PDM also requires that files be checked out and you can see who else has it checked out and is working on it. Lastly, there is a revision history and you can quickly see any old version. I think this has been a huge improvement for even our small programming department.

Hello all, Thanks to everyone who has provided any assistance to me. I have been making progress (believe it, or not) and I am starting to grasp some of the more simple concepts of Visual Basics and the Masteram API. I am trying to create surfaces from a single solid that has been selected. The surfaces are created, but a prompt appears on the screen "Set options, press <ENTER>, Apply, or OK". I wish for my project to enter the appropriate response and keep moving. Can someone point me in the direction I need to go? Again, all help and advice is much appreciated. Steven

There is a hack to enlarge the QAT - but it enlarges all QAT's on your computer. And it's not the best in the world - a small change makes a big difference. Do a search here as I posted it up a few years ago now. Bad luck CNC picking the wrong toolkit but glad they have seen sense and are building in flexibility to remove/change/alter what half the people have been moaning about.

99.9% sure Smart is Samsung Machine rebranded.

I think that entire page is a decimal error

Contour with Ramp would be how I would approach this. Get lead in/out and done. I would do a full pass a depth also.

yes.. running a Logitech K840 at work and a DasKeyboard at home once you get used to a mechanical keyboard, the regular ones suck They are like typing in a bowl of oatmeal

It is a free tool and use as is. If you want to pay the developer to help you then email Günther and I am sure he will be glad to help you for the right amount of money. Not trying to be ugly, but he has offered this for free for many years and never once asked for anything in return.

Here we are 3 programmer and everything is shared from a single network drive, so everyone use the same files for Machines, posts and tools

Looking to do more advanced milling on a lathe. The c-axis tool paths are pretty self explanatory. I dont have the C and Y axis mill turn book, but I can guess it only covers basic c-axis tool paths. I am looking to get more advanced, like possibly surfacing and stuff on a lathe with milling options. Do I tackle this just a mill would? Would I need an advanced mill book then? Any recommendations?

Ok so we use Okuma machines and we use what we call "OSET1" values, which are the distances from machine zero to the WCS coordinates. Below is an example of the outpu I would like to see. The "X", "Y", and "Z" coordinates are from the tool plane box in Mastercam. I edited them in for now, but I would like to output them using the toolplane values automatically. This is an example of the main program: (**** 59330AR ****) (**** CNC10 ****) (**** FIXTURE LAY OUT WORK OFFSETS ****) (**** OP20 ****)(**** OP10 ****) (**** 41, 11 ****)(**** 40, 10 ****) (**** 31, 21 ****)(**** 30, 20 ****) (**** POCKET ON/OFF ****) NPKT CALL OPKT (**** PROBING ****) CALL OSET1 <-------------------------------------------------This calls out the WCS sub. NA1 CALL OT01A ( BOTTOM OD - OP10) NB1 CALL OT01B (CORD PLATE - OP20) ......... M30 This is the Sub for WCS. OSET1 (**** WORK OFFSETS ****) (**** BOTTOMS - OP10 ****) (**** 10 ****) VZOFX[10]=15.8492 VZOFY[10]=4.8288 VZOFZ[10]=3.1454 RTS ************************************** This is what I put into my post, I was trying to use misc, integers and reals to drive this. if mi10$ = ten, [ fixtrack1 ] else, if mi10$ = twenty, [ fixtrack2 ] else, if mi10$ = thirty, [ fixtrack3 ] else, if mi10$ = forty, [ fixtrack4 ] ***************************** I inserted this into the peof$ area in order to get the output after the M30. fixtrack1 [ pbld, "OSET1", e$ pbld, "VC110=1(SETS ACTIVE PALLET)", e$ pbld, ,"VZOFX[10]", mr1$, e$ pbld, ,"VZOFY[10]", mr2$, e$ pbld, ,"VZOFZ[10]", mr3$, e$ ] pbld, e$ pbld, e$ fixtrack2 [ pbld, "OSET2", e$ pbld, "VC110=1(SETS ACTIVE PALLET)", e$ pbld, ,"VZOFX[20]", mr1$, e$ pbld, ,"VZOFY[20]", mr2$, e$ pbld, ,"VZOFZ[20]", mr3$, e$ ] pbld, e$ pbld, e$ fixtrack3 [ pbld, "OSET3", e$ pbld, "VC110=1(SETS ACTIVE PALLET)", e$ pbld, ,"VZOFX[30]", mr1$, e$ pbld, ,"VZOFY[30]", mr2$, e$ pbld, ,"VZOFZ[30]", mr3$, e$ ] pbld, e$ pbld, e$ fixtrack4 [ pbld, "OSET4", e$ pbld, "VC110=1(SETS ACTIVE PALLET)", e$ pbld, ,"VZOFX[40]", mr1$, e$ pbld, ,"VZOFY[40]", mr2$, e$ pbld, ,"VZOFZ[40]", mr3$, e$ ] ************************************** This is the code output I am getting, the coordinates aren't coming out. I defined the constants. OSET1 VC110=1(SETS ACTIVE PALLET) VZOFX[10] = VZOFY[10] = VZOFZ[10] = OSET2 VC110=1(SETS ACTIVE PALLET) VZOFX[20] = VZOFY[20] = VZOFZ[20] = OSET3 VC110=1(SETS ACTIVE PALLET) VZOFX[30] VZOFY[30] VZOFZ[30]