IMDTouchKnowledge BaseShop main store

Troubleshooting

Fixing FATAL ERROR 11 Touchscreen Controller Not Found

HMI and touchscreens Published 7 min read

Short answer

FATAL ERROR 11 is the machine application's touch-initialization routine timing out because the touch controller never answered, not a dead panel. Check four things in order: the overlay tail and connector, each 4-wire electrode under 50 ohms; the DOS driver files on the PCMCIA boot card; the controller's power-on string at 9600 baud 8N1; and the +5 V rail, which must sit between 4.75 and 5.25 V.

On this page
  1. What FATAL ERROR 11 tells you
  2. Check 1: the touch tail and its connector
  3. Check 2: the DOS driver files on the PCMCIA boot card
  4. Check 3: the controller's power-on string
  5. Worked example: the 5 V rail window on a 386 DOS panel
  6. The decision for each case
  7. Questions asked

FATAL ERROR 11 on a DOS 6.x panel means one thing: the machine application's touchscreen initialization routine probed for the controller and nothing answered inside its timeout, so the application aborted. Everything before that point, including POST, the splash and the boot from the PCMCIA card, worked. The fault sits in one of four places, and you check them in this order: the overlay tail and its connector at the board, the DOS touch-driver files on the PCMCIA boot card, the controller's power-on string on its serial port, and the controller's 5 V supply rail. On 386-class panels that have run for years untouched, the first two account for most of these faults; the controller itself becomes the prime suspect only after an electrical event or a blow to the glass.

What FATAL ERROR 11 tells you #

The message comes from the machine application, not from DOS. The startup sequence runs POST, the splash, the do-not-touch initialization prompt, and then the application loads its touch driver and polls the controller hardware. Legacy DOS touch drivers wait roughly 250 to 1000 ms for the controller to answer after the reset; no answer inside that window aborts startup with FATAL ERROR 11 --> TouchScreen Controller not found.

These platforms predate USB, so every touch signal runs over a legacy path: COM1 through COM4, the printer port, or a proprietary bus on the single-board computer. A touchscreen plugged directly into the motherboard means the controller is either a chip on that board or a small PCB behind the overlay connector, which is why the short cable between overlay and header is the first thing to prove.

Ranked by field frequency, the causes are:

  1. Lost electrical connection between overlay and board: tail, ZIF connector or crimp.
  2. Corrupted or missing touch-driver files on the PCMCIA boot card, breaking the CONFIG.SYS and AUTOEXEC.BAT chain.
  3. Mismatch between the driver and the DOS version, or between driver and controller firmware.
  4. Failed controller ASIC or analog front end, dominant only after mains transients, lightning, cabinet shorts or mechanical stress to the overlay.

If the panel never gets as far as the splash, the fault is upstream of all this, and troubleshooting a panel stuck on the autotest boot screen is the procedure for that stage.

Check 1: the touch tail and its connector #

Before you open the enclosure, isolate the machine and prove zero energy: drive sections and DC bus links can hold voltage for several minutes after the main breaker opens. Verify with a CAT III 600 V meter, and bond a wrist strap to the chassis before touching the board or the card.

The resistive overlay ends in a 4-wire, sometimes 5-wire, flat tail that seats in a ZIF or IDC header on the board or on a small controller PCB beside it. The field failure patterns are:

  • Intermittent error after warm-up: cracked solder or crimp at the connector; reflow or re-crimp.
  • Permanent error after an electrical event: open sense line from a flex fracture; find it with a continuity check.
  • Error only on cold morning starts: contamination on the contact pads; clean with IPA and reseat.
  • Error after someone has reseated the tail: pin order reversed at the header; compare against the schematic.

Measure each tail conductor end to end with a meter on ohms. Each of the four corner electrodes of a 4-wire overlay must read under 50 Ω to its pin at the header. Anything higher means the conductive coating has fatigued or a trace inside the glass has fractured, and that overlay is replaced, not repaired.

Check 2: the DOS driver files on the PCMCIA boot card #

The panel has no keyboard, so pull the card and inspect it in a DOS 6.22 machine: run CHKDSK /F against it and check the boot chain with MSD.EXE. A touch application needs these files intact on the boot volume:

  • COMMAND.COM
  • IO.SYS and MSDS.SYS, or IBMBIO.COM and IBMDOS.COM
  • CONFIG.SYS, carrying the touch driver's DEVICE= or DEVICEHIGH= line; one documented Elo setup uses DEVICE=C:\DRV\ELO.SYS /COM2 /NOINT
  • AUTOEXEC.BAT, with the touch calibration utility line
  • the application EXE and its overlay files

Reject any entry with a length of 0 bytes, a creation date of 01-01-1980, or a missing file. That is a corrupted image, and the fix is to restore the card from the machine builder's distribution image. SRAM cards hold their contents only while their internal battery lives, so a card that read fine for a decade can lose exactly these files overnight. When the image must be matched to the specific panel, getting the right firmware file for a legacy HMI panel covers the identification steps before you copy anything.

If the driver loads but prints an error, the code narrows the fault:

Driver error code Meaning Action
2 File not found Recopy the driver from the distribution image
4 Insufficient memory Reduce FILES and BUFFERS in CONFIG.SYS
7 Bad memory block Resolve memory-manager conflicts and retry
11 Controller not responding Check COM port, IRQ and controller power
14 Calibration checksum invalid Recalibrate and save to NVRAM

