Re: Infrared to serial signaler

["Robert Green" <ROBERT_GREEN1963@xxxxxxxxx>]

"Marc_F_Hult" <MFHult@xxxxxxxxxxxxxxxxxxxxx> wrote in message

<stuff snipped>

> Thank you Bobby. This is very helpful. As you know, I also have two
Samsung
> GVI video multiplexors so this is directly pertinent and appreciated.

Your posts about them are what inspired me to purchase some of my own.

> As best I can tell from the description, the Industrologic IR232 only has
one
> input which is soldered to the board, right? IOW, multiple inputs would
> require additional homebrew?

The answer to your question is that I ordered the board and the case and to
my surprise (and delight!) it was already assembled.  Peeking inside I see a
4 wire ribbon cable (actually, it turns out to be a set of SCR leads!).  If
it comes apart easily, I'll look inside and report back.  I've got a bad
history with taking things apart.  I was trying to replace what I thought
were the huge batteries in my Sonicare toothbrush but when I finally
Dremeled it open I found it had two very puny NiCad AA's and a lot of
enameled wire wrapped around iron cores right up the edge of the case where
the cutoff wheel cut them quite neatly. )-:

The IR232 is very small - much smaller than I visualized (about 2.5" square
and 1" thick).  I'm going to use a DB9 switch box to switch between the
functions:

(1) connected to the PC's DB9 to load mapping data and
(2) connected to MUX DB25 serial input for IR to serial operation

The big problem for now is that the database of text/hex commands I've made
from the listing in the GVI MUX manual has 93 records.  So far, no Sony
definition on the UR24 maps more than 22 discrete keys.  I won't need all 93
commands because I can do some things via hyperterm but 22 keys may not be
enough to really manage the MUX remotely unless I can work some magic with
the GVI "macro" function.

One thing that really surprised me was what the IR232 said about my Sony AV
system master remote (RM-P501).  It explained why I've had so much
variability in learning certain codes from this particular remote.  The
IR232 reports as many a four different device/function codes for a single
button press.  Other buttons are context sensitive and change depending on
the state of other button presses.  I think this particular Sony remote (11
devices!) could be made the master remote for the GVI because it appears
able to generate several hundred discrete codes.

> Also, are you controlling two multiplexers from the same  IR232 (using
> multidrop RS-232) ?

Whoa, dude!  The UPS guy just brought it to me!  (-:

Right now, I am sitting at the PC, stepping through all the Sony codes that
are in the UR24A and mapping them to the remote's buttons.  The problem I
can see immediately is that I can't reach cameras 11-16 without doing
something strange.  It's way too early in the process to determine whether I
will be able to connect the two units.  Dan's already discovered some issues
with daisy-chaining them.  IIRC, they ask you to be sure to check the status
of the MUX before issuing a command, but provide no way of actually doing
it. It's also hard to be absolutely sure that something selling for 1/10 the
best street price is 100% functional.  Have you been able to connect the two
MUXes together using the In/Out modular ports on the rear?

What I hope to do in the next few days is to control a single MUX with a
single box.  I believe that if worst comes to worst, a second IR232,
programmed with Sony codes exclusive of the way the first one is set up,
could operate in tandem, requiring me to only select between AUX1 and AUX2
to control either one.  It would be nice to use only one IR232, but that
would some sort of networking connection between the two MUXes or a way to
feed the output of the IR232 to both MUX serial inputs.

I just opened the box and the DB9's soldered to the board and there's about
enough room on the PCB between that connector and the power input connector
to put a small 4 or 6 pin modular phone jack in between them.  You might
also be able to replace the DB9 with a DB15 connector if you needed more I/O
to the unit for some reason.

One other thing that I like:  As soon as you connect the unit and tap ESC
three times, it writes a very thorough "crib sheet" similar to what PKZIP
uses to the screen.  I think it's thorough enough so that most people could
program and reprogram the unit without having to locate the documentation.

Unfortunately, progress will be slower than I like over the next few weeks
as outside maintenance chores begin consuming chunks of time, but I will try
to document what I discover in a timely fashion, even if it leads to the
same dead end the Ocelot did.

--
Bobby G.