IMPROVEMENT: rename write/read of FC params to upload/download of par…

…ameters

ARCHITECTURE.md

@@ -12,7 +12,7 @@ This list of functionalities provides a comprehensive overview of the software's
 
 - The software must allow users to view and manage drone parameters.
 - Users should be able to select an intermediate parameter file from a list of available files.
-- The software must display a table of parameters with columns for the parameter name, current value, new value, unit, write to flight controller, and change reason.
+- The software must display a table of parameters with columns for the parameter name, current value, new value, unit, upload to flight controller, and change reason.
 - The software must validate the new parameter values and handle out-of-bounds values gracefully, reverting to the old value if the user chooses not to use the new value.
 - The software must save parameter changes to both the flight controller and the intermediate parameter files
 
@@ -21,18 +21,18 @@ This list of functionalities provides a comprehensive overview of the software's
 - The software must support communication with the drone's flight controller using MAVlink and FTP over MAVLink protocols.
 - The software must handle the encoding and decoding of messages according to the specified protocols.
 - The software must allow users to tune drone parameters.
-- Users should be able to write selected parameters to the flight controller and advance to the next intermediate parameter file.
+- Users should be able to upload selected parameters to the flight controller and advance to the next intermediate parameter file.
 - The software must provide a mechanism to reset the ArduPilot if required by the changes made to the parameters.
-- The software must make sure the parameter change communication worked by re-reading and validating that the parameter changed on the vehicle.
+- The software must make sure the parameter change communication worked by re-downloading and validating that the parameter changed on the vehicle.
 
 ### 4. User Interface
 
 - The software must provide a user-friendly interface with clear navigation and controls.
 - The interface must be responsive and adapt to different screen sizes and resolutions.
 - Users should be able to toggle between showing only changed parameters and showing all parameters.
-- The software must provide feedback to the user, such as success or error messages, when performing actions like writing parameters to the flight controller.
-- Users should be able to skip to the next parameter file without writing changes.
-- The software must ensure that all changes made to entry widgets are processed before proceeding with other actions, such as writing parameters to the flight controller.
+- The software must provide feedback to the user, such as success or error messages, when performing actions like uploading parameters to the flight controller.
+- Users should be able to skip to the next parameter file without uploading changes.
+- The software must ensure that all changes made to entry widgets are processed before proceeding with other actions, such as uploading parameters to the flight controller.
 - Read-only parameters are displayed in red, Sensor Calibrations are displayed in yellow and non-existing parameters in blue
 - Users should be able to edit the new value for each parameter directly in the table.
 - Users should be able to edit the reason changed for each parameter directly in the table.

BLOG-discuss2.md

@@ -17,7 +17,7 @@ After it is set, do another flight and [check that the windspeed and direction a
 
 Follow [ArduCopter's baro compensation Wiki](https://ardupilot.org/copter/docs/airspeed-estimation.html#barometer-position-error-compensation) and/or use the [Lua script provided by Yuri in the forum](https://discuss.ardupilot.org/t/scripting-copter-wind-estimation-baro-compensation-tuning/98470/).
 
-Use *ArduPilot Methodic Configurator* to edit and write the `39_barometer_compensation.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `39_barometer_compensation.param` file to the FC.
 
 Now do the flight to collect the data and analyze the logs to see if the barometer is correctly compensated and insensitive to wind.
 
@@ -30,25 +30,25 @@ Documentation is available on [Fabian Bredemeier's Identification of a multicopt
 
 ## Roll rate mathematical model
 
-Use *ArduPilot Methodic Configurator* to edit and write the `40_system_id_roll.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `40_system_id_roll.param` file to the FC.
 
 Now do the flight to collect the data for the roll rate system identification.
 
 ## Pitch rate mathematical model
 
-Use *ArduPilot Methodic Configurator* to edit and write the `41_system_id_pitch.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `41_system_id_pitch.param` file to the FC.
 
 Now do the flight to collect the data for the pitch rate system identification.
 
 ## Yaw rate mathematical model
 
-Use *ArduPilot Methodic Configurator* to edit and write the `42_system_id_yaw.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `42_system_id_yaw.param` file to the FC.
 
 Now do the flight to collect the data for the yaw rate system identification.
 
 ## Thrust mathematical model
 
-Use *ArduPilot Methodic Configurator* to edit and write the `43_system_id_thrust.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `43_system_id_thrust.param` file to the FC.
 
 Now do the flight to collect the data for the thrust system identification.
 
@@ -58,31 +58,31 @@ This describes how to use IAV's multi-objective optimization to achieve even bet
 
 One other approach is described by Bill Geyer in his Blog post: [Predicting Closed Loop Response For Faster Autotune](https://discuss.ardupilot.org/t/predicting-closed-loop-response-for-faster-autotune/75096).
 
-Use *ArduPilot Methodic Configurator* to edit and write the `44_analytical_pid_optimization.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `44_analytical_pid_optimization.param` file to the FC.
 
 # 14. Productive configuration
 
 Some changes should be made for everyday productive operation.
 
-Use *ArduPilot Methodic Configurator* to edit and write the `45_everyday_use.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `45_everyday_use.param` file to the FC.
 
 # 15. Position controller
 
 The most inner *angle rate* and *angle* control loops have been tuned. Now let's tune the position controller.
 
-Use *ArduPilot Methodic Configurator* to edit and write the `46_position_controller.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `46_position_controller.param` file to the FC.
 
 # 16. Precision land
 
 These are **optional**, and only make sense if you have extra hardware on your vehicle to support it.
 
-Use *ArduPilot Methodic Configurator* to edit and write the `47_precision_land.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `47_precision_land.param` file to the FC.
 
 # 17. Guided operation without RC transmitter
 
 These are **optional**, and only make sense if you do beyond visual line-of-sight (BVLOS) autonomous flights using a companion computer.
 
-Use *ArduPilot Methodic Configurator* to edit and write the `48_guided_operation.param` file to the FC.
+Use *ArduPilot Methodic Configurator* to edit and upload the `48_guided_operation.param` file to the FC.
 
 # 18. Conclusion