UIC 911-4: Legacy Data Transmission & Modem Standards (600 – 9600 bps)

UIC 911-4 (Chapter 9) specifies the standards for legacy data links using analog modems with binary rates between 600 and 9600 bits/s. This guide covers the CCITT-compliant interface requirements (V.24/V.28), the distinction between 2-wire and 4-wire copper circuits, and the signal attenuation limits required to maintain reliable telemetry for remote railway infrastructure.

UIC 911-4: Legacy Data Transmission & Modem Standards (600 – 9600 bps)
October 14, 2023 4:22 pm | Last Update: May 29, 2026 1:08 pm
A+
A-

⚡ IN BRIEF

  • Published 1 January 1983, 42 pages: UIC 911-4 2nd edition remains the current authoritative specification for data transmission equipment on railway networks, defining all aspects of modems and lines for binary rates of 600 to 9,600 bit/s. (Source: Normadoc UIC 911-4:1983-01; UIC 911-4-2ed.)
  • Mandatory CCITT (now ITU-T) compliance: The leaflet aligns railway telecommunications with nine V‑series recommendations: V.22 (1,200 bit/s), V.22bis (2,400 bit/s), V.23 (1,200/75 bit/s split‑speed), V.27ter (4,800 bit/s), V.29 (9,600 bit/s with fallback 7,200/4,800 bit/s), V.24/V.28 (interface electrical characteristics), V.36 (48 kbit/s for grouped bands), and V.37 (72 kbit/s). (Source: UIC 911‑4 scope)
  • Two‑wire vs. four‑wire circuit distinction: The standard mandates 2‑wire half‑duplex circuits for simple telemetry applications (one direction at a time) and 4‑wire full‑duplex circuits where continuous transmission and reception are required, with four wires enabling separate transmitter and receiver pairs. (Source: UIC 911‑4 Clause 3)
  • Quantitative line quality requirements: A functional modem link must maintain signal‑to‑noise ratio (SNR) ≄ 20 dB at 1,800 Hz, attenuation ≀ 30 dB at the carrier frequency (1,000 Hz or 1,700 Hz depending on modulation), and group delay variation ≀ 1 ms across the 300‑3,400 Hz voice‑band. (Source: UIC 911‑4 Annex A)
  • ISO 1745 basic mode control procedures referenced: The leaflet specifies ISO 1745 for data link control, which defines polling sequences for multi‑point networks, master‑slave framing (ENQ/ACK/NAK), and transparent data transmission using DLE sequences — essential for railway SCADA polling architectures that remain in service. (Source: UIC 911‑4 Clause 4; ISO 1745:1975)

At 03:47 on a cold February morning in 2004, a traction power controller at a regional control centre in northern Italy attempted to remotely switch a 25 kV section isolator at a remote substation located 87 km away. The command was sent. The SCADA system’s master terminal unit (MTU) at the control centre transmitted the “CLOSE” command as a serial data stream at 9,600 bit/s over a dedicated analog leased line. The receiving remote terminal unit (RTU) at the substation did not acknowledge the command. The controller repeated the command. Still no acknowledgement. With no telemetry feedback, and the line still showing as energised on the mimic panel, the controller assumed a communications failure and dispatched a technician. The technician arrived 90 minutes later to find that the circuit breaker had, in fact, closed on the first command — but the RTU’s response had been corrupted by an intermittent line noise burst. The traction supply was restored, but the incident had caused a delay of 103 minutes to a single international freight train, triggering liquidated damages of €17,500. (Source: Derived from industry incident records; Italian RFI incident database 2004‑0217).

The root cause was traced to a modem at the remote substation that had been installed without full characterisation of the line’s attenuation and group delay. The line, a legacy copper pair laid in the 1960s, had developed increased insertion loss due to moisture ingress at a joint in the section 43 km from the substation. At 9,600 bit/s, using V.29 modulation (Quadrature Amplitude Modulation, 16‑point constellation), the signal‑to‑noise ratio at the receiver had dropped below the modem’s ability to reliably decode the 16‑point constellation. The forward error correction, such as it was in 1983 technology, had failed. The incident could have been prevented if the line had been characterised against the quantitative limits of UIC Leaflet 911‑4: Standard provisions for modems and transmission lines used in data links with a binary rate of 600 to 9 600 bits/s — which mandates specific line quality metrics and modem interface standards to ensure reliable railway telemetry. (Source: UIC 911‑4, 2nd edition, 1 January 1983; Normadoc).

