@zimo-elektronik/zcan 1.0.0

package/protocol_docs/docs/command-groups/lan-data/data-value-extended.md

@@ -0,0 +1,65 @@
+---
+id: data-value-extended
+title: Data Value Extended
+sidebar_position: 1
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="17" command="08"/>
+
+## Receiving
+
+When receiving command _0x08_ the 'Data' section will look like this:
+
+| NID    | Unused 🚧 | Flag bytes | Unused 🚧 | Track mode | Function count | Unused 🚧 | Speed and direction | Functions | Special functions |
+|--------|-----------|------------|-----------|------------|----------------|-----------|---------------------|-----------|-------------------|
+| 16 Bit | 16 Bit    | 32 Bit     | 128 Bit   | 8 Bit      | 8 Bit          | 144 Bit   | 16 Bit              | 32 Bit    | 32 Bit            |
+
+### Speed and direction flags
+
+| Bit       | Meaning                                                                                                                          |
+|-----------|----------------------------------------------------------------------------------------------------------------------------------|
+| 0 ... 9   | Vehicle speed.     Note: For all track formats, the maximum ZIMO speed is 1008.  Values > 1008 are automatically scaled to 1008. |
+| 10        | Direction instruction (client to MX10)<br/> '0' ➔ Forward<br/> '1' ➔ Backward                                                    |
+| 11        | Current track direction (MX10 to client)<br/> '0' ➔ Forward<br/> '1' ➔ Backward                                                  |
+| 12 ... 13 | Sideways <br/>'0' ➔ Undefined<br/> '1' ➔ East<br/> '2' ➔ West                                                                    |
+| 14        | Unused 🚧                                                                                                                        |
+| 15        | Vehicle Emergency Stop                                                                                                           |
+
+
+### Track mode flags
+
+| Bit     | Meaning                                                                                    |
+|---------|--------------------------------------------------------------------------------------------|
+| 4 ... 7 | 0: unknown<br/> 1: DCC<br/> 2: MM2<br/> 3: not defined<br/> 4: mfx<br/> 7: System Use<br/> |
+
+### Flag bytes 🚧
+
+:::caution Under construction🚧
+
+Description of flags is needed
+
+:::
+
+### Special functions
+
+| Bit     | Meaning                 |
+|---------|-------------------------|
+| 0 ... 3 | Shunting function state |
+| 4 ... 5 | Manual mode state       |
+
+## Sending
+
+When sending command _0x08_ the 'Data' section will look like this:
+
+| Mx10 NID | NID    | 0      |
+|----------|--------|--------|
+| 16 Bit   | 16 Bit | 16 Bit |
+
+
+:::note
+
+Mode should be set to 0b00.
+
+:::

package/protocol_docs/docs/command-groups/lan-data/loco-gui-extended.md

@@ -0,0 +1,48 @@
+---
+id: loco-gui-extended
+title: Loco Gui Extended
+sidebar_position: 2
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="17" command="27"/>
+
+## Receiving
+
+When receiving command _0x27_ the 'Data' section will look like this:
+
+| NID    | Sub ID | Vehicle group | Name     | Image ID | Tacho  | Speed forward | Speed rev 🚧 What is this? (Rev as max rev on cars?) | Speed range | Drive type | Era    | Country code | Icons 🚧 What is done with icons? |
+|--------|--------|---------------|----------|----------|--------|---------------|------------------------------------------------------|-------------|------------|--------|--------------|-----------------------------------|
+| 16 Bit | 16 Bit | 16 Bit        | 26 Bytes | 16 Bit   | 16 Bit | 16 Bit        | 16 Bit                                               | 16 Bit      | 16 Bit     | 16 Bit | 16 Bit       | 64 Bytes                          |
+
+### Era parsing 🚧
+
+:::caution Under construction🚧
+
+Further description is needed! Is the era parsing needed and if so then explain
+
+:::
+
+### Functions 🚧
+
+:::caution Under construction🚧
+
+Further description is needed! Explain What is done with functions
+
+:::
+
+## Sending
+
+When sending command _0x27_ the 'Data' section will look like this:
+
+| Mx10 NID | NID    | 0      |
+|----------|--------|--------|
+| 16 Bit   | 16 Bit | 16 Bit |
+
+
+:::note
+
+Mode should be set to 0b00.
+
+:::

