[RDD] I am starting to hate USB

Wayne Merricks waynemerricks at thevoiceasia.com
Thu May 26 12:00:43 EDT 2016

How do you get on if you use something like screen to talk to the 
serial connection directly?

The broadcast tools switchers have very simple serial commands you can 
use so Riv is not strictly necessary.

I use this:


Then I have macros that instead of doing ST 0 1 2, I just run my script 
instead (RN 1 2).  If you're already using a script to remap the USB 
then using screen like this might work:

screen -fn -L -d -m -S switcher /dev/ttyUSB0 9600 (<- connect to the 
port do this after you remap)
screen -S switcher -X stuff *0012  (<- send input 01 to output 2)

On 2016-05-26 15:47, Rob Landry wrote:
> WCRI has a Rivendell machine that uses a USB-to-serial converter to
> talk to a Broadcast Tools audio switcher. The machine occasionally
> "forgets" the USB-to-serial converter (which is normally 
> /dev/ttyUSB0)
> and then wakes up and remaps it as /dev/ttyUSB1.
> Now, I have a udev rule in place that automatically creates a symlink
> o whatever device the converter gets mapped as... but if it gets
> remapped while rdairplay is running, rdairplay can't talk to the
> switcher until I stop and restart the Rivendell service.
> On Tuesday, I discovered that I could get around the problem by
> stopping and restarting the ripcd daemon, so I set up a cron job to
> detect the remapping of the USB-to-serial converter and autoatically
> stop and restart ripcd.
> That turned out to be a mistake; it seems to have caused rdairplay to
> lose the ability to chain to the next day's log. Two days in a row 
> the
> station has gone silent at midnight, and we've had to load the log
> manually.
> The only solution I can think of is to use a machine with an actual
> serial port.
> Have any of y'all enocuntered this issue? If so, how did you deal 
> with it?
> Rob

More information about the Rivendell-dev mailing list