[CRTech] Christian Radio Tech [MSG 81527]
[Thread Prev] [-- Thread Index --] [Thread Next] [Date Prev] [-- Date Index --] [Date Next]
RE: Feeding serial x2 (WAS:BSI Auto...)
To: CRTech <crtech@crtech.org>
Subject: RE: Feeding serial x2 (WAS:BSI Auto...)
From: Jesse Diller <jdiller@weec.org>
Date: Fri, 15 Dec 2017 16:24:37 +0000
Accept-language: en-US
Content-language: en-US
In-reply-to: <CAOkhgWqGcPeVGkAWeAoYEXwXR-G3AWtDSX=YROaqUqz6o_8o8A@mail.gmail.com>
References: <CAOkhgWqGcPeVGkAWeAoYEXwXR-G3AWtDSX=YROaqUqz6o_8o8A@mail.gmail.com>
Thread-index: AQHTdb/bhZ95VGlsJ0W2UG0nxiWSxqNElPwg
Thread-topic: [CRTech] Feeding serial x2 (WAS:BSI Auto...)

Going the other way, I have had good success feeding multiple devices from multiple sources using the Perle IOLAN; Now all my ENCO Dad automation machines can control my BT 8.4 switchers. As Willie said, you set the ID for each switcher using the onboard DIP switch; then you can address the correct switcher using the ID in the command string.  It “Just Works.”


As a bonus, there is no extra wiring; the IOLAN has an Ethernet jack, and the computers have a virtual serial port; the commands go over the local LAN. 


- Jesse Diller

IT Director, Strong Tower Christian Media
WEEC 100.7FM / WFCJ 93.7FM


From: Willie Barnett [mailto:wbradiolists@gmail.com]
Sent: Friday, December 15, 2017 11:15 AM
To: CRTech
Subject: [CRTech] Feeding serial x2 (WAS:BSI Auto...)


I remember controlling two B'cast Tools 8x2 switchers with one serial port on the AudioVault system at WFIF. It was what you described... both units "listened only" (in parallel) to one serial port.

My rusty memory (hey, we're talking about stuff I haven't seen/touched in 10 years) ;) recalls that each unit had a 1-character "ID", either "0" or "1" which was programmed into  the serial commands. It worked great once I got all of the command strings set properly in the AV system. The system's other serial port controlled the U4K directly. It "purred like a kitten" until the day I left, about 10 years later. (10 years ago, now!)

You could "cheat" by modifying a couple of cables and disconnecting the TXD line from the devices you're controlling, only using their RXD lines (and ground, of course), to make them "listen-only".

A "normal" cable could be used for programming/troubleshooting one at a time, as needed.




On Fri, Dec 15, 2017 at 9:35 AM, Dan Harder <dan@am91.org> wrote:

NOTE: Doing it this way is ugly and may not work. I had several people tell me it wouldn’t, but it did in my circumstance. At the time I was using the ENCO Dad (before windows).

I had one serial port to control two serial devices, so tried splitting the serial cable.

Because the syntax of the commands for the different devices was different, one device ignored the commands of the other. I think I had to begin each command with a carriage return to “clean the cobwebs” of any unknown command before sending, and I think the baud was relatively low, but after experimenting and learning it worked without fail for 4-5 years before the station was sold.

Neither serial device “talked back” to the computer. Just listened.

Good luck.


This email was scanned by Bitdefender

References: Feeding serial x2 (WAS:BSI Auto...)
(Willie Barnett <wbradiolists@gmail.com>, 15 Dec 2017 16:15:44 -0000)
Prev by date: Feeding serial x2 (WAS:BSI Auto...)
(Willie Barnett, 15 Dec 2017 16:15:44 -0000)
Next by date: Re: BSI Automation upgrades
(Terry Cowan, 15 Dec 2017 16:38:14 -0000)
Prev by thread: Feeding serial x2 (WAS:BSI Auto...)
(Willie Barnett, 15 Dec 2017 16:15:44 -0000)
Next by thread: FM Translators
(KGBA Radio, 15 Dec 2017 17:42:04 -0000)