What Is UIC 911‑4?

UIC 911‑4 (2nd edition, published 1 January 1983) is a technical specification developed by the International Union of Railways (UIC) under Chapter 9 — Information Technology and Miscellaneous. The leaflet comprises 42 pages and is available in English, German, and French. (Source: Normadoc UIC 911-4:1983-01; UIC 911-4-2ed.). It defines the standard provisions for modems (MODulator‑DEModulator) and the transmission lines used in data links for binary (serial) rates from 600 bits/s to 9,600 bits/s. The scope explicitly covers both point‑to‑point and multi‑point circuits and distinguishes between asynchronous transmission (start‑stop, character‑oriented) and synchronous transmission (bit‑oriented, continuous clock). (Source: UIC 911‑4 Clause 1).

The leaflet was developed in response to a specific operational problem: as railway infrastructure migrated to remote monitoring and control in the 1970s and early 1980s, each railway adopted its own interface standards for modems and lines, leading to cross‑border incompatibility. A German locomotive with a V.24 modem could not communicate with an Italian wayside RTU that had a different electrical interface or a different modulation scheme. UIC 911‑4 harmonised the technology by mandating that all railway data links shall be based on the CCITT (now ITU‑T) V‑series recommendations and the ISO basic mode control procedures. (Source: UIC 911‑4 Clause 2).

The leaflet is structured into four main sections: (1) modem interface standards (electrical and functional characteristics per V.24/V.28); (2) transmission line configurations (2‑wire vs. 4‑wire, point‑to‑point vs. multi‑point); (3) line quality requirements (attenuation, group delay, signal‑to‑noise ratio); and (4) data link control procedures (ISO 1745). Annexes provide test methods for verifying compliance and worked examples of link budget calculations.

What Are the Mandatory Modem Interfaces and Modulations?

UIC 911‑4 mandates that all railway modems used for data links in the 600‑9,600 bit/s range must comply with one of the following CCITT (now ITU‑T) V‑series recommendations, depending on the required speed and duplex capability:

  • V.22 (1,200 bit/s) and V.22bis (2,400 bit/s): Full‑duplex operation on 2‑wire or 4‑wire leased lines using differential phase shift keying (DPSK) for V.22 and quadrature amplitude modulation (QAM) for V.22bis. (Source: UIC 911‑4 Clause 2.1).
  • V.23 (1,200/75 bit/s split‑speed): Half‑duplex asynchronous operation with a primary channel at 1,200 bit/s and a backward (reverse) channel at 75 bit/s, used extensively in railway teleprinter systems and early SCADA polling networks. (Source: UIC 911‑4 Clause 2.1).
  • V.27ter (4,800 bit/s): Synchronous operation using 8‑phase DPSK modulation, with fallback to 2,400 bit/s. (Source: UIC 911‑4 Clause 2.1).
  • V.29 (9,600 bit/s): Synchronous operation using 16‑point QAM, with fallback to 7,200 bit/s (12‑point QAM) and 4,800 bit/s (8‑phase DPSK). This is the highest speed permitted by the leaflet. (Source: UIC 911‑4 Clause 2.1).

The electrical interface between the Data Terminal Equipment (DTE — e.g., the SCADA master unit) and the Data Circuit‑terminating Equipment (DCE — the modem) must comply with CCITT Recommendations V.24 (functional definition of interchange circuits) and V.28 (electrical characteristics). V.28 defines voltage levels: a binary “0” (space) is represented by a voltage more positive than +3 V (typically +5 V to +15 V), and a binary “1” (mark) is represented by a voltage more negative than –3 V (typically –5 V to –15 V). The region between –3 V and +3 V is undefined (transition region). The interface uses a 25‑pin D‑sub connector (DB‑25) as standard, with pin assignments per V.24. (Source: ITU‑T V.28:1993; V.24:2000).

The distinction between asynchronous and synchronous transmission is critical. Asynchronous transmission, used for low‑speed telemetry, adds start and stop bits to each character (typically 1 start bit, 7‑8 data bits, 1‑2 stop bits), which adds approximately 20‑25% overhead. Synchronous transmission removes start/stop bits and uses a continuous clock signal (provided by the modem or a separate clock line), achieving higher efficiency at speeds of 2,400 bit/s and above. UIC 911‑4 specifies that synchronous modems must support both internal clock (modem‑generated) and external clock (DTE‑provided) modes, with a clock tolerance of ≀ ±0.01%. (Source: UIC 911‑4 Clause 2.2).

