Define the Communication Gap
The target is communication between a Beckhoff PC running MS-DOS and a Siemens S7-400. The evidence confirms Ethernet transceiver activity at the Beckhoff PC, but activity alone does not prove that MS-DOS has a functioning TCP stack or that either endpoint implements a compatible application protocol.
| Layer | Known condition | Required verification |
|---|---|---|
| Physical Ethernet | The transceiver indicates transmitted and received traffic. | Confirm that the observed frames belong to the Beckhoff PC and S7-400. |
| TCP networking | No working MS-DOS TCP stack is identified. | Verify interface configuration and successful bidirectional TCP traffic. |
| Application protocol | No common data-exchange protocol, driver, or command is specified. | Identify compatible software at both endpoints before designing the data transfer. |
Establish the Ethernet Path
First establish a TCP Ethernet stack under MS-DOS. This provides the transport needed to send and receive data, but it does not by itself provide S7-400 data access. The evidence does not identify a supported MS-DOS Siemens driver, its installation package, or its commands; therefore, verify driver availability directly rather than assuming that legacy software can be obtained.
Define the missing application layer explicitly: determine which software on the S7-400 side will accept connections, which software on the Beckhoff PC will initiate or receive them, and how both sides will encode data. Do not proceed from link indication directly to PLC data mapping.
Capture and Diagnose the Traffic
- Confirm that the Beckhoff Ethernet interface can transmit and receive frames through the installed MS-DOS network stack.
- Capture the network traffic with Wireshark from a location where the relevant frames are visible.
- Check whether the traffic contains valid bidirectional TCP exchanges between the intended endpoints rather than unrelated network broadcasts.
- If TCP works, identify the application protocol in the capture and verify that both endpoints use the same message structure.
- If only physical activity is present, correct the MS-DOS network stack or interface configuration before troubleshooting PLC data access.
Use RS-232 as the Fallback
If a usable Ethernet stack or compatible application protocol cannot be established, evaluate an RS-232 serial connection. The evidence identifies serial communication only as a backup option and supplies no baud rate, framing, cable pinout, or Siemens interface details. Select those settings only after confirming the actual serial interfaces and supported protocol at both endpoints.
FAQ
Can an MS-DOS Beckhoff PC communicate with a Siemens S7-400 over Ethernet?
Potentially, but the PC first needs a functioning TCP Ethernet stack and both endpoints need a compatible application protocol. Ethernet transceiver activity alone does not confirm PLC data communication.
Why does the Ethernet transceiver flash without S7-400 data transfer?
The indication proves only that frames are present at the interface. Capture the traffic with Wireshark and verify bidirectional TCP exchanges and a shared application protocol.
What is the fallback if MS-DOS Ethernet communication cannot be established?
Evaluate RS-232 communication after confirming that both endpoints provide compatible serial interfaces and protocols. Baud rate, framing, and cable wiring remain unspecified and must be determined from the installed hardware.