Code 11 at driver level is the same condition the application reports as FATAL ERROR 11: the controller exists in the driver's configuration but does not answer.

Check 3: the controller's power-on string #

Controllers of this era, such as the Elo E271-1410 and E271-2210, the MicroTouch SMT3 and the Carroll Touch CT1000, are serial devices, typically on COM2 or COM4 at 9600 baud, 8 data bits, no parity, one stop bit, speaking a vendor polling protocol. You can prove the controller without the machine software: connect a null-modem cable from the suspected port to a laptop, open a terminal emulator at 9600 8N1, and power the panel. A healthy controller announces itself at power-on; Elo units send an ELO or EU identification string, MicroTouch units send TS followed by the firmware revision.

A string present means the controller is alive and the fault is on the driver side: the wrong COM port or IRQ in the driver line, or a driver that does not match the DOS version on the card. No string means the controller is unpowered, not clocked, or its UART transceiver is damaged, and the rail check next decides which.

Worked example: the 5 V rail window on a 386 DOS panel #

Inputs:

  • Nominal supply at the controller: +5 VDC, the documented rail for these legacy serial touch controllers.
  • Tolerance: ±5 % of nominal, the documented acceptance limit for the rail.
  • Measurement point: at the controller's supply pins, panel powered and touch circuit connected, because a reading taken at the system supply hides the drop across a corroded connector.

Rule in words: the rail passes only if the measured voltage lies inside nominal plus and minus 5 % of nominal.

Arithmetic:

5.0 V × 0.05 = 0.25 V

5.0 V − 0.25 V = 4.75 V, the lower limit

5.0 V + 0.25 V = 5.25 V, the upper limit

Result: the acceptance window is 4.75 V to 5.25 V at the controller pins.

Decision: a reading below 4.75 V explains a silent controller, since the oscillator and UART brown out and never send the power-on string, so repair the supply path of connector, wiring or on-board regulator and retest before condemning anything. A reading inside the window, with no power-on string and no oscillation at the controller's crystal on a scope, convicts the controller board itself.

The decision for each case #

  • Every electrode under 50 Ω and the tail seats clean: the overlay and its connection are proven, so stop suspecting them and move to the card.
  • A 0-byte or 1980-dated file, or a missing driver line: restore the PCMCIA card from the machine builder's image. On panels this age this fix alone clears the error more often than any other.
  • Power-on string present but the error persists: fix the driver configuration, the COM port, the IRQ or the DOS-version mismatch; the hardware is good.
  • No string and the rail inside 4.75 to 5.25 V: a failed controller. Confirm with the scope check, then source the controller board.
  • Board dead outright or no image obtainable: when repair is no longer worth it, an industrial panel PC running a modern HMI runtime replaces the 386 terminal, and verifying an obsolete HMI replacement before ordering keeps the swap to a single shutdown.

Questions asked

Can the PCMCIA card cause FATAL ERROR 11 even though the panel still boots?

Yes. DOS boots from the first files on the card, so the machine can start, show its splash and still fail when the touch-driver files themselves are gone. SRAM cards keep their contents only while a small internal battery lives, and when it dies exactly these files vanish or show 0 bytes and a 01-01-1980 date. Restoring the card from the machine builder's distribution image clears it.

What should each electrode of a 4-wire resistive overlay read on a meter?

Under 50 ohms end to end, from the electrode at the glass to its pin at the board header. Higher readings mean the conductive coating has worn thin or a trace inside the glass has cracked; no reseating fixes that, and the overlay is a replace-on-fail part. Test all four, because one open sense line is enough to trigger the error.

The controller sends its power-on string but the error still appears. What is left?

The driver side. A controller that talks at 9600 baud is alive, so the fault is configuration: the DEVICE= line naming the wrong COM port or an IRQ conflict, a driver that does not match the DOS version on the card, or driver and controller firmware from different revisions. The driver's own error codes, 2, 4, 7, 11 or 14, tell you which of these it is.

When is replacing the panel the better decision than repairing it?

When the single-board computer will not boot at all, when no distribution image can be sourced for the card, or when the overlay keeps failing from vibration. At that point a PC-based panel running a modern HMI runtime replaces the terminal; match the existing cut-out and the machine's I/O before ordering so the swap happens in one shutdown.

Keep reading

  • Troubleshooting

    Fixing HMIRTM.EXE Runtime Crashes on a Comfort Panel

    The HMIRTM.EXE serious error is the HMI runtime crashing on the panel itself, most often because internal storage filled with accumulated logs. Back up to a USB stick from the panel operating system, delete the logs, and stop the runtime before changing the IP address; the failed ping is a network fault that sits below the project layer.

    HMI and touchscreens

  • How-to

    How to Upload a Program From an Old Touchscreen HMI

    An editable upload from an old Siemens touchscreen HMI is possible only if Enable back transfer was checked when the project was first downloaded; it was off by default, so most panels refuse. Without it, ProSave recovers at best a binary backup that restores to the same panel type and cannot be edited. Identify the exact model from the label, and ask the original supplier for the project before anything else.

    HMI and touchscreens

  • Troubleshooting

    Getting the Right Firmware File for a Legacy HMI Panel

    Before you chase a firmware file, decide which of three things the panel actually lacks: a communications fix, an application restore, or an operating-system image. A panel that boots and navigates almost never needs firmware, and the only safe source for the image is the manufacturer or an authorized distributor, matched to the exact nameplate model and revision.

    HMI and touchscreens