Working With Sjobergs Cable Tv Guide
I still have the original PDF printed out somewhere in a binder, though honestly I barely touch it anymore. The thing about Sjobergs Cable Tv Guide is that it was written for a specific era of cable infrastructure and it shows. When I first started using it around 2014, it was still relevant for most standard QAM channel mappings. A lot of people treat it like a static reference document, which is fine until your headend equipment doesn't line up with what the guide assumes. The original resource is archived and you can find it at various technical forums, but the direct download links tend to rotate. I usually point people toward the Internet Archive's Wayback Machine versions or the Usenet backups that circulate on technical newsgroups. The guide itself is a straightforward mapping document — it covers channel assignments, QAM frequencies, and the standard cable box programming tables for systems running legacy equipment.
Sjobergs Cable Tv Guide
Here's where it gets interesting and where most people run into trouble. The guide was designed around a specific ATSC/QAM layering scheme that assumed most headends were pushing analog and digital channels on predictable frequencies. If you're working with a modern hybrid fiber-coax setup that uses OFDM instead of traditional QAM, most of the channel mapping in the guide becomes irrelevant. I learned that the hard way when I tried to use it for a DOCSIS 3.1 deployment and spent three hours wondering why my channel scanner wasn't finding anything on the documented frequencies. Another issue that nobody really warns you about: the guide uses EIA/SCTE standards for event IDs and guide data formatting, but those standards shifted between editions. The 2009 version and the later revisions handle virtual channel numbers differently, especially for subchannels. If you're parsing the guide data programmatically and your output looks right but your boxes are displaying scrambled information, check which revision of the standard the guide is targeting. I had a situation where my electronic program guide was off by one day because I was cross-referencing the guide's timestamp format with a system that expected the newer SCTE-104 alignment instead of the older SCTE-35 approach. The workaround was adding a manual offset function in the ingestion script — not elegant, but it kept things from drifting further over time. The practical use case for this guide today is mostly legacy maintenance. If you're running older Motorola or Pace equipment that still reads QAM tables directly, the guide is worth having on hand. It covers the standard hierarchical modulation settings, the typical channel spacing patterns, and the basic PSIP tables that cable systems used before everyone moved to IP-based middleware. For anything involving modern IPTV or streaming integration, you're better off with an XMLTV-compatible solution or a dedicated middleware platform like TiVo Enterprise or AereoGrid.
The common pitfall is assuming the frequency table in the guide is universal. It isn't. Different system operators had different frequency plans even within the same region, and the guide reflects a best-effort composite of common configurations. I once spent a morning tuning a rig only to realize the operator had shifted the entire upper digital band by a few megahertz to accommodate a new FM bridge. Nothing in the guide would have warned you about that unless you knew to check the system's engineering documentation first. Another limitation worth noting: the guide doesn't account for encrypted or premium channel slot assignments. If you need the full PSIP data including conditional access information, you're going to need access to the headend's actual transmission parameters, not just a reference document. The guide is useful as a starting point for understanding the structure, but it won't solve problems that require live signal analysis or headend configuration access. For people who are just trying to populate a simple guide database for a small system or a personal project, the format is straightforward enough to parse manually. The data is organized in clear sections — each channel entry includes the virtual channel, transport stream ID, network ID, program number, and the associated audio and video PID references. A basic script that reads the tables and outputs XMLTV format will handle most routine conversion tasks without too much trouble.
Get the Full Details
If you're doing this for professional installation work, I'd recommend pairing the guide with a spectrum analyzer and a proper OTN viewer. Having the mapping on paper is one thing. Verifying it against actual signal output is another. The gap between the two is where most projects either succeed or fail, and the guide alone won't bridge that distance for you.
