Posted on

Switch-Edit lamp personalities

The Switch-Edit software is downloaded from the product page, under the Resources section.

Occasionally, after installation, the Switch-Edit software does not list any lamp personalities. This problem occurs due to the different international names for the ‘Program Files’ folder.

To fix this, use the menu: Tools – Fixture Library Folder.

Navigate to the folder shown below and press OK.

Posted on

Art-Net: I can’t find my gateway

I can’t find my gateway:

1) Check that you have the IP on your laptop setup correctly. It should be 2.0.0.1 and subnet 255.0.0.0

See: 0110 Art-Net Setting an IP address on Windows XP

2) You should be running DMX-Workshop as administrator.

See: 0801 Misc – Using Windows XP Compatibility Mode

3) To find out the IP address of your product, see FAQ Art-Net: Finding the IP Address of a product

Posted on

Product connector types

Artistic Licence products use various connector types. The most common are XLR5, RJ45 and screw terminals. We offer the following adapter products:

Rail-Patch provides a connection between a 5-pin XLR connector and screw terminals for DIN rail products.

Henry/Henrietta provides a connection between a 5-pin XLR connector and an RJ45 terminal for rack mount products.

Posted on

DMX512: Resources

Application Note 0201 – DMX & RDM Introduction. This includes wiring details for XLR and RJ45.

Application Note 0205 – DMX & RDM Splitters. What are they and where to use them.

Application Note 0215 – DMX & RDM Marking. Howe to interpret splitter marking symbols.

Application Note 0210 – DMX & RDM Splitter Comparison. Compare Artistic Licence splitters.

FAQ:

Q: What is maximum cable length for DMX512?

A: 300m

Q: Can I use Cat5?

A: Yes

Q: How do I terminate:

A: With products that use an XLR, you can connect a terminator plug. With DIN-Rail products, there is an internal terminator which is connected enabled by fitting a wire link between TERM and DATA+.

Posted on

PoE: Power over Ethernet

Power-over-Ethernet or PoE defines the way that an ethernet cable can be used to send both power and data to a product. The product which uses PoE is called a ‘PD’ (Powered Device) and the product which supplies the power and data – often an ethernet switch – is called the ‘PSE’ (Power Sourcing Equipment).

PDs require differing amounts of power depending upon their design and the load they are driving.

PSEs are capable of supplying different amounts of power.

These variables are addressed by a number of IEEE standards:

  • PoE is described by IEEE802.3af-2003. It allows a maximum of 15.4W to be supplied.
  • PoE+ is described by IEEE802.3at-2009. It allows a maximum of 25.5W to be supplied.
  • PoE++ is in development and will be described by IEEE802.3bt-2017. It allows a maximum of 90W to be supplied using all 4 pairs. There are 4 different power levels available: 38.7W, 52.7W, 70W and 90W.

The wattages described above refer to the power made available by the PSE. As there are significant losses in the cable, the amount of power available at the PD is lower.

Posted on

sACN: Artistic Licence products

The sACN (streaming ACN) protocol is supported in Artistic Licence ethernet products. The differences between Art-Net and sACN lead to some minor clashes which this document seeks to clarify.

Universe numbering

In Art-Net, universes are called Port-Address and number from 0 to 32,767. There are 32,768 unique numbers.

In sACN, universes number from 1 to 63,999. There are 64,000 unique numbers. The standard reserves the values of 0 and 64,000 to 65,535 for future expansion.

Clearly there is the potential for confusion over the number ‘0’. If a universe is set to ‘0’ and the sACN protocol is selected, Artistic Licence products will use a universe value of ‘1’ instead.

Merging and arbitration

The sACN protocol uses a concept called Component Identifier (CID) as a method to optionally distinguish unique streams of data, and a concept called Priority as a method to define the priority of a stream.

 

The following table defines how sACN packets A & B are arbitrated or merged when directed to same universe.