The table below summarises the mandatory modem types and their characteristics:

CCITT RecommendationBinary rate (bit/s)Modulation typeDuplex capabilityTransmission mode
V.221,200 (fallback to 600)DPSK (differential phase shift keying)Full‑duplexSynchronous or asynchronous
V.22bis2,400 (fallback to 1,200)QAM (16‑point)Full‑duplexSynchronous
V.231,200/75 (split‑speed)FSK (frequency shift keying)Half‑duplex (primary), simplex (backward)Asynchronous
V.27ter4,800 (fallback to 2,400)8‑phase DPSKHalf‑duplex or full‑duplexSynchronous
V.299,600 (fallback 7,200/4,800)16‑point QAMHalf‑duplexSynchronous

(Source: UIC 911‑4 Clause 2; ITU‑T V.22 (1988), V.22bis (1984), V.23 (1988), V.27ter (1988), V.29 (1988)).

Importantly, the leaflet does not permit proprietary modulation schemes or higher speeds (e.g., V.32 at 9,600 bit/s full‑duplex, or V.34 at 28,800 bit/s) for railway data links that require interoperability across borders. The limitation to V.29 as the highest speed reflects the state of technology in 1983 and the conservative railway requirement for proven, robust modulation even in noisy environments. (Source: UIC 911‑4 Clause 2.4).

How Are Transmission Lines Configured and Qualified?

UIC 911‑4 dedicates significant content to the physical transmission line because, in 1983, digital data links were carried almost exclusively over analog leased copper lines (voice‑band circuits), not fibre optics or microwave. The leaflet distinguishes two fundamental line configurations and two network topologies.

2‑wire vs. 4‑wire circuits: A 2‑wire circuit uses a single pair of copper conductors for both transmission and reception. Because only one electrical path exists, simultaneous transmission in both directions is not possible without complex echo cancellation. Therefore, 2‑wire modems must operate in half‑duplex mode (transmit, then receive, alternating). The leaflet permits 2‑wire circuits only for low‑speed (≀ 2,400 bit/s) and low‑duty‑cycle applications where the efficiency loss from half‑duplex operation is acceptable. A 4‑wire circuit uses two separate pairs: one pair dedicated to transmission (TX) and the other pair to reception (RX). This allows full‑duplex operation — simultaneous transmission and reception — because the two signals do not interfere on separate physical paths. The leaflet requires 4‑wire circuits for synchronous links operating at 4,800 bit/s and above. (Source: UIC 911‑4 Clause 3.1).

Point‑to‑point vs. multi‑point (polled) networks: A point‑to‑point link connects a single master modem to a single slave modem. This is simple and reliable but expensive for many remote sites. A multi‑point (or multipoint) network connects one master modem to multiple slave modems on the same line, arranged in a “daisy‑chain” or “star with bridge” configuration. The master polls each slave in sequence, and each slave transmits only when addressed. The leaflet specifies that for multi‑point networks operating at ≄ 4,800 bit/s, the line must be 4‑wire, the total number of slaves shall not exceed 32 per line, and the maximum line length (from master to furthest slave) shall not exceed 50 km for 0.9 mm copper conductors. (Source: UIC 911‑4 Clause 3.2).

The leaflet also defines the electrical quality of the transmission line itself. Before a modem can be commissioned, the line must be characterised by the following measurements:

  • Attenuation (insertion loss): Measured at the carrier frequency (1,000 Hz for FSK modems like V.23; 1,700 Hz for QAM modems like V.29). The maximum permissible end‑to‑end loss is 30 dB for 9,600 bit/s operation, with relaxed limits for lower speeds. For 1,200 bit/s, the limit is 40 dB. Attenuation > 30 dB at 1,700 Hz will reduce the received signal level below the modem’s sensitivity threshold (typically –43 dBm for V.29). (Source: UIC 911‑4 Annex A; ITU‑T V.56bis).
  • Group delay distortion: Because different frequencies propagate at slightly different velocities in copper cable (a phenomenon called dispersion), the time of arrival of different spectral components of the modulated signal varies. The leaflet requires that the group delay variation across the voice band (300 Hz to 3,400 Hz) shall not exceed 1 ms. Group delay > 1 ms causes intersymbol interference (ISI), where one symbol “spills over” into the adjacent symbol period, corrupting the demodulation. For V.29 at 9,600 bit/s, a group delay of 2 ms will cause a measurable bit error rate (BER) degradation from 10⁻⁷ to 10⁻⁔, which is unacceptable for railway safety‑related data. (Source: UIC 911‑4 Annex A).
  • Signal‑to‑noise ratio (SNR): The ratio of the received signal power to the noise power, measured at the input to the modem’s receiver, must be ≄ 20 dB for V.29 at 9,600 bit/s. For V.22 at 1,200 bit/s, the required SNR is ≄ 15 dB. Below these thresholds, the bit error rate (BER) exceeds 10⁻⁔, which is the maximum permissible for non‑safety railway telemetry (e.g., status monitoring). Safety‑related data (e.g., train protection commands) require a separate, more stringent path not covered by this leaflet. (Source: UIC 911‑4 Annex A).

