Leapfrog 48 remote GO

[TimC]

I would like to be able to remotely send a GO cue to the board. Don’t have the SMPTE/MIDI/CAN/REMOTES UPGRADE KIT and doubt I will ever find one. Now the ZerOS Monitor obviously can do this but it suggests to me that it might be possible to send a message from my pc via Ethernet, any ideas?

I use Show Cue System for sound including sending control messages to my sound desk.

[TimC]

I should add that I have read this

https://zero88.com/manuals/zeros/setup/triggers/midi-notes

but this would only work if I had the upgrade card

[Edward Z88]

Hi @TimC

1 hour ago, TimC said:

I would like to be able to remotely send a GO cue to the board. Don’t have the SMPTE/MIDI/CAN/REMOTES UPGRADE KIT and doubt I will ever find one. Now the ZerOS Monitor obviously can do this but it suggests to me that it might be possible to send a message from my pc via Ethernet, any ideas?

I use Show Cue System for sound including sending control messages to my sound desk.

There are currently two methods of triggering cues over the network: ZerOS Remote Apps, and Vision.Net commands.

Vision.Net is an architectural lighting control protocol, based on simple UDP broadcast commands. I don't believe SCS has the ability to send native Vision.Net commands. However, it may allow you to send raw UDP messages. This is something you'd need to investigate. If it does, please send us an email to support@zero88.com, and I can provide more information on how you could write your own Vision.Net commands. These commands could then be fired from an SCS cue, and received by your console.

If you have any questions, please let us know.

Edward

[TimC]

I believe using UDP is possible having read the following post which was to do with sending control messages to Qlab

SCS must be configured as follows:

Editor / Production Properties / Devices / Control Send
Remote Device: Any Device or Product
Network Protocol: UDP
Network Role: SCS is a Network Client
IP Address or Server Name: (IP address of the MAC) or in our case the Leapfrog board
Port No.: 53535 (QLAB is basically configured to receive OSC messages on this Port) don’t know what Leapfrog will require
_________________________________________

SCS 'Control Send' Structure:

In EDITOR / Cue / Add 'Control Send' Cue

Create a 'Control Send' Cue

Control Send Device: udp
Entry Mode: ASCII
Network Message: 

[Edward Z88]

Hi @TimC

I have replied to your email.

Edward

[TimC]

I have managed to achieve sending Strand Vision.Net messages from SCS to ZerOS. In my case to a LeapFrog 48 lighting board.
There is a little bit of easy setting up to do in ZerOS (Setup / Triggers)
The tricky part was formulating the HEX message (Thanks to Edward in support), once I had achieved that putting it into SCS was straightforward
SCS must be configured as follows:

Editor / Production Properties / Devices / Control Send
Remote Device: Any Device or Product
Network Protocol: UDP
Network Role: SCS is a Network Client
IP Address or Server Name: needs to be a broadcast address 192.168.1.255
Port No.: 2741

SCS 'Control Send' Structure:

In EDITOR / Cue / Add 'Control Send' Cue

Create a 'Control Send' Cue

Control Send Device: as named in Devices
Entry Mode: HEX
Network Message:
8C 01 A8 C0 01 00 00 00 01 00 00 00 00 84 09 01 5f 00 02 05 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

8C 01 A8 C0 is the IP Address of the sending PC in this example 192.168.1.140 but in reverse order 140.1.168.192
02 05 The message is set for ‘Room’ 2 ‘Preset’ 5 which will fire macro 5
My Macro 5 is a recording of pressing the ‘Go’ buttton

In addition to Macros it is possible to map Vision.Net rooms to things like Playback faders and Cues (via playback buttons)

[TimC]

Just an update to my previous post

The IP address the message is being sent to

In a typical Vision.Net system, Vision.Net commands trigger multiple different devices on the network simultaneously. It is therefore best practice to send UDP broadcast messages, that all “receivers” on the network can listen to.

Using unicast is fine where there is just the one Lighting Board, as you only have a single Vision.Net “receiver”.

So I prefer to specify the actual address of my LeapFrog so that the message is notpicked up by any other device on the network.

With regard to the IP Address of the sending PC ZerOS dosent actually use this so it can be any value at all eg 02 02 02 02

Finally you dont need quite as many trailing Nulls you can reduce that to 24 Nulls