Visual Productions IoCore2 User Manual

IOCORE2

MANUAL

© VISUAL PRODUCTIONS BV WWW.VISUALPRODUCTIONS.NL

Revision History

Revision Date Author(s) Description

1 04.09.2017 ME Initial version.

2 19.10.2017 ME Rackmount adapter added. Quick-

start system diagrams improved.

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 Quickstart 14

4 Setting up 22

5 Network 24

6 Show Control 28

7 Monitors 33

8 Settings 35

9 vManager 41

10 Kiosc 45

Appendices 46

A Trigger Types 47

B Task Types 55

C Templates 61

D API 63

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

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

Declaration of Conformity

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

IoCore2

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:
August 31th, 2017 Haarlem, The Netherlands

ing. Maarten Engels
Managing Director
Visual Productions BV

Chapter 1

Introduction

Thank you for choosing the IoCore2. The IoCore2 is expansion module for
the CueCore and QuadCore range of solid-state lighting controllers. The Io­Core2 can add extra GPI, GPO, RS-232 and DMX ports to a CueCore based
installation. The IoCore2 is the successor of the original IoCore1.

Furthermore, the IoCore is perfectly capable of working stand-alone when
there is no CueCore attached. It can be programmed to convert and trigger any
of its protocols autonomously. Given the open nature of the IoCore’s protocol
suite (UDP, OSC, Art-Net) this unit can easily be integrated with third-party
systems.

An internal web-server provides the web-interface through which you can
program the IoCore. A modern browser is required to access this web-interface
during set-up. A browser or computer is not required for standalone use after
the initial set-up.

Figure 1.1: IoCore2

This manual discusses setting up and programming the unit. Chapter 2
provides background information on the communication protocols used the Io­Core2. Chapters 4 and 5 cover how to set up the unit and configure the network
connection.

Programming the triggering and converting functionality is done in the 6
chapter as discussed on page 28.

At the time of writing this manual the IoCore2’s firmware was at version

1.01.

6

1.1 Feature comparison

The following table visualises the difference between the IoCore2 and IoCore1.
This overview might prove to be helpful to IoCore users considering choosing
the model for their new designs.

IoCore2 IoCore1

CPU 180MHz 120MHz

Flash memory 16MB 8MB

GPI 8x digital/analog 8x digital/analog

GPO 8x relay 8x relay

RS-232 yes yes

DMX bi-directional bi-directional

Art-Net input+output input+output

sACN input+output -

TCP input input

UDP input+output input+output

OSC input+output input+output

POE class I class I

DC 12-24V 12V

DHCP yes -

CueluxPro Licence 1 universe -

Kiosc compatible yes yes

1.2 What’s in the box?

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

• IoCore2

• Power supply (including international plug set)

• Network cable

• 16-pin + 3x 6-pin terminals

• Info card

1.3 Saving data to memory

This manual will describe how to configure the IoCore2 and program conver­sions, action, etc. The unit’s web-interface is used for editing these kinds of

7

Figure 1.2: IoCore2 box contents

elements. When changes are made, these changes are directly stored in the
RAM memory of the IoCore2 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 IoCore2 will copy any changes
in the RAM memory to its onboard flash memory. Flash memory retains its
data even when not powered. The IoCore2 will load all its data back from the
flash memory upon startup.

This memory copy process is conducted automatically by the IoCore2 and should
not be of any concern of the user. One point of consideration is, however, 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 IoCore2 is fitted with several communication ports and supports various
protocols. This chapter describes these protocols and to which extent they are
implemented in the IoCore2

2.1 GPI

The IoCore2 features four General Purpose Inputs (GPI) ports that can be
connected to external equipment, switches and sensors. State changes on these
GPI ports can be used to trigger programmed events inside the IoCore2.

Figure 2.1: GPI Pinout

Each GPI port can be switched between ’digital’ and ’analog’. In the digital
mode the signal is held up by an internal pull-up resistor and results in a logic
’0’. The external equipment is intended to short the port’s pin to the provided
ground pin. This short will create a logic ’1’. All four ports share one common
ground pin.