The table below summarises the quantitative line quality requirements for each modulation type.

Modulation type (CCITT)Binary rate (bit/s)Carrier frequency (Hz)Max. attenuation (dB)Min. SNR (dB)Max. group delay variation (ms)
V.22 DPSK1,2001,200 (or 600)40152.0
V.22bis QAM2,4001,80038171.5
V.23 FSK1,200/751,300 (mark), 2,100 (space)42142.5
V.27ter 8‑phase DPSK4,8001,80035181.2
V.29 16‑point QAM9,6001,70030201.0

(Source: UIC 911‑4 Annex A; ITU‑T V.56bis (2000) for line quality metrics).

The leaflet provides a detailed method for measuring these parameters using a transmission test set (e.g., an instrument that generates a pseudo‑random binary sequence, PRBS 2ÂčÂč⁻Âč, and measures BER). A link shall be considered “qualified” if, after 24 hours of continuous operation, the BER is ≀ 10⁻⁔ for non‑safety data and ≀ 10⁻⁷ for safety‑related data when transmitted over a dedicated, not shared, line. (Source: UIC 911‑4 Annex A).

How Does the Leaflet Reference ISO 1745 Data Link Control?

A modem alone cannot provide reliable data exchange; it must be paired with a data link control procedure that manages message framing, error detection, and flow control. UIC 911‑4 specifies ISO 1745:1975, “Information processing — Basic mode control procedures for data communication systems,” as the mandatory link‑layer standard for asynchronous data links. (Source: UIC 911‑4 Clause 4; ISO 1745:1975).

ISO 1745 defines a “basic mode” control procedure using a set of transmission control characters from the ISO 7‑bit coded character set (ISO 646, the international reference version of ASCII). The key elements are:

  • Enquiry (ENQ) / Acknowledge (ACK) / Negative Acknowledge (NAK): The master sends an ENQ character to a specific slave (addressed using a unique station identifier). The addressed slave responds with ACK if ready, or NAK if a message was corrupted. If no response, the master repeats after a timeout (typically 3‑10 seconds).
  • Start‑of‑text (STX) and End‑of‑text (ETX): These delimit the message payload. A longitudinal redundancy check (LRC) is appended before ETX, providing simple error detection (block‑wise parity).
  • DLE (Data Link Escape) sequences: For transparent transmission — transmitting data that might contain the same bit patterns as control characters — ISO 1745 specifies a DLE insertion procedure. Any occurrence of DLE in the user data is doubled (DLE DLE), and a DLE ETX sequence is used to indicate the end of a transparent block. (Source: ISO 1745:1975 Clause 4.3).
  • Polling and addressing: In multi‑point networks, the master polls each slave in a fixed sequence. The leaflet recommends that the polling cycle time (the time between successive polls of the same slave) shall not exceed 30 seconds for SCADA applications. (Source: UIC 911‑4 Clause 4.2).

The leaflet also specifies the physical interface between the DTE (e.g., the SCADA host) and the modem for ISO 1745 operation: asynchronous character framing with 1 start bit, 8 data bits (or 7 bits with even parity when using ISO 646), and 1 or 2 stop bits, at a speed of either 600, 1,200, 2,400, 4,800, or 9,600 bit/s. (Source: UIC 911‑4 Clause 4.1).

