Visual Productions TIMECORE User Manual [EN]

TIMECORE

MANUAL

© VISUAL PRODUCTIONS BV WWW.VISUALPRODUCTIONS.NL

Revision History

Revision Date Author(s) Description

1 10.05.2016 ME Initial version.

2 10.11.2017 ME Added: RTP-MIDI, Rackmount ac-

cessory, MSC API & password protec­tion feature. Replaced VisualTouch
info by Kiosc.

3 07.06.2018 ME Updated vManager chapter to reflect

app-store distribution. Moved major­ity of Kiosc information to a dedicated
Kiosc manual. Added discussion on
password and share analytics.

2

Contents

1 Introduction 6

2 Protocols 9

3 Setting up 12

4 Network 14

5 Show Control 18

6 Monitors 23

7 Settings 25

8 RTP-MIDI 32

9 vManager 38

10 Kiosc 42

Appendices 43

A Templates 44

B Trigger Types 45

C Task Types 52

D API 60

3

c

2018 Visual Productions BV. All rights reserved.

No parts of this work may be reproduced in any form or by any means - graphic,
electronic, or mechanical, including photocopying, recording, taping, or infor­mation storage and retrieval systems - without the written permission of the
publisher.

While every precaution has been taken in the preparation of this document,
the publisher and the author assume no responsibility for errors or omissions,
or for damages resulting from the use of information contained in this docu­ment or from the use of programs and source code that may accompany it. In
no event shall the publisher and the author be liable for any loss of profit or
any other commercial damage caused or alleged to have been caused directly or
indirectly by this document.

Due to the dynamic nature of product design, the information contained in
this document is subject to change without notice. Revisions of this informa­tion or new editions may be issued to incorporate such changes.

Products that are referred to in this document may be either trademarks and/or
registered trademarks of the respective owners. The publisher and the author
make no claim to these trademarks.

4

Declaration of Conformity

We, manufacturer Visual Productions BV, herby declare under sole responsibility,
that the following device:

TimeCore

Conforms to the following EC Directives, including all amendments:
EMC Directive 2004/108/EG

And the following harmonized standards have been applied:
NEN-EN-IEC 61000-6-1:2007
NEN-EN-IEC 61000-6-3:2007

Full name and identication of the person responsible for product quality and
accordance with standards on behalf of the manufacturer

Date: Place:
May 8th, 2017 Haarlem, The Netherlands

ing. Maarten Engels
Managing Director
Visual Productions BV

VISUAL PRODUCTIONS BV

IZAAK ENSCHEDEWEG 38A

NL-2031CR HAARLEM

THE NETHERLANDS

TEL [phone]

WWW.VISUALPRODUCTIONS.NL

[e-mail]

ABN-AMRO BANK 53.22.22.261

BIC ABNANL2A

IBAN NL18ABNA0532222261

VAT NL851328477B01

COC 54497795

Chapter 1

Introduction

The TimeCore is a solid-state device for handling timecode. It is intended to
be used for entertainment shows at events, concerts, festivals and in themed
environments. The TimeCore will help in keeping the various show elements
like sound, lighting, video, laser and special FX synchronised.

Figure 1.1: TimeCore

The TimeCore can generate timecode, it can convert it between different
protocols and it can display any received timecode on its display. The unit
features inbuilt web-server; this web-interface allows the user to configure the
unit. The web-interface also enables other non-timecode protocols like UDP,
OSC and sACN to be linked to certain timecode events. The TimeCore can be
the bridge between timecode and other non-timecode show equipment such as
video players, relays and dimmers. The TimeCore features a rich suite of pro­tocols that include the two most popular timecodes in show business SMPTE
and MTC. Furthermore, it has Art-Net timecode implemented, which has the
advantage of being network-based.

This document discusses setting up the device and programming its internal
software functions. At the time of writing this manual the TimeCore’s firmware

6

was at version 1.07.

1.1 Features

The feature set of the TimeCore includes:

• Ethernet port

• Programming via web-interface

• SMPTE

• MTC

• MIDI, MSC, MMC

• RTP-MIDI

• OSC, UDP, TCP

• Art-Net (data & timecode)

• sACN

• Large 7-segment LED display

• 2x user-definable push-button

• 9-24V DC 500mA (PSU included)

• Power over Ethernet (class I)

• Desktop or DIN Rail mounted (optional adapter)

• Operating temperature -20C to +50C (-4F to 122F)

• Compliance EN55103-1 EN55103-2

• Bundled with vManager and Kiosc software

1.2 What’s in the box?

The TimeCore packaging contains the following items (see figure 1.2):

• TimeCore

• Power supply (inc. international plug set)

• Network cable

• Info card

7

Figure 1.2: TimeCore box contents

1.3 Saving data to memory

This manual will describe how to configure the TimeCore and actions, tasks,
etc. The unit’s web-interface is used for editing these kinds of elements. When
changes are made, these changes are directly stored in the RAM memory of
the TimeCore and the programming will directly influence the behaviour of the
unit. RAM memory is, however, volatile and its content will be lost through a
power cycle. For this reason the TimeCore will copy any changes in the RAM
memory to its onboard flash memory. Flash memory retains its data even when
not powered. The TimeCore will load all its data back from the flash memory
upon startup.

This memory copy process is conducted automatically by the TimeCore and
should not be of any concern of the user. One point of consideration is, how­ever, that after making a change the unit should be given time to perform the
copy to flash. As a rule of thumb, do not disconnect the power from the device
within 30 seconds from making a programming change.

1.4 Further Help

If, after reading this manual, you have further questions then please consult
the online forum at http://forum.visualproductions.nl for more technical
support.

8

Chapter 2

Protocols

The TimeCore is fitted with several communication ports and supports various
protocols. This chapter describes these protocols and to which extent they are
implemented in the TimeCore

2.1 SMPTE

SMPTE is timecode signal which can be used to synchronise audio, video, light­ing and other show equipment. The TimeCore supports receiving SMPTE that
is transferred as an audio signal, also know as LTC timecode.
The TimeCore can send and receive SMPTE.

2.2 MIDI

The MIDI protocol is intended for inter-connecting musical devices such as syn­thesisers and sequencers. Furthermore, this protocol is also very suitable to
send triggers from one device to another and is often used to synchronise audio,
video and lighting equipment. There is also a large collection of MIDI con­trol surfaces available; user-interface consoles with knobs, (motorised-)faders,
rotary-encoders, etc.

The TimeCore is fitted with a MIDI input and MIDI output port. It supports
receiving and sending MIDI messages like NoteOn, NoteOff, ControlChange and
ProgramChange.

2.2.1 MTC

MIDI Timecode (MTC) is the timecode signal which is embedded into MIDI.
The TimeCore supports receiving and transmitting MTC. It is not recommended
to combine the use of MTC with ordinary MIDI as MTC consumes the band­width of the MIDI connection.

2.2.2 MMC