When set to analog the external equipment is supposed to supply a voltage
between 0V and 10V to the port’s pin. For convenience, a 10V supply is available
on one of the pins of the GPI connector. Please refer to figure 2.1 for the pinout
of the GPI connector. Be careful not to supply more than 10V to the GPI port

as that might cause permanent damage.

Figure 2.2 shows examples of how to wire a contact-closure to a GPI port
set to digital. And it shows an example of potentiometer connected to a GPI
port set to analog.

Please refer to page 37 for more information on configuring the GPI ports.
Programming events based on GPI activity is done in the Show Control page,
which is discussed on page 28.

9

(a) Contact-closure (b) Potentiometer

Figure 2.2: GPI Wiring examples

2.2 GPO

Each GPO port features a normally-open (NO) relay for switching external
equipment. The relay can switch 250VAC/30VDC up to 2A. Please refer to
figure 2.3 for the pinout of the GPO connector.

Figure 2.3: GPO Pinout

2.3 RS-232

The bi-directional RS-232 port can be used to communicate with external equip­ment such as video projectors and matrix switchers. Figure 2.4 shows the pinout
of the connector which shared with the DMX port. Please refer to page 36 for
more information on configuring the RS-232 port.

Figure 2.4: RS-232 Pinout

10

2.4 DMX-512

DMX-512 is the standard communication protocol for stage lighting. Its official
name is E1.11-2008 USITT DMX512-A. Nowadays the reach of the DMX proto­col has extended beyond entertainment lighting and is also used for architectural
lighting.

Originally one DMX network contained 512 channels which is called a ’uni­verse’. With the growing size and complexity of lighting systems it is now very
common for a system to compose of multiple universes, each conveying 512
channels.

It is advised to use a shielded twisted pair cable for DMX cabling. The cable
should be terminated with an 120 Ohm resistor.

DMX-512 is a very successful protocol with, however, a few limitations. The
maximum number of attached devices is limited to 32 and they all have to be
connected in bus-topology having one cable running via each device. Further­more, a DMX-512 cable should not be longer than 300 meters.

Figure 2.5: Visual Productions’ RdmSplitter

The DIN Rail RdmSplitter from Visual Productions (See figure 2.5) helps tackle
those inconvenient limitations. The Splitter takes a DMX signal and sends it
out again on its 6 DMX output ports for scaling group topology. Each output
port is capable of driving 32 more devices. The Splitter can also function as a
signal booster as each port supports another 300 meter long connection.

The IoCore2 has one DMX port and is therefor able control 512 channels.
The port can be configured either as input or output. Figure 2.6 shows the
pinout of the connector.

Figure 2.6: DMX Pinout

11

2.5 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,
therefore it is recommended to disable Art-Net when not in use. The IoCore2
can receive and send out one DMX universe over Art-Net. Art-Net can be used
for creating triggers in the show control programming.

2.6 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 IoCore2 supports sending and receiving of 1 sACN universe.

2.7 KiNet

KiNet is a proprietary protocol of Philips Color Kinetics to control their LED
fixtures and power supplies. It is a lightweight Ethernet-based protocol that
carries DMX-style data. Within the IoCore2 it can only be used to output
data.

2.8 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
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 IoCore2 supports reception of TCP message.

2.9 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 IoCore2 respond to incoming UDP
messages. The API (see page 64) makes typical IoCore2 functions available

12

through UDP. Furthermore, custom messages can be programmed in the Show
Control page (see page 28). This is also the place where to program outgoing
UDP messages.

2.10 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 IoCore2 respond to incoming OSC
messages. Firstly, the API (see page 63) makes typical IoCore2 functions avail­able through OSC. Secondly, custom messages can be programmed in the Show
Control page (see page 28).

2.11 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 IoCore2 is a DHCP client.

13

Chapter 3

Quickstart

This chapter provides step by step tutorials on how to program your IoCore2
for some typical tasks:

• Convert 0-10V levels to DMX

• Use DMX to trigger a RS-232 lamp strike command to a video projector

3.1 Convert 0-10V levels to DMX

