Skip to main content

configuring XAIT

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

I see 2 ways to get XAIT info into the RI.
1) The shunt provides canned XAIT info that is provided by the OOB FDC. This information is in a binary section filter format, like the other canned OOB files.
2) DavicSignallingManager can load persisted XAIT info via:
MPEEnv.getEnv("OCAP.persistent.xaitstorage")+ "/xait";

In Vidiom Workbench xait data could be loaded via xait.properties, like the hostapp.properties laoding we are using in the ri today. (AIT data was laoded in a similar manner). Is this same mechanism available in the RI?

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

Thanks Greg.

From the ocap-ri perspective, what's the difference between unbound apps loaded via hostapp.properties and xait.properties?

Scott

greg80303
Offline
Joined: 2008-07-03
Points: 0

hostapp.properties signaling is identical to xait.properties (all fields are the same). The difference in how the stack sees these applications is defined in the OCAP spec under the classification of Host Device Manufacturer Applications. There are numerous sections throughout the spec that describe how these applications are to be treated by the stack.

One of the things that people miss often is from OCAP1.1.1 Section 11.2.2.3.14. If you declare an abstract service in your hostapp.properties file that is not in the range of 0x010000 - 0x01FFFF, the stack will ignore that service and any apps associated with that service.

greg80303
Offline
Joined: 2008-07-03
Points: 0

The RI supports file-based signaling just like VWB. I have created an internal Wiki page that fully documents the capabilities of the file-based signaling system. This page has not yet been migrated to the public site. We will update this post when the page is made public.

For now, you can use any of your existing x/ait.properties files by modifying the mpeenv.ini file:

OCAP.mgrmgr.Signalling=com.vidiom.impl.manager.signalling.TestSignallingMgr
#OCAP.mgrmgr.Signalling=com.vidiom.impl.manager.signalling.DavicSignallingMgr

Use TestSignallingMgr for file-based signaling. Use DavicSignallingMgr for MPEG section-based signaling.

G