Do D11-100s go to sleep

[trini0]

There are a total of 3 in the house. I'll try swapping one to see what happens.
But before I do that, I'll try a hard reset of the stb.

[bcjenkins]

Is it only one causing issues?

[trini0]

The other 2 are not connected to the server. But as far as I can tell, they do not have any problems.

[trini0]

This is for future reference. If anyone wants to reset the counter for "USB Reset", just double click the number, and it will reset to zero, and the paterson device will reinitialize.

I changed the settings (dont remember right now, but I'll check it later).
I set a program to record 4 hrs in the future, and let it sit idle as I've been doing.
Around 6:15 the program started, and it tuned to the correct channel. But dummy me, had opened the Sage Client UI a few minutes early (Just the UI, not LiveTV). Not sure if that contributed to the successful channel change. But I have another program to record at 12am, so I'll see what happens then.

[trini0]

The 12am test failed, and the fight goes on...

I'm looking over the logs, and I notice something that I didn't see before

Here is what happened at 12am, when it didn't tune

Wed 6/20 0:00:01.039 Seeker channel string=503
Wed 6/20 0:00:01.039 dtvSerialChannel(handle=3084, chan=503)
Wed 6/20 0:00:01.044 DTVSerial Valid Command Recognized for handle 3084
Wed 6/20 0:00:02.543 Incomplete COM Read on handle 3084

Here is what happened a few minutes later, when it tuned successfully

Wed 6/20 0:18:42.187 Seeker channel string=330
Wed 6/20 0:18:42.188 dtvSerialChannel(handle=3084, chan=330)
Wed 6/20 0:18:42.189 DTVSerial Set Top is Processing Request for handle 3084
Wed 6/20 0:18:42.189 DTVSerial Unknown Command Response on handle 3084 of 0xf5

Here is another successful tune

Wed 6/20 0:28:41.841 Seeker channel string=244
Wed 6/20 0:28:41.842 dtvSerialChannel(handle=3084, chan=244)
Wed 6/20 0:28:41.843 DTVSerial Valid Command Recognized for handle 3084
Wed 6/20 0:28:41.843 DTVSerial Set Top is Processing Request for handle 3084
Wed 6/20 0:28:41.843 DTVSerial Command Successful for handle 3084

And one more successful tune

Wed 6/20 0:31:22.018 Seeker channel string=7
Wed 6/20 0:31:22.019 dtvSerialChannel(handle=3084, chan=7)
Wed 6/20 0:31:22.020 DTVSerial Valid Command Recognized for handle 3084
Wed 6/20 0:31:22.021 DTVSerial Set Top is Processing Request for handle 3084
Wed 6/20 0:31:22.021 DTVSerial Command Successful for handle 3084

I'm currently using the DirectTVSerialControl.dll file dated 5/1/2006
I'm going to go back to the current version dated 4/17/2007. Even though I had the problem with the newer version, I want to see if the logs are the same. If they are, I'm going to send them in to Sage to see what they say, as I'm running out of ideas.

[bcjenkins]

Is this a new stb or same? What port is bafo on? I am on the latest dll myself.

B

[trini0]

6 am test failed...
This is with the latest version of DirectTVSerialControl.dll

Wed 6/20 6:00:00.008 Seeker channel string=7
Wed 6/20 6:00:00.008 dtvSerialChannel(handle=2944, chan=7)
Wed 6/20 6:00:00.008 DTVSerial using fast channel changes
Wed 6/20 6:00:00.008 DTVSerial ignoring replies for wait
Wed 6/20 6:00:00.013 DTVSerial Valid Command Recognized for handle 2944
Wed 6/20 6:00:01.512 Incomplete COM Read on handle 2944, poking the receiver...
Wed 6/20 6:00:01.514 DTVSerial Valid Command Recognized for handle 2944
Wed 6/20 6:00:02.014 DTVSerial Set Top is Processing Request for handle 2944
Wed 6/20 6:00:02.018 DTVSerial Unknown Command Response on handle 2944 of 0xf5

Here is a successful tune

Wed 6/20 6:38:04.078 Seeker channel string=202
Wed 6/20 6:38:04.078 dtvSerialChannel(handle=2944, chan=202)
Wed 6/20 6:38:04.079 DTVSerial using fast channel changes
Wed 6/20 6:38:04.079 DTVSerial ignoring replies for wait
Wed 6/20 6:38:04.083 DTVSerial Valid Command Recognized for handle 2944
Wed 6/20 6:38:04.096 DTVSerial Set Top is Processing Request for handle 2944
Wed 6/20 6:38:04.102 DTVSerial Command Successful for handle 2944

Here is another successful tune

Wed 6/20 6:40:43.209 Seeker channel string=612
Wed 6/20 6:40:43.209 dtvSerialChannel(handle=2944, chan=612)
Wed 6/20 6:40:43.210 DTVSerial using fast channel changes
Wed 6/20 6:40:43.210 DTVSerial ignoring replies for wait
Wed 6/20 6:40:43.214 DTVSerial Valid Command Recognized for handle 2944
Wed 6/20 6:40:43.228 DTVSerial Set Top is Processing Request for handle 2944
Wed 6/20 6:40:43.230 DTVSerial Command Successful for handle 2944

So it looks like once I get that incomplete COM read, that is when it fails.
What is causing the errors on the COM port? Not sure.
I don't think its a hardware issue, as I can repeat the error with a fair amount of certainty. Usually hardware problems are random.
I'm going to get Sage involved to see if they have any ideas.

[trini0]

Originally Posted by bcjenkins

Is this a new stb or same? What port is bafo on? I am on the latest dll myself.

B

This is with the same stb. I'll try another stb this morning.
The bafo is on Com Port One

[trini0]

I swapped out the stb

It got way worse...

Wed 6/20 8:26:40.602 Seeker channel string=244
Wed 6/20 8:26:40.602 dtvSerialChannel(handle=3076, chan=244)
Wed 6/20 8:26:40.603 DTVSerial using fast channel changes
Wed 6/20 8:26:40.603 DTVSerial ignoring replies for wait
Wed 6/20 8:26:40.607 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:26:42.106 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:26:42.108 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:26:43.607 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:26:43.609 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:26:45.108 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:26:45.110 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:26:46.609 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:26:46.611 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:26:48.218 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:26:48.218 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:26:49.717 Incomplete COM Read on handle 3076

Wed 6/20 8:30:49.975 Seeker channel string=202
Wed 6/20 8:30:49.976 dtvSerialChannel(handle=3076, chan=202)
Wed 6/20 8:30:49.976 DTVSerial using fast channel changes
Wed 6/20 8:30:49.977 DTVSerial ignoring replies for wait
Wed 6/20 8:30:49.980 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:30:51.480 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:30:51.481 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:30:52.981 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:30:52.982 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:30:54.482 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:30:54.483 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:30:55.983 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:30:55.984 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:30:57.593 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:30:57.594 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:30:59.086 Incomplete COM Read on handle 3076

Wed 6/20 8:32:28.915 dtvSerialChannel(handle=3076, chan=503)
Wed 6/20 8:32:28.915 DTVSerial using fast channel changes
Wed 6/20 8:32:28.915 DTVSerial ignoring replies for wait
Wed 6/20 8:32:28.919 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:32:30.418 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:32:30.420 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:32:31.919 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:32:31.923 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:32:33.422 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:32:33.424 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:32:34.923 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:32:34.925 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:32:36.424 Incomplete COM Read on handle 3076, poking the receiver...
Wed 6/20 8:32:36.426 DTVSerial Valid Command Recognized for handle 3076
Wed 6/20 8:32:37.926 Incomplete COM Read on handle 3076

Its not tuning at all now.
I've already rebooted the server, and power cycled/hard reset the stb.

So is the problem with the stb. Is it that much of a hit/miss to get a good stb???

[bcjenkins]

I would submit these to support. Is this the same model receiver? You did buy the right PatersonTech device, right? (There's two) The only other suggestion I could offer is changing the comport to something higher than 1. I realize your mobo doesn't have a serial port on it. I run mine 4,5,6,7.

B

P.S. Have you tried tuning outside of Sage with some of the software on the Paterson site?

[trini0]

All 3 are D11-100.
Yeah I ordered the USB TV Translator (TV3). Unless they sent me the wrong item.
I'll try a higher port number.
I'll try testing with an external app later today...

[trini0]

I took the day off yesterday from debugging.

I changed the port number to 4 per your suggestion (even though all on board ports are disabled in the bios).
But I'm still having the problem changing channels.

I just tried using the DTVCon app, to change channels on the stb.
It seems to be working fine. Even turns the stb on/off.
I last changed the channel at 12:49pm using DTVCon.
I will try changing the channel with DTVCon in about 4 hrs, to see if it will change or not.

[trini0]

Originally Posted by trini0

I last changed the channel at 12:49pm using DTVCon.
I will try changing the channel with DTVCon in about 4 hrs, to see if it will change or not.

Around 4:32pm, I went back to the server, and used DTVCon to tune to several channels. It worked fine. So its definately not a hardware problem, and a problem with Sage.

I'll collect the logs for Sage tomorrow...

[bcjenkins]

let us know what you find out

[bcjenkins]

Forgot to ask, are you running service mode?

B

[trini0]

Originally Posted by bcjenkins

Forgot to ask, are you running service mode?

B

Yes

[trini0]

Adding the debug file to thread so that Sage (or whomever wants to) can view it.

Just search for "Seeker channel string".
At 1:00am and 5:05am, you'll see the attempts to tune a channel, and the COM read error

[bcjenkins]

did you mail them to support at sagetv dot com?

[trini0]

I used the web form @ http://www.sagetv.com/request.html
And I referenced this thread in it.

[trini0]

Reply from Sage ->

The DTVControl program you are testing with most likely opens the serial port each time it sends a command. SageTV doesn't do it that way because it's inefficient for doing automatic detection of what type of receiver it is.

The problem is likely in the driver for the USB-serial adapter you are using. You should try using a different USB-serial adapter to resolve the issue.

I have mixed feelings about the response.
I'll be upset if I get another BAFO adapter, and it doesn't work...
bcjenkins, where did you purchase yours, so that I can try purchasing it from them.

Thanks