MIDI Machine Control (MMC) is part of the MIDI protocol. It defines special
messages for controlling audio equipment such as multi-track recorders. The

9

TimeCore supports the sending of MMC commands; please refer to page 55.

2.2.3 MSC

MIDI Show Control (MSC) is an extension of the MIDI protocol. It comprises
of commands for synchronising show equipment like lighting, video and audio
devices. The TimeCore supports receiving MSC commands. This support is
hard coded and does not require any Show Control programming. Please refer
to appendix ??.

2.3 RTP-MIDI

RTP-MIDI is an Ethernet-based protocol for transferring MIDI messages. It
is part of the RTP (Real-time Protocol) protocol suite. RTP-MIDI is natively
supported by the macOS and iOS operating systems. Through installing a
driver, it is also supported on Windows.

Once the RTP-MIDI connection is established between the TimeCore and
the computer, then software running on the computer will see the TimeCore s
MIDI ports as if it was a USB connection MIDI interface.

2.4 Art-Net

The Art-Net protocol primarily transfers DMX-512 data over Ethernet. The
high bandwidth of an Ethernet connection allows Art-Net to transfer up to 256
universes.

The data sent out for Art-Net does put a certain load on the network, there­fore it is recommended to disable Art-Net when not in use.

Additional to transmitting DMX-512 data, Art-Net can also be used for
transferring timecode information for equipment synchronisation.

The TimeCore supports sending and receiving of Art-Net timecode as well
as one universe of Art-Net data.

2.5 sACN

The streaming Architecture of Control Networks (sACN) protocol uses a method
of transporting DMX-512 information over TCP/IP networks. The protocol is
specified in the ANSI E1.31-2009 standard.

The sACN protocol supports multi-cast in order to take efficient use of the
network’s bandwidth.

The TimeCore supports sending and receiving of one sACN universe.

2.6 TCP

The Transmission Control Protocol (TCP) is a core protocol of the Internet
Protocol Suite. It is used for its reliable, ordered and error checked delivery
of a stream of bytes between applications and hosts over IP networks. It is
considered ’reliable’ because the protocol itself checks to see if everything that

10

was transmitted was delivered at the receiving end. TCP allows for the retrans­mission of lost packets, thereby making sure that all data transmitted is received.

The TimeCore supports reception of TCP message.

2.7 UDP

User Datagram Protocol (UDP) is a simple protocol for sending messages across
the network. It is supported by various media devices like video projectors and
Show Controllers. It does not incorporate error checking, therefor it is faster
than TCP but less reliable.

There are two ways how to have the TimeCore respond to incoming UDP
messages. The API (see page 61) makes typical TimeCore functions available
through UDP. Furthermore, custom messages can be programmed in the Show
Control page (see page 18). This is also the place where to program outgoing
UDP messages.

2.8 OSC

Open Sound Control (OSC) is a protocol for communicating between software
and various multi-media type devices. OSC uses the network to send and receive
messages, it can contain MIDI and custom information.

There are apps available for creating custom-made user interfaces on iOS
(iPod, iPhone, iPad) and Android. These tools allow to program fool-proof
user-interfaces for controlling the device. E.g. Kiosc from Visual Productions.

There are two ways how to have the TimeCore respond to incoming OSC
messages. Firstly, the API (see page 60) makes typical TimeCore functions
available through OSC. Secondly, custom messages can be programmed in the
Show Control page (see page 18).

2.9 DHCP

The Dynamic Host Configuration Protocol (DHCP) is a standardised network
protocol used on Internet Protocol (IP) networks for dynamically distributing
network configuration parameters, such as IP addresses.

The TimeCore is a DHCP client.

11

Chapter 3

Setting up

This chapter discusses how to set up the TimeCore.

3.1 Mounting

The device can be placed desktop or it can be DIN Rail mounted. The device
is prepared for DIN Rail mounting by using the ’DIN rail holder TSH 35’ from
Bopla (Product no. 22035000).

Figure 3.1: Bopla DIN rail adapter

This adapter is - amongst others - available from:

• Farnell / Newark (order code 4189991)

• Conrad (order code 539775 - 89)

• Distrelec (order code 300060)

3.2 Rackmount

There is an adapter available for mounting the TimeCore into a 19” rack . The
rackmount adapter is 1 HE and is sold separately. It fits two units, however, it
is supplied with one position closed by a blind panel, see figure 3.2.

12

Figure 3.2: Rackmount adapter

3.3 Kensington Lock

The device can be secured by using a Kensington style laptop lock.

Figure 3.3: Kensington lock

3.4 Power

The TimeCore requires a DC power supply between Volt with a minimum of
500mA. The 2,1 mm DC connector is center-positive. The TimeCore is also
Power-over-Ethernet (PoE) enabled. It requires PoE Class I.

Figure 3.4: DC polarity

13

Chapter 4

Network

The TimeCore is a network capable device. A network connection between
between a computer and the unit is required to configure and program the
TimeCore, however, once the device is programmed then it is not necessary
anymore for the TimeCore to be connected to an Ethernet network.

There are multiple arrangements possible for connecting the computer and the
TimeCore. They can be connected peer-to-peer, via a network switch or via
Wi-Fi. Figure 4.1 illustrates these different arrangements.

Figure 4.1: Network arrangements

The Ethernet port on the TimeCore is auto-sensing; it does not matter whether
a cross or straight network-cable is being used.

14

4.1 IP Address

The TimeCore supports both static IP addresses and automatic IP addresses.
By default, the TimeCore is set DHCP in which it will be automatically as­signed an IP address by the DHCP server in the network. The ’DHCP server’
is typically part of the router’s functionality.

Static IP addresses are useful when there is no DHCP server in the network, for
instance when there is a direct peer-to-peer connection between a TimeCore and
a computer. It is also useful in permanent installations where the IP address
of the TimeCore is known by other equipment and therefor should not change.
When using DHCP there is always the risk of automatically being given a new
IP address in the event that the DHCP server is replaced. When using static IP
addresses make sure that all equipment on the network have unique IP addresses.

The TimeCore’s LED helps to determine which kind of IP address is set. The
LED will indicate red when using DHCP and it will indicate white in the case
of a static IP address.

There are three ways to change the IP address setting of the TimeCore.

Figure 4.2: Reset button

• vManager can be used to detect a TimeCore on the network. Once
found, the vManager software (figure chapter 9) allows for changing the
IP address, subnet mask and DHCP settings.

• If the IP address is already known then browsing to this address using the
computer’s browser will show the TimeCore’s web-interface. The Set­tings page on this web-interface enables changing the IP address, subnet
mask and DHCP settings.

• By briefly pressing the reset button on the device it toggles between
static and automatic IP addresses. By pressing and holding the reset
button (see figure 4.2) on the device for 3 seconds, it will reconfigure the
unit to the factory default IP address and subnet mask. No other settings
will be changed. The default IP address is 192.168.1.10 with the subnet
mask set to 255.255.255.0.

15

4.2 Web-interface

