Detecting Nova-t-500 (or USB) tuner crash??

[martint123]

Does this happen to other USB DVB tuner devices????
Missed three recordings last night due to device or driver failure with my nova-t-500 tuner. I'm fairly sure this is from going to sleep and coming out of hibernate. This seems to happen every few weeks but unpredictably.
Devcon only shows the error after a recording has failed and not after coming out of hibernate - it doesn't set a return code either.

Code:

USB\VID_2040&PID_9951\4027355045
  Name: USB Composite Device
  Device has a problem: 10.

GBPVR detects the error like this

Code:

2010-02-16 15:43:02.500    ERROR    [5]    Error starting recording: GBPVR.Backend.Common.GbpvrException: Failed to locate configured BDA capture device......

What would be really nice would be a small proglet, running from one of the wake/hibernate tools, that checked the device and rebooted if it did not respond as expected. I'm guessing a reboot would be fast enough to start recording on time - anyway, missing a minute is better than missing the lot.

As the machine has just come out of hibernate, there shouldn't be anything else attached to the device. Can anyone think of anything that could check the device status by trying to connect to it.
I've looked at the source of the scancahannelsbda tools, but taht is way beyond my capabilities.......

any thoughts?

[Graham]

It may be specific to the 500. I have a Nova-T USB2 (single tuner) that works flawlessly. It went in and out of hibernation once or more each day for three weeks while I was on holiday without incident. Have you tried the Hauppauge UK forum?

[martint123]

There a quite a few threads there, but the consensus seems to be Hauppauge won't or can't fix it and not to use suspend or hibernate.
I might see if I can get my system to go to power off rather than hibernate as a reboot seems to work ok. I suppose I have to try seeing if my bios/XP/gbpvr etc will startup from power off though first........

[Graham]

Near the bottom of ...

http://www.gbpvr.com/pmwiki/pmwiki.php/M...BatchFiles

wake.cmd is mentioned (Dunno if it still works with current release). This plus devcon might help.

[martint123]

Thanks Graham... but...
I already run Devcon from wake.cmd (well, did, but now run it from hibernate.exe that does more or less the same thing).

The problem seems to be that when the system comes out of standby with the device/driver faulty, devcon does not report this at the time, but says it is OK.
It is not until gbpvr tries to set the card up for a recording or grabbing an EPG and it fails that the driver then responds to devcon with a "problem" message.

I might just go for a forced reboot with the first exit from standby on a Sunday or something like that and see how it goes.......

[Graham]

http://members.optusnet.com.au/toppytool...start.html

http://digital.ni.com/public.nsf/allkb/1...A700602459

I'll get my coat now ...

[martint123]

Many thanks for that. I think I'll start restarting the device every time it comes out of hibernate with the script from the first link and see how it goes.

Thanks again Graham - you must have far too much time on your hands