4.4 KiB
4.4 KiB
G7: FOCAS live-CNC smoke on a real FANUC control (2026-11-13)
Result: PASS. Every criterion passes. An axis tag was added to vd03 for the axis criterion (see "Axis position" below). The one item not done is the comparison of the identity values against the control panel, which needs a person at the machine.
Setup
- Target: the deployed DEV server on wonder-app-vd03 (
opc.tcp://10.220.157.247:4840), master76e73e7dsince 12:28Z the same day. Its FOCAS driverfocas-z-34184polls the Makino Z-34184, a FANUC 31i-B (series G431), over the wire client (FOCAS2 PDU v3). - Access: read-only. OPC UA reads and subscriptions came from the Mac with
otopcua-cli(anonymous). The server log was pulled over SMB (winrm smb pull, file copy only). No remote exec, no configuration change, no deploy.
Criteria (docs/plans/v2-ga-lab-gates-plan.md §G7)
| Criterion | Result | Evidence |
|---|---|---|
| The wire client opens a FOCAS2 session | PASS. The driver has served Good values since boot (12:28:45Z); every value below comes from that live session. | reads.txt |
| Identity nodes return non-null values | PASS (non-null). SeriesNumber G431, Version 22.0, CncType 31, MtType MM, MaxAxes 32, AxisCount 7, all Good. Not compared with the control panel (needs a person at the machine). G431 matches the series recorded for this control in the 2026-10 wire-decode work. |
reads.txt |
| An axis position reads Good with a plausible value | PASS after the deploy below (Axes/X/AbsolutePosition = 280.1574, Good). Before it: vd03's configuration authors no Axes/ tags, and adding one would mean a deploy to DEV. Plausible Good values from the same live session: Spindle/S1/Load 56.7 % and MotorSpeedPct (moving), Timers/CuttingSeconds, OperationMode/ModeText AUTO, Program/Name //CNC_MEM/USER/LIBRARY/O1111. The position decode is pinned by real-31i-B captures from this machine (docs/drivers/FOCAS.md §"Wire decode corrections (2026-10)"). |
reads.txt |
| A subscription delivers ≥ 3 updates within 5 s | PASS: 6 Good updates of Spindle/S1/Load in 5 s (13:15:16–13:15:21Z). |
sub5.txt |
No EW_SOCKET (-1) / EW_HANDLE (-7) during a 2-minute soak |
PASS. Soak 13:15:22–13:17:27Z: a recursive subscription on the driver's 22 variables got 272 notifications, and 21 variables were Good throughout. The 22nd, Program/BlockCount, read BadNoData throughout (the control does not report it; the same in every deploy record). 0 EW_SOCKET/EW_HANDLE in the whole day's server log. The only ERR/WRN lines in the window come from these reads connecting by IP ("domain not listed in the server certificate") and the known DEV mesh-PSK warning. |
soak-summary.txt, soak-notifications.txt, vd03-log-window.txt |
Record: CNC FANUC 31i-B (Makino Z-34184), series G431, version 22.0; test date 2026-11-13; OtOpcUa 76e73e7d
(deployed); client otopcua-cli from c9bc358d.
Axis position (owner-approved DEV config deploy, 2026-11-13 15:30Z)
The owner approved adding an axis tag to vd03 so the axis criterion could be checked directly.
- Authoring: in vd03's AdminUI
/raw: devicez-34184→ Browse device (a live FOCAS browse of the control listed axes X, Y, Z, B, C, AA6, AA7) → selectedFOCAS/z-34184/Axes/X/AbsolutePositionwith "Create matching tag-groups" → Add 1 tag. - Deploy:
e9fbe63e, revisionf902e9409d79…, sealed 15:30:13Z. It also cleared the standing "Configuration drift" chip left by the #903 edit-and-revert check. - Apply: server log
AddressSpaceApplier: applied plan (kind="PureAdd", added=3, removed=0, changed=0, … rebuild=false)andraw subtree materialised (containers=2, tags=1, subset=true, failed=0). This was a surgical add: no rebuild, existing subscriptions untouched (vd03-log-deploy-excerpt.txt). - Read:
ns=2;s=focas-z-34184/z-34184/FOCAS/z-34184/Axes/X/AbsolutePosition= 280.1574, Good, 11 s after the seal. ServiceLevel stayed 250. - Subscription: 30 s, the axis held still (one Good notification,
axis-sub30.txt). The 5-update subscribe criterion is met bySpindle/S1/Loadabove. - Re-check of all 23 variables: 22 Good +
BlockCountBadNoData, as before (after-deploy-summary.txt). - Log: still 0
EW_SOCKET/EW_HANDLEfor the day. The only ERR lines after the deploy are these reads by IP.
The tag is left in place on vd03 as a permanent axis-position monitor.