The TimeCore features an inbuilt web-server. This web-interface can be ac­cessed via a standard browser. It is recommended to use any of the following
browsers:

• Microsoft Edge

• Google Chrome (v59 or higher)

• Apple Safari (v10 or higher)

• Mozzila Firefox (v54 or higher)

The web-interface enables you to configure and program the TimeCore.
When browsing to the unit the home page (figure 4.3) will appear first. The
home page is read-only; it provides information but does not allow for changing
any setting. The other pages present many settings that can be edited. These
pages will be discussed in the subsequent chapters.

Figure 4.3: Home page

4.2.1 Uptime

This field indicates how long the unit has been alive since its last reboot.

16

4.2.2 Last Server Poll

Indicates the last time the time & date was fetched from a NTP time server.

4.2.3 Master IP

When the unit is not in Stand Alone mode, then this field displays the IP
number of system that is mastering the TimeCore. Refer to chapter ?? for
more information on operating modes.

4.3 Access via Internet

The TimeCore can be accessed through the Internet. There are two ways to
achieve this: Port Forwarding and VPN.

• Port Forwarding Is relatively easy to setup in the router. Each router
is different so it is advised to consult the router’s documentation (some­times it is revered to as NAT or Port-Redirecting). Please note that port
forwarding is not secure, since anybody could access the TimeCore this
way.

• Accessing via a Virtual Private Network (VPN) tunnel requires more
setup efforts, also the router needs to support the VPN feature. Once set
up, this is a very secure way to communicate with the TimeCore. A VPN
is a network technology that creates a secure network connection over a
public network such as the Internet or a private network owned by a service
provider. Large corporations, educational institutions, and government
agencies use VPN technology to enable remote users to securely connect
to a private network. For further information about VPN please refer to
http://whatismyipaddress.com/vpn.

17

Chapter 5

Show Control

The TimeCore can interact with the outside world; it can receive messages and
values through various protocols and it can send out many protocols. It is pos­sible to automate the TimeCore by having it respond automatically to incoming
signals. An example of this would be to start the time-code clock upon receiv­ing a specific UDP network message. The Show Control page (See figure 5.1)
enables this kind of programming to be made.

Figure 5.1: Show Control page

The Show Control page presents a system of ’actions’. A signal that the
TimeCore needs to respond to or perhaps convert into some other signal, needs
to be expressed in an actions. Converting timecode protocols is the exception;
this can be done in the Settings page (see page 28).Before programming actions
please consider the Show Control structure in figure 5.2.

18

Figure 5.2: Show Control structure

The TimeCore is capable of listening to various protocols. These available
protocols are listed in Sources, however, the TimeCore can only actively listen
to 8 protocols at once. The active protocols are listed in ’Action Lists’. Each
action list can contain actions. Within a protocol/source each individual sig­nal requires its own action. For example, when listening to channel 1 and 2 on
the incoming DMX, the DMX action list needs two actions; one for each channel.

Inside the action we define the trigger and tasks. The trigger specifies for which
signal to filter. In the above DMX example the trigger would be set to ’channel
1’ and ’channel 2’ respectively. The tasks determine what the TimeCore will do
when this action is triggered. Several tasks can be placed in the action. There
are tasks available for a wide range of TimeCore features and external protocols.
Task types are detailed in Appendix C on page 52.

Please consult the API appendix on page 60 before implementing incoming
OSC or UDP messages; the API already exposes typical functionality through
OSC and UDP and therefor it might not be necessary to implement custom
messages.

5.1 Sources and Action Lists

The Sources listing presents all protocols that the TimeCore is capable of re­ceiving. It also includes internal features that can create events that can be used
for triggering actions, such as the power-up event. These sources are available,
however, they will only be actively listened to once moved to the action-list table.

19

Buttons One of the two front side buttons is pushed

MIDI MIDI messages

RTP-MIDI RTP-MIDI network messages

UDP UDP network messages

TCP TCP network messages

OSC OSC network message

Art-Net Art-Net DMX data

sACN sACN DMX data

Timecode Timecode signal, specify the incoming timecode protocol on

the Settings page.

Kiosc Triggers from Kiosc. For each Action various controls can

be chosen such as buttons and sliders, colour picker etc. The
order of the actions will control the arrangement in Kiosc.

Randomiser The randomiser can generate a random number

System Events such as ’Power on’

Variable The Variable source works in combination with the variable

task (For more information about the Variable task please
refer to Task Types). The Variable task will set a value of
which an enabled action-list type with Variable as Source
will use as a trigger. The TimeCore will not keep the values
of the 8 variables between power-cycles.

Timer

User List 1-4 These action-lists will never trigger an event, however, they

Action-lists can be temporarily suspended by disabling their checkbox in the
Show Control page. There is also a task available to automate changing the
state of this checkbox.

There are 4 internal timers in the TimeCore. An event will
be raised when a timer expires. Timers are set and
activated by the Timer tasks.

are useful for advanced programming.

5.2 Actions

Actions are executed when a certain signal is received. This signal is defined by
the trigger. A trigger is always relative to the action-list the action belongs to.
For example, when the trigger-type is set to ’Channel’ then it refers to a single
DMX channel if the action is placed inside a ’DMX Input’ list and it means a
single Art-Net channel if the action resides in an Art-Net action-list.

A trigger is determined by the trigger-type, trigger-value and trigger-flank
fields. Although these fields are not applicable for all action-lists and are therefor
sometimes omitted in the web GUI. The trigger-type field specifies what kind
of signal the action will be triggered by. For example, when making an action

20

in the Button list there is the choice between ’Short press’ and ’Long press’
trigger-types. The trigger-value specifies the actual signal value. In the Button
example the trigger-value denotes which button.

In some action-lists actions do also need to specify the trigger-flank. The
flank further specifies the value that the signal should have before triggering
the action. For example, when an action is triggered from a Kiosc list and it
is linked to a button in the Kiosc software, the flank will determine whether to
trigger only when the button goes down or only when it goes up. Appendix B
provides an overview of the available trigger-types.

An action-list can have up to 48 actions, system-wide there is a maximum
of 64 actions.

5.3 Tasks

Tasks are added to an action in order to specify what to do when it gets executed.
Up to 8 tasks can be included in an action, system-wide there is a maximum
of 128 tasks. The tasks are executed in the order of the list. There is a wide
selection of tasks available to choose from, they include altering any of the
internal software features like time-code clock and the LED display, also sending
out messages through any of the supported protocols.

The tasks are organised in categories. Once a task is chosen from these
categories each task allows for further choice between several Features and
Functions. Tasks contain up to two parameters that might be required for
its execution.

A task can be tested by selecting it and pressing the ’execute’ button in
the action-edit dialog. The complete action can also be tested; go to the Show
Control page, select the action and press the ’execute’ button.

Appendix B provides a detailed overview of the available tasks, features,
functions and parameters.

5.4 Templates

