After the user interface is installed before the programming package, the TSX17 software can proceed past the missing-interface error and the PLC upload can be tested on a supported DOS platform. The documented target is DOS 5.x through 6.22. Windows 95 or Windows 98 requires changes to CONFIG.SYS and AUTOEXEC.BAT; a vDOS attempt produced the same prerequisite error and is not the preferred recovery route.
Installation approach comparison
Choose the operating environment before building floppy media. The package is intended to install on an existing DOS system; it is not described as software that supplies its own operating system.
| Approach | Prerequisites | Known issue | Recommendation |
|---|---|---|---|
| Physical PC with DOS | DOS 5.x-6.22, floppy drive, suitable serial port | The user-interface disks and programming disks must be presented in the required order | Preferred for recovering the TSX17 program |
| Windows 3.11 over DOS | An underlying DOS version within the stated range | Installation must be run from the DOS environment, with the same media-order requirements | Use the DOS layer rather than treating Windows 3.11 as the target platform |
| Windows 95 or Windows 98 | Ability to modify CONFIG.SYS and AUTOEXEC.BAT
|
Default startup configuration may not provide the environment expected by the software | Use only when the required startup-file changes are understood and recoverable |
| vDOS virtual environment | Virtual DOS configuration and access to installation media | A reported attempt from the PL7-1 folder stopped because the user interface was missing |
Do not use as the first recovery path |
For a one-time upload from an unidentified TSX17, use the physical DOS laptop. It already provides the two hardware features needed for the job: a floppy drive and a physical serial port. Do not move on until the DOS version is confirmed as 5.x through 6.22.
PLC and workstation prerequisites
- Record the PLC identity. The missing part-number sticker means that “TSX17” is the only confirmed controller identification. Inspect the remaining front-panel markings, connector labels, installed modules, and any existing cable documentation. Do not select an exact model or communication accessory by appearance alone.
- Protect the running controller. Treat the first connection as a read-only recovery operation. Do not clear memory, initialize the PLC, create a blank project, or issue a download command. The required direction is PLC-to-PC upload.
- Confirm the host platform. Start the laptop in DOS and read its reported version. Proceed only with DOS 5.x-6.22. If Windows 3.11 starts automatically, exit to DOS before installing.
- Check local resources. Confirm that the floppy drive reads known-good media and that the serial port is available to DOS. A connector being present does not prove that the port, cable, or communication path works.
- Preserve the download archive. Keep an untouched copy on the modern computer. Build working floppies from a separate extracted copy so a failed disk or incorrect split does not damage the only software source.
Distribution files and disk order
The downloaded package contains a password or instruction file. Its English instructions appear near the end. Read that section before copying files to disks. It provides the package-specific installation directions and should take precedence over guesses based on filenames.
The installation has at least two logical layers:
| Layer | Purpose in the installation | Required order |
|---|---|---|
| User interface | Provides the prerequisite environment checked by the programming installer | Install first |
| PL7 programming software | Provides the TSX17 programming and upload functions | Install only after the interface completes |
Starting the programming installer without the interface can launch part of setup, but it then reports that the user interface is missing. That message identifies an unmet software prerequisite rather than a PLC communication fault.
The interface distribution may span two floppies. Preserve the disk grouping and order specified by the archive instructions and the installation documentation. Do not divide files between disks solely by available capacity, alphabetic order, or folder order. Multi-disk installers commonly depend on volume sequence, companion files, and relative paths; an arbitrary split can make valid files appear non-executable or unavailable.
Physical DOS installation procedure
- Extract the archive on the modern computer. Retain its directory structure. Locate the instruction or password file and read the English section near the end.
- Identify the interface media sequence. Use the supplied directions and section 2 of the PL7 software manual to determine which files belong to each interface disk. Label the disks by package and sequence. Do not move on until every required interface disk has a defined position.
- Create the interface floppies. Copy the files without renaming them or flattening required subdirectories. After writing each disk, compare its filenames and sizes with the extracted source.
-
Create the programming floppies. Keep these separate from the interface set and preserve their documented order. The
PL7-1folder name identifies programming-package content in the supplied distribution, not a substitute for the user interface. - Boot into DOS. Confirm the DOS version again before setup. Run the installer entry point specified in the supplied directions from the correct first interface disk. Do not try every file as though each were a DOS executable.
- Install the complete user interface. Insert subsequent interface disks only when setup requests them. If setup rejects a disk, stop and verify its sequence and contents rather than advancing to the programming package.
- Restart if directed by the package. Return to the same DOS environment and confirm that the interface starts or is recognized using the package’s documented check.
- Install the PL7 programming software. Start with its first documented disk and follow the media prompts in order. The missing-interface message must no longer appear.
Windows startup-file alternative
Windows 95 and Windows 98 are possible installation hosts only when their DOS startup environment is configured for the package. The supplied instructions specifically call for modifications to CONFIG.SYS and AUTOEXEC.BAT. No exact lines or values are stated here, so take them from the package instructions rather than inventing memory-manager, path, driver, or serial-port settings.
- Make recoverable copies of
CONFIG.SYSandAUTOEXEC.BAT. - Apply only the entries specified by the package documentation.
- Restart the computer so the files are processed.
- Install the user interface before the programming package.
- Confirm that PL7 starts without the missing-interface error before connecting the PLC.
If the startup changes are unclear, return to the physical DOS 5.x-6.22 route. Repeated installation attempts in an unverified environment make media-order faults difficult to distinguish from startup-configuration faults.
Failure diagnosis by symptom
| Symptom | Likely cause | Next action |
|---|---|---|
| Programming setup reports that the user interface is missing | The interface was not installed, did not complete, or is not visible in the active DOS environment | Stop PL7 setup, install the interface first, then restart the programming installer |
| DOS does not run any selected file | The wrong file is being launched, the archive structure was altered, or the required first disk was not used | Use the installer entry point named in the English instructions and manual section 2 |
| Setup requests or rejects another disk | The interface spans multiple disks and the media were split or ordered incorrectly | Rebuild the floppy set from the untouched archive using the documented grouping |
PL7-1 setup fails in vDOS |
The user-interface prerequisite is absent or the virtual environment does not reproduce the expected installation context | Move the recovery job to the physical DOS laptop |
| PL7 starts but cannot communicate with the PLC | Installation is complete; the remaining fault is in controller identification, cable selection, serial-port access, or communication configuration | Verify each communication-layer item independently before attempting an upload |
Keep software-installation and PLC-communication faults separate. A missing-interface error occurs before the controller link is relevant. Conversely, successful application startup proves only that the workstation software is installed; it does not validate the serial cable or PLC configuration.
Upload and backup verification
- Start the installed user interface and PL7 software. Confirm that no prerequisite error appears.
- Connect the verified serial path. Use the cable and interface identified for the actual TSX17 hardware. With the part-number label missing, stop if the connection hardware cannot be positively identified.
- Select upload, not download. Read from the PLC into the computer. Reject any prompt that would initialize, overwrite, or transfer a blank application to the controller.
- Check the uploaded application. Confirm that the software reports a completed transfer and that program content is present. Review controller identity and communication diagnostics exposed by the software instead of assigning an unsupported TSX17 variant.
- Save independent backup copies. Preserve the uploaded project on the DOS laptop and copy it to separate media. Keep the untouched software archive and the working floppy images with the backup.
FAQ
Can I install TSX17 PL7 software directly from the PL7-1 folder?
Only after installing the user interface. Starting the programming package first can produce a missing-interface error even though its installer begins to run.
Does TSX17 PL7 require a specific DOS version?
The supplied package instructions call for DOS 5.x through 6.22. Windows 95 or Windows 98 requires documented changes to CONFIG.SYS and AUTOEXEC.BAT.
Can I verify the installation before connecting the TSX17?
Yes. Start the interface and PL7, confirm that the missing-interface error is gone, and verify that the programming application opens. Then perform a PLC-to-PC upload, save the project, reopen the saved copy, and confirm that the recovered program content remains present.