Working With the Mazatrol Fusion 640 T Controller
The Fusion 640 T is Fanuc's third-generation Mazatrol controller, built around the M Series architecture. It handles multi-axis turning with live tooling and sub-spindle work, which means you'll be programming both main and sub spindle cycles in the same part program. Most shops running these machines got them between 2012 and 2018, and they're still doing decent work in production environments. The controllers hold up well if you keep the backup batteries fresh and don't ignore the absolute position alarm on the sub-spindle axis. I need to be straightforward about where to find documentation. Fanuc doesn't put their manuals on public websites anymore. You go through the Fanuc website support portal, log in with a customer account tied to a serial number, and download what you need. If your company doesn't have a Fanuc account set up, that's the first thing to sort out. Some machines came with a CD or DVD in the control cabinet back in the day. Check the electrical panel area — there's usually a paper file folder clipped inside the door. The manuals inside are often yellowed but legible, and they predate the current digital versions. I've found revision differences between what's on the CD and what's available online, so it pays to verify against the actual control on your machine by checking the software version in the SYSTEM screen.
Mazatrol Fusion 640 T Manual
Inside the official manual you'll find the Mazatrol language reference, parameter tables, and the programming examples specific to the T configuration — that's the twin-spindle turning variant. The Mazatrol side of things is different from standard G-code. You write macro-level instructions and the control translates them into the underlying motion. It's faster for setup because you describe the operation rather than the toolpath. But it hides a lot of what's actually happening, which becomes a problem when something goes wrong mid-cycle. Here's something the manual doesn't make obvious: the Mazatrol ON PART and ON TOOL sections compile into G-code at run time, not at save time. So if you change parameters or add an option package after your program was written, the compiled output can shift without any warning in the Mazatrol editor. I ran into this on a part where the sub-spindle catch timing drifted by roughly 0.3 millimeters after a controller option was added. The Mazatrol program looked identical, the simulation in the editor passed clean, and the machine started dropping parts on the sub-spindle side. The fix was pulling up the compiled G-code screen and comparing it to the previous shift's output. Once I saw the difference in the Y-axis compensation value that the Mazatrol compiler had adjusted, I went back and locked that parameter. That's the kind of thing nobody tells you until you've already lost a batch. The manual covers the basic structure — MAIN PART, SUB PART, TOOL section, and the sequence of operations. You define the stock shape, the operations in order, and the control fills in the tool moves. For turning centers with twin spindles, the SUB PART is where you tell the control what happens after the part transfers. If you're doing offhand grinding or knurling, those operations need to be in the right section or the machine will try to execute them on the wrong spindle. The manual has examples for most common operations, but custom ones require you to understand what's happening under the hood anyway.
On the G-code side, the Fusion 640 T runs the same code as other M Series controllers. You can write pure G-code programs alongside Mazatrol ones, which is useful when Mazatrol can't handle a particular cycle. The canned cycles for boring, threading, and facing are all there. Live tooling with C and Y axis requires the appropriate option package, and the parameter tables in the manual show which options are needed for each feature. If your machine doesn't have Y axis on the live tool station, trying to use G-code Y-axis commands will just trip an alarm. The manual lists the alarm codes, but again, it doesn't emphasize that some alarms only appear under specific option combinations. Parameters are where most people get stuck. The 640 T uses the same parameter numbering scheme as the broader M Series line, but certain ranges are dedicated to the Mazatrol compiler settings. Parameter 3100 series controls Mazatrol execution behavior, and if you tweak anything there without understanding it, you can change how the compiler interprets your operations. I've seen someone disable the automatic tool length compensation in the compiler parameters, which made every Mazatrol part program skip the H offset on the first tool call. The parts came out to length, the alarm didn't trigger, and it took two shifts to figure out what was happening because the tool table screen looked normal. Network connectivity on the 640 T is another area the manual barely scratches. You can send and receive programs over Ethernet using the FOCAS library or the built-in DNC mode. The DNC mode is fine for single-part uploads, but if you're pushing whole job files with offsets and tool data, the FOCAS route is more reliable. Several shops run automated program management systems that connect directly to the controller. Setting that up requires the right option package and some configuration in the Ethernet parameters, which are documented but not always easy to find in the manual index.
Get the Full Details
One thing the manual omits entirely is the behavior of the controller during power transitions with dual spindles. When the control restarts, the sub-spindle absolute position needs to be re-established. If you skip the reference return on the sub-spindle after a power loss, the transfer mechanism will move to the wrong position and you'll either crash the part or damage the catch mechanism. The alarm table mentions this, but it's buried in the general reference position section. I'd recommend putting a sticky note on the inside of the control cabinet door reminding operators to run the sub-spindle reference return after any power-down. That's cheaper than replacing a damaged part transfer unit. For actual Mazatrol programming, the workflow is straightforward once you understand the structure. You start with the MAIN PART definition, set the stock dimensions, define the operations you need — facing, OD turning, boring, parting, threading — and the control generates the toolpaths. The ON TOOL section lets you specify tool geometry, compensation, and feed override limits per tool. The SUB PART mirrors the MAIN PART structure for the second spindle. Operations defined in the SUB PART run on the sub-spindle after transfer. Mixing up which operations belong in which section is the most common error I see, and it wastes time on the floor because the machine will alarm or produce scrap before anyone realizes the programs are swapped. The system screen shows real-time tool position, cycle time, and alarm history. Use the alarm history screen to track recurring issues. The 640 T stores several pages of recent alarms, and if you're seeing a particular alarm come back after a clear, that usually means there's a mechanical or wiring issue, not a program issue. The manual lists the alarm meaning, but the diagnostic procedure is in a separate maintenance manual that isn't always included in the standard documentation package. Check with your Fanuc rep or look for the SRX Series/B Series maintenance manual online through the proper channels.
Backup and restore is something you should set up before you need it. The 640 T can back up the entire controller — parameters, programs, macros, offsets — to a USB drive or over the network. The process is documented in the manual under the data management section. I'd suggest doing a full backup every time you make a significant change, and keeping at least three generations of backups. The controller can fail without warning, and losing a week of work because you never backed up is avoidable. The manual doesn't emphasize the USB backup method enough, partly because older controllers used floppy drives and the documentation sometimes lags behind. If you're new to Mazatrol programming, the learning curve is steeper than standard G-code because you're working at a higher abstraction level. You need to understand the machine's mechanical capabilities and the control's limitations to write efficient Mazatrol programs. The manual includes operation examples, but they're generic. Real-world programming requires judgment about sequence, tool selection, and how the control will interpolate between operations. Watching an experienced programmer work through a complex part on the 640 T is more educational than reading any section of the manual. But once you understand the compiler behavior and the parameter interactions, Mazatrol can cut programming time significantly compared to writing equivalent G-code from scratch. The manual itself runs several hundred pages across multiple volumes — one for Mazatrol programming, one for G-code programming, one for parameters, and one for maintenance. Make sure you have all the volumes, not just the programming guide. The parameter volume is where you'll find the tables you need when something doesn't behave as expected. The maintenance volume covers servo tuning, ball screw compensation, and spindle diagnostics. Those topics aren't in the programming manuals, so if you're trying to troubleshoot a mechanical issue using only the programming guide, you'll hit a wall quickly.
There are also third-party resources and forums where people share Mazatrol programs and troubleshooting tips. The Fanuc community forums have a section for Mazatrol programming, and while the official support is reliable for specific issues, the peer discussion often surfaces edge cases the manual never addresses. One thread I remember discussed an issue where the 640 T would occasionally reject a valid Mazatrol program if the tool number exceeded a certain threshold in combination with a specific parameter setting. The fix was adjusting parameter 1815 bit 3, which controls the maximum tool station count. The manual mentions the parameter but doesn't link it to program rejection behavior. For download access, the official route remains the Fanuc website with proper credentials. If your company doesn't have an account, contact your Fanuc sales representative or authorized distributor. They can set one up and provide access to the current manual revisions. Avoid unofficial sources — the manuals are technically straightforward, but modified versions circulating online may have incorrect parameter values or outdated alarm codes, which is worse than no manual at all when you're debugging a live machine. What tends to surprise people is how much the Fusion 640 T shares with the later Fusion 30 and Fusion 35 controllers. The Mazatrol language syntax is nearly identical, and many programs written for a 640 T will run on a 35 with minimal adjustment. The parameter sets diverge in the I/O and servo sections, but the programming side overlaps significantly. If your shop has mixed Fanuc controllers, learning the 640 T manually gives you a foundation that transfers across the product line.
Another practical note: the 640 T's screen resolution is lower than newer controllers. The graphics are functional but not especially sharp, and the touch panel response can feel sluggish compared to the F30i or F32i panels. If you're programming on the control itself, consider using a keyboard and mouse through the USB port or the serial-to-USB adapter. Typing Mazatrol commands on the soft keyboard eats time and increases typos, which then take longer to find in the compiled output than in raw G-code. The manual also covers the tool management system, which tracks tool life, wear compensation, and automatic tool replacement. This is optional and requires the appropriate software package. When configured correctly, the system can run a full production shift without operator intervention on tool changes. But the setup is finicky — tool offset tables need to be consistent between the manual entry and the automatic offset records, or the compiler will throw a mismatch alarm during the Mazatrol ON TOOL section execution. I've spent more time fixing tool offset inconsistencies on the 640 T than I have on any other Fanuc controller I've worked with, and it's almost entirely preventable with a disciplined tool presetting procedure. At the end of the day, the Mazatrol Fusion 640 T is a mature platform that handles complex turning jobs efficiently when it's set up correctly. The manual is comprehensive but not always easy to navigate, and some of the most important details are scattered across volumes or implied rather than stated explicitly. The best approach is to keep all the manuals in one place, maintain a clean backup schedule, and develop the habit of checking compiled G-code when Mazatrol programs behave unexpectedly. Those two habits alone will save you more time than any single section of the documentation.