The Show Control page presents a list of templates. A template is a set of action­list, actions and task. These templates configure the TimeCore to perform
typical functions; for example control the time-code clock with the two push­buttons or show the time-code status on the LED display.

The templates thus save time; otherwise actions should have been set up
manually. They can also function as a guide to soften the learning curve on
actions; a lot can be learned from adding a template and then exploring the
actions and tasks it created. Please note that some templates require settings
to changed in the settings page. Appendix A gives an overview of the available
templates.

5.5 Variables

Variables are internal memories that can hold a value; a number in the range
of [0,255]. There are 8 variables and they are typically used for advanced show

21

control programming. In the IoCore2, the content of the variable is not stored
between power cycles.

Variables can be set by tasks. Variables can be added as sources in order to
have actions triggered when a variable changes value.

5.6 Randomizer

The randomizer is an internal software feature that can generate a (pseudo­)random number. This is useful for having an event trigger a random lighting
scene in a themed environment. The randomizer is activated by the Randomizer­task. The result of the randomizer’s calculation can be obtained by catching
the event in the Randomizer-actionlist.

22

Chapter 6

Monitors

This page allows the user to inspect the incoming and outgoing data, both
DMX-type data (See figure 6.1) as well as control messages (See figure 6.2).
Monitoring incoming and outgoing data can help the user troubleshoot during
programming.

In the Monitor page three different sources of input can be found (DMX, Art­Net and sACN), along with the control input and output sources (TCP, UDP
and OSC). On the right side of the page there are the universes were the user
can swap between the four of them or choose a preferable unit for displaying
the requested information.

23

Figure 6.1: DMX Monitor page

Figure 6.2: OSC Monitor page

24

Chapter 7

Settings

The TimeCore’s settings are organised into sections, see the Settings page figure

7.1. This chapter will discuss each section.

Figure 7.1: Settings page

7.1 General

You can change the TimeCore’s label. This label can be used to distinguish the
unit in a set-up with multiple devices.

By enabling the Blink checkbox the device’s LED will blink to help to iden­tify it amongst multiple devices.

By enabling the Share Analytics options, you will help Visual Productions
improve its products. When enabled, the TimeCore will send daily diagnostics

25

Figure 7.2: General Settings

and usage data to Visual Productions. This information remains anonymous.

Unauthorised users can be prevented by making changes to the TimeCore by
enabling the password protection. Once enabled, the password can be disabled
via the web-interface (using the ’Disable’ button) and the reset button (see
figure 4.2). Long-press the reset button to disable the password protection; this
will also revert the unit’s static IP back to the default factory settings.

7.2 IP

The IP fields are for setting up the IP address and subnet mask of the TimeCore.
The Router field is only required when Port Forwarding is used. You can also
enable or disable the DHCP feature (For more information see chapter 4 at page

14).

Figure 7.3: IP Settings

7.3 Buttons

The two buttons in the web-interface mimic the two push-buttons on the phys­ical device. These software buttons are useful for testing or controlling the unit
when it is placed out of your reach.

26

Figure 7.4: Buttons Settings

7.4 Input

This section determines the timecode source for the TimeCore. The options are:

Source Description

Internal Timecode will be generated internally by the TimeCore

SMPTE LTC signal received on SMPTE IN connector

MTC MTC signal received on MIDI IN connector

Art-Net Art-Net timecode received via the network port

Figure 7.5: Input settings

The SMPTE and Art-Net protocol do not offer means to distinguish a signal
loss from a ’pause’ of the time. Therefor, the ’Signal Loss Policy’ allows you to
control a drop in the timecode signal should be interpreted.

27

Policy Description

Continue In the case of a signal loss the TimeCore will continue the

timecode by using its internal clock. When the signal reappears
the TimeCore will sync again to it.

Pause The TimeCore will pause the timecode when the signal is lost.

It will continue the timing as soon as the signal is restored.

7.5 Output

This section controls if any timecode protocol is transmitted from the TimeCore.
Each timecode protocol has its own frame-rate setting.

Figure 7.6: Output settings

The SMPTE and Art-Net protocol do not offer means to indicate a ’pause’ of
the timecode signal. Therefor, the TimeCore offers an ’active during pause’
checkbox to control the behaviour of the SMPTE and Art-Net signal during a
pause state.

When disabled, both SMPTE and Art-Net signal will cease; no signal will
be generated. In this case it is hard for the recipient to determine the difference
between a ’pause’ and ’signal loss’.

When ’active during pause’ is enabled for SMPTE then the TimeCore will
generate invalid SMPTE frames during the pause. This enabled the recipient
to still detect activity on the SMPTE line (this would not be the case during a
signal loss). When the checkbox is enabled for Art-Net then the TimeCore will
continue repeating the last timecode frame during the pause.

7.6 OSC

External equipment sending OSC messages to the TimeCore need to be aware
of the number specified in the ’Port’ field. This is the port the TimeCore listens
to for incoming messages.
The TimeCore will send its outgoing OSC messages to the IP addresses speci­fied in the ’Out IP’ fields. Up to four IPs can be specified here. Use the ’ipad­dress:port’ format in these fields, e.g. ”192.168.1.11:9000”. If a field should not

28

Figure 7.7: OSC Settings

be used that it can be filled with IP 0.0.0.0:0. It is possible to enter a broadcast
IP address like 192.168.1.255 in order to reach more than four recipients.

Enabling the Forward checkbox will have the TimeCore copy every incoming
OSC message and send it the addresses specified in the ’Out IP’ fields.

7.7 TCP/IP

Defines the listening ports for TCP and UDP messages. External system in­tending to send TCP or UDP message to the TimeCore should need to know
the unit’s IP address and this port number. By default both ports are set to

7000.

Figure 7.8: TCP/IP settings

7.8 Art-Net

The Art-Net (DMX data) feature in the TimeCore supports one universe out and
2 universe in. These universes can be mapped to any of the 256 available uni­verses in the Art-Net protocol. The universe is entered in the ’subnet.universe’
format, i.e. the lowest universe number is written as ’0.0’ and the highest uni­verse number is denoted as ’15.15’. The outgoing Art-Net transmission can be
disabled by entering ’off’ in the output field.

The destination IP determines where the outgoing Art-Net data will be
send to. Typically, this field contains a broadcast address like 2.255.255.255
which will send the Art-Net data to the 2.x.x.x IP range. Another typical

29

Figure 7.9: Art-Net settings

Art-Net broadcast address is 10.255.255.255. When using broadcast address

255.255.255.255 then all the devices on the network will receive the Art-Net
data.

It is also possible to fill in a unicast address like 192.168.1.11; in this case
the Art-Net data will be send to one IP address only. This keeps the rest of the
network clean of any Art-Net network messages.

7.9 sACN

Figure 7.10: sACN settings

The TimeCore supports one incoming sACN universe and 1 outgoing uni­verse. Each universe field should hold a number in the range of [1,63999].
Outgoing sACN transmission can be disabled by entering ’off ’ into the sACN
output field.

