Skip to content

Corrections

Things this project got wrong and later fixed. Kept in one place so nobody — including a future session reading the notes — re-derives an answer that has already been shown to be wrong.

Most of these were caught by Grant looking at the actual machine. That is the pattern worth noticing: the paper record is excellent, and it still lost to a physical look about half the time.

Changed the design

Was Is How it surfaced
Axis loom connector is female at the Housing 🔴 Male. The panel end is female — that is the half to buy Physical check. The device list had said MASCHIO all along
Land the encoder screen at the Housing 🔴 Already landed at the drive, on the drive's frame-ground pin. A second bond would create the ground loop the screen exists to prevent Re-reading the connector schedule
LinuxCNC will not see the axis limit switches 🔴 It does. Three inputs are per-axis overtravel and arrive through the ribbon. The drive's own overtravel path is separate and additional Reading the symbolic map properly
The controller reads a carousel encoder 🔴 It does not. That connector is the carousel drive's own motor encoder. The controller gets position from binary bits Grant's instinct, confirmed in the device list
The servo enables need sinking outputs or interposing relays 🔴 Neither. The analog card's enable outputs are floating isolated switches — a dry contact does not care which way current flows Reading the card documentation
Panel-mount adds four connections, a slot adds none 🔴 Misleading. The ribbon ends in a latching header either way; the breakout board is itself a component. Counted properly, the panel route has fewer joints Grant pointed out the flaw
The photocell HOLD chain is a plain AND of both beams 🔴 Incomplete, and it would have broken pendulum working. Each beam has its own arming bit (MCONTR_FOTOC_Zn); disarming one pins its term high. Without that, the operator loading one zone holds the program running in the other — the whole point of pendulum working Reading JOB 9
The zone boundary is the pair 1828.30 / 1839.10 mm 🔴 One number, 1833.70 mm. From PLC version 3.82 the machine tests the mean of the two and nothing else. The pair survive only as per-zone soft limits The version note in the PLC says so outright
The ATC is refusing to run, and the reason is in the PLC source 🔴 Wrong premise, and mine not Grant's. The cycle had never been commanded — a gap in knowing how to drive the software, not a refusal. Two claims built on that framing (the diagnostic screen cannot start a change; EN_CU_MAN = 0 disables manual tool change) were unfounded. VEN_CU_MAN is declared in the PLC and never used Grant said so plainly
The Z brake stops the carriage dropping, so Z sags a little on every enable and disable 🔴 Over-asserted, and the wrong question. No evidence was offered that Z is gravity-loaded that way. The brake relay returns through the Z drive's own CN1-27, so /BK releases it whenever the servo is on — it is released throughout every cut and cannot be holding anything during one. What resists the cut reaction is the servo's own stiffness Grant pushed back on the premise
Which branch owns the locating stops is unsettled ✅ Both do, and it is configurable per field. VBATT_Y_SU_END selects AUTO (stops rise at the end of the previous program) or PEDAL (stops rise on pedal release) zones-and-loading.md

Changed the numbers

Was Is
46 inputs and 42 outputs 41 and 41. Those were symbol counts — one input carries six symbols. The output shortage was 9, not 10
Ribbon pitch 2.24 mm 2.54 mm. "22.4 mm over 10 pins" is nine gaps, not ten. 2.24 mm is not a standard pitch and does not exist
One fuseholder on the panel Two
Ferrules for the 28 AWG conductors 0.08 mm² ferrules are hard to source. Fold the conductor double instead — and never tin it, solder cold-flows and the joint loosens

Changed the understanding

Was Is
The summary-fault input is the E-stop chain It is a summary fault fed by seven breakers, three drive alarms, the carousel relay and the inverter
The drives are self-homing They are not. The home switches come back to the Housing on a pin that has no drive destination, and in speed mode these drives have no homing function at all
The drive serial port is a generic serial route It needs the manufacturer's own software and cable
The spindle pot might be the speed source It is an override in the controller's path. The S word will control spindle speed
P-clips will anchor the ribbons Wrong part for flat cable — and then the requirement was dropped entirely

The big one

"We have no records of the driver connectors."

The records existed. They were in a 40-sheet drawing, a 14-page device list and a 12-page connector schedule that had not been read. Reading all 66 pages produced the complete axis pinout, the full drive interface, all 82 I/O points, the homing method, four hardware interlocks invisible in the software, and the spare capacity inventory.

The planned work — opening both ends of the servo connectors to record pin-to-pin — turned out to be unnecessary. Nothing had to be unplugged.