This tutorial shows how to use the IoCore2 to convert 0-10V levels to DMX.
The 0-10V levels could be generated by sensors (e.g. ambient lighting sensor)
or a potentiometer (1-10V wall mount rotary dimmer). The DMX levels can
then be used to directly control lighting fixtures or it can be fed into an external
lighting console to control the intensity of complete scenes. Please follow the
next few steps.

14

1. Connect to the network
Connect the IoCore2 with an Ethernet cable to the router. It is required
that the network is managed by a router that features a DHCP server. If
the network router is not DHCP capable then read the network chapter
on page 24 for alternative setups.

2. Install the vManager
To access the web-interface of the IoCore2, the vManager tool is rec­ommended. This tool can be downloaded from the Visual Productions
website and installed. Once the installation is complete, run the vMan­ager to discover the IP address of the IoCore2.

3. Open the web-interface
Choose the IoCore2 from the device list and click on the ’Browse’ button
to open the web-interface.

15

4. Add template
Go to the Show Control page and select the ’GPI ->DMX’ template.
Press the ’Add >>’ button in the lower left corner of the screen.

5. Configure GPI port
Go to the IoCore2 Settings page and set GPI port 1 to ’analog’.

6. Configure the DMX port
In the settings page, set the DMX port direction to ’output’

Changing the rotary encoder should now control DMX channel 1 for the fixture.

16

3.2 Use DMX to trigger a RS-232 lamp strike
command to a video projector

This example enables an external DMX source to trigger a RS-232 message that
will be send to a video projector; the RS-232 message could be used to strike
the lamp within the projector. Please take the following steps:

1. Setup network and connect equipment
Connect the IoCore2 and the computer to a DHCP capable network
router. Connect the the external DMX board to the DMX port. Connect
the projector to the RS-232 port.

17

2. Add source
Open a browser on the computer and browse to the web-interface of the
IoCore2 by typing ’192.168.1.10’ in the browser’s address field. Go to the
Show Control page and select the ’DMX In’ source. Press the ’Add >>’
button below the table.

18

3. Add action
Make sure the ’DMX In’ actionlist is selected and press the ’<<Add’
button below the ’Action Types’ table.

4. Edit action
Make sure the new action is selected and press the ’Edit’ button. Set the
flank to ’Down’. This will make sure that the action is only triggered
when DMX channel 1 goes from 0% to non-zero.

19

5. Add task
Press the ’Add’ button at the top left of the screen and choose ’RS-232’
from the task categories.

6. Edit task
Select the task and change the feature to ’Send String’. Set the function
to ’Set’. Enter e.g. ’lampon’ in parameter 1. You can now exit the
dialog by pressing the ’Close’ button. Please consult the projector’s
documentation and replace the ’lampon’ string accordingly.

20

7. Configure RS-232 port
Go to the IoCore2 Settings page. Set the RS-232 details to match
specifications that would be found in the projector’s documentation.

8. Configure the DMX port
In the settings page, set the DMX port direction to ’input’

Bringing channel 1 up from 0% will now make the IoCore2 send the RS-232
string to the projector. The DMX console should bring channel back to 0% so
it is ready to triggered again.

21

Chapter 4

Setting up

This chapter discusses how to set up the IoCore2.

4.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 4.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)

4.2 Rackmount

There is an adapter available for mounting the IoCore2 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 4.2.

22

Figure 4.2: Rackmount adapter

4.3 Kensington Lock

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

Figure 4.3: Kensington lock

4.4 Power

The IoCore2 requires a DC power supply between 12 and 24 Volt with a mini­mum of 500mA. The 2,1 mm DC connector is center-positive. The IoCore2 is
also Power-over-Ethernet (PoE) enabled. It requires PoE Class I.

Figure 4.4: DC polarity

23

Chapter 5

Network

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

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

Figure 5.1: Network arrangements

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

24

5.1 IP Address

The IoCore2 supports both static IP addresses and automatic IP addresses. By
default, the IoCore2 is set DHCP in which it will be automatically assigned 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 IoCore2 and
a computer. It is also useful in permanent installations where the IP address
of the IoCore2 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 IoCore2’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 IoCore2.

Figure 5.2: Reset button

• vManager can be used to detect a IoCore2 on the network. Once found,
the vManager software (figure chapter 9) allows for changing the IP ad­dress, 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 IoCore2’s web-interface. The Settings
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 5.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.

