Yeah, about the tutorials! They make it look super easy, but they are missing about 10 crucial steps in between each to actually use the software. We had our ABB distributor come in for a couple of days and he gave me some pointers and tips in RobotStudio. Otherwise I would not have been able to use it based on their tutorials. I would suggest taking their class or other training. There is a pretty decent forum for RobotStudio/ABB.

I use RobotStudio, probably not anywhere near the extent of it's capabilities but I do use it. We only do machine tending with our robots so no path programming is needed. Our programs are very algorithm driven so I just write the rapid code myself. However I do use RobotStudio to simulate and do layout/reach studies. I am in the process of adding the Safemove zones in robot studio for further protection against crashes. Just being able to real time connect to the robot to check IO and even program is awesome. The code editor has predictive text and intellitype like VisualStudio or other modern programming IDE's.

I understand the reasoning for the cutter. The forces are towards the solid body making it stronger. However, instead of positioning in X and cutting in Y, couldn't they just reorient the blade so you position in Y and cut in X? Especially in MT machines with lots of Y travel.

I do not use Mcam anymore so I can't help you get the post but to help clarify what you are looking for I have a few questions. A fixed point in space does not have vector information by itself. Are the points you are wanting extract on a surface that can use the normal as vector definition? Also, The code sample you show has X,Y,Z,0,0,0,0, I am assuming this quaternions for vector definition? I know there are posts that can output Euler angles normal to surface for points for 3D comp, I am sure it could be converted into quaternions.

I did not look over your code, but short answer, yes it can be used with probing. I helped a customer with a casting that required cross features of a cast bore to be controlled to the center line of the cast bore. We probed the bore for XYZ at B0 then used the rotation macro to update the work offset for B90 cross work.

Word of caution when planning on using dynamic turning. Check the back clearance angles of the inserts you plan to use. If your feedrate is high enough and the back angle is minimal you can get a condition where you are pushing material with the face of the insert in addition to the cutting face. this will "pop" and insert quickly. That is why threading tools for fast pitch threads actually tilt the insert.

Set your post or programs to force the X and Y position of the first drilling location in the G81 (or other) canned cycle call line. That way if the machine ran out of travel in the G0 positioning move it will alarm on the G81 call versus drilling in the wrong location.

Todd, you are correct in your comments. The XMPS will be a number very close to 0 and the ZMPS will be about half the table size in inches. Also if you do prefer to program to the center of the table there is a document that explains setting the Z0 to the center of the table. It simplifies work offsets as they should be close to 0 for X and Z after making the changes. Your Okuma dist should be able to get you a copy of the document if interested.

What type of printer are you planning to use, Do you have one that will take serial data and print it. I have never done that before. I have always output to a file and then printed the file if you want a paper copy.

What are you trying to print. Are you needing serial communication to another device or are you just wanting to collect data in a text or CSV file?

You can name local variables as you choose with a few rules. They can have 4 characters max and cannot start with N, V, S, O. They cannot be named the same as any other mnemonic calls or math functions, MOD, ATAN, etc. If they contain numbers and letters they have to be letters first, then numbers, example; XP1 is valid whereas X1P is not. There is a limit of 127 active local variables in a program. They are only valid in the program (local) that they are called, meaning if you declare a local in your main, then go into a sub, it will not be declared in the sub. I try to name them as something that makes sense. for a counter I may use CNTR. for time I may use TIME. For a position I may use XPS1 or ZPS1, etc. To declare you need to give it a value, TIME=0, XPS1=10.556, etc.

Our parts are simple as far as geometry and machining, but they do take enough tool variation that we could benefit from the ATC capabilities of a B axis machine. We have quotes on a Multus B300II, Mazak J300, and we are waiting on a quote for a DMG CTX.

I will be one to praise the benefits of a true Y axis, however some of the needs will vary based on your parts. For example, We are getting ready to buy a B axis millturn. Most of our parts are currently run in compound Y axis machine that I have never used the Y axis on. Everything is done is C-X contouring mode. For us the need for a B axis millturn is about having more tools setup and more clearance between the chuck and tools.

I'm not sure about Mazak but I know in Okuma or Fanuc controls you can send the angle command to the TPC-Jr using RS232 (DPRINT or PUT/WRITE). This makes the TPC-Jr act as a slave and you do not need to program it or be concerned over mid-program restarts.

It is a new option that has not been around very long. I just learned of it late last year. I do not know how long they were working on it.

Essentially DFO does the same thing as CALL OO88 but with some differences. As Greg said, CALL OO88 only updates the XYZ offset position so you still need to post the rotary moves. DFO is modal and dynamic. Once G605 is active any rotary move will automatically update the XYZ offset position. The one limitation is that you have to post rotary moves by themselves, no linear on the same line. The biggest advantage and need for developing the DFO was being able to use it in conjunction with slope machining. If you have a casting or other organic part that you need to align the coordinate system to using slope, you can also turn on DFO to maintain that alignment for other rotary positions.

PM me your email address and I will email you the MU series 5 axis training manual. It gives a more simplified explanation of the auto tuning use than the full manual.

DFO in an Okuma is G605. Not the same thing as TCPC (G169). G605 is used for 3+2 positioning. G169 is used for full five axis cutting. Did you run the 5 axis auto-tune to make sure the rotation centers are set correctly?

Writes to RS232 or to a text/CSV file. I use it all the time to record work offsets, load monitor data, etc.

M73/M74/M75 determine how many cuts by formula. Each M code is a different formula. M73 will give the least cuts, M75 will give the most. M32 is leading edge cutting, M33 is alternate edge cutting, M34 is trailing edge cutting.

Mod returns the remainder after division has been processed. IE; #501=10 #502=4 #500=MOD[#501/#502] will return #500=.5

Most MTB's have some sort of robot interface that allows for remote program select. This is what cell controllers and robots use to load programs. Some of them are Ethernet IP and others are oldschool BCD IO. I know for sure Fanuc and Okuma are add on options. I don't know what Haas has but I would guess they have something available.

G110 and G111 have to do with CSS speed control for the spindle. G110 puts turret A position in control of CSS. G111 puts turret B in control.

VOPRB[2] is an 8 bit (0-7) parameter. Bit seven determines whether or not buffering is on. For buffering to on, bit seven needs to be a 0. To always set it to be on you will need to do some logic checking. IF [VOPRB[2] LT 128] NSKP1 VOPRB[2]=VOPRB[2]-128 NSKP1 Also, for reference, you can check the VDIN variable to act as a one line look ahead limit in a program. VDIN[****] (where **** = 1000-1004) are system clocks for days, hours, minutes, seconds, milsec. If you write any one of those values to a variable the NC will not process that line of code until it reaches it in actual execution. This will act as a look ahead buffer. Example; TIME=VDIN[1001]

Mastercam or TopSolid? I know a lot of the Mastercam MT posts are relatively new.