ROVER - hono_interaction: stdout of curl is discarded to /dev/null now.
A4MCAR - readme indentation is corrected.

Signed-off-by: Mustafa Ozcelikors <mozcelikors@gmail.com>
diff --git a/a4mcar/readme.txt b/a4mcar/readme.txt
index 74ed088..b33e25e 100644
--- a/a4mcar/readme.txt
+++ b/a4mcar/readme.txt
@@ -80,43 +80,43 @@
 		
 	The repository should have the following main folders:
 	
-	web_interface :				The web interface that is developed for A4MCAR project which is used to control 
-								A4MCAR over remote Wi-Fi connection. 
+	web_interface :			The web interface that is developed for A4MCAR project which is used to control 
+					A4MCAR over remote Wi-Fi connection. 
 								
-								In order to set up web_interface, run the setup script:
-								web_interface/setup_web_interface.sh
-										
-								In order to run the web_interface correctly, the high-level modules core_reader
-								and ethernet_client should be ready and working.
-								To run the web_interface one should connect to the access point of Raspberry Pi
-								from a client computer web browser and visit 
-								http://<IP_Address>/jqueryControl2.php or http://<IP_Address>/jqueryControl.php
+					In order to set up web_interface, run the setup script:
+					web_interface/setup_web_interface.sh
+					
+					In order to run the web_interface correctly, the high-level modules core_reader
+					and ethernet_client should be ready and working.
+					To run the web_interface one should connect to the access point of Raspberry Pi
+					from a client computer web browser and visit 
+					http://<IP_Address>/jqueryControl2.php or http://<IP_Address>/jqueryControl.php
 					
 	high_level_applications :	This module consists of several high-level applications that are developed for
-								A4MCAR's high-level module (Raspberry Pi). These applications involve: 
-								touchscreen_display, core_recorder, dummy_loads, ethernet_client, and 
-								image_processing.
+					A4MCAR's high-level module (Raspberry Pi). These applications involve: 
+					touchscreen_display, core_recorder, dummy_loads, ethernet_client, and 
+					image_processing.
 								
-								In order to run the applications, respective Python files could be run or C/C++
-								binaries could be executed. Also the scripts that are located under scripts 
-								folder could be used to initialize some of the applications.
+					In order to run the applications, respective Python files could be run or C/C++
+					binaries could be executed. Also the scripts that are located under scripts 
+					folder could be used to initialize some of the applications.
 								
-								In order to set up high_level_applications module dependencies, one should run
-								the setup script and follow the instructions:
-								high_level_applications/setup_high_level_applications.sh
+					In order to set up high_level_applications module dependencies, one should run
+					the setup script and follow the instructions:
+					high_level_applications/setup_high_level_applications.sh
 									
-	models:						A4MCAR's hardware and software model with Eclipse APP4MC is located in this 
-								directory.
+	models:				A4MCAR's hardware and software model with Eclipse APP4MC is located in this 
+					directory.
 								
 	android_application:		This directory consists of the source files that belong to the A4MCAR's bluetooth
-								based driving application. The source and design files could be used in an Android
-								IDE in order to make tweaks to the application and to generate new .apk files.
+					based driving application. The source and design files could be used in an Android
+					IDE in order to make tweaks to the application and to generate new .apk files.
 								
 	low_level_applications:		low_level_applications module involves the source code for the low-level module that
-								are run using a multi-core microcontroller XMOS xCORE-200 eXplorerKIT. The low level
-								applications are responsible for tasks such as sensor driving, actuation, communication,
-								and core monitoring of the A4MCAR. The low_level_applications module could be imported
-								into xTIMEcomposer to make tweaks to the tasks.
+					are run using a multi-core microcontroller XMOS xCORE-200 eXplorerKIT. The low level
+					applications are responsible for tasks such as sensor driving, actuation, communication,
+					and core monitoring of the A4MCAR. The low_level_applications module could be imported
+					into xTIMEcomposer to make tweaks to the tasks.
 								
-	docs:						Involves documentation and Sphinx-generated how-to-setup manual.
+	docs:				Involves documentation and Sphinx-generated how-to-setup manual.
 					
\ No newline at end of file
diff --git a/rover/src/hono_interaction/hono_interaction.cpp b/rover/src/hono_interaction/hono_interaction.cpp
index 155de6c..e67eea6 100644
--- a/rover/src/hono_interaction/hono_interaction.cpp
+++ b/rover/src/hono_interaction/hono_interaction.cpp
@@ -131,7 +131,7 @@
 	strcat(buffer, tenant_name);
 
 	//To redirect pipe to prevent stdout showing all outputs generated by curl
-	strcat(buffer, " 2>curl_log"); //2>&1 would redirect to stderr, we choose to redirect to a file to be able to parse returned code
+	strcat(buffer, " 2>/dev/null"); //2>&1 would redirect to stderr, we choose to be able to parse returned code
 
 #ifdef DEBUG_DEVICE_REGISTRATION
 	//Print the command that is created
@@ -208,7 +208,7 @@
 	num_buffer[0] = 0; //Clear array
 
 	//To redirect pipe to prevent stdout showing all outputs generated by curl
-	strcat(buffer, " 2>curl_log"); //2>&1 would redirect to stderr, we choose to redirect to a file to be able to parse returned code
+	strcat(buffer, " 2>/dev/null"); //2>&1 would redirect to stderr, we choose to be able to parse returned code
 
 #ifdef DEBUG_HTTP_RESPONSE
 	//Print the command that is created
@@ -285,7 +285,7 @@
 	num_buffer[0] = 0; //Clear array
 
 	//To redirect pipe to prevent stdout showing all outputs generated by curl
-	strcat(buffer, " 2>curl_log"); //2>&1 would redirect to stderr, we choose to redirect to a file to be able to parse returned code
+	strcat(buffer, " 2>/dev/null"); //2>&1 would redirect to stderr, we choose to be able to parse returned code
 
 #ifdef DEBUG_HTTP_RESPONSE
 	//Print the command that is created