Production Switchers

I built a panel in DashBoard to control my Vision 4 with RossTalk.

I was able to get the Fade to Black command to work but the recall Custom Control doesn't seem to do anything.

I used the CC [Bcc] so to recall bank 1 cc 1 I entered 101.

Any ideas?

I ran into this exact problem and got the following answer: "There is a bug in the Vision release of RossTalk where the 1st custom of a bank does not work. Will be fixed with v16.1g due for release in late August."

I was successfully able to make any other custom control work. I've not yet had time to upgrade to 16.1g or beyond. I also couldn't make the XPT command work and was told that it was an error corrected in version 16.1f

Hope this helps.

Philip

#Vision

thanks Philip,

I'm running v16.1g.

I didn't try another CC past #1. I'll try some higher numbers and see.

#Vision

Hi Guys,

So 16.1i which will be out in about a week will have the fix for the CC bug. Yes it is just the first one of each bank.

The XPT command was fixed in g. So if you wait for i you will get both of these resolved.

Les

#Vision

Paul/Les how exactly did you get dashboard panel button configured to work with even FTB?

Trying to set up a similar scenario to fire off CC from a networked PC on the same network as the frame.

Ross Vision 1 is using v.16.1d, and Dashboard 6.2 beta

Com Port is set to: RTalk-IN, Network TCP, IP address, Port 7788 on the Vision 1.

On Dashboard our frame is not detected automatically or manually added or visible in the basic tree, but each panel button we created is configured to use Rosstalk using the frame IP address.

Am I missing something? Any help would be greatly appreciated.

Tim

#Vision

The RossTalk port is on the panel not the frame.

So make sure you are using the panel IP address and not the frame.

You are correct that it will not be in the tree as RossTalk Devices are not displayed in the SLP auto detect.

Les

#Vision

Tim,

Other than what is described in the thread I think I had to enable RossTalk as an external device on my switcher.

Paul

#Vision

Our dashboard panel buttons are now directed in the Rosstalk editor to the Panel IP, but we still have no functionality with the Vision 1

Our communications on the vision are set as following:

Type/Port=Rosstalk device

Device=Rtalk-IN

Com Type= Network TCP

Com settings= CLIENT - remote IP of dashboard PC - (remote port) 7788

Local IP address = 0.0.0.0 Local Port 0

To be noted,

We can ping the panel from the Dashboard PC, and also

we currently are controlling Xpression from the Vision using Rtalk-XPN on port 7788

#Vision

Hi Timothy,

In Vision.

Try setting the Com settings to : 'Server' with no IP addresses, (0's)

The port should be set to 7788 as you have it.

This will have Vision listen on port 7788 for incoming RossTalk messages, which is what you want if you are using DashBoard to send messages to Vision.

There is no need to configure the DashBoard PC IP address anywhere on the switcher since you are not sending messages to DashBoard.

Let us know how that worked for you.

Thanks!

Troy.

#Vision

Thanks Troy, that's the setting we needed, our dashboard buttons are working!

And thanks, Les and Paul for the quick responses!

#Vision