Hint:
25.10.2013: UPrenner: create the article page
01.11.2013 UPrenner: work-in-progress
01.11.2013: UPrenner article ready, just update of pictures
If you are a native speaker, please Help us and review this
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
To execute a specific order with rush command, one must know which ID the order has. One very simply can find out this ID with the call GetCommandPossibilities. One works himself at this step by step down from the topmost level (1) up to the required level (e.g. 3). The first number behind the call represents the level on which one just is. The following numbers stand for the IDs of the results of the queries of the previous levels. It is therefore very important that the level of the row will pass after.
To start e.g. an effect this way, this could look as follows: A call of the order GetCommandPossibilities 1 delivers the following table in which there isn't a second number since we are on the highest level (level 1).
Installed Plugins join the list if available.
1. Deaktivate 2. Audio 3. Audio track 4. BeatTool 5. DMX outpute 6. DMXIn remote 7. Chasers 8. External Action (Plugin) 9. Devices 10. Group selection 11. Joystick 12. Command box 13. Command line 14. Master 15. MIDI remote 16. OSC receiver (Plugin) 17. Sound analyzer 18. Submaster 19. Cue libary 20. Cue list 21. Textbook
We question on the options for the ID 7 chasers for the level 2 now: GetCommandPossibilities 2 7 provides the ID, the options which can be accessed, to us. In this case 1-4 would be choice and jumps of the chasers possibly about the IDs. The pro-even grief rents chasers have the IDs as of 6:
1. All 2. Selected 3. Next 4. Previous 5. ---- 6. [CHASER 1] 7. [CHASER 2] 8. [CHASER 3] 9. ...
The call following now for the 3rd level GetCommandPossibilities 3 6 shows the functions possible for this effect in our example [CHASER 1]. DMXControl gives the following list back:
1. Select 2. Start/Stop 3. Start 4. Stop 5. Set acceleration 6. Set intensity 7. Next step 8. Repeat on/off
With RunCommand 7 6 3 the chaser has 1 to start or to stop with RunCommand 7 6 4 for itself. For the chaser 3 these would be the calls RunCommand 7 8 3 and RunCommand 7 8 4. If values still must be transferred, these are appended behind: RunCommand 7 6 3 0 0,000. Other calls work according to the same principle.
| |
Perhaps it helps at the understanding to look at the programming of the command box. The columns at the button programming module, device/function, channel, flags and value correspond to the levels, IDs and values of the RunCommand command. |
Links and references
Links
- PDA-Fernbedienung Software: http://www.dmxcontrol.de/files/pda-2-dmxc/PDA-2-DMXC_1.0_Setup.exe
Tutorials
- PDA-2-DMXC Tutorial 'Not yet translated'
| |||||||||||||