RCA Reciever DRD515R

[nef]

Trying to get the serial port functionality to work on this reciever. Is there any way i can test the com port to see if its working? When i bring up hyperterminal to com1 on 8n1 at 9600 baud, i dont get anything at all. Am i supposed to see text?

Thank you
-nef

[fulltilt]

Yes, if you have it hooked up correctly you will see what looks like a divide symbol returned from the RCA unit every time you press any key.

It should be returning an extended ASCII code for the character represented by hex FB.

See this table for what FB looks like in hyperterm. http://www.jimprice.com/jim-asc.htm#extended

I found that the RS232 connections for my RCA DRD303RA should be as follows.
DB9 DB15 Signal
5 13 GND
2 14 RD
3 6 TD
This works for me.

This pinout is also confirmed by reverse engineering the DB9 to DB15 adaptor supplied with a Phillips Tivo unit.

I also created some binary files with codes to control the RCA box and sent them to it via Hyperterm and they worked so I knew I had it right.

I installed SnapStream with the dss.dll and it worked the first time.

[z0rak]

fulltilt,

sounds like you're really on the stick with your SnapStream DSS hookup. I am trying to gather info in order to improve the DSS dll (namely provide an satellite autodetect function).

If you would be so kind, could you set up a hyperterm connection, power off your dss, and then power it back on. If it is anything like my sony DSS (which up to this point it seems to match exactly), your should get some sort of power on message from the unit.

If you do get some sort of message when you turn the unit back on, would you be so kind as to dump me a log of your hyperterm session so that I can analyze it for inclusion in the dll??

I know this is asking a lot, but I'd really like to make the use of this dll easier for everyone. Your help will be instrumental in this. Thank you in advance for your time !

-z0rak

[fulltilt]

I will try and gather the data you need tonight or tomorrow.

Question for ya. Do you have any kind of a test program for your dss.dll that allows you to remotely control the DSS receiver from the PC manually?

[z0rak]

Sorry, but I really don't... I suppose I could hack one together pretty quick. Actually it's a good idea in order to test the new autodetect functions I'm trying to write.

[This message has been edited by z0rak (edited 05-22-2001).]

[This message has been edited by z0rak (edited 05-22-2001).]

[fulltilt]

I haven't forgotten about this. I tried hooking the laptop back up like I had it before and now it won't respond at all. The other PC that I have snapstream running on is able to control the DSS and everything works normally there. When I try to use Hyperterm from it though I get nothing again. This has me puzzled and I will keep working on it. In the meantime it would be great to have some type of TCL/TK type of program to interface to dss.dll to be able to debug this with. Any volunteers. I am an electrical engineer and I have made EIA-561 adaptors for the DSS and PC so I can run the signals over standard CAT-5 wiring in my house. That part works fine. It's all plug and chug as they say.

Does the dss.dll put the DSS receiver in some no-echo mode or something?

Power cycling didn't seem to change anything WRT this.

[z0rak]

I'll give a whack at the test prog for the DSS dll tonight. It won't be TCL/TK prog tho I'm more proficient in VB.

When you say you power cycled your unit, do you mean that you just turned it on off/on using the remote or front panel button? If so, try unplugging the unit, and leaving it disconnected for a few before you try again. My Sony has done this exact thing before (inexplicably), and the only way out was disconnecting it for a bit (I though I toasted it the first time - very scary). Seems that the DSS receiver's internal circuitry, which includes the serial stuff, is always on, and that powering the unit down merely disables the video/audio outputs.

As far as this being a defect of the DLL, anything is possible, but I've gotten the same symptoms you describe by merely using hyperterminal (long before I wrote the DLL).

I think the Cat-5 wiring idea rocks... do you transmit AV signals as well as control signals for the DSS? If so, we need to talk... I've got a move coming up and could use some advice in how to wire my new batcave.

[z0rak]

Okay, I've written a test program for the dll. In doing so, I had to create a slightly modified version of the DLL (one that was callable from VB) but the internal logic is unchanged. You should be able to replace the dll in your tuner directory with this one with no ill effects.

Email me and I'll send you the dll and test .exe (about 100K combined). I haven't built a setup program for this so you'll need the VB runtime libraries.

[fulltilt]

I only powered the DSS off from the front panel. I figured the next thing to try was to unplug it as you suggested. I'll do that next chance I get.

Wiring the next bat cave? I suggest you "don't wire it at all" like I did when I built my house ~10 years ago. I installed 4" square boxes with raised plaster covers in each room where I wanted low voltage to run to. I then used Carlon flexible PVC conduit to make runs to the basement. Now I am set for life as far as what type of media I want to run into the rooms. When I built the house CAT-3 was the only thing available so I ran that. I have since pulled most of that out and rerun CAT5. I have this conduit system throughout the house for thermostat / phone / data / video / security / door bell / etc. It's the only way to go.

Yes, AV can be run over CAT5 wiring. I am not currently doing this in my house but I do it all the time at my work.

[z0rak]

Wish I could run to the basement, but In Virginia Beach, no basements... the water table is too high

I've seen baluns for running AV signals over CAT-5, but at almost $200 bucks a pop for each run, i would quickly go bankrupt... know any cheaper sources or have a schematic? I'm not afraid of a soldering iron if thats what it takes.

[fulltilt]

Well, I tried powering off the DSS by unplugging it for a few minutes and then powering it back up. No effect. Still nothing. I know this was working when I first started playing with it. I have a file with the catured output of the get-sub-info command.

[fulltilt]

An alternative if no basement is available is to install a large pull box near the main electrical panel for all the low voltage stuff to run to. Conduit systems are forever upgradeable. Yes, AV baluns are expensive, ie. why I use them at work but not at home.

[fulltilt]

Did some more playing around this morning with the connection to the RCA DRD303RA DSS via the Wide Band Data (really async serial RS232) port. I found that when using Hyperterm to connect to it you need to set flow control to "none". If it is set to "hardware" which is Hyperterm's default Hyperterm doesn't send anything. I'm sure that's because I don't have all the RS232 hardware handshake signals nailed up. Anyway if flow control is set to "none" Hyperterm communicates with the DSS just fine. I did several powerup tests and the RCA always sends the same thing. It sends a hex 0x55 or ASCII "U" upon power up. That's it. When I type an "Enter" on the keyboard I get back the checkmark, 0xFB, divide symbol.

Summary:

Using Hyperterm the settings should be:
9600, 8 data bits, No parity, 1 stop bit and flow control set to "none".

You should get a 0xFB (checkmark or divide symbol) back whenever you type anything on the keyboard.

[This message has been edited by fulltilt (edited 05-27-2001).]

[z0rak]

Thanks for giving it a shot... I'll have to look close at my sony dump to see if it spits back a similar code on power up. At least you've identified a tangible difference between the sony and RCA DSS receviers, which goes a long way towards me being able to differentiate between them. Thanks a bundle for your efforts in this matter, and for the info that you've contributed. Rest assured that I will consider the changes you've recommended for the test DLL and EXE.

For the benefit of everyone else, I've created a test versio of the serial tuning dll and a test executable to allow you to directly tune channels on your serial connection outside the Snapstream environment so that you may test your serial connectivity and make sure that all is above board before you jump in snapstream recording. If there is any interest, I will post the url for the downloads...

-z0rak