<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p><br>
</p>
<div class="moz-cite-prefix">Hi Bob!<br>
</div>
<blockquote type="cite"
cite="mid:mailman.3.1739275202.23535.mythtv-users@mythtv.org">
<pre>Regarding the HDPVR - It's recognized by the OS (/dev/video2) and backend.
I have had this thing for years; it usually works great, but its biggest
issue is flaky wall-warts. I finally found a good power supply for it that
doesn't croak after a few months to a year. Even so, I still have to power-
cycle it once every week or two; if I don't it goes into hibernation mode.
Once I wake it up, it works fine.</pre>
</blockquote>
<p>As an electronics hobbyist I've found wall wart specifications
seem to lie, and/or the manufacturer will use the barely-scrape-by
option to save a few cents. In general I keep the voltage and
increase the current -- stay with the 5v, 12v, etc. (I'm talking
output voltage -- to the powered device -- not the
plug-in-to-the-wall portion.) Current can be increased -- the
device will only take what it needs. A 1,000mA ( = 1A) device
will not be happy using a 750 mA (0.75A) wall wart; it will be
quite happy with a 1500mA (1.5A) or 2000mA (2.0A) wall wart
supply, again only using what it needs, but now we have 'extra
current' available for starting up, etc.</p>
<p>And charger wall warts are really sloppy: don't need to be
precise, and they definitely are not.</p>
<p><br>
</p>
<p>As for power cycling, I have found some devices need to be
restarted and restarted: memory gets full or something. The
Raspberry Pi Frontends I have around here have a weekly cron job
to reboot just so I don't have a problem ten days, two weeks,
whatever later and have a lock up mid-show. ...I'd be tempted to
put the HDPVR on a timer control -- WiFi, X10 - just because I'm
lazy: do work now to save work later! <br>
</p>
<p><br>
</p>
<p>Barry<br>
</p>
<p><br>
</p>
<p><br>
</p>
</body>
</html>