A Fagor 8025T can drip feed through WinDNC even when ordinary program upload and download already work. In the reported case, the TRANSMISSION ERROR came from using the file-transfer serial format and end-of-file character for a DNC session. The working configuration changed the serial framing from 7,E,2 to 8,N,1 and the end-of-file character from ESC to NUL.
Why ordinary transfers can work while DNC fails
A successful upload or download proves that the cable and basic communication path operate, but it does not prove that WinDNC has the correct DNC framing. The existing terminal programs communicated at 1200 baud, 7 data bits, even parity, and 2 stop bits; applying those same settings to WinDNC produced TRANSMISSION ERROR.
| Function | Serial format | End-of-file character |
|---|---|---|
| Existing program-transfer tools | 1200,7,E,2 in the reported setup; 8,N,1 was also reported as usable | ESC can be used |
| WinDNC drip feed | Baud,8,N,1; the reported setup retained 1200 baud | NUL |
Configure WinDNC for the 8025T
- Keep the baud rate matched between WinDNC and the CNC. For the reported installation, use 1200 baud.
- Set WinDNC to 8 data bits, no parity, and 1 stop bit.
- Set the WinDNC end-of-file character to NUL, not ESC.
- Select the program, starting block, and the execution mode in WinDNC. The reported guidance identifies Infinite Length Execution as the drip-feed function and automatic mode as mode 0.
- Start the DNC execution and confirm that blocks begin transferring without TRANSMISSION ERROR.
Interpret the CNC indications
Enabling DNC through operating mode 7-6 produced a flashing DNC indication and N* on the automatic screen. Pressing Cycle Start in that state produced error 014, but the evidence does not define error 014 or establish a direct mapping between that code and a specific setting. Correct the proven framing and NUL terminator faults first; do not treat working file transfers as validation of the WinDNC configuration.
Verify the correction
Verification requires an actual drip-feed run, not another upload or download. Confirm that WinDNC uses the matched baud rate with 8,N,1, terminates the file with NUL, starts at the selected block, and continues execution without TRANSMISSION ERROR. If it still fails, recheck those DNC-specific values independently of the settings stored in other terminal software.
FAQ
What WinDNC serial settings work with a Fagor 8025T?
Use a baud rate matched to the CNC with 8 data bits, no parity, and 1 stop bit. The successful reported configuration was 1200,8,N,1.
Which end-of-file character does WinDNC require for 8025T drip feed?
Set the end-of-file character to NUL. Using ESC was part of the configuration that failed.
Why does WinDNC show TRANSMISSION ERROR when uploads work?
Ordinary file-transfer tools can operate with 7,E,2 and an ESC terminator, while the successful WinDNC DNC session required 8,N,1 and NUL. Working uploads therefore validate the communication path but not the DNC-specific framing.