←Back
⚡ Quick Reference

SAT>IP URL Builder & T2-MI

Quick reference guide to SAT>IP URL construction, multistream parameters, and T2-MI configuration

⚡ Jump to Section:

🔢

Basic SAT>IP Parameters

Essential Parameters for Standard DVB-S/S2 Transponders

Essential Parameters

ParameterDescriptionExample Values
freqFrequency in MHz10700-12750 (Ku-band)
polPolarizationV (Vertical) or H (Horizontal)
srSymbol Rate in KSym/s22000, 27500, 30000
msysDelivery SystemDVBS, DVBS2, DVBT, DVBT2
mtypeModulationqpsk, 8psk, 16apsk, 32apsk, 256apsk
fecForward Error Correction12 (1/2), 23 (2/3), 34 (3/4), 45 (4/5), 56 (5/6), 89 (8/9), 910 (9/10)
http://your-satip-server-ip:8875/?src=1&freq=11727&pol=v&sr=30000&msys=dvbs2&mtype=8psk&fec=34

FEC Notation: Two digits represent numerator/denominator. 34 = 3/4, 910 = 9/10. Higher FEC (8/9, 9/10) = more bandwidth but requires stronger signal. Lower FEC (1/2, 2/3) = more error protection but wastes bandwidth.

🌊

Multistream Parameters

ISI & PLS Codes for DVB-S2X Multistream

ISI (Input Stream Identifier)

  • Range: 0-255
  • Selects stream from multistream transponder
  • Example: isi=9
  • Eutelsat 5W: ISI=1 (RAI mux), ISI=9
  • 31+ channels on one frequency

PLS (Physical Layer Scrambling)

  • PLSC range: 0-262143
  • Modes: gold, root, combo
  • Example: plsc=131070&pls=gold
  • Use either ISI or PLSC, not both
  • Check LyngSat for correct values
http://your-satip-server-ip:8875/?src=1&freq=12536&pol=h&sr=35300&msys=dvbs2&mtype=8psk&fec=23&isi=9

Example: Eutelsat 5 West B 12.536 GHz H carries multiple streams. Stream 9 (ISI=9) contains 17 Puglia local channels. Total: 31+ channels on one frequency.

📺

T2-MI Configuration

DVB-T2 Encapsulated in DVB-S2

T2-MI Parameters

  • t2mi_pid: Default 4096 (range 4095-4099), or auto
  • t2mi_plp: Default 0 (range 0-255), or all
  • bbframe=1: Raw DVB-S2 BBFrame input mode
  • Most transponders use PID 4096; PLP 0 = main multiplex
  • Query parameters, not a # fragment

Important Notes

  • Only use if the transponder actually carries T2-MI
  • Adding it to a non-T2MI transponder causes failure
  • bbframe=1 needs the patched STiD135 driver
  • Without that driver it falls back silently to normal tuning
  • Pair bbframe=1 with t2mi_pid= and pids=all
http://your-satip-server-ip:8875/?src=1&freq=12606&pol=v&msys=dvbs2&mtype=8psk&sr=35300&fec=23&ro=0.35&isi=5&plsm=gold&plsc=131070&bbframe=1&pids=all&t2mi_pid=4096&t2mi_plp=0

Corrected 2026-08-05. This section previously gave the parameters as #t2mi=4096&plp=0 — a URL fragment, which is never sent to the server, so the example could not work. The real form is the query parameters t2mi_pid and t2mi_plp above. It also said the server does not decapsulate T2-MI and that external software is required; that is wrong — the server runs the T2-MI demux on the fly, in real time as the stream passes through, and delivers the inner TS. No extra stage, no extra hop.

bbframe=1 — when the RF is perfect but the output is not. Some multistream transponders carry a bursty T2-MI feed that the demodulator's hardware de-encapsulation drops, around 9% packet loss, producing near-total T2-MI CRC failure on a flawless signal. bbframe=1 takes raw DVB-S2 BBFrames instead and rebuilds the outer TS losslessly in software. Applies to HTTP, RTSP and SRT.

plsm takes a name, not a number. Use plsm=gold; a numeric value is read as root mode and re-derives the code, so you tune the wrong scrambling sequence and get no lock.

📝

Complete URL Examples

Real-World Scenarios

Example 1: Standard DVB-S2

Astra 19.2°E, 11.954 GHz H, 27500 KSym/s, 8PSK 3/4

http://your-satip-server-ip:8875/?src=1&freq=11954&pol=h&sr=27500&msys=dvbs2&mtype=8psk&fec=34&pids=all

Example 2: Multistream with ISI

Eutelsat 5W, 12.536 GHz H, 35300 KSym/s, 8PSK 2/3, ISI=9

http://your-satip-server-ip:8875/?src=1&freq=12536&pol=h&sr=35300&msys=dvbs2&mtype=8psk&fec=23&isi=9&pids=all

Example 3: Multistream with PLS

Hotbird 13°E, 11.470 GHz V, 27500 KSym/s, 8PSK 3/4, PLS Gold 131070

http://your-satip-server-ip:8875/?src=1&freq=11470&pol=v&sr=27500&msys=dvbs2&mtype=8psk&fec=34&plsc=131070&pls=gold&pids=all

Example 4: T2-MI

T2-MI encapsulated, 11.727 GHz V, 30000 KSym/s, 8PSK 3/4, PID 4096, PLP 0

http://your-satip-server-ip:8875/?src=1&freq=11727&pol=v&sr=30000&msys=dvbs2&mtype=8psk&fec=34&pids=all&t2mi_pid=4096&t2mi_plp=0
🔧

Troubleshooting Tips

Common Issues & Solutions

Common Mistakes

  • Wrong frequency (check LyngSat)
  • Incorrect polarization (V vs H)
  • Symbol rate typo (27500 vs 2750)
  • FEC mismatch (34 vs 23)
  • Adding T2MI to non-T2MI
  • ISI/PLS confusion
  • Wrong PLS mode (gold vs root)

Diagnostic Steps

  • Verify with LyngSat.com
  • Start with basic parameters
  • Test without PID filtering
  • Increase duration to 20 seconds
  • Check SATLINE.TV admin panel
  • Try alternative ISI values
  • Consult satellite forums
⚠️ Signal Quality: Advanced modulation (16APSK, 32APSK, 256APSK) and high FEC ratios (8/9, 9/10) require excellent signal quality. Check SNR and signal strength in SATLINE.TV monitoring dashboard.

About the author

Gleb Sazanov

Project Leader

Gleb Sazanov is an accomplished Chief Technology Officer (CTO) with over 20 years of experience in software development, system architecture, and cloud-based solutions. As the CTO of SATLINE, a leading provider of virtual and colocation services tailored to SATCOM businesses, Gleb drives the company’s technological strategy, fostering innovation and efficiency in data center services. His expertise spans various domains, including DevOps, system scaling, and high-performance infrastructure management. With a deep passion for cutting-edge technologies, Gleb plays a pivotal role in shaping the future of the SATCOM industry.