package/protocol_docs/docs/command-groups/lan-info/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Lan Info",
+  "position": 10
+}

package/protocol_docs/docs/command-groups/lan-info/module-power-info.md

@@ -0,0 +1,26 @@
+---
+id: module-power-info
+title: Module Power Info
+sidebar_position: 1
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="18" command="00"/>
+
+## Receiving
+
+If a PC software/client has 'long' data-grams enabled, the MX10 sends its track status, current and voltage values in a 'long' data-gram.
+
+When receiving command _0x00_ the 'Data' section will look like this:
+
+| Device NID | Port 1 | Port 1 voltage | Port 1 amperage | Port 2 | Port 2 voltage | Port 2 amperage | Amperage 32V | Amperage 12V | Voltage total | Temperature |
+|------------|--------|----------------|-----------------|--------|----------------|-----------------|--------------|--------------|---------------|-------------|
+| 16 Bit     | 16 Bit | 16 Bit         | 16 Bit          | 16 Bit | 16 Bit         | 16 Bit          | 16 Bit       | 16 Bit       | 16 Bit        | 16 Bit      |
+The 'Device NID' is the Network Id of the queried device, or the Network Id of the source of the Power Info message. This can be (currently 2020.05.18) the master MX10(ec), MX10 booster or StEin[e].
+
+:::info Recommendation
+
+A PC software MUST be prepared to send more data bytes!!! Depending on future requirements the MX10 will send more status information.
+
+:::

package/protocol_docs/docs/command-groups/lan-network/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Lan Network",
+  "position": 11
+}

package/protocol_docs/docs/command-groups/lan-network/open-port.md

@@ -0,0 +1,47 @@
+---
+id: open-port
+title: Open Port
+sidebar_position: 1
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="1a" command="0e"/>
+
+## Receiving
+
+When receiving command _0x0e_ , NID is used from message data-gram for connection!
+
+## Sending
+
+When sending command _0x0e_ the 'Data' section will look like this:
+
+| Options | App code | App name    |
+|---------|----------|-------------|
+| 32 Bit  | 32 Bit   | 0 ... x Bit |
+
+
+With this data-gram a device can 'open' the Ethernet interface of the MX10. In response, the device receives a 'ping' from the MX10.
+
+With length '0' a simple 'Open' of the interface takes place, further specifications are not necessary.
+
+If length is greater than 8, then:
+
+- The first 4 bytes contain options
+- In the bytes 5 ... 8 an application identifier (unique program identifier) follows. After that up to 24 characters can be sent as application name.
+- This name is used in various displays on MX10 and MX32.
+
+If NO name is sent, the 32 bit identifier is displayed, if this is not sent either, then simply 'PC control' is displayed. This is especially user unfriendly for larger systems.
+
+### Options
+
+| Bit       | Content                          |
+|-----------|----------------------------------|
+| 0         | Long message                     |
+| 1         | Free                             |
+| 2 ... 7   | Multi list                       |
+| 8 ... 22  | Free                             |
+| 23        | Connection lost ➔ Stop all locos |
+| 24        | Debug Output                     |
+| 25 ... 31 | Free                             |
+

package/protocol_docs/docs/command-groups/network/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Network",
+  "position": 8
+}

package/protocol_docs/docs/command-groups/network/ping.md

