Production Switchers

Hi all,

Newbie here, but been cutting on Ross switchers for a while.

I am working on a particularly large sporting event in Melbourne, Australia at the moment (you can probably guess which one), and am driving an Ultra 60 for my stadium screens. I was messing around looking at spitting out some tally data over the network so I could connect it in with Companion and eventually some wireless tally lights I have just received.

However when I go to add a TSL UMD device, the entire switcher locks up, crashes, and then reboots 5-10 seconds after I select TSL 3.1 in the protocol type. TSL 5 doesn't cause the issue, but is currently not compatible with the companion module I am hoping to use to interpret the data.

I'm driving all this from a touch drive up in a control booth with the switcher frame located in the bowls of the stadium somewhere I'm not sure.

Wondering if anybody has any advice on what might be happening here? It's by no means a critical problem, just a nice to have thing, but thought I would mention that I'm having it to get other people's input.

Thanks

Running SW version: 9.1.1.13797

Hi Kenton,

Sorry for the delay.  New posts have been going into moderation since we had an issue previously with some spam bots.

TSLv3.1 is not supported at all in the Ultra 60 as it only has 127 label addresses.  We will need to look into why it is visible in the UI as that is probably why the issues.  It is setting something that should not be possible to select.

Ultra 60 v9.1.3 is the current release I would suggest when you have time to also upgrade to that.

Hi all,

Newbie here, but been cutting on Ross switchers for a while.

I am working on a particularly large sporting event in Melbourne, Australia at the moment (you can probably guess which one), and am driving an Ultra 60 for my stadium screens. I was messing around looking at spitting out some tally data over the network so I could connect it in with Companion and eventually some wireless tally lights I have just received.

However when I go to add a TSL UMD device, the entire switcher locks up, crashes, and then reboots 5-10 seconds after I select TSL 3.1 in the protocol type. TSL 5 doesn't cause the issue, but is currently not compatible with the companion module I am hoping to use to interpret the data.

I'm driving all this from a touch drive up in a control booth with the switcher frame located in the bowls of the stadium somewhere I'm not sure.

Wondering if anybody has any advice on what might be happening here? It's by no means a critical problem, just a nice to have thing, but thought I would mention that I'm having it to get other people's input.

Thanks

Running SW version: 9.1.1.13797

Hey there Les,

Ahhh okay well that makes sense then. Thanks for that, good to know it was a simple known thing.

Yeah maybe future firmware should not have the option to select the old protocol on the Ultras then.

Cheers

KR

Hi Kenton,

Sorry for the delay.  New posts have been going into moderation since we had an issue previously with some spam bots.

TSLv3.1 is not supported at all in the Ultra 60 as it only has 127 label addresses.  We will need to look into why it is visible in the UI as that is probably why the issues.  It is setting something that should not be possible to select.

Ultra 60 v9.1.3 is the current release I would suggest when you have time to also upgrade to that.

Hi all,

Newbie here, but been cutting on Ross switchers for a while.

I am working on a particularly large sporting event in Melbourne, Australia at the moment (you can probably guess which one), and am driving an Ultra 60 for my stadium screens. I was messing around looking at spitting out some tally data over the network so I could connect it in with Companion and eventually some wireless tally lights I have just received.

However when I go to add a TSL UMD device, the entire switcher locks up, crashes, and then reboots 5-10 seconds after I select TSL 3.1 in the protocol type. TSL 5 doesn't cause the issue, but is currently not compatible with the companion module I am hoping to use to interpret the data.

I'm driving all this from a touch drive up in a control booth with the switcher frame located in the bowls of the stadium somewhere I'm not sure.

Wondering if anybody has any advice on what might be happening here? It's by no means a critical problem, just a nice to have thing, but thought I would mention that I'm having it to get other people's input.

Thanks

Running SW version: 9.1.1.13797