Directv serial channel changer

[shnack]

Ok, so I had to break it up anyway. Here's the rest of the results:

C:\Program Files\devnz\gbpvr\utilities>directv -port com5 -box d10200 -set new -verbose on -text "Hello There"
Settings:
Port: COM5 Baud: 9600 Box: D10200 Retries: 0 Verbose: ON Hex Command Set:
NEW
Display Text: Hello There
Open port to receiver
Openning Command Start: 0XFA ...SUCCESS
Sending Command: 0XAA ...SUCCESS
Sending Command Data [0X0C 0X48 0X65 0X6C 0X6C 0X6F 0X20 0X54 0X68 0X65 0X72 0X6
5]...(command wrote (12 bytes) status [0xf2])...SUCCESS
Sending Command Complete: 0X0D ...SUCCESS
Reading Reply Status For Command: (valid status [0xf0])...SUCCESS
Reading Command Status: ...(read status 0xf2)...FAILED
Failed to send dss command
Clearing Data Port: ..SUCCESS


C:\Program Files\devnz\gbpvr\utilities>directv -port com5 -box d10200 -set new -verbose on -hide
Settings:
Port: COM5 Baud: 9600 Box: D10200 Retries: 0 Verbose: ON Hex Command Set:
NEW
Hiding Text Output
Sending Command: 0x86
Open port to receiver
Openning Command Start: 0XFA ...SUCCESS
Sending Command: 0X86 ...SUCCESS
Sending Command Complete: 0X0D ...SUCCESS
Reading Reply Status For Command: (valid status [0xf0])...SUCCESS
Reading Command Status: ...(read status 0xf4)...SUCCES

[cheval]

Thanks again for the effort in resolving this it looks like we ar getting closer......

From the looks of it the code is not able to handle the f2 in process message properly for commands that send additional data with the commands (key sequences and text message). I should be able to fix that shortly.

You are right regarding a possible timing problem. In one of the key sequences we actually got an f3 timeout response. I need to look at that in more detail to figure out if it was a result of the problems with the way I handle the additional data or if there is another problem.

Either way there will be another update shortly for the first problem. I'll let you know if I figure something out about the timing.

If there is anyone out there using a D10-100 receiver I would love to get some feedback on the programs performance with that receiver.

[cheval]

Another day another release.

This latest release will hopefully get channel changing to be more stable. If not correct the errors in the protocol.

I've remove the "verbose" option and replaced it with a debug version of the code. If you want to see the text output then use the debug version. Text output will be on all the time in that version.

Once its working then switch to the non debug version. Less work it has to do to change channels, etc.

The code base for the two versions is the same. Just some output is compiled out in the non debug version.

[shnack]

Well, I've got the new version, and it seems to be working pretty good. It seems like it's changing channels a little quicker and making fewer mistakes. Thanks for all the work you've done on this project!

[cheval]

Glad it performing better. You might try bumping up the retries count "-retries 3". You comment is basically the same as some other sites have been saying about the d10-200 channel changing.

If you want to work more to try to resolve it, I'm happy to try to get it A LOT MORE reliable. There are some timing parameters on the serial port that may be to fast/slow for D10 to handle. Or maybe there are some more things I can do in the program to recognize the error has occured and fix it.

Either way I guess I would need a few examples to output from the debug version to see what is going on during those situations. If it happens often enough then 5-10 examples would be great.

Another option is to setup the debug version up to always dump output to a file when GBPVR is using it to change channels. Then after a day or two there should be enough data.

There is another question. On your remote is it select or enter that you use to jump to the channel. The reason I ask is there are actuall two different codes and I'm wondering if you get better performance out of one versus the other: "296select" or "296enter"

One last question, would there be any value to another command "!<channel>". Where I would confirm that the receiver has changed to the requested channel. If not keep trying to change for a few times.

[teaboss]

Where can I purchase one of these cables for my D10? Why do you like the serial over the ir?

[cheval]

They are sold here and there over the internet. I actually just built my own cable. If you have access to an old phone handset cord (somwhat hard to find with all the wireless ones) then it really is easy. Garage sales are a good spot and Goodwill. After that the local electronics store has the DB9 connectors. They should have a solderless one available if you don't want to solder.

I like serial much better because for my RCA receivers it has speed up channel changing by A LOT! Meaning I can go back to my habit of channel surfing in live-tv mode.

[shnack]

Sorry for not replying earlier. I tried the "-retries 3" option, but I'm not too sure if it's doing much. It's still pretty accurate at changing channels, but does still make a mistake from time to time. I'll see if I can get some debugging output tomorrow.

As for the remote, it's labelled Select. As for the !<channel> command, it seems like it could be useful for when the channel "misfires" to try again.

[shnack]

Well, for whatever reason, gbpvr doesn't seem to actually want to dump the output to a file (I tried adding ">> filename.txt" as a parameter to the debug version and it changes the channel, but doesn't create/modify the text file), so I just changed channels manually via command line several times. I'm hoping this will give you the info you need. After every channel change I also ran a "-get channel" to make sure it's right. I've uploaded the text file in zip format. Let me know if you have any more questions.

[jchiso]

cheval:

Would you please PM me so I can send you some debug info?