<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="static/style.xsl"?><OAI-PMH xmlns="http://www.openarchives.org/OAI/2.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd"><responseDate>2026-11-22T11:28:17Z</responseDate><request verb="GetRecord" identifier="oai:uwspace.uwaterloo.ca:10012/3002" metadataPrefix="dim">https://dspacemainprd01.lib.uwaterloo.ca/server/oai/request</request><GetRecord><record><header><identifier>oai:uwspace.uwaterloo.ca:10012/3002</identifier><datestamp>2017-03-21T20:01:42Z</datestamp><setSpec>com_10012_9900</setSpec><setSpec>com_10012_1</setSpec><setSpec>col_10012_9914</setSpec><setSpec>col_10012_6</setSpec></header><metadata><dim:dim xmlns:dim="http://www.dspace.org/xmlns/dspace/dim" xmlns:doc="http://www.lyncode.com/xoai" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.dspace.org/xmlns/dspace/dim http://www.dspace.org/schema/dim.xsd">
   <dim:field mdschema="dc" element="contributor" qualifier="author" authority="571a3118-f1d7-4f44-9fe3-8a93b1d8ba3c" confidence="600">Morency, Kevin</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="accessioned">2007-05-14T13:04:50Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="available">2007-05-14T13:04:50Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="issued">2007-05-14T13:04:50Z</dim:field>
   <dim:field mdschema="dc" element="date" qualifier="submitted">2007</dim:field>
   <dim:field mdschema="dc" element="identifier" qualifier="uri">http://hdl.handle.net/10012/3002</dim:field>
   <dim:field mdschema="dc" element="description" qualifier="abstract" lang="en">In recent years, hardware-in-the-loop (HIL) simulation has assumed a prominent role&#xd;
in the vehicle development process. A physical part, which may be a prototype at any stage of development, is tested, while the rest of the vehicle is represented by a mathematical model. Vehicle models used with hardware-in-the-loop must be capable of simulating an event in less time than it takes the event to occur in reality. Fast simulation necessitates&#xd;
a model that is represented by very efficient simulation code. This thesis presents&#xd;
a procedure for automatically generating this simulation code, given a description of the&#xd;
vehicle as input.&#xd;
&#xd;
&#xd;
&#xd;
For this work, a symbolic formulation procedure based on linear graph theory and&#xd;
the principle of orthogonality is used to generate governing equations for vehicle systems;&#xd;
this procedure forms the basis of the DynaFlexPro software package. In order to generate&#xd;
simulation code for vehicle dynamics studies, the DynaFlexPro component model template&#xd;
was extended to include rules for calculating intermediate variables and rules for&#xd;
calling external functions. These changes enabled the development of a tire component&#xd;
model, known as DynaFlexPro/Tire, that adds critically important (and computationally&#xd;
efficient) blocks to the overall vehicle simulation code. The combination of DynaFlexPro&#xd;
and DynaFlexPro/Tire allows analysts to construct a model for any vehicle topology and&#xd;
gives analysts great freedom to define how tire forces and moments will be calculated.&#xd;
Simulation code describing the vehicle model is automatically generated using symbolic&#xd;
computing techniques. The accuracy of the approach was validated by comparing results&#xd;
for DynaFlexPro vehicle models to results for equivalent models developed in a&#xd;
well-established tool for vehicle dynamics simulation (MSC.ADAMS).&#xd;
&#xd;
&#xd;
&#xd;
Two different vehicle models were constructed using DynaFlexPro and DynaFlex-&#xd;
Pro/Tire: a generic 4-wheeled vehicle with independent suspension and an articulated&#xd;
forestry skidder. Both models had an open-loop topology. When appropriate modeling&#xd;
variables were selected, each model was described by a minimal set of ordinary differential&#xd;
equations (ODEs) and the simulation code generated by DynaFlexPro was capable&#xd;
of being used for hardware-in-the-loop applications; the braking and handling behavior&#xd;
of the example models was simulated faster than real-time on a desktop PC with a 3.2&#xd;
GHz Pentium 4 processor and 1 GB of RAM. For the same vehicle models, a different&#xd;
choice of modeling variables resulted in a mixed set of differential and algebraic equations&#xd;
(DAEs); in that case, HIL-capable simulation code could not be consistently generated.&#xd;
The approach works well for vehicle models described by ODEs, but more research is&#xd;
needed into the treatment of DAEs for real-time simulation of vehicle dynamics.</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="extent">2322353 bytes</dim:field>
   <dim:field mdschema="dc" element="format" qualifier="mimetype">application/pdf</dim:field>
   <dim:field mdschema="dc" element="language" qualifier="iso" lang="en">en</dim:field>
   <dim:field mdschema="dc" element="publisher" lang="en">University of Waterloo</dim:field>
   <dim:field mdschema="dc" element="title" lang="en">Automatic Generation of Real-Time Simulation Code for Vehicle Dynamics using Linear Graph Theory and Symbolic Computing</dim:field>
   <dim:field mdschema="dc" element="type" lang="en">Master Thesis</dim:field>
   <dim:field mdschema="dc" element="pending" lang="en">false</dim:field>
   <dim:field mdschema="dc" element="subject" qualifier="program" lang="en">System Design Engineering</dim:field>
   <dim:field mdschema="uws-etd" element="degree" qualifier="department" lang="en">Systems Design Engineering</dim:field>
   <dim:field mdschema="uws-etd" element="degree" lang="en">Master of Applied Science</dim:field>
   <dim:field mdschema="uws" element="typeOfResource" lang="en">Text</dim:field>
   <dim:field mdschema="uws" element="peerReviewStatus" lang="en">Unreviewed</dim:field>
   <dim:field mdschema="uws" element="scholarLevel" lang="en">Graduate</dim:field>
   <dim:field mdschema="others" element="access-status">open.access</dim:field>
</dim:dim>
</metadata></record></GetRecord></OAI-PMH>