MotoHawk:Model-Based Design - Revision history

Wendy.Bolakowski at 15:24, 1 February 2013

2013-02-01T15:24:40Z

Wendy.Bolakowski at 14:39, 1 February 2013

2013-02-01T14:39:11Z

Wendy.Bolakowski at 14:32, 1 February 2013

2013-02-01T14:32:13Z

Wendy.Bolakowski: /* Why Model Based Design? */

2013-02-01T14:31:42Z

‎Why Model Based Design?

Wendy.Bolakowski: /* What is MotoHawk's Role? */

2013-02-01T14:30:36Z

‎What is MotoHawk's Role?

Wendy.Bolakowski at 14:22, 1 February 2013

2013-02-01T14:22:16Z

Wendy.Bolakowski at 14:21, 1 February 2013

2013-02-01T14:21:42Z

Wendy.Bolakowski at 14:19, 1 February 2013

2013-02-01T14:19:44Z

Wendy.Bolakowski at 14:09, 1 February 2013

2013-02-01T14:09:45Z

Wendy.Bolakowski at 14:04, 1 February 2013

2013-02-01T14:04:39Z

← Older revision		Revision as of 15:24, 1 February 2013
Line 62:		Line 62:

	[[File: MotoHawk_Simulink.jpg\|center\|500px]]		[[File: MotoHawk_Simulink.jpg\|center\|500px]]
		+
		+
		+	== MotoHawk - One Step Build from Model Based Design to Production Hardware ==
		+
		+	Application Engineers work at the Application Layer, implementing for example Sensor Characterizations, Actuator Components, etc in the MotoHawk model. MotoHawk provides the Model Based Developer a blockset to abstract behavior on the hardware (ex. Operating System, Communication, Complex Device Drivers, Module Configuration) as well as build support to allow a one step build from the MotoHawk model to files that can be directly flashed to real production hardware.
		+
		+	[[File:MH_diagram1.jpg\|center\|500px]]

← Older revision		Revision as of 14:39, 1 February 2013
Line 56:		Line 56:

	[[File: puzzle.jpg\|center\|500px]]		[[File: puzzle.jpg\|center\|500px]]
		+
		+	=== The User Works Directly in the Simulink Environment ===
		+
		+	The MotoHawk Blockset is a Toolbox in Simulink, so the user works directly in the Simulink Environment.
		+
		+	[[File: MotoHawk_Simulink.jpg\|center\|500px]]

@@ Line 37: / Line 37: @@
 *'''Readable documentation of system design automatically created from models'''
+<br>
 == What is MotoHawk's Role? ==

@@ Line 25: / Line 25: @@
 [[File:process_comparison.jpg|center|500px]]
 <big>'''Summary'''</big>
 * '''Simpler, faster development cycle that is flexible to unanticipated changes'''

← Older revision		Revision as of 14:30, 1 February 2013
Line 37:		Line 37:

	== What is MotoHawk's Role? ==		== What is MotoHawk's Role? ==
		+
		+	'''MotoHawk is a Toolbox to Simulink and is the glue that connects the Model Based Developer with real production hardware.'''
		+
		+
		+	It is a toolbox to Simulink that uses the customization features to interact with the Woodward Operating System – ControlCore and the hardware devices it supports. This enables a Simulink user to construct models that will be executed on the target hardware that MotoHawk supports using a combination of the native Simulink blocks and the custom MotoHawk blocks.
		+
		+	MotoHawk also interacts with a variety of protocols that are transmitted over a variety of hardware platforms. CAN and Serial are two examples of the hardware. On the software side, we support CCP, XCP, J1939, UDS, among others (and the list is growing). These protocols also support the ability to calibrate MotoHawk applications using Woodward MotoTune, Toolkit, or industry standard tools such as INCA or ATI Vision.
		+
		+	MotoHawk provides an interface to Digital and Analog Input behaviors, as well as more complex behaviors such as Position Synchronized Pulses syncronized by the crank/cam encoder to engine position.
		+
		+	It also provides access to different types of memory such as NonVolatile, RAM and calibration.
		+
		+	Blocks for Fault Detection and Diagnostics (including a blockset for OBD fault management) are also provided to the application developer.
		+
		+
		+	[[File: puzzle.jpg\|center\|500px]]

← Older revision		Revision as of 14:22, 1 February 2013
Line 35:		Line 35:

	*'''Readable documentation of system design automatically created from models'''		*'''Readable documentation of system design automatically created from models'''
		+
		+	== What is MotoHawk's Role? ==

@@ Line 7: / Line 7: @@
 Model Based design allows the Application Designer to work at the Model Level, cutting out the time and expense involved in SW Design, Implementation, SW Debugging, and SW verification.  The low level software for drivers, communication links,  RTOS is done upfront.
-[[File:v_diagram.jpg|center]]
+[[File:v_diagram.jpg|center|400px]]
@@ Line 23: / Line 23: @@
 Model Based Design Allows Software and Application Engineer to work together right from the beginning, rather than 'throwing things over the wall' as unexpected changes occur.  This provides faster more rapid development, and also improves validation and verification capacity because changes can be quickly simulated or applied and tested on real hardware.
-[[File:process_comparison.jpg|center]]
+[[File:process_comparison.jpg|center|500px]]
 <big>'''Summary'''</big>

@@ Line 10: / Line 10: @@
-'''Further, Model Based Design allows for Flexibility to Unexpected Changes.'''   The Design Process is often shown as linear.  One develops a set of Requirements, Designs to meet the requirements, Implements the Design, Verifies the implementation, and the Produces the product.
+'''Model Based Design allows for Flexibility to Unexpected Changes.'''
 [[File:linear_process.jpg|center]]
@@ Line 19: / Line 21: @@
-Model Based Design Allows Software and Application Engineer to work together right from the beginning, rather than 'throwing things over the wall' as unexpected changes occur.
+Model Based Design Allows Software and Application Engineer to work together right from the beginning, rather than 'throwing things over the wall' as unexpected changes occur.  This provides faster more rapid development, and also improves validation and verification capacity because changes can be quickly simulated or applied and tested on real hardware.
 [[File:process_comparison.jpg|center]]

← Older revision		Revision as of 14:09, 1 February 2013
Line 17:		Line 17:

	[[File:circular_process.jpg\|center]]		[[File:circular_process.jpg\|center]]
		+
		+
		+	Model Based Design Allows Software and Application Engineer to work together right from the beginning, rather than 'throwing things over the wall' as unexpected changes occur.
		+
		+	[[File:process_comparison.jpg\|center]]

@@ Line 1: / Line 1: @@
 == Why Model Based Design? ==
 The V diagram below compares hand coding with Model Based Design.  The process starts at the upper left with Specifications.  Often, these specifications are in the form of graphical representations such as a flow chart.   The process continues downward along the left to modeling of the system and then Designing and Implementing Software to meet the requirement.  Once the software is written, then the process continues up along the right of the V, towards debugging the software, SW verification, and then to verification on hardware.   This is in low level code.
@@ Line 5: / Line 7: @@
 Model Based design allows the Application Designer to work at the Model Level, cutting out the time and expense involved in SW Design, Implementation, SW Debugging, and SW verification.  The low level software for drivers, communication links,  RTOS is done upfront.
-[[File:v_diagram.jpg|center|200px]]
+[[File:v_diagram.jpg|center]]