7.10 RTP-MIDI

Figure 7.11: RTP-MIDI settings

30

Refer to chapter 8 for a detailed discussion on how to setup a RTP-MIDI
connection.

31

Chapter 8

RTP-MIDI

The TimeCore supports RTP-MIDI. It is a protocol for sending MIDI messages
over Ethernet. This chapter discussed how to setup the connection between the
TimeCore and a computer.

Figure 8.1: Typical RTP-MIDI setup

Figure 8.1 illustrates a typical RTP-MIDI setup. The computer connects to
the TimeCore via Ethernet. This allows the computer to send MIDI messages to
the TimeCore. These messages can be used to control the TimeCore internally.
Alternatively, the messages can be forwarded to the physical MIDI port on the
TimeCore, using the TimeCore as a MIDI interface.

Likewise, MIDI messages generated by the TimeCore internally can be re­ceived at the computer via RTP-MIDI. As well as MIDI messages received on
the physical MIDI port.

The MIDI Throughput checkbox in figure 8.2 enables the RTP-MIDI for­warding to the TimeCore’s physical MIDI port. When disabled, the RTP­MIDI messages received from the computer can only be used internally in the
TimeCore.

8.1 Sessions

In order to communicate via RTP-MIDI a ’session’ is required. A RTP-MIDI
session is made up by one host and one or more participants. A participant

32

Figure 8.2: RTP-MIDI settings

connects to a host. This host should therefor already be made available on the
network.

Figure 8.3: Session

The TimeCore can act either as host or as participant. This choice is made
in the settings page (see figure 8.2).

8.1.1 Host

When configured as host the TimeCore will create a session. The name of this
session is derived from the TimeCore’s label plus its serial number. For example
a TimeCore with label ’MyTimeCore’ and serial 201620001 will result in session
name mytimecore201620001.

When a TimeCore sends a message via RTP-MIDI, this message will be send
to all participants. The TimeCore is capable of maintaining a connection with
up to 4 participants at the same time.

8.1.2 Participant

If the TimeCore is configured as participant it will attempt to connect to a
session with the name as defined in the ’Service name’ field (see figure 8.2).

33

8.2 Setting up the computer

The computer also needs to either host a session or join an existing session.
This paragraph describes how to set it up on macOS and Windows.

8.2.1 macOS

RTP-MIDI is natively supported by the macOS operating system. Please follow
the next steps to set it up.

1. Open Application/Utilities/Audio Midi Setup

2. Click ’Window’ and choose ’Show Midi Studio’

34

3. Double-click on ’Network’

4. Continue with ’Host’ setup on page 35 or ’Participant’ setup on page 36.

8.2.2 Windows

The Windows OS supports RTP-MIDI with the aid of a driver. We recommend
the rtpMIDI driver from Tobias Erichsen. It can be downloaded from http:
//www.tobias-erichsen.de/software/rtpmidi.html.

Install the driver and open it. Then continue with ’Host’ setup on page 35
or ’Participant’ setup on page 36

8.2.3 Host + Participant

Follow the next steps for either setting up your computer as host or as partici­pant.

1. If there are no sessions already, then add a session using the + button
underneath the My Sessions section.

35

2. Choose a local name and a Bonjour name.

3. Enable the session.

4. Set ’Anyone’ in the ’Who may connect to me’ field.

8.2.4 Participant

To join a session created by another host, select the session in the Directory list
and click on the Connect button.

36

In case the TimeCore does not automatically become visible in the Directory
listing then it is possible to add it manually. Click on the + button underneath
the Directory section.

You are free to give it any name you like. The Host field should contain the
TimeCore’s IP address. The Port field should be 65180. On Windows the host
and port are combined, separated by a ’:’ character (e.g. 192.168.1.10:65180).

37

Chapter 9

vManager

A free-of-charge software tool called vManager has been developed to manage
the devices. vManager allows for:

• Setup the IP address, subnet mask, router and DHCP

• Backup and restore the device’s internal data and settings

• Perform firmware updates

• Identify a specific device (in a multi device set-up) by blinking its LED

• Revert to factory defaults

Figure 9.1: vManager

The following section explain the buttons in the vManager, as seen in figure

9.1.

38

9.1 Backup

Backups of all the programming data inside the device can be made. This
backup file (an XML) is saved on the computer’s hard-disk and can be easily
transferred via e-mail or USB stick. The data of the backup can be restored via
the Restore button.

Figure 9.2: Creating a backup

Apps distributed by app stores are not allowed to access files outside this
designated location. It is important to know where vManager is storing its files,
in case you wish transfer a backup file to memory stick or dropbox.

The designated file location differs per operating system and is likely to be a
long and obscure path. For this reason, vManager provides you with a shortcut
to the correct file location. A Folder button can be found in the file related
dialogs. Clicking this button will open a file browser at appropriate folder.

9.2 Upgrade Firmware

To upgrade the firmware, first select the device and press the Upgrade Firmware
button. The dialogue allows for selecting from the list of firmware versions
available.

Figure 9.3: Firmware upgrade

Warning: Make sure the power to the device is not interrupted during the
upgrade process.

39

9.3 Set Date & Time

The computer’s date and time can be quickly copied to the unit by selecting a
device and clicking the Set Date & Time button. Not all Visual Productions
devices feature an internal real-time clock. The TimeCore does not have such
a RTC.

9.4 Blink

The device’s LED can be set to blink fast for identifying the particular unit
amongst multiple devices. The blinking is enabled by double-clicking on a device
in the Devices list or by selecting a device and then clicking the Blink button.

9.5 Factory Defaults

All the user data like cues, tracks and actions are stored on the memory. They
will be completely erased and all settings will reverted to their defaults by
pressing the Factory Defaults button. This action does not affect the device’s
IP settings.

9.6 Reboot

The Reboot button allows you to remotely restart the device. This is useful for
testing the unit’s behaviour after a power-cycle.

9.7 Installing vManager

The vManager app is available on a wide range of operating systems, both
mobile and desktop.

The softwares is distributed through app-stores to take advantage of receiv­ing future software updates automatically.

9.7.1 iOS

vManager can be downloaded from the Apple iOS app-store at itunes.apple.
com/us/app/vman/id1133961541.

9.7.2 Android

vManager can be found on the Google Play store at play.google.com/store/
apps/details?id=org.visualproductions.manager.

Android 5.0 or higher is required.

40

9.7.3 Windows

Visit the Microsoft store at www.microsoft.com.

Windows 10 or higher is required.

9.7.4 macOS

Visit the Apple macOS app store at itunes.apple.com/us/app/vman/id1133961541.

macOS 10.13 is recommended.

9.7.5 Ubuntu

You can acquire the vManager from the uApp Explorer uappexplorer.com/
snap/ubuntu/vmanager.

Alternatively, it can be installed by using the command-line:

snap find vmanager
snap install vmanager

To update the apps later on via the command-line type:

snap refresh vmanager