CIDPriorityWhat happens?
A=BA=BStreams A and B are identical and are output as DMX.
A<>BA=BStreams A and B are from different controllers but have same priority. The streams will be merged using the LTP/HTP settings of the product. A maximum of two streams can be merged. If a third stream appears it will be ignored.
A=BA>BStreams A and B are from the same controller and A has higher priority. B is ignored and A is output. If A stream stops for more than a 5 second time out period, the lower priority stream will take over. If a stream with a higher priority that which is outputting is detected, the higher priority stream immediately takes precedence.
A=BA<BStreams A and B are from the same controller and B has higher priority. A is ignored and B is output. If A stream stops for more than a 5 second time out period, the lower priority stream will take over. If a stream with a higher priority that which is outputting is detected, the higher priority stream immediately takes precedence.
A<>BA>BStreams A and B are from different controllers and A has higher priority. B is ignored and A is output. If A stream stops for more than a 5 second time out period, the lower priority stream will take over. If a stream with a higher priority that which is outputting is detected, the higher priority stream immediately takes precedence.
A<>BA<BStreams A and B are from different controllers and B has higher priority. A is ignored and B is output. If A stream stops for more than a 5 second time out period, the lower priority stream will take over. If a stream with a higher priority that which is outputting is detected, the higher priority stream immediately takes precedence.
Posted on

Software products – Windows compatibility

After Windows XP, Microsoft significantly changed the way in which application software can communicate with Windows. This means that in Vista, Windows 7, 8 and 10 some of our software products must be run in a special mode. This mode is called Windows XP compatibility mode with administrator rights. See the application note.

The products concerned are Mic-Edit and Switch-Edit.

Posted on

LED: Constant Voltage Dimming

There are two key methods of dimming LED: Constant current (CC) and constant voltage (CV). CV dimmers put out a constant voltage and the current control is done by the LED fixture. This type of dimming tends to be used for the lower power LED products such as Flexi-Strip. CC dimmers put out a controlled current, which means that the fixture does not need electronics for current control of the LED. This style of dimming is used for higher power LED products.

It is important to choose the correct technology of dimmer as an incorrect choice will most likely damage the fixture.

Below is a summary of the Constant Voltage dimmers offered by Artistic Licence:

Rail-Pipe HC is a high current DMX dimmer for 2 x RGB circuits (6 channel).

  • Voltage: 12-24V.
  • Current Max: 20A per product, 10A per RGB circuit
  • Control: DMX512 / RDM
  • Form: DIN Rail

Art-Pipe is an 8 x RGB circuits (24 channel) dimmer with network control.

  • Voltage: 12-24V.
  • Current Max: 10A per product, 2A per RGB circuit. (Note that RGB circuit current is limited by maximum, so if all channels are equally loaded, the limit per RGB circuit is 1.25A
  • Control: Art-Net
  • Form: DIN Rail

 

Posted on

RDM: Manufacturer Specific PIDs

Manufacturer-specific PIDs are used to provide manufacturers with a mechanism to implement RDM commands that are not available in the standard RDM command set. The RDM standard says:

“Manufacturer-specific PID‘s shall be created in the range of 0x8000 – 0xFFDF. Uniqueness of PID‘s in this range is accomplished by associating the PID with the Manufacturer ID found as the most significant 16-bits of the UID. PID‘s in the range of 0xFFE0 – 0xFFFF are reserved for future uses of this standard.”

There are generally two categories of use:

1) To implement additional functionality that will be available to all.

2) To implement manufacturing specific commands that will be closed to all but the manufacturer.

The first option is simple to implement. The manufacturer-specific PIDs are defined and published using PIDs such as Supported_Parameters and Parameter_Description. From then on, it is the controller’s responsibility to ensure that it only sends you valid manufacturer-specific Pids.

The second option provides more room for error if the designer does not think through all scenarios. It is quite usual for manufacturers to use a manufacturer-specific Pid for functions such as ‘programme UID’. Clearly these are intended to only be used in the manufacturing process and chaos would ensue if they were activated in the field.

What can manufacturers do to protect against inadvertent activation of their manufacturer-specific Pids:

1) Not public the Pid in Supported-Parameters. This is sensible, but does not give any real protection. For example, network test software way well send un-published manufacturer-specific Pids to see whether the device responds.

2) Ensure that the responder will only accept critical manufacturer-specific Pids when it is in a “special configuration mode”.

3) Include ‘magic-numbers’ in the packet to ensure that manufacturer-specific Pids sent in error do not have unexpected effects.

4) Ensure that the responder will only accept critical manufacturer-specific Pids which have a source-UID containing the manufacturer code. This is the strongest protection.

An index of published manufacturer PIDs can be found at http://rdm.openlighting.org/pid/manufacturer

Posted on

Art-Net: Version Numbers

