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.

⥠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 Recommendation | Binary rate (bit/s) | Modulation type | Duplex capability | Transmission mode |
|---|---|---|---|---|
| V.22 | 1,200 (fallback to 600) | DPSK (differential phase shift keying) | Fullâduplex | Synchronous or asynchronous |
| V.22bis | 2,400 (fallback to 1,200) | QAM (16âpoint) | Fullâduplex | Synchronous |
| V.23 | 1,200/75 (splitâspeed) | FSK (frequency shift keying) | Halfâduplex (primary), simplex (backward) | Asynchronous |
| V.27ter | 4,800 (fallback to 2,400) | 8âphase DPSK | Halfâduplex or fullâduplex | Synchronous |
| V.29 | 9,600 (fallback 7,200/4,800) | 16âpoint QAM | Halfâduplex | Synchronous |
(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 DPSK | 1,200 | 1,200 (or 600) | 40 | 15 | 2.0 |
| V.22bis QAM | 2,400 | 1,800 | 38 | 17 | 1.5 |
| V.23 FSK | 1,200/75 | 1,300 (mark), 2,100 (space) | 42 | 14 | 2.5 |
| V.27ter 8âphase DPSK | 4,800 | 1,800 | 35 | 18 | 1.2 |
| V.29 16âpoint QAM | 9,600 | 1,700 | 30 | 20 | 1.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.
| Parameter | UIC 911â4 (1983) | ITUâT V.22 / V.29 (1988) |
|---|---|---|
| Scope | Railwayâspecific: modems + transmission lines + link control + line qualification | Modem modulation and functional characteristics only; no transmission line or link control |
| Mandatory line quality measurement | Yes â attenuation, group delay, SNR must be measured on every link before commissioning | No â assumed that telephone network meets general voiceâband requirements |
| Maximum line length for 0.9âŻmm copper at 9,600âŻbit/s | 25âŻkm without repeaters, 50âŻkm with one repeater | Not specified |
| Bit error rate (BER) requirement | â€âŻ10â»â” for telemetry, â€âŻ10â»â· for safetyârelated data | Not specified |
| Environmental requirements (EMC, temperature, vibration) | Reference to UIC 550 (thermal) and IEC 61000â4 (EMC) for wayside equipment | None â not railwayâspecific |
| Superseded by? | Not formally superseded, but functionally replaced by Ethernet/TSN for new designs | V.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).
