added missing chapters
This commit is contained in:
@ -55,8 +55,29 @@ This subsection elaborates the fundamental building blocks of the program that a
|
||||
\centering
|
||||
\includegraphics[width=0.8\textwidth]{./design/ProcessOverview}
|
||||
\caption{Overview of the communication and processing process between the remote controller and the local processor.}
|
||||
\label{fig:processoverview}
|
||||
\end{figure}
|
||||
|
||||
With the objective of creating a marketable commercial product in mind, the process flow was designed for ease-of-use and ease-of-configuration for the end-user. This is the justification for implementing a remote controller that allows the setup to be remotely configured once installed.
|
||||
|
||||
While \autoref{fig:processoverview} gives a brief overview of the inter-relationship of the remote and local sides in the complete process, it is here further elaborated:
|
||||
\begin{enumerate}
|
||||
|
||||
\item \textbf{Transmission of Raw Data:} Upon first startup, the local processing software immediately begins to broadcast the raw sensor data. This data can then be subscribed to by a remote controller.
|
||||
|
||||
\item \textbf{Remote Configuration:} Once the remote devices has subscribed to the raw data broadcast, it will be previewed on the FlowRemote GUI interface. See \autoref{fig:flowremote} for an overview of the FlowRemote interface.
|
||||
\begin{enumerate}
|
||||
\item \textbf{Image Pre-Processing:} The engineer then pre-processes the image --- rotating, skewing and cropping --- the conveyor belt in the sensor image is vertically aligned and the perspective has been corrected.
|
||||
\item \textbf{Calibration and Fitting:} Now the engineer may select a single layer or slice of the sensor image which will be used to fit for the conveyor belt curve. The fitting parameters are selected, and the calibration is saved.
|
||||
\item \textbf{Belt Parameters:} In order to correctly determine the band velocity and volume flow --- see \autoref{sec:dataproc} --- the conveyor belt parameters such as visible length and width need to be provided.
|
||||
\end{enumerate}
|
||||
|
||||
\item \textbf{Transmission of Configuration Parameters:} The parameters that were configured in the previous step are then transmitted back to the local processor, FlowPi, and local processing mode is then engaged.
|
||||
|
||||
\item \textbf{Local Processing:} In local processing mode, raw data is no longer transmitted for performance purposes. The sensor data is directly processed on the Raspberry Pi, and the outputs are delivered over Profinet to the Profinet Controller.
|
||||
|
||||
\end{enumerate}
|
||||
|
||||
\section{Software Architecture}\label{sec:softarch}
|
||||
\begin{figure}[h]
|
||||
\centering
|
||||
@ -108,7 +129,8 @@ The FlowRemote part of the program is designed in order to allow easier configur
|
||||
As described in \autoref{fig:flowremote}, FlowRemote allows the engineer to remotely preview the raw sensor data, run pre-processing on it, configure the processing parameters and deliver those back to the local processor running on the Raspberry Pi.
|
||||
|
||||
|
||||
\section{Data Processing Details}
|
||||
\section{Data Processing and Outputs}\label{sec:dataproc}
|
||||
|
||||
|
||||
\section{Housing}
|
||||
Prototype housing, ideal housing.
|
Reference in New Issue
Block a user