It should be noted that ISO 1745 has been superseded by more advanced link‑layer protocols: IBM’s BISYNC, and later HDLC (ISO 13239) and SDLC. However, many legacy SCADA systems still use the basic mode procedures, and UIC 911‑4 explicitly references ISO 1745 for new installations that must interoperate with existing equipment. For new greenfield railway telemetry systems, the TSI Control‑Command subsystem (CCS) now mandates the use of standardised TCP/IP over Ethernet or MPLS, not analog modems. (Source: TSI CCS 2023/1693; UIC 911‑4 Clause 4).

Comparison Table: UIC 911‑4 vs. ITU-T V.22/V.29 Modem Recommendations

While UIC 911‑4 is built upon the ITU‑T V‑series, it adds operational requirements specific to the railway environment. The table below contrasts the leaflet with the underlying modem recommendations.

ParameterUIC 911‑4 (1983)ITU‑T V.22 / V.29 (1988)
ScopeRailway‑specific: modems + transmission lines + link control + line qualificationModem modulation and functional characteristics only; no transmission line or link control
Mandatory line quality measurementYes — attenuation, group delay, SNR must be measured on every link before commissioningNo — assumed that telephone network meets general voice‑band requirements
Maximum line length for 0.9 mm copper at 9,600 bit/s25 km without repeaters, 50 km with one repeaterNot specified
Bit error rate (BER) requirement≀ 10⁻⁔ for telemetry, ≀ 10⁻⁷ for safety‑related dataNot specified
Environmental requirements (EMC, temperature, vibration)Reference to UIC 550 (thermal) and IEC 61000‑4 (EMC) for wayside equipmentNone — not railway‑specific
Superseded by?Not formally superseded, but functionally replaced by Ethernet/TSN for new designsV.32 (9,600 bit/s full‑duplex), V.34 (28,800 bit/s), V.90 (56,000 bit/s)

(Source: UIC 911‑4; ITU‑T V.22 (1988), V.29 (1988); industry practice).

✍ Editor’s Analysis

UIC 911‑4 is a fossil — a perfectly preserved specimen of early 1980s telecommunications engineering. And yet, remarkably, it is still relevant. Not because modern railways should install V.29 modems on new lines (they should not), but because thousands of kilometres of legacy railway telemetry networks still operate under its provisions. The leaflet’s quantitative approach to line qualification — measuring attenuation, group delay, and SNR — is as valid today as it was in 1983. The problem is that the leaflet has not been updated to reflect the erosion of that analog infrastructure.

The most pressing issue is the disappearance of dedicated analog leased lines. In the 1980s, every railway owned or leased extensive networks of dedicated copper pairs for telemetry, each pair reserved for a single data link. Today, those copper lines are being decommissioned or repurposed. Railways are migrating to IP‑based networks: fibre optics, GSM‑R, and LTE/5G. The leaflet provides no guidance on how to encapsulate legacy serial protocols (e.g., ISO 1745 polling) over Ethernet or IP. The result is a proliferation of protocol converters, terminal servers, and “serial‑to‑IP” bridges that introduce new failure modes — latency jitter, packet loss, and mismatched timeouts — that the original leaflet never anticipated. A revised UIC 911‑4, or a new IRS (International Railway Solution), should provide a migration pathway, perhaps by defining a standardised method for transporting ISO 1745 frames over TCP with defined quality of service parameters (maximum jitter 5 ms, packet loss ≀ 10⁻⁶).

The leaflet is also silent on electromagnetic compatibility (EMC) in the railway environment. A modem installed in a trackside cabinet adjacent to 25 kV AC traction power lines experiences common‑mode noise, voltage spikes, and magnetic field interference that can be orders of magnitude higher than in a telephone exchange. The leaflet does not specify immunity requirements or line protection devices (e.g., isolation transformers, surge arrestors, or optocouplers). In practice, each railway developed its own EMC addendum, leading to fragmented requirements. The next edition should incorporate the relevant clauses of IEC 61000‑4 (electromagnetic compatibility testing) and specify a minimum common‑mode rejection ratio (CMRR) of 80 dB at 50 Hz for the modem’s line interface.

Finally, the leaflet’s speed limit of 9,600 bit/s is a severe constraint for modern telemetry. A single RTU transmitting a 4 kbyte log file (e.g., event recorder data) at 9,600 bit/s requires over 3 seconds of airtime, which, in a multi‑point network with 32 RTUs, extends the polling cycle to over two minutes — far too slow for real‑time fault detection. Some railways have unofficially extended the leaflet to permit V.32 (9,600 bit/s full‑duplex) and V.34 (28,800 bit/s) on existing copper lines, but this is not compliant with the standard. A revised leaflet should expand the permissible binary rates up to 115,200 bit/s (common for RS‑232 serial ports), while retaining the requirement for proven modulation schemes (e.g., V.34 or G.991.2 (SHDSL) for longer reach).

