Added more details to section 6

6-asyn-troubleshooting.md

@@ -64,20 +64,70 @@ This launches **asynRecord.ui**:
 
 The commands used by the virtual motor controller are documented [here](https://git.aps.anl.gov/practical_beamline_controls_training/session_2/motorVMC#command-reference).
 
-Do the following:
+Connect to the IOC's console
+```
+$ ./softioc/xxx.sh console
+```
+
+Turn **traceIODriver** On:
+
+![screenshot of asynRecord.ui](images/asynRecord-traceIODriver.png)
+
+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
 
-### 6.4 "Upgrade" the Virtual Motor Controller to a newer firmware.
+#### 6.4 Stop the IOC
+
+Exit the IOC from the IOC shell:
+
+```
+kmp> exit
+```
+
+<details>
+<summary>alternate approach</summary>
+
+Disconnect from the IOC:
+```
+kmp> ctrl+a, ctrl+d
+```
+
+Then stop the IOC:
+```
+$ ./softioc/xxx.sh stop
+```
+</details>
+
+### 6.5 "Upgrade" the Virtual Motor Controller to a newer firmware.
+
+#### 6.5.1 Kill server.py
+
+Type `ctrl+c` in the xterm window or click the `X` in the corner of the window.
 
-#### 6.4.1 Stop the IOC
+#### 6.5.2 Run server-new-fw.py
 
-#### 6.4.2 Kill server.py
+```
+$ xterm -e "${SUPPORT_DIR}/motorVMC/python/server-new-fw.py -p 33333" &
+```
+<details>
+<summary>output</summary>
 
-#### 6.4.3 Run server-new-fw.py
+```
+Listening on port 33333
+```
+</details>
+
+### 6.6 Run the IOC
+
+Run the IOC
+
+```
+$ ./softioc/xxx.sh run
+```
 
-#### 6.4.4 Start the IOC
+### 6.7 Observe the motor behavior with the new firmware
 
 ## [The End](README.md)