Implement dot2 specific workarounds

1 files changed, 27 insertions, 8 deletions

diff --git a/backends/maweb.md b/backends/maweb.md
index dd13db9..6076f44 100644
--- a/backends/maweb.md
+++ b/backends/maweb.md
@@ -5,10 +5,15 @@ instances (GrandMA2 / GrandMA2 OnPC / GrandMA Dot2 / GrandMA Dot2 OnPC).
 It grants read-write access to the console's playback faders and buttons as well as write access to
 the command line buttons.
 
-To allow this backend to connect to the console, enter the console configuration (`Setup` key),
-select `Console`/`Global Settings` and set the `Remotes` option to `Login enabled`.
+#### Setting up the console
+
+For the GrandMA2 enter the console configuration (`Setup` key), select `Console`/`Global Settings` and
+set the `Remotes` option to `Login enabled`.
 Create an additional user that is able to log into the Web Remote using `Setup`/`Console`/`User & Profiles Setup`.
 
+For the dot2, enter the console configuration using the `Setup` key, select `Global Settings` and enable the
+Web Remote. Set a web remote password using the option below the activation setting.
+
 #### Global configuration
 
 The `maweb` backend does not take any global configuration.
@@ -27,12 +32,23 @@ Currently, three types of channels can be assigned
 
 ##### Executors
 
-Executors are arranged in pages, with each page having 90 fader executors (numbered 1 through 90) and
-90 button executors (numbered 101 through 190).
-
-Note that when creating a new show, only the first page is created and active.
-
-A fader executor consists of a fader, two buttons (`upper`, `lower`) above it and one `flash` button below it.
+* For the GrandMA2, executors are arranged in pages, with each page having 90 fader executors (numbered 1 through 90)
+	and 90 button executors (numbered 101 through 190).
+	* A fader executor consists of a `fader`, two buttons above it (`upper`, `lower`) and one `flash` button below it.
+	* A button executor consists of a `button` control.
+* For the dot2, executors are also arranged in pages, but the controls are non-obviously numbered.
+	* For the faders, they are right-to-left from the Core Fader section (Faders 6 to 1) over the F-Wing 1 (Faders 13 to 6) to
+	F-Wing 2 (Faders 21 to 14).
+	* Above the fader sections are two rows of 21 `button` executors, numbered 122 through 101 (upper row) and 222 through 201 (lower row),
+		in the same order as the faders are.
+	* Fader executors have two buttons below them (`upper` and `lower`).
+	* The button executor section consists of six rows of 18 buttons, divided into two button wings. Buttons on the wings
+		are once again numbered right-to-left.
+		* B-Wing 1 has `button` executors 308 to 301 (top row), 408 to 401 (second row), and so on until 808 through 801 (bottom row)
+		* B-Wing 2 has 316 to 309 (top row) through 816 to 809 (bottom row)
+
+When creating a new show, only the first page is created and active. Additional pages have to be created explicitly within
+the console before being usable.
 
 These controls can be addressed like
 
@@ -45,6 +61,7 @@ A button executor can likewise be mapped using the syntax
 
 ```
 mw1.page2.button103 > mw1.page3.button101
+mw1.page2.button803 > mw1.page3.button516
 ```
 
 ##### Command line buttons
@@ -58,6 +75,8 @@ mw1.<button-name>
 
 The following button names are recognized by the backend:
 
+| Supported	| Command	| Line		| Keys		|			|				|		|
+|---------------|---------------|---------------|---------------|-----------------------|-------------------------------|---------------|
 | `SET`		| `PREV`	| `NEXT`	| `CLEAR`	| `FIXTURE_CHANNEL`	| `FIXTURE_GROUP_PRESET`	| `EXEC_CUE`	|
 | `STORE_UPDATE`| `OOPS`	| `ESC`		| `OFF`		| `ON`			| `MA`				| `STORE`	|
 | `0`		| `1`		| `2`		| `3`		| `4`			| `5`				| `6`		|