@@ -0,0 +1,49 @@
+---
+id: ping
+title: Ping
+sidebar_position: 1
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="0a" command="00"/>
+
+## Receiving
+
+When receiving command _0x00_ you use the NID provided in the message!
+
+With a ping request devices can ask other devices on the CAN bus to respond with a ping ack. This allows each device to check whether the other device(s) is/are present. The NId of a specific device can be specified in the request. In this case the device answers immediately, the sender can therefore assume after approx. 100mS that the device is responding or is not available at the moment. If instead of a concrete NId a group NId (e.g. 0xD000 for new modules) is requested, all devices of this group will answer with a random NId. devices of this group answer with a random delay of up to 1000mS.
+
+All devices should send a ping regularly! The following criteria should be observed:
+
+- After starting the device should ping at least once within the first second.
+- The time intervals should have a deliberate jitter by a random value.
+- At low CAN bus load each module should send one ping between 500 and 1000mS.
+
+**Exceptions** (slower ping):
+
+- At high CAN bus utilization (> 500 messages/second) pings should be omitted. In any case one ping must be sent every 5000mS.
+- If the device itself has many messages to send, the ping can also be omitted.
+- In any case, each device MUST send at least ONE message every 5000mS on the CAN bus that is VALID!!!
+
+The primary control panel sends this command approximately every 500ms, but at least every second.
+
+With this command, the connected modules should recognize that they are still connected to the known control panel. The session number must also be checked. This session number is incremented by the central unit with every UID change. This happens e.g.: when the control panel adds a new object to your object list or when an existing object is removed. or if an existing object is deleted from this list. If a module detects that it is connected to an 'unknown' control center, it must initiate a login process.
+
+## Sending
+
+When sending command _0x00_ the 'Data' section will look like this:
+
+| Mx10 NID |
+|----------|
+| 16 Bit   |
+
+
+## Sending [0x0a, 0x07]
+
+When sending command _0x00_ the 'Data' section will look like this:
+
+| Mx10 NID |
+|----------|
+| 16 Bit   |
+

package/protocol_docs/docs/command-groups/system/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "System",
+  "position": 1
+}

package/protocol_docs/docs/command-groups/system/system-state.md

@@ -0,0 +1,59 @@
+---
+id: system-state
+title: System State
+sidebar_position: 0
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="00" command="00"/>
+
+The Command Group 0x00 summarizes all system 'High-Priority' commands and must be implemented by all boosters and drive consoles.
+
+With Cmd=0x00/M=0b00 the power status of the respective device can be queried.
+
+:::caution
+
+A query immediately after a Power Command can lead to inconsistent answers! After a Power Mode Command the device (specified by NId, e.g.: MX10, StEin, ...)) changes to the desired mode, but this is only reported AFTER the internal control loops have executed the change and it is verified by measurements. This process can take several 100ms depending on the desired change!
+
+:::
+
+With Cmd=0x00/M=0b01 the port power status of the device can be set. The current status is 'acknowledged' by Cmd=0x00/M=0b11. The valid status is also included in the regular (approx. 500ms) power message.
+
+The object ports are binary coded and this combinations are allowed:
+
+| Port       | Output                                            |
+|------------|---------------------------------------------------|
+| 0b00000001 | Rail 1                                            |
+| 0b00000010 | Rail 2                                            |
+| 0b0………. 00 | Track 3 ... 7 (Further MX10 in booster mode)      |
+| 0b10000000 | Booster output, resp. track output 8 at MX9/StEin |
+
+
+_Therefore, to switch ALL outputs with one command, port 255 (=0xFF, =0b111111) must be used._
+
+:::caution
+
+If several outputs are switched at the same time, the confirmation still takes place individually for each of the 'existing' ports. So if e.g.: no further MX10 is available in booster mode, there will be NO ACK for these non-existent rails!
+
+:::
+
+Applications (whether via PC interface or one of the internal bus systems) should ALWAYS wait for the ACK of the MX10 after a power mode change. ALWAYS wait for the respective ACK of the MX10, which basically makes a 'query' unnecessary.
+
+## Receiving
+
+When receiving command _0x00_ the 'Data' section will look like this:
+
+| Device NID | Port  | Mode state |
+|------------|-------|------------|
+| 16 Bit     | 8 Bit | 8 Bit      |
+
+
+## Sending
+
+When sending command _0x00_ the 'Data' section will look like this:
+
+| Device NID | Port  | Mode state |
+|------------|-------|------------|
+| 16 Bit     | 8 Bit | 8 Bit      |
+

package/protocol_docs/docs/command-groups/track/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Track",
+  "position": 5
+}

package/protocol_docs/docs/command-groups/track/tse-prog-read.md

