diff --git a/COSI-Measure/External_Control_Scripts/Readme.md b/COSI-Measure/External_Control_Scripts/Readme.md
index 2baeb92c38c5241db07b40b8619f5fc6acf81350..eb6a478d8ee1d02a4083c3a4a20db6a264ec6817 100644
--- a/COSI-Measure/External_Control_Scripts/Readme.md
+++ b/COSI-Measure/External_Control_Scripts/Readme.md
@@ -1,6 +1,6 @@
 # Software instructions
 
-This folder has two python scripts for automated mapping using COSI Measure. The first **cosi_gui_testbed.py** uses the original Beagle Bone Black hardware and software from Han et al. [1]. The other one **server_GUI** works under the server computer that prepares and sends the coordinates (e.g. the console with the m4i cards). An ethernet cable is needed between host (COSI Measure) and server (m4i computer).
+This folder has two python scripts for automated mapping using COSI Measure. The first **cosi_gui_testbed.py** uses the original Beagle Bone Black hardware and software from Han et al. [1]. The other one, **server_GUI.py**, works under the server computer that prepares and sends the coordinates (e.g. the console with the m4i cards). An ethernet cable is needed between host (COSI Measure) and server (m4i computer).
 
 The **cosi_gui_testbed.py** script has an individual homing option for each axis and each direction. If wanted, the buttons (x+, x- ,y+ ,y- ,z+ ,z-) can be used seperately. This has the advantage that the order of homing can be chosen, which is sometimes required if an object is within the homing area of COSI Measure to avoid collision with the probe.
 
@@ -17,14 +17,19 @@ The first one is for submillimeter precision is 2, first 3 digits are the coordi
 ```console
 netstat -tulnap  
 ```
-Then, find the PID number of python program that has the IP number “192.168.101.253”. E.g., it is 2571/python : [Instructions1.png](./COSI-Measure/External_Control_Scripts/Instructions1.png)
-
-
+Then, find the PID number of python program that has the IP number “192.168.101.253”. E.g., it is 2571/python : [Instructions1.png](./COSI-Measure/External_Control_Scripts/Instructions1.png). Type
+```console
+gdb -p PORTNUMBER #(e.g., gdb -p 2571)
+#This will attach to the process and open GDB server. Type:
+call close() 
+quit
+```
+If you see ($1=0). Then, it should be successfull. [Instructions2.png](./COSI-Measure/External_Control_Scripts/Instructions2.png)
 
 “OK” command can be sent for a connection check. COSI Measure will respond with an “ok” message if the connection is established. 
 
-Server_GUI implements the mapping. Currently cartesian mapping is supported by the GUI, which follows a snake like path. For each position, it transmits a composite pulse and calculates a worst-case vector [2]. Next, a circularly polarized, orthogonal projection and worst case transmit pulses are sent and the corresponding files are saved into a Measurements1 folder. For each position the files are saved into a folder according to the measurement number. The means of each measurement are also displayed in the GUI. Currently, creating different measurement folders was not implemented. Therefore, please check if there is an empty “Measurements1” folder in the directory.
-An arbitrary path file can also be used with the GUI. For this, a path file using the same structure from Han et al. [1] should be prepared and named as ‘PathFile.txt’. And the default coordinate values from the GUI must be kept the same. 
+**Server_GUI.py** implements the mapping. Currently cartesian mapping is supported by the GUI, which follows a snake like path. For each position, it transmits a composite pulse and calculates a worst-case vector [2]. Next, a circularly polarized, *orthogonal projection* and *worst case* transmit pulses are sent and the corresponding files are saved into a **Measurements1** folder. For each position the files are saved into a folder according to the measurement number. The means of each measurement are also displayed in the GUI. Currently, creating different measurement folders was not implemented. Therefore, please check if there is an empty **Measurements1** folder in the directory.
+An arbitrary path file can also be used with the GUI. For this, a path file using the same structure from Han et al. [1] should be prepared and named as **PathFile.txt**. And the default coordinate values from the GUI must be kept the same. 
 
 Please note that there is no limitation about the numbers that you can enter to the GUI. Therefore, make sure that the coordinates are within the boundaries that COSI measure can approach. A coordinate that is outside of the physical coordinates may damage components. The physical dimensions of the measurement probe and device under test should also be considered. It is highly encouraged to determine the customized spatial boundaries of the mapping area before any operation with COSI Measure.