Numerous of the Art-Net packets contain Version numbers.

These can be either the version number of Art-Net or the Node’s version number. The terms ProtVerHi / ProtVerLo are used to describe the Art-Net protocol version number. This has never been changed and is set at:

  • ProtVerHi = 0
  • ProtVerLo = 14

The terms VersInfoH / VersInfoL are used to describe the Node’s version number. This field is defined by the manufacturer and usually contains the firmware revision number. The ArtPollReply message contains this information.

Posted on

Art-Net: Multiple controllers

Art-Net allows and supports multiple controllers on a network. When there are multiple controllers, Nodes will receive ArtPolls from different controllers which may contain conflicting diagnostics requirements. This is resolved as follows:

  • If any controller requests diagnostics, the node will send diagnostics. (ArtPoll->Flags->2).
  • If there are multiple controllers requesting diagnostics, diagnostics shall be broadcast. (Ignore ArtPoll->Flags->3).
  • The lowest minimum value of Priority shall be used. (Ignore ArtPoll->Priority).
Posted on

Art-Net: ArtPoll and ArtPollReply timeout

A Node must respond to an ArtPoll with an ArtPollReply within 3 seconds. If the Controller does not receive a response in this time it should consider the Node to have disconnected. It is a requirement of Art-Net that all controllers broadcast an ArtPoll every 2.5 to 3 seconds. This ensures that any network devices can easily detect a disconnect.

Posted on

Art-Net: Implementing ArtPoll and ArtPollReply

In order to make a product visible in DMX-Workshop, the product must reply to an ArtPoll with one or more ArtPollReply. The screenshot below shows a Wire Shark capture of the ArtPollReply packets from a Data-Lynx IOP.

Common errors in formatting ArtPollReply are:

1) The text signature at the top of the packet is “Art-Net”. It is case sensitive.

2) DMX-Workshop only listens on Port 6454 (decimal).

If you have difficulty making your product visible in DMX-Workshop then submit a Wire Shark capture on a support ticket and we will try to help.

artpollreply in wireshark
artpollreply in wireshark
Posted on

moody: Fade time detail

All versions of moody (with a DMX512 port) output a total of 42 slots (or channels) of data. The first 40 slots are filled with colour information in either 3 slot footprints for RGB or 4 slot footprints for RGBW. For example, the largest moody – the “moody y10” – outputs 4 x 10 slots.

moody products which produce less data will still output 42 slots – the unused slots are just zero.

The final slot: slot 42 contains the firmware version number.

The penultimate slot: slot 41 is used by the “moody f” series to identify the programmed fade rate. For those users wishing to programme an accurate fade time – the following table allows you to do so:

Slot 41Time (mins)
00.50
11.00
21.50
32.00
42.50
53.00
63.50
74.00
84.50
95.00
105.50
116.00
126.50
137.00
147.50
158.00
168.50
179.00
189.50
1910.00
2010.50
2111.00
2211.50
2312.00
2412.50
2513.00
2613.50
2714.00
2814.50
2915.00
3015.50
3116.00
3216.50
3317.00
3417.50
3518.00
3618.50
3719.00
3819.50
3920.00
4020.50
4121.00
4221.50
4322.00
4422.50
4523.00
4623.50
4724.00
4824.50
4925.00
5025.50
5126.00
5226.50
5327.00
5427.50
5528.00
5628.50
5729.00
5829.50
5930.00
6030.50
6131.00
6231.50
6332.00
6432.50
6533.00
6633.50
6734.00
6834.50
6935.00
7035.50
7136.00
7236.50
7337.00
7437.50
7538.00
7638.50
7739.00
7839.50
7940.00
8040.50
8141.00
8241.50
8342.00
8442.50
8543.00
8643.50
8744.00
8844.50
8945.00
9045.50
9146.00
9246.50
9347.00
9447.50
9548.00
9648.50
9749.00
9849.50
9950.00
10050.50
10151.00
10251.50
10352.00
10452.50
10553.00
10653.50
10754.00
10854.50
10955.00
11055.50
11156.00
11256.50
11357.00
11457.50
11558.00
11658.50
11759.00
11859.50
11960.00
12060.50
12161.00
12261.50
12362.00
12462.50
12563.00
12663.50
12764.00
12864.50
12965.00
13065.50
13166.00
13266.50
13367.00
13467.50
13568.00
13668.50
13769.00
13869.50
13970.00
14070.50
14171.00
14271.50
14372.00
14472.50
14573.00
14673.50
14774.00
14874.50
14975.00
15075.50
15176.00
15276.50
15377.00
15477.50
15578.00
15678.50
15779.00
15879.50
15980.00
16080.50
16181.00
16281.50
16382.00
16482.50
16583.00
16683.50
16784.00
16884.50
16985.00
17085.50
17186.00
17286.50
17387.00
17487.50
17588.00
17688.50
17789.00
17889.50
17990.00
18090.50
18191.00
18291.50
18392.00
18492.50
18593.00
18693.50
18794.00
18894.50
18995.00
19095.50
19196.00
19296.50
19397.00
19497.50
19598.00
19698.50
19799.00
19899.50
199100.00
200100.50
201101.00
202101.50
203102.00
204102.50
205103.00
206103.50
207104.00
208104.50
209105.00
210105.50
211106.00
212106.50
213107.00
214107.50
215108.00
216108.50
217109.00
218109.50
219110.00
220110.50
221111.00
222111.50
223112.00
224112.50
225113.00
226113.50
227114.00
228114.50
229115.00
230115.50
231116.00
232116.50
233117.00
234117.50
235118.00
236118.50
237119.00
238119.50
239120.00
240120.50
241121.00
242121.50
243122.00
244122.50
245123.00
246123.50
247124.00
248124.50
249125.00
250125.50
251126.00
252126.50
253127.00
254127.50
255128.00
Posted on

