Knowledge base: Download Area > XRA-31
XRA-31 5.2 Changelog
Posted by Dieter Dobbelaere, Last modified by Dieter Dobbelaere on 20 June 2022 09:50 AM


We are very excited to announce this release of the XRA-31 system!

This version extends capture filtering capabilities to further reduce the size of capture files.
Moreover, all core software components (Debian GNU/Linux, Wireshark) are upgraded to their latest stable upstream versions.

Furthermore this release has several stability and bug fixes.

New since 5.2!

Extended capture filtering with the following new packet types:

  • SYNC,
  • MAP on reference channel and
  • MAP on non-reference channel.

Changelog 5.2.2-1664 (2022-04-05)


  • [Firmware] Fixed critical issue with OFDMA equalizer that caused considerable packet loss for pilot patterns 1-3 and 8-10.
  • [Firmware] Fixed critical bug in downstream SC-QAM phase equalizer that was the source of occasional packet loss.
  • [System] Fixed support archives functionality.
  • [System] Fixed issue where codeword metadata of downstream SC-QAM packets was sometimes duplicated.
  • [System] Improved responsiveness of capture stop action if a large capture file has to be replaced.
  • [GUI] Fixed issue with capture button that does not respond after changing capture configuration.

Changelog 5.2-1661 (2021-11-08)


  • [System] Upgraded operating system to Debian 11 (bullseye).
  • [System] Switched to more versatile network manager.
  • [System] Support data disks formatted as XFS for improved performance.
  • [Wireshark] Upgraded on-system Wireshark version to v3.4.8.


  • [System] Improved rolling file switchover performance (also fixes potential data loss for high loads).
  • [System] Fixed accuracy and drift issues of duration-based capture/file stop criterion.
  • [System] Fixed issue where OFDMA initial and fine ranging bursts are missing if there are multiple initial (respectively station) maintenance grants in a single OFDMA frame.
  • [System] Cleanup stale temporary data files at bootup.
  • [GUI] Fixed overlay issues leading to hidden scrollbars on wide screens.
  • [Firmware] Fixed potential OFDMA data loss if channel center frequency is around 102.4MHz.



  • Real-time demodulation and decoding 
  • Full line rate
  • All FFT sizes, cyclic prefixes and roll-off periods defined by [CM-SP-PHYv3.1] 
  • Data demodulation and decoding 
    • All interleaver settings defined by [CM-SP-PHYv3.1] 
    • All modulations from zero-bit-loading up to 4096-QAM defined by [CM-SP-PHYv3.1] 
    • All possible configurations of exclusion bands defined by [CM-SP-PHYv3.1] 
    • Multiple concurrent data profiles (from A up to P) 
    • Mixed-modulation profiles 
    • Dynamic data profile changes 
    • Timestamp precision of DOCSIS frames is equal to one OFDM symbol (between 21 and 45 microseconds depending on FFT size and cyclic prefix) 
  • PLC and NCP demodulation and decoding 
    • Including MER statistics 
    • Timestamp precision is on the order of a few nanoseconds 


  • Real-time demodulation and decoding 
  • Full line rate
  • All FFT sizes, cyclic prefixes and roll-off periods defined by [CM-SP-PHYv3.1] 
  • Dynamic UCD changes (including data profile IUC changes) 
  • Data demodulation and decoding 
    • All interleaver settings defined by [CM-SP-PHYv3.1] 
    • All modulations from zero-valued up to 4096-QAM defined by [CM-SP-PHYv3.1] 
    • All possible configurations of exclusion bands and unused sub-carriers defined by [CM-SP-PHYv3.1] 
    • All data profile IUCs defined by [CM-SP-MULPIv3.1] concurrently 
    • Supported pilot patterns: 1-4, 8-11 
    • Timestamp precision of DOCSIS frames is equal to one OFDMA frame (between 126 and 1665 microseconds depending on OFDMA frame size, cyclic prefix and FFT size) 
  • Real-time full line rate bandwidth request (REQ) message demodulation and decoding 
    • Timestamp precision is on the order of a few nanoseconds 
  • Initial Ranging and Fine Ranging demodulation and decoding 
    • Including MER statistics and time offset estimations 
    • Timestamp precision is on the order of a few nanoseconds

