From 84e9f1ae624e6209aeec14ae18792ce1b6939406 Mon Sep 17 00:00:00 2001 From: "Robin P. Clark" Date: Tue, 31 Jul 2012 08:45:29 +0100 Subject: [PATCH] tidying --- papers/fmea_software_hardware/software_fmea.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/papers/fmea_software_hardware/software_fmea.tex b/papers/fmea_software_hardware/software_fmea.tex index 4939de8..17b1084 100644 --- a/papers/fmea_software_hardware/software_fmea.tex +++ b/papers/fmea_software_hardware/software_fmea.tex @@ -360,7 +360,7 @@ Let us assume the {\ft} detection is via a \ohms{220} resistor, and that we read from an ADC into the software. Let us define any value outside the 4mA to 20mA range as an error condition. % -As a voltage, we use ohms law~\cite{aoe} to determine the voltage ranges: $V=IR$, $0.004A * \ohms{220} = 0.88V$ +As a voltage, we use ohms law~\cite{aoe} to determine the voltage ranges: $V=IR$, $$0.004A * \ohms{220} = 0.88V $$ and $$0.020A * \ohms{220} = 4.4V \;.$$ % Our acceptable voltage range is therefore @@ -660,8 +660,8 @@ and these are described in~\cite{sfmeainterface}. %An interface FMEA is performed in table~\ref{hwswinterface}. % The hardware to software interface for the {\ft} example is handled -by the 'C' function $read\_ADC()$. -~\cite{sfmeaauto}. +by the 'C' function $read\_ADC()$ +(see code sample in figure~\ref{fig:code_read_ADC}). % % An FMEA of the `software~medium' is given in table~\ref{tbl:sfmeaup}. \paragraph{Timing and Synchronisation.}