versaSplit: Part number reference

The versaSplit range provides a very flexible solution to DMX distribution. The number of product configurations runs to millions and so not every configuration is available from stock, but is built to order. The following guide is an overview of how to generate the part code.

There are four base units:

  • “mini” – vSplit mini (Desk / truss mount. 1 input module. 6 outputs. Ground referenced).
  • “mono” – vSplit mono (19 ” rack. 1 input module. 10 outputs. Ground referenced).
  • “duo” – vSplit duo (19 ” rack. 2 input modules. 8 outputs. Ground referenced).
  • “iso” – vSplit iso (19 ” rack. 1 input module. 8 outputs. Isolated outputs).

There are seven codes for the input modules:

There are three output connector options:

  • “3” – XLR 3 pin
  • “5” – XLR 5 pin
  • “8” – XLR 8 pin ethcon

If all output connectors are the same, just one number is needed.

The part number is constructed as follows:

vSplit “base unit” “input A module” – “Output connectors” – “input B module”.

Examples.

  • The part number for a vSplit mono with a 5 pin XLR input and all 5 pin XLR outputs is: vSplit mono xlr5-5.
  • The part number for a vSplit mono with a 3 pin XLR input and all 3 pin XLR outputs is: vSplit mono xlr3-3.
  • The part number for a vSplit mono with a 5 pin XLR input and all 3 pin XLR outputs is: vSplit mono xlr5-3.
  • The part number for a vSplit mono with a 5 pin XLR input and outputs 1-4 with 3 pin, outputs 5-8 with 5 pin and outputs 9-10 with ethcon is: vSplit mono xlr5-3333555588.
  • The part number for a vSplit duo with a 5 pin XLR input module and a blanking plate for the second input and all 5 pin XLR outputs is: vSplit duo xlr5-5-x.
  • The part number for a vSplit duo with a 5 pin XLR input module and a CRMX input module and outputs 1-4 with 3 pin, outputs 5-8 with 5 pin is: vSplit duo xlr5-33335555-crmx.

The table below shows the common vSplit mono and iso configurations.

Input moduleversaSplit mono XLR3versaSplit mono XLR5versaSplit mono XLR8versaSplit iso XLR3versaSplit iso XLR5versaSplit iso XLR8
EmptyvSplit mono x-3vSplit mono x-5vSplit mono x-8vSplit iso x-3vSplit iso x-5vSplit iso x-8
XLR3vSplit mono xlr3-3vSplit mono xlr3-5vSplit mono xlr3-8vSplit iso xlr3-3vSplit iso xlr3-5vSplit iso xlr3-8
XLR5vSplit mono xlr5-3vSplit mono xlr5-5vSplit mono xlr5-8vSplit iso xlr5-3vSplit iso xlr5-5vSplit iso xlr5-8
XLR8vSplit mono xlr8-3vSplit mono xlr8-5vSplit mono xlr8-8vSplit iso xlr8-3vSplit iso xlr8-5vSplit iso xlr8-8
CRMXvSplit mono crmx-3vSplit mono crmx-5vSplit mono crmx-8vSplit iso crmx-3vSplit iso crmx-5vSplit iso crmx-8
ETHBvSplit mono ethb-3vSplit mono ethb-5vSplit mono ethb-8vSplit iso ethb-3vSplit iso ethb-5vSplit iso ethb-8

