Yes and no. Granted, most apps of this type are "loose" parts. However, depending on circumstances and the set up, there is something called LCTE .... You can calculate expected movement and get pretty close... closer than most would think. Takes a good bit of work up front and likely several test runs but it's 'doable'. 5 tenths? Probably pushing it there but with certain geometries, materials and configurations it's possible. Generally speaking though, this app isn't my first choice... but kudos for people still thinking of this stuff....

Huh... ran into him today. I have no issues with him or the company but to each his own... That's too bad though for ya'... They make some serious kickin' tools.... The S-Carbs are a good price which is surprising considering how "proud" SGS was back in the day of Ski-Carbs which were pricey for the time even. Then again, didn't buy much "Skis" after SGS took over the design. I started getting heavy into ARFs and Javelins....

Yep.... Ice Chucking as we've always called it from back in the day. Work very well for that type of app and with general "thin wall, thin floor" type of work. I used to do a lot "contactor" work that I programmed this way. There is a particular fluid that we found that worked with even better holding power and "solid time" (frozen time) than water... I can't remember the name of that stuff now. At room temp, it had the viscosity of "Slime" if any of you guys remeber that product from years ago (kid's toys). It didn't have the expansion problems of water when freezing it... Now I wouldn't necessarily use this for cavity work unless you don't care about the product mixing into your coolant tank or just the fact of machining it away. But pouring it into a "pan" then freezing a thin wall/floor part to it works no problem with minimal issues.

I'm a big fan of SGS S-Carb and yes, the necked back versions work awesome as well. I've use Destiny for a number of years being that they are "next door" to me... Dataflute is a tried and true tool. Codebreaker's test is interesting but didn't say which model Dataflute was being tested... Helical is also a great tool and just so happens that the owner/founder of it is also the same guy who founded Dataflute "oh, so many years ago".... Another one of my favs for this app.... SwiftCarb (by Newtech) and I should mention some good luck with GW Schultz tools as well... ... and Robb Jack.... Hanita..... Harvey .... Weldon.... ..... Man, there's quite a few good ones out there these days....

How many digits are you allowed in your s/n? We do this same thing on our Makino cells right now. You can set it up like Jim and James mentions or.... What we do is use the first digit of a s/n as an 'identifier' of what machine it ran in as well. This way, the s/n's can stay consecutive (at the very least 'unique') and this also tells us what machine ran the part for traceability without having to keep a log of any sort (from using the above mentioned method). This "first digit" machine number uses a dedicated variable number at each machine to pull from. The rest of the digits is just a simple macro for the counter and number engraving.

... thanks for the correction. I don't know where my head was on that one...

A 400mm pallet isn't that heavy and changing them on a Mazak (or any HMC I can think of) is breeze. To cart it around, you can buy a steel part cart from Grainger/MSC type of thing. Just get one that's got a high enough rating to handle your set ups as well. Most 400mm machines can only lift around 800-1000 pounds of set up so add that to your pallet weight and get a cart. I can roll around 630mm and 800mm pallets the same way so I'm sure a 400mm is no sweat. As for lifting them in, a HCN4000 is low enough so you could use a cherry picker but that is a PITA. Doesn't roll around very well with a dangling weight and grime on your concrete floor can fight with you. A "Big Joe" as mentioned is a nice alteranative or any small forklift. Jib cranes work great as well and if you can place it right, have it work for 2 machines. Jib cranes are pretty cheap too and can be bought off of eBay or something for a very low price.

I think the "quickest" can be debated.... Certainly you can edit code but you have to get in there and do that. For HDD or DS programs, you'd have to download, edit, reload, restart.... You can jump and search inside of HD so for me, this is the quickest and I don't have to change any codes or programs...or worry that me (or someone else) left something behind to mess up the next part. And I hate having a "junk" program simply to restart and finish..... But that's me....

This is on a FANUC control???? Why edit anything in the program? You can use the search function to restart a program anywhere. No need to edit, delete, insert GOTO or anything else. Just write down the line where you stopped at. Then, I just simply go into single block mode at the start of the toolpath, ... single block the program to pick up some codes like work offset, spindle on, coolant on, Tool length, Lookahead.... whatever you need. Then take the machine out of MEMORY mode and go into a HANDLE/jog mode and without pressing anyother keys, type into the control the line information you want to jump to and press the DOWN arrow key (or search down button on i controls), put the control back into MEMORY mode and hit the start button. This is called Manual Interrupt. All FANUC controls can do this.... at least every one that I've used in the last few decades through numerous MTBs. It only takes about 2 seconds and you don't have to worry about leaving behind edits in a program. With Manual interrupt, you jump into sub routines, use toolpaths paths from a totally different tool.... all kinds of stuff. The only thing to be careful of is to not move any of the machine axes unless you need to because the control is not tracking the any changes to axes position in Manual Interrupt. This is another way you can take a "deeper" cut without reprogramming.

My guess... "G" in this case should be referencing a Sliding Fit class. This is a metric standard. But G doesn't go to 11 on scales I've seen (I thought it stopped at 10). It could be that they mean a H11 tolerance or they're mixing up IT Grade with the G class and basically it's saying "G" fit with IT 11 grade for deviation. Take a look at these... ANSI B4.2, ISO/R286, ISO 1829

quote: Couldn't you make a separate custom coolant option to turn them all on at once? No because I don't want to (I think I've been saying that.. ) ANYHOW.... I figured out how to string it with the existing logic. Just edit the output in "pcant_out" in the coolant section of it: From: pbld, n$, *scoolantx, e$ Change to: *scoolantx This will now string the coolant M-codes. Only need to place a "e$" with the string line in ptlch or place the pcan, pcan1, pcan2 where it will pick up the end block for posting. Now I can turn on ANY combination of coolant using the existing menu.... Haven't run into any other cantext issue with it.... so far anyway...

The machine/control is no problem... they'll take up to 3 m-codes. I'm looking to see if there's a way to edit the post using X style coolant so that whatever is selected will post on the same line. I was looking into somehow tweaking pcan1, pcan2 and pcan3 but it looks like they're also controlling other canned text which may end up messing up other commands? So based on this menu: The code will output all the coolant commands on the same line. If I we're to select only "Flood" and "Shower", then only those 2 will post but on the same line of code . As I mentioned, on all MC versions up to now, I've done this by creating different command lines based on the number of variations I could command (like Flood only, ... Flood and shower only.... TSC and Shower only... TSC only .... etc, etc). I'm looking to avoid writing the post like this.....

This is for X style coolant commands... (did some searching but couldn't find what I was looking for) Is there a way to have all the coolant codes post on the same line? For example: Instead of: M8 M26 M754 Have it post: M8M26M754 In V9 and earlier, I used just have all these different options/arrangements for every which way possible. I could do the same thing in X but I'm hoping for something "flexible" with existing logic. (MPMaster type post)

quote: The Integrex was sold to do a job and typical Mazak, it couldn't. Yeah... I have the same problem with Toyoda... it was sold to do a job and typical Toyoda, it couldn't. I remember Chris' deal with that Integrex. One thing I totally agree with Chris about is the downfall and crappy sales "engineers" and apps guys that are in the business. Not just for Mazak but it's some kind of plague for all MTBs... I know our Integrexes don't have the issues Chris had and can hold the true positions that he was looking for all day long. Funny how the world works... The only thing to do there is do what he did... get the anchor out of there... quote: [2] years later I was very interested in when that half hour was to start. quote: What a maroon.... ROFL I've made that comment many times before with factories.... and yes, maroon...

I generally program with respects of the drawing datums (not always though for center of rotation) but this subject certainly can go back forth all day long with opinions... Another option I like doing is using 3D Coordinate Rotate (G68 in 3D). I use this on Mazak eVerticals. I can use one offset at the center of the table/part but still use code that follows the print making it easy for a machinist to follow. G54.2 works well also but I use for different reasons. I run many parts as center of rotation but most of them don't have the datums at center. The backfiguring for adjustments can get quite brutal especially on parts with mulitple primaries. Certainly lots of ways to move parts & offsets around though huh? G10, G52, G53(through G10), G54.2, G68, G68 G92, macros.....

Which Integrex type are you looking to replace the old one with? There's a 'few' versions for these. The Mark IV (traditional type), the e-Horizontal (Lathe based with 5x), and the e-Vertical (mill based 5x with VTL type turning).

Did that... they're all there on the list.... still doesn't pull the color/font settings for NC code. It only works for ".nc" file extensions. I have to manually change it every time for other files. Cimco editor doesn't drop this... Maybe I just need to switch back and don't use the Mastercam Editor since it doesn't work...

Permissions was the culprit. No more errors from either MCX or the editor. Only one left though.... quote: Another issue I've had for a long time using MCX editor: Why won't the "window properties" stick? We have a few different NC file extensions being used and even though the other extensions are listed, it won't open the window using the NC view. I have to change it all the time on the Language/Tab setting. Any .NC file is fine, only other extensions on the list doesn't work. What's the deal here?

Thanks Scott. Thought about the privileges on Friday but... it was the weekend. I'll have it changed... Anyone with any ideas about the other two issues (MCX Editor issues)?

Had X4 installed and I'm getting some strange errors that I'm not sure of the fix...(see pics) Tool filter error: comes up when I OK to close window ... and now, I also get an error changing parameters for the MCX editor... Another issue I've had for a long time using MCX editor: Why won't the "window properties" stick? We have a few different NC file extensions being used and even though the other extensions are listed, it won't open the window using the NC view. I have to change it all the time on the Language/Tab setting. Any .NC file is fine, only other extensions on the list doesn't work.

So Toyoda may have stuff of their own written and judging by Tinhman's actions it appears that it's adjustable by changing #5xx numbers/values. I'd say just try changing the #505 value and see if it sticks and corrects your problem. Make notes of your changes so in case something isn't looking right, you can get back to it. The skip signal should keep you protected. My Toyoda's have the Renishaw programs installed so I don't adjust in this manner...

Tinhman, Many installs will have common variables identified to be able to show what the settings are/will be for current cycles. Are you saying that by changing #500 numbers your probing will act differently? I can view those as well on my Toyodas (among many other machines) but changing them doesn't affect the actual running cycle since the local variables being set on the actual macro call line (or system default which is a written variable) will overwrite them (which is what Mick is wondering about). (this is based on actual Inspection Plus installations. I have seen "custom" software written that acts the way you describe)

quote: We didn't have a Renishaw guy set ours up. It was set up at the Toyoda factory afaik :/ Even so, it's probably still running Renishaw's Inspection Plus macros. Toyoda should've given you a programming book for it. But, as Tim said, generally these macros use a "Q" value for overtravel distance you can write in (with 10mm being the default XY skip distance and 4mm in Z).

What?? Getting stranger by the minute there... Should be no difference between M05 and M5 for the machine. Sure the code wasn't maybe MO5 by chance? (as in the letter O and not a zero)? Glad you're fixed up though....

You're right, if your machine is set up like that, it will do that. You'll have to have the M131 on a different line. If you wired the M131 as a M code, you can get around that. Or, if you did not get the pressure switch option, it would be wired only. It's looking at a couple of "R" outputs. I remember now too, I have a couple switches my eMachines are looking at so I had to split off the M131 as well... The DEATH parameter Rick is talking about... F114.1