Merge branch 'main' into external to pull in improvements to the

instructions through commit 5acb35e9

5-Add-virtual-motors.md

@@ -375,6 +375,8 @@ Options:
 
 #### 5.10.2 Start servery.py in a different terminal window
 
+Reminder: the port argument passed to the `-p` option must match the value of `VMC_PORT` chosen in [step 5.7.2](5-Add-virtual-motors.md#572-modify-iocshvmccmd)
+
 ```
 $ xterm -e "${SUPPORT_DIR}/motorVMC/python/server.py -p 33333" &
 ```

6-asyn-troubleshooting.md

@@ -66,7 +66,7 @@ The **traceMask** determines which messages are printed on the IOC's console:
 * **traceError** should always be on
 * **traceIODriver** is useful for looking at serial/ethernet communication (when connected to the correct asyn port)
 
-The **traceIOMask** deterines how the messages are printed on the IOC's console:
+The **traceIOMask** determines how the messages are printed on the IOC's console:
 * **traceIOASCII** prints the messages as ASCII strings (this works well for messages that only include symbols that appear on a keyboard)
 * **traceIOEscape** prints the messages and unprintable characters using escape sequences (starting with a backslash)
 * **traceIOHex** prints the messages as a series of byte values in hexadecimal (without the **0x** prefix)
@@ -88,9 +88,13 @@ Turn **traceIODriver** on:
 
 Do the following and observe the commands on the IOC's console:
 
-* Note the commands sent while idle polling
-* Move a motor and look for the MV command
-* Stop a motor and look for the AB command
+* Note the commands sent while idle polling: `POS` and `ST`
+* Move a motor and look for the `MV` command
+* Stop a motor and look for the `AB` command
+
+Typing `ctrl+a, [` will cause screen to enter copy/scrollback mode at which point the arrow keys can be used to navigate up to commands that scrolled off the screen.  More info about screen's copy/scrollback mode can be found [here](https://www.gnu.org/software/screen/manual/html_node/Copy.html).
+
+Note: The **Abort** button at the bottom of **motorx_all.ui** writes to an allstop PV, NOT directly to the motor record's `STOP` field; the motor has to be moving for the **Abort** button to cause the `AB` command to be sent to the controller.
 
 ### 6.4 Synchronize the terminators on asynOctet.ui
 
@@ -146,6 +150,8 @@ Type `ctrl+c` in the xterm window or click the `X` in the corner of the window.
 
 #### 6.7.2 Run server-new-fw.py
 
+Reminder: the port argument passed to the `-p` option must match the value of `VMC_PORT` chosen in [step 5.7.2](5-Add-virtual-motors.md#572-modify-iocshvmccmd)
+
 ```
 $ xterm -e "${SUPPORT_DIR}/motorVMC/python/server-new-fw.py -p 33333" &
 ```
@@ -254,7 +260,7 @@ When the position is queried manually, the I/O status and severity return to `NO
 
 ### 6.14 Solve the communication problem
 
-IOC's configuration needs to be modified so the change to the input terminator persists across IOC restarts.  Stop the IOC to get the command prompt back.
+Autosave is saving the new input terminator, but the IOC's configuration should still be modified so the configuration is consistent with the autosaved values.  Stop the IOC to get the command prompt back.
 
 ```
 kmp> exit