A Unidex 511 without its Windows NT/95 software disk is still a complete i386 MS-DOS motion controller. The missing CD removes the PC-side utilities (auto-tune, file transfer front end), not the controller's command interpreter. The recovery path is: image the resident flash, drive the unit with the command set in the U511 manual, and rebuild the host side on a current PC.
Controller internals that set the recovery options
The U511 is a DSP-based 4-axis controller carrying an i386 host processor running MS-DOS. Units inspected in the field expose a DOS shell with drives A and B, a BIOS-embedded debugger, and a UART port on the i386. The main board also carries a JTAG interface to the DSP and FPGA (readable while running), GPIB ports, and an iSBX connector with direct access to the DSP bus plus additional expansion I/O.
The resident software, firmware, system files, and parameter files sit on AM29F040B flash devices in PLCC32 sockets. That matters for recovery: a working unit can be imaged, and a second unit can be brought to the same state. It also means a unit may already carry a different image. One unit in the field ran a U11 clone/emulator system instead of the native U511 software, so identify what is installed before assuming behavior matches the manual.
Recovery approaches compared
| Approach | What it restores | Dependency | Risk |
|---|---|---|---|
| Locate original Windows NT/95 utilities | Vendor GUI, auto-tune, file transfer | Archived media. The Aerotech contact attempt returned no software; the A3200 platform is a different controller family and does not substitute | None to hardware; availability is the constraint |
| Command-level control from the U511 manual | Motion, program upload/download, parameter access | A communication link (GPIB used successfully) and the manual's command list | Low. Parameter writes change tuning and limits |
| Flash clone from a working unit | Identical firmware, system, and parameter files | EPROM/flash programmer with parallel port, PLCC32 adapter or socket, second unit | Moderate: socket wear, overwriting parameters, ESD |
| Custom host front end (Excel/VBA/C over GPIB) | Remote motion, macro buttons, parametric programming, dashboards | Command-level control working first | Low; software only |
Recommended path: image the flash, then command the unit
Back up the flash before any parameter change. Then use the manual's command set as the primary interface. The manual lists every command used to communicate with the controller, including how to download and upload files, which is enough to make the unit useful without the vendor GUI. Where the U511 manual is thin, the earlier U500PCI and DR500 manuals carry additional detail; the U511 reuses the same DSP control architecture as the U500 PCI boards.
Auto-tune remains available: tuning was run on units already carrying the resident software, and the results fed a working remote-control front end. Treat the flash image as the recovery point for tuned parameters as well.
Flash imaging procedure
- Power down the U511 and observe ESD handling. Remove the AM29F040B (PLCC32) with a PLCC extractor and note pin-1 orientation.
- Prepare the programmer host. A PCB5.0T-class programmer that needs a parallel port ran on Windows 10 64-bit through a PCIe parallel card on a mini-tower PC. Confirm the programmer powers up with correct rails before connecting a chip.
- Read the device twice and compare the two images byte for byte. A mismatch means a socket or contact fault, not a bad chip.
- Save the image with the device type, board position, and unit serial number. Back up the firmware, system, and parameter files separately from the raw chip image.
- Write to a spare chip only after a verify pass on the read. Verify after write, then boot the unit from the clone.
- Keep the images on at least two flash drives.
Programmer faults: heat, contact, and logic
| Symptom | Mechanism | Fix |
|---|---|---|
| New surplus programmer arrives dead or unstable | Failed solder joints in the programmer's power supply section, so rails sag or vanish under load | Reflow the supply-section joints; measure rails before inserting a device |
| Programmer reads but will not program AM29F040B | Worn PLCC32 socket contacts leave one or more pins with high contact resistance during the program pulse | Respring the socket contacts; re-run read-compare, then program and verify |
| Software runs on Windows 10 only with driver trouble | Legacy parallel-port I/O access on a 64-bit OS | Use a PCIe parallel card and the port configuration that worked for the programmer software on Windows 10 64-bit |
| Unit boots a different environment than the manual describes | A U11 clone/emulator image is resident | Load the U511 image from a known-good unit |
Command-level control from a Windows 10 host
The proven host stack is an Excel/VBA/C front end over GPIB, with macro buttons issuing U511 commands; the same interface supports a dashboard exposing all remote commands. Pair it with a text editor for part programs. Parametric programming is straightforward because the host computes values and sends resolved commands. A 4+1 configuration is workable: four axes on the U511 plus a fifth axis on a separate machine, with the host coordinating.
The controller executes multiple programs concurrently. One program can run independent 4-axis motion while another sits in a static loop polling the DSP user-interrupt input. That structure is the basis for probe routines, because the polling loop never waits on a motion block.
- Establish a link and send a benign query command from the manual to confirm two-way communication.
- Upload the controller's existing program and parameter files to the host as a second backup layer.
- Issue a small, low-speed single-axis move with the drive amplifier enabled and travel clear.
- Script the sequence in VBA/C, logging each command and response so faults trace to a command.
Probe and tool-setter wiring to the user interrupt input
The user interrupt input is opto-coupled, so it needs its own loop power. A Renishaw MP1/MP4 probe/tool setter was wired to it with a 5 V supply. The physics: the optocoupler LED needs a defined forward current, set by supply voltage minus the LED drop divided by the series resistance. Read the input's current and voltage limits from the connector section of the U511 manual before choosing the supply and any external resistor. Keep the isolated supply return separate from the controller logic ground so the opto-coupler keeps its isolation.
When the input asserts, the encoder positions latch within 3 µs. At a feed rate v, the position uncertainty is v times 3 µs. For example, at 1 mm/s the latch uncertainty is 3 nm (assumed feed for illustration), so the dominant probe error is mechanical trigger repeatability, not controller latency. Note the polling loop reads the latched values afterward, so scan time in the host does not degrade the latched position.
Servo, amplifier, and encoder quantities to confirm
| Quantity | Value from the installation | Where to read the limit |
|---|---|---|
| Flash device | AM29F040B, PLCC32 | Chip marking; programmer device list |
| Servo motors | 80v-703 Electro-Craft DC servos | Motor datasheet: continuous/peak current, back-EMF constant |
| Encoders | 10k quadrature encoders | Encoder datasheet: confirm whether 10k is lines or post-decode counts; x4 decoding changes counts per revolution and the velocity ceiling |
| Servo amplifier modules | DS16020 DC servo modules; DR300/DR500 amplifier racks in the family | Module datasheet: bus voltage, continuous and peak output current |
| Encoder latch time | Within 3 µs of user interrupt | U511 manual, user interrupt section |
| Probe supply | 5 V to opto-coupled input | U511 manual, input electrical specification |
A 5th axis was planned by the vendor as an iSBX daughter board feeding encoder, limit, and home inputs directly onto the DSP bus, with outputs going to an external DR300 or DR500 amplifier rack. Treat the iSBX connector as a documented expansion path rather than a place to probe casually: it sits on the DSP bus.
Verification after recovery
- Boot the cloned flash and confirm the controller reaches the same prompt and file set as the source unit.
- Compare a re-read of the new chip against the saved image; the bytes must match.
- Jog each axis in both directions at low speed and confirm encoder counts change with the correct sign.
- Command a known distance and confirm the encoder count matches the expected counts, using the decoding factor confirmed in the table above.
- Watch following error during a move; a rising error with steady velocity signals a tuning or amplifier current-limit problem, not a communication fault.
- Trip the probe input by hand and confirm the polling program sees the interrupt and reports a latched position.
FAQ
Can I run a Unidex 511 without the original Windows software?
Yes. The U511 manual lists the full command set, including file download and upload, so a host can drive it over GPIB with a custom Excel/VBA or C front end. Auto-tune is the feature you lose unless the resident software on the unit provides it.
Can I back up the U511 firmware by reading the flash chips?
Yes. The resident software sits on AM29F040B devices in PLCC32 sockets. Read the chip twice, compare the images byte for byte, and verify after any write; failed writes usually trace to worn socket contacts.
Does the U511 support a touch probe or tool setter?
Yes. The opto-coupled user interrupt input accepts a probe such as a Renishaw MP1/MP4 with a 5 V supply, and encoder positions latch within 3 µs. Run the probe polling loop as a second program alongside the motion program.
When should I stop and contact Aerotech?
Stop when a flash image will not boot after a verified write, or when a command in the manual produces behavior the earlier U500PCI and DR500 manuals cannot explain. Do the same before modifying DSP, FPGA, or iSBX hardware. Send the unit's serial number and a description of the installed image to Aerotech's official support channel.