No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Chaptertitle_DMXC}}<br> | {{Chaptertitle_DMXC}}<br> | ||
{{Inuse}}<br> | {{Inuse}}<br> | ||
{{Hint|25.10.2013: UPrenner: create the article | {{Hint|25.10.2013: UPrenner: create the article page01.11.2013 UPrenner: work-in-progress<br> | ||
<!--01.11.2013: UPrenner article ready, just update of pictures<br>'''If you are a native speaker, please Help us and review this--> | <!--01.11.2013: UPrenner article ready, just update of pictures<br>'''If you are a native speaker, please Help us and review this--> | ||
}}<br> | }}<br> | ||
| Line 12: | Line 12: | ||
{{Start-LaTeX}} | {{Start-LaTeX}} | ||
==Overview== | ==Overview== | ||
The PDA remote control has developed from the terminal interface of DMXControl over the serial remote control. By the « PDA remote control » DMXControl can ( telnet, COM interface, Bluetooth or about WLAN ) head with PDA and other serial interfaces. | |||
{{ BoxImportant| Text= | {{ BoxImportant| Text=The window of the PDA remote control must remain open as in the case of all other remote controls/controls in DMXControl. No communication takes place at closed window.}} | ||
==Description== | ==Description== | ||
This one « Serial remote control » did you implement in DMXControl to make the access about a serial interface or network (Ethernet) to the program possible. DMXControl expects a connection in the Netwerk on port 2145. This one can this port in the window « PDA remote control » being changed. Any program which can send character strings (strings) out is able to radioguide DMXControl with that. | |||
This one « Serial remote control » among other things android is (e.g. ) uses of the PDA control [[PDA_2_DMXC]] and of the web interface or the PHP class as well as different other controls. | |||
Since the protocol of the interface is open, it is possible for everybody to access DMXControl about a program of one's own. | |||
The interface works bidirectionally, i. e. data can be sent and made an enquiry about. A table of the possible orders can be found below. Some orders don't return a value other after executing as a confirmation. | |||
To DMXControl every order is sent to it, n must with a line break (in Java and C # "") be completed. | |||
==Port== | ==Port== | ||
A list of the commands and answers are listed by DMXControl into table following this one. Developers who would like to write an external program for DMXControl's control can make first experiences the best with a terminal program like telnet or Putty. This goes with the order at local work: '''telnet 127. 0. 0. 1 2145'''. One then immediately recognizes what the answers look. All commands are interpreted by great/use of small initial letters independently of DMXControl. | |||
{{ BoxHint | {{ BoxHint | ||
| Text= | | Text=Instead of '''SetChannel''', so '''sEtChAnNeL''' also can be written to. | ||
}} | }} | ||
The abbreviation '''CV''' stands '''for ChannelValueChanged''' for '''ChannelValue''' and '''CVC''' | |||
{|cellpadding="5" cellspacing="0" border="1" | {|cellpadding="5" cellspacing="0" border="1" | ||
|''' | |'''Enquiry to DMXC''' | ||
|''' | |'''Answer from DMXC''' | ||
|''' | |'''Description''' | ||
|''' | |'''Example''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|SetChannel ''Channel | |SetChannel ''Channel value'' | ||
|CV ''Channel | |CV ''Channel value'' | ||
| | |Set the '''''Channel''''' on the '''''Wert'''''. | ||
|'''SetChannel 1 200''' -> '''CV 1 200''' | |'''SetChannel 1 200''' -> '''CV 1 200''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|SC ''Channel Wert'' | |SC ''Channel Wert'' | ||
|CV ''Channel Wert'' | |CV ''Channel Wert'' | ||
| | |Short notation for SetChannel. | ||
|'''SC 1 200''' -> '''CV 1 200''' | |'''SC 1 200''' -> '''CV 1 200''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|GetChannel ''Channel'' | |GetChannel ''Channel'' | ||
|CV ''Channel | |CV ''Channel value'' | ||
| | |Ask the value of the channel '''''Channel'''''. | ||
|'''GetChannel 1''' -> '''CV 1 200''' | |'''GetChannel 1''' -> '''CV 1 200''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|GC ''Channel'' | |GC ''Channel'' | ||
|CV ''Channel | |CV ''Channel value'' | ||
| | |Short notation for GetChannel. | ||
|'''GC 1''' -> '''CV 1 200''' | |'''GC 1''' -> '''CV 1 200''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|GetAllDevices | |GetAllDevices | ||
|'' | |''List of Devices'' | ||
| | |Question on all devices available in DMXControl. | ||
|'''GetAllDevices''' -> | |'''GetAllDevices''' -> | ||
'''1. PAR-1''' | '''1. PAR-1''' | ||
| Line 71: | Line 71: | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|GetDeviceInfo ''DeviceID'' | |GetDeviceInfo ''DeviceID'' | ||
|'' | |''Device information'' | ||
| | |Asks for more exact information about the device with the number '''''DeviceID'''''. Three possibilities exist for PanTilt: '''No, Coarse, Fine'''. With Coarse or Fine, so the channels follow of Pan Tilt, at a scanner: '''''PanTilt: Coarse 0 1''''' on a 16 bit Scanner '''''PanTilt: Fine 0 1 14 15'''''. The order is there '''Pan Tilt PanFine TiltFine'''. After '''''Channels: quantity''''' is a list appended with all names of the channels as they are deposited in the DDF. | ||
|'''GetDeviceInfo 10''' -> | |'''GetDeviceInfo 10''' -> | ||
'''Name: Botex SP-1500 Stroboskop''' | '''Name: Botex SP-1500 Stroboskop''' | ||
| Line 78: | Line 78: | ||
'''PanTilt: No''' | '''PanTilt: No''' | ||
'''Channels: 2''' | '''Channels: 2''' | ||
'''Channel1: | '''Channel1: frequenz''' | ||
'''Channel2: | '''Channel2: intensity''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|StartChannelNotification ''StartChannel EndChannel'' | |StartChannelNotification ''StartChannel EndChannel'' | ||
| | |None | ||
| | |The asynchronous information about channel changes activates. In DMXControl if himself a channel '''''StartChannel''''' and '''''EndChannel''''' change, DMXControl sends a message with the new value. Of StartChannelNotification overwrites the old area send a further. | ||
|'''StartChannelNotification 1 10'''. | |'''StartChannelNotification 1 10'''. After value change of channel 5 on 255: -> '''CVC 5 255''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|StopChannelNotification | |StopChannelNotification | ||
| | |None | ||
| | |The notification deactivates about channel changes. | ||
|'''StopChannelNotification''' | |'''StopChannelNotification''' | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|GetCommandPossibilities ''Dropdown | |GetCommandPossibilities ''Dropdown Index, Predecessor index'' | ||
|'' | |''List of the possibilities'' | ||
| | |An command consists of single parts. ''Module'', ''Device/Function'', ''Channel'', ''...''. Since the following choice is based on the previous one, must the row after be questioned from the front. With ''GetCommandPossibilities 1'' one receives a list of the module possibilities. Every possibility has one ID. With ''GetCommandPossibilities 2 3'' one receives the choice for Device/Function, based on module 3. | ||
|'''GetCommandPossibilities 1''' -> | |'''GetCommandPossibilities 1''' -> | ||
'''1. | '''1. Deaktivate''' | ||
'''2. Audio''' | '''2. Audio''' | ||
'''3. Audiotrack''' | '''3. Audiotrack''' | ||
| Line 101: | Line 101: | ||
|- style="vertical-align:top;" | |- style="vertical-align:top;" | ||
|RunCommand ''Index1 Index2 Index3 Flags Value'' | |RunCommand ''Index1 Index2 Index3 Flags Value'' | ||
| | |None | ||
| | |With this command one executes the command. '''''Index1, Index2''''' and '''''Index3''''' the indices are there of GetCommandPossibilities. | ||
'''''Flags''''' | '''''Flags''''' is one binarily more codedly uprightly. Bit 0 stands for ''using indicated value'' for ''Toggle mode'' and bits 1. | ||
'''''Value''''' a DMX value is in per cent of 0,000 to 100,000 (for future 16 bits of values). | |||
|'''RunCommand 2 5 3 0 0.000''' | |'''RunCommand 2 5 3 0 0.000''' | ||
|} | |} | ||
Revision as of 20:31, 1 November 2013
|
This section is actively undergoing a major edit for a while. To help avoid edit conflicts, please do not edit this section while this message is displayed or contact the editor (Steiny) of this page. | This page was last edited at 20:31, 1 November 2013 (UTC) 4041 days ago. |
Hint:
25.10.2013: UPrenner: create the article page01.11.2013 UPrenner: work-in-progress
Overview
The PDA remote control has developed from the terminal interface of DMXControl over the serial remote control. By the « PDA remote control » DMXControl can ( telnet, COM interface, Bluetooth or about WLAN ) head with PDA and other serial interfaces.
 |
The window of the PDA remote control must remain open as in the case of all other remote controls/controls in DMXControl. No communication takes place at closed window. |
Description
This one « Serial remote control » did you implement in DMXControl to make the access about a serial interface or network (Ethernet) to the program possible. DMXControl expects a connection in the Netwerk on port 2145. This one can this port in the window « PDA remote control » being changed. Any program which can send character strings (strings) out is able to radioguide DMXControl with that. This one « Serial remote control » among other things android is (e.g. ) uses of the PDA control PDA_2_DMXC and of the web interface or the PHP class as well as different other controls. Since the protocol of the interface is open, it is possible for everybody to access DMXControl about a program of one's own.
The interface works bidirectionally, i. e. data can be sent and made an enquiry about. A table of the possible orders can be found below. Some orders don't return a value other after executing as a confirmation.
To DMXControl every order is sent to it, n must with a line break (in Java and C # "") be completed.
Port
A list of the commands and answers are listed by DMXControl into table following this one. Developers who would like to write an external program for DMXControl's control can make first experiences the best with a terminal program like telnet or Putty. This goes with the order at local work: telnet 127. 0. 0. 1 2145. One then immediately recognizes what the answers look. All commands are interpreted by great/use of small initial letters independently of DMXControl.
 |
Instead of SetChannel, so sEtChAnNeL also can be written to. |
The abbreviation CV stands for ChannelValueChanged for ChannelValue and CVC
| Enquiry to DMXC | Answer from DMXC | Description | Example |
| SetChannel Channel value | CV Channel value | Set the Channel on the Wert. | SetChannel 1 200 -> CV 1 200 |
| SC Channel Wert | CV Channel Wert | Short notation for SetChannel. | SC 1 200 -> CV 1 200 |
| GetChannel Channel | CV Channel value | Ask the value of the channel Channel. | GetChannel 1 -> CV 1 200 |
| GC Channel | CV Channel value | Short notation for GetChannel. | GC 1 -> CV 1 200 |
| GetAllDevices | List of Devices | Question on all devices available in DMXControl. | GetAllDevices ->
1. PAR-1 2. PAR-2 ... 10. Botex SP-1500 Stroboskop |
| GetDeviceInfo DeviceID | Device information | Asks for more exact information about the device with the number DeviceID. Three possibilities exist for PanTilt: No, Coarse, Fine. With Coarse or Fine, so the channels follow of Pan Tilt, at a scanner: PanTilt: Coarse 0 1 on a 16 bit Scanner PanTilt: Fine 0 1 14 15. The order is there Pan Tilt PanFine TiltFine. After Channels: quantity is a list appended with all names of the channels as they are deposited in the DDF. | GetDeviceInfo 10 ->
Name: Botex SP-1500 Stroboskop StartAddress: 257 PanTilt: No Channels: 2 Channel1: frequenz Channel2: intensity |
| StartChannelNotification StartChannel EndChannel | None | The asynchronous information about channel changes activates. In DMXControl if himself a channel StartChannel and EndChannel change, DMXControl sends a message with the new value. Of StartChannelNotification overwrites the old area send a further. | StartChannelNotification 1 10. After value change of channel 5 on 255: -> CVC 5 255 |
| StopChannelNotification | None | The notification deactivates about channel changes. | StopChannelNotification |
| GetCommandPossibilities Dropdown Index, Predecessor index | List of the possibilities | An command consists of single parts. Module, Device/Function, Channel, .... Since the following choice is based on the previous one, must the row after be questioned from the front. With GetCommandPossibilities 1 one receives a list of the module possibilities. Every possibility has one ID. With GetCommandPossibilities 2 3 one receives the choice for Device/Function, based on module 3. | GetCommandPossibilities 1 ->
1. Deaktivate 2. Audio 3. Audiotrack ... |
| RunCommand Index1 Index2 Index3 Flags Value | None | With this command one executes the command. Index1, Index2 and Index3 the indices are there of GetCommandPossibilities.
Flags is one binarily more codedly uprightly. Bit 0 stands for using indicated value for Toggle mode and bits 1. Value a DMX value is in per cent of 0,000 to 100,000 (for future 16 bits of values). |
RunCommand 2 5 3 0 0.000 |
GetCommandPossibilities und RunCommand
Um einen spezifischen Befehl mit RunCommand auszuführen, muss man wissen, welche ID der Befehl besitzt. Diese ID kann man mit dem Aufruf GetCommandPossibilities sehr einfach herausfinden. Man arbeitet sich dabei Schritt für Schritt von der obersten Ebene (1) bis zur benötigten Ebene (z.B. 3) herab. Die erste Ziffer hinter dem Aufruf stellt die Ebene dar, auf der man sich gerade befindet. Die folgenden Ziffern stehen für die IDs der Ergebnisse der Abfragen der vorherigen Ebenen. Daher ist es sehr wichtig, dass die Ebenen der Reihe nach durchlaufen werden.
Um z.B. einen Effekt auf diese Weise zu starten, könnte dies wie folgt aussehen: Ein Aufruf des Befehls GetCommandPossibilities 1 liefert die folgende Tabelle, wobei es hier keine zweite Ziffer gibt, da wir uns auf der höchsten Ebene (Ebene 1) befinden.
Installierte Plugins reihen sich in die Liste ein, wenn vorhanden.
1. Deaktivate 2. Audio 3. Audiotrack 4. BeatTool 5. DMX-Ausgabe 6. DMXIn-Remote 7. Effekte 8. External Action (Plugin) 9. Geräte 10. Gruppenauswahl 11. Joystick 12. KommandoBox 13. Kommandozeile 14. Master 15. MIDI-Remote 16. OSC-Receiver (PLugin) 17. Sound Analyzer 18. Submaster 19. Szenenbibliothek 20. Szenenliste 21. Textbuch
Nun fragen wir die Optionen für die ID 7 Effekte für die Ebene 2 ab: GetCommandPossibilities 2 7 liefert uns die ID, der Optionen, auf die zugegriffen werden kann. Auswahl und Sprünge der Effekte wäre in diesem Fall über die IDs 1-4 möglich. Die selbst programmieten Effekte haben die IDs ab 6:
1. Alle 2. Ausgewählter 3. Nächster 4. Vorheriger 5. ---- 6. [EFFEKT 1] 7. [EFFEKT 2] 8. [EFFEKT 3] 9. ...
Der nun folgende Aufruf für die 3. Ebene GetCommandPossibilities 3 6 zeigt in unserem Beispiel [Effekt 1] die für diesen Effekt möglichen Funktionen. DMXControl gibt folgende Liste zurück:
1. Auswählen 2. Start/Stop 3. Start 4. Stop 5. Beschl. setzen 6. Intens. setzen 7. Nächster Schritt 8. Wiederh. ein/aus
Mit RunCommand 7 6 3 lässt sich der Effekt 1 starten oder mit RunCommand 7 6 4 stoppen. Für den Effekt 3 wären das die Aufrufe RunCommand 7 8 3 und RunCommand 7 8 4. Wenn noch Werte mit übertragen werden müssen, werden diese hinten angehängt: RunCommand 7 6 3 0 0.000. Andere Aufrufe funktionieren nach dem selben Prinzip.
| |
Evtl. hilft es beim Verständnis sich die Programmierung der Kommandobox anzusehen. Die Spalten bei der Buttonprogrammierung Modul, Gerät/Funktion, Kanal, Flags und Wert entsprechen den Ebenen, IDs und Werten des RunCommand-Befehls. |
Links und Referenzen
Links
- PDA-Fernbedienung Software: http://www.dmxcontrol.de/files/pda-2-dmxc/PDA-2-DMXC_1.0_Setup.exe
Tutorials
| |||||||||||||