Group all 69 projects into category subfolders under src/ and tests/ so the Rider Solution Explorer mirrors the module structure. Folders: Core, Server, Drivers (with a nested Driver CLIs subfolder), Client, Tooling. - Move every project folder on disk with git mv (history preserved as renames). - Recompute relative paths in 57 .csproj files: cross-category ProjectReferences, the lib/ HintPath+None refs in Driver.Historian.Wonderware, and the external mxaccessgw refs in Driver.Galaxy and its test project. - Rebuild ZB.MOM.WW.OtOpcUa.slnx with nested solution folders. - Re-prefix project paths in functional scripts (e2e, compliance, smoke SQL, integration, install). Build green (0 errors); unit tests pass. Docs left for a separate pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5.7 KiB
focas-mock
focas-mock is a Python TCP mock server for testing higher-level FOCAS clients without a real FANUC control.
The project is built from two inputs:
- The 64-bit FANUC-related DLLs downloaded from Ladder99/fanuc-cnc-api
- The vendor
fwlib.csinterop file, used as the callable surface reference
The DLLs are not reimplemented at the binary ABI level. Instead, this project extracts their export tables, builds per-version capability profiles, exposes a JSON-over-TCP mock API, and implements the targeted native FOCAS Ethernet wire protocol used by OtOpcUa fixed-tree tests.
What is included
- Vendored 64-bit DLLs under
vendor/fanuc-cnc-api/64bit/ - A profile extractor that inspects PE exports with
pefile - A Windows P/Invoke shim source under
shim/for clients that loadFWLIB64.dlldirectly - Built-in profiles for:
FWLIB64fwlib0DN64fwlib0iD64fwlib30i64fwlibe64fwlibNCG64
- A stateful mock server with:
- version/profile switching
- forced error injection
- runtime state patching
- built-in default mock data
- auto-detected native FOCAS Ethernet PDU handling for the targeted API subset
Quick start
Install in editable mode:
python -m pip install -e .
List the generated profiles:
focas-mock list-profiles
Start the mock server with the 30i profile:
focas-mock serve --profile fwlib30i64 --host 127.0.0.1 --port 8193
Start with a JSON patch file that overrides the default data:
focas-mock serve --profile fwlib30i64 --data examples/mock-30i.json
Protocol
The server accepts two protocols on the same port:
- newline-delimited JSON for fixture control and shim tests
- native FOCAS Ethernet binary PDUs from the real
fwlibe64.dll
JSON requests are one object per line:
{"id":1,"method":"cnc_allclibhndl3","params":{"ipaddr":"127.0.0.1","port":8193,"timeout":10}}
Example response:
{"id":1,"method":"cnc_allclibhndl3","rc":0,"message":"EW_OK","result":{"FlibHndl":1,"profile":"fwlib30i64"}}
Supported admin methods:
mock_get_statemock_patchmock_resetmock_load_profilemock_list_methodsmock_schedule_alarms
Example patch request:
{"id":2,"method":"mock_patch","params":{"state":{"parameters":{"6711":{"type":"long","value":1234,"decimal":0}}}}}
Native FOCAS Ethernet clients do not use the JSON request format. Seed profile
and fixture state with JSON first, then point cnc_allclibhndl3 at the same
host and port. Wire-level details are documented in
docs/FOCAS_WIRE_PROTOCOL.md.
For clients that should avoid FANUC DLL loading entirely, dotnet/Focas.Wire
contains a native C# read-only TCP client for the verified wire subset. It does
not expose write APIs; use the JSON control channel to preset fixture state.
Example test setup over TCP:
{"id":1,"method":"mock_load_profile","params":{"profile":"FWLIB64"}}
{"id":2,"method":"mock_patch","params":{"state":{"pmc":{"R":{"100":{"type":"byte","value":1}}},"parameters":{"6711":{"type":"long","value":1234,"decimal":0}},"macros":{"500":{"value":42000,"decimal":3}},"statinfo":{"run":3,"aut":1,"emergency":0},"alarms":[{"alm_no":100,"type":1,"axis":0,"msg":"TEST ALARM"}]}}}
{"id":3,"method":"cnc_allclibhndl3","params":{"ipaddr":"127.0.0.1","port":8193,"timeout":10}}
{"id":4,"method":"pmc_rdpmcrng","params":{"FlibHndl":1,"area":"R","data_type":"byte","start":100,"end":100}}
Regenerating profiles
The built-in JSON profiles are generated from the vendored binaries:
python -m focas_mock.cli extract-profiles
By default this reads:
vendor/fanuc-cnc-api/64bit/*.dllupstream/fwlib.cs
and writes:
src/focas_mock/builtin_profiles/*.json
Testing Direct P/Invoke Clients
If a client directly P/Invokes FANUC's 64-bit DLLs, point it at the shim DLLs built from shim/ instead of the real vendor DLLs. The shim exports the small FOCAS surface used by the client and forwards calls to this Python server over JSON/TCP.
focas-mock serve --profile FWLIB64 --host 127.0.0.1 --port 8193
.\shim\build.ps1
$env:FOCAS_MOCK_HOST = "127.0.0.1"
$env:FOCAS_MOCK_PORT = "8193"
Before running the client, seed profile/state with mock_load_profile and mock_patch as shown above.
Detailed documentation for the supported FOCAS subset is in docs/USED_FOCAS_API.md.
Native Ethernet wire notes are in docs/FOCAS_WIRE_PROTOCOL.md.
OtOpcUa-specific setup notes are in docs/OTOPCUA_DOTNET_INTEGRATION.md.
Implemented mock calls
The server currently implements a practical subset of the surface observed in the exported DLLs and the C# wrapper:
cnc_allclibhndlcnc_allclibhndl2cnc_allclibhndl3cnc_freelibhndlcnc_sysinfocnc_statinfocnc_rddynamic2cnc_actfcnc_actscnc_acts2cnc_getpathcnc_setpathcnc_rdaxisnamecnc_rdspdlnamecnc_rdparamcnc_wrparamcnc_rdmacrocnc_wrmacrocnc_rdalmmsg2pmc_rdpmcrngpmc_wrpmcrngcnc_rdopmsgcnc_rdopmodecnc_rdprgnumcnc_exeprgname2cnc_rdexecprogcnc_rdseqnumcnc_rdblkcountcnc_rdproginfocnc_rdprogdir3cnc_rdtimercnc_rdspmetercnc_rdsvmetercnc_rdsploadcnc_rdspgearcnc_rdspmaxrpmcnc_rddiagnumcnc_rddiaginfocnc_diagnoss
Limitations
- This is not a binary-compatible replacement for FANUC's DLLs.
- Native FOCAS Ethernet support is intentionally scoped to the targeted API subset documented in
docs/FOCAS_WIRE_PROTOCOL.md. - The per-version profiles are grounded in exported symbol tables plus the published interop wrapper, while some defaults such as axis-count hints are inferred from filename families and documented as heuristics.