Raptor Locks Up on AMI TV

[Pixl]

107w 3748 V 6774 two channels in the mux, scan as $ but are ITC. However, one is ok, v32 a33, but the other v16 a17 locks up the Raptor, sound only, and no navigation after this requiring a hard re-boot. Can someone else with a Raptor, or any receiver try this?

[el bandido]

I do not have any c band due to moving the dish, but will check this when I have c band going again. EB

[eastof111]

"107w 3748 V 6774 two channels in the mux, scan as $ but are ITC. However, one is ok, v32 a33, but the other v16 a17 locks up the Raptor, sound only, and no navigation after this requiring a hard re-boot. Can someone else with a Raptor, or any receiver try this? "

Pixl, on the v32 a33, I get v32 a34 and on the v16 a17, I get v16 a18. Both coming in fine with no lock ups. Both show up as SVC_1 Service and SVC_2 Service. Using 2.11.07 Openbox again.

[mengram]

"107w 3748 V 6774 two channels in the mux, scan as $ but are ITC. However, one is ok, v32 a33, but the other v16 a17 locks up the Raptor, sound only, and no navigation after this requiring a hard re-boot. Can someone else with a Raptor, or any receiver try this? "

Pixl, on the v32 a33, I get v32 a34 and on the v16 a17, I get v16 a18. Both coming in fine with no lock ups. Both show up as SVC_1 Service and SVC_2 Service. Using 2.11.07 Openbox again.

My Raptor does the same thing on those channels eastof111. I posted about this issue in an earlier thread. Also have the same problem on the NUVO channel on 105.0W C-band 3920/V/30000.

mengram

[Sublime]

"107w 3748 V 6774 two channels in the mux, scan as $ but are ITC. However, one is ok, v32 a33, but the other v16 a17 locks up the Raptor, sound only, and no navigation after this requiring a hard re-boot. Can someone else with a Raptor, or any receiver try this? "

Pixl, on the v32 a33, I get v32 a34 and on the v16 a17, I get v16 a18. Both coming in fine with no lock ups. Both show up as SVC_1 Service and SVC_2 Service. Using 2.11.07 Openbox again.

There are two audio PIDs on each channel. SVC_2 always locks up for me, as well. I've never been able to get these channels in very well on the Solomend or Manhattan, either. At best, those receivers will show a pixellated still picture with audio that cuts in and out. On the Raptor, audio cuts in and out, but no picture at all.

On a similar note, I've scanned a few scrambled muxes in the Western arc and a few with only SVC names will lock up on the second channel. The symptom is often a lockup when changing from the bad channel to another one. I get blank screen on the AMI channel and on the scrambled muxes the OSD will show the old channel, while the FPD shows the new one.

[Pixl]

East, that is interesting. I'll try to key in your slightly different pids tonight and see what happens.

[Pixl]

East I keyed in your pids and both channels work now, no lock up. As a verification test, I tried blind scanning the TPs back in, they reverted to my first set of pids and locked up the Raptor again.

Mengram, I also scanned in your 105w TP, confirmed it too locks up the Raptor. I have no manual pid remedy for this one. One common to the two services is they both scan in as $ but are ITC.

[eastof111]

I wonder if it's the firmware? Like I said earlier, I reverted back to 2.11.07 from 2.11.16 Openbox version and did a blind scan with the ALL options.

[Pixl]

Nevermind, now the Raptor is locking up on the 107w channels again. Hmmnn..

[eastof111]

Sounds like you have a real mystery going on there.... Hope you get it working.