Venturer STB7766G settop digital tuner

sixt7gt350 · Post by **sixt7gt350** » Thu Dec 25, 2008 5:12 pm

1. Device: Venturer STB7766G
2. Type of device: Digital settop tuner
3. Year: 2008
4. JP1/UEI Remote model: RCU810
5. Do you have a JP1 cable? Yes
6. Still have original remote? Yes
7. Checked the file section? Yes
8. Checked Pronto file section (at R/C)? Yes
9. Partially working setup code? No
10. Learning remote question? Yes

Can't get either the RS 15-1994 or RCA RCU810 to learn anything from the OEM remote.

Rather than do the smart thing and buy one of the more common DTV boxes that already had Replay RID files available, I bought a couple of these at Target with my gubmint coupons.

One Accurian tuner with three 5040s wasn't going to cut it come February.

Anybody have any knowledge of protocol or UEI upgrades for these beasts?

Thanks.

underquark · Post by **underquark** » Fri Dec 26, 2008 4:27 am

Unless you get a better response, try:

1] Alter you learning technique. Vary the distance between each remote from 1 to 25cm and try learning just one or two buttons (suggest power, ch+ and ch- as most useful starters) many times to different receiving buttons (e.g learn power to 1,2,3,4 then ch+ to 5,6,7,8 etc.).

2] Guess. Try NEC1, Dev 0 and create an upgrade starting with values from 0 to 32 and see if you et at least some response.

Post by **The Robman** » Fri Dec 26, 2008 10:23 am

I wouldn't bother trying NEC1-dev0 because if that were the right code, there wouldn't be any problems learning the signals.

But I do agree that it's worth trying different learning methods to see if you can capture something.

First off, of course, make sure that you have new fresh batteries in all of the remotes.

Then, try different length of button press. The conventional method is to hold the OEM button down until the learning remote indicates it's complete, but if that's not working, try really short presses instead, then try medium length presses. Varying the distance, like UQ suggested is also a good idea.

As soon as you're able to get at least one button to learn, verify that the learn actually works and then post the code. And if you can remember what you did to get it to learn, try to learn more.

sixt7gt350 · Post by **sixt7gt350** » Mon Dec 29, 2008 6:27 pm

No luck with fresh batts, press length, or distance.

I got a killer deal on a new Harmony 520 a few weeks back. ($30 shipped)
The RCU810 learned the Venturer codes from the Harmony.

Now I have to find my JP1 cable! If I can't figure out the protocol, I'll post here for the experts to decode.

(Went to Fry's today to get components for a JP1.3 cable: RS 15-100 needs some love and that stupid left arrow corrected.)

sixt7gt350 · Post by **sixt7gt350** » Mon Dec 29, 2008 7:26 pm

OK, maybe it's been too long and I've forgotten something, but IR should be showing me the learned codes from the RCU810.
It's showing nothing but the raw data.

Someone kick me in the right direction.

Thanks.

<EDIT>
Scratch that.
It wasn't seeing the RDF files, even though it wasn't telling me it wasn't/

sixt7gt350 · Post by **sixt7gt350** » Mon Dec 29, 2008 8:39 pm

OK, IR got the learned-learned signal decoded.
NEC1, Device 66, Sub-device 187

Some of the buttons have strange data, but that's probably from OEM -> Harmony -> JP1 learning
("0" is showing a 37735 frequency, no protocol)
Select and Info are NEC1, device 1.

Post by **The Robman** » Mon Dec 29, 2008 10:43 pm

If you build an upgrade and it works, all's well, but if you can't, load your IR file with the learns and I'll take a look, but first confirm that all the learned buttons work. If they don't, try re-learning them until they do.

sixt7gt350 · Post by **sixt7gt350** » Mon Dec 29, 2008 11:08 pm

Second learn of "0" was 37558 frequency.

Grrr..

Post by **The Robman** » Tue Dec 30, 2008 7:36 am

If there are some buttons that you just can't learn, skip them, because if you're able to get most of the other buttons, we'll probably spot the gaps in the OBC sequence and find them that way.

mdavej · Post by **mdavej** » Tue Dec 30, 2008 3:57 pm

Had one of these in my closet. Man those learns were a b***h! I think they're right, but you'll need to check them all, as some still weren't clean and others were guesses.

EDIT: Deleted file and link. Use sixt7's fixed version below.

sixt7gt350 · Post by **sixt7gt350** » Wed Dec 31, 2008 12:25 pm

mdavej wrote:Had one of these in my closet. Man those learns were a b***h! I think they're right, but you'll need to check them all, as some still weren't clean and others were guesses. HERE it is.

Great and so close!!!

It didn't like OBC 138 for "0" at first, then it did.

Still struggling with signal. (OBC 103)

sixt7gt350 · Post by **sixt7gt350** » Wed Dec 31, 2008 12:40 pm

I found a correction to "CC" in your file.
It should be OBC 140.

Still working on "signal" code.....

sixt7gt350 · Post by **sixt7gt350** » Wed Dec 31, 2008 12:52 pm

Success!

"Signal" was OBC 152.

Now a complete RMDU for someone else to use.

mdavej had all the numbers needed to make a .rid file, but I figured while I was at it, I might as well flesh out the RMDU for anyone else getting the Venturer for the February change.

http://www.hifi-remote.com/forums/dload ... le_id=6054

sixt7gt350 · Post by **sixt7gt350** » Wed Dec 31, 2008 12:53 pm

Now to dig back into the .rid brewing!

Also quite rusty....

sixt7gt350 · Post by **sixt7gt350** » Wed Dec 31, 2008 3:32 pm

Now that the JP1 portion has been completed, I'm starting a new thread in the ReplayTV section.
Robman: Please feel free to move this thread to the "CLOSED" area.

RIDGen is ignoring the subdevice code, 187.
It has no effect on the output HEX file and when I open the .rid file, the subdevice code is missing.