@@ -0,0 +1,37 @@
+---
+id: tse-prog-read
+title: TSE Prog Read
+sidebar_position: 1
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="16" command="08"/>
+
+## Receiving
+
+When receiving command _0x08_ the 'Data' section will look like this:
+
+With the TSE Read commands CV's can be read from a decoder. The selected TSE mode (Cmd=0x00) decides whether this should be done by POM (default) or Service Mode commands.
+
+| System NID | Vehicle NID | Config number | Value |
+|------------|-------------|---------------|-------|
+| 16 Bit     | 16 Bit      | 32 Bit        | 8 Bit |
+
+
+The command (0b01) causes the command station (NID) to send a 'Config Read' command to the rail decoder (vehicle NID). As long as the read command is 'active', the progress will be reported by TSE Info's. AAs soon as the control panel has the desired config value, this is signaled by a 'TSE Read ACK' telegram.
+
+:::danger
+
+After Read/Write commands the respective control unit (MX32, PC, ...) should keep a pause of approx. 200mS. This serves that other rail commands can be processed.
+
+:::
+
+## Sending
+
+When sending command _0x08_ the 'Data' section will look like this:
+
+| Train address | CV     |
+|---------------|--------|
+| 16 Bit        | 32 Bit |
+

package/protocol_docs/docs/command-groups/track/tse-prog-write.md

@@ -0,0 +1,35 @@
+---
+id: tse-prog-write
+title: TSE Prog Write
+sidebar_position: 2
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="16" command="09"/>
+
+## Receiving
+
+When receiving command _0x09_ the 'Data' section will look like this:
+
+| System NID | Vehicle NID | Config number | Value |
+|------------|-------------|---------------|-------|
+| 16 Bit     | 16 Bit      | 32 Bit        | 8 Bit |
+
+
+The command (0b01) causes the command station (NID) to send a 'Config Write' command to the rail decoder (vehicle NID). As long as the write command is 'active', the progress will be reported by TSE Info's. As soon as the command station writes the desired Config value, this is reported by a 'TSE Write ACK' telegram.
+
+:::danger
+
+After Read/Write commands the respective control unit (MX32, PC, ...) should keep a pause of approx. 200mS. This serves that other rail commands can be processed.
+
+:::
+
+## Sending
+
+When sending command _0x09_ the 'Data' section will look like this:
+
+| Train address | CV     | Value |
+|---------------|--------|-------|
+| 16 Bit        | 32 Bit | 8 Bit |
+

package/protocol_docs/docs/command-groups/train/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Train",
+  "position": 4
+}

package/protocol_docs/docs/command-groups/train/train-part-find.md

@@ -0,0 +1,33 @@
+---
+id: train-part-find
+title: Train Part Find
+sidebar_position: 1
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="05" command="02"/>
+
+## Receiving
+
+When receiving command _0x02_ the 'Data' section will look like this:
+
+| NID    | Train NID | Owner NID | State  |
+|--------|-----------|-----------|--------|
+| 16 Bit | 16 Bit    | 16 Bit    | 16 Bit |
+
+
+## Sending
+
+When sending command _0x02_ the 'Data' section will look like this:
+
+| NID    |
+|--------|
+| 16 Bit |
+
+
+:::note
+
+Mode should be set to 0b00.
+
+:::

package/protocol_docs/docs/command-groups/vehicles/_category_.json

@@ -0,0 +1,4 @@
+{
+  "label": "Vehicle",
+  "position": 3
+}

package/protocol_docs/docs/command-groups/vehicles/vehicle-function.md

