You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/about/index.rst
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Supported |WTSS| include:
28
28
* Easily create and edit on-the-fly consists / multiple units (software-defined)
29
29
* Control layout power, turnouts/points, routes, and access JMRI web panels and windows
30
30
* Play virtual loco sounds
31
-
* Specific to the DCC-EX EX-CommandStation, when using the Native DCC-EX Protocol, |ED| can also:
31
+
* Specific to the `DCC-EX EX-CommandStation<https://dcc-ec.com>`_ can also use the Native DCC-EX Protocol to communicate. |BR| When using the Native DCC-EX Protocol, |ED| can also:
32
32
33
33
* Program CVs (Service Mode and Operation Mode)
34
34
* Control the TrackManager features.
@@ -69,11 +69,11 @@ The WiThrottle Protocol itself is a standard for how WiFi throttles can communic
69
69
WiThrottle protocol VS DCC-EX Native protocol
70
70
---------------------------------------------
71
71
72
-
|ED| traditionally used the WiThrottle Protocol (described above). When the |DCC-EX| team designed the |EX-CS| they found the WiThrottle Protocol too limiting and came up with a new protocol referred to originally as **DCC++** but later as **DCC-EX Native Protocol**.
72
+
|ED| traditionally used the WiThrottle Protocol (described above). When the |DCC-EX| team designed the |EX-CS| they found the WiThrottle Protocol too limiting and came up with a new protocol referred to originally as **DCC++** but later as **Native DCC-EX Protocol**.
73
73
74
-
|ED| can use either protocol and, by default, will try to use the more powerful **DCC-EX Native Protocol** when connecting to a |EX-CS|.
74
+
|ED| can use either protocol and, by default, will try to use the more powerful **Native DCC-EX Protocol** when connecting to a |EX-CS|.
75
75
76
-
|ED| can also us the Native Protocol to connect to a |EX-CS| via |JMRI| but you need to enable the "DCC++ over TCP Server" in the "DCC++" menu on Decoder-Pro.
76
+
|ED| can also us the Native DCC-EX Protocol to connect to a |EX-CS| via |JMRI| but you need to enable the "DCC++ over TCP Server" in the "DCC++" menu in Decoder-Pro.
Copy file name to clipboardExpand all lines: docs/index.rst
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Engine Driver
28
28
:align:right
29
29
30
30
Supported servers include |JMRI|, |EX-CS|, `MRC Prodigy WiFi <https://www.modelrectifier.com/category-s/332.htm>`_, `Digitrax LnWi <https://www.digitrax.com/products/wireless/lnwi/>`_, and `WifiTrax (for NCE) <http://wifitrax.com/products/product-WFD-30-detail.html>`_.
31
-
Once connected, you can control the speed direction and up to 29 DCC functions of your DCC enabled locomotives (locos). From one to six locos or consists / multiple units can be controlled at the same time.
31
+
Once connected, you can control the speed direction and up to 32 DCC functions of your DCC enabled locomotives (locos). From one to six locos or consists / multiple units can be controlled at the same time.
32
32
You can easily create and edit on-the-fly consists / multiple units (software-defined).
33
33
You can also control layout power, turnouts/points, routes, and access JMRI web panels and windows.
0 commit comments