The table below shows the common vSplit mini configurations. Please note that vSplit mini is only offered with XLR5 output connectors.

Input moduleversaSplit mini XLR5
EmptyvSplit mini x-5
XLR3vSplit mini xlr3-5
XLR5vSplit mini xlr5-5
XLR8vSplit mini xlr8-5
CRMXvSplit mini crmx-5
ETHBvSplit mini ethb-5

The table below shows the common vSplit duo configurations.

Input A moduleInput B moduleversaSplit duo XLR3versaSplit duo XLR5versaSplit duo XLR8
BlankBlankvSplit duo b-3-bvSplit duo b-5-bvSplit duo b-8-b
XLR3BlankvSplit duo xlr3-3-bvSplit duo xlr3-5-bvSplit duo xlr3-8-b
XLR5BlankvSplit duo xlr5-3-bvSplit duo xlr5-5-bvSplit duo xlr5-8-b
XLR8BlankvSplit duo xlr8-3-bvSplit duo xlr8-5-bvSplit duo xlr8-8-b
CRMXBlankvSplit duo crmx-3-bvSplit duo crmx-5-bvSplit duo crmx-8-b
ETHBBlankvSplit duo ethb-3-bvSplit duo ethb-5-bvSplit duo ethb-8-b
BlankXLR3vSplit duo b-3-xlr3vSplit duo b-5-xlr3vSplit duo b-8-xlr3
XLR3XLR3vSplit duo xlr3-3-xlr3vSplit duo xlr3-5-xlr3vSplit duo xlr3-8-xlr3
XLR5XLR3vSplit duo xlr5-3-xlr3vSplit duo xlr5-5-xlr3vSplit duo xlr5-8-xlr3
XLR8XLR3vSplit duo xlr8-3-xlr3vSplit duo xlr8-5-xlr3vSplit duo xlr8-8-xlr3
CRMXXLR3vSplit duo crmx-3-xlr3vSplit duo crmx-5-xlr3vSplit duo crmx-8-xlr3
ETHBXLR3vSplit duo ethb-3-xlr3vSplit duo ethb-5-xlr3vSplit duo ethb-8-xlr3
BlankXLR5vSplit duo b-3-xlr5vSplit duo b-5-xlr5vSplit duo b-8-xlr5
XLR3XLR5vSplit duo xlr3-3-xlr5vSplit duo xlr3-5-xlr5vSplit duo xlr3-8-xlr5
XLR5XLR5vSplit duo xlr5-3-xlr5vSplit duo xlr5-5-xlr5vSplit duo xlr5-8-xlr5
XLR8XLR5vSplit duo xlr8-3-xlr5vSplit duo xlr8-5-xlr5vSplit duo xlr8-8-xlr5
CRMXXLR5vSplit duo crmx-3-xlr5vSplit duo crmx-5-xlr5vSplit duo crmx-8-xlr5
ETHBXLR5vSplit duo ethb-3-xlr5vSplit duo ethb-5-xlr5vSplit duo ethb-8-xlr5
BlankXLR8vSplit duo b-3-xlr8vSplit duo b-5-xlr8vSplit duo b-8-xlr8
XLR3XLR8vSplit duo xlr3-3-xlr8vSplit duo xlr3-5-xlr8vSplit duo xlr3-8-xlr8
XLR5XLR8vSplit duo xlr5-3-xlr8vSplit duo xlr5-5-xlr8vSplit duo xlr5-8-xlr8
XLR8XLR8vSplit duo xlr8-3-xlr8vSplit duo xlr8-5-xlr8vSplit duo xlr8-8-xlr8
CRMXXLR8vSplit duo crmx-3-xlr8vSplit duo crmx-5-xlr8vSplit duo crmx-8-xlr8
ETHBXLR8vSplit duo ethb-3-xlr8vSplit duo ethb-5-xlr8vSplit duo ethb-8-xlr8
BlankCRMXvSplit duo b-3-crmxvSplit duo b-5-crmxvSplit duo b-8-crmx
XLR3CRMXvSplit duo xlr3-3-crmxvSplit duo xlr3-5-crmxvSplit duo xlr3-8-crmx
XLR5CRMXvSplit duo xlr5-3-crmxvSplit duo xlr5-5-crmxvSplit duo xlr5-8-crmx
XLR8CRMXvSplit duo xlr8-3-crmxvSplit duo xlr8-5-crmxvSplit duo xlr8-8-crmx
CRMXCRMXvSplit duo crmx-3-crmxvSplit duo crmx-5-crmxvSplit duo crmx-8-crmx
ETHBCRMXvSplit duo ethb-3-crmxvSplit duo ethb-5-crmxvSplit duo ethb-8-crmx
BlankETHBvSplit duo b-3-ethbvSplit duo b-5-ethbvSplit duo b-8-ethb
XLR3ETHBvSplit duo xlr3-3-ethbvSplit duo xlr3-5-ethbvSplit duo xlr3-8-ethb
XLR5ETHBvSplit duo xlr5-3-ethbvSplit duo xlr5-5-ethbvSplit duo xlr5-8-ethb
XLR8ETHBvSplit duo xlr8-3-ethbvSplit duo xlr8-5-ethbvSplit duo xlr8-8-ethb
CRMXETHBvSplit duo crmx-3-ethbvSplit duo crmx-5-ethbvSplit duo crmx-8-ethb
ETHBETHBvSplit duo ethb-3-ethbvSplit duo ethb-5-ethbvSplit duo ethb-8-ethb
Posted on

