PDA

View Full Version : [GiGaBlue HD800SE+] No data on Transponder - Error



Mister786
02-01-16, 22:11
Hi, ive been getting this error for the past week or so from time to time on most of the channels. The channels other than FTA dont work and get this error. However, after a reboot they start working and the error goes away for about 24 hours or so until it pops up again, when I have to reboot again to get it working.

Anyone got an idea what could be wrong?

Mister786
03-01-16, 09:14
Okay just had a look and there's a new bootloader available from December? Could the issue possibly be that my bootloader needs updating? If so, would I need to flash the image again after updating the bootloader, and is there any guide on how to go about updating the bootloader?

antosat
04-01-16, 15:40
there are instructions in the bootloader zip if you download it.

Cheers

Mister786
08-01-16, 00:06
Updated the bootloader but still keep getting this error. Across all channels now, quite frustrating. Any help please? Could it be a case of a faulty tuner?

Joe_90
08-01-16, 12:18
Is this the error message you are getting "No data on transponder (Timeout reading PAT)" ? What services? SAT/TERR/CABLE?

I am getting this problem intermittently on a GB Quad Plus on and off for several weeks, maybe as far back as late November. The channel tunes ok, but I get the error message on-screen and I can clear it with the OK button. This happens on satellite and terrestrial channels so I'm assuming it's not an actual tuner issue. I view mostly FTA channels. I notice that when this starts, I can no longer view any of my pre-recorded shows. If I try to reboot, the box mostly shuts down (picture and sound go off, but the blue LED on the front panel stays on), and I have to toggle the power switch on the back of the receiver to restart. It's fine after reboot for a day or two.

I've replaced the bootloader with the new one in the past couple of days and done a fresh flash with settings restore. Previously, had flashed without any settings restore but that didn't seem to resolve it either.

antosat
08-01-16, 12:58
Yes tony that's the issue in a nutshell. I reverted to ver 3.2.09 and its not a problem.

I installed a frsh install with not restore and it was still the same. I only have SAT.

Joe_90
08-01-16, 13:34
@antosat - I did a little search and see that you are having a similar problem to mine, all right. I wonder if the problem is the same for @Mister786?

Are you saying that the problem does not happen with 3.2.09 at all? I wonder could this be related to the new versions of gstreamer not playing nice with Gigablue models?

antosat
08-01-16, 13:39
@antosat - I did a little search and see that you are having a similar problem to mine, all right. I wonder if the problem is the same for @Mister786?

Are you saying that the problem does not happen with 3.2.09 at all? I wonder could this be related to the new versions of gstreamer not playing nice with Gigablue models?

Yes tony, Mister786 has the same problem. the issue has never happened to me using 3.2.09. Each time a new version comes out I will try it but within 24 hours the problem reoccurs. Have the GB drivers changed post 3.2.09?

Regards
A

Joe_90
08-01-16, 13:47
There were a lot of driver changes and reverted driver changes back in Nov/Dec, so I'm not actually sure what the problem might be. I've reported this as a possible bug. In the meantime I may revert back to 3.2.09 also.

Mister786
08-01-16, 18:18
Yep I'm having the same issue. It usually comes up with the error after around 24 hours and then works after a reboot.

So which image do you guys recommend I use whilst someone can fix this on the newer images? Would having a new bootloader impact in any way on the compatibility of the older images?

antosat
09-01-16, 20:53
i use ver 3.2.09

Joe_90
10-01-16, 17:23
I'm using 3.3.005 as I don't have a copy of 009 - so far so good.

Mister786
13-01-16, 23:58
Reverted back to 3.2.009 and it seems to be working fine. Any idea yet what the issue could be on the recent images?

Joe_90
14-01-16, 15:19
3.2.005 didn't actually work out for me. Within hours I had a scheduled recording which resulted in a zero-length file. I went back further to a Hades 018 image and it's been stable since Monday last.

Mister786
16-05-16, 00:40
Are the newer 4.1 images working okay or still same issue? I havent bothered updating from the last working image which was the 3.2.09. If the newer images have solved this then please let me know, thanks.

Joe_90
16-05-16, 13:15
I haven't had the issue on 4.1

Touchey2
17-05-16, 21:39
Same problem with my Gigablue 800ue ( "No data on transponder (Timeout reading PAT)"

Mister786
22-05-16, 12:27
Yep I'm still having the issue after upgrading to 4.1.

welshman2305
20-06-16, 11:21
Virtuosso Image Extreme Version 5.1 build 0

welshman2305
20-06-16, 11:29
Your lucky I got the same message and no channels working.

mike1961
20-07-16, 23:28
I've had this issue for several months. I think it first appeared with version 3.2.xxx. recently upgraded to 4.1 but issue still there. Drives me bananas. Whether its the "No data on transponder" or" tune failed" . Might flash with an older version and see how that goes...

mike1961
24-07-16, 23:06
Brief update.... downgraded to apollo (v 85 I think) and box is working fine for the last 48 hours. Things are looking up ☺

dsayers
24-07-16, 23:10
This sounds like a conflict with a providers file not been able to read by abm. Ensure that you are using the latest autobouqetesmarker when upgrading the providers files

mike1961
24-07-16, 23:31
I don't think the issue is anything to do with bouquets. ...but I'm glad I'm sorted (I hope)

trevsat
26-07-16, 01:20
Last stable release for me is v3.2 build 003. Go higher just one version and the timebomb is present.

GB quadplus

mike1961
26-07-16, 18:57
Last stable release for me is v3.2 build 003. Go higher just one version and the timebomb is present.

GB quadplus

Thanks for that. I'm just glad we have a working image.... but I'd love to know what the time bomb is .... and will it ever be fixed :confused:

ccs
26-07-16, 20:08
Thanks for that. I'm just glad we have a working image.... but I'd love to know what the time bomb is .... and will it ever be fixed :confused:I may well have missed something, but why has it taken 6 months+ for you to mention it if it's been that bad?

mike1961
26-07-16, 23:09
I gave up on the box. .. reckonEd I had terminal tuner issues and reverted to my Ferguson ariva 120. I recently tried to revive it by flashing the latest image (4.1) but that didn't work ... then reverted to an old image and was pleasantly surprised that the box is working fine since.

mike1961
18-09-16, 20:04
I gave up on the box. .. reckonEd I had terminal tuner issues and reverted to my Ferguson ariva 120. I recently tried to revive it by flashing the latest image (4.1) but that didn't work ... then reverted to an old image and was pleasantly surprised that the box is working fine since.

confused:doh ... I spoke too soon. Issue is back.... no channels most of the time ... 'tune faile'd error msg... It might or might not be a coincidence but the epg has also stopped downloading (to usb) and isnt being detected. When I check for satellite signal (service search) I have no signal on most transponders but can get a signal on some. :rolleyes:

sebus
19-06-17, 17:04
I never ever had this issue for over 4 years of using GB800SE (without image change/update, my old image works fine doing all I need)
Suddenly it started yesterday, as the heatwave hit southern England. So I attribute it to LNB just overheating.