Ubuntu 18.04 LTS is recommended. The software is only available for the
amd64 architecture.

41

Chapter 10

Kiosc

Kiosc is an app for creating custom user-interface. This app (see figure 10.1)
is available on many operating systems: (iOS, Android, Windows, macOS &
Ubuntu Linux). It can remote control lighting controllers from Visual Produc­tions such as CueluxPro, CueCore, IoCore and the B-Station.

Figure 10.1: Kiosc

Please read the Kiosc manual, available from http://www.visualproductions.nl/downloads,
for more details.

42

Appendices

43

Appendix A

Templates

This appendix discusses the templates provided in the Show Control page.

Template Description

Buttons ->timecode Left push-button will start/stop. Right push-button will reset

timecode.

Timecode state ->display Timecode events like start, pause and stop will printed on the

display.

44

Appendix B

Trigger Types

The following tables list the different types of triggers that can be used in the
CueluxPro. The different types are accompanied with values and flanks.

B.1 Button

Two push-buttons at the front of the unit.

Trigger Type Trigger Value Flank Description

Button Button number Change Button state changes

Button Button number Down Button is depressed

Button Button number Up Button is released

Short press Button number - Button is depressed momentary

Long press Button number - Button is depressed for long time

B.2 MIDI

Trigger Type Trigger Value Flank Description

Message Address Change Receive a message that matches the address

Message Address Down Receive a message that matches the address and

the value non-zero

Message Address Up Receive a message that matches the address and

the value is zero

Receiving - - Receive any message

MIDI address can be any note-on, note-off, control-change, program-change
and machine-control.

45

B.3 RTP-MIDI

Trigger Type Trigger Value Flank Description

Message Address Change Receive a message that matches the address

Message Address Down Receive a message that matches the address and

the value non-zero

Message Address Up Receive a message that matches the address and

the value is zero

Receiving - - Receive any message

MIDI address can be any note-on, note-off, control-change, program-change
and machine-control.

B.4 UDP

Trigger Type Trigger Value Flank Description

Message String - Receive a message that matches the trigger-value

Receiving - - Receive any message

The user can define his own string as the trigger value of a message. Please
note that this string has a maximum length of 31 characters.

B.5 TCP

Trigger Type Trigger Value Flank Description

Message String - Receive a message that matches the trigger-value

Receiving - - Receive any message

The user can define his own string as the trigger value of a message. Please
note that this string has a maximum length of 31 characters.

B.6 OSC

Trigger Type Trigger Value Flank Description

Message URI Change Receive a message that matches the URI

Message URI Down Receive a message that matches the URI and the

value non-zero

Message URI Up Receive a message that matches the URI and the

value is zero

Receiving - - Receive any message

46

The user can define his own URI as the trigger value of a message, however,
the OSC specification dictate this string must start with a ’/’ sign. Please note
that this string has a maximum length of 31 characters, including the ’/’.

B.7 Art-Net

Trigger Type Trigger Value Flank Description

Channel DMX address Change Channel changes

Channel DMX address Down Channel becomes non-zero

Channel DMX address Up Channel becomes zero

UniverseA - - A DMX level change in the universe

Receiving - Change Start receiving or loose Art-Net signal

Receiving - Down Lost Art-Net signal

Receiving - Up Start receiving Art-Net signal

B.8 sACN

Trigger Type Trigger Value Flank Description

Channel DMX address Change Channel changes

Channel DMX address Down Channel becomes non-zero

Channel DMX address Up Channel becomes zero

UniverseA - - A DMX level change in the universe

Receiving - Change Start receiving or loose sACN signal

Receiving - Down Lost sACN signal

Receiving - Up Start receiving sACN signal

47

B.9 Timecode

Trigger Type Trigger Value Flank Description

Timecode Frame - Incoming timecode frame

reached

Playing - Change Playing state changed

Playing - Play Timecode started

Playing - Not play Timecode stopped

Paused - Change Paused state changed

Paused - Pause Timecode halted

Paused - Not pause Timecode resumed

Stopped - Change Stopped state changed

Stopped - Stop Timecode stopped

Stopped - Not stop Timecode started

Receiving SMPTE - Change Receiving changed

Receiving SMPTE - Start Start receiving

Receiving SMPTE - Stop No longer receiving

Receiving MTC - Change Receiving changed

Receiving MTC - Start Start receiving

Receiving MTC - Stop No longer receiving

Receiving RTP-MTC - Change Receiving changed

Receiving RTP-MTC - Start Start receiving

Receiving RTP-MTC - Stop No longer receiving

Receiving Art-Net timecode - Change Receiving changed

Receiving Art-Net timecode - Start Start receiving

Receiving Art-Net timecode - Stop No longer receiving

B.10 Kiosc

Trigger Type Trigger Value Flank Description

- - Change Button/Fader goes up or down

- - Down Button is pressed

- - Up Button is released

48

When editing the Kiosc actionlist it will be possible to add different kind of
actions such as Button, Fader and Colour Picker. These elements will be dis­played in the Kiosc app which is available from Visual Productions.

B.11 Randomizer

Trigger Type Trigger Value Flank Description

Result - - The Randomizer made a new

value

Specific Value Number in the range of [0,255] - The Randomizer made a value

that matches

B.12 System

Trigger Type Trigger Value Flank Description

Startup - - The IoCore2 has been power up

Network Connection - Change Network connection established or lost

Network Connection - Stop Network connection lost

Network Connection - Start Network connection established

ReleasedByMaster - Change Master (e.g. CueluxPro) released or

obtained connection

ReleasedByMaster - Stop Master released connection

ReleasedByMaster - Start Master obtained connection

49

B.13 Variable

Trigger Type Trigger Value Flank Description

Channel Variable Index - The specified variable changes

Variable 1 Number [0,255] Change Variable 1 becomes = or # to the value

Variable 1 Number [0,255] Down Variable 1 becomes = to the value

Variable 1 Number [0,255] Up Variable 1 becomes # to the value

Variable 2 Number [0,255] Change Variable 2 becomes = or # to the value

Variable 2 Number [0,255] Down Variable 2 becomes = to the value

Variable 2 Number [0,255] Up Variable 2 becomes # to the value

Variable 3 Number [0,255] Change Variable 3 becomes = or # to the value

Variable 3 Number [0,255] Down Variable 3 becomes = to the value

Variable 3 Number [0,255] Up Variable 3 becomes # to the value

Variable 4 Number [0,255] Change Variable 4 becomes = or # to the value

Variable 4 Number [0,255] Down Variable 4 becomes = to the value

Variable 4 Number [0,255] Up Variable 4 becomes # to the value

Variable 5 Number [0,255] Change Variable 5 becomes = or # to the value

Variable 5 Number [0,255] Down Variable 5 becomes = to the value

Variable 5 Number [0,255] Up Variable 5 becomes # to the value

Variable 6 Number [0,255] Change Variable 6 becomes = or # to the value

Variable 6 Number [0,255] Down Variable 6 becomes = to the value

Variable 6 Number [0,255] Up Variable 6 becomes # to the value

Variable 7 Number [0,255] Change Variable 7 becomes = or # to the value

Variable 7 Number [0,255] Down Variable 7 becomes = to the value

Variable 7 Number [0,255] Up Variable 7 becomes # to the value

Variable 8 Number [0,255] Change Variable 8 becomes = or # to the value

Variable 8 Number [0,255] Down Variable 8 becomes = to the value

Variable 8 Number [0,255] Up Variable 8 becomes # to the value

50

B.14 Timer

Trigger Type Trigger Value Flank Description

- Timer Index Change The timer starts or stops

- Timer Index Stop The timer stops

- Timer Index Start The timer starts

B.15 Actionlist

Trigger Type Trigger Value Flank Description

- Actionlist Index Change Enabled checkbox has changed

- Actionlist Index Disabled Checkbox has been disabled

- Actionlist Index Enabled Checkbox has been enabled

B.16 User List (1-4)

User lists have no triggers. Actions inside user lists can only be activated by
other actions through ’Action’ task with the ’Link’ feature.

51

Appendix C

Task Types

Tasks allow you to automate the functionality in the IoCore2. All this func­tionality is categorized in task-types. This appendix provides a listing of the
various task-types. The tables present an overview of all available features and
functions per task-type.

C.1 Action

Trigger another action.

Feature Function Parameter 1 Parameter 2

Link Set Action -

C.2 Actionlist

Manipulate an actionlist.

Feature Function Parameter 1 Parameter 2

Enable Set Action-list On or Off

Enable Toggle Action-list -

Enable Control Action-list -

Enable Inverted Control Action-list -

C.3 Button

Force the Button actions to be triggered.

Feature Function Parameter 1 Parameter 2

Refresh Set - -

52

C.4 DMX

Manipulate the DMX levels. These are the levels that can also be send out via
Art-Net or sACN.

Feature Function Parameter 1 Parameter 2

Universe Control HTP Universe # -

Universe Control LTP Universe # -

Universe Control Priority Universe # -

Universe Clear Universe # -

Channel Set DMX Channel DMX Value

Channel Toggle DMX Channel -

Channel Control DMX Channel -

Channel Inverted Control DMX Channel -

Channel Decrement DMX Channel -

Channel Increment DMX Channel -

Bump Set DMX Channel DMX Value

Bump Control DMX Channel -

Clear Set - -

RGB Set DMX Address RGB Colour Value

RGB Control DMX Address -

RGBA Control DMX Address -

XY Control DMX Address -

XxYy Control DMX Address -

C.5 MIDI

Send an MIDI message.

Feature Function Parameter 1 Parameter 2

Send Set MIDI Address MIDI Value

Send Control MIDI Address -

C.6 MMC

Send an MMC (MIDI Machine Control) message via the MIDI port.

53

Feature Function Parameter 1 Parameter 2

Send Start MIDI Channel -

Send Stop MIDI Channel -

Send Restart MIDI Channel -

Send Pause MIDI Channel -

Send Record MIDI Channel -

Send Deferred Play MIDI Channel -

Send Record Exit MIDI Channel -

Send Record Pause MIDI Channel -

Send Eject MIDI Channel -

Send Chase MIDI Channel -

Send Fast Forward MIDI Channel -

Send Rewind MIDI Channel -

Send Goto MIDI Channel Time

C.7 MSC

Send an MSC (MIDI Show Control) message via the MIDI port.

Feature Function Parameter 1 Parameter 2

Send Set Control Number Control Value

Send Start Q Number Q List

Send Stop Q Number Q List

Send Resume Q Number Q List

Send Load Q Number Q List

Send Fire - -

Send All Off - -

Send Restore - -

Send Reset - -

Send Go Off Q Number Q List

C.8 RTP-MIDI

Send an MIDI message via RTP-MIDI.

54

Feature Function Parameter 1 Parameter 2

Send Set MIDI Address MIDI Value

Send Control MIDI Address -

C.9 RTP-MMC

Send an MMC (MIDI Machine Control) message via RTP-MIDI.

Feature Function Parameter 1 Parameter 2

Send Start MIDI Channel -

Send Stop MIDI Channel -

Send Restart MIDI Channel -

Send Pause MIDI Channel -

Send Record MIDI Channel -

Send Deferred Play MIDI Channel -

Send Record Exit MIDI Channel -

Send Record Pause MIDI Channel -

Send Eject MIDI Channel -

Send Chase MIDI Channel -

Send Fast Forward MIDI Channel -

Send Rewind MIDI Channel -

Send Goto MIDI Channel Time

C.10 OSC

Send an OSC message via the network. The OSC recipients are specified in the
Settings page.

55

Feature Function Parameter 1 Parameter 2

Send Float Set URI floating point number

Send Float Control URI -

Send Unsigned Set URI positive number

Send Unsigned Control URI -

Send Bool Set URI true or false

Send Bool Control URI -

Send String Set URI String of characters

Send String Control URI -

Send Colour Set URI RGB colour

Send Colour Control URI -

Please note that string in parameter 1 has a maximum length of 25 charac­ters, including the compulsory leading ’/’ sign.

C.11 Randomiser

Trigger the Randomizer to generate a new random number.

Feature Function Parameter 1 Parameter 2

Refresh Set Minimum value Maximum value

C.12 System

Miscellaneous tasks.

Feature Function Parameter 1 Parameter 2

Blink Set On or Off -

Blink Toggle - -

Blink Control - -

C.13 Timecode

Control timecode related functions.

56

Feature Function Parameter 1 Parameter 2

Playstate Start - -

Playstate Stop - -

Playstate Restart - -

Playstate Pause - -

Playstate Toggle Start Pause - -

Playstate Toggle Start Stop - -

Time Set Frame -

Source Set Source -

Source Toggle Source Source

Source Increment - -

Autonoom Pause Set On/Off -

Enable Set Source On/Off

C.14 Timer

Manipulate on of the four internal timers.

Feature Function Parameter 1 Parameter 2

Playstate Start Timer # -

Playstate Stop Timer # -

Playstate Restart Timer # -

Time Set Timer # Time

C.15 UDP

Send an UDP message via the network. Specify the recipient in Parameter 2.
For example ”192.168.1.11:7000”.

57

Feature Function Parameter 1 Parameter 2

Send Float Set floating point number IP address & port

Send Float Control - IP address & port

Send Unsigned Set positive number IP address & port

Send Unsigned Control - IP address & port

Send Bool Set true or false IP address & port

Send Bool Control - IP address & port

Send String Set text string IP address & port

Send String Control - IP address & port

Send String Hex Set hex string IP address & port

Send String Hex Control String IP address & port

Wake On Lan Set MAC Address IP address & port

Please note that string in parameter 1 has a maximum length of 25 charac­ters.

