Troubleshooting BT200 PROFIBUS Cable Length Doubling Errors

Troubleshooting BT200 PROFIBUS Cable Length Doubling Errors

When the Siemens BT200 handheld cable tester returns a distance reading that is roughly twice the physical cable length, the symptom is almost always measurement contamination from connected PROFIBUS nodes, not a defective cable. This guide consolidates field data from a 60-system test campaign (40% of which returned 88 m on a 36 m run) and walks through the parameter model, root causes, verification procedure, and corrective actions.

1. Problem Overview

The BT200 distance-measurement function (cable test) is based on a TDR (Time Domain Reflectometry) principle. The instrument injects a fast edge into the bus cable and evaluates the reflection profile. Under clean conditions the dominant reflection corresponds to the end of the segment terminated by the BT200 test plug, and the reported distance matches the physical run within a few percent.

Field symptoms:

• Reported length is approximately 2x the actual run (e.g., 88 m reported on a 36 m segment).
• Result is non-deterministic - repeated tests on the same segment produce both correct and doubled values without changes to the cable.
• Variation appears unrelated to the operator-entered loop resistance; distance persists across entries from 4.17 to 10.43 Ω.
• Issue is over-represented in segments built around Turck field I/O with Siemens PROFIBUS interfaces (CP/IM/ET 200S/ET 200pro gateways).
• Verified independently by SIMATIC Step 7 Topology Editor showing the correct run length.

2. How the BT200 Measures Distance

The BT200 transmits a high-frequency pulse into the two-wire bus and measures the round-trip propagation time. The internal model assumes a fixed propagation velocity (typically specified for a PROFIBUS DP cable with nominal velocity factor ~0.66 c). The distance is calculated as:

L (m) = (v_p x t_round) / 2

Where v_p is the propagation velocity inside the cable (~2.0 x 10^8 m/s for standard PROFIBUS cable) and t_round is the measured round-trip time of the reflection.

Two termination conditions produce strong reflections:

1. Open circuit at the end of the cable (no terminator installed).
2. Connected devices with internal capacitance (input stages of ASIC transceivers, repeaters, optocouplers) which the BT200 charges during the pulse.

If the BT200 sees a strong reflection from a connected device before the pulse reaches the real end of the line, the distance is read out to that device - the "double length" anomaly is in fact a read-out to the first major reflection, which on a 36 m segment happens to land at ~72-88 m depending on device placement and stub length.

3. Required Measurement Parameters

The BT200 prompts for three values before each distance test. Wrong values degrade accuracy but, per the source data, do not produce the doubling symptom - they only shift the result by a few percent.

For PROFIBUS DP type A cable (standard violet, 2 x 0.34 mm², 150 Ω characteristic impedance), use:

• Loop resistance: 110 Ω/km
• Capacitance per unit length: ~30 pF/m (informational; not entered)
• Velocity factor: ~0.66 c

4. Test Setup Procedure (Manufacturer-Defined)

1. Power down all bus stations on the segment being tested.
2. Connect the BT200 test plug connector to the far end of the line (this is the loopback terminator that the BT200 uses as a reflection target).
3. Connect the BT200 to the near end of the line.
4. Disable the BT200's built-in bus terminator (menu option "Term OFF") for the duration of the test - the test plug at the far end is the only termination that should be active.
5. Start the distance measurement from the BT200 menu.
6. When prompted, enter loop resistance (default 110 Ω/km).
7. Enter the number of 12-Mbaud connectors / inductively-loaded devices.
8. Enter resistance per connector (default 0.32 Ω).
9. Confirm with OK - the BT200 performs the measurement and displays the result.

5. Root Cause Analysis - Why the Reading Doubles

Three mechanisms were observed or are consistent with the source data:

5.1 Connected devices with bus capacitance

Every PROFIBUS node has a transceiver ASIC (e.g., Siemens SPC3, VPC3+, LSPM2; Turck interface ASICs in TBEN, FDN, BL20 gateways) with a bus-side capacitance of typically 15-60 pF per node. With all stations powered down but still connected to the bus, the BT200 must charge this distributed capacitance through the test pulse. The charging curve produces a reflection that the BT200's TDR correlator can interpret as a segment end.

This is the single most common cause of the 2x reading. It is amplified when many devices (typical Turck I/O segments: gateway + multiple I/O slices) are daisy-chained on a stub-free trunk.

5.2 Turck field I/O specific behavior

Turck multiprotocol gateways (TBEN-S, TBEN-L, FDN, BL20) include internal bus termination that remains in-circuit when the device is de-energized, plus input-filter capacitance on the PROFIBUS port. The combination produces a reflection profile that, in field measurements, consistently falls at roughly twice the physical segment length when the BT200's default 187.5 kBaud pulse is used.

5.3 Stubs and T-drop topology

Each drop cable (T-drop) to a field device acts as an unterminated stub. Stubs longer than ~0.3 m at 12 MBaud or ~3 m at 1.5 MBaud produce visible reflections. The BT200 reads the first major stub reflection and stops the distance search, which can fall on a stub rather than the segment end - and the round-trip to the stub and back to the BT200 is approximately twice the trunk distance to that device.