25

5.2 Web-interface

The IoCore2 features an inbuilt web-server. This web-interface can be accessed
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 IoCore2. When
browsing to the unit the home page (figure 5.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 5.3: Home page

5.2.1 Uptime

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

5.2.2 Master IP

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

26

5.3 Access via Internet

The IoCore2 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 IoCore2 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 IoCore2. 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.

27

Chapter 6

Show Control

The IoCore2 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 IoCore2 by having it respond automatically to incoming
signals. An example of this would be to control the GPO relays by receiving a
specific UDP network message. The Show Control page (See figure 6.1) enables
this kind of programming to be made.

When using the IoCore2 as an expansion to the CueCore controller then it
is advised to use OSC messages to establish communication between IoCore2
and CueCore. To setup the IoCore2 quickly for this purpose it is recommended
to add a template. Templates are discussed on page 31.

Figure 6.1: Show Control page

The Show Control page presents a system of ’actions’. A signal that the Io­Core2 needs to respond to or perhaps convert into some other signal, needs to

28

be expressed in an actions. Before programming actions please consider the
Show Control structure in figure 6.2.

Figure 6.2: Show Control structure

The IoCore2 is capable of listening to various protocols. These available pro­tocols are listed in Sources, however, the IoCore2 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 IoCore2 will do
when this action is triggered. Several tasks can be placed in the action. There
are tasks available for a wide range of IoCore2 features and external protocols.
Task types are detailed in Appendix B on page 55.

6.1 Sources and Actionlists

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

29

Source Description

GPI Changes on one of the GPI ports

GPO Changes on one of the GPO ports

DMX Input Receiving DMX data when the DMX port is set as input

RS-232 Receiving RS-232 serial messages

UDP UDP network messages

TCP TCP network messages

OSC OSC network message

Art-Net Art-Net DMX data

sACN sACN DMX data

Touch Screen 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.

Timer Internal timers expiring

Actionlist Actionlist’s enable-checkboxes changing state

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

are useful for advanced programming.

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.

6.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 some­times omitted in the web GUI. The trigger-type field specifies what kind of sig-

30

nal the action will be triggered by. For example, when making an action in the
Art-Net list there is the choice between ’Channel’ and ’Receiving’ trigger-types.
The trigger-value specifies the actual signal value. In the Art-Net example the
trigger-value could be set to ’channel 1’ or ’channel 2’.

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 ac­tion. For example, when an action is triggered from a Touch Screen 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 A
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.

6.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, systemwide 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 GPOs but 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.

If the event that triggers the action passes a parameter along then this
parameter can be used in a task. The ’set’ function makes a task use a fixed
value, however, when using the ’control’ function then the trigger’s parameter
is used. This is very useful for conversions between protocols.

For example when converting 0-10V to DMX the GPI action specifies the
port (e.g. #1) and flank (e.g. OnChange) on which it will trigger. The actual
0-10V level sampled on the GPI port will passed along and fed into the action.
Then when a task (e.g. DMX) uses the function ’control’ this 0-10V level will
be used for setting the DMX value.

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.

6.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 IoCore2 to perform
typical functions; for example convert Art-Net to DMX or control the 8 relays
through OSC. 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

31

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; for example the ’Receiving Art-Net’ template needs the Art-Net sub­net/universe to specified in order to achieve an Art-Net to DMX conversion.
Appendix C gives an overview of the available templates.

6.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
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.

6.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.

32

Chapter 7

Monitors

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

33

Figure 7.1: DMX Monitor page

Figure 7.2: UDP Monitor page

34

Chapter 8

Settings

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

8.1. This chapter will discuss each section.

Figure 8.1: Settings page

8.1 General

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

35

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

Figure 8.2: General Settings

By enabling the Share Analytics options, you will help Visual Productions
improve its products. When enabled, the IoCore2 will send daily diagnostics
and usage data to Visual Productions. This information remains anonymous.

Unauthorised users can be prevented by making changes to the IoCore2 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 5.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.

8.2 IP

The IP fields are for setting up the IP address and subnet mask of the IoCore2.
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 5 at page

24).

Figure 8.3: IP Settings

8.3 RS-232

Settings for RS-232 communication like baudrate and stopbits.

36

Figure 8.4: RS-232 Settings

8.4 GPI

The GPI ports can be configured either as digital (contact-closure) or as analog
(0-10V) input.

In case a port is set as analog and the signal supplied falls within the 0-10V
range (e.g. 1-5V) then it is recommended to calibrate to port in order to map
the minimal voltage to a logical 0% and map the maximum voltage to 100%.

To perform a calibration first enable the Calibrate button, then bring the
incoming signal to the minimum level, bring the signal to the maximum level
and then close the calibration process by clicking the Calibrate button again.

Figure 8.5: GPI Settings

Do not apply more than 10V to the GPI port, as this could cause permanent
damage.

Each port has a label field that can contain a user-description.

8.5 GPO

This section shows the status of the GPO relays and provides buttons to switch
them directly. Each port has a label field that can contain a user-description.

37

Figure 8.6: GPO Settings

8.6 DMX

This section allow for changing the direction of the DMX port. When the ’Slow

Figure 8.7: DMX Settings

DMX’ checkbox is enabled, the IoCore2 will slowdown the rate at which it
sends out DMX from its ports. This is done to facilitate DMX fixtures that
have difficulties keeping up with the optimal DMX transmission rate.

8.7 Art-Net

The IoCore2 supports sending out 1 universe or and receiving 1 universe of Art­Net. These universes can be mapped to any of the 256 available universes 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 universe number
is denoted as ’15.15’. The outgoing Art-Net transmission can be disabled by
disabling the checkbox.

Figure 8.8: Art-Net settings

38

The vManager software also allows you to change the Art-Net destination IP.
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 Art-Net broad­cast 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.

8.8 sACN

Figure 8.9: sACN settings

The IoCore2 supports 1 incoming sACN universe and 1 outgoing universe.
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 fields.

8.9 OSC

External equipment sending OSC messages to the IoCore2 need to be aware of
the number specified in the ’Port’ field. This is the port the IoCore2 listens to
for incoming messages.

Figure 8.10: OSC Settings

The IoCore2 will send its outgoing OSC messages to the IP addresses specified

39

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
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 IoCore2 copy every incoming OSC
message and send it the addresses specified in the ’Out IP’ fields.

8.10 TCP/IP

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

Figure 8.11: TCP/IP settings

40

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.

41

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.

42

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 IoCore2 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.

43

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.

44

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.

45

Appendices

46

Appendix A

Trigger Types

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

47

A.1 GPI

Trigger Type Trigger Value Flank Description

Channel Port number Change Port state changes

Channel Port number Down Port is closed

Channel Port number Up Port is opened

Channel 0-19% Port number Change Analog level enters or leaves the range

Channel 0-19% Port number Down Analog level enters the range

Channel 0-19% Port number Up Analog level leaves the range

Channel 20-39% Port number Change Analog level enters or leaves the range

Channel 20-39% Port number Down Analog level enters the range

Channel 20-39% Port number Up Analog level leaves the range

Channel 40-59% Port number Change Analog level enters or leaves the range

Channel 40-59% Port number Down Analog level enters the range

Channel 40-59% Port number Up Analog level leaves the range

Channel 60-79% Port number Change Analog level enters or leaves the range

Channel 60-79% Port number Down Analog level enters the range

Channel 60-79% Port number Up Analog level leaves the range

Channel 80-100% Port number Change Analog level enters or leaves the range

Channel 80-100% Port number Down Analog level enters the range

Channel 80-100% Port number Up Analog level leaves the range

Binary Combination value - A combination of ports being closed

Short press Port number - Short closure on port

Long press Port number - Long closure on port

Use the Binary trigger type to catch port combinations when they are set as
digital. Specify the port combination by adding the values that correspond to
the ports (see table below). This value is entered as the trigger value.

48

Port Value

1 1

2 2

3 4

4 8

5 16

6 32

7 64

8 128

For example, to trigger on both port 1 and 2 being closed fill in trigger value 3
(1+2). To trigger on port 5 and 6, fill in value 48 (16+32).

A.2 DMX In

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

A.3 RS-232

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 25 characters.

It is possible to pass a parameter along with a message. In order to do
this use the syntax trigger=value. For example when the trigger type is set
to ’message’ and the trigger value is set to intensity then the transmitting
equipment can pass an intensity level by sending intensity=255, where 255
can be any number in the range [0,255].

49

A.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.

It is possible to pass a parameter along with a message. In order to do
this use the syntax trigger=value. For example when the trigger type is set
to ’message’ and the trigger value is set to intensity then the transmitting
equipment can pass an intensity level by sending intensity=255, where 255
can be any number in the range [0,255].

A.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.

A.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

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 ’/’.

50

A.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

A.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

A.9 Touch Screen

Trigger Type Trigger Value Flank Description

- - Change Button/Fader goes up or down

- - Down Button is pressed

- - Up Button is released

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

51

A.10 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

A.11 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

52

A.12 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

53

A.13 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

A.14 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

A.15 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.

54

Appendix B

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.

B.1 Action

Trigger another action.

Feature Function Parameter 1 Parameter 2

Link Set Action -

B.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 -

B.3 DMX

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

55

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 -

B.4 GPI

Force the GPI actions to be triggered.

Feature Function Parameter 1 Parameter 2

Refresh Set - -

B.5 GPO

Control the GPO relays.

56

Feature Function Parameter 1 Parameter 2

Set Value Set Port [1,8] On/Off

Set Value Toggle Port [1,8] -

Set Value Control Port [1,8] -

Set Value Pulse Port [1,8] -

Solo Set Port [1,8] -

Solo Control Port [1,8] -

Random Solo Set - -

Clear All Set - -

B.6 OSC

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

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.

B.7 Randomiser

Trigger the Randomizer to generate a new random number.

Feature Function Parameter 1 Parameter 2

Refresh Set Minimum value Maximum value

57

B.8 RS-232

Send an message via the RS-232 port. Specify the port settings (baudrate, stop­bits, etc) in the settings page.

Feature Function Parameter 1 Parameter 2

Send Float Set floating point number -

Send Float Control - -

Send Unsigned Set positive number -

Send Unsigned Control - -

Send Bool Set On or Off -

Send Bool Control - -

Send String Set text string -

Send String Control - -

Send String Hex Set hex string -

Send String Hex Control String -

Send Bytes Set Hex string -

Send Bytes Control - -

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’.

B.9 System

Miscellaneous tasks.

Feature Function Parameter 1 Parameter 2

Blink Set On or Off -

Blink Toggle - -

Blink Control - -

B.10 Timer

Manipulate on of the four internal timers.

58

Feature Function Parameter 1 Parameter 2

Playstate Start Timer # -

Playstate Stop Timer # -

Playstate Restart Timer # -

Time Set Timer # Time

B.11 UDP

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

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.

B.12 Variable

Manipulate one of the eight variables.

59

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 32.

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.

60

Appendix C

Templates

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

61

Template Description

GPI ->OSC Float Each GPI port converts to an OSC message using a floating point

parameter. This template is intended for GPI set to analog. Specify
the OSC target IPs on the settings page.

GPI ->OSC Bool Each GPI port converts to an OSC message using a boolean

parameter. This template is intended for GPI set to digital. Specify
the OSC target IPs on the settings page.

GPI ->UDP Float Each GPI port converts to an UDP message using a floating point

parameter. This template is intended for GPI set to analog. Specify
the UDP target IPs in parameter 2 of each task.

GPI ->UDP Bool Each GPI port converts to an UDP message using a boolean

parameter. This template is intended for GPI set to digital. Specify
the UDP target IPs in parameter 2 of each task.

GPI ->DMX Each GPI port controls a DMX channel (1-8). The direction of the

DMX port should be set to output.

DMX ->GPO Control the GPO relays by DMX (channel 1-8). The direction of the

DMX port should be set to input.

Art-Net ->GPO Control the GPO relays by Art-Net (channel 1-8). The Art-Net

universe number is determined on the settings page.

sACN ->GPO Control the GPO relays by sACN (channel 1-8). The sACN universe

number is determined on the settings page.

Receiving DMX Read in the DMX universe. It can be outputted by Art-Net and/or

sACN.

Receiving Art-Net Read in the Art-Net universe. It can be outputted by DMX and/or

sACN.

Receiving sACN Read in the sACN universe. It can be outputted by DMX and/or

Art-Net.

GPI ->CueCore2 Each GPI port controls a playback on a CueCore2. The CueCore2 is

controlled via its fixed OSC mapping. Specify the OSC target IP on
the settings page.

GPI ->LPU-2 Each GPI port controls a playback on a LPU-2. The LPU-2 is

controlled via its fixed OSC mapping. Specify the OSC target IP on
the settings page.

62

Appendix D

API

The IoCore2 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 GPO #1 as an example. The number ’1’ can be re­placed by any number in the range of [1,6].

URI Parameter Description

/core/gpo/1 bool Switch the relay on GPO port #1

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 directly control the DMX values. The
DMX port needs to be switched to output. The table uses dmx channel #1 as
an example. The number ’1’ can be replaced by any number in the range of
[1,512].

URI Parameter Description

/core/dmx/1 integer Set the value of DMX channel 1

The following table uses timer #1 as an example. The number ’1’ can be

63

replaced by any number in the range of [1,4].

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 IoCore2’s LED

/core/hello - The unit will reply with the same Hello message

D.2 UDP

The following table uses GPO #1 as an example. The number ’1’ can be re­placed by any number in the range of [1,6].

String Description

core-gpo-1=<0/1> Switch the relay on GPO port #1

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

64

The following table shows how to directly control the DMX values. The
DMX port needs to be switched to output. The table uses dmx channel #1 as
an example. The number ’1’ can be replaced by any number in the range of
[1,512].

String Description

core-dmx-1=<integer> Set the value of DMX channel #1

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 IoCore2’s LED

core-hello The unit will reply with the same Hello message

65

Index

vManager, 41
19 rack, 22

Action, 28, 30
Action list, 29
Actionlist, 29
Android, 43
API, 63
Art-Net, 12, 38, 51
Auto-sensing, 24

Backup, 42
Baudrate, 36
Blink, 36, 43
Bopla, 22
Box contents, 7
Broadcast, 39

Calibrate, 37
Comparison, 7
Contact-closure, 9
Control, 31

Date, 43
Destination IP, 39
DHCP, 13, 25, 36
DIN Rail, 11, 22
DMX, 38
DMX-512, 11

Execute, 31

Factory Defaults, 43
Feature, 55
Features, 7
Firmware, 42
Flank, 30, 47
Forum, 8
Forward, 40
Function, 55

General, 35

GPI, 9, 37
GPO, 10, 37

IoCore1, 7
iOS, 43
IP, 36

Kensington, 23
KiNet, 12
Kiosc, 30, 45, 51

Label, 35
LED, 25
Lock, 23

macOS, 44
Master IP, 26
Memory, 7
Mode, 26
Monitor, 33
Mounting, 22

Network Interface Controller, 59

OSC, 13, 39, 50

Password, 36
PoE, 23
Polarity, 23
Port, 40
Port Forwarding, 27, 36
Potentiometer, 9
Power, 23

Quickstart, 14

Rackmount, 22
Randomizer, 32, 52, 57
RdmSplitter, 11
Reboot, 43
Relay, 37
Reset button, 25

66

Router, 36
RS-232, 10, 36, 49

sACN, 12, 39, 51
Settings, 35
Share Analytics, 36
Show Control, 28
Single Dimmer, 60
Snap, 44
Source, 29
Startup, 52
Subnet mask, 25
System, 52

Task, 29, 31
Task type, 55
TCP, 12, 40, 50
TCP/IP, 40
Template, 31, 61
Templates, 61
Time, 43
Timer, 54, 58
Touch Screen, 51
Trigger, 29
Trigger Type, 47
Trigger type, 47
Tutorial, 14

Ubuntu, 44
UDP, 12, 40, 50
Unicast, 39
Uptime, 26
URI, 50
User List, 54

Variable, 53
Variables, 32, 59
VPN, 27

Wake On Lan, 59
Windows, 44

67