The Send Bytes features allows for sending ASCII codes. For example, in or­der to send the string ’Visual’ followed by a line feed parameter 1 should be
’56697375616C0A’.

When using the Wake On Lan feature parameter 1 should contain the MAC
Address of system’s NIC (Network Interface Controller) you wish to wake up.
The recommended value for parameter 2 is 255.255.255.255:7. This broad­casts the message to the whole network at port 7 which is most commonly used
for Wake On Lan.

C.16 Variable

Manipulate one of the eight variables.

58

Feature Function Parameter 1 Parameter 2

Set Value Set Variable [1,8] Value [0,255]

Set Value Toggle Variable [1,8] Value [0,255]

Set Value Control Variable [1,8] -

Set Value Inverted Control Variable [1,8] -

Set Value Decrement Variable [1,8] -

Set Value Increment Variable [1,8] -

Set Value Continuous Decrement Variable [1,8] Delta [1,255]

Set Value Continuous Increment Variable [1,8] Delta [1,255]

Set Value Stop Continuous Variable [1,8] -

Set Value Control Scaled Variable [1,8] Percentage [0%,100%]

Set Value Control Offset Variable [1,8] Offset [0,255]

Refresh Set Variable [1,8] -

Single Dimmer Control Variable # Delta

Variables are further explained on page 21.

The Single Dimmer feature is used to increase or decrease a level by using
only one switch. When controlling this task via GPI action, then closing the
GPI will increase or decrease the level. Opening the GPI port will freeze on
the current level. This feature is useful for controlling an intensity will just one
button.

59

Appendix D

API

The TimeCore is pre-programmed to make its internal functionality available via
OSC and UDP. There is a simple API implemented for each protocol. Notwith­standing these API’s, it is possible to create your own OSC and UDP imple­mentation in the Show Control page.

D.1 OSC

The following table uses actionlist #1 as an example. The number ’1’ can be
replaced by any number in the range of [1,8]. The table also uses action #2 as
an example. The number ’1’ can be replaced by any number in the range of
[1,48].

URI Parameter Description

/core/al/1/2/execute bool/float/integer Execute action #2 inside action list #1

/core/al/1/enable bool Set the ’enable’ checkbox for action list #1

The following table shows how to manipulate the internal timecode.

URI Parameter Description

/core/tc/start - Start timecode

/core/tc/stop - Stop timecode

/core/tc/restart - Restart timecode

/core/tc/pause - Pause timecode

/core/tc/set time-string Set the timecode frame at the specified string. For example

”23:59:59.24”

The following table uses timer #1 as an example. The number ’1’ can be
replaced by any number in the range of [1,4].

60

URI Parameter Description

/core/tm/1/start - Start timer #1

/core/tm/1/stop - Stop timer #1

/core/tm/1/restart - Restart timer #1

/core/tm/1/pause - Pause timer #1

/core/tm/1/set time-string Set timer #1 at the time-string

The following table uses variable #1 as an example. The number ’1’ can be
replaced by any number in the range of [1,8].

URI Parameter Description

/core/va/1/set integer Set the value of variable #1

/core/va/1/refresh - Refresh variable #1; a trigger will be generated as if the

variable changed value

/core/va/refresh - Refresh all variables; triggers will be generated

The following table shows how to active miscellaneous functions.

URI Parameter Description

/core/blink - Momentarily flashes the TimeCore’s LED

D.2 TCP & UDP

The following table uses actionlist #1 as an example. The number ’1’ can be
replaced by any number in the range of [1,8]. The table also uses action #2 as
an example. The number ’1’ can be replaced by any number in the range of
[1,48].

String Description

core-al-1-1-execute=<arg> Execute action #2 inside action list #1

core-al-1-enable=<bool> Set the ’enable’ checkbox for action list #1

The following table shows how to manipulate the internal timecode.

String Description

core-tc-start Start timecode

core-tc-stop Stop timecode

core-tc-restart Restart timecode

core-tc-pause Pause timecode

core-tc-set=<text> Set the timecode frame at the specified string. For example

”23:59:59.24”

61

The following table uses timer #1 as an example. The number ’1’ can be
replaced by any number in the range of [1,4].

String Description

core-tm-1-start Start timer #1

core-tm-1-stop Stop timer #1

core-tm-1-restart Restart timer #1

core-tm-1-pause Pause timer #1

core-tm-1-set=<text> Set timer #1 at the time-string

The following table uses variable #1 as an example. The number ’1’ can be
replaced by any number in the range of [1,8].

String Description

core-va-1-set=<integer> Set the value of variable #1

core-va-1-refresh Refresh variable #1; a trigger will be generated as if the

variable changed value

core-va-refresh Refresh all variables; triggers will be generated

The following table shows how to active miscellaneous functions.

String Description

core-blink Momentarily flashes the TimeCore’s LED

62

Index

vManager, 38
19 rack, 12

Action, 18
Action list, 19
Active during pause, 28
Android, 40
API, 60
Art-Net, 10, 29, 47
Auto-sensing, 14

Backup, 39
Blink, 25, 40
Bopla, 12
Box contents, 7
Buttons, 26

Date, 40
Destination IP, 29
DHCP, 11, 15, 26
DIN Rail, 12

Factory Defaults, 40
Feature, 52
Firmware, 39
Flank, 20, 45
Forward, 29
Frame-rate, 28
Function, 52

General, 25

Host, 33

Input, 27
Internal, 27
iOS, 40
IP, 26

Kensington, 13
Kiosc, 42, 48, 49

Label, 25

Last Server Poll, 17
LED, 15
Lock, 13
LTC, 9

macOS, 41
Master IP, 17
Memory, 8
MIDI, 9, 45
MMC, 9
Mode, 17
Monitor, 23
Mounting, 12
MSC, 10
MTC, 9, 27

Network Interface Controller, 58
NTP, 17
Number of Tracks, 25

OSC, 11, 28, 46
Output, 28

Participant, 33
Password, 26
Pause, 28
PoE, 13
Polarity, 13
Port, 29
Port Forwarding, 17, 26
Power, 13

Rackmount, 12
Randomizer, 22, 49, 56
Reboot, 40
Reset button, 15
Router, 26
RTP-MIDI, 10, 30, 32, 46

sACN, 10, 30, 47
Sessions, 32
Settings, 25

63

Share Analytics, 26
Show Control, 18
Signal Loss Policy, 27
Single Dimmer, 59
SMPTE, 9, 27, 28
Snap, 41
Source, 19
Startup, 49
Subnet mask, 15
System, 49

Task, 19
Task type, 52
TCP, 10, 29, 46, 61
TCP/IP, 29
Template, 21
Templates, 44
Time, 40
Timecode, 56
Timer, 51, 57
Trigger, 19
Trigger type, 45

Ubuntu, 41
UDP, 11, 29, 46, 61
Uptime, 16
URI, 47
USB, 10
User List, 51

Variable, 50
Variables, 21, 58
VPN, 17

Wake On Lan, 58
Windows, 41

64