Re: [RDD] Rivendell and Broadcast Tools switcher.
Hi, I'm not sure if this is a broadcast appliance install or something else, but one thing that I've run into on Ubuntu based distributions is the user ID that you're running Rivendell as needs to be a member of the dialout group in order to access the serial port. Especially if you're running the daemons under a different user ID from the ID you're running the GUI under, you'll need to add the user ID's that runs the daemons to dialout or else it won't be able to access the serial port. I don't know if this is the problem, but it is something to look at. > > If you get correct results in Minicom but not in Rivendell, the problem > might be Rivendell-related. > > But if you never get correct results even in Minicom, then you've got a > hardware problem (bad serial port? bad cable? incorrect pinout?) or a > configuation problem. > > > Rob > > -- > Я там, где ребята толковые, > Я там, где плакаты "Вперёд", > Где песни рабочие новые > Страна трудовая поёт. > > On Mon, 6 Mar 2017, James Greenlee wrote: > > > > > As far as producing the "correct" result...That would be a negative. > > > > No matter what the macro says, Rivendell always puts the switch into mute. > > > > Executing a *140 directly into the switcher via minicom doesn't do anything. > > > > So Rivendell is logging in to Linux as user "rd." I just added the user rd > > to the group dialout (which has access to the serial port). Now rd can run > > minicom and execute switches via commands punched into minicom (*11, *81, > > *62, etc). Rivendell macros fail though. > > > > I'm obviously missing something. > > > > In my mind, this should be really easy: > > > > 1. Install standard Rivendell per the instructions provided: > > http://static.paravelsystems.com/rivendell-install/rivendell-install-rhel7.html > > 2. Configure host, setup serial port, add matrix as Broadcast Tools 8x2. > > 3. Fire up RDLibrary, create a macro, ST 0 1 1! > > 4. Run macro, watch the switch assign input 1 to output 1. > > > > Sadly it doesn't work. The Macro puts the switcher into "mute" state. > > Minicom allows me to switch inputs just fine though and it's using the same > > configuration as Rivendell for the serial port. > > > > James > > > > > > - Original Message - > > From: "Rob Landry" <41001...@interpring.com> > > To: "James Greenlee" > > Cc: "Wayne Merricks" , "User discussion > > about the Rivendell Radio Automation System" > > > > Sent: Monday, March 6, 2017 3:42:46 PM > > Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. > > > > On Mon, 6 Mar 2017, James Greenlee wrote: > > > >> Using screen, and executing a ST macro from Rivendell, I see an output of > >> *140 and the switcher goes to mute. Executing a *140 in minicom does not > >> produce the same result. > > > > Does it produce the correct result, though? > > > >> It would appear then that the Rivendell "driver" > >> for the Broadcast Tools 8x2 speaks a slightly different language than > >> what my 8x2 actually understands. > > > > As far as I know, 8x2s have always understood the same language. > > > > Is Rivendell defining the serial port with different parameters than > > minicom? Is Rivendell running as a different user than minicom? If so, > > does that user have sufficient privileges to use the serial port? > > > >> In Wayne's documentation, you can execute commands to the serial port via > >> rmlsend with some shell scripts with screen commands. I'm sure I can make > >> that work, but is there a way to make a "driver" for Rivendell like the > >> existing Broadcast Tools 8x2 switcher one? > > > > UTSL ("Use the source, Luke"). > > > > Personally, I wouldn't bother, though; I'd have Rivendell run a > > constellation of shell commands containing whatever language you need to > > make the switcher work. > > > > > > Rob > >___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
If you get correct results in Minicom but not in Rivendell, the problem might be Rivendell-related. But if you never get correct results even in Minicom, then you've got a hardware problem (bad serial port? bad cable? incorrect pinout?) or a configuation problem. Rob -- Я там, где ребята толковые, Я там, где плакаты "Вперёд", Где песни рабочие новые Страна трудовая поёт. On Mon, 6 Mar 2017, James Greenlee wrote: As far as producing the "correct" result...That would be a negative. No matter what the macro says, Rivendell always puts the switch into mute. Executing a *140 directly into the switcher via minicom doesn't do anything. So Rivendell is logging in to Linux as user "rd." I just added the user rd to the group dialout (which has access to the serial port). Now rd can run minicom and execute switches via commands punched into minicom (*11, *81, *62, etc). Rivendell macros fail though. I'm obviously missing something. In my mind, this should be really easy: 1. Install standard Rivendell per the instructions provided: http://static.paravelsystems.com/rivendell-install/rivendell-install-rhel7.html 2. Configure host, setup serial port, add matrix as Broadcast Tools 8x2. 3. Fire up RDLibrary, create a macro, ST 0 1 1! 4. Run macro, watch the switch assign input 1 to output 1. Sadly it doesn't work. The Macro puts the switcher into "mute" state. Minicom allows me to switch inputs just fine though and it's using the same configuration as Rivendell for the serial port. James - Original Message - From: "Rob Landry" <41001...@interpring.com> To: "James Greenlee" Cc: "Wayne Merricks" , "User discussion about the Rivendell Radio Automation System" Sent: Monday, March 6, 2017 3:42:46 PM Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. On Mon, 6 Mar 2017, James Greenlee wrote: Using screen, and executing a ST macro from Rivendell, I see an output of *140 and the switcher goes to mute. Executing a *140 in minicom does not produce the same result. Does it produce the correct result, though? It would appear then that the Rivendell "driver" for the Broadcast Tools 8x2 speaks a slightly different language than what my 8x2 actually understands. As far as I know, 8x2s have always understood the same language. Is Rivendell defining the serial port with different parameters than minicom? Is Rivendell running as a different user than minicom? If so, does that user have sufficient privileges to use the serial port? In Wayne's documentation, you can execute commands to the serial port via rmlsend with some shell scripts with screen commands. I'm sure I can make that work, but is there a way to make a "driver" for Rivendell like the existing Broadcast Tools 8x2 switcher one? UTSL ("Use the source, Luke"). Personally, I wouldn't bother, though; I'd have Rivendell run a constellation of shell commands containing whatever language you need to make the switcher work. Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
On Tue, 7 Mar 2017 13:18:11 -0500 Sherrod Munday wrote: > (That being said, I have successfully used shell scripts in the past > to send commands directly to the serial port while minicom had it > open (this was useful to use a cron job to send a timestamp/keepalive > and telemetry command to a device while using minicom to log the > output), but I was not attempting to read data back out of the serial > port back to the CLI.) I'm fairly routinely ( lately ) reading the port while something else is writing to it. That's tough with something like minicom, but real easy with cat and echo. tail doesn't work directly, but you can do something like cat /dev/ttyS0 >> /tmp/temporary & tail -f /tmp/temporary OTOH, cat will continue showing the character stream until either you stop it, or something else actually closes the port. -- Cowboy http://cowboy.cwf1.com The trouble with heart disease is that the first symptom is often hard to deal with: death. -- Michael Phelps ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
On Mar 7, 2017, at 10:29, James Greenlee wrote: > This isn't a SS8.2, it's a straight 8x2 from 1995. According to the manual > provided by Broadcast Tools, the default speed is 2400 8n1 which works fine > with minicom. Unfortunately, Rivendell doesn't for some reason. > > The solution of making shell scripts is workable, but I think we're just > going to step up to a new switcher. Before going there, have you tried a null modem cable on the serial port of your Rivendell machine, connecting it up to another computer running at 2400 (8N1) to see what minicom vs. Rivendell produces? This is your best best to determine what's actually going on. If you get strange characters from RD when doing this, but minicom works fine, then you may have to delve down to hex mode in minicom (or another terminal emulations program) to see the actual codes that are sent and then try to figure out what protocol/settings are being used by RD -- or, just manually brute-force try the many different settings with minicom on the RD machine and see what they come out as on the far end of the null modem cable until you hit a match. My bet is that Rivendell isn't initializing the port correctly. BTW, you didn't mention the process you used to test minicom, but I'm hoping/guessing you stopped the RD daemons to run minicom on the same computer. If you didn't stop the daemons but were able to successfully open up the port with minicom, I'd really wonder what port RD is actually opening. Serial ports are generally only able to be controlled by one application at a time (the lock file that the first comm program creates usually tells subsequent programs to disallow accessing the same port). (That being said, I have successfully used shell scripts in the past to send commands directly to the serial port while minicom had it open (this was useful to use a cron job to send a timestamp/keepalive and telemetry command to a device while using minicom to log the output), but I was not attempting to read data back out of the serial port back to the CLI.) — Sherrod Munday ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
This isn't a SS8.2, it's a straight 8x2 from 1995. According to the manual provided by Broadcast Tools, the default speed is 2400 8n1 which works fine with minicom. Unfortunately, Rivendell doesn't for some reason. The solution of making shell scripts is workable, but I think we're just going to step up to a new switcher. James - Original Message - From: "Mike Price" To: "User discussion about the Rivendell Radio Automation System" Sent: Tuesday, March 7, 2017 10:13:34 AM Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. The default speed of the Broadcast Tools switcher is 9600 N81. Your original post indicates you had set up for 2400 baud. From the manual: The SS 8.2 may operate at baud rates from 2400 to 38400 baud. The unit is shipped set for 9600 baud, with 8 data bits, no parity and one stop bit. Cheers, Mike Price -Original Message- From: rivendell-dev-boun...@lists.rivendellaudio.org [mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of James Greenlee Sent: Monday, March 06, 2017 6:02 PM To: Rob Landry Cc: User discussion about the Rivendell Radio Automation System Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. As far as producing the "correct" result...That would be a negative. No matter what the macro says, Rivendell always puts the switch into mute. Executing a *140 directly into the switcher via minicom doesn't do anything. So Rivendell is logging in to Linux as user "rd." I just added the user rd to the group dialout (which has access to the serial port). Now rd can run minicom and execute switches via commands punched into minicom (*11, *81, *62, etc). Rivendell macros fail though. I'm obviously missing something. In my mind, this should be really easy: 1. Install standard Rivendell per the instructions provided: http://static.paravelsystems.com/rivendell-install/rivendell-install-rhel7.html 2. Configure host, setup serial port, add matrix as Broadcast Tools 8x2. 3. Fire up RDLibrary, create a macro, ST 0 1 1! 4. Run macro, watch the switch assign input 1 to output 1. Sadly it doesn't work. The Macro puts the switcher into "mute" state. Minicom allows me to switch inputs just fine though and it's using the same configuration as Rivendell for the serial port. James - Original Message - From: "Rob Landry" <41001...@interpring.com> To: "James Greenlee" Cc: "Wayne Merricks" , "User discussion about the Rivendell Radio Automation System" Sent: Monday, March 6, 2017 3:42:46 PM Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. On Mon, 6 Mar 2017, James Greenlee wrote: > Using screen, and executing a ST macro from Rivendell, I see an output of > *140 and the switcher goes to mute. Executing a *140 in minicom does not > produce the same result. Does it produce the correct result, though? > It would appear then that the Rivendell "driver" > for the Broadcast Tools 8x2 speaks a slightly different language than > what my 8x2 actually understands. As far as I know, 8x2s have always understood the same language. Is Rivendell defining the serial port with different parameters than minicom? Is Rivendell running as a different user than minicom? If so, does that user have sufficient privileges to use the serial port? > In Wayne's documentation, you can execute commands to the serial port via > rmlsend with some shell scripts with screen commands. I'm sure I can make > that work, but is there a way to make a "driver" for Rivendell like the > existing Broadcast Tools 8x2 switcher one? UTSL ("Use the source, Luke"). Personally, I wouldn't bother, though; I'd have Rivendell run a constellation of shell commands containing whatever language you need to make the switcher work. Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
The default speed of the Broadcast Tools switcher is 9600 N81. Your original post indicates you had set up for 2400 baud. From the manual: The SS 8.2 may operate at baud rates from 2400 to 38400 baud. The unit is shipped set for 9600 baud, with 8 data bits, no parity and one stop bit. Cheers, Mike Price -Original Message- From: rivendell-dev-boun...@lists.rivendellaudio.org [mailto:rivendell-dev-boun...@lists.rivendellaudio.org] On Behalf Of James Greenlee Sent: Monday, March 06, 2017 6:02 PM To: Rob Landry Cc: User discussion about the Rivendell Radio Automation System Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. As far as producing the "correct" result...That would be a negative. No matter what the macro says, Rivendell always puts the switch into mute. Executing a *140 directly into the switcher via minicom doesn't do anything. So Rivendell is logging in to Linux as user "rd." I just added the user rd to the group dialout (which has access to the serial port). Now rd can run minicom and execute switches via commands punched into minicom (*11, *81, *62, etc). Rivendell macros fail though. I'm obviously missing something. In my mind, this should be really easy: 1. Install standard Rivendell per the instructions provided: http://static.paravelsystems.com/rivendell-install/rivendell-install-rhel7.html 2. Configure host, setup serial port, add matrix as Broadcast Tools 8x2. 3. Fire up RDLibrary, create a macro, ST 0 1 1! 4. Run macro, watch the switch assign input 1 to output 1. Sadly it doesn't work. The Macro puts the switcher into "mute" state. Minicom allows me to switch inputs just fine though and it's using the same configuration as Rivendell for the serial port. James - Original Message - From: "Rob Landry" <41001...@interpring.com> To: "James Greenlee" Cc: "Wayne Merricks" , "User discussion about the Rivendell Radio Automation System" Sent: Monday, March 6, 2017 3:42:46 PM Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. On Mon, 6 Mar 2017, James Greenlee wrote: > Using screen, and executing a ST macro from Rivendell, I see an output of > *140 and the switcher goes to mute. Executing a *140 in minicom does not > produce the same result. Does it produce the correct result, though? > It would appear then that the Rivendell "driver" > for the Broadcast Tools 8x2 speaks a slightly different language than > what my 8x2 actually understands. As far as I know, 8x2s have always understood the same language. Is Rivendell defining the serial port with different parameters than minicom? Is Rivendell running as a different user than minicom? If so, does that user have sufficient privileges to use the serial port? > In Wayne's documentation, you can execute commands to the serial port via > rmlsend with some shell scripts with screen commands. I'm sure I can make > that work, but is there a way to make a "driver" for Rivendell like the > existing Broadcast Tools 8x2 switcher one? UTSL ("Use the source, Luke"). Personally, I wouldn't bother, though; I'd have Rivendell run a constellation of shell commands containing whatever language you need to make the switcher work. Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
As far as producing the "correct" result...That would be a negative. No matter what the macro says, Rivendell always puts the switch into mute. Executing a *140 directly into the switcher via minicom doesn't do anything. So Rivendell is logging in to Linux as user "rd." I just added the user rd to the group dialout (which has access to the serial port). Now rd can run minicom and execute switches via commands punched into minicom (*11, *81, *62, etc). Rivendell macros fail though. I'm obviously missing something. In my mind, this should be really easy: 1. Install standard Rivendell per the instructions provided: http://static.paravelsystems.com/rivendell-install/rivendell-install-rhel7.html 2. Configure host, setup serial port, add matrix as Broadcast Tools 8x2. 3. Fire up RDLibrary, create a macro, ST 0 1 1! 4. Run macro, watch the switch assign input 1 to output 1. Sadly it doesn't work. The Macro puts the switcher into "mute" state. Minicom allows me to switch inputs just fine though and it's using the same configuration as Rivendell for the serial port. James - Original Message - From: "Rob Landry" <41001...@interpring.com> To: "James Greenlee" Cc: "Wayne Merricks" , "User discussion about the Rivendell Radio Automation System" Sent: Monday, March 6, 2017 3:42:46 PM Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. On Mon, 6 Mar 2017, James Greenlee wrote: > Using screen, and executing a ST macro from Rivendell, I see an output of > *140 and the switcher goes to mute. Executing a *140 in minicom does not > produce the same result. Does it produce the correct result, though? > It would appear then that the Rivendell "driver" > for the Broadcast Tools 8x2 speaks a slightly different language than > what my 8x2 actually understands. As far as I know, 8x2s have always understood the same language. Is Rivendell defining the serial port with different parameters than minicom? Is Rivendell running as a different user than minicom? If so, does that user have sufficient privileges to use the serial port? > In Wayne's documentation, you can execute commands to the serial port via > rmlsend with some shell scripts with screen commands. I'm sure I can make > that work, but is there a way to make a "driver" for Rivendell like the > existing Broadcast Tools 8x2 switcher one? UTSL ("Use the source, Luke"). Personally, I wouldn't bother, though; I'd have Rivendell run a constellation of shell commands containing whatever language you need to make the switcher work. Rob ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
On Monday 06 March 2017 03:12:39 pm James Greenlee wrote: > I see an output of *140 and the switcher goes to mute. Executing a *140 in > minicom does not produce the same result. Suggests your serial port parameters are not set the same. E7 vs N8 for instance. -- Cowboy http://cowboy.cwf1.com "Avoid revolution or expect to get shot. Mother and I will grieve, but we will gladly buy a dinner for the National Guardsman who shot you." -- Dr. Paul Williamson, father of a student entering school in the fall after the Kent State shootings ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
On Mon, 6 Mar 2017, James Greenlee wrote: Using screen, and executing a ST macro from Rivendell, I see an output of *140 and the switcher goes to mute. Executing a *140 in minicom does not produce the same result. Does it produce the correct result, though? It would appear then that the Rivendell "driver" for the Broadcast Tools 8x2 speaks a slightly different language than what my 8x2 actually understands. As far as I know, 8x2s have always understood the same language. Is Rivendell defining the serial port with different parameters than minicom? Is Rivendell running as a different user than minicom? If so, does that user have sufficient privileges to use the serial port? In Wayne's documentation, you can execute commands to the serial port via rmlsend with some shell scripts with screen commands. I'm sure I can make that work, but is there a way to make a "driver" for Rivendell like the existing Broadcast Tools 8x2 switcher one? UTSL ("Use the source, Luke"). Personally, I wouldn't bother, though; I'd have Rivendell run a constellation of shell commands containing whatever language you need to make the switcher work. Rob___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
Okay... According to the Broadcast Tools manual, I'm supposed to be able to pull up a menu via the 232 port but I can't seem to do that. I can however switch inputs with minicom (*11 = input 1 to output 1). Using screen, and executing a ST macro from Rivendell, I see an output of *140 and the switcher goes to mute. Executing a *140 in minicom does not produce the same result. It would appear then that the Rivendell "driver" for the Broadcast Tools 8x2 speaks a slightly different language than what my 8x2 actually understands. In Wayne's documentation, you can execute commands to the serial port via rmlsend with some shell scripts with screen commands. I'm sure I can make that work, but is there a way to make a "driver" for Rivendell like the existing Broadcast Tools 8x2 switcher one? Thanks! - Original Message - From: "Wayne Merricks" To: "James Greenlee" Sent: Monday, March 6, 2017 4:39:19 AM Subject: Re: [RDD] Rivendell and Broadcast Tools switcher. I wrote this a few years ago for a broadcast tools 8.2 plus switcher. It goes through the Riv way, as well as using minicom and screen with sample scripts to use it directly with just a Riv RN macro. http://rivendell.tryphon.org/wiki/Switchers Hopefully should help you figure out what is going on. Regards, Wayne On 6 Mar 2017 01:27, "James Greenlee" < ja...@madsonics.com > wrote: I've recently loaded Rivendell 2.15.2 on CentOS 7 and am trying to configure an older Broadcast Tools 8x2 switcher. The COM port on the system is configured as ttyS2, Rivendell host serial port is configured as /dev/ttyS2, I'm using the Broadcast Tools 8x2 selection under "Switchers/GPIO" and everything is configured as follows: "GENERAL NOTES: Control is done by means of an RS-232C connection to a four pin RJ11 modular jack on the back of the unit (an adapter to a standard DB9 connector is supplied by Broadcast Tools with the unit). Serial port parameters should be set to 2400 baud rate, no parity, 8 data bits, 1 stop bit, CR/LF termination. The 8x2 should be configured to use 'Mix' mode. This can be done by holding down the F1 button on the switcher while powering up. Operation in 'multidrop' mode is not supported. " Which I got that information from here: http://rivendell.tryphon.org/wiki/SWITCHERS.txt_-_Switcher_Application_Notes_for_Rivendell#BROADCAST_TOOLS_8x2 The Broadcast Tools is configured as switcher matrix 1 (local sound card is matrix 0), on serial port 0, and Rivendell knows that it's serial port 0 is /dev/ttyS2. When I create a macro that performs "ST 1 1 1!" and run it, the Broadcast Tools goes to mute. Really...Any ST command ends up in mute. Other RML commands (SR SA) do nothing. Any thoughts? Rivendell is definitely sending something to the switcher because it does mute every time I run a macro. My guess is it has older firmware with a different command set than Rivendell is sending. Thanks, James ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] Rivendell and Broadcast Tools switcher.
You might need to use the terminal and send commands to the BT outside of Rivendell to see what it is doing in reaction to manufacturers documented commands. That way you can assure that the switcher is working properly. Had a BT relay box that came half DOA and that is how we determined the source of the problems. Sent from my iPhone > On Mar 5, 2017, at 8:27 PM, James Greenlee wrote: > > I've recently loaded Rivendell 2.15.2 on CentOS 7 and am trying to configure > an older Broadcast Tools 8x2 switcher. > > The COM port on the system is configured as ttyS2, Rivendell host serial port > is configured as /dev/ttyS2, I'm using the Broadcast Tools 8x2 selection > under "Switchers/GPIO" and everything is configured as follows: > > "GENERAL NOTES: Control is done by means of an RS-232C connection to a four > pin RJ11 modular jack on the back of the unit (an adapter to a standard DB9 > connector is supplied by Broadcast Tools with the unit). Serial port > parameters should be set to 2400 baud rate, no parity, 8 data bits, 1 stop > bit, CR/LF termination. > > The 8x2 should be configured to use 'Mix' mode. This can be done by holding > down the F1 button on the switcher while powering up. > Operation in 'multidrop' mode is not supported. " > > > Which I got that information from here: > http://rivendell.tryphon.org/wiki/SWITCHERS.txt_-_Switcher_Application_Notes_for_Rivendell#BROADCAST_TOOLS_8x2 > > > The Broadcast Tools is configured as switcher matrix 1 (local sound card is > matrix 0), on serial port 0, and Rivendell knows that it's serial port 0 is > /dev/ttyS2. When I create a macro that performs "ST 1 1 1!" and run it, the > Broadcast Tools goes to mute. Really...Any ST command ends up in mute. > Other RML commands (SR SA) do nothing. > > Any thoughts? Rivendell is definitely sending something to the switcher > because it does mute every time I run a macro. My guess is it has older > firmware with a different command set than Rivendell is sending. > > Thanks, > > James > ___ > Rivendell-dev mailing list > Rivendell-dev@lists.rivendellaudio.org > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev