Skip to main content

How to generate canned headend data

6 replies [Last post]
scottkell
Offline
Joined: 2007-04-04
Points: 0

In the 5/27 Barcelona discussion, CableLabs mentioned that information would be posted concerning how to generate the canned OOB section data used by the cg_shunt.

That is, the binary files found in emu\HeDri\Emulator\deploy\resources\fdcdata\.

Note that we do not want to populate the binary files with information from a real head-end, but with channel data of the user's choosing.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
scottkell
Offline
Joined: 2007-04-04
Points: 0

TVWorks has contributed code to write NIT-CDS, NIT-MMS, NTT and SVCT binary tables. This code can be found in experimental/TVT-framework/tvt/siWriter.

dhooley
Offline
Joined: 2008-04-23
Points: 0

yes that is a safe assumption

stcarson65
Offline
Joined: 2009-03-02
Points: 0

Dave,

Would it be possible for us to get the code for the SI/PSI generating tool? We understand that this tool is not yet of release quality. However it would still aid us greatly in developing/testing our simulation configuration UI.

Thanks,
Sean

stcarson65
Offline
Joined: 2009-03-02
Points: 0

Actually the binaries would work too if you could tell us how to invoke it and gave us the XSD for the XML file it expects.

scottkell
Offline
Joined: 2007-04-04
Points: 0

In that case, we may have to generate these files ourselves.

It looks like these files live in the HE4RI deploy folder, so can I assume when we switch from the shunt to using HE4RI that it will also use the same file format?

dhooley
Offline
Joined: 2008-04-23
Points: 0

The canned data we use for testing was not captured from a CableLabs head-end - it was generated with an internal tool. The tool has the ability to read XML and generate the *.bin files we use in both the he4ri and the shunt.

At this point the tool is not ready to release in source or binary form, although that is likely a future outcome.

For now, the channel line-up in the platform_xxxxx.cfg files will have to be sufficient for tune-test capabilities. The latest merged trunk supports decode of the example streams.