Downstream SC-QAM 

  • Real-time demodulation and decoding 
  • Full line rate
  • Hardware timestamping of packets using reference channel clock (nanosecond resolution) 
  • 64/256-QAM, independently configurable per channel 
  • Dynamically configurable annex 
    • Annex A (EuroDOCSIS)  
    • Annex B (US DOCSIS)  
      • All interleaving parameters (control words) defined in [ITU-T Rec. J.83] supported 
      • Viterbi decoding for increased reliability. 
  • Extended downstream frequency range support 
    • Channel frequencies can be any multiple of 62.5 kHz between 108 and 1006 MHz, complying with all CM requirements in [CM-SP-PHYv3.1]. 
  • Two independent 248 MHz wide receive modules 
    • All channel frequency configurations that can be grouped evenly into the two receive module bands are valid, e.g. a channel configuration consisting of three channels at 200 MHz, 440 MHz and 1000 MHz is valid, but a configuration with frequencies 200 MHz, 600 MHz and 1000 MHz is not. 
  • Data MER and Reed-Solomon decoder statistics 
  • Timestamp precision of DOCSIS frames is equal to one MPEG frame (between 29 and 56 microseconds depending on annex and modulation)


  • Real-time demodulation and decoding 
  • Full line rate
  • Full A-TDMA UCD type 29 and 35 support (with the sole exceptions of differential encoding, zero-length preambles and IUC 2 Request_2 demodulation). 
    • All channel bandwidths (from 200 kHz to 6.4 MHz) defined in [CM-SP-PHYv3.0] 
    • All upstream center frequencies allowed by [CM-SP-PHYv3.0] 
    • All modulation types (from QPSK to 64-QAM) defined in [CM-SP-PHYv3.0] 
    • All preamble patterns, types (QPSK0/QSPK1) and lengths from 2 to 1536 bits defined in [CM-SP-PHYv3.0] (Hence, the minimum allowed preamble length is one QPSK symbol) 
    • Scrambler on/off 
    • Fixed/shortened last codeword 
    • All interleaving parameters allowed by [CM-SP-PHYv3.0] 
    • All Reed-Solomon FEC parameters allowed by [CM-SP-PHYv3.0] 
    • Supported IUCs: 1 (Request), 3 (Initial Maintenance), 4 (Station Maintenance), 5 (Short Data Grant), 6 (Long Data Grant), 9 (Advanced PHY Short Data Grant), 10 (Long PHY Short Data Grant), 11 (Advanced PHY Unsollicited Grant) 
    • Dynamic UCD changes 
  • Detailed statistics per demodulated burst 
    • Data MER 
    • Time offset 
    • Reed-Solomon decoder statistics 
    • Start minislot ID


  • [CM-SP-PHYv3.0] DOCSIS® 3.0 Physical Layer Specification (December 2017, 
  • [CM-SP-PHYv3.1] DOCSIS® 3.1 Physical Layer Specification (September 2019, 
  • [CM-SP-MULPIv3.1] DOCSIS® 3.1 MAC and Upper Layer Protocols Interface Specification (September 2019, 
  • [ITU-T Rec J.83] ITU-T J.83: Digital multi-programme systems for television, sound and data services for cable distribution  (December 2007, Telecommunication Standardization Sector of ITU)

Known limitations


  • OFDM

    • Possible temporary data loss during dynamic NCP updates
    • Zero-bit-loading of NCP subcarriers not supported
    • No data MER statistics

    • Unsupported pilot patterns: 5-7, 12-14
    • No probing sequences
    • No data MER statistics
  • A-TDMA

    • UCD type 2 (DOCSIS 1.x PHY channel and mixed DOCSIS 1.x/2.0 TDMA PHY channel) channels not supported
    • Differential encoding not supported
    • Zero preamble length not supported
    • IUC 2 (Request_2) not supported

Environment and system tools

  • xra31-admin: It is not possible to follow the system/service logs

Known Issues


  • The first channel locking attempt of an OFDM or downstream SC-QAM channel after a system reset or a CMTS change can take considerably longer than subsequent locking attempts. This is because internal frequency offset has to be reliably estimated (after which it is cached).

System and services

  • The reported upstream channel MER is the average over all fine ranging requests (for OFDMA) or all data bursts excluding initial ranging requests and bandwidth requests (for A-TDMA) over an elapsed interval of at most 30s. As such, it is possible that N/A (not available) is shown on low-load channels with T4 timeout multiplier higher than 1.
  • Captured Wireshark traces might contain invalid (malformed) packets corresponding to collisions (or possible RF interference) on A-TDMA IUC 1 (bandwidth request) grants. In a future release we plan to filter out these spurious bursts.
  • Inverse upstream Concatenation and Fragmentation (ICCF) of "segment header on" service flows is now performed for each channel independently. Hence, for CMs in MTCM (multi transmit channel mode), MAC frames that are fragmented over multiple upstream channels are not detected and consequently absent in the Wireshark trace. A future release will support ICCF over multiple channels.


(0 vote(s))
Not helpful

Comments (0)

We to help you!