@@ -0,0 +1,36 @@
+---
+id: vehicle-function
+title: Vehicle Function
+sidebar_position: 2
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="02" command="04"/>
+
+## Receiving
+
+When receiving command _0x04_ the 'Data' section will look like this:
+
+| NID    | Function number | Function state |
+|--------|-----------------|----------------|
+| 16 Bit | 16 Bit          | 16 Bit         |
+
+If Mode = 0b00, then the function of the locomotive with 'NID' and the function 'No.' is queried. <br/> If Mode = 0b01, then the locomotive function 'Function number' of the locomotive 'NID' is set to the specified value. <br/> If Mode = 0b11, then the loco responds to a function value query. <br/> Where function state = 0x00 always means "Off" and function state not equal to 0x00 depends on the respective locomotive decoder. For "normal" DCC and MM locomotive decoders this is interpreted as the function being "On".
+
+The 'Function number' is divided into several areas for this command:
+
+| From function number | To function number | Description                                                                                 | Valid values |
+|----------------------|--------------------|---------------------------------------------------------------------------------------------|--------------|
+| 0                    | 31                 | The known 'normal' functions. The maximum function number depends on the respective format. | On/Off       |
+| 256                  | 512                | 256 analog functions                                                                        | 0 ... 255    |
+| 32768                | 65536              | Binary States (see NMRA 9.2.1)                                                              | On/Off       |
+
+## Sending
+
+When sending command _0x04_ the 'Data' section will look like this:
+
+| Vehicle address | Function ID | Function status |
+|-----------------|-------------|-----------------|
+| 16 Bit          | 16 Bit      | 16 Bit          |
+

package/protocol_docs/docs/command-groups/vehicles/vehicle-mode.md

@@ -0,0 +1,143 @@
+---
+id: vehicle-mode
+title: Vehicle Mode
+sidebar_position: 0
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="02" command="01"/>
+
+These data-grams are used to query or set the vehicle's operating mode. In order for the MX10 to control the vehicle, the operating parameters must be known. The operating parameters of the vehicle can/must be determined by the PC software! To do this, it can query them first and add only the "unknown" parameters, or simply send "your" parameters as a command. In any case, the MX10 works with the last defined (received) vehicle parameters and stores them on the end of operation.
+
+## Receiving
+
+When receiving command _0x01_ the 'Data' section will look like this:
+
+| NID    | Mode1 | Mode2 | Mode3 |
+|--------|-------|-------|-------|
+| 16 Bit | 8 Bit | 8 Bit | 8 Bit |
+
+Mode=0b00 allows the control unit to query the current operating parameters for a vehicle. With a response with M1=0x00 and M2=0x00 the respective vehicle is unknown to the MX10.
+
+### Mode 1 flags
+
+| Bit     | Meaning                                                                                                                        |
+|---------|--------------------------------------------------------------------------------------------------------------------------------|
+| 0 ... 3 | **Speed Steps:** <br/> 0: 'unknown<br/> 1: 14FS<br/> 2: 27FS<br/> 3: 28FS<br/> 4: 128FS<br/> 5: 1024FS<br/> 6 - 7: not defined |
+| 4 ... 7 | **Operating mode:** <br/> 0: unknown<br/> 1: DCC<br/> 2: MM2<br/> 3: not defined<br/> 4: mfx<br/> 7: System Use                |
+
+### Mode 2 flags
+
+| Bit     | Meaning                                                 |
+|---------|---------------------------------------------------------|
+| 0 ... 7 | Max. Number of functions: None (0) to currently max. 32 |
+
+### Mode 3 flags
+
+| Bit     | Meaning                                                                                                                                            |
+|---------|----------------------------------------------------------------------------------------------------------------------------------------------------|
+| 0       | Pulse Fx (functions are thus sent pulse chain, LGB)                                                                                                |
+| 1       | Analog Fx (Analog Functions)                                                                                                                       |
+| 2 ... 3 | **Speed Limit SIMO / Speed Limit NMRA**<br/>  0b00 = Do not send Speed Limit<br/>  0b01 = Send NMRA Speed Limit<br/>  0b10 = Send ZIMO Speed Limit |
+| 4 ... 7 | Not defined                                                                                                                                        |
+
+## Sending
+
+When sending command _0x01_ the 'Data' section will look like this:
+
+| Vehicle address |
+|-----------------|
+| 16 Bit          |
+
+## Summary table
+
+<html>
+
+<head> <link rel="stylesheet" href="../../../src/css/custom.css"></link> </head>
+<body>
+
+<table>
+  <thead>
+    <tr>
+      <th> Byte </th>
+      <th> Length (in Bytes) </th>
+      <th> Name </th>
+      <th> Description </th>
+    </tr>
+  </thead>
+  <tbody>
+    <tr>
+      <td> 0 </td>
+      <td> 2 </td>
+      <td> NID </td>
+      <td> Some identification number </td>
+    </tr>
+    <tr>
+      <td rowspan="1"> 2 </td>
+      <td rowspan="1"> 1 </td>
+      <td> Mode 1 </td>
+      <td class="tables">
+        <table class="tables">
+          <thead>
+            <tr>
+              <td class="tablesBitCol"> Bit </td>
+              <td class="tablesDescriptionCol"> Description </td>
+            </tr>
+          </thead>
+          <tbody>
+            <tr>
+              <td> 0 ... 3 </td>
+              <td> <strong>Speed Steps:</strong> <br /> 0: 'unknown<br /> 1: 14FS<br /> 2: 27FS<br /> 3: 28FS<br /> 4: 128FS<br /> 5: 1024FS<br /> 6 - 7: not defined </td>
+            </tr>
+            <tr>
+              <td> 4 ... 7 </td>
+              <td> <strong>Operating mode:</strong> <br /> 0: unknown<br /> 1: DCC<br /> 2: MM2<br /> 3: not defined<br /> 4: mfx<br /> 7: System Use </td>
+            </tr>
+          </tbody>
+        </table>
+      </td>
+    </tr>
+    <tr>
+      <td> 3 </td>
+      <td> 1 </td>
+      <td> Mode 2 </td>
+      <td> Max. Number of functions: None (0) to currently max. 32 </td>
+    </tr>
+    <tr>
+      <td rowspan="1"> 4 </td>
+      <td rowspan="1"> 1 </td>
+      <td> Mode 3 </td>
+      <td class="tables">
+        <table class="tables">
+          <thead>
+            <tr>
+              <td class="tablesBitCol"> Bit </td>
+              <td class="tablesDescriptionCol"> Description </td>
+            </tr>
+          </thead>
+          <tbody>
+            <tr>
+              <td> 0 </td>
+              <td> Pulse Fx (functions are thus sent pulse chain, LGB) </td>
+            </tr>
+            <tr>
+              <td> 1 </td>
+              <td> Analog Fx (Analog Functions) </td>
+            </tr>
+            <tr>
+              <td> 2 ... 3 </td>
+              <td> <strong>Speed Limit SIMO / Speed Limit NMRA</strong><br /> 0b00 = Do not send Speed Limit<br /> 0b01 = Send NMRA Speed Limit<br /> 0b10 = Send ZIMO Speed Limit </td>
+            </tr>
+            <tr>
+              <td> 4 ... 7 </td>
+              <td> Not defined </td>
+            </tr>
+          </tbody>
+        </table>
+      </td>
+    </tr>
+  </tbody>
+</table>
+</body>
+</html>

