The main FOCAS guide in this series is written for the 0i-D and newer, because that’s where the FOCAS Ethernet option is common enough to assume by default. A 0i-C, or anything from FANUC’s lineup older than that, is a different conversation. Some of these machines connect the exact same way. A lot of them don’t, and pretending otherwise wastes an afternoon standing at a panel that was never going to answer. Here’s the breakdown, by what’s actually on the machine.
Why the 0i-C generation is a genuine dividing line
The 0i-C series shipped roughly from the early 2000s through around 2010, before FANUC’s 0i-D took over as the current mainstream control. FOCAS Ethernet, the built-in network interface the main guide walks through, became a much more standard inclusion starting with the 0i-D generation. On a 0i-C, it was frequently an add-on board, an optional Fast Ethernet or Embedded Ethernet card the machine builder could order, not something that shipped standard the way it does now. A lot of 0i-C machines in the field today were never built with that option, because nobody paid for it fifteen years ago when nobody was thinking about connecting a CNC to anything.
That’s the actual reason a 0i-C is a different case, not because the protocol changed, FOCAS itself is the same API, but because the hardware it depends on might not be present.
Option 1: check for the Ethernet board first
Before assuming anything, check the back of the control cabinet, or ask your machine builder or a FANUC service tech, for whether an Ethernet board was ever installed. If it’s there, the setup is identical to the main FOCAS guide: set the IP under the embedded Ethernet parameters, confirm the FOCAS port, power cycle, and run the same three-step connection test. A 0i-C with the Ethernet option equipped is not a special case at all, it’s just an older 0i-D in every way that matters here.
Where “0i-C” sits in FANUC’s own timeline
It’s worth being specific about the generations, because “old FANUC” gets used loosely on a shop floor and it’s not precise enough to plan around. The 0i-B series came before the 0i-C, further back and even less likely to carry a network option. The 0i-C followed it and stayed in production for a long run, which is exactly why there are so many of them still cutting parts today, a serviceable machine that’s old enough to predate a design assumption FANUC didn’t make standard until the 0i-D. None of this affects how FOCAS itself behaves once it’s reachable, a 0i-C with the Ethernet board answers the exact same FOCAS calls a 0i-D does. The generation only matters for whether that board showed up in the machine to begin with.
Option 2: ask about a retrofit board
FANUC and third parties have sold retrofit Ethernet boards for older 0i-C and even 0i-B controls for years, aimed at exactly this situation, a serviceable machine that just never got the network option. Whether one’s available and worth ordering for your specific machine is a conversation with your machine builder or a FANUC-authorized service provider, not something we can promise sight unseen. If FOCAS data matters for a given machine and it’s otherwise in good shape, ask the question before writing the machine off.
Option 3: RS-232, and its limit
A lot of 0i-C controls that shipped without an Ethernet option do have a serial RS-232 port, originally meant for DNC program transfer, not live monitoring. Spall doesn’t have a FANUC-specific serial connector today, FOCAS over Ethernet is the only FANUC path currently implemented, so a bare RS-232 DNC port on its own isn’t a route into Spall. If your control has no path to Ethernet and no retrofit is realistic, this is the dead end for reading the control’s own data directly.
Option 4: the sensed fallback, and why it’s not a downgrade
When FOCAS isn’t reachable, a clamp-on current sensor wired to the gateway’s analog input tells you off, idle, and running from the machine’s own power draw, no controller connection at all, no rewiring of the machine’s electronics. It won’t give you the active program name or an alarm code the way FOCAS would, but it gives you real availability, real downtime, and a real OEE number, calibrated against an actual run cycle rather than left as a guess. See monitoring machines with no controller for the full picture of what that path covers and what it doesn’t.
A lot of shops running a mix of 0i-C and newer machines end up with both paths on the same floor, FOCAS on the newer ones, sensed on the older holdouts, and that’s a perfectly normal fleet, not a compromise. The data lands in the same OEE view either way, labeled by which method produced it.
Quick recap
- The 0i-C generation predates FOCAS Ethernet being standard, it was frequently an optional board
- Check the cabinet or ask your builder whether that board was ever installed, if it was, the setup is identical to any newer FANUC
- A retrofit Ethernet board is sometimes available for a 0i-C or 0i-B, worth asking about before writing off the machine
- RS-232 DNC ports exist on a lot of these controls, but Spall has no FANUC serial connector today, that’s a known gap, not a workaround
- When FOCAS isn’t reachable, a clamp-on current sensor gives real availability and OEE, labeled as inferred from power draw
Not sure which case your machine is in? Send us a photo of the control cabinet and the model number on it, that’s usually enough to tell you before anyone drives out.