Micro-Scope: Adding a fixture

Most customers use Mic-Edit to create their own fixtures when required. However Artistic Licence does release occasional updates to the library. You can make requests using the following application form.

Additionally, if you have created fixtures you would like to share with other users, send the file to Support@ArtisticLicence.com.

 

Mic-Edit fixture request:

Fixture Manufacturer:

Fixture Name:

Fixture User Guide URL:

Footprint (number of channels used):

 

ChannelFunctionDefault Value
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
Posted on

dVnet: Using dual-NIC configuration

dVnet has the ability to operate as a network translator / soft-patch. This can be done using one or two network cards.

The input protocol is always Art-Net and the output protocol can be selected between Art-Net, KiNet and sACN. This example describes how to translate Art-Net to KiNet on separate network cards. The Art-Net is assumed to be in the standard 2.x.y.z IP range with a subnet mask of 255.0.0.0. The lighting console generating the Art-Net should be set to broadcast, the input network NIC of dVnet should be set to an IP address of, for example, 2.0.0.100.

Assuming that the KiNet is to output on the 192.168.10.x range (subnet 255.255.255.0) the output Nic should be set to an IP address of, for example, 192.168.10.100.

In dVnet, the output Nic must be selected as the active NIC in the driver window.

The attached files can be loaded to provide detail of the method by which the patch is set. In the first example, Art-Net is received on Pipes 101-110 and converted to KiNet Port Out protocol on pipes 1-10. These are unicast to 192.168.10.1 through 192.168.10.10

Posted on

Rail-DALI-DMX: Power cycle and fault conditions

Users who are more familiar with DMX512 than DALI can find the way DALI ballasts respond to power cycle or fault conditions confusing. A key difference between DMX512 and DALI is that DMX512 is continuously refreshing whereas DALI is not.

When a DMX512 fixture is power cycled it will immediately take the DMX512 level data. When a DALI ballast is power cycled it will go to a pre-programmed level called “POWER ON LEVEL”. It will stay at that level until a new DALI level command is sent. DALI-Scope can be used to both read and programme the ballast’s “POWER ON LEVEL”.

When a DALI ballast detects a fault, such as a brown out of the DALI BUS POWER SUPPLY it will go to a pre-programmed level called “SYSTEM FAILURE LEVEL”. It will stay at that level until a new DALI level command is sent. Dali-Scope can be used to read the ballast’s “SYSTEM FAILURE LEVEL”.

Posted on

Dali-Scope: Adding a ballast to an existing system

It is sometimes necessary to add a new ballast to an existing installation. Usually you will want to do this without changing the short addresses of the existing ballasts.

To do this you need to isolate the new ballast from the existing network prior to commissioning with Dali-Scope. This means that you should connect the new DALI ballast, the bus power supply and Dali-Scope together. If the new ballast has previously been assigned a short address, simply change the short address to the preferred address using Dali-Scope. If the ballast is in factory default state, run an “Automatic channel discovery”. This process will assign short address 1 to the ballast. Then change the short address to the preferred value prior to connecting it to the ballast network.

You can then connect the new ballast to the existing network.

Posted on

Art-Net: Resetting a product’s IP address

Our gateway products, which include artLynx duo, artLynx quad, artLynx RJ45, netLynx quad and dataLynx II all have a factory reset switch. To reset to factory defaults, hold down the switch and cycle the power. Once you have reset to the factory default, the IP address will change. See Art-Net: Finding the IP Address of a product

The IP address of legacy Artistic Licence network products can be reset to factory default using the front panel controls as described below:

ProductIP Reset Procedure
AL5001A
AL5002A
Data-Lynx O/PB
Data-Lynx I/PB
Data-Lynx IO/PB
Down-LynxA
Up-LynxA
Net-Lynx O/PA
Net-Lynx I/PA
Cata-Lynx I/PA
Cata-Lynx O/PA
Ether-Lynx IIB
Art-Lynx O/PA
Art-Lynx I/PA
Art-PipeB
Art-RelayB
Multichrome E1 & E2A

A: Set Sub-Net wheel and both Universe wheels to F, power off, power on.

B: Set Sub-Net wheel to 9, power off, power on, power off, set Sub-Net wheel to F, power on.

Posted on

Rail-DALI-DMX: Quick start

Often a customer simply wishes to use Rail-DALI-DMX to convert a DALI channel to DMX. The following instructions allow this:

  • Open the top cover to access the DIP switches.
  • Set Switch-6 to off. This puts product in ballast mode.
  • Set Switch-3 and Switch-4 to off – this tells the product to emulate a single DALI ballast.
  • Connect the DALI input to your DALI controller and start discovery. Your DALI controller will discover one new ballast which you should address to a free short address – this is your virtual DALI address. (Your controller may do that automatically).
  • Connect the DMX output to your DMX receiver.
  • Any intensity changes sent to the virtual DALI address will appear on channel 1 of the DMX output.
Posted on

Jump-Start: Firmware Upload

From time to time, new firmware is released for Jump-Start. The latest version can be downloaded here. It is not necessary to return Jump-Start for upgrade – it can be done in the field. This is achieved by connecting Jump-Start to an Artistic Licence Art-Net node such as artLynxDMX-Workshop can then be used for the upgrade.

Please follow the following procedure:

  1. Ensure Jump-Start is set to ‘RDM Standard’ and not ‘DRAFT’. This can be found in the setup menu.
  2. Put the Jump-Start in firmware upload mode. This is done by pressing the left and right arrow keys at the same time.
  3. The right-side LED will light to confirm upload mode is active.
  4. Connect the Jump-Start to the Art-Net node.
  5. Download the latest firmware (see link above) and copy file to: C:\Program Files (x86)\Artistic Licence\DMX-Workshop\Firmware.
  6. Select the network list in DMX-Workshop and wait for Jump-Start to be discovered as a node.
  7. Upload the firmware to the Jump-Start by right-clicking in RDM information area and following the options to upload firmware.
Posted on

DMX-Workshop: Installation

DMX-Workshop is our free-of-charge Windows application for monitoring and configuring Art-Net devices. The software requires Administrator permission to run. The installer for DMX-Workshop will attempt to auto-enable this for you, but it may fail depending on the configuration of your PC and your security settings.

To achieve manually, right-click the DMX-Workshop icon and select ‘run as administrator’. The right-click menu also accesses the properties dialogue which allows you to select DMX-Workshop to always run as administrator.

Posted on

DALI: An introduction

Artistic Licence offers a number of products used to convert and manage DALI.

Rail-DALI-DMX converts DALI to DMX512 and Rail-DMX-DALI converts to DMX to DALI.

There is a very large speed difference between DMX512 and DALI which means that care must be taken when designing a lighting installation which converts the between them.

This link offers a primer on DALI and discusses some of the pitfalls.

Posted on

dVnet: Importing from Excel

You’ll find the import from CSV button in the Pixel Map tab. From here the process of importing a properly formatted CSV is straight forward. You just need to find and open your pre-existing CSV file. Please note that you must not have the file open in any other applications (Excel or NotePad) as the import will not work.

In order to make a dVnet CSV file you need to have the following line as the first line of the file. Attached is an example which can be used with the example show which installs with dVnet.

Name, Type, X, Y, Width, Height, Fixture #, Pixel #, Pipe, Start, Footprint, Red slot, Grn slot, Blu slot, Yel slot, Wht slot, Int slot, Group.

Each subsequent line of the CSV file will be a single pixel within your map.

  • Name is required though this can just be a number
  • Type would be the type of fixture this pixel is in – optional
  • X & are the co-ordinates that this pixel will take on your map
  • Width and Height are the relative size of this pixel
  • Fixture this will be a number representing the fixture that this pixel is a part of
  • Pixel # represents which pixel this is within its fixture. As all the fixtures in the example file only contain a single pixel this number will always be 1. However if you are using a fixture with 4 LEDs this would be between 1 and 4.
  • Pipe see the notes below on pipes
  • Start is this pixels DMX address
  • Footprint is the number of DMX slots this pixel occupies
  • Red slot which of the slots for this pixel contains data for the red channel (typically 1)
  • Grn slot which of the slots for this pixel contains data for the green channel (typically 2)
  • Blu slot which of the slots for this pixel contains data for the blue channel (typically 3)
  • Yel slot which of the slots for this pixel contains data for the yellow channel (typically 0 for RGB pixels)
  • Wht slot which of the slots for this pixel contains data for the white channel (typically 0 for RGB pixels)
  • Int slot which of the slots for this pixel contains data for the intensity channel (typically 0 for RGB pixels)
  • Group is optional

Please note that we have implemented a ‘pipe-centric’ way of patching pixels. When patching pixels you first select the pipe that the fixture is on (between 1 and 300) then the fixtures start address which will be its DMX address between 1 and 512.

By default each pipe is patched 1 to 1 with its respective universe and will unicast as Art-Net. However you can patch a pipe to any Art-Net or sACN universe using the ‘Pipe patch’ tab.

Lastly there is an export to dVnet function within the latest release of Colour-Tramp.

Posted on

Art-Net: Finding the IP Address of a product

There are three methods for finding the IP address of an Art-Net product:

    • Connect using DMX-Workshop, this will display the product in a network list along with its IP address. DMX-Workshop can be downloaded from here.
    • Ping: Open a command line window and use the ping command. If the products are on the normal Art-Net address range, type: “ping 2.255.255.255”. This approach is best on a Mac as Macs do not support net-bios.
    • Perform a net-bios search (Windows only). To do this, connect the product to your laptop’s network, open browser and type in the net-bios name of the product you are using (see below). Occasionally the net-bios cache in the browser gets out of date. To flush the cache and restart, type the following in the browser window: nbtstat -R

Current Products (product code – net-bios name)

  • oemGate quad – oemGatequad
  • rackLynx octo – rackLynx
  • daliGate quad – daliGatequad
  • netLynx quad – netLynxquad
  • dataLynx II – dataLynxII
  • artLynx duo – artLynxduo
  • artLynx quad – artLynxquad
  • artLynx RJ45 – artLynxRJ45
  • versaSplit EthB – VersaEtherB

Legacy Products (product code – net-bios name)

  • Data-Lynx O/P – DATALYNXOP
  • Data-Lynx I/P – DATALYNXIP
  • Data-Lynx I/OP – DATALYNXIO
  • Down-Lynx – DownLynx
  • Up-Lynx – UpLynx
  • Net-Lynx O/P – NetLynxOp
  • Net-Lynx I/P – NetLynxIp
  • Cata-Lynx I/P – CataLynxIp
  • Cata-Lynx O/P – CataLynxOp
  • Ether-Lynx II – EtherLynxII
  • Art-Lynx O/P – ArtLynxOp
  • Art-Lynx I/P – ArtLynxIp
  • Art-Pipe – ArtPipe
  • Art-Relay – ArtRelay
  • Multichrome E2 – E2MultiChrome
  • Eaton / Cooper Controls EN2RDM – EN2RDM
  • Eaton / Cooper Controls EN8RDM – EN8RDM
  • Thorn SensaDMX – SENSAEDMX
  • Lex Products LexNet – LEXNET