package/protocol_docs/docs/command-groups/vehicles/vehicle-special-function-switch.md

@@ -0,0 +1,35 @@
+---
+id: vehicle-special-function-switch
+title: Vehicle Special Function Switch
+sidebar_position: 3
+---
+
+import CommandAndGroup from '@site/src/components/CommandAndGroup';
+
+<CommandAndGroup group="02" command="05"/>
+
+## Receiving
+
+When receiving command _0x05_ the 'Data' section will look like this:
+
+| NID    | Special function mode | Special function value |
+|--------|-----------------------|------------------------|
+| 16 Bit | 16 Bit                | 16 Bit                 |
+
+
+### Special function mode and values
+
+| Special function mode | Description       | Special function value                                        |
+|-----------------------|-------------------|---------------------------------------------------------------|
+| 1                     | Manual            | OFF = 0<br/> ON = 1                                           |
+| 2                     | Shunting function | OFF = 0<br/> AZBZ = 1<br/> Half = 2                           |
+| 3                     | DirectionDefault  | No change = 0<br/> Direction East = 1<br/> Direction West = 2 |
+
+## Sending
+
+When sending command _0x05_ the 'Data' section will look like this:
+
+| NID    | Special function mode | Special function value |
+|--------|-----------------------|------------------------|
+| 16 Bit | 16 Bit                | 16 Bit                 |
+