Skip to main content

How to trigger EAS events

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

I'm trying to figure out the best way to trigger EAS events on-demand. The use case is this. The RI user starts their application from our dev environment. After it is up and running, they want to trigger EAS events to ensure this case is handled correctly by their app.

I know there is some canned EAS binary data in the FDC, which this user is currently removing from fdc-files.txt b/c they don't want EAS signaling before their app is initialized. One idea is that when the user requests EAS events to start, I would modify fcd-files.txt to include the EAS binary data, then force a reload of the FDC data.

Are there other APIs/backdoors/configuration to trigger EAS events to start happening? (Note that we are not expecting that Xlet itself can trigger these events-- our dev environment would call into the RI code to trigger events.

Could you point me to any spec for what is found in the EAS binary file? Is there a writer for this file available?

In 1.1.3, I see 7 different EAS binary files. (Eas-form1.bin, EAS_event_ID_[2-7].bin). Could someone tell me what each of these are?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
cpratt
Offline
Joined: 2008-12-18
Points: 0

Scott,

There's a CRC calculator in the RI that you can find in trunk/ri/ODLSrc/OCAP-1.0/mpe/mgr/simgr/si_util.c

See init_mpeg2_crc() and calc_mpeg2_crc().

scottdeboy
Offline
Joined: 2009-02-02
Points: 0

/common/resources/fdcdata/eas-test-files/README contains a description of the individual EAS binary files, as well as instructions for demonstrating EAS functionality using these files with an EAS host key listener xlet.

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

Thanks, that's helpful.
I'm trying to change the .hex and regenerate the .bin files. However, I think the CRC_32 bytes would be invalid with changed data.
Any pointers/tools for generating a new valid CRC_32 bytes?

scottkell
Offline
Joined: 2007-04-04
Points: 0
greg80303
Offline
Joined: 2008-07-03
Points: 0

Yes, SCTE18 is the spec that defines the EAS MPEG section format.

As for triggering your own events -- the fdc-files.txt file is read everytime the system "re-broadcasts" OOB data. So, if you make a change to this file while the system is running, it will be detected at runtime just as if some sort of change was made from the headend. Therefore, if you would like to trigger EAS, just add the name of an EAS section file to the end of fdc-files.txt and save it. When you are ready to discontinue EAS, just remove the EAS file from fdc-files.txt and save it.

As for the contents of the individual EAS section files distributed with the RI -- these files were used to test various parts of the SCTE18 spec in the RI. I'm not sure about the exact contents of each file, but I'm sure that they test things like tuning to a new service to handle EAS. I will make some inquiries to see who may have more details about how these files were generated.

Greg