diff --git a/Article_Scientifique/Figures/Motor_currents.png b/Article_Scientifique/Figures/Motor_currents.png new file mode 100644 index 0000000..c988e6f Binary files /dev/null and b/Article_Scientifique/Figures/Motor_currents.png differ diff --git a/Article_Scientifique/main.aux b/Article_Scientifique/main.aux index 3261566..ed830b8 100644 --- a/Article_Scientifique/main.aux +++ b/Article_Scientifique/main.aux @@ -75,10 +75,13 @@ \@writefile{lof}{\contentsline {figure}{\numberline {2}{\ignorespaces Position tracking error between bicycle and cargo cart.}}{4}{figure.2}\protected@file@percent } \newlabel{fig:tracking-error}{{2}{4}{Position tracking error between bicycle and cargo cart}{figure.2}{}} \@writefile{toc}{\contentsline {subsubsection}{\numberline {\mbox {IX-A}2}Experimental Load Characterization}{4}{subsubsection.9.1.2}\protected@file@percent } -\@writefile{toc}{\contentsline {section}{\numberline {X}Discussion}{4}{section.10}\protected@file@percent } \bibstyle{IEEEtran} \bibdata{PIR_MadMax3} \bibcite{patil_analysis_2025}{1} +\@writefile{lof}{\contentsline {figure}{\numberline {3}{\ignorespaces Measured motor current under three loading conditions.}}{5}{figure.3}\protected@file@percent } +\newlabel{fig:motor-currents}{{3}{5}{Measured motor current under three loading conditions}{figure.3}{}} +\@writefile{toc}{\contentsline {section}{\numberline {X}Discussion}{5}{section.10}\protected@file@percent } +\@writefile{toc}{\contentsline {section}{\numberline {XI}Conclusion/Summary}{5}{section.11}\protected@file@percent } \bibcite{li_quantitative_2019}{2} \bibcite{mohammd_taher_new_2021}{3} \bibcite{gieras_modern_2023}{4} @@ -88,6 +91,5 @@ \bibcite{lee_advanced_2001}{8} \bibcite{b1}{9} \bibcite{b2}{10} -\@writefile{toc}{\contentsline {section}{\numberline {XI}Conclusion/Summary}{5}{section.11}\protected@file@percent } -\@writefile{toc}{\contentsline {section}{References}{5}{section*.2}\protected@file@percent } -\gdef \@abspage@last{5} +\@writefile{toc}{\contentsline {section}{References}{6}{section*.2}\protected@file@percent } +\gdef \@abspage@last{6} diff --git a/Article_Scientifique/main.log b/Article_Scientifique/main.log index 350909a..5a5a868 100644 --- a/Article_Scientifique/main.log +++ b/Article_Scientifique/main.log @@ -1,4 +1,4 @@ -This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) (preloaded format=pdflatex 2026.3.16) 12 MAY 2026 22:57 +This is pdfTeX, Version 3.141592653-2.6-1.40.22 (TeX Live 2022/dev/Debian) (preloaded format=pdflatex 2026.3.16) 13 MAY 2026 18:32 entering extended mode restricted \write18 enabled. %&-line parsing enabled. @@ -535,15 +535,21 @@ Underfull \vbox (badness 1354) has occurred while \output is active [] <./Figures/sys_dyn_matlab.png, id=202, 430.2474pt x 226.6869pt> File: ./Figures/sys_dyn_matlab.png Graphic file (type png) -Package pdftex.def Info: ./Figures/sys_dyn_matlab.png used on input line 372. +Package pdftex.def Info: ./Figures/sys_dyn_matlab.png used on input line 373. (pdftex.def) Requested size: 252.0pt x 132.77559pt. <./Figures/error_fig.png, id=206, 509.7444pt x 328.5876pt> File: ./Figures/error_fig.png Graphic file (type png) -Package pdftex.def Info: ./Figures/error_fig.png used on input line 398. +Package pdftex.def Info: ./Figures/error_fig.png used on input line 399. (pdftex.def) Requested size: 252.0pt x 162.44328pt. [4 <./Figures/sys_dyn_matlab.png> <./Figures/error_fig.png (PNG copy)>] -(./main.bbl +<./Figures/Motor_currents.png, id=218, 499.6266pt x 328.1058pt> +File: ./Figures/Motor_currents.png Graphic file (type png) + +Package pdftex.def Info: ./Figures/Motor_currents.png used on input line 421. +(pdftex.def) Requested size: 252.0pt x 165.48434pt. + +(./main.bbl [5 <./Figures/Motor_currents.png (PNG copy)>] Underfull \hbox (badness 1490) in paragraph at lines 97--99 []\OT1/ptm/m/n/8 ------, ``lispbm in vesc,'' []$https : / / github . com / vedd erb / bldc / tree / master / @@ -561,18 +567,20 @@ Before submitting the final camera ready copy, remember to: uses only Type 1 fonts and that every step in the generation process uses the appropriate paper size. -[5] (./main.aux) +[6 + +] (./main.aux) Package rerunfilecheck Info: File `main.out' has not changed. (rerunfilecheck) Checksum: 4840E35989685C6A900816FED622AB01;6851. ) Here is how much of TeX's memory you used: - 14792 strings out of 478287 - 281340 string characters out of 5849289 - 566325 words of memory out of 5000000 - 32760 multiletter control sequences out of 15000+600000 + 14802 strings out of 478287 + 281591 string characters out of 5849289 + 566416 words of memory out of 5000000 + 32767 multiletter control sequences out of 15000+600000 505639 words of font info for 98 fonts, out of 8000000 for 9000 1141 hyphenation exceptions out of 8191 - 70i,8n,79p,470b,753s stack positions out of 5000i,500n,10000p,200000b,80000s + 70i,8n,79p,470b,903s stack positions out of 5000i,500n,10000p,200000b,80000s {/usr/share/texlive/texmf-dist/fonts/enc/dvips/base/8r.enc} -Output written on main.pdf (5 pages, 244634 bytes). +Output written on main.pdf (6 pages, 315176 bytes). PDF statistics: - 294 PDF objects out of 1000 (max. 8388607) - 261 compressed objects within 3 object streams - 55 named destinations out of 1000 (max. 500000) - 299 words of extra memory for PDF output out of 10000 (max. 10000000) + 301 PDF objects out of 1000 (max. 8388607) + 266 compressed objects within 3 object streams + 57 named destinations out of 1000 (max. 500000) + 304 words of extra memory for PDF output out of 10000 (max. 10000000) diff --git a/Article_Scientifique/main.pdf b/Article_Scientifique/main.pdf index b27a9dd..280851f 100644 Binary files a/Article_Scientifique/main.pdf and b/Article_Scientifique/main.pdf differ diff --git a/Article_Scientifique/main.tex b/Article_Scientifique/main.tex index 0fe5a0f..e791566 100644 --- a/Article_Scientifique/main.tex +++ b/Article_Scientifique/main.tex @@ -5,7 +5,7 @@ \usepackage{amsmath,amssymb,amsfonts} \usepackage{algorithmic} \usepackage{url} -\usepackage{hyperref} +\usepackage[hidelinks]{hyperref} \usepackage{placeins} \usepackage{siunitx} \usepackage{graphicx} @@ -90,7 +90,7 @@ bikes while significantly improving repairability. \end{abstract} \begin{IEEEkeywords} -VESC Project, Brushless DC motor, Field Oriented Control, Trapezoidal commutation, Low-Tech, e-bike. +VESC, Brushless DC motor, Field Oriented Control, Trapezoidal commutation, Low-Tech, PID-Control. \end{IEEEkeywords} \section{Introduction} @@ -114,7 +114,7 @@ We also argue the need for general public's safety when it comes to these bikes, \section{Related Work} \subsection{Modeling of BLDC Motor} -The electromechanical model of a BLDC motor is foundational for understanding its behavior under different control +The electromechanical model of a BLDC (Brushless DC) motor is foundational for understanding its behavior under different control schemes. BLDC motors are categorized by their back-electromotive force (back-EMF) waveform: trapezoidal or sinusoidal. This distinction is crucial, as the trapezoidal shape inherently leads to torque ripple when the supplied phase currents are not perfectly aligned, directly influencing the choice and effectiveness of the control strategy @@ -185,6 +185,7 @@ repairability constraints. To date, researchers have not addressed the challenge be locally fabricated, repaired with standard components, and secured against unauthorised wireless access requirements that are critical for decentralised, community-operated fleets. + \section{Aim and Research Objectives} This work presents the design and implementation of a motor control system for electric bicycles and cargo transport applications developed within the context of the Manufacture Autonome Décentralisée (MAD) initiative at INSA Toulouse. @@ -401,6 +402,41 @@ equilibrium position, demonstrating stable closed-loop behaviour and satisfactor \end{figure} \subsubsection{Experimental Load Characterization} +Experimental tests were conducted on flat terrain in order to evaluate the influence of mechanical load on the motor +current consumption of the cargo cart system. The system was powered using a \SI{48}{\volt} battery pack. + +Current measurements were acquired using an Analog Discovery 2 connected to a computer running the WaveForms software +environment. A current clamp probe was used to measure the motor current, and the signals were sampled at +\SI{1}{\kilo\hertz}. + +During each test, the throttle command was set to its maximum value in order to produce the highest possible +acceleration. Once the maximum speed was reached, the motor current naturally decreased and stabilised as the motor +only compensated for rolling resistance and friction effects. + +Three loading conditions were investigated corresponding approximately to one, two, and three passengers inside the +cargo cart. The motor current measured during these experiments is shown in Fig.~\ref{fig:motor-currents}. + +\begin{figure}[!h] + \centering + \includegraphics[width=\linewidth]{./Figures/Motor_currents.png} + \caption{Measured motor current under three loading conditions.} + \label{fig:motor-currents} +\end{figure} + +The results show a significant current peak during the acceleration phase, reaching the controller limit of +approximately \SI{25}{\ampere}. After this transient phase, the current decreases and converges toward a lower +steady-state value corresponding mainly to friction and resistive force compensation. + +As expected, higher loading conditions resulted in higher steady-state current consumption, indicating an increase in +the required motor torque. In addition, the duration during which the current remained close to the maximum controller +limit also increased with heavier loads, reflecting the longer acceleration time required to reach steady-state +operation. +These variations are mainly attributed to terrain irregularities, throttle response fluctuations, and limitations +associated with the measurement setup and current probe acquisition chain. + +However, due to the absence of direct velocity measurements during the experiments, only qualitative observations could +be extracted from these tests. Consequently, a precise estimation of dynamic friction parameters and energy efficiency +could not be achieved. % ******************************** DISCUSSION **************************************************************************