org.omg.space.xtce.schema.doc.SpaceSystemV1.2-27Feb2014-mods_SyncStrategyType.html Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of xtcetools Show documentation
Show all versions of xtcetools Show documentation
This project contains software to support the Object Management Group (OMG) Space Domain Task Force (SDTF) maintained XML Telemetry and Command Exchange (XTCE) specification.
SpaceSystemV1.2-27Feb2014-mods - SyncStrategyType
complexType
SyncStrategyType
diagram
namespace
http://www.omg.org/space/xtce
children
xtce:AutoInvert
used by
elements FixedFrameStreamType/SyncStrategy VariableFrameStreamType/SyncStrategy
attributes
Name Type Use Default Fixed Annotation verifyToLockGoodFrames nonNegativeInteger 4 checkToLockGoodFrames nonNegativeInteger 1 maxBitErrorsInSyncPattern nonNegativeInteger 0 documentation Maximum number of bit errors in the sync pattern (marker).
annotation
documentation A Sync Strategy specifies the strategy on how to find frames within a stream of PCM data. The sync strategy is based upon a state machine that begins in the 'Search' state until the first sync marker is found. Then it goes into the 'Verify' state until a specified number of successive good sync markers are found. Then, the state machine goes into the 'Lock' state, in the 'Lock' state frames are considered good. Should a sync marker be missed in the 'Lock' state, the state machine will transition into the 'Check' state, if the next sync marker is where it's expected within a specified number of frames, then the state machine will transition back to the 'Lock' state, it not it will transition back to 'Search'.
source
<complexType name="SyncStrategyType">
<annotation>
<documentation xml:lang="en">A Sync Strategy specifies the strategy on how to find frames within a stream of PCM data. The sync strategy is based upon a state machine that begins in the 'Search' state until the first sync marker is found. Then it goes into the 'Verify' state until a specified number of successive good sync markers are found. Then, the state machine goes into the 'Lock' state, in the 'Lock' state frames are considered good. Should a sync marker be missed in the 'Lock' state, the state machine will transition into the 'Check' state, if the next sync marker is where it's expected within a specified number of frames, then the state machine will transition back to the 'Lock' state, it not it will transition back to 'Search'. </documentation>
</annotation>
<sequence>
<element name="AutoInvert" minOccurs="0">
<annotation>
<documentation xml:lang="en">After searching for the frame sync marker for some number of bits, it may be desirable to invert the incoming data, and then look for frame sync. In some cases this will require an external algorithm</documentation>
</annotation>
<complexType>
<sequence>
<element name="InvertAlgorithm" type="xtce:InputAlgorithmType" minOccurs="0"/>
</sequence>
<attribute name="badFramesToAutoInvert" type="positiveInteger" default="1024"/>
</complexType>
</element>
</sequence>
<attribute name="verifyToLockGoodFrames" type="nonNegativeInteger" default="4"/>
<attribute name="checkToLockGoodFrames" type="nonNegativeInteger" default="1"/>
<attribute name="maxBitErrorsInSyncPattern" type="nonNegativeInteger" default="0">
<annotation>
<documentation xml:lang="en">Maximum number of bit errors in the sync pattern (marker).</documentation>
</annotation>
</attribute>
</complexType>
attribute
SyncStrategyType/@verifyToLockGoodFrames
type
nonNegativeInteger
properties
default 4
source
<attribute name="verifyToLockGoodFrames" type="nonNegativeInteger" default="4"/>
attribute
SyncStrategyType/@checkToLockGoodFrames
type
nonNegativeInteger
properties
default 1
source
<attribute name="checkToLockGoodFrames" type="nonNegativeInteger" default="1"/>
attribute
SyncStrategyType/@maxBitErrorsInSyncPattern
type
nonNegativeInteger
properties
default 0
annotation
documentation Maximum number of bit errors in the sync pattern (marker).
source
<attribute name="maxBitErrorsInSyncPattern" type="nonNegativeInteger" default="0">
<annotation>
<documentation xml:lang="en">Maximum number of bit errors in the sync pattern (marker).</documentation>
</annotation>
</attribute>
element
SyncStrategyType/AutoInvert
diagram
namespace
http://www.omg.org/space/xtce
properties
minOcc 0 maxOcc 1 content complex
children
xtce:InvertAlgorithm
attributes
Name Type Use Default Fixed Annotation badFramesToAutoInvert positiveInteger 1024
annotation
documentation After searching for the frame sync marker for some number of bits, it may be desirable to invert the incoming data, and then look for frame sync. In some cases this will require an external algorithm
source
<element name="AutoInvert" minOccurs="0">
<annotation>
<documentation xml:lang="en">After searching for the frame sync marker for some number of bits, it may be desirable to invert the incoming data, and then look for frame sync. In some cases this will require an external algorithm</documentation>
</annotation>
<complexType>
<sequence>
<element name="InvertAlgorithm" type="xtce:InputAlgorithmType" minOccurs="0"/>
</sequence>
<attribute name="badFramesToAutoInvert" type="positiveInteger" default="1024"/>
</complexType>
</element>
attribute
SyncStrategyType/AutoInvert/@badFramesToAutoInvert
type
positiveInteger
properties
default 1024
source
<attribute name="badFramesToAutoInvert" type="positiveInteger" default="1024"/>
element
SyncStrategyType/AutoInvert/InvertAlgorithm
diagram
namespace
http://www.omg.org/space/xtce
type
xtce:InputAlgorithmType
properties
minOcc 0 maxOcc 1 content complex
children
xtce:LongDescription xtce:AliasSet xtce:AncillaryDataSet xtce:AlgorithmText xtce:ExternalAlgorithmSet xtce:InputSet
attributes
Name Type Use Default Fixed Annotation shortDescription string optional documentation It is strongly recommended that the short description be kept under 80 characters in length
name xtce:NameType required
source
<element name="InvertAlgorithm" type="xtce:InputAlgorithmType" minOccurs="0"/>
XML Schema documentation generated by
XMLSpy
Schema Editor
http://www.altova.com/xmlspy