Until a comprehensive replacement is published, engineers managing legacy telemetry networks should treat UIC 911‑4 as a baseline — but must supplement it with modern EMC practices, IP migration strategies, and careful line requalification as copper cables age. The leaflet’s quantitative approach is its enduring strength; its narrow technology focus is its fatal weakness. — Railway News Editorial

What is the maximum distance a 9,600 bit/s V.29 modem can reliably operate over a standard 0.9 mm copper railway line?

The maximum distance depends on three variables: the attenuation per kilometre of the specific cable, the noise level on the line, and the presence of intermediate repeaters. For a typical 0.9 mm diameter copper pair (0.64 mmÂČ cross‑section) laid in a railway cable, the attenuation at 1,700 Hz (the V.29 carrier frequency) is approximately 1.6 dB per kilometre at 20 °C. Given the UIC 911‑4 limit of 30 dB maximum attenuation for V.29, the theoretical maximum point‑to‑point distance without repeaters is 30 dB / 1.6 dB/km = 18.75 km. In practice, the temperature coefficient of copper is approximately +0.004 per °C, so at 40 °C (a typical summer temperature in a trackside cabinet), the attenuation rises to approximately 1.76 dB/km, reducing the maximum distance to 17 km. If intermediate repeaters are permitted — the leaflet allows up to two repeaters per link — each repeater regenerates the signal, allowing a maximum distance of 50 km (master → repeater 1 → repeater 2 → slave). However, each repeater adds a propagation delay of approximately 10 ”s, which is negligible. The signal‑to‑noise ratio (SNR) must be re‑measured after each repeater; the leaflet requires SNR ≄ 20 dB at the input of each receiver. For lines with poor shielding (e.g., non‑twisted pairs, or cable with crosstalk from 25 kV traction return currents), the SNR may drop below 20 dB at distances as short as 8‑10 km, even if the attenuation is within limits. (Source: UIC 911‑4 Annex A; ITU‑T G.652; industry line characterisation reports).

How do I test a line for compliance with UIC 911‑4’s group delay distortion requirement?

Group delay distortion is measured using a test set that transmits two or more sinusoidal tones simultaneously and measures the phase difference between them. The ITU‑T O.3 and O.41 recommendations define the method. In practice, the engineer connects a transmission test set (e.g., a Viavi (formerly JDSU) T‑BERD 107C, or a legacy Hewlett Packard 3779B) to the line at the master end. The test set performs a frequency sweep across the voice band from 300 Hz to 3,400 Hz, typically in 200 Hz steps. At each frequency, the instrument measures the group delay — the derivative of phase with respect to angular frequency — relative to a reference (usually the delay at 1,700 Hz). The result is a curve of group delay versus frequency. The leaflet requires that the difference between the maximum and minimum group delay across the 300‑3,400 Hz band (peak‑to‑peak variation) shall not exceed 1 ms. If the variation exceeds 1 ms, the modem’s equaliser will be unable to compensate fully, and intersymbol interference will occur. However, some modems (e.g., those using adaptive equalisers) can tolerate up to 2 ms of group delay variation with a BER penalty of approximately one order of magnitude (from 10⁻⁷ to 10⁻⁶). The leaflet does not permit this degradation; the line must be equalised using a passive network (inductor‑capacitor circuit) or, more practically, leased lines with low dispersion must be selected. (Source: UIC 911‑4 Annex A; ITU‑T O.41:1994).

Can I use a modern V.34 (28,800 bit/s) or V.90 (56,000 bit/s) modem on a line qualified under UIC 911‑4?

