lmxopcua/docs/Driver.FOCAS.Cli.md

otopcua-focas-cli — Fanuc FOCAS test client

Ad-hoc probe / read / write / subscribe tool for Fanuc CNCs via the FOCAS/2 protocol. Uses the same FocasDriver the OtOpcUa server does — PMC R/G/F file registers, axis bits, parameters, and macro variables — all through FocasAddressParser syntax.

Sixth of the driver test-client CLIs.

Architecture note

FOCAS is an in-process driver. The pure-managed WireFocasClient speaks the FOCAS2 binary protocol directly over TCP:8193, removing the Tier-C process-isolation split that the historical P/Invoke + out-of- process Host arrangement required. The CLI loads FocasDriver with WireFocasClientFactory and talks to the CNC without any native components.

A dev-friendly mock is available — start tests/Drivers/ZB.MOM.WW.OtOpcUa.Driver.FOCAS.IntegrationTests/Docker/docker-compose.yml and point --cnc-host at localhost for end-to-end CLI exercises without a real CNC. See drivers/FOCAS-Test-Fixture.md.

Build + run

dotnet build src/Drivers/Cli/ZB.MOM.WW.OtOpcUa.Driver.FOCAS.Cli
dotnet run --project src/Drivers/Cli/ZB.MOM.WW.OtOpcUa.Driver.FOCAS.Cli -- --help

Or publish a self-contained binary:

dotnet publish src/Drivers/Cli/ZB.MOM.WW.OtOpcUa.Driver.FOCAS.Cli -c Release -o publish/focas-cli
publish/focas-cli/otopcua-focas-cli.exe --help

Common flags

Every command accepts:

Flag	Default	Purpose
-h / --cnc-host	required	CNC IP address or hostname
-p / --cnc-port	8193	FOCAS TCP port (FOCAS-over-EIP default)
-s / --series	Unknown	CNC series — Unknown / Zero_i_D / Zero_i_F / Zero_i_MF / Zero_i_TF / Sixteen_i / Thirty_i / ThirtyOne_i / ThirtyTwo_i / PowerMotion_i
--timeout-ms	2000	Per-operation timeout
--verbose	off	Serilog debug output

Addressing

FocasAddressParser syntax — the same format the server + FocasTagDefinition use. Common shapes:

Address	Meaning
R100	PMC R-file word register 100
X0.0	PMC X-file bit 0 of byte 0
G50.3	PMC G-file bit 3 of byte 50
F1.4	PMC F-file bit 4 of byte 1
PARAM:1815/0	Parameter 1815, axis 0
MACRO:500	Macro variable 500

Data types

Bit, Byte, Int16, Int32, Float32, Float64, String. Default is Int16 (matches PMC R-file word width).

Commands

probe — is the CNC reachable?

Opens a FOCAS session, reads one sample address, prints driver health.

# Default: read R100 as Int16
otopcua-focas-cli probe -h 192.168.1.50

# Explicit series + address
otopcua-focas-cli probe -h 192.168.1.50 -s ThirtyOne_i --address R200 --type Int16

read — single address

# PMC R-file word
otopcua-focas-cli read -h 192.168.1.50 -a R100 -t Int16

# PMC X-bit
otopcua-focas-cli read -h 192.168.1.50 -a X0.0 -t Bit

# Parameter (axis 0)
otopcua-focas-cli read -h 192.168.1.50 -a PARAM:1815/0 -t Int32

# Macro variable
otopcua-focas-cli read -h 192.168.1.50 -a MACRO:500 -t Float64

write — single value

Values parse per --type with invariant culture. Booleans accept true / false / 1 / 0 / yes / no / on / off.

otopcua-focas-cli write -h 192.168.1.50 -a R100 -t Int16 -v 42
otopcua-focas-cli write -h 192.168.1.50 -a G50.3 -t Bit -v on
otopcua-focas-cli write -h 192.168.1.50 -a MACRO:500 -t Float64 -v 3.14

PMC G/R writes land on a running machine — be careful which file you hit. Parameter writes may require the CNC to be in MDI mode with the parameter-write switch enabled.

Writes are non-idempotent by default — a timeout after the CNC already applied the write will NOT auto-retry (plan decisions #44 + #45).

subscribe — watch an address until Ctrl+C

FOCAS has no push model; the shared PollGroupEngine handles the tick loop.

otopcua-focas-cli subscribe -h 192.168.1.50 -a R100 -t Int16 -i 500

Output format

Identical to the other driver CLIs via SnapshotFormatter:

• probe / read emit a multi-line block: Tag / Value / Status / Source Time / Server Time. probe prefixes it with CNC, Series, Health, and Last error lines.
• write emits one line: Write <address>: 0x... (Good | BadCommunicationError | …).
• subscribe emits one line per change: [HH:mm:ss.fff] <address> = <value> (<status>).

Typical workflows

"Is the CNC alive?" → probe.

"Does my parameter write land?" → write + read back against the same address. Check the parameter-write switch + MDI mode if the write fails.

"Why did this macro flip?" → subscribe to the macro, let the operator reproduce the cycle, watch the HH:mm:ss.fff timeline.

"Can I reach the CNC on TCP:8193?" → probe against any host. A BadCommunicationError means the wire client couldn't open a socket (firewall / wrong host / FOCAS Ethernet option unlicensed on the CNC). BadDeviceFailure after a successful connect means the CNC is rejecting the session setup — check the CNC's FOCAS option and password settings.