5.4 Repeaters and OLM in segment

Repeaters (Siemens RS 485 Repeater, 6ES7 972-0AA01-0XA0) and OLMs electrically isolate segments. The BT200 cannot see past an active or passive repeater. If a repeater is in-line but powered, the BT200 will report the distance to the repeater, which on a typical 36 m segment can be ~70-90 m depending on the repeater's position.

5.5 Power-on residual capacitance

Devices left in their normal powered state during the test force the BT200 to charge device power supplies, bus drivers, and DC-DC converter input caps. The resulting current draw distorts the TDR pulse and can shift the apparent end of cable. The source data confirms this: repeating the test on the same physical segment produces different results because device power states are inconsistent between runs.

6. Step-by-Step Troubleshooting Procedure

Use this matrix in field order. Each step takes < 5 minutes.

7. Cross-Verification with SIMATIC Step 7 / TIA Topology

The Siemens Topology Editor in STEP 7 V5.x (and TIA Portal's Topology view) infers cable lengths from the port-to-port delay of live PROFIBUS DP frames. It is a statistical measurement, not a TDR measurement, so it is not affected by the same capacitive loading that fools the BT200.

Procedure:

1. Open the PROFIBUS DP master project in STEP 7 / TIA Portal.
2. Select the bus, right-click, choose "PROFIBUS - Topology".
3. Read the inferred run length for the segment in question.
4. Compare with the BT200 result.

Typical STEP 7 topology reading accuracy: ±0.5 m on runs up to 100 m, sufficient for engineering acceptance. Use it as the authoritative length whenever BT200 and BT200 disagree.

8. Field-Confirmed Fixes

8.1 Isolate the segment under test

Disconnect all device bus connectors (Sub-D, M12) except the BT200 test plug at the far end. The BT200 will then read the bare copper run. Once the bare-run length is verified, reconnect devices one by one to find the source of the spurious reflection.

8.2 Verify the test plug

Use only the manufacturer-supplied BT200 test plug (delivered as part of the BT200 starter kit, designed to be a matched 150 Ω termination). Aftermarket Sub-D terminators (commonly 120 Ω, 220 Ω, or with parallel capacitor) can produce reflections that fall at multiples of the actual run length and were observed to generate the 88 m / 36 m split in the source data.

8.3 Use a higher baud rate for the BT200 measurement

Select 1.5 MBaud or 12 MBaud test rate in the BT200 menu. The faster pulse has a shorter rise time and a higher resolution. Capacitive low-pass effects of connected devices are less able to distort the leading edge. The 12 MBaud setting is the recommended mode for final acceptance testing on segments with multiple field devices.

8.4 Insert a repeater for measurement purposes

If the segment must be measured in its operational state with all devices connected, install a temporary repeater (Siemens 6ES7 972-0AA01-0XA0) at the BT200 end of the segment. The repeater isolates the BT200 from the device-side capacitance. Note: this changes the bus topology, so the segment must be returned to its original state after measurement.

8.5 Replace problematic Turck I/O interfaces

Where doubling is consistently reproducible with a specific Turck gateway model, contact Turck support for a revision check. Some early TBEN-S2-EP revisions had a higher bus-side capacitance specification than the successor hardware. Replacing the gateway with a current revision typically resolves the doubling without further action.

8.6 Check for mid-segment power injection

Repeater power supplies and OLM power feeds inject small DC bias onto the bus. This can shift the BT200's pulse threshold and create an apparent reflection. Measure with the segment fully de-energized including any 24 V bus terminator power supplies.

9. Prevention and Long-Term Best Practices

• Maintain an as-built cable schedule with measured lengths, baud rate, and connector count. Cross-check on every new build using both BT200 and STEP 7 Topology.
• Avoid mixing manufacturers on a single PROFIBUS DP trunk. Turck, Siemens, Beckhoff, and Wago gateways have different bus-capacitance profiles. Mixing increases the chance of BT200 measurement artifacts.
• Keep stub length to the PROFIBUS installation guidelines: < 0.3 m at 12 MBaud, < 1 m at 1.5 MBaud, < 3 m at 500 kBaud and below. Long stubs are the dominant source of TDR artifacts.
• Use a PROFIBUS cable marker to record the actual measured length on the cable jacket (e.g., "36.2 m / BT200 / 12 MBaud / 2024-03"). This serves as a reference for future maintenance.
• Train commissioning engineers to always run BT200 measurements with all stations physically disconnected at the bus connector, not just powered down. This is the only way to remove the dominant capacitive contamination.
• For new installations, specify a single termination topology: terminated end (BT200 test plug) at one end, BT200 at the other end, and no terminator power. This is the BT200's expected topology and the one in which its measurements are most accurate.
• Log every BT200 measurement with date, baud rate, parameter entries, and which devices were connected. A trend of stable readings over time is a better health indicator than any single shot.

10. Diagnostic Flowchart

11. Specifications and Limits Reference

12. FAQ