Log in
Register
Menu
Log in
Register
Home
What's new
Latest activity
Authors
Forums
New posts
Search forums
What's new
New posts
Latest activity
Members
Current visitors
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Forums
Satellite TV receivers & systems support forums
Satellite PC Card Receivers, Internet by Satellite
Video on ACM GS streams
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="midwestmac" data-source="post: 910490" data-attributes="member: 402839"><p>Hello,</p><p>I haven't given up on this yet. I like being able to record with crazyscan now.</p><p>I have recorded both ways modcod "all" or sometimes a specific modcod like say QPSK 3/4</p><p>For me it depends on the signal I'm looking at. </p><p>If I record a signal with modcod 'ALL" I get a few more BBframes That look like this</p><p>42 00 00 00 00 80 00 00 00 f7</p><p>The Dfl 00 80 (Data field length) is only 16 bytes which I think, is when the modcod is at idle or waiting for the receiving end to say "it wants more". Not sure? I have seen these with the TBS recorder too, not a big deal they could probably be garbage anyway and thrown away,</p><p></p><p>Lately I've been going over recordings with a hex editor trying to figure out more, to make it</p><p>easier for my friend to piece this puzzle together.</p><p>The BBframes are the easy part but the GSE headers are a little more trickey</p><p>I was told these streams will have to be sorted by either there Fragment ID or Protocol Type</p><p></p><p>So I have been searching looking for info on protocol types that make sense in are recordings</p><p>A GSE header is always right after the 10 byte BBheader here's an example of a GSE header with a popular protocol type "<span style="color: #0000ff">00 02</span>" and fragment ID "<span style="color: #ff0000">0c</span>" that I see many of, and are easy to find</p><p> </p><p><span style="color: #ff0000"> Fragment ID is the 3rd byte</span> and the<span style="color: #0000ff"> protcol type</span> is the 6th & 7th byte with a 6 byte label</p><p> 82 80 <span style="color: #ff0000">0c</span> 05 52 <span style="color: #0000ff">00 02</span> 00 ff fd c1 00 00 </p><p>And thats following the GSE specs.</p><p>The protocol type can also be at the 3rd & 4th byte depends if its a Concatenated PDU</p><p></p><p>But its the other GSE headers that have different Protocol types then this "00 02" that need to be sorted </p><p>to make sure everything is extracted from a recording.</p><p>And I can't find any specs yet on the protocol types that are being used all I know is this "<span style="color: #0000ff">00 02</span>" that usually has Pid 256 behind it, comes up a lot.</p><p>I have been able to find the Pid 256 associated with different Protocol types but I'm not sure what</p><p>they are yet?</p><p>Thought I'd share what I have so far. Happy New Year</p></blockquote><p></p>
[QUOTE="midwestmac, post: 910490, member: 402839"] Hello, I haven't given up on this yet. I like being able to record with crazyscan now. I have recorded both ways modcod "all" or sometimes a specific modcod like say QPSK 3/4 For me it depends on the signal I'm looking at. If I record a signal with modcod 'ALL" I get a few more BBframes That look like this 42 00 00 00 00 80 00 00 00 f7 The Dfl 00 80 (Data field length) is only 16 bytes which I think, is when the modcod is at idle or waiting for the receiving end to say "it wants more". Not sure? I have seen these with the TBS recorder too, not a big deal they could probably be garbage anyway and thrown away, Lately I've been going over recordings with a hex editor trying to figure out more, to make it easier for my friend to piece this puzzle together. The BBframes are the easy part but the GSE headers are a little more trickey I was told these streams will have to be sorted by either there Fragment ID or Protocol Type So I have been searching looking for info on protocol types that make sense in are recordings A GSE header is always right after the 10 byte BBheader here's an example of a GSE header with a popular protocol type "[COLOR=#0000ff]00 02[/COLOR]" and fragment ID "[COLOR=#ff0000]0c[/COLOR]" that I see many of, and are easy to find [COLOR=#ff0000] Fragment ID is the 3rd byte[/COLOR] and the[COLOR=#0000ff] protcol type[/COLOR] is the 6th & 7th byte with a 6 byte label 82 80 [COLOR=#ff0000]0c[/COLOR] 05 52 [COLOR=#0000ff]00 02[/COLOR] 00 ff fd c1 00 00 And thats following the GSE specs. The protocol type can also be at the 3rd & 4th byte depends if its a Concatenated PDU But its the other GSE headers that have different Protocol types then this "00 02" that need to be sorted to make sure everything is extracted from a recording. And I can't find any specs yet on the protocol types that are being used all I know is this "[COLOR=#0000ff]00 02[/COLOR]" that usually has Pid 256 behind it, comes up a lot. I have been able to find the Pid 256 associated with different Protocol types but I'm not sure what they are yet? Thought I'd share what I have so far. Happy New Year [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Satellite TV receivers & systems support forums
Satellite PC Card Receivers, Internet by Satellite
Video on ACM GS streams
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top