Geoffrey,
You were correct in your assumptions. For all of those that want to
intergrate an ST-CP with a Homevision controller, you must create a
crossover cable. On the ST-CP you must have an rj-11 with 2-grnd 3 -
rx 4-tx. On the Homevision you must have a male DB9 to female rj-11
with 5- grnd, 3- tx 2-rx (rx is tx and tx is rx on the HV coming from
the ST-CP).
Thanks, you are a treasure in this forum.
--- In Crestron@..., "goldengot" <goldengot@...> wrote:
Geoffrey,
I think you hit the nail on the head!
Looking at the doc, I see that the pinouts for the two are
different. I will make a x-over cable at work tomorrow and let you
know if it works or not.
Thanks again
--- In Crestron@..., "Geoffrey Reynolds" <greynlds@>
wrote:
For the purposes of getting this going, a SerialIO symbol with an
input tied
directly to your touchpanel should suffice.
My guess is that you have the serial port on the ST-CP configured
to the
wrong baud rate (or other parameters) OR that the serial cable
you're using
to connect the ST-CP to the HomeVision is wired incorrectly.
Take HomeVision out of the equation - get the ST-CP sending
strings to
Terminal Emulator (set the same way it was when you used it to
connect to
HomeVision). Once you have that working, you should be able to
connect that
cable to your HomeVision controller and get the results you're
looking for.
--
Geoffrey Reynolds
----- Original Message -----
From: "goldengot" <goldengot@>
To: <Crestron@...>
Sent: Saturday, January 12, 2008 6:03 AM
Subject: [Crestron] Help with Homevision
I can't seem to figure this one out. I am trying to use HV and an
old ST-CP to control x-10 lights in a particular room. I created a
simple SIO that maps back to a homevision controller with the
ASCII
string 'lights' in str1 which is tied directly to the touchpanel.
So in theory when the user pressed the hv_light button it sends a
string through the serial into the home vision. The home vision
has
been configured to accept any text over 1 character (testing
purposes). When the button is pressed, nothing happens. It works
within the terminal emulator, but not connected to the st-cp.
There
was a post by Geoffrey Reynolds detailing how to do this (see
below)
The homevision part works just fine but the Crestron piece is
another question. It appears to be sending hex through the serial
and not ASCII. If anyone has had any experience in setting up
Crestron alongside Homevision, please detail your exact steps
(i.e.
which mods were used if any, which analog or digital symbols,
strings that were used, if you had to convert using HEX, which
baud
rate is used on the serial driver, etc. In other words, any
information that you can give me that would make my life easier.
TIA
In HomeVision:
From the main menu, select Objects/Events -> Serial Data Input ->
Port1
(substitute Port2, Port3, etc. as appropriate for your situation)
This will give you a window where you can program HomeVision to
respond to
events on a serial port.
Next, configure the logic that will handle serial events by, for
example,
setting up a series of If - Then - End If statements. Start by
clicking the
If Then button in the ACTIONS toolbar. Next, the ACTIONS toolbar
switches
to the CONDITIONS toolbar. Now, select the SERIAL button. I've
found
the
most useful condition to be "Serial input characters # through #
are
:'____' - this lets you listen for a specific string to come from
the
Crestron controller. Now enter the string you want and press OK.
Now
click
on End If and the toolbar switches back to ACTIONS. Click X10 and
choose
the X10 action you want to perform. That's all you need to do on
the
HomeVision side. It sounds a bit clunky (and is), but is pretty
easy
to use
and will work very reliably once you have it programmed.
Now just program your Crestron program to send the appropriate
strings
terminated with \n. HomeVision has default support for it's OSD
remote
control commands, so some strings are reserved:
,J0\n = 0
,J1\n = 1
...
,J9\n = 9
,JA\n = Enter
,JB\n = Channel Up
,JC\n = Channel Down
,JD\n = Volume Up
,JE\n = Volume Down
,JF\n = Cancel
