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
Operation Mode CV Programming is available form the 'CV Programming' screen, when 'Program on Main (Operation Mode)' is selected in the drop down list at the top of the screen.
156
+
Operation Mode CV Programming is available from the 'CV Programming' screen, when 'Program on Main (Operation Mode)' is selected in the drop down list at the top of the screen.
157
157
158
158
Operation Mode CV Programming ONLY allows you to *Write* CVs.
159
159
@@ -497,14 +497,33 @@ View log
497
497
498
498
Accessed from any of the main screens via :menuselection:`Menu --> View Log`.
499
499
500
-
This screen allows you to view the internal Engine Driver log of events.
501
-
This is sometimes useful for analysing problems.
500
+
This screen allows you to view the internal EX-Toolbox log of events. (referend to as 'logcat').
502
501
503
502
The option to `Start recording to file` creates a user-accessible file that can be sent to the |EX-TB| app developers to assist you in resolving a problem.
504
-
The file will be located on your mobile phone at:
505
-
Internal storage ``/Android/data/dcc_ex.toolbox/files`` |br|\ and will be named something like: ``logcat9999999999999.txt``
506
503
507
-
Enable the preference to include the timestamp on each line of the log.
504
+
The file will be located on your Android device/phone at:
505
+
Internal storage ``/Android/data/dcc_ex.ex_toolbox/files`` |br|\ and will be named something like: ``logcat9999999999999.txt``
506
+
507
+
Optionally enable the preference to include the timestamp on each line of the log.
508
+
509
+
Saving a Log File
510
+
-----------------
511
+
512
+
To record a log file in |EX-TB|....
513
+
514
+
1. Start |EX-TB|.
515
+
2. From the menu, select :guilabel:`View Log`
516
+
3. Click :guilabel:`Start recording to a file`
517
+
4. Click :guilabel:`Close``
518
+
5. Attempt whatever is causing the problem a few times
519
+
6. Exit |EX-TB|
520
+
7. Connect a USB cable to your device/phone and PC
521
+
8. Allow access if the device/phone asks.
522
+
9. In some versions of Android you may also need to change the connection type on the device/phone from 'charging' to 'file transfer'
523
+
10. Open a file manager and find the connected device/phone
524
+
11. Browse down to the folder ...\Internal shared storage\Android\data\dcc_ex.ex_toolbox\files
525
+
12. Find the most recent file that looks like ``logcatxxxxxxxxxxxxx.txt`` e.g. logcat1699833098998.txt
526
+
13. Attach that file to a message in discord using the :guilabel:`+` button on the row of the message content```
508
527
509
528
510
529
About
@@ -523,7 +542,7 @@ This screen displays
523
542
Connecting via JMRI
524
543
===================
525
544
526
-
|EX-TB| can't normally connect to a |EX-CS| through |JMRI|, however it is possible if you ``Load DCC== over TCP Server`` in the 'DCC-EX' menu in |JMRI|, then connect |EX-TB| to the additional server that is presented.
545
+
|EX-TB| can't normally connect to a |EX-CS| through |JMRI|, however it is possible if you ``Load DCC++ over TCP Server`` in the 'DCC-EX' menu in |JMRI|, then connect |EX-TB| to the additional server that is presented in Connection screen. It will be the same name as your JMRI Railroad name, but will have " [DCC-EX]" appended to it.
All the Android based throttle apps listed can be run on Microsoft Windows PCs.
10
+
All the Android based throttle apps listed can be run on Microsoft Windows PCs and Apple Silicon Macs using `BlueStacks <https://www.bluestacks.com/>`_ |EXTERNAL-LINK|.
11
11
12
-
There are a least two methods:
13
-
14
-
- Using *BlueStacks*
15
-
- Using *Windows Subsystem for Android*
16
12
17
13
BlueStacks
18
14
==========
@@ -21,7 +17,7 @@ The `BlueStacks <https://www.bluestacks.com/>`_ |EXTERNAL-LINK| app allows you t
21
17
22
18
It has the advantages of:
23
19
24
-
- Works on most recent Windows PCs
20
+
- Works on most recent Windows PCs and Apple Silicon Macs
25
21
- User Friendly installation of apps
26
22
- Allows you to run multiple instances of same app at the same time
27
23
@@ -30,83 +26,3 @@ Disadvantages include:
30
26
- Has advertisements
31
27
32
28
Follow the instructions on their `site <https://www.bluestacks.com/>`_ |EXTERNAL-LINK| to install BlueStacks, then get the appropriate .apk to install the throttle app you want. e.g. The Engine Driver .apk is available from the `Engine Driver site <https://enginedriver.mstevetodd.com/downloads>`_ |EXTERNAL-LINK|
33
-
34
-
Windows Subsystem for Android
35
-
=============================
36
-
37
-
`Windows Subsystem for Android <https://https://learn.microsoft.com/en-us/windows/android/wsa//>`_ |EXTERNAL-LINK| is a built in feature of Windows 11 that allows you to install and run most Android apps on *some* Windows PCs.
38
-
39
-
It has the advantages of:
40
-
41
-
- Built in feature of Windows 11
42
-
- No Advertisements
43
-
44
-
Disadvantages include:
45
-
46
-
- Only works of Windows 11 PCs with an SSD (not a physical Hard Drive)
47
-
- Not very user friendly installation (sideloading) of non-Amazon approved apps (i.e. the throttle apps)
48
-
- Does *not* allow you to run multiple instances of same app at the same time
49
-
50
-
Follow the `instructions here <https://www.windowscentral.com/how-sideload-android-apps-using-wsa-windows-11>`_ |EXTERNAL-LINK| (or `a slightly differnt version of instructions here <https://www.xda-developers.com/how-to-sideload-android-apps-on-windows-11/>`_ |EXTERNAL-LINK|) to setup *Windows Subsystem for Android* to allow 'sideloading'.
51
-
52
-
You will also need to install the `SDK Platform Tools <https://developer.android.com/tools/releases/platform-tools>`_ |EXTERNAL-LINK|.
53
-
54
-
You will also need to get the appropriate .apk to install the throttle app you want. e.g. The Engine Driver .apk is available from the `Engine Driver site <https://enginedriver.mstevetodd.com/downloads>`_ |EXTERNAL-LINK|
55
-
56
-
|hr-dashed|
57
-
58
-
Refer to pages linked above for details but a summary of the process for installing with Windows Subsystem for Android is:
59
-
60
-
# Install *Windows Subsystem for Android*
61
-
# Download the *SDK Platform Tools*
62
-
63
-
# Extract the files from the zip file and record the folder there are in |BR| e.g. C:\Users\your_username\Downloads\platform-tools\
64
-
65
-
# Download the APK you want to install
66
-
67
-
# Note the name of the file where you saved it |BR| e.g. ``C:\Users\your_username\Downloads\EngineDriver-2.36.177.apk``
68
-
69
-
# Start *Windows Subsystem for Android*
70
-
71
-
# Enable the Developer option
72
-
73
-
# click the overflow menu (the three bars) in the top left
74
-
# Then ``Advanced settings``
75
-
# Turn on ``Developer mode``
76
-
# Note the ip address and port on the same row (normally 127.0.0.1:58526)
77
-
78
-
# Start a command prompt with Administrator privileges
79
-
80
-
# Click :guilabel:`Start`
81
-
# Type in ``CMD`` or ``command``
82
-
# Right click on ``Command Prompt`` from the found list and select ``Run as Administrator``
83
-
# Click :guilabel:`Yes` when it asks
84
-
85
-
# Connect the PC to the Windows Subsystem for Android
86
-
87
-
# Enter the command |BR| ``<extracted_location>\adb connect <ip_address_&_port>`` |BR| where **<extracted_location>** is the folder you you extracted the *SDK Platform Tools* to above, and |BR| **<ip_address_&_port>** are the ip address and port that you recorded above |BR| e.g. ``C:\Users\your_username\Downloads\platform-tools\adb connect 127.0.0.1:58526``.
88
-
# You should see a request to 'Allow ADB debugging'. Click :guilabel:`Allow`
89
-
90
-
# If you don't see the request. |BR| e.g. you see something like ``cannot connect to 127.0.0.1:58526: No connection could be made because the target machine actively refused it. (10061)``
91
-
92
-
# In the 'Windows Subsystem for Android' app (on the PC), click ``Turn Off``
93
-
# Then open the 'Amazon Appstore' (that you should have installed as part of installing Windows Subsystem for Android). this will automatically restart the subsystem.
94
-
# Enter the adb connect command again.
95
-
96
-
# Note: it is normal (not sure why) to see ``failed to authenticate to 127.0.0.1:58526``
97
-
98
-
# Install the sdk.
99
-
100
-
# enter the command |BR| ``<extracted_location>\adb install <apk_file_location>`` |BR| where **<extracted_location>** is the folder you you extracted the *SDK Platform Tools* to above, and |BR| **<apk_file_location>** is the floaction and name of the downlaoded apk above. |BR| e.g. ``C:\Users\your_username\Downloads\platform-tools\adb install C:\Users\your_username\Downloads\EngineDriver-2.36.177.apk``
101
-
102
-
# Close the command prompt windows
103
-
104
-
|hr-dashed|
105
-
106
-
To run the app once installed
107
-
108
-
# Click :guilabel:`Start`
109
-
# Click :guilabel:`all Apps`
110
-
# Scroll down to ``Engine Driver`` (or whatever app you installed) and click it.
111
-
# First use only: When **Engine Driver** start the first time you will be asked a number of questions
112
-
# When you get the "Connect" screen, **Engine Driver** cannot 'discover' the |EX-CS|, so you will need to enter the IP address and port, then click :guilabel:`Connect`
This is an Android and iOS App. One of the major benefits of DCC-EX CAB is that it speaks the |DCC-EX Native Commands| natively. This means it is fast and can take advantage of some features that exist in the |EX-CS| not implemented in other APIs.
21
+
22
+
You can find it in the Google Play Store: `DCC-EX CAB Android App <https://play.google.com/store/apps/details?id=com.gothicmaestro.dccexcab>`_ |EXTERNAL-LINK|
23
+
24
+
You can find it in the Apple App Store: `DCC-EX CAB iOS App <https://apps.apple.com/us/app/dcc-ex-cab/id6695754417?uo=2>`_ |EXTERNAL-LINK|
0 commit comments