On Wed, 21 Aug 2019, Jamie Dennis wrote:
I am building a new machine and have installed the latest version of RD. The machine seems fine but I am having issues with my switcher, the BT ACS 8.2 Plus. There are no serial ports on this machine so I am connecting the switcher to the computer via a USB to Serial Adapter, which the computer recognizes.
The motherboard may have a serial port that isn't brought out to the back panel. Most of the recent motherboards I've seen have had them.
The first time I run any macros that change sources, it works flawlessly. But if I run a second macro that changes sources within a couple of minutes, nothing happens. Its like there is something hung-up.
In my experience, USB-serial converters tend to get remapped by the operating system. They can show as /dev/ttyUSB0 one moment, and /dev/ttyUSB1 the next. The last time I had occasion to use oe, I set up a udev rule to give it an alias (e.g. /dev/switcher0) which it retains no matter how the OS maps it.
Here is how I have the Serial configured ... Serial0 Enabled TTY Device: /dev/ttyUSB0 Baud Rate: 9600 Parity: None Data Bits: 8 Stop Bits: 1 Terminator: None
That looks right. Do you have the DIP switches on the ACS 8.2 Plus set correctly?
I have a feeling that the problem might be with the way RD is talking to the adapter but like I said, it works at first than seems to hang-up for minutes before you can execute another command to the switcher.
I had a similar problem with a new ACS 4.1 just last night; it turned out to have an incorrect DIP switch setting ("remote" instead of "PIP").
If you temporarily stop the Rivendell service and install Putty, you'll find it an excellent diagnostic tool.
Rob -- Сквозь грозы сияло нам солнце свободы И Linus великий нам путь озарил; Нас вырастил Stallman на верность народу, На труд и на подвиги нас вдохновил.
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