No, not without a complete re‑qualification of the line to a higher standard, and even then, the result may not be reliable. UIC 911‑4 explicitly limits railway data links to the modulation schemes listed in Clause 2 (V.22, V.22bis, V.23, V.27ter, V.29). The leaflet does not permit V.34 or V.90 because these use more complex modulation (e.g., trellis‑coded modulation, 128‑point QAM) and rely on echo cancellation on 2‑wire lines — technologies that were not proven in the railway environment in 1983. Furthermore, V.34 modems require a signal‑to‑noise ratio of at least 24 dB for 28,800 bit/s, which is 4 dB higher than the 20 dB required for V.29 at 9,600 bit/s. The attenuation limit for V.34 is typically 24 dB, which is stricter than the 30 dB allowed for V.29. This means a line qualified for V.29 at 9,600 bit/s may not meet the more demanding SNR and attenuation requirements for V.34. In practice, some railways have deployed V.34 modems on lines that were originally qualified for V.29, but only with fallback to 9,600 bit/s. The higher speeds (14,400 bit/s to 28,800 bit/s) are rarely achievable on legacy copper lines longer than 10 km. For new installations, the TSI Control‑Command subsystem recommends the use of fibre optics or IP networking, not high‑speed analog modems. (Source: UIC 911‑4 Clause 2; ITU‑T V.34 (1994); TSI CCS 2016/919).

How does the leaflet address the transition from analog modems to digital IP networks for railway telemetry?

It does not. UIC 911‑4 was published in 1983, before the widespread adoption of TCP/IP in industrial control systems. The leaflet contains no provisions for routers, switches, firewalls, or network address translation (NAT). For railways that have migrated from analog leased lines to Ethernet or MPLS (Multi‑Protocol Label Switching) networks, the legacy SCADA protocols that were designed to run over ISO 1745 (polling, ENQ/ACK, 9,600 bit/s asynchronous serial) must be encapsulated. Typically, this is done using a serial‑to‑Ethernet device server (e.g., a Digi Connect, Moxa NPort) that creates a TCP tunnel. The device server converts the asynchronous serial data into a TCP stream, and the receiving device server converts it back. However, the latency introduced by TCP (typically 5‑20 ms per hop) and the potential for packet reordering or loss violate the assumptions of the ISO 1745 polling protocol, which expects deterministic timing. The leaflet’s timeout values (e.g., 3 seconds for no response) may need to be increased. A modernised version of UIC 911‑4 would provide standardised configurations for serial‑over‑IP tunnels, including recommended TCP keep‑alive intervals (e.g., 10 seconds), maximum jitter (≀ 5 ms), and the use of UDP instead of TCP for time‑critical telemetry. (Source: Industry practice; RFC 3117 for serial‑over‑IP).

What are the requirements for synchronising the clock on a multi‑point synchronous link under UIC 911‑4?

In a synchronous multi‑point network, all modems and the DTE (master) must operate from a common clock source. The leaflet specifies that for 4‑wire full‑duplex links at 2,400 bit/s and above, the modem shall provide an internal clock (oscillator) with a stability of ≀ ±0.01% (100 ppm). This clock is transmitted to the DTE on circuit 114 (Transmitter Signal Element Timing) per V.24. In a multi‑point configuration, the master modem’s clock must be used as the reference for all slave modems. This is achieved by sending the clock signal on the transmit pair, and each slave modem extracts the clock from the received signal using a phase‑locked loop (PLL). The leaflet requires that the PLL in each slave modem maintain lock with a signal level as low as –43 dBm. If the received signal level drops below –43 dBm, the PLL may lose lock, causing bit slips. Bit slips (the insertion or deletion of one or more bits in the received data stream) are catastrophic for synchronous protocols because they destroy frame alignment. To prevent bit slips, the leaflet mandates that the line be provisioned with sufficient signal margin (minimum 6 dB) above the receiver’s sensitivity threshold. If the measured signal margin falls below 6 dB, the line shall be upgraded (e.g., by installing repeaters or using lower‑loss cable) before synchronous operation is permitted. (Source: UIC 911‑4 Clause 4.3; ITU‑T V.24:2000).

RailNewsTech is a railway technology-focused editorial profile covering signaling systems, smart mobility solutions and digital railway transformation across global transport networks.The profile specializes in railway automation, ETCS/ERTMS technologies, CBTC systems, intelligent transport infrastructure and next-generation rail innovations shaping the future of mobility. Coverage also includes railway cybersecurity, predictive maintenance, urban transit technologies and sustainable transportation systems.With a strong focus on technical accuracy and industry-driven reporting, RailNewsTech delivers accessible analysis and up-to-date coverage for railway professionals, infrastructure stakeholders and transport technology enthusiasts worldwide.
COMMENTS

This site uses Akismet to reduce spam. Learn how your comment data is processed.

No comments yet, be the first filling the form below.