From f538807b5d460c7bedce9acc74b3b3e12e6afde7 Mon Sep 17 00:00:00 2001 From: taban Date: Fri, 15 May 2026 00:11:46 +0200 Subject: [PATCH] =?UTF-8?q?le=20truc=20que=20t'a=20chang=C3=A9?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- Article_Scientifique/logiciel.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Article_Scientifique/logiciel.tex b/Article_Scientifique/logiciel.tex index 544d45e..b64ed6b 100644 --- a/Article_Scientifique/logiciel.tex +++ b/Article_Scientifique/logiciel.tex @@ -132,7 +132,7 @@ This risk could be patched by developing a VESC application for the VESC control \subsection{VESC Compiling} As mentioned, we have been able to compile the VESC tool and the VESC firmware. This firmware has been put onto an STM32F4xx Discovery card. This card uses the same chip as the aforementioned ``Cheap FOCer'' project. The thought was that using something with the same chip would facilitate the switch from the discovery card to a PCB with the same target. -However, this choice posed several obstacles for our progress on the topic of cybersecurity. We will nonetheless summarise what we have learned for you and propose some additional work for the future. The challenges we encountered were the following: The lack of bluetooth capabilities. We did not have a module with BLE either. We had access to a HC-05 module, but that only allows for a normal Bluetooth version 2.0 protocol and would require further work on a bridge to UART by using an esp8622 that we had as well. We propose that the next group has access to a VESC controller from the beginning, as well as a motor we could control. This could be in cooperation with the MAD, as the MAD could propose some models they're interested in. +However, this choice posed several obstacles for our progress on the topic of cybersecurity. We will nonetheless summarise what we have learned and propose some additional work for the future. The challenges we encountered were the following: The lack of bluetooth capabilities. We did not have a module with BLE either. We had access to a HC-05 module, but that only allows for a normal Bluetooth version 2.0 protocol and would require further work on a bridge to UART by using an esp8622 that we had as well. We propose that the next group has access to a VESC controller from the beginning, as well as a motor we could control. This could be in cooperation with the MAD, as the MAD could propose some models they're interested in. We also found that the information on the VESC is scattered around the internet. The resources is also sometimes based on a Debian-based Linux system which adds more work for someone using another distribution of Linux. This could hinder the implementation facility for new users. We struggled particularly with the Qt packages for positioning and game pad. We would therefore recommend the use of a Debian-based Linux system for the computer working with the VESC for the MAD associates.