On Monday 01 June 2015 08:57:05 am Rob Landry wrote:
> There is something about USB devices that makes them prone to name
> changes.
And that is the relatively random nature of things at the exact moment
the IRQ is raised.
> I've had to make a file /etc/udev/rules.d/10-ftdi.rules with the
>
On Fri, 29 May 2015, James L. Stewart wrote:
Finally, just checking, you DO have the full path name to the "TTL Device" in
your "Serial port setup" as in "/dev/ttyS0" not just "ttyS0"? I'm also
assuming that ttyS0 is in fact your serial port and not something like
"/dev/ttyUSB0"? (I'm thin
laudio.org
[mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of James
L. Stewart
Sent: Friday, May 29, 2015 1:08 PM
To: rivendell-dev@lists.rivendellaudio.org
Subject: [RDD] Trying to get Rivendell to work with Broarcast Tools
Since we do this all the time with a BT ACS8.2 switcher, let
suming that ttyS0 is in fact your serial port and
not something like "/dev/ttyUSB0"? (I'm thinking you have this right
from your testing with minicom)
On 5/28/2015 10:00 AM, rivendell-dev-requ...@lists.rivendellaudio.org wrote:
Date: Wed, 27 May 2015 22:18:08 -0400
From: "Jo
What happens if you connect a second computer to the Rivendell machine's
serial port and run minocom on it? Can you see the commands Rivendell is
sending?
Rob
On Wed, 27 May 2015, Joe Panarello wrote:
Hi;
I wonder if anyone has had this problem or could shed some light on the
issue. We ar
Hi;
I wonder if anyone has had this problem or could shed some light on the
issue. We are trying to integrate a Broadcast Tools Switcher SRC-16+ to use
on a new Rivendell installation 2.10.3. The problem is that we cannot get
Rivendell to communicate with the switcher.
We are able to talk to the BT
