On Tue, Mar 8, 2011 at 6:11 PM, Nasa <span dir="ltr"><<a href="mailto:nasa01@comcast.net">nasa01@comcast.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><br>
----- "Gabe Rubin" <<a href="mailto:gaberubin@gmail.com">gaberubin@gmail.com</a>> wrote:<br>
<br>
> On Tue, Mar 8, 2011 at 3:47 PM, Nasa <<a href="mailto:nasa01@comcast.net">nasa01@comcast.net</a>> wrote:<br>
> ><br>
> > ----- "Stephen Otto" <<a href="mailto:sotto@emsco.com">sotto@emsco.com</a>> wrote:<br>
> ><br>
> >> From: Christopher Meredith [mailto:<a href="mailto:chmeredith@gmail.com">chmeredith@gmail.com</a>]<br>
> >> Sent: Tuesday, March 08, 2011 3:43 PM<br>
> >> To: Discussion about MythTV<br>
> >> Cc: Stephen Otto<br>
> >> Subject: Re: [mythtv-users] Comcast STB upgrade breaks firewire<br>
> >> channel changing<br>
> >><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> On Tue, Mar 8, 2011 at 10:04 AM, Stephen Otto < <a href="mailto:sotto@emsco.com">sotto@emsco.com</a> ><br>
> >> wrote:<br>
> >><br>
> >><br>
> >> > About a week or two ago, Comcast sent out a ton of promotion<br>
> >> material<br>
> >> > pushing on-demand content. I didn't pay much attention to it.<br>
> But<br>
> >> > shortly after that, they pushed a software update to my STB<br>
> (Cisco<br>
> >> > RNG-150) that looks to be completely new. The layout and color<br>
> of<br>
> >> the<br>
> >> > menus are completely different and the guide bears the "TV<br>
> Guide"<br>
> >> > logo. Anyway, this update also broke firewire channel changing.<br>
> I<br>
> >> have<br>
> >> > been using 'mythchanger' with the -f 6 option to great effect.<br>
> Now<br>
> >> it<br>
> >> > does not work at all. The script detects and unknown STB, but<br>
> cannot<br>
> >> > change channels on it.<br>
> >> ><br>
> >> ><br>
> >> > Has anyone run into this? Is there a solution? Does anyone know<br>
> >> > anything about this software "upgrade?"<br>
> >><br>
> >> For the last month plus, my firewire capability has stopped work<br>
> >> for exactly the same reason. I had it working for almost 3 years<br>
> >> prior to that -- and hadn't changed anything when it stopped<br>
> working.<br>
> >> I too would love to hear if anyone has solved this. BTW: see<br>
> thread<br>
> >> here<br>
> >><br>
> <a href="http://www.gossamer-threads.com/lists/mythtv/users/457642?search_string=fire" target="_blank">http://www.gossamer-threads.com/lists/mythtv/users/457642?search_string=fire</a><br>
> >> wire%20channel%20change ;#457642<br>
> >><br>
> >> Nasa<br>
> >> _______________________________________________<br>
> >><br>
> >> What are you using for a channel change script? 6200ch? If so, any<br>
> >> chance<br>
> >> that Comcast changed the Vendor ID or Model ID in your STB to<br>
> >> something new<br>
> >> with the update?<br>
> >><br>
> > No,<br>
> ><br>
> > I was using sa3250hd script and tried the mythchanger script.<br>
> ><br>
> ><br>
> >><br>
> >><br>
> >> I've been using the mythchanger script referenced in the thread<br>
> linked<br>
> >> above. I cycled through all the options to no avail. I've been<br>
> >> assuming that it shouldn't matter if Comcast only changed the<br>
> Vendor<br>
> >> or Model IDs because those merely identify the device to the<br>
> computer.<br>
> >> I've been using the -f option in mythchanger to force the protocol<br>
> it<br>
> >> uses, so detection of the device should be irrelevant. Am I right<br>
> >> about that?<br>
> >><br>
> >><br>
> >><br>
> >> I’m not 100% sure but I know that I needed to update the code to<br>
> get<br>
> >> my box working (although I am not sure if originally I was using<br>
> the<br>
> >> –f option or not at the time). Try running mythchanger with a –v<br>
> >> option and see what it reports.<br>
> ><br>
> > I tried this and got:<br>
> ><br>
> > ./mythchanger -c 220 -v<br>
> ><br>
> > mythchanger .10f beta<br>
> ><br>
> > Acquiring firewire handle... OK.<br>
> > 1 port(s) found<br>
> ><br>
> > Acquiring handle on port 0... 1 devices detected.<br>
> > STB Vendor ID: 0x1947 Model ID: 0x0be0, Scientific Atlanta Model<br>
> SA3250HD<br>
> ><br>
> ><br>
> > Skipping empty node 1<br>
> > 1 STB(s) found:<br>
> > -------------<br>
> > STB 1: port=0, node=0, changer=1, GUID=0x0019472d784a0000<br>
> ><br>
> > Note: it didn't change channels...<br>
> ><br>
> Look at my email in this thread, where I link to a prior email sent<br>
> to<br>
> the list detailing what to do this information. Once you have the<br>
> Vendor ID and Model ID, you will need to use that information to<br>
> modify the source code and recompile. It sounds daunting, but it is<br>
> very easy. I can't code and I try not to install from source because<br>
> I seem to always have make error out on me, but this worked fine.<br>
<br>
</div></div>Thanks for the hints (I had missed your earlier email)...<br>
<br>
However, for both sa3250ch and mythchanger, my boxes Vendor ID and Model<br>
ID are already included.</blockquote><div> </div><div><br></div><div>I grabbed the source for mythchanger and added by vendor and model IDs. The cable box is now "recognized" but the channel still cannot be changed.</div>
</div>