How to Set Up FANUC FOCAS on a DN Solutions (Doosan) CNC and Connect It to Spall

Doosan Machine Tools became DN Solutions in 2023. The nameplate changed, the Lynx, Puma, and DNM model names didn’t, and neither did the thing that actually matters for getting data out of one: the control. Nearly every DN Solutions and Doosan lathe and mill on a shop floor runs a FANUC control, most often the 0i-D, 0i-F, or 31i series, wearing Doosan’s own operator panel skin. That FANUC control is what Spall talks to. This guide covers FOCAS setup on that FANUC control, however the machine badge reads.

Before you start This is a FANUC control guide with DN Solutions specifics called out. If your machine’s control badge reads Siemens or Fanuc-Doosan on an older or unusual model, confirm which one you actually have before following these steps, the screens below assume FANUC. You’ll need the FOCAS Ethernet option equipped (standard on the 0i-D and newer), an Ethernet drop at the machine, a fixed IP from your network person, and the Spall gateway on the same network. The gateway reads only. It never writes to the control.

1. Confirm you’re looking at the FANUC screens

DN Solutions puts its own labels on some operator-facing screens, but the network and FOCAS settings live underneath, on the same FANUC menus every other FANUC machine uses. Press SYSTEM, then press the continue soft key (the rightmost arrow) until a screen labeled EMBED PORT shows up (older models may show ETHPRM or ETHER-BOARD instead). If you land on a DN Solutions branded settings page instead, look for a way to reach the CNC’s own parameter screens, sometimes labeled MAINTENANCE or CNC SCREEN, the FANUC menus are always in there somewhere.

2. Set the machine’s IP address

Get a static IP, subnet mask, and gateway address from whoever runs your network first, in the same range as the Spall gateway.

On the EMBED PORT screen, open COMMON:

1. Enter IP ADDRESS, SUBNET MASK, and ROUTER IP ADDRESS, typing each and pressing INPUT.
2. Leave DHCP CLIENT at 0 so the machine keeps a fixed address.
3. Confirm AVAILABLE DEVICE reads EMBEDDED. If it shows something else, use the (OPRT) soft key to select EMB/PCMCIA, then EXECUTE.

3. Turn on FOCAS2 and note the port

Press the FOCAS2 soft key from the same area. If PORT NUMBER (TCP) shows 0, set it to 8193, FANUC’s standard FOCAS port. If a number is already there, leave it and write it down, that’s the one Spall will use. On most 0i-D and newer machines this ships already equipped, since DN Solutions has included the FOCAS option standard for years. Older 0i-C era machines and some early 0i-D units may not have the option installed at all, in which case FANUC or your machine tool dealer can add it, this isn’t something Spall or a shop tech can turn on from a menu that doesn’t exist.

4. Restart the control

FANUC controls apply Ethernet and FOCAS settings on power-up, not live. Power the control off and back on. Skipping this is the most common reason the next step’s tests fail for no obvious reason.

5. Test it before you trust it

Same three checks as any FANUC control, run from a PC on the same network.

# 1. is the machine on the network?
ping 192.168.1.35

# 2. is the FOCAS port open?
nc -vz 192.168.1.35 8193
   -> Connection to 192.168.1.35 port 8193 succeeded!

The real proof is a FOCAS handle opening and returning live data, the control’s model, active program, run state, and part count. Spall’s setup wizard runs that test for you when you add the machine, or use any FOCAS test utility first if you want to confirm it yourself.

If a test fails Ping fails: recheck the IP and cabling in step 2, and confirm you power-cycled the control. Ping works but 8193 is closed: FOCAS2 wasn’t set in step 3, or the option isn’t equipped at all, check with your dealer. A firewall between the machine network and the gateway can also block 8193, ask IT to allow it.

6. Connect it to Spall

In Spall, add the machine, choose FANUC FOCAS as the source, and enter the address and port:

192.168.1.35:8193

Assign the Spall gateway on that network and save. Run state, program, spindle, and part count start flowing within seconds.

What Spall does with this data

Availability. Every hour splits into running, idle, and down straight from the FOCAS run state, whichever badge is on the machine.

Downtime and reasons. FOCAS alarms and state changes catch each stop as it happens. Operators tag the reason, and Spall ranks them into a Pareto.

Production. Spall reads part count directly over FOCAS for target-vs-actual by shift and job. Lynx and Puma lathes running multi-part or bar-fed cycles work the same as any FANUC lathe, see the FANUC multiple part counts guide if one part program produces more than one finished piece per cycle.

Quality and OEE. Availability, performance, and quality roll into one OEE view, each loss ranked in dollars.

One thing worth repeating Spall reads FOCAS, it never writes to the control. The gateway pulls data on your network and sends it outbound over encrypted MQTT. There’s no inbound port opened on your firewall, no VPN, and no changes to programs or PMC, on a DN Solutions machine the same as on a bare FANUC one. Worst case if it can’t reach the machine is a gap in the chart. The spindle keeps running.

Quick recap

• DN Solutions and Doosan machines run a FANUC control under the badge, FOCAS setup is the same as any FANUC control
• Reach the FANUC screens under SYSTEM even if the front panel is styled by Doosan
• Set the IP under EMBED PORT > COMMON, FOCAS2 port = 8193
• Power-cycle the control, then test ping, port 8193, and a FOCAS handle in order
• Add the machine in Spall as a FANUC FOCAS source

Whether the plate on the machine says Doosan or DN Solutions, once FOCAS answers, connecting it to Spall is identical to any other FANUC machine. Repeat per machine, or hand us the addresses and we’ll bring them on together.