SID not found in PAT (DVB-T channels)

[SatDreamer]

I am having the "Service not found! SID not found in PAT" problem for the last 1-2 months, never had it before. It only happens for DVB-T channels. Using the Hauppauge WinTV-MiniStick and the latest 2.0.9.1 image.

I scan all DVB-T channels and they usually work ok. After a couple of days, some of them just stop working (SID not found...) and I have to re-scan. They work again, but only for a while.

 

[angelofsky1980]

I am having the "Service not found! SID not found in PAT" problem for the last 1-2 months, never had it before. It only happens for DVB-T channels. Using the Hauppauge WinTV-MiniStick and the latest 2.0.9.1 image.

I scan all DVB-T channels and they usually work ok. After a couple of days, some of them just stop working (SID not found...) and I have to re-scan. They work again, but only for a while.

Sometimes the TV broadcaster reorganize their muxes and it's normal that appear "SID not found in PAT". This hannep also on my installation with your same hardware.

 

[SatDreamer]

Thanks for answering. But every 2-3 days? Doesn't seem normal.

 

[Eragon]

If you have arranged to download some channel lists from the feeds every 2-3 days, it might be that the DVB-T channels in the list you're using have not been updated and so the problem constantly reappears at every update.

 

[SatDreamer]

Thanks, I haven't arranged such a download, but will check the settings.

 

[angelofsky1980]

Thanks for answering. But every 2-3 days? Doesn't seem normal.

Every TV broadcaster change mux settings according to their internal plans. I suppose a TV set can detect these changes and re-tune the service automaticlaly but our vu+ boxes needs a rescan.

 

[SatDreamer]

Could be, but this is a recent problem (for me at least). Is a problem/bug in the newer image/drivers to be excluded?

 

[angelofsky1980]

Could be, but this is a recent problem (for me at least). Is a problem/bug in the newer image/drivers to be excluded?

I suggest to write down PIDs of the channel you don't see, make a full scan and take a look to PIDs: if they are changed, the TV broadcaster has changed something.

 

[SatDreamer]

Info from such a channel (currently working).

 

[SatDreamer]

Just checked the above info after a re-scan on the same channel (after it had been lost again) and they are exactly the same. I'll try with an older image.

 

[SatDreamer]

Running the 2.0.4 image for almost a week now and never had this problem again. Channels were usually lost after 2-4 days. Could this be an image or driver issue? Is it possible to use the 2.0.4 driver for this device with the latest image?

 

[angelofsky1980]

Running the 2.0.4 image for almost a week now and never had this problem again. Channels were usually lost after 2-4 days. Could this be an image or driver issue? Is it possible to use the 2.0.4 driver for this device with the latest image?

Drivers cannot be exchanged between images, I'm sorry.

 

[SatDreamer]

Thanks for the info angelofsky. I'm just confirming that I've still haven't lost any DVB-T channels, so this is possibly an image/driver issue of the newer versions.