Lesson 24 Tut3: Difference between revisions

From English DMXC-Wiki
No edit summary
No edit summary
Line 10: Line 10:
}}
}}
==Overview==
==Overview==
In this lesson we look at how we can combine the advantages of DMXControl, release 3 with those of release 2 by connecting the tools via ArtNet.
In this lesson we look at how we can combine the advantages of DMXControl release 3, with those of release 2, by connecting the tools via ArtNet.


= Lesson24: Transferring DMX values ​​over Artnet to DMXControl 2 =
= Lesson24: Transferring DMX values ​​over Artnet to DMXControl 2 =
Line 19: Line 19:




Since DMXControl 3 still is in an early stage, some functions of the series 2 does not yet exist. This will be improved in the future, but it will still take some time before all the functions of the series 2 are present.
Since DMXControl 3 still is in an early stage, some functions of the series 2 do not yet exist. This will be improved in the future, but it will take some time before all the functions of the series 2 are present. Nevertheless, we do not want to miss the advantages when using release 3. This section shows how a connection can be made from DMXControl 3 ​​to DMXControl 2 via ArtNet.
 
 
Nevertheless, we do not want to miss the advantages when using release 3. This section shows how a connection can be made from DMXControl 3 ​​to DMXControl 2 via ArtNet.




Line 30: Line 27:




Important here are the settings '''SubNet''' and for '''input node''' the '''Universe'''. We will configure DMXControl 3 in this way, that it transmits our desired values in the subnet 0 in the universe 0.
Important here are the settings '''SubNet''' and for '''input node''' the '''Universe'''. We will configure DMXControl 3 in this way, so that it transmits our desired values in the subnet 0 in the universe 0.


The setting'' 'Universe''' in '''output node''' does not matter and can (if required) be freely selected.  
The setting'' 'Universe''' in '''output node''' does not matter, and can (if required) be freely selected. But it must differ from the'' 'Universe''' of the input node, otherwise we get (in this configuration), a feedback loop, and DMXControl is no longer operable. In our configuration, the universe 8 is the next free universe.
But it must differ from the'' 'Universe''' of the input node, otherwise we get (in this configuration), a feedback loop, and DMXControl is no longer operable. In our configuration, the universe 8 is the next free universe.




We close the window by clicking OK and activate the output plugin by setting the hook before the name of the interface:
Close the window by clicking OK and activate the output plugin by checking the box in front of the name of the interface:
{{Bild_mit_Unterschrift |2.12_Ausgabeplugin.PNG|2|Ausgabepluginverwaltung DMXControl 2|center|400px}}
{{Bild_mit_Unterschrift |2.12_Ausgabeplugin.PNG|2|Ausgabepluginverwaltung DMXControl 2|center|400px}}




DMXControl 2 is now ready to receive ArtNet data. In the next step we need to bring DMXControl 3 for sending its DMX output via Artnet. At '''Settings--> DMX Interfaces''' we find the output plugins of DMXControl 3:
DMXControl 2 is now ready to receive ArtNet data. In the next step we need to configure DMXControl 3 to send its DMX output via Artnet. At '''Settings--> DMX Interfaces''' we find the output plugins of DMXControl 3:


{{Bild_mit_Unterschrift |3.0_Ausgabeplugin.PNG‎|3|Ausgabepluginverwaltung DMXControl 3|center|600px}}
{{Bild_mit_Unterschrift |3.0_Ausgabeplugin.PNG‎|3|Ausgabepluginverwaltung DMXControl 3|center|600px}}
Line 49: Line 45:




In simple configurations the ArtNet transmitter is running now. But to be sure we configure the ArtNet plugin still on the correct network interface. By clicking on '''Advanced Interface Settings ...''' we come to the configuration dialog. We are interested in the '''binding to''' entry.
In simple configurations the ArtNet transmitter is now running. But to be sure, configure the ArtNet plugin still on the correct network interface. By clicking on '''Advanced Interface Settings ...''' we come to the configuration dialog. We are interested in the '''binding to''' entry.


Here we need to select the IP address of our computer, which is typically located in the same network as the computer with our DMXControl 2 installation:
Here we need to select the IP address of our computer, which is typically located in the same network as the computer with our DMXControl 2 installation:
Line 56: Line 52:




If you start in DMXControl 2 now the DMX remote control (Window -> DMXin remote control) and change in '''Channel Overview''' of DMXControl 3 a value, it should be displayed on the DMXin remote control:
If you start in DMXControl 2 and go to the DMX remote control (Window -> DMXin remote control) then change a value in '''Channel Overview''' of DMXControl 3, it should be displayed on the DMXin remote control:


{{Bild_mit_Unterschrift |ErsterArtNetTest.PNG‎|6|Verbindung überprüfen DMXControl3 -> DMXControl 2|center|450px}}
{{Bild_mit_Unterschrift |ErsterArtNetTest.PNG‎|6|Verbindung überprüfen DMXControl3 -> DMXControl 2|center|450px}}




This window must remain open for further operating!
This window must remain open to continue operating!
Now we just need to patch the DMXin remote control of DMXControl 2 properly. About '''Configuration -> DMXin Remote control ...''' we get the configuration screen:
Now we just need to patch the DMXin remote control of DMXControl 2 properly. If you go to '''Configuration -> DMXin Remote control ...''' we get the configuration screen:
{{Bild_mit_Unterschrift |2_12DMXIn-Konfig.png‎|7|Aufrufen der DMXIn Konfiguration in DMXControl 2|center|300px}}
{{Bild_mit_Unterschrift |2_12DMXIn-Konfig.png‎|7|Aufrufen der DMXIn Konfiguration in DMXControl 2|center|300px}}




Here you could now control commands of DMXControl 2. We would like first of all patch all channels from ArtNet input of DMXControl 2 to DMX output. For this, we click at the right, still empty soft patch list '''1:1''':
Here you can now control commands in DMXControl 2. First of all, we would like to patch all channels from ArtNet input in DMXControl 2 to DMX output. For this, we click at the right, in the still empty soft patch list '''1:1''':
{{Bild_mit_Unterschrift |Softpatch212.PNG‎|8|Konfiguration DMXIn Fernbedienung mit Softpatch DMXControl 2|center|600px}}
{{Bild_mit_Unterschrift |Softpatch212.PNG‎|8|Konfiguration DMXIn Fernbedienung mit Softpatch DMXControl 2|center|600px}}




In the following dialogues we select the desired range of values​​. I decided to patch the entire DMX universe:
In the following dialogues, we select the desired range of values​​. I decided to patch the entire DMX universe:
{{Bild_mit_Unterschrift |1zu1Patch212.PNG‎|9|Softpatch von Start-DMX-Adresse bis End-DMX-Adresse DMXControl 2|center|600px}}
{{Bild_mit_Unterschrift |1zu1Patch212.PNG‎|9|Softpatch von Start-DMX-Adresse bis End-DMX-Adresse DMXControl 2|center|600px}}


Line 82: Line 78:
Now all values ​​of DMXin are directly sent to the DMXOut interface.
Now all values ​​of DMXin are directly sent to the DMXOut interface.


You can test the connection e.g. by sending color gradient from DMXControl 3 to DMXControl 2. With this workaround we extend the functionality of DMXContro 2 with features from DMXControl 3.
You can test the connection by sending color gradient from DMXControl 3 to DMXControl 2. With this workaround, we extend the functionality of DMXControl 2 with features from DMXControl 3.


===Error handling===
===Error handling===




If  no DMXin values ​​of the remote control are shown, there is still a fault with the network configuration, so please check the following points:
If  no DMXin values ​​from the remote control are shown, there is still a fault with the network configuration. Please check the following points:
* Are the computers in the same network, can the computers ping each other?
* Are the computers in the same network? Can the computers ping each other?
* switch off firewalls (for test only), because the often block UDP data (ArtNet is based on UDP)
* Switch off firewalls (for test only), because the often block UDP data (ArtNet is based on UDP)
* Are both DMXControl plug-ins configured on the same subnet?
* Are both DMXControl plug-ins configured on the same subnet?
* Is DMXControl 2 configured for the same universe as a receiver, on which DMXControl 3 sends data?
* Is DMXControl 2 configured for the same universe as a receiver, on which DMXControl 3 sends data?
Line 96: Line 92:




==Excercise==
==Exercise==
* Configure the connection between DMXControl 3 and DMXControl 2
* Configure the connection between DMXControl 3 and DMXControl 2
* Test the color gradient example mentioned above
* Test the color gradient example mentioned above

Revision as of 12:40, 11 April 2013

[[File:{{{Logo}}}|48px|link=]] {{{Pagetitle}}}


Arrow back.png Lesson 23
Appendix 1 Arrow forw.png
table of content

Overview

In this lesson we look at how we can combine the advantages of DMXControl release 3, with those of release 2, by connecting the tools via ArtNet.

Lesson24: Transferring DMX values ​​over Artnet to DMXControl 2

 Important Hint This lesson works in if you are using Win XP or Win 7. Win 8 has more problems, but it is possible to make it work.


Since DMXControl 3 still is in an early stage, some functions of the series 2 do not yet exist. This will be improved in the future, but it will take some time before all the functions of the series 2 are present. Nevertheless, we do not want to miss the advantages when using release 3. This section shows how a connection can be made from DMXControl 3 ​​to DMXControl 2 via ArtNet.


We start with the configuration of DMXControl 2 for receiving ArtNet data. For this, we choose in the taskbar of DMXControl 2 Configuration -> Output Plugins .... We go to the output plugin dialog in which we configure the "ArtNet Plugin" by clicking "Configure Selected Plugin":

Template:Bild mit Unterschrift


Important here are the settings SubNet and for input node the Universe. We will configure DMXControl 3 in this way, so that it transmits our desired values in the subnet 0 in the universe 0.

The setting 'Universe in output node does not matter, and can (if required) be freely selected. But it must differ from the 'Universe of the input node, otherwise we get (in this configuration), a feedback loop, and DMXControl is no longer operable. In our configuration, the universe 8 is the next free universe.


Close the window by clicking OK and activate the output plugin by checking the box in front of the name of the interface: Template:Bild mit Unterschrift


DMXControl 2 is now ready to receive ArtNet data. In the next step we need to configure DMXControl 3 to send its DMX output via Artnet. At Settings--> DMX Interfaces we find the output plugins of DMXControl 3:

Template:Bild mit Unterschrift


With Add Interface ...we now select the ArtNet plugin: Template:Bild mit Unterschrift


In simple configurations the ArtNet transmitter is now running. But to be sure, configure the ArtNet plugin still on the correct network interface. By clicking on Advanced Interface Settings ... we come to the configuration dialog. We are interested in the binding to entry.

Here we need to select the IP address of our computer, which is typically located in the same network as the computer with our DMXControl 2 installation:

Template:Bild mit Unterschrift


If you start in DMXControl 2 and go to the DMX remote control (Window -> DMXin remote control) then change a value in Channel Overview of DMXControl 3, it should be displayed on the DMXin remote control:

Template:Bild mit Unterschrift


This window must remain open to continue operating! Now we just need to patch the DMXin remote control of DMXControl 2 properly. If you go to Configuration -> DMXin Remote control ... we get the configuration screen: Template:Bild mit Unterschrift


Here you can now control commands in DMXControl 2. First of all, we would like to patch all channels from ArtNet input in DMXControl 2 to DMX output. For this, we click at the right, in the still empty soft patch list 1:1: Template:Bild mit Unterschrift


In the following dialogues, we select the desired range of values​​. I decided to patch the entire DMX universe: Template:Bild mit Unterschrift

Template:Bild mit Unterschrift


By clicking on 'OK' now we have to activate the DMXin remote control: Template:Bild mit Unterschrift


Now all values ​​of DMXin are directly sent to the DMXOut interface.

You can test the connection by sending color gradient from DMXControl 3 to DMXControl 2. With this workaround, we extend the functionality of DMXControl 2 with features from DMXControl 3.

Error handling

If no DMXin values ​​from the remote control are shown, there is still a fault with the network configuration. Please check the following points:

  • Are the computers in the same network? Can the computers ping each other?
  • Switch off firewalls (for test only), because the often block UDP data (ArtNet is based on UDP)
  • Are both DMXControl plug-ins configured on the same subnet?
  • Is DMXControl 2 configured for the same universe as a receiver, on which DMXControl 3 sends data?
  • No other sender configured in this universe?


Exercise

  • Configure the connection between DMXControl 3 and DMXControl 2
  • Test the color gradient example mentioned above

Next Lesson: RGB Matrix



Arrow back.png Lesson 